Check database DB13 WARNING, type: IN_WRONG_TABLESPACE

[tomkam]

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 “The table doesn’t exist” 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 don’t 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

[Snowy]

First of all, as a new Basis, you should ALWAYS log into SAP with language EN.

Why? Because you will see error messages in English and be able to search on the Internet with the errors.

Second: always provide SAP/OS/DB versions.

[hoinz]

I had a look at a few of our systems, and I could find table D021T, but neither D021T_COPY nor D021T_DUPS.
As these two tables seem not to be in the ABAP dictionary either, I suspect this:

You (or a predecessor of yours) felt the necessity to have backup copies of table D021T, and created them by Oracle tools. (Actually I am doing something like that myself sometimes.) And nobody thought of deleting the copies afterwards.

But as I wrote: That's just my suspicion.
Draw a conclusion at your own risk!

regards

[Snowy]

export these 2 tables, take these exports in a backup, then, drop the 2 tables.

good luck.