Question:
Hello
We are upgrading ECC 5.0 to ECC 6.0 on Windows 2003 Server/Database
10.2.0.2. There is an upgrade error on
upgrade monitor phase "JOB_RSVBCHCK_D" (Phase 321 of 486)
Attached log.
PSVBCHCK.LOG:
-----------------------
1 ETQ201XEntering upgrade-phase "JOB_RSVBCHCK_D" ("20070102113211")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPDEV
4 ETQ399 auth_shadow_upgrade=0
4 ETQ260 Starting batchjob "RSVBCHCK"
4 ETQ010 Date & Time: 20070102113211
4 ETQ260 Starting batchjob "RSVBCHCK"
4 ETQ230 Starting RFC Login to: System = "SBX", GwHost = "sysaptest", GwService = "sapgw00"
4 ETQ359 RFC Login to: System="SBX", Nr="00", GwHost="sysaptest", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC
4 ETQ010 Date & Time: 20070102113216
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
2EETQ241 Errors found in logfiles - accumulated in file "PSVBCHCK.ELG"
1EETQ203 Upgrade phase "JOB_RSVBCHCK_D" aborted with errors ("20070102113216")
PSVBCHCK.ELG:
--------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CHECK OF UPDATE TASK Errors and RETURN CODE in RSVBCHCK.SBX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0HDRSETUP""100"
Long text:
Cause
Changing the extract structure &V#& for application &V#& is not
permitted, because the restructure table &V#& for the extractor still
contains data in &V#&.
You cannot change the structure in this status, because when you load
an InfoPackage from BW, this leads to errors.
What to do
<DS:TRAN.LBWG>Delete</> the entries for all restructure tables for
application &V#&.
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0ITMSETUP""100"
Long text: see above
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SCLSETUP""100"
Long text: see above
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SCNSETUP""100"
Long text: see above
A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table -> Long text" ""MC02M_0SGRSETUP""100"
Long text: see above
As per the log, I found out that from txn SMQ1(outbound queue RFC
calls) a RFC calls is listed. When I login to client 000 with user
DDIC, it says it cannot be deleted, please login with client 100.
When i login to client 100 with user ddic, user is locked.Nologon
possible while upgrade.
Please advise ASAP.
Thanks & Regards
MBHLOL
Answer:
Try to unlock system with "tp unlock_sys"
Answer:
search OSS notes, this s a well-known problem. IT wil lexplain you how to unlock the system and what steps are needed.
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Hello
when i executing the command, i get
D:\usr\sap\trans\bin>tp unlock SBX
This is tp version 340.16.24 (release 640, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
D:\usr\sap\trans\bin>
Answer:
D:\usr\sap\put>tp 'unlocksys SBX pf=/usr/sap/trans/bin/TP_DOMAIN_SBX.PFL'
This is tp version 340.16.24 (release 640, unicode enabled)
E-/usr/sap/trans/bin/TP_DOMAIN_SBX.PFL' could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in /usr/sap/trans/bin/TP_DOMAIN_SBX.PFL': transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
Please advise for correct the upgrade error.
Answer:
Hi,
Is this profile present, TP_DOMAIN_SBX.PFL i meant ?
Check if that profile is present.
Also is your Transport Domain configured on the SBX system, means is SBX your Domain controlller ? , if not then the profile name is incorrect.
Regards,
cryptosid
_________________
Its always ok in the end if its not ok its not the end
Answer:
yes the profile present .
here is the TP_DOMAIN_SBX.PFL:
#TMS:0001:DOMAIN_SBX
#U
#
#---------------------------------------------------------------------------
#Caution !
#This file was generated by the Transport Management System.
#Do not change this file using a text editor.
#For further information please see the online documentation of
#transaction STMS.
#If this file was destroyed, it can be regenerated in the TMS.
#To do this, log on to the domain controller (system SBX) and call
#Transaction STMS. In the System Overview, you can distribute the TMS
#configuration. This regenerates the file.
#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
#---------------------------------------------------------------------------
#
#
TRANSDIR = D:\usr\sap\trans
#
SBX/DBHOST = sysaptest
SBX/DBNAME = SBX
SBX/DBTYPE = ora
SBX/NBUFFORM = 1
SBX/TP_VERSION = 266
Also here is the tpparam_instSBX:
TRANSDIR =\\sysaptest\sapmnt\trans
SBX/DBHOST =sysaptest
SBX/DBNAME =SBX
SBX/DBTYPE =ora
SBX/SYSTEM_PF =\\sysaptest\sapmnt\SBX\SYS\profile\DEFAULT.PFL
SBX/MSPORT =3600
When I login to the client 000 , i am get TMS Alert Viewer: Error Message.
System SBX Command TMS_PM_DISTRIBUTE_PROFILE
Client 000 Service Communication Interface
User DDIC Start Online
Date 02.01.2007 Function TMS_PS_WRITE_PROFILE_TO_DISK
Time 14:02:39 Message RFC_SYSTEM_FAILURE
RFC system error in system/destination
TMSADM@SBX.DOMAIN_SBX
Please advise....
Thnaks & regards
MBHLOL
Answer:
please check OSS notes or the upgrade guide, You must run R3UP with options to unlock the upgraded system.
check that.
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Hello
I could not find out the options run R3UP with options to unlock the upgraded system on upgrade guide or OSS Notes.
Can you specify the option for the Phase JOB_RSVBCHCK_D?
Thanks & Regads
MBHLOL
Answer:
Hi,
Check the directory permissions, login as <sid>adm and see if you can access and open files in /usr/sap/trans/bin
Regards,
cryptosid
_________________
Its always ok in the end if its not ok its not the end
Answer:
Yes, the permission is fine for D:/usr/sap/trans/bin
Here is the TRANS BIN directory files:
DOMAIN.CFG
----------------------
sysaptest
00
TMSADM
DOMAIN_SBX
Transport domain SBX
SBX
System SBX
SBX
System SBX
GROUP_SBX
Transport group SBX
#---------------------------------------------------------------------------
#Caution !
#This file was generated by the Transport Management System.
#Do not change this file using a text editor.
#If this file was destroyed, it can be regenerated in the TMS.
#To do this, log on to the domain controller (system SBX) and call
#Transaction STMS. In the System Overview, you can distribute the TMS
#configuration. This regenerates the file.
#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
#---------------------------------------------------------------------------
TP_DOMAIN_SBX.PFL
------------------------------
TMS:0001:DOMAIN_SBX
#U
#
#---------------------------------------------------------------------------
#Caution !
#This file was generated by the Transport Management System.
#Do not change this file using a text editor.
#For further information please see the online documentation of
#transaction STMS.
#If this file was destroyed, it can be regenerated in the TMS.
#To do this, log on to the domain controller (system SBX) and call
#Transaction STMS. In the System Overview, you can distribute the TMS
#configuration. This regenerates the file.
#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
#---------------------------------------------------------------------------
#
#
TRANSDIR = D:\usr\sap\trans
#
SBX/DBHOST = sysaptest
SBX/DBNAME = SBX
SBX/DBTYPE = ora
SBX/NBUFFORM = 1
SBX/TP_VERSION = 266
tpparam_instSBX
-------------------------
TRANSDIR =\\sysaptest\sapmnt\trans
SBX/DBHOST =sysaptest
SBX/DBNAME =SBX
SBX/DBTYPE =ora
SBX/SYSTEM_PF =\\sysaptest\sapmnt\SBX\SYS\profile\DEFAULT.PFL
SBX/MSPORT =3600
DEFAULT.PFL
------------------
SAPSYSTEMNAME = SBX
SAPDBHOST = sysaptest
rdisp/mshost = sysaptest
rdisp/accept_remote_trace_level = 0
rdisp/sna_gateway = sysaptest
rdisp/sna_gw_service = sapgw00
rslg/collect_daemon/listen_port = 37
rslg/collect_daemon/talk_port = 13
rdisp/bufrefmode = sendoff,exeauto
ms/server_port_0 = PROT=HTTP, PORT=8100
dbs/ora/tnsname = SBX
login/system_client = 100
# *** UPGRADE EXTENSIONS (RELEASE "700") ***
rdisp/btcname =sysaptest_SBX_00
dbms/type =ora
Please advise....
Thanks&Regards
MBHLOL
Answer:
Hi,
I could see from your inputs that you executed,
D:\usr\sap\put>tp 'unlocksys SBX pf=/usr/sap/trans/bin/TP_DOMAIN_SBX.PFL'
which seems wrong naming convention.
If you are in D:\usr\sap\trans\bin then try using,
tp unlocksys SBX PF=TP_DOMAIN_SBX.PFL
Regards
Yatin
Answer:
Thanks buddy!!
It's working...
D:\usr\sap\trans\bin>tp unlocksys SBX PF=TP_DOMAIN_SBX.PFL
This is tp version 340.16.24 (release 640, unicode enabled)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
tp finished with return code: 0
meaning:
Everything OK
D:\usr\sap\trans\bin>
I able to solve the problem for upgrade.
Thanks & Regards
MBHLOL
Answer:
Enjoy SAP !!!