Upgrade documents

[Former Member]

Hi ,

Iam senior basis resource for my company.Actually I have very good experiance on Implementations and Support.I have implemneted 5 implementations and 4 support projects in my experiance.

Now I need to jump into Upgrade projects.Till now I have no experiance on upgrade projects.Is there any documents and steps for each and very area so that I can quick look into that.

Amy

[Former Member]

Hi

I would suggest you to look at Forum SAP Solutions-->SAP ERP 6.0 upgrade, where in you could find all the real time issues whcih users are facing and how they are getting it resolved.

Hope that forum will help you understand better

Let me know if needed more information

Regards

Uday

[Former Member]

Dear Uday,

I dont think u have read my message.Iam looking for some high level hints like, what are the issues we can face during upgrade, and methods to minimize downtime,time frame and project plans.

Not local installation documents.

- Amy

[Former Member]

Hi

SAP recommendation

SAP recommends to always import the latest version of the SPAM/SAINT update before importing installation packages. It is also a good idea to download the latest versions of executables tp and R3trans from a sapserv# application server (see Note 19466).

If we are using several application servers, we should make sure that profile parameter rdisp/bufrefmode is set to sendon,exeauto, and if we are using only one application server,we should make sure that the profile parameter is set to sendoff,exeauto. Otherwise, we only have the option of executing the "/$sync" command to make the changes become completely effective after the installation.

Problems, Symptoms Reasons and Solutions

1. Termination in the XPRA_EXECUTION step (TP_FAILURE)

Symptom: A termination occurs when we import an add-on or a preconfigured system (PCS). The following dialog box appears:

Error in step: XPRA_EXECUTION

Cause of error: TP_FAILURE

Return code: 0204

Error message: parameter is missing

Solution: If we encounter this error, proceed as described in Note 537881.

2. SPAM/SAINT - Version 0003 - Version 0008

Symptom: User exits are deactivated after we import an installation queue. Only user exists are affected, however, that are contained in inactive CMOD enhancement projects.

Reason: With SPAM/SAINT Version 0003, an automatic import reprocessing was implemented that automatically reactivates any user exits that may have been deactivated during the import (see Note 402972). In the first version of this post-processing, the case not supported by SAP that there may be active user exits in inactive CMOD enhancement projects has not been taken into account correctly. Therefore, when restoring the consistency of the customer enhancements, all user exits in inactive CMOD enhancement projects are deactivated.

Solution: If the given case has occurred in a system where active user exits in inactive CMOD enhancement projects, please check whether the implementation of the user exits can be changed to the SAP standard case (active user exits only in active CMOD enhancement projects or inactive user exits only in inactive CMOD enhancement projects).

In addition, the import post-processing in SPAM/SAINT Version 0009 was enhanced so that all combinations of the user exit status and the enhancement project status are now correctly dealt with.

3. SPAM/SAINT - Version 0013

Symptom: An error occurs in the phase ADD_SYNCMARKS when we import an installation queue. The action log contains the following tp message:

tp finished with return code: 200

Not exactly one SYNCMARK set; buffer unchanged!

We also find the same error message in SLOG.

Reason: The enhanced transport control is activated in the TMS (tp parameter CTC=1 is set in the transport profile). The tp command line used in SPAM/SAINT Version 0013 to set SYNCMARKs does not work in this case.

Solution: The problem is solved in SPAM/SAINT - Version 0014.

Use 'Back' to delete the installation queue in SAINT. Then import the SPAM/SAINT update - Version 0014 (or higher) in the Support Package Manager. Then restart the installation in SAINT.

4. SPAM/SAINT Version 0016: Incorrect Support Package proposals

Symptom: As of Version 0016, we can link additional Support Packages to an add-on installation queue. When we upgrade an add-on, the system determines (in the same way as for system upgrades) which Support Packages need to be included for the target add-on release based on the Support Packages that have been imported for the add-on source release to achieve the same maintenance state. In SPAM/SAINT Version 0016, a program error means that the system does not just determine this for the add-on contained in the upgrade, but for all components. As a result, we may find that Support Packages that should not be imported at all have been preselected on the Support Package selection screen. It is easy to undo this preselection using the relevant dropdown fields. However, if we overlook this preselection, the selected Support Packages are included in the installation queue and then imported once the import conditions have been met.

Solution: SPAM/SAINT Version 0017 corrects this problem.

When we use SPAM/SAINT Version 0016, we should always check carefully which Support Packages have been selected for the individual components on the Support Package selection screen, and if necessary, undo any incorrect preselections.

5. SPAM/SAINT Versions 0016, 0017: Unauthorized Support Packages in the queue

Symptom: As of Version 0016, we can add further Support Packages to an add-on upgrade queue. If the Support Packages we are adding require Support Packages of the pd release in wer system for the add-on we are upgrading, these Support Packages that belong to the pd system may be sorted after the add-on installation/upgrade package. This is incorrect and means that after importing this queue, the add-on is inconsistent.

Note that sorting before the installation/upgrade package is correct and is not an error.

Solution: The problem is solved with SPAM/SAINT Version 0018.

When we use SPAM/SAINT Version 0016 or 0017, before we begin the import, carefully check whether the Support Packages of the pd release for the add-on we are upgrading have been sorted after the add-on installation/upgrade. If this is the case, do not import this queue. In this instance, only import the actual installation/upgrade queue without the added Support Packages. The additional Support Packages should then be imported with the Support Package Manager in a second step.

6. Problems with R3trans patch level 1848 (SAP Kernel 6.20) and patch level 62 (SAP Kernel 6.40)

Symptom: If we use R3trans with patch level 1848 (SAP Kernel 6.20) or patch level 62 (SAP Kernel 6.40) (see R3trans -v) to import OCS packages, the import may terminate when we activate the DDIC or when we execute the after-import method. Error messages of the following type appear in the logs:

LANG DTEL * Object information could not be imported

LANG TABL * Object information could not be imported

or

Object "..." "..." has not yet been imported successfully

Solution: Do NOT use R3trans with patch level 1848 (SAP Kernel 6.20) or patch level 62 (SAP Kernel 6.40) to import a SAINT queue.

If we have already encountered these errors, it is no longer sufficient to simply change the R3trans. In this case, contact SAP Support (component BC-UPG-OCS).

7. Usage of a 6.40 kernel with a database of the family IBM DB2

Symptom: When we import Support Packages to use a 6. 40 kernel on an IBM DB2 database, in some circumstances problems can occur with the buffer synchronization.

Solution: Refer to Note 841938 and only use the kernel and transportation top versions recommended there.

Downtime-minimized import only with R3trans from December 06, 2005 (or later)

The downtime-minimized import mode in the Add-on Installation Top may only be used with an R3trans version from December 06, 2005 (or later). If we use an older R3trans version, ABAP Object methods may not be imported correctly. Note 906008 describe this phenomenon and the symptoms that occur.

As of Version 0020, the Add-On Installation Top checks whether the minimum R3trans version exists.

8. "SAPCAR error: format error in header" when extracting an SAR archive

Symptom: When we unpack an SAR archive, the SAPCAR utility terminates with the error message "SAPCAR error: format error in header".

Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, pder SAPCAR versions can no longer unpack the archive (also refer to SAP Note 892842).

Solution: Use SAPCAR Version 700 or SAPCAR Version 640 patch level 4. These versions can process the new archive format (refer to SAP Note 892842).

9. SAR archives cannot be loaded and unpacked using the function "Load from front end"

Symptom: We want to unpack an SAR archive using the function "Load from front end". The system refuses the archive with the message "File '???.SAR' is not a CAR or SAPCAR file'.

Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, and the archive format versions were also changed, the Support Package Manger does not recognize the file as a valid SAR archive.

Solution: SPAM/SAINT Version 620/0020 contains an adjustment to the new SAR archive format. Note that we may require a new SAPCAR version (refer to the problem described above, or to SAP Note 892842).

10. Avoiding DDIC activation errors during the import

To avoid DDIC activation errors when we import installation queues (especially long queues), we must implement the following notes BEFORE we implement the corrections.

791984 u201CSimultaneous activation of view appends and appending view"

1015068 "Deleting and recreating dictionary objects"

Alternatively, check whether we have already implemented this note as part of a Basis Support Package.

11. Termination of table conversion (tp step "N") on MSSQL systems

Symptom: When we import installation queues on MSSQL Server systems, the import step for the table conversion (tp step "N") terminates. The job log of the associated background job RDDGEN0L contains the runtime error SAPSQL_SUBQUERY_ILL_TABLE_TYPE.

Solution: To avoid the error, implement the corrections contained in Note 1042435 before we import the Support Package.

If we have already encountered the error, proceed as described in Note 1042435.

I hope this helps

Regards

Chen

[Former Member]

Hi

As a senior Basis consultant you should have good idea about service market place how SAP provides with complete details information about each and every installation steps and know issues.

To my knowledge you can check any of the upgrade documents and drill it out all your questions will be answered in that .

Regards

Uday

[Former Member]

Hi,

Thanks for the updates. Actually Iam looking for some high level documents

1. What are issues we normally face

2.What type of upgrade process ( like for ex: minimize down time, parallel process and etc)

3.Database issues

4. Project plan for each and every task

- Amy

[Former Member]

Hi

Also please check the following links:

http://www.thespot4sap.com/upgrade_guide_v2.pdf

and

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/003fcffd-bee6-2a10-3784-e51df6a2...

and

http://iponsel.com/ebook/sap-upgrade-guide-manual/2008/04/28/

I hope this helps

Regards

Chen

[Former Member]

Hi

You can find all the relevant documents in www.service.sap.com/instguides and www.service.sap.com/pam these are the best places to search for documents you needed

and also check

http://www.easymarketplace.de

Regards

Uday