cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager 7.1 SP10 Upgrade using SUM 1.0 SP10 taking long time during the phase MAIN_SHDRUN/DDIC_UPG 38 Hours now

Former Member
0 Kudos

Hello,

We have Installed Solman 7.1 SP4 and now trying to upgrade to SP10.

kernel release                721

kernel make variant           721_EXT_REL

OS windows 2008 R2

DB: Oracle 11.2.0.3

This seems to be stuck in Preprocessing Phase. 

SAPup LOg

CURRENTPHASE MAIN_SHDRUN/CMDFILE_UPG

...started at 20140507212957

...begin processing at 20140507212959

..finished at 20140507213914 with status SUCCEEDED.

CURRENTPHASE MAIN_SHDRUN/DDIC_UPG

...started at 20140507213914

...begin processing at 20140507213916

SAPup.ECO

### Phase MAIN_SHDRUN/DDIC_UPG:

SAPup> Starting subprocess in phase 'DDIC_UPG' at 20140507213929

    ENV: DBMS_TYPE=ora

    ENV: JAVA_HOME=H:\usr\sap\SOL\DVEBMGS00\exe\sapjvm_4

    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

    ENV: ORACLE_HOME=G:\oracle\SOL\11203

    ENV: ORACLE_SID=SOL

    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

    ENV: PATH=H:\usr\sap\SOL\SUM\abap\exe;G:\oracle\SOL\11203\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;H:\usr\sap\SOL\SYS\exe\uc\NTAMD64

    ENV: SAPDATA_HOME=G:\oracle\SOL

    ENV: SAPSYSTEMNAME=SOL

    ENV: auth_shadow_upgrade=1

    ENV: dbs_ora_schema=SAPSR3

    ENV: dbs_ora_tnsname=SOL

    ENV: rsdb_ssfs_connect=0

EXECUTING H:\usr\sap\SOL\SUM\abap\exe\tp.EXE

"pf=H:\usr\sap\SOL\SUM\abap\var\DDICUPG.TPP" put SOL

"-Dmainimp_proc=1" "-Dparallel=3"

This is H:\usr\sap\SOL\SUM\abap\exe\tp.EXE version 380.13.51 (release

721, unicode enabled)

Looking for effective putsteps ... ... ready (looking for putsteps)

ULOG

### Phase MAIN_SHDRUN/DDIC_UPG:

soladm       20140507213919    : H:\usr\sap\SOL\SUM\abap\exe\tp.EXE

pf=H:\usr\sap\SOL\SUM\abap\var\SHADOW.TPP setstopmark buffer=SOL

before SAPK-70107INWEBCUIF  (pid=9528)

soladm       20140507213929    : H:\usr\sap\SOL\SUM\abap\exe\tp.EXE

pf=H:\usr\sap\SOL\SUM\abap\var\DDICUPG.TPP put SOL -Dmainimp_proc=1

-Dparallel=3  (pid=14756)

Parameter Values

abap/heap_area_nondia                       300000000

rsdb/obj/max_objects                        20000

rsdb/obj/buffersize                         50000

sap/bufdir_entries                          10000

zcsa/presentation_buffer_area               20000000

zcsa/db_max_buftab                          10000

zcsa/table_buffer_area                      100000000

rsdb/cua/buffersize                         10000

rtbb/buffer_length                          60000

rsdb/ntab/irbdsize                          15000

abap/shared_objects_size_MB                 350

abap/buffersize                             500000

rdisp/max_wprun_time                        3600

ztta/roll_area                              30000000


Please help.


Raghu

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello,

I have managed to run the phase now.

Just restarted the ORACLE and now the sap\SOL\SUM\abap\tmp directory is updating .

Thanks all. I will update you incase if I get stuck again.

Regards,

Raghu

Former Member
0 Kudos

Hi Raghu,

May i ask you just shutdown and startup oracle without stopping the SUM process and application server? I think at that phase, it cannot choose the Stop Update option right.

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Raise a new thread with the full details of the upgrade. You will get prompt replies.

Former Member
0 Kudos

Hi Shawn,

yes . Just restart the Oracle . leave the SUM update running as it is . Once the restart is finished, check tmp and log folder where you can see the logs updating every 10 or max in 20 minutes . In case it didnt work please carry on as Mr. RB said. SUM will start from the same phase it exited.

Regards

Former Member
0 Kudos

Hi all,

just like to update with respect to what I have done.

Encounter MAIN_SHDRUN/DDIC_UPG running for very long and all the logs are not being updated.

Restarted database --> No use.

Search through all the logs carefully and found out in DDICUPG.SAV has an error stating ORA-03113: End of file on communication channel.

Follow snote 1635605 & added parameter _use_zero_copy_io = false into oracle parameter

Restarted database and this time round, all logs are being updated prompty and the phase ended in only 3 hours.

Former Member
0 Kudos

I can see SAPupStat log as

2014/05/07 21:17:05:  39.08% LEFT: 258:43:48 END: 2014/05/18 16:00:53

2014/05/07 21:27:35:  39.14% LEFT: 258:23:47 END: 2014/05/18 15:51:22

2014/05/07 21:28:31:  39.64% LEFT: 253:02:17 END: 2014/05/18 10:30:48

2014/05/07 21:29:57:  39.81% LEFT: 251:18:37 END: 2014/05/18 08:48:34

2014/05/07 21:39:14:  39.87% LEFT: 250:57:32 END: 2014/05/18 08:36:46


Does it mean it will end on 2014/05/18 ?



Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Do a clean restart of the system and restart the upgrade tool and repeat the phase.

Unfortunately there is no way others can support you without proper trace files.

Restart the systems (main and the shadow) and repeat the phase in upgrade tool and check the latest logs.

madasamy_arunachalam
Active Participant
0 Kudos
Former Member
0 Kudos

Hi Swami/RB

I have checked the table and there is no transport request to be released.

As the system still not ended with error , I could not find any log DDICUPG.ELG . Same time another log DDIC_UPG.ECO which says 140 transport to be imported and tp finished with return code 0 .

And last update happened in usr\sap\SOL\SUM\abap\tmp around 40 hours ago .

Regards

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

You must be hitting the bug mentioned in this SAP note 1635605 - CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE LOB

Set the Oracle parameter _use_zero_copy_io=false and restart the system.

Regards

RB

Former Member
0 Kudos

Hello RB,

I already started with that option.

Regards,

Raghu

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

You mean to say you have already tried that work around before raising this thread ?

In that case I don't in the original post about this information and that is the reason why I suggested as it is a known issue.

Check for the logs in the H:\usr\sap\SOL\SUM\abap\tmp directory