I’d like you to help me with this situation, weekly I make a checkDB in the db13, when I check the Detail log I notice I have the following warnings:
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
When I review if this tables exist, using the transactions SE11 and SE17, it says this tables doesn’t exist in an active way. I want to solve this problem because I want to configure RMAN to make a weekly backup.
Thanks a lot for your help.
This error is common and a note in SAP exists. To remove them from the checkdb you can simply add
them to the DBDIFF table as per note #33814 ->
Entering/Maintaining exceptions in DBDIFF
One thing to consider is
"Objects which are missing on the database but which have been created
in the ABAP/4 Dictionary must not be entered as an exception in the table but
instead be created on the database", however I see you mentioned above they are not existing your system and are not active.
If both tables exist also in the abap then you need to move them to the correct tablespace via the BRSPACE tool. From Brtools 7.00 there is an option "-l" for example "-l PSAPES46CD". The new tablespace will then take over all data classes from the old tablespace and no manipulation
of the tables DD09L, DDART, DARTT, TAORA, ISORA and TSORA would be necessary. Brtools are database dependent so you can use a higher version with lower oracle versions. Please refer to oss note #12741 to see if Brtools 7.00 is suported with your Oracle version. Unfortunately I cannot find the above tables internally, so I cannot advise you to drop them but if they already exist I would recommend to move them to the correct tablespace and create the indexes if they already are present in the ddic and database to avoid the warnings in the checkdb job. To reorganise the tables with BRSPACE the option -l is listed in oss note #646681. Indexes can be created for the tables via SE14 transaction. As with all changes please ensure you take a backup afterwards,
These tables have been created on the database level as a backup of table D021T it seems for some reason previously . Since these are non-standard SAP tables , you can delete them from the database level as suggested by Orkun. Do not add these tables in the exception table DBDIFF as this contains SAP provided internal tables which are not part of the ABAP dictionary and SAP tools such as R3ldctl are aware of this table set in DBDIFF.
To be absolutely sure check with SAP via an OSS message if the tables are standard.
Also just to be extra cautious , check if the entries for these tables exist in NAMETAB tables DDNTT and DDNTF which ideally should not when you delete the tables.
I checked an internal test system based on the other replies above, you should see the original table D021T in SE11/SE14. It is a standard table and it looks like you have a copy of the table leftover from some other operation. Proceed as per the other suggestions.