Dear Raghunahth ,
Did you follow the steps in note 817463
1. !!! Caution:
Note the following during ERP 2005 upgrades with the following conditions:
Source system: 46C
Operating system: Linux X86_64 (AMD64)
Under certain circumstances, TADIR entries are incorrectly copied during the SAP upgrade and the SAP upgrade does not notice this.
This has the following consequences:
1. After the upgrade, customer objects can no longer be edited.
2. Problems occur during the XPRAS_UPG phase because objects without a TADIR entry were edited.
3. Problems occur during the ACT_UPG phase because objects had no TADIR entry.
This faulty copy operation appears to be caused by a database error in MaxDB Version 7.6.
Unfortunately, we have not managed to reproduce the error internally at SAP using the relevant DB trace, in the same way as it has been reproduced externally.
If you carry out an ERP 2005 upgrade subject to the conditions mentioned above, you must implement the workaround described below:
1. After the PREPARE and before you start the actual upgrade, create a file called R3UPPHAS.BRK in the /usr/sap/put/bin directory with the following content line:
RUN_RDDCP4TB
2. Then start the actual upgrade, which is then halted before the RUN_RDDCP4TB phase. This is still in the uptime.
3. You can now execute the RDDCP4TB report, which must be executed in the phase, online in transaction SE38.
When calling RDDCP4TB, you must specify two parameters:
Enter the TADIR~ value for NEWTADI.
Enter the TADIR value for OLDTADI.
The system then issues 5 lines of numbers in the log. The sum of these numbers (sum of the lines Saved, Updated, Deleted, Invalid and Original) must match the number of entries in the original TADIR. If this is the case, the copy procedure was successful. To display the number of entries in the original TADIR, choose
transaction SE16 -> TADIR number of entries.
4. If the RDDCP4TB report, which is executed manually, returns the correct result, you can continue with the upgrade.
If the report returns results that do not match the number of entries in the original TADIR, proceed as follows:
a) If this is a time-critical upgrade, execute the report manually again once or several times, if necessary.
After the report has run and returned the correct result, you can continue with the upgrade.
If you are unable to obtain the correct result when you run the report, contact SAP Support.
b) If this is a test upgrade or a non-time-critical upgrade, notify SAP Support and provide them with access to your system (component BC-DB-DB as specified in Note 826037). They will then investigate the report directly using the relevant database tracing (SQL trace ST05 and precompiler trace) in an effort to identify the actual cause of the error.
Kind regards.
Alexander.
Please reward points if helpfull.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.