on 03-06-2008 2:33 PM
Hello.
Recently we did a reorganization of tables and indexes (RESB, PLAF, EBAN,
MDTB, MDKP, KBED) , as instructions of note 23278.
We create a new tablespace for these tables (PSAP4TABD & PSAP4TABI).
However, we now have WRONG_TABLESPACES alerts in DB13.
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.EBAN, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.KBED, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.KBED~0, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.KBED~1, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.KBED~2, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.MDKP, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.MDKP~ZA, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.NAST, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.NAST~0, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.NAST~A, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.NAST~I, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.NAST~S, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.NAST~ZNS, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.PLAF, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.PLAF~0, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.PLAF~1, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.PLAF~2, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.PLAF~Z03, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.RESB, value: PSAP4TABD
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.RESB~0, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.RESB~M, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.RESB~Z01, value: PSAP4TABI
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPR3.RESB~ZRE, value: PSAP4TABI
It's possible that SAP Data Dictionary is pointing to the old tablespace.
How should proceed in this situation?
Regards.
Rafael Carlos
Refer note 655162 for solution.
With regards
Sudha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.