Add. info. on upgrading to SAP CRM 7.0 SR1 ABAP

[] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. Add. info. on upgrading to SAP CRM 7.0 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  2. Add. info. on upgrading to SAP SCM 7.0 SR1 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  3. Add. info. on upgrading to EHP 4 for SAP ERP 6.0 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  4. Add. info. on upgrading to SAP ERP 6.0 EHP4 SR1 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  5. Add. info. on upgrading to SAP SCM 7.0 SR1 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  6. Add. info. on upgrading to SAP SCM 7.0 ABAPSymptom Errors in the upgrade procedure or in the upgrade...
  7. Add. info.: Upgrade to SAP NetWeaver 7.0 EHP 1 (ABAP)Symptom Errors in the upgrade procedure or in the upgrade...
  8. Add. info.: Upgrade to SAP NW 7.0 Support Rel. 2 ABAPSymptom Errors in the upgrade procedure or in the upgrade...

Symptom

Errors in the upgrade procedure or in the upgrade guide; preparations for the upgrade; additional information to the upgrade guide
Other terms

Upgrade, migration, release upgrade, release, SAPup, SAP CRM 7.0 SR1
Reason and Prerequisites

*
Solution

CAUTION:
This note is updated regularly!
Therefore, you should read it again immediately before starting the upgrade.

What can I expect from this note?

This note describes problems that may occur when you upgrade the system and provides you with information on how to solve them.This usually takes the form of references to other notes.
The aim of this note is to prevent data loss, upgrade shutdowns and long runtimes.
Only database-independent problems are dealt with here.

What should I not expect from this note?

Problems that occur after the upgrade are only dealt with if they are caused directly by the upgrade tools.

Which notes do I also need in preparation for the upgrade?

You need to refer to the relevant database-specific note below:
Database ………………………………………….. Note number
_______________________________________________________________________
SAP MaxDB ……………………………………………….817463
IBM DB2 for i (NetWeaver-specific)…………………………1168235
IBM DB2 for i (Business Suite-specific)…………………….1179413
IBM DB2 for Linux, UNIX and Windows ………………………..819876
IBM DB2 for z/OS………………………………………….815202
MS SQLServer…………………………………………….825146
Oracle…………………………………………………..819655
You also need to refer to the following important SAP Notes:
Short text ………………………………………… Note number
_______________________________________________________________________
Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1 SR1..1293744
OCS: Known problems with Support Packages in SAP NW 7.0 AS ABAP..822379

———————————————————————-

Contents

I/ …… SAPup keyword
II/ ….. Important general information
III/ …. Corrections to the guides
IV/ ….. Errors on the CD-ROM
V/ ….. .Preparations for the upgrade
VI/ …. .Problems in the PREPARE and upgrade phases
VII/ … .Problems after the upgrade
VIII/ ….Chronological summary

I/ SAPup keyword

———————————————————————-
The SAPup keyword is: 31656394
This must be entered in phase KEY_CHK.
———————————————————————-

II/ Important general information

———————< D025323 NOV/21/08 >—————————-
Corrections and repairs for the upgrade
Before the upgrade, it is vital that you check whether the following are available for your specific upgrade:
A new version of SAPup.Repairs to the ABAP upgrade programs.
For more information, seeNote 1293744
It is ESSENTIAL that you apply this Note.

———————–< D028310 JUL/19/02 >————————–
Problems with the shadow instance
The following Notes contain information about problems with the shadow instance:
525677: Problems with starting the shadow instance430318: Shadow instance on other operating system

——————–< changed D043320 DEC/05/08 >———————-
———————–< D020904 MAR/15/07 >—————————
MSCS Configuration: Upgrade of the ABAP System
In an MSCS configuration, you must split the ABAP central instance into the ABAP central instance (ASCS) and central instance, as described in SAP Note1011190if you have upgraded your SAP NetWeaver ‘04 -based ABAP system to SAP NetWeaver 7.0-based ABAP system.
The split is required for the use of the enqueue replication server. If you run an MSCS configuration without enqueue replication server, which is the traditional MSCS configuration (where the clustered central instance runs the message server and enqueue work process), you will lose the enqueue lock table during a failover. The enqueue replication server configuration prevents this loss.
If you want to migrate an ABAP+Java system that is already upgraded to SAP NetWeaver 7.0 (and higher) to the new configuration with enqueue replication server, you must perform a homogeneous system copy.
———————————————————————

III/ Corrections to the guides

———————–< D022030 JUL/15/09 >—————————
SAP NetWeaver Library Paths
Some paths to SAP NetWeaver Library used in the guide, wrongly refer to SAP Library documentation for Release 7.1x.
Use the table that is attached to this Note (Library_Paths_external.pdf) – it lists all affected sections and the correct paths in column “Path for SAP NetWeaver 7.0x Library”.

———————————————————————

IV/ Errors on the CD-ROM

———————————————————————-

V/ Preparations for the upgrade

————————< D038245 09/DEC/08 >————————
Downloading Kernel DVDs for the Upgrade
The software of the kernel is split into two files with the following naming convention:

Upgrade
When you download the kernel DVDs for the upgrade, you must download both files from SAP Service Marketplace.
———————–< D023536 30/OCT/08 >————————–
Add-On Component CPRXRPM 400 with a Support Package Level < 7
In case you have installed the add-on component CPRXRPM 400 with a Support Package level lower than 7 and you have applied SAP Note975043, you need to apply this Note again after the upgrade.

----------------------——————–
————————< D001330 03/JUL/07 >————————-
Parameter for the Central Syslog rslg/collect*
There may be conflicts with parameter values for the central syslog “rslg/collect*” of the default profile.
If the parameters are set with 39 and 40, you must change them to 14 and 15. Make sure that the ports are not used by other applications. If so, choose some other number.
For more information, see Note1069225.
———————–< D038006 02/NOV/05 >————————–
Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
If you are using the above combination on your source release and have set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note 797084, proceed as follows:
Before you start the upgrade, you need to delete the environment variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by setting the following instance profile entry:
rdisp/start_icman=false
Restart the system.
After the upgrade, delete the instance profile entry again.
————————–< I080284 12/OCT/05 >————————
Software Agent Framework only:
If you use Software Agent Framework (SAF) in the source release system, clean old SAF queue jobs and indexes before you start the upgrade of the CRM server. For more information, see SAP Note887277.
————————< D003327 15/SEP/05 >————————–
Back up customer-specific entries in table EDIFCT
If you have maintained customer-specific entries in table EDIFCT, they may get lost during the upgrade. If you do not want to lose these entries, export them before the upgrade and reimport them after the upgrade.
For more information, see Note865142.
————————–< D034302 16/AUG/05 >———————–
Windows only: Last profile text line must end with line feed
Check that the last text line in all profiles ends with a line feed.To check this, open a profile file with a text editor, go down with the cursor and ensure that the last line is empty. Otherwise there could be problems in the KX_SWITCH phase as some tools will not be able to handle the profiles properly.
——————-——————————–
SAP CRM only: Database <-> ABAP/4 Dictionary consistency check
Before the upgrade, carry out a consistency check between the database and the ABAP/4 Dictionary. If the M_MCHA table in the database does not exist in the DDIC, you can delete this table. Doing this prevents an error in the PARDIST_SHD phase.

———————————————————————-

VI/ Problems in the Preparation and Upgrade Phases

In this section, you will find known problems that cannot be prevented using preventive measures.These problems can only occur under certain conditions or prerequisites.

Problems in the Preparation Phases

————————–< D038245 28/FEB/08 >———————–
Windows only: MSSERV_INTERN port numbers
During PREPARE, the upgrade tool requests a port number for the MSSERV_INTERN port. If your system is running on Windows, you cannot use port numbers within the following range: 6665 – 6669.

———————————————————————–

Problems in the Upgrade Phases

————————–< D034302 16/AUG/05 >———————–
Phase: KX_SWITCH (Windows only)
Description: Upgrade stops with an error message which asks you to checkfile NTPARVAL.LOG. In this file, messages like the following are displayed:
fopen(…): Invalid argument
Check that the last text line in all profiles ends with a line feedback.To check the profile, open a profile file with a text editor, go down with the cursor, and ensure that the last line is empty. If it is not, add an empty line at the end of the file and save it.

———————-< D038245 FEB/28/06 >————————–
Phase: MODPROFP_UPG
Description: When you are performing a double-stack upgrade (ABAP and Java system at the same time), in phase MODPROFP_UPG the ABAP system is started together with the Java system part for the first time. The phase may fail if the SAP J2EE Engine does not start fast enough.
Check manually if the SAP J2EE Engine is running and if so, choose “repeat” to repeat the upgrade phase.

————————–< D021063 OCT/12/06 >———————-
Phase: XPRAS_UPG
Description: The phase issues the following short dump:
“GEN_BAD_MACRO_SOURCE” for program /1BCDWB/
You can ignore this message.
————————–< I006704 DEC/12/05 >———————-
Phase: XPRAS_UPG
Description: If your codepage does not equal 1100, you may get a codepage conversion error. In this case, replace the current kernel with the latest version and repeat the phase.
—————–< D038245 changed 25/FEB/04 >————————
Phase: XPRAS_UPG
Description: If a database error occurs in this phase (an overflowing tablespace, for example), SAPup automatically repeats the phase. In somecases, SAPup may continue to run but posting is deactivated in the system. The following entry appears in the system log:
The update task was deactivated.
In this case, solve the database problem (extend the tablespace, for example), call transaction SM14 and activate the update again.
———————–< D003551 NOV/25/05 >—————————
Phase: JOB_RDDNTPUR
Description: In the longpost-log file, you may get the error message:
3PETG447 Table and runtime object “BBP_UPGR_CLASSES” exist without DDIC reference (”Transp. table”)
and
3PETG447 Table and runtime object “BBP_UPGR_CRMTABS” exist without DDIC reference (”Transp. table”)
You can ignore this message.
———————————————————————-
Phase: CHK_POSTUP
Note: 996953
Description: Log file LONGPOST.LOG asks you to migrate a CMOD project although no project exists.
———————————————————————–
Phase CHK_POSTUP
Note: 197886
Description:If you have imported notes 178631, 116095 or 69455 into your system before the upgrade, error messages for objects without a DDIC reference will appear in the LONGPOST.LOG log. Proceed as described in Note197886.
———————————————————————-

VII/ Problems after the upgrade

In this category, you find known problems that are caused by the upgrade tools and that you can prevent using preventive measures. These problems only occur in certain conditions or prerequisites.
———————–< D000587 25/FEB/08 >—————————
Error when Converting Print Parameters
After the upgrade, in some clients the printing parameters have either gone or been replaced by other parameters. For more information, see Note1142364.
The problem is solved with SAP Basis Support Package 16.
———————-———————-
————————< D003551 02/MAY/05 >————————–
Check Primary Index of Table MEMGMT_DEPLOYMNT
After the upgrade, check that the primary index of table MEMGMT_DEPLOYMNT exists. If not, create the index manually. If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown object in the dictionary, drop it on the database level.
———————-—————————–
Obsolete entries in table SMO9_KYTBL
After the upgrade, delete obsolete entries from the SMO9_KYTBL table. For more information, see Note637829.
————————< D020815 AUG/23/02 >——————-
SPAU: Names of interface methods are truncated
In transaction SPAU, some methods that were modified and overwritten by the upgrade (ABAP objects) may be displayed in abbreviated form (truncated to 30 characters). As a result, methods in transaction SPAU may also be sorted incorrectly under “Deleted objects”.
Caution: Deleted objects are not displayed for the standard selection in transaction SPAU. It is very easy to overlook these.
For more information on the correction, seenote 547773.

———————————————————————-

IX/ Chronological summary

Date……Topic..Short description
———————————————————————–
JUL/15/09..III…SAP NetWeaver Library Paths
DEC/09/08….V…Downloading Kernel DVDs for the Upgrade
NOV/21/08…II…Corrections and repairs for the upgrade
OCT/30/08….V…Add-On CPRXRPM 400 with a Support Package Level < 7
FEB/28/08...VI...Windows only: MSSERV_INTERN port numbers
FEB/25/08..VII...Error when Converting Print Parameters
JUL/03/07....V...Parameter for the Central Syslog rslg/collect*
MAR/15/07...II...MSCS Configuration: Upgrade of the ABAP System
FEB/28/07...VI...Phase CHK_POSTUP - CMOD/SMOD migration
JAN/23/07...II...SAP NW BI: Do not include BW SP 11
OCT/12/06...VI...Phase XPRAS_UPG: short dump GEN_BAD_MACRO_SOURCE
FEB/28/06...VI...Phase MODPROFP_UPG fails - check J2EE Engine
NOV/25/05...VI...Longpost.log: Table Without DDIC Reference
NOV/02/05....V...Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/12/05....V...SAF: Clean old SAF queue jobs and indexes
SEP/15/05....V...Back up customer-specific entries in table EDIFCT
AUG/16/05...VI...Windows only: KX_SWITCH - Check file NTPARVAL.LOG.
AUG/16/05....V...Windows only: Last profile text line - line feedback
MAY/02/05..VII...Primary Index of Table MEMGMT_DEPLOYMNT
FEB/02/05...II...LSMW now part of SAP_BASIS
JUL/22/03..VII...Obsolete entries in table SMO9_KYTBL
AUG/23/02..VII...SPAU: Names of interface methods are truncated
AUG/01/02....V...Database <-> ABAP/4 Dictionary consistency check
JUL/19/02…II…Problems with the shadow instance
MAY/23/02…VI…CHK_POSTUP phase – objects without DDIC reference
———————————————————————-

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment