Error in MAIN_INIT/DB_ACTION_UPG

[Former Member]

Hi,

We are performing a SP upgrade  for  a Solution Manager   and now we are in the initial stage of pre-processing phase after the lock of the downtime . We are getting the below error .

Has anyone faced this error before . If yes, please guide me on how to fix it. I searched in the SAP portal and other places but couldn’t find any concrete  solution.

XXXXXX:[/var/crash/SUM/abap/log](root)# more DBACTUPG.LOG

1 ETQ201 Entering upgrade-phase "MAIN_INIT/DB_ACTION_UPG" ("20150327135402")

2 ETQ367 Connect variables are set for standard instance access

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

4 ETQ399 Environment variables:

4 ETQ399   dbs_syb_schema=SAPSR3

1 ETQ206 Executing pre-phase DB specific actions.

1 ETQ200 Executing actual phase 'MAIN_INIT/DB_ACTION_UPG'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'CONTAINER'

2 ETQ399 Arg[1] = 'SELDBSU.$(DBAEXT)'

2 ETQ399 Arg[2] = 'SELDBSU.LOG'

2 ETQ399 Arg[3] = 'oramaext.sql'

2 ETQ399 Arg[4] = 'ALTDBS.LOG'

1 ETQ399 Expanded phase arguments:

2 ETQ399 Arg[1] = 'SELDBSU.SYB'

3 ETQ121 20150327135402: PID 27102 execute '/var/crash/SUM/abap/bin/sybctrl exec_cmd -f /var/crash/SUM/abap/bin/SYBALTERINROW.SQL -u SAPSR3 -o /var/crash/SUM/abap/log/SYBALTERINROW.LOG' in backgrou

nd, output written to 'SYBALTERINROW.OUT'.

3 ETQ122 20150327135402: PID 27102 exited with status 255 (time: 0.000/0.000/0.012 real/usr/sys)

4 ETQ399 20150327135402: WAITED for 1 processes to finish, 0 aborted.

1EETQ399 Last error code set is: OSQL call failed for SYBALTERINROW

1EETQ204 Upgrade phase "DB_ACTION_UPG" aborted with severe errors ("20150327135402")

XXXX:[/var/crash/SUM/abap/log](root)#

Thanks and Regards,

Vimal

[former_member182657]

Is file SYBALTERINROW.LOG exists ? Please share and raise SAP OSS as well.

Thanks,

[former_member182657]

Hi Vimal,

Last error code set is: OSQL call failed for SYBALTERINROW

Have you checked SAP Note   2052760 - MSS: Additional Information – Software Update Manager 1.0 SP12

with below

OSQL call failed for MSSUPGGETREL in phase PREP_PRE_CHECK/INITPUT_PRE
If you followed SAP Note 965908 to use SQL Server Database Mirroring and changed the environment variable MSSQL_SERVER for the <sid>adm user SUM will fail in phase PREP_PRE_CHECK/INITPUT_PRE
Please stop SUM and make sure that all processes of SUM are closed.
Change the environment variable to only contain the principal server.
Restart SUM
Enable database mirroring again after SUM has finished by setting the environment variable back to its old value

As the resolution is completely different from yours in terms of DB,but you could consider it.

Hope this will help you to push the phase.

Good luck !!

[Former Member]

Hi,

I have already tried that..But no forward movement.

Thanks,

Vimal

[former_member182657]

Hi,

Could you share SYBALTERINROW.OUT file as well as SUM version.

Thanks,

[Former Member]

There is no SYBALTERINROW.OUT created.

SUM version is 12

any other suggestions ?

[former_member182657]

And what about with SYBALTERINROW.LOG file ? Have you checked by complete restart of the system ?

Thanks,

[Former Member]

Yes. We have tried after complete system restart .

[Reagan]

And have you checked the additional logs mentioned in the DBACTUPG.LOG?

Most likely an issue at the Sybase side. The other option is to try with a different kernel patch set.

If you have checked all the SAP KBA's and notes then the best solution is to raise an OSS message.

[Former Member]

Hi,

We are in Latest Kernel . We were able to peform the upgrade in sandbox & Development without any issues.

Thanks and Regards,

Vimal

[Reagan]

Unfortunately there is very little information available in your post to assist you. If you were able to upgrade the sandbox and development without any issues then check if all the systems in the landscape are consistent (kernel level, client libraries and DB version / patch level) and if they are then check with SAP support.

Good Luck

RB