Solman 7.1: Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative

[Former Member]

Hi experts,

during the Upgrade in phase Downtime the following error occurs:

Checks after phase MAIN_NEWBAS/XPRAS_AIMMRG were negative
Last error code set: Unresolved requests in buffer <SID>

Check logfiles 'XPRASUPG.ELG' and '/usr/sap/<SID>/SOLMANUP/abap/log/SAPup.ECO'

Trouble Ticket Generation

A trouble ticket and an archive with all relevant log files have been generated. 
Trouble ticket: "/usr/sap/<SID>/SOLMANUP/abap/log/SAPup_troubleticket.log" 
Log archive: "/usr/sap/<SID>/SOLMANUP/abap/log/SAPup_troubleticket_logs.sar"

To repeat the phase is not the solution. The error occurs again.

Logfile SAPup.ECO:

### Phase XPRAS_AIMMRG:
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 21037196 at 20120104084915
ENV: CLASSPATH=:/db2/db2<sid>/sqllib/java/sqlj.zip:/db2/db2<sid>/sqllib/java/db2java.zip:/db2/db2<sid>/sqllib/java/runtime.zip:.
ENV: DB2DBDFT=<SID>
ENV: DB2INSTANCE=db2<sid>
ENV: DIR_LIBRARY=/usr/sap/<SID>/DVEBMGS03/exe
ENV: JAVA_HOME=/usr/java14_64
ENV: LIBPATH=/usr/sap/<SID>/DVEBMGS03/exe:/usr/sap/<SID>/SOLMANUP/jvm/jre/lib/ppc64/server:/usr/sap/<SID>/SOLMANUP/jvm/jre/lib/ppc64
:/usr/sap/<SID>/SOLMANUP/jvm/jre/../lib/ppc64:/usr/sap/<SID>/SOLMANUP/jvm/jre/lib/ppc64/jli:/usr/sap/<SID>/SOLMANUP/jvm/jre/../lib/p
pc64/jli:/usr/lib:/lib:/usr/sap/<SID>/SYS/exe/run
ENV: PATH=/usr/sap/<SID>/DVEBMGS03/exe:.:/home/<sid>adm:/usr/sap/<SID>/SYS/exe/run:/opt/OpenSource/bin:/opt/freeware/bin:/usr/bin:/e
tc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14_64/jre/bin:/usr/java14_64/bin:/db2/db2<SID>/sqllib/bin:/db2/db2<SID>/sqllib/a
dm:/db2/db2<SID>/sqllib/misc:/usr/tivoli/tsm/client/ba/bin
ENV: SAPSYSTEMNAME=<SID>
ENV: auth_shadow_upgrade=0
ENV: dbms_type=db6
ENV: dbs_db6_schema=SAP<SID>

EXECUTING /usr/sap/<SID>/DVEBMGS03/exe/tp (/usr/sap/<SID>/DVEBMGS03/exe/tp) pf=/usr/sap/<SID>/SOLMANUP/abap/bin/XPRASUPG.TPP put <SID>
This is /usr/sap/<SID>/DVEBMGS03/exe/tp version 375.98.07 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT

tp returncode summary:

TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
  A tool used by tp aborted
Process with ID 21037196 terminated with status 12

[Former Member]

Last but not least the log SAPK702XPRA00000023.<SID>

A3 E/SAPCND/TRANSPORT 011XTransport: Execution of method "/SAPCND/TRN_AFT_IMP_CLIENT_OW"
1AETR012XProgram terminated (job: "RDDEXECL", no.: "12460300")
1AEPU320 See job log"RDDEXECL""12460300""<SID>"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time   : "20120103125339"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP101 transport order     : "SAPK702XPRA00000023"
1 ETP102 system              : "<SID>"
1 ETP108 tp path             : "/usr/sap/<SID>/DVEBMGS03/exe/tp"
1 ETP109 version and release : "375.98.07" "720"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK702XPRA00000023"
4 EPU111    on the application server: "<server>"
2 EPU122XPost-import method "/SAPCND/TRN_AFT_IMP_CLIENT_OW" started for "/SAPCND/VC_GROUP" "C", date and time: "20120103125556
"

[Former Member]

Hi,

Are you able to login to the Solution Manager ABAP instance 03. As from the logs, the jobs are running in this shadow instance.

Would have to check the jobs logs, as to why the job is getting cancelled.

Regards,

Srikishan

[nicholas_chang]

Hi,

Please have a look in SM37 -> RDDEXECL which were canceled. You can get more info from there. Also, paste job message if you need help.

Cheers,

Nicholas Chang

[Former Member]

In logfile XPRASUPG.ELG is written that I have to check the job log, but I can't logon the SAP System, the error message "connection refused" occurs

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR702XPRA00000023.<SID>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08512603")

  Long text: see above

1AEPU320 See job log"RDDEXECL""08512603""<SID>"
1 ETP111 exit code           : "12"

Maybe the phase.log is also interesting:

1 ETQ201 Entering upgrade-phase "XPRAS_AIMMRG" ("20120104084915")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '03', GwService = 'sapgw03'
4 ETQ399 Environment variables:
4 ETQ399   dbs_db6_schema=SAP<SID>
4 ETQ399   auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_NEWBAS/XPRAS_AIMMRG'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'XPRASUPGMOD.BUF'
2 ETQ399 Arg[1] = 'XPRASUPG.TPP'
2 ETQ399 Arg[2] = 'XPRASUPG.TP0'
2 ETQ399 Arg[3] = 'XPRASUPG.ELG'
2 ETQ399 Arg[4] = 'AFTXPRAS.BUF'
4 ETQ399 2012/01/04 08:49:15: put_execute: (tp) forkpid:21037196
2WETQ399 tp terminated with status 12
4 ETQ399 2012/01/04 08:52:33: put_execute: (tp) forkpid:21037198
4 ETQ380 computing toolpath for request "TP_ACT_ON_NEW_BUFFER"
4 ETQ381 request "TP_ACT_ON_NEW_BUFFER" means "act on the tp buffer, new format"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_SYS"
4 ETQ383 translates to path "/usr/sap/<SID>/DVEBMGS03/exe"
4 ETQ399 2012/01/04 08:52:36: put_execute: (tp) forkpid:21037200
2 ETQ399XAnalyze summary error logfile XPRASUPG.ELG and remove all error
2 ETQ399Xconditions as described in the upgrade manual
4 ETQ010 Date & Time: 20120104085236

If I execute ps -ef on os, I can see that all processes for the shadow system are running (dw, ms, jc etc.). But for the normal system only the java processes are running. So I can't logon the system and check the error. I've read that the shadow instance should not exist in this phase.

Can anybody help me?

Thanks and best regards,

Max

[Former Member]

Hi Max

You wrote, that you are not able to login to your shadow instance (which would be 03). If so, it is still possible to get a bit more information about the error. Go to /usr/sap/<SID>/DVEBMGS03/work and use "grep", "less" or "more" on dev_w* - files to find the correct work process where the failing step was running on.

To have a look into your shadow instance, you could also use dpmon pf=<profile-of-DVEBMGS03>. Like this you should be able to see, if your shadow instance waits on any resource.

Regards, Michael

[Former Member]

Hi experts,

many thanks for your answers. It was possible to logon in the shadow system, I had some problems with saprouter and /etc/services.

In the shadow system I found the short dump:

Error in the ABAP Application Program

The current ABAP program "/SAPCND/SAPLCUSTOMIZING_GEN" had to be terminated
 because it has
come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "/SAPCND/SAPLCUSTOMIZING_SRV "
 in include "/SAPCND/LCUSTOMIZING_SRVU32 " in
line 16:
"The type "/SAPCND/ENGINE_TYPE" is unknown."
" "
" "
" "

The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program

The current ABAP program "/SAPCND/SAPLCUSTOMIZING_GEN" had to be terminated
 because it has
come across a statement that unfortunately cannot be executed.

In the Job-Log was the following message:

Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server svc12312 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled

Best regards,

Max

[Former Member]

Hi experts,

the solution is described in this thread: /thread/2016542 [original link is broken]

After activating the enhancement spot '/SAPCND/ENGINE_TYPE' it works fine.

Many thanks for your help!

Best regards,

Max