Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error while importing a table index.

Former Member
0 Kudos

Hi,

We are facing a problem while importing an index to the production region. Below are the details.

1. A secondary index was created on standard SAP table ILOA in DEV region.

2. The Index was successfully moved to the Quality system, without any glitches.

3. Due to some issue (releated to testing, for which we had to revert back the changes), we had to delete the index on ILOA in the DEV region. The transports were moved to the PPD region and hence, the index on ILOA was deleted in PPD also.

4. Once the issue related to testing was resolved, we again created an index on the table ILOA and moved it to PPD.

All these 4 mentioned steps happened successfully and in PPD there was no error while importing the transports.

But, while moving the above transports to the Production region, there was an error :

"Index ILOA~Y could not be activated

(E - No index ILOA~Y found with status M)"

Please note that Y is the name of the index that was created on the table ILOA.

The error code that we have got is "8".

Can anyone please shed any light on what the issue is?? WE cannot re-import the transports in to Production without analysing this issue,because our client doesnt permit that.

Thanks and eagerly awaiting a kind reply.

Regards,

Raghavendra.

1 ACCEPTED SOLUTION

matt
Active Contributor
0 Kudos

You've three transports - one to create the index, one to delete, and one to recreate. It could be that the the third one tried to run before the database had finished with the second?

Have you looked on SE14 for the actual status on production of the index?

matt

2 REPLIES 2

matt
Active Contributor
0 Kudos

You've three transports - one to create the index, one to delete, and one to recreate. It could be that the the third one tried to run before the database had finished with the second?

Have you looked on SE14 for the actual status on production of the index?

matt

Former Member
0 Kudos

Yes Matthew....i agree on that. That must be the possible error...though i cant login to productiona and see the status, our client doesnt grant that access.

Thanks any ways.