cancel
Showing results for 
Search instead for 
Did you mean: 

Check database DB13 WARNING, type: IN_WRONG_TABLESPACE

Former Member
0 Kudos

Good afternoon experts:

(i have Server: SAP, Solaris 10 and Oracle 9i )

I made a Check database in the transaction DB13 of SAP and the result was this:

Realice un Check database en la transacción DB13 de SAP y el resultado fue el siguiente:

BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.D021T_COPY, value: PSAPES46CD

BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.D021T_DUPS, value: PSAPES46CD

BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3.D021T_COPY

BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3.D021T_DUPS

I used the transactions se11 and se16 to see the tables, but I get the message u201CThe table doesnu2019t existu201D as shows the images:

http://s2.subirimagenes.com/imagen/prev ... 78se11.png

http://s2.subirimagenes.com/imagen/prev ... 80se16.png

Using the transaction db02 I can see the tables are in the tablespace PSAPES46CD, but I donu2019t know the reason of the warning:

http://s2.subirimagenes.com/imagen/prev ... espace.png

http://s3.subirimagenes.com:81/imagen/p ... space2.png

If you look, with the db02 I can see the tablespace that contains both tables and the nexts is the tablespace that should contain the index but it's empty:

http://s2.subirimagenes.com/imagen/prev ... 91db02.png

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

SAP provided work around for this. It also has provided the corrections for avoiding this error in future.

Please implement below Snote

SAP Note 1578001 - BR0970W IN_WRONG_TABLESPACE, BR0989W Unknown tablespace .

Regards,

Venkata S Pagolu

former_member182034
Active Contributor
0 Kudos

hi,

there is data inconsistency between database and ABAP Dictionary,

for this,

you can adjust with help of SE14 or

alter index SAPSR3."<index name>" rebuild online;

Read this SAP Note 33814 - Warnings of inconsistencies between database & R/3 DDIC

Regards,