ECC5 to ECC6 (Windows MAXDB) - Prepare phase : SHDINST_DB_PREP Error

[Former Member]

Hello All

In the mentioned phase I receive the below error:

"Upgrade phase "SHDINST_DB_PREP" aborted with severe errors"

As per the guide, I have changed the MAXUSERTASKS and MAXLOCKS.

Please see below extract from the SHDDBBRP.LOG:

1 ETQ201XEntering upgrade-phase "SHDINST_DB_PREP" ("20071115080750")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ada_schema=SAPECT

4 ETQ399 auth_shadow_upgrade=0

4 ETQ399 SQLOPT=DEFAULT

4 ETQ399 checking db user / DB for shadow system ...

1EETQ204 Upgrade phase "SHDINST_DB_PREP" aborted with severe errors ("20071115080750")

Many thanks

Anwar

[markus_doehr2]

Check the log SHDDBBRP.ELG.

--

Markus

[Former Member]

Thank-you

I think you meant SHDDBPRP.LOG, as the one you mentioned does not exist. I have checked, the output is as below:

1 ETQ201XEntering upgrade-phase "SHDINST_DB_PREP" ("20071115080750")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ada_schema=SAPECT

4 ETQ399 auth_shadow_upgrade=0

4 ETQ399 SQLOPT=DEFAULT

4 ETQ399 checking db user / DB for shadow system ...

1EETQ204 Upgrade phase "SHDINST_DB_PREP" aborted with severe errors ("20071115080750")

Regards

Anwar

[markus_doehr2]

That is the RFC call of that phase but not the actual error your face.

Sort the files in /usr/sap/put/log via data and check the latest ones for error.

--

Markus

[Former Member]

Tried that already, have been through all the log files.

There is a generic tp error, but this cannot be the root cause as tp checks out fine, if tested.

My suspicion is that it is more then likely a MAXDB authentication issue with the shadow instance, which cannot authenticate on the DB level, I could be wrong though.

[markus_doehr2]

Each phase during the upgrades writes a file in case of an error, it may be difficult to find that one though...

Did you also look in \usr\sap\put\tmp

and

\usr\sap\trans\log

--

Markus

[Former Member]

Thanks, checked. Nothing of relevance.

[markus_doehr2]

You are on MaxDB 7.6, yes?

--

Markus

[Former Member]

yes, 7.6.03.

This might help, the specific error when the upgrade assistant stops is:

ERROR: Check User Operation failed (File SAPECTSHD not found) ; note ECT being my SID.

Thanks a lot.

[markus_doehr2]

On our (already upgraded) system this phase looks like

1 ETQ201XEntering upgrade-phase "SHDINST_DB_PREP" ("20071030165544")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ada_schema=SAPP01

4 ETQ399 auth_shadow_upgrade=0

4 ETQ399 SQLOPT=

4 ETQ399 checking db user / DB for shadow system ...

4 ETQ399 ext. env.: DIR_LIBRARY=/usr/sap/P01/SYS/exe/run

4 ETQ399 ext. env.: LD_LIBRARY_PATH=/usr/sap/P01/SYS/exe/run:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava

2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/P01/SYS

/exe/run:/sapdb/programs/lib

4 ETQ399 2007/10/30 16:55:44: put_execute: (tp) forkpid:32700

4 ETQ399 creating db user / DB for shadow system ...

4 ETQ399 ext. env.: DIR_LIBRARY=/usr/sap/P01/SYS/exe/run

4 ETQ399 ext. env.: LD_LIBRARY_PATH=/usr/sap/P01/SYS/exe/run:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava

2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/P01/SYS

/exe/run:/sapdb/programs/lib

4 ETQ399 2007/10/30 16:55:45: put_execute: (tp) forkpid:32705

4 ETQ399 user created successfully

1 ETQ202 Upgrade phase "SHDINST_DB_PREP" completed sucessfully ("20071030165545")

So the system is trying to create the user/the schema SAPECTSHD. Our SID is P01 and I don´t have a file SAPP01SHD.

Never seen that error before and I have no more idea.. I think you should open a call on BC-UPG if no one else comes up with another idea...

--

Markus

[Former Member]

Thank-you Markus, your help is appreciated. I will leave this open for now, possibly someone else can shed some light on this.

[Former Member]

Hello Anwer,

By looking at ur log i didnt understand why there is a default in the log for SQLOPT and not there on ur earlier upg...

4 ETQ399 SQLOPT=DEFAULT

I think DB is tring to create the shadow user but somehow not able to do it.I have seen this kind of problems during upg.You can actually create SHADOW Instance user and repeat the phase.

also assign DBA rights to the user.

hope this solves ut problem.

rgds,

Vamshi.