Problem in CRM upgrade - phase MAIN_NEWBAS/JOB_RSINDCHK

Question

Hello,
Iu00B4m in the middle of a CRM migration from 4.0 to 7.0. In phase MAIN_NEWBAS/JOB_RSINDCHK I get the error RFC_ERROR 2: DUMP_ERROR.
I know I can solve the problem applying note 1483283 but have a problem in the process.
First I unlock de system with commands...
tp unlocksys SAPSID pf=(DIR_UPG)/bin/DEFAULT.TPP
tp unlock_EU SAPSID pf=(DIR_UPG)/bin/DEFAULT.TPP
...then I can login in the system but when try to access transaction SE24 or any other I get a dump
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_ENH_INTERNAL_ERROR
Date and Time          29.12.2010 09:39:19
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_ENH_INTERNAL_ERROR' was raised, but it was not caught
      anywhere along
     the call hierarchy.
     Since exceptions represent error situations and this error was not
     adequately responded to, the running ABAP program
      'CL_R3STANDARD_PERSISTENCE=====CP' has to be
     terminated.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_ENH_INTERNAL_ERROR', was not
      caught in
     procedure "SFW_GET_SWITCHPOS" "(FUNCTION)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     No text available for this exception
Missing RAISING Clause in Interface
    Program                                 SAPLSFW_COMMON
    Include                                 LSFW_COMMONU01
    Row                                     1
    Module type                             (FUNCTION)
    Module Name                             SFW_GET_SWITCHPOS
Trigger Location of Exception
    Program                                 CL_R3STANDARD_PERSISTENCE=====CP
    Include                                 CL_R3STANDARD_PERSISTENCE=====CM00Z
    Row                                     46
    Module type                             (METHOD)
    Module Name                             LOAD_SPOT
Any idea about that?
When I execute tp commands I get this message
G:\usr\sap\CRQ\upg\abap\exe>tp unlocksys CRQ pf=G:\usr\sap\CRQ\upg\abap\bin\DEFAULT.TPP
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 372.04.40 (release 701)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
tp finished with return code: 0
meaning:
  Everything OK
Do you think it could be the problem? Why I get the message of unknown SID & profile? Syntax problem? Iu00B4m working on Windows Server 2003.
Thanks in advance.

Answer 1

Hi,
I've got strictly the same error in my upgrade step JOB_RSINDCHK  ( from ECC5.0 to     ECC6.0  Ehp4 / 701 NW)
same step and  same symptoms .
(job failed, dump on ST22, CX_ENH_INITERNAL_ERROR ,   object SFW_GET_SWITCHPOS)
We solved the issue by implemented manually the oss note 1483283
It mean :
Unlock your system : tp unlocksys <SID> pf=/usr/sap/<SID>/upg/abap/bin/DEFAULT.TPP
Then logon on your system  with your user
se06 :  change the setting if necessary to allow modifications
se80 :  chose class :  CL_ENH_BADI_PREGENERATION
               then chose method =  BADI_PREGENERATION
change "display" to "Change"
and apply manually the corrections intructions deliver in oss note 1483283 (= correction 943161)
by clic on it you can then acces to the code.
after that check + activate the badi
try to liberate your OT (for us only the task has been liberated, no way to liberate the OT...).
Logoff
Then re-lock your system :  tp locksys <SID> pf=/usr/sap/<SID>/upg/abap/bin/DEFAULT.TPP
Repeat the failure step : job_rsindchk  .   For us it has been worked.
Best regards
Stéphane