Looking for effective putsteps ... ... ready . ERROR: stopping on error 12 during DD ACTIVATION

[former_member325638]

Hi Experts,

We are doing stack upgrade of our PI  system using SUM tool. In the preprocessing step; it got terminated with error "Checks after MAIN_SHDRUN/ACT_UPG were negatice. Last error code set : Detected 40 aborted activities in 'ACTUPG.ELG' . tp returned with code 12. Check SAPup.ECO.

In SAPup.ECO; we have below logs

"

EXECUTING /usr/sap/SID/SUM/abap/exe/tp pf=/usr/sap/SID/SUM/abap/var/ACTUPG.TPP put SID
This is tp version 380.29.44 (release 721, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during DD ACTIVATION
stopping on error 12 during DD ACTIVATION

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
SAPup> Process with PID 28990 terminated with status 12 at 20150623073200!

"

But other than above; there is no errors like lw memory or an ySQL error as found in few SDN posts or SA notes. Went through other log files as wel but there is nothign much useful. In SAP; there is no ABAP dump or failed jobs. Could you please help

Thanks

Varun

[former_member182657 · Accepted solution]

Suggest you to follow SAP Note 2050604 - Problem analysis in upgrade: Phase ACT_UPG

You may only choose "IGNORE errors" or "IGNORE non-severe errors" if you can ensure that no data loss can occur and that no SAP tables or SAP views are affected. It is also possible for syntax errors that require an upgrade reset to take place in later phases such as in the second run of the shadow instance.

Regards,

[former_member325638 · Accepted solution]

Hi Gaurav,

ACTUPG.ELG file output is below

"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DDIC ACTIVATION ERRORS and RETURN CODE in /usr/sap/<SID>/SUM/abap/log/SAPA-71106INPIBASIS.<SID>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<NO ERROR LINES FOUND, BUT HIGHEST EXIT CODE WAS: "12">"

and in SAPA-71106INPIBASIS.<SID>; it shows below

"

EPU324 See log for request "SAPKB71106" (timestamp "07:31:50", system "<SID>")
1 ETP155 ACTIVATION OF DD-OBJECTS
1 ETP110 end date and time   : "20150623073151"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
4 EPU202XEND OF SECTION BEING ANALYZED END OF ACT_UPG ======================================================

"

While going through every file inside abap/log folder. In file SHDINST.OUT; noticed below

"

Maximum shared memory size > 20G
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0

SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =486000000

Shared memory disposition overview
================================================================
Shared memory pools
Key:   10  Pool
            Size configured.....:   128000000 ( 122.1 MB)
            Size min. estimated.:   121836508 ( 116.2 MB)
            Advised Size........:   126000000 ( 120.2 MB)

Key:   40  Pool for database buffers
            Size configured.....:   112000000 ( 106.8 MB)
            Size min. estimated.:   482199040 ( 459.9 MB)
            Advised Size........:   486000000 ( 463.5 MB)

Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....:         30
System-imposed number of shared memories.:        206
Shared memory segment size required min..:  486000000 ( 463.5 MB)
Currently available maximum segment size.: 34359738368 (32768.0 MB)

"

I think this is something need to be corrected

Thanks

Varun

[former_member182657 · Accepted solution]

Hi Varun,

Have you followed previously mentioned SAP Note by me ? Also request you to share file SAPA-71106INPIBASIS.<SID> .

Thanks,

[former_member325638 · Accepted solution]

Hi Gaurav

Yes; have already gone through the note but it does not exactly mention anything about shared memory. The output of file SAPA-71106INPIBASIS.<SID> ; I hav ealready posted in my reply yesterday.

Now after increasing the value of parameter; ipc/shm_psize_40; we were able to proceed further. In next stage getting below error

"

2015/06/24 02:46:44  START OF PHASE MAIN_SHDRUN/ACT_UPG

Collecting adjustments ...

<< 2015/06/24 02:46:44  END OF PHASE   MAIN_SHDRUN/ACT_UPG
INFO: shadow instance unlocked.
Synchronizing buffers via 'UPG_BUFFER_SYNC'...
WARNING: Unlocking system failed with 'RFC login to system <SID> ashost <server name> nr 03 gwhost <server name> gwservice sapgw03 failed with code 1 key RFC_COMMUNICATION_FAILURE:
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '<IP address>:3303' not reached
TIME        Wed Jun 24 02:46:50 2015
RELEASE     721
COMPONENT   NI (network interface)
VERSION     40
RC          -10
MODULE      nixxi.cpp
LINE        3283
DETAIL      NiPConnect2: <IP address>:3303
SYSTEM CALL connect
ERRNO       146
ERRNO TEXT  Connection refused
COUNTER     9
'!
=========== Repeat Phase ===========

Severe error(s) occurred in phase MAIN_SHDRUN/ACT_UPG!

Last error code set: RFC login to system <SID> ashost <server name> nr 03 gwhost
<server name> gwservice sapgw03 failed with code 1 key
RFC_COMMUNICATION_FAILURE: <br/> LOCATION CPIC (TCP/IP) on local host with
Unicode<br/> ERROR partner '<IP address>:3303' not reached<br/> TIME Wed Jun
24 02:46:44 2015<br/> RELEASE 721<br/> COMPONENT NI (network interface)<br/>
VERSION 40<br/> RC -10<br/> MODULE nixxi.cpp<br/> LINE 3283<br/> DETAIL
NiPConnect2: <IP address>:3303<br/> SYSTEM CALL connect<br/> ERRNO 146<br/>
ERRNO TEXT Connection refused<br/> COUNTER 6<br/>"

While I check in SM59; the RFC 'SAP_UPGRADE_SHADOW_SYSTEM' is facign connection failure

"

ERROR: partner 'servername.com:sapgw03' not reached

LOCATION: SAP-Gateway on host server name.com / sapgw00

ERROR NUMBER: 146

ERROR TEXT: Connection refused

RETURN CODE -10"

The local instavce is sapgw00 and shadow instance auto created is trying sapgw03. Do we need to make any manul change to this RFC to wor properly.

Thanks

Varun

[divyanshu_srivastava3 · Accepted solution]

Is your SAP and shadow system up ?

[former_member325638 · Accepted solution]

Hi Divyanshu

Main SAP system is up but shadow system is not up.

Thanks

Varun

[divyanshu_srivastava3 · Accepted solution]

I am not looking anywhere in your message - just RFC error only - that it failed.

For 2 system to communicate - bith should be UP... right ?

So from where to where if the RC not working ?

Regards,

[former_member325638 · Accepted solution]

Hi Divyanshu

Yes; systems should be up to communicate. BUt the same is taken care by SUM tool while stack upgrade. Should we try to start shadow instance DVEBMGS03 manually iwht startstap r3 DVEBMGS00 or there is some other thing to be looked at here

Thanks

Varun

[divyanshu_srivastava3 · Accepted solution]

if it is that RFC which is blocking your upgrade then the instance DVEBMGS03 should be started...!!

Regards,

[former_member325638 · Accepted solution]

Hi

Started shadow instance using below command

SAPup stopshd

from directory

/usr/sap/<SID>/SUM/abap/bin

It unlocked shadow instance as well

But its stuck in DDIC activation again and tp returned with code 12. Same error messages as shown previously. The transport log shows below

"

Main language for documentation module CA_FSBP_TAXC_TBZ0A not found

Setting up Repository tree: no object list found

Error during copy of DDIC objects from switches"

Found one note 1476315 for this. But both maual corrections mentioned in this note are already applied

Could you please help

Thanks

Varun

[former_member325638 · Accepted solution]

Hi All

After applying note corrections from 1476315 , for errors in transports related XPRA_EXECUTION.

We manually applied note 415682

DDIC was not able to make change so we had to do with self user ID after unlocking

To do the steps we stopped SUM and then unlocked using tp commands

tp unlocksys <SID> pf=./TPPARAM

tp unlock_EU <SID> pf=./TPPARAM

After this; patching went through successfully

Thanks

Varun

[divyanshu_srivastava3 · Accepted solution]

That's good news..!!

Regards,

[former_member182657]

Hi Varun,

Could you share ACTUPG.ELG log file.Also confirm for the option Accept & Ignore the non sever error on the issue screen.

Regards,

[manumohandas82]

Hi Varun ,

Did you check the transport logs  . ( ALOG , SLOG )

Thanks ,

Manu

[former_member325638]

Hi Manu

Nothing useful found in these two log files too

"

ERROR SAPKW71114           <SID> A 0012 20150623071507 SAP          <SID>adm       <server name> 201506230715050052ce

STOP  tp_getprots          <SID> A      20150623071510              <SID>adm       <server name> 201506230715050052ce

STOP  DD ACTIVATION        <SID> A      20150623071510              <SID>adm       <server name> 201506230715050052ce

ERROR: stopping on error 12 during DD ACTIVATION"

Thanks

Varun