SAP BW Upgrade – General issues
This upgrade was a 2 step process with EHP1 upgrade as a first step and SP3 upgrade as a second step.
SAP is on AIX and Database is on DB2/zOS (Distributed environment)
I. Step 1 -> Upgrade to BI 7.0 EHP1 (based on NW 7.0)
|
SAP Product |
SAP BW |
|
Source Release |
BW 700 |
|
Target Release |
BW 701 |
|
Source Database |
DB2 / zOS 9.1.5 |
|
Target Database |
DB2 / zOS 9.1.5 |
Issues during EHPI upgrade:
1) 1) Issue in BI_CONT add-on installation
Two Dumps – ST22
Dump 1:
Runtime Errors SYNTAX_ERROR
Short text
Syntax error in program “CL_RSDD_DTA_TGT===============CP “.
Solution: Apply Note 1237247 and 1085398 using SNOTE
Dump 2:
Runtime Errors SYNTAX_ERROR
Short text
Syntax error in program “CL_RSBK_DTP_V=================CP “.
Solution: Apply Note 1401966 using SNOTE
1) 2) Configuration phase:
Solution:
cdexe
mv libsapcrypto.o libsapcrypto.o.old
Download the Cryptographic software and copy below files
cp /../aix-6.1.0-64/libsapcrypto.o .
cp /..//aix-6.1.0-64/sapcrypto.lst .
cp /../aix-6.1.0-64/sapgenpse .
cdD
cd exe
mv libsapcrypto.o libsapcrypto.o.old
cp /../aix-6.1.0-64/libsapcrypto.o .
cp /../aix-6.1.0-64/sapcrypto.lst .
mv sapgenpse sapgenpse.old
cp /../aix-6.1.0-64/sapgenpse .
3) Checks phase:
Error details are:
Logifle: PSUPGCHK.ELG
Logfile : JOBLOG.LOG
Solution:
Execute /$SYNC from T-code bar and all buffers will be reset
Repeat the phase.
4)Preprocessing phase :
Logfile : PARCONV.SAV
Just repeat this phase and upgrade will go to next phase.
II. Step 2-> Upgrade to BI 7.3 SP3 (based on NW 7.0)
|
SAP Product |
SAP BW |
|
Source Release |
BW 701 |
|
Target Release |
BW 730 |
|
Source Database |
DB2 / zOS 9.1.5 |
|
Target Database |
DB2 / zOS 9.1.5 |
Issues during upgrade:
1) Extraction:
Logfile : DB2CNNCT.LOG
cp db2*.lic /usr/sap/<SID>/SYS/global/db2/AIX_64/db2_clidriver/license
Logfile: TP.LOG
There was an issue with rfcoscol process which was holding locks on sysibm.systables. The process was terminated and the rfc collectors were stopped on lpars.
Logfile : DB2RADM.LOG
cd /usr/sap/<SID>
<sid>1adm > mkdir –m 775 db2radm
If db2radm already exists no need to create new one.
<sidadm > SAPCAR -xvf db2radm_98-20005240.sar
cd /usr/sap<SID>/<SID>/upg/abap/exe
mv db2radm db2radm_720_65
cp /usr/sap<SID>/<SID>/db2radm/db2radm .
cd /usr/sap<SID>/<SID>/upg/abap/exenew
mv db2radm db2radm_720_86
cp /usr/sap<SID>/<SID>/db2radm/db2radm .
cdexe
mv db2radm db2radm_720_86
cp /usr/sap<SID>/<SID>/db2radm/db2radm .
cdD
cd exe
cp /usr/sap<SID>/<SID>/db2radm/db2radm .
1) 2) CHECKS.LOG
WARNING: The following DDIC objects you created reference SAP
DDIC objects which will be deleted during the upgrade.
As a result activation errors will occur during phase ACT_UPG if the references are not removed.To remove the references make a copy of the SAP objects in the customer name range and change your DDIC objects to reference the copy.
object DMCSOURCER of type DTEL referenced by:
ZBW_INVLD_LOG of type TABL
object DMCSOURCER of type DTEL referenced by:
ZOXDB10002 of type TABL
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_01_CAT of type SHLP
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_01_GEN of type SHLP
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_02_CAT of type SHLP
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_02_GEN of type SHLP
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_99_CAT of type SHLP
object COMM_PRODUCT of type TABL referenced by:
ZOM_PRWB_99_GEN of type SHLP
These are all custom development which be taken care post upgrade.
During Preprocessing Phase MAIN_SHDRUN/ACT_UPG you can accept non-severe errors and repeat Phase MAIN_SHDRUN/ACT_UPG
3) LONGPOST.LOG
CURRENTPHASE XPRAS_AIMMRG
1PEPU203X–> Messages extracted from log file “SAPR730XD1.<SID>” <–
Long text:
Cause
During the upgrade, a message relevant for postprocessing was written to
a log file. This message is not dealt with until the end of the entire
upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the
original log file, this message is generated by SAPup.
What to do
Note the messages following this message and proceed according to the
instructions.
A2PERSO 323 Exception ‘&3″An exception with the type CX_SY_OPEN_SQL_DB occur”‘ in progrmm ‘&4″CL_RSD_DTA====================CP,CL_RSD_DTA======
A2PERSTCO_UT 003 An error occurred while activating BW object &2″0RATE_TYPE” (&1″IOBJ”)&3″OM”
Long text:
The BW object &V#& is part of the technical Content that is required
for problem-free use of the BW system in an active version.
Cause
During activation of the object, an error occurred. For more detailed
information on activation errors, see the application log, which you can
view either with transaction RSTCO_ADMIN or SLG1.
System Response
What to do
Try to activate object &V#& of type &V#& manually.
To do this, start transaction RSOR in your BW client and
activate the object. If this activation also leads to errors
or if the object is not there, create an error message on component
BW-BCT-TCT.
The problem is not critical for the upgrade or the installation of the
BW system. For productive use, the activation problem does have to be
activated.
Tasks for system administration
A2PERSBM 035 The creation of the export DataSource failed
Long text:
Cause
It was not possible to create the DataSource &V#&.
System Response
The metadata for a DataSource must be created when you generate the
export InfoSource. An error occurred.
What to do
Contact the developer (function module: RSA1_OLTPSOURCE_GENERATE).
Tasks for system administration
A2PERSAR 051 “Upgrade still running: Logon not possibl” “e” ” ” ” “
A2PERSAR 051 “Upgrade still running: Logon not possibl” “e” ” ” ” “
A2PERSDODSO 169 Error when creating the export DataSource and dependent Objects
A2PERSO 404 Error when activating “DataStore Object” “0RSPL_LCK”
A2PERSBM 035 The creation of the export DataSource failed
Long text: see above
A2PERSAR 051 “Upgrade still running: Logon not possibl” “e” ” ” ” “
A2PERSAR 051 “Upgrade still running: Logon not possibl” “e” ” ” ” “
A2PERSDODSO 169 Error when creating the export DataSource and dependent Objects
A2PERSO 410 Error when resetting “DataStore Object” “0RSPL_LCK” to the active version
Long text:
Cause
Errors arose when activating &V#& &V#&. An active version already
existed before the activation.
System Response
&V#& &V#& could not be reset to the old active version. Since the
generated objects no longer correspond to the old active version, they
were reset to inactive.
What to do
The old active version of &V#& &V#& can no longer be used. Remove the
cause of the activation error and activate &V#& &V#& anew.
Tasks for system administration
A2PERSTCO_UT 003 An error occurred while activating BW object &2″0BWTCT_PLAN” (&1″AREA”)&3″OM”
Long text: see above
2PEOO003 “Class” “CL_RSPLFC_SET_VALUES” does not exist
A2PERSTCO_UT 003 An error occurred while activating BW object &2″0RSPL_SET_VALUES” (&1″PLST”)&3″OM”
Long text: see above
4) Kernel upgrade :
Error during extraction :
Login as root
Go to /sapmnt/<SID>/exe and do slibclean
Do again disp+work -version and it will display the version.
1) 5) Extraction Phase
PRE_IMPORT in EXTRACTION running long due to RDDIMPDP job not running
Schedule RDDIMPDP job through program RDDNEWPP
6) Checks phase:
Can’t change the persmission of /usr/sap/<SID>/SYS/exe/run/icmbnd & icmbnd.bk : Not owner
Changed owner to sidadm
7) Downtime phase (MAIN_SWITCH/KX_SWITCH_1)
3EETQ399 Copy ‘dsrlib.o’ failed: Cannot write to ‘/usr/sap/SG1/SYS/exe/run/dsrlib.o’: Text file busy
rename dsrlib.o to old_dsrlib.o in source kernel /sapmt/<SID>/exe then repeat the phase, it will recopy whole upgrade kernel to central instance kernel
Good one!