Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error in MAIN_INIT/DB_ACTION_UPG

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 Member
Not what you were looking for? View more on this topic or Ask a question