Take long time MAIN_SHDCRE/SHADOW_IMPORT_UPG1 is normal?

    Hello guys !!!!

    I’m running an upgrade from SAP R/3 4.7 Enterprise ext.110 to ERP 6. + EHP6 SP07.

    My platform is Windows 2008 R2 and Oracle 11.2g

    The version I’m using is SUM SUM 1.0 SP07.

    Currently the upgrade is in step 5.5 Preprocessing and MAIN_SHDCRE/SHADOW_IMPORT_UPG1 phase.

    This phase began yesterday at 3 pm and the last update of the logs was at 4:41 pm, I was reviewing at night and there is no more any files updated.

    Today when you arrive is at the same phase and decide to stop, but it would seem that it was disconnected from the SUM.

    I start running again, and returned to start the same phase and has only been updated to now PHASES.txt file in the directory: x:\usr\sap\<sid>\SUM\abap\log, and displays the following information :

    1 ETQ201 Entering upgrade-phase “MAIN_SHDCRE/SHADOW_IMPORT_UPG1” (“20130521151200”)

    2 ETQ399 Setting SQL connect to standard DB.

    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_ora_schema=SAP<sid>

    4 ETQ399   auth_shadow_upgrade=<null>

    1 ETQ200 Executing actual phase ‘MAIN_SHDCRE/SHADOW_IMPORT_UPG1’.

    1 ETQ399 Phase arguments:

    2 ETQ399 Arg[0] = ‘SHDUPG1.BUF’

    2 ETQ399 Arg[1] = ‘SHDUPGIMP1.TP0’

    2 ETQ399 Arg[2] = ”

    2 ETQ399 Arg[3] = ‘parallelgroups’

    1 ETQ399 Using error summary log ‘SHDUPGIMP1.ELG’.

    1 ETQ399 Executing putsteps ‘HK’.

    4 ETQ380 computing toolpath for request “TP_IMPORT_TO_SHADOW”

    4 ETQ381 request “TP_IMPORT_TO_SHADOW” means “tp calles R3trans with import to shadow”

    4 ETQ382 translates to group “R3UP_TOOL_GROUP_SHDNEW”

    4 ETQ399 Requirement for tp maps to ‘exe’

    4 ETQ383 translates to path “x:\usr\sap\<sid>\SUM\abap\exe”

    2 ETQ399 Copying buffer ‘SHDUPG1.BUF’ to target ‘<sid>‘.

    2 ETQ399 Sorting transports between syncmarks for decreasing size to optimize parallel import.

    2 ETQ399 Analyzing buffer ‘<sid>’ to optimize parallel execution.

    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_NEW”

    4 ETQ399 Requirement for tp maps to ‘exe’

    4 ETQ383 translates to path “x:\usr\sap\<sid>\SUM\abap\exe”

    3 ETQ399 20130521151200: PID 15224 execute ‘x:\usr\sap\<sid>\SUM\abap\exe\tp pf=x:\usr\sap\<sid>\SUM\abap\var\DEFAULT.TPP showbuffer buffer=<sid> -DR3UP=1’ , output written to ‘x:\usr\sap\<sid>\SUM\abap\log\SHADOW_I.ECO’.

    3 ETQ399 20130521151200: PID 15224 exited with status 0

    4 ETQ384 restoring old toolpath for request “TP_IMPORT_TO_SHADOW”

    4 ETQ399 Requirement for tp maps to ‘exe’

    4 ETQ383 translates to path “x:\usr\sap\<sid>\SUM\abap\exe”

    3 ETQ399 Determined 1 transport groups in buffer.

    3 ETQ399 Estimating maximum useful number of processes for each group.

    4 ETQ399 1: Reducing process upper limit from 40 to 9 due to large transport of 154.396MB from total 1377.19MB.’

    3 ETQ399 Analysis of buffer ‘<sid>’ yields 1 parallel groups:

    4 ETQ399 1: 40 transports between syncmarks, range from ‘SAPKLFR606CAECC606F3’ to ‘SAPKLES606CAECC606F0’. Max parprocs 9.

    4 ETQ399 Group 1: Calling ‘tp put’ for transports from ‘SAPKLFR606CAECC606F3’ to ‘SAPKLES606CAECC606F0’.

    4 ETQ399 Distributing 3 parallel processes for import.

    2 ETQ399 Distribute 3 parallel processes to 3 tp and 1 R3trans.

    3 ETQ399 20130521151205: PID 15256 execute ‘x:\usr\sap\<sid>\SUM\abap\exe\tp pf=x:\usr\sap\<sid>\SUM\abap\var\DEFAULT.TPP delstopmark buffer=<sid>’ , output written to ‘x:\usr\sap\<sid>\SUM\abap\log\TP.ECO’.

    3 ETQ399 20130521151205: PID 15256 exited with status 0

    3 ETQ399 20130521151205: PID 15276 execute ‘x:\usr\sap\<sid>\SUM\abap\exe\tp pf=x:\usr\sap\<sid>\SUM\abap\var\SHDUPGIMP1.TPP put <sid> -Dmainimp_proc=3 -Dparallel=no’ in background, output written to ‘x:\usr\sap\<sid>\SUM\abap\log\SAPup.ECO’.

    1 ETQ399 Scanning logs meanwhile takes 2 seconds.

    1 ETQ399 Scanning logs meanwhile takes 2 seconds.

    1 ETQ399 Scanning logs meanwhile takes 2 seconds.

    1 ETQ399 Scanning logs meanwhile takes 3 seconds.

    1 ETQ399 Scanning logs meanwhile takes 2 seconds.

    This last line is repeated each time the file is updated

    It will be running the process? It´s normal?

    No movement is memory and cpu, if I see disk recording. The server has enough space. The tablespace has space as well.

    What has been your experience in this phase of the upgrade?

    I appreciate any comments that can help me.

    Desirée C.

    Hello guys !!!!I'm running an upgrade from SAP R/3 4.7 Enterprise ext.110 to ERP 6. + EHP6 SP07.My platform is Windows 2008 R2 and Oracle 11.2gThe version I'm using is SUM SUM 1.0 SP07. Currently the upgrade is in step 5.5 Preprocessing and MAIN_SHDCRE/SHADOW_IMPORT_UPG1 phase.This phase began yesterday at 3 pm and the last update of the logs was at 4:41 pm, I was reviewing at night and there is no more any files updated.Today when you arrive is at the same phase and decide to stop, but it would seem that it was disconnected from the SUM.I start running…

    Take long time MAIN_SHDCRE/SHADOW_IMPORT_UPG1 is normal?

    Very Helpfull

    User Rating: Be the first one !
    Vice Professor Asked on November 2, 2016 in 60 upgrade.
    Add Comment
    1 Answer(s)

      Hello Surojit

       

      I could solve using SAP OSS Note: 1635605 CLIENT HANGS ON INSERT INTO TABLE WITH LOB SecureFile.

       

      Add the Oracle parameter via SQLnet: _use_zero_copy_io = false

       

      With this change continued the upgrade process normaly.

       

      Thanks for the help

       

      Desirée C.

      Add Comment

        Hello Surojit

         

        I could solve using SAP OSS Note: 1635605 CLIENT HANGS ON INSERT INTO TABLE WITH LOB SecureFile.

         

        Add the Oracle parameter via SQLnet: _use_zero_copy_io = false

         

        With this change continued the upgrade process normaly.

         

        Thanks for the help

         

        Desirée C.

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.