Application Development and Automation 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: 
Read only

Error accessing a table

senthil_kumar29
Participant
0 Likes
2,164

Hello Friends,

I try to access a SAP standard table using SE16 txn, its dumping.

This table structure has recently been changed, and all data in it is lost.

I add a field to this table, When I do error check, getting following log.

-


Check table T9AA01 (SAPRAJU/05.12.07/21:33)

Old key field VALIDFROM has been deleted

An SQL error occurred during a test access to the table

Cause: Database lock or inconsistency: Dictionary database

Table T9AA01 (Statements could not be generated)

Error number in DD_DECIDE (0)

Check on table T9AA01 resulted in errors

-


When I use Utility menu to adjust table structure, getting following error.

-


Request: Convert Table T9AA01 (SAPRAJU/05.12.07/21:35)

Process: erpdev1_1

Test activation of Table T9AA01 successful

Old key field VALIDFROM has been deleted

An SQL error occurred during a test access to the table

Cause: Database lock or inconsistency: Dictionary database

Compare module DD_DECIDE ended with error(s)

Database object for table T9AA01 is checked

Database object for table T9AA01 is inconsistent

Convert Table T9AA01 by unloading and reloading the data

Type of conversion: T -> T

-


Begin step T9AA01-STEP1:

Step is empty

Step T9AA01-STEP1 executed successfully

-


Begin step T9AA01-STEP2:

sql:

ALTER TABLE [T9AA01]

DROP CONSTRAINT [T9AA01~0]

Constraint 'T9AA01~0' does not belong to table 'T9AA01'.Could not drop constraint. See previous erro

DDL time___1: .........5 milliseconds

T9AA01~0 could not be removed

Error deleting index T9AA01~0

Not all indexes could be deleted for table T9AA01

Error in step T9AA01-STEP2

-


Total time for table T9AA01: 000:00:01

Request for T9AA01 could not be executed

-


ThanQ for ur valuable time.

Cheers,

Senthil

6 REPLIES 6
Read only

Former Member
0 Likes
1,777

Hi

In SE14 try Activate and Adjust database .

Praveen

Read only

0 Likes
1,777

I have tried SE14 to adjust the table, its not successful. actually its locking the table.

Cheers,

Senthil

Read only

Former Member
0 Likes
1,777

It looks like table VALIDFROM had a field VALIDFROM as a key field and you deleted the field from the table. Could it be that the field VALIDFROM was also a field in a secondary index? If so, try deleting that field from the secondary index and then use SE14 to adjust.

Rob

Read only

KN-Nampoothiry
Active Participant
0 Likes
1,777

Hi,

I think Bob is correct ... seems some indexes are there with the deleted field as the field in it and u have to explicitly delete all indexes...take note of the exisiting indexes and create them all over again as alraeady u have cleared the data.

I guess try this way :

1. Note all indexes and then delete all indexes.

2.SE14 : Activate & adjust DB

3. Create Indexes

This should solve.

<b>Do reward if this works out</b>

Regards

Read only

0 Likes
1,777

Don't delete all the indexes - just the ones that have this field. If that doesn't work, get back to the forum.

Rob

Read only

0 Likes
1,777

Hi,

Thank you for ur answers.

I can able to activate the table.

But there is inconsistency between Runtime object and database object.

How to rectify this problem. There is no secondary index exist.

when I try display table entries its dumping.

SM21 shows database error 207.

Cheers