on 12-02-2008 4:25 PM
hi all,
I am updating patches for solman. i got struck with an issue while applying the patch "SAPKW70018"
firstly I got an issue at IMPOR_PROPER ....then i checked in the "Import Logs of the Queue" its given that
" The SQL statement was not executed
Index could not be created completely in the database
Index RSDADAP-002 could not be created "
along with it the other four indexes missing are
RSDADAP-001
RSPCPROCESSLOG-005
RSTT_LOGRUN-2
RSTT_LOGRUN-3
then i created the indexes manually in SQL server enterprise Manager and executed the query.....
but the issue is the same.....but when i checked in "Import Logs of the Queue" giving the error as
" Request: Create Index RSDADAP-001 (DDIC/02.12.08/08:22)
Index RSDADAP~001 already exists in the database
Index RSDADAP-001 could not be created
Request for RSDADAP could not be executed "
same as for the other 4 ......
tell me how to resolve my issue......
waiting for ur replies...........
regards,
Aravind
Edited by: Aravind Bheemalingam on Dec 2, 2008 5:26 PM
Edited by: Aravind Bheemalingam on Dec 3, 2008 5:46 AM
Hi,
Regarding the error, please refer to note 1180553.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi wong,
thanks for ur reply.
after created the five missing indexes ..I crossed the import_proper phase:
now i am getting error as:
"
Phase CHECK_REQUIREMENTS: Explanation of Errors
Some open conversion requests still exist in the ABAP Data Dictionary for the following ABAP Dictionary objects. To avoid inconsistencies and loss of data, you must process these conversions first.
Proceed as follows:
- Open a new session.
- Start the Database Utility (transaction SE14).
- Correct the inconsistencies for the specified objects.
- Repeat the import phase. If no more inconsistencies are found, the import Continues.
Phase CHECK_REQUIREMENTS: Open ABAP Dictionary Conversions
Object Type Object Name
Table Index RSDADAP ~ 001
RSDADAP ~ 002"
but in se14 i am not having any inconsistencies...i did the import phase but the error is same...
waiting for ur reply
regards,
Aravind
Edited by: Aravind Bheemalingam on Dec 3, 2008 7:56 AM
Edited by: Aravind Bheemalingam on Dec 3, 2008 10:02 AM
Edited by: Aravind Bheemalingam on Dec 3, 2008 11:57 AM
now when i clicked on import queue its showing that teh error is in IMPORT_PROPER phase:
andin log it is given as:
ED0327XProcess..................: "usirs255_11"
2 EGT055XRequest: Delete and recreate "Index RSPCPROCESSLOG-005 (DDIC/03.12.08/06:10)"
4 EGT281 sql:
4 ED0314 DROP INDEX [RSPCPROCESSLOG].[RSPCPROCESSLOG~005]
4 EDA093 "DDL time(___1):" ".........2" milliseconds
2 EDT502 Index "RSPCPROCESSLOG"-"005" must be created in the database
4 EDT520 Index "RSPCPROCESSLOG"-"005" was successfully activated
4 EGT281 sql:
4 ED0314 CREATE
4 ED0314 INDEX [RSPCPROCESSLOG~005] ON [RSPCPROCESSLOG]
4 ED0314 ( [TYPE] ,
4 ED0314 [VARIANTE] ,
4 ED0314 [INSTANCE] )
4 ED0314 WITH ( ONLINE=OFF )
4 ED0314 ON [PRIMARY]
2 ED0314 Line 1: Incorrect syntax near '('.
4 EDA093 "DDL time(___1):" "........18" milliseconds
2EEGT236 The SQL statement was not executed
2EEDI006 Index " " could not be created completely in the database
2EEGT082 "Index" "RSPCPROCESSLOG-005" could not be created
2 EGT067 Request for "RSPCPROCESSLOG" could not be executed
1 ETP166 CONVERSION OF DD OBJECTS (TBATG)
1 ETP110 end date and time : "20081203061056"
1 ETP111 exit code : "8"
1 ETP199 ######################################
same as for
RSPCPROCESSLOG~001
RSPCPROCESSLOG~002
RSPCPROCESSLOG~003
RSPCPROCESSLOG~004
RSDADAP~001
RSDADAP~002
regards,
Aravind
Edited by: Aravind Bheemalingam on Dec 3, 2008 3:53 PM
Hello,
I activated indexes with the same error message by using SE14. You have to edit the table and then select the index so you will have the table name - <index> at the top of the page. Use the Activate and adjust database button. After this I was able to continue processing support packs.
Regards,
Robert
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.