on 04-21-2009 9:17 PM
Hi,
I am trying to import following support packs on Solution Manager 7.0.
SAPK-40007IN.. CPRXRPM 400 CPRXRPM 400: patch 0007 to patch 15.
The import was stopped with the following error:
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: IMPORT_PROPER
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package ALL, tp step "N", return code 0008
Also, when I looked at the overview of transport log, this is what I found.
Request: Create Index /RPM/CAP_B_GROUP-001 (DDIC/20.04.09/22:29)
Line 1: Incorrect syntax near '('.
The SQL statement was not executed
Index could not be created completely in the database
Index /RPM/CAP_B_GROUP-001 could not be created
Request for /RPM/CAP_B_GROUP could not be executed
Request: Create Index /RPM/DECISION-01 (DDIC/20.04.09/22:29)
Line 1: Incorrect syntax near '('.
The SQL statement was not executed
Index could not be created completely in the database
Index /RPM/DECISION-01 could not be created
Request for /RPM/DECISION could not be executed
Request: Create Index /RPM/FIN_B_CAT-001 (DDIC/20.04.09/22:29)
Line 1: Incorrect syntax near '('.
The SQL statement was not executed
Index could not be created completely in the database
Index /RPM/FIN_B_CAT-001 could not be created
Request for /RPM/FIN_B_CAT could not be executed
Request: Create Index /RPM/FIN_B_GROUP-001 (DDIC/20.04.09/22:29)
Line 1: Incorrect syntax near '('.
The SQL statement was not executed
Index could not be created completely in the database
Index /RPM/FIN_B_GROUP-001 could not be created
Request for /RPM/FIN_B_GROUP could not be executed
Request: Delete and recreate Index DPR_OBJLINK_SC-1 (DDIC/20.04.09/22:29)
Index DPR_OBJLINK_SC-1 must be created in the database
Line 1: Incorrect syntax near '('.
The SQL statement was not executed
Index could not be created completely in the database
Index DPR_OBJLINK_SC-1 could not be created
Request for DPR_OBJLINK_SC could not be executed
Table conversion (TBATG)
End date and time : 20090420222912
Ended with return code: ===> 8 <===
I have never come across this error before. I looked at the note SAP Note 822379 "Known problems with Support Packages in SAP NW 7.0x AS ABAP" without any luck.
Drive where all DATAFILEs are located was full and I thought this could be the reason support pack stopped with the above error. I moved DATAFILE1 from datafile D drive to F drive (freed up 20 GB) and I restarted support pack upgrade again but the issue is same. Has anyone come across this error before or any idea that would help me to resolve this issue?
Thanks in advance for all your help.
Shahid Anjum
Seems like potentially the index where not created because your DB was full or the tablespace where the index was been created was full and system was not able to extend it.
Now check in DB02 if any tablespaces are full and let us know.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Praseen and all,
Thanks for your expert advise. OSS note 1180553 resolved my issue. All /RPM/* tables were not consistant and I could see few missing indexes in ST04. It seems like this issue is specific to SQL 2000 only. I ran following command from Query analyser and I also implemented correction attached to this note.
update sm1.TATAF
set PRTEXT = ' '
where PRTEXT like '%WITH ( ONLINE=OFF )%';
delete from sm1.TBATG where OBJECT = 'INDX' and
( FCT = 'CRE' or FCT = 'CNV' and INDNAME <> ' ' and SEVERITY = 'E' )
Since this issue is resolved, I am closing this thread.
Regards,
Shahid Anjum
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
From se14, please check all /RPM/* tables are consistent in database and check the indexes also. It seems the indexes for these tables are not mainteined in sync in both Database and data dictionary.
Thanks
Gautam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.