11g upgrade question - is BW system but is reported as NOT one.

[vince_laurent]

I am running the pre-upgrade script and there is a section that looks like this:

check_info('Check for SAP BW system');
   BEGIN
       sap_bw := FALSE;
       FOR obj IN (SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'RSADMINA' and owner like 'SAP%' and length(owner) = 6) LOOP
         display_trace('RSADMINA-owner: ' || obj.owner);
         BEGIN
                 BEGIN
             EXECUTE IMMEDIATE 'SELECT bwmandt from ' || obj.owner || '.RSADMINA ' INTO sap_bwmandt;
           EXCEPTION 
             WHEN OTHERS THEN NULL;
           END;
           display_trace('BW Mandt: ' || sap_bwmandt);
           display_trace('Length(BW Mandt): ' || nvl(length(ltrim(sap_bwmandt, ' ')),0));
           --if length(sap_bwmandt) > 0 then
           if nvl(length(ltrim(sap_bwmandt, ' ')),0) > 0 then
             sap_bw := TRUE;
             sap_bw_status := 'YES';
           else
             sap_bw := FALSE;
             sap_bw_status := 'NO';
           end if;
         END;
       END LOOP;
   EXCEPTION
       WHEN NO_DATA_FOUND THEN 
         sap_bw_status := 'UNKNOWN';
   END;

I AM upgrading a BW system. Why did this return a FALSE? is this something I need to be concerned about?

Currently running 10.2.0.4 on HP-UX 11.31

[volker_borowski2 · Accepted solution]

Hi,

if you browse table RSADMINA in SE16, what is the value in field BWMANDT?

It should be set if your System is BW.

The script obviously thinks this value to be empty.

Do you have a MCOD system and may be multiple SAP% Users in the DB?

Volker

[volker_borowski2 · Accepted solution]

Aaaah :

like 'SAP%' and length(owner) = 6) LOOP

Your system is an old one and the OWNER is SAPR3 and thus only 5 chars long !

Volker

[vince_laurent · Accepted solution]

Since SAP is down I checked it manually:

SQL> select bw_user, bwmandt from sapr3.rsadmina;
ALEREMOTE    923

[volker_borowski2 · Accepted solution]

>

> Since SAP is down I checked it manually:
> 

> SQL> select bw_user, bwmandt from sapr3.rsadmina;
> ALEREMOTE    923
> 

GOTCHA:

So SAPR3 is your schema user and it is only 5 chars long, so the script fails,

because it is only accepting SAP% users with a length of 6.

Volker

[vince_laurent · Accepted solution]

So is this an error/warning I can ignore? Or should I change the user or what?

[volker_borowski2 · Accepted solution]

Hi,

from what release do you upgrade to which one ?

May be there is a note stateing to apply a corrected script.

Usually these are in the FIX_... packs that need to be applied in the beginning of the upgrade.

Did you search SMP for the name of the script ?

Volker

[vince_laurent · Accepted solution]

I am not upgrading BW at all. I am trying to upgrade Oracle from 10g to 11g and the message about NOT being a BW system appeared from running the pre_upgrade_status.sql script.

[volker_borowski2 · Accepted solution]

Ok, i think I missunderstood.

You are not upgrading BW , you are upgrading Oracle on a BW system !

Change the 6 to a 5 in the script should do the job !

Volker

same time post ..:-)

Edited by: Volker Borowski on Feb 10, 2011 9:00 PM

[vince_laurent · Accepted solution]

In other words, you think I can disregard the warning?

My BW Admin isn't real confortable with that so I guess I need to open a ticket with SAP.

Thanks for your quick responses!

Edited by: Vince Laurent on Feb 10, 2011 9:11 PM

Edited by: Vince Laurent on Feb 10, 2011 9:11 PM

[volker_borowski2 · Accepted solution]

I am not at a system right now, so I can't check the script myself.

Note 1431793 - Oracle 11.2.0: Upgrade Scripts

has an attachment, which might be outdated.

If you upgrade to 11.2.0.2 this script should come from the latest SBP in it's most recent version.

From what I see there, it is just logging information and not doing any changes to the DB.

(no insert, update or delete in the script)

So I'd change in

owner like 'SAP%' and length(owner) = 6) LOOP

the 6 to a 5 and proceed (of course, I take no warranty

But if you are uncertain, you should log a call.

Volker