RFC_ERROR_SYSTEM_FAILURE no CM_DATA_RECIVED Upgrade ECC6

[Former Member]

hi

Iam getting this error during the ugrade from 4.7 ,linux,maxdb.this error came up soon after the Modification phase:we created some indexes that were missing in the database as part of the modifications.No its just hangs in the phase PARDSHD

error log:

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

2EETQ360 RFC of "subst_check_batchjob" failed:

2EETQ361 code/exception : SYSTEM_FAILURE

2EETQ362 key : RFC_ERROR_SYSTEM_FAILURE

2EETQ364 message :

2EETQ399 connection closed without message (CM_NO_DATA_RECEIVED)

4 ETQ359 RFC Login to: System="MX1", Nr="01", GwHost="mnx1", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

2EETQ235 Call of function module "SUBST_CHECK_BATCHJOB" by RFC failed (error-sta

tus "-2")

4 ETQ010 Date & Time: 20070808204524

Did anyone faced a problem like this before ?any ideas will be helpful

[markus_doehr2]

Check if your shadow instance is up and running. If not, check the logfiles in /usr/sap/put/<SID>/work directory

--

Markus

[Former Member]

the shadow instance is up and running but when i try to log in it just hangs and the same as the main system iam upgrading.should i stop both instances( shadow and 4.7)and restart prepare?

[markus_doehr2]

First check, if you have a LOG FULL situation ("archiver stuck").

execute as <sid>adm

x_cons <SID> show ac 1

do you see any activity?

(or simply use dbmgui to check your log area)

--

Markus

[Former Member]

hi

Thanks my log is full but i had set this to autolog on.i am wondering what happened .i was also keeping a check on my file system space amnd all is ok.

[markus_doehr2]

Maybe you filesystem space has been full - autolog gets deactivated in that case.

Enable it again - and the upgrade will continue.

--

Markus