cancel
Showing results for 
Search instead for 
Did you mean: 

Error during phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/JOB_UPDATE_DDYTT of EHP6 upgrade

arsnlgunnr
Participant
0 Kudos

Hi,

I am getting the following error at phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/JOB_UPDATE_DDYTT while running ECC6 EHP6 upgrade using the SUM tool.  I have searched through the logs but am only able to find useful information in the log PUPDYTT.  I haven't been able to find a SAP note for the error either.  Has anyone ever seen this?  Thanks in advance!

#--------------------------------------------------------------

#---- MASKING file PUPDYTT.LOG from H:\EHP6\kernel\SUM\abap\log

#---- TIME: 20130417194426  PHASE: JOB_UPDATE_DDYTT

#--------------------------------------------------------------

1 ETQ201 Entering upgrade-phase "JOB_UPDATE_DDYTT" ("20130417191750")

4 ETQ399 Set environment for shadow connect:

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "H:\EHP6\kernel\SUM\abap\exe"

4 ETQ399 Set tool parameters for shadow connect:

4 ETQ399   default TPPARAM: SHADOW.TPP

2 ETQ366 Connect variables are set for shadow instance access

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_mss_schema=ns1

4 ETQ399   auth_shadow_upgrade=1

1 ETQ206 Executing pre-phase DB specific actions.

1 ETQ200 Executing actual phase 'MAIN_SHDIMP/JOB_UPDATE_DDYTT'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'RS_UPD_DDYTT'

2 ETQ399 Arg[1] = ''

2 ETQ399 Arg[2] = 'NO-IGNORE'

2 ETQ399 Arg[3] = ''

2 ETQ399 Arg[4] = '5'

2 ETQ399 Arg[5] = 'UPDATE DDYTT FOR SOME TABLES'

1 ETQ399 Using error summary log 'PUPDYTT.ELG'.

4 ETQ260 Starting batchjob "RS_UPD_DDYTT"

1 ETQ359 RFC Login to: System="NS1", AsHost="vappsrv52" Nr="01", GwHost="vappsrv52", GwService="sapgw01"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130417191750 

1 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC

2 ETQ373 parameter "BATCHHOST" = "vappsrv52"

2 ETQ373 parameter "JOBNAME" = "RS_UPD_DDYTT"

2 ETQ373 parameter "REPNAME" = "RS_UPD_DDYTT"

2 ETQ373 parameter "VARNAME" = ""

2 ETQ373 parameter "IV_SCHEDEVER" = " "

2 ETQ373 parameter "BATCHINSTANCE" = ""

1 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded

4 ETQ010 Date & Time: 20130417191804 

2 ETQ373 parameter "JOBCOUNT" = "19180000"

2 ETQ374 parameter "RC_START" = "0"

4 ETQ311 Batch job "RS_UPD_DDYTT" with job count "19180000" scheduled

2 ETQ399 'SUBST_CHECK_BATCHJOB' for JOBNAME='RS_UPD_DDYTT' JOBCOUNT='19180000' returns 'Y'.

1 ETQ359 RFC Login to: System="NS1", AsHost="vappsrv52" Nr="01", GwHost="vappsrv52", GwService="sapgw01"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130417191809 

1 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

2 ETQ373 parameter "JOBNAME" = "RS_UPD_DDYTT"

2 ETQ373 parameter "JOBCOUNT" = "19180000"

2 ETQ373 parameter "IV_VERIFY" = " "

1 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ010 Date & Time: 20130417191809 

2 ETQ373 parameter "JOBSTATUS" = "A"

2 ETQ374 parameter "RC_CHECK" = "0"

2 ETQ373 parameter "JOBENDDATE" = "20130417"

2 ETQ373 parameter "JOBENDTIME" = "191805"

1 ETQ359 RFC Login to: System="NS1", AsHost="vappsrv52" Nr="01", GwHost="vappsrv52", GwService="sapgw01"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130417191811 

1 ETQ233 Calling function module "SUBST_LIST_SYS_LOGS" by RFC

2 ETQ373 parameter "FILE_SYS" = "JOBLOG.LOG"

2 ETQ373 parameter "JOBCOUNT" = "19180000"

2 ETQ373 parameter "JOBNAME" = "RS_UPD_DDYTT"

2 ETQ374 parameter "TIMESPAN" = "10"

1EETQ235 Call of function module "SUBST_LIST_SYS_LOGS" by RFC failed (error-status "5")

2EETQ360 RFC of "SUBST_LIST_SYS_LOGS" failed:

2EETQ361 code/exception  : 5

2EETQ362 key             : DUMP_ERROR

2EETQ399  Number:000

4 ETQ010 Date & Time: 20130417191812 

2WETQ399 Ignore error message 'RFC error system NS1 nr 01 function 'SUBST_LIST_SYS_LOGS' failed with code 5 key DUMP_ERROR:  Number:000'.

2EETQ262 Batchjob "RS_UPD_DDYTT" aborted

1EETQ399 Last error code set is 'Batchjob 'RS_UPD_DDYTT' with id '19180000' aborted'

1EETQ204 Upgrade phase "JOB_UPDATE_DDYTT" aborted with severe errors ("20130417191812")

Accepted Solutions (0)

Answers (4)

Answers (4)

arsnlgunnr
Participant
0 Kudos

Never got an answer from SAP, so I ended up starting the upgrade over.

charles_koekemoer2
Participant
0 Kudos

Hi guys,

I got the same error and i logged into the shadow instance. On st22, there were spool errors and I cleared them via spad and the upgrade continued successfully.

Kind regards,

Charles Koekemoer

former_member189797
Active Contributor
0 Kudos

Hello Daniel,

1 ETQ359 RFC Login to: System="NS1", AsHost="vappsrv52" Nr="01", GwHost="vappsrv52"   <-----

So job is running on the instance 01 (shadow). Could you please check if you are able to login to the

shadow system ??

Login to the shadow system...check the JOB log in the transaction SM37......check the corresponding dev_w* log for more details about the issue.  Check the ST22 for the related dumps.

Please provide the above information.

Regards,

Gaurav

arsnlgunnr
Participant
0 Kudos

Gaurav,

The shadow instance is up and running but I am not able to get a login prompt on the GUI.  see the posts above for the error i get.

former_member189797
Active Contributor
0 Kudos

Hello Mr. Parker,

Very strange, that you are not able to login to the shadow system due to the system error. It seems that shadow instance is inconsistent. I would suggest to open a message to SAP. It would be very difficult to check it without connection as we might have to check what happened during the upgrade which caused this inconsistency in the shadow.

Regards,

Gaurav

Former Member
0 Kudos

Hi Jayson,

Please check if you are hitting some dumps , job logs in SM37, transaction SM50 and DB01 in order to detect deadlock in shadow system.

It am not quite sure but may be the error that you are hitting is due to bug in SUM tool. I suggest you to contact SAP support as well.

Regards,

Sachin

arsnlgunnr
Participant
0 Kudos

Sachin,

I'm not able to login to the shadow system.  When I initiate a GUI session, I get this error: "Syntax error in program SAPLOLEA". 

I've have looked at the trace file for the DW processes but cannot find a root cause for the error.

karthikeyan_natarajan4
Active Contributor
0 Kudos

Hi Jay, could you look at the note 0000934728 and see any thing you can get from it.

arsnlgunnr
Participant
0 Kudos

Karthikeyan,

That note is not intended for my release.  My current release is NW 702

Former Member
0 Kudos

Hi Jayson,

Can you please attached the complete syntax error ?

Regards,

Sachin

arsnlgunnr
Participant
0 Kudos

Sachin,

This is all I get when starting a GUI session for the shadow instance:

Also see this in the dev_w0 trace file:

A Thu Apr 18 10:43:29 2013

A  *GENER* request remote generation: SAPLOLEA.

A  *** ERROR => Syntax error in program SAPLOLEA                                 [abgen.c      1816]

A  {root-id=9A96FC5B7B6A1ED2AA86CA9FBF6FF79D}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => > Include LOLEAU13                                 line 261 [abgen.c      1818]

A  {root-id=9A96FC5B7B6A1ED2AA86CA9FBF6FF79D}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => > Different number of parameters in FORM and PERFORM (routine: CONVERT_TO_VARIANT, [abgen.c      1820]

A  {root-id=9A96FC5B7B6A1ED2AA86CA9FBF6FF79D}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => >  number of formal parameters: 4, number of actual parameters: 5) [abgen.c      1822]

A  {root-id=9A96FC5B7B6A1ED2AA86CA9FBF6FF79D}_{conn-id=00000000000000000000000000000000}_0

former_member188883
Active Contributor
0 Kudos

Hi Jayson,

As a primary check do the following

1) Check space in the tablespace

2) Check space on the Server drives

Additionally share information

1) What is the source database and SAP release

Regards,

Deepak Kori

arsnlgunnr
Participant
0 Kudos

Deepak,

The DB is SQL Server 2008 R2.  All the data files are set to unlimited growth and the drive is 250GB in size with 75GB available for growth.  Also the transaction log has been backed up and truncated.

The source SAP release is NW702 ECC6 EHP5