Error in Phase Deleting Substitution Tablespaces - (Follow Up Activities)

Question

Hello,
I have the following problem after finish upgrade 4.7 for ECC6 SR3 AIX-DB2 9.5
At phase Follow up Activities :  6.2 Deleting Substitution Tablespaces. (pag 139 - Upgrade Guide)
Delete old
PSAPES<source release>D
PSAPES<source release>I
PSAPEL<source release>D
PSAPEL<source release>I
I deleted the tablespaces PRD#EL620D and PRD#EL620I with sucess, but when I try delete the tablespace  PRD#ES620D, the following error appear :
$ db2 drop tablespace PRD#ES620D
DB21034E  The command was processed as an SQL statement because it was not a
valid Command Line Processor command.  During SQL processing it returned:
SQL0282N  Table space "PRD#ES620D" cannot be dropped because at least one of
the tables in it, "SAPPRD.BCACT", has one or more of its parts in another
table space.  SQLSTATE=55024
How can I resolve this problem ?
best regards

Answer 1

Dear Emerson,
Can you check your list of tables if they are all listed in OSS note 674070.
From reading you message it sounds like you situation is covered by section 4.
Can I ask you to please follow the instructions in attached note 674070?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Table names: BTCSED, DVERS, EDMAP, FREF, IXDIT, IXTYT, ST05RESULT,
TESCL, TESPO, VBLOG, BCACT, BCCOM, BCSPO, BCTOU, CNTLWARN, DFAXD, E071K,
STXRDIR, T705T, TRT1, TRTES, TSTCA_C, BCEXC, BCRES, PDSNR, POCTRACE,
STXRDID, T705X, T77ALE_DEF, T77ALE_IF, T77ALE_IFT, TRSTIT, TWPSSO2SGN,
TWPSSO2VER, CD0T000, CD0T120TAB, CD0T130TAB, CD0T140TAB, CD0T500TAB,
CD2APP0, CD2HV1PTAB, CD2HV2FTAB, DDVE1, DDVEPR, TFLOATCONV, VERPF,
VERPF2, VGGT2, VGHT2, VGPT2
The error only occurs with databases that use different containers
(tablespaces, DBSpaces, and so on) for saving data. Caution: The report
described in this note is only implemented for the Oracle, Informix and
DB2 UDB for UNIX and Windows databases. It is not required for other
databases.
Solution
1.  Download the attached SAR archive ("Attachments" tab) and use the
    relevant SAPCAR to unpack it to your transport directory.
2.  Then import the transport B20K8A1ZZI into your system. This contains
    the report RSCHECKEXC.
    Caution: To import the transport, you need an R3trans version dating
    from at least 18.8.05.
3.  Call transaction SE38 and execute the "RSCHECKEXC" report directly.
       The report output is attached to the log file
       <DIR_TRANS>/tmp/RSCHKEXC.<SID>.
The various possible uses for the report are explained below:
4.  You have performed the release upgrade and notice the symptom
     described above: The old substitution containers are not empty.
     Solution: Use database tools to generate a list of tables that are
     in the old substitution container and save this list in a text file
     (one table name on each row). Copy this file to the application
     server on which you call the RSCHECKEXC report.
     When you call the report, enter the absolute file name in the
     "TABFILE" field and execute the report.
     As described above, you can now select the MODE="" (check only),
     MODE="DRCR" (recreate empty tables) and MODE="ICNV" (add tables wit
     contents to the ICNV) options.
     Unlike before, where the report selects all of the tables that have
     one substitution table type, the report now works on the list of
     tables from the file.
After you have successfully implemented this note, the old exchange
container (PSAP<SID>620) should be empty. Use database tools to confirm
that this is the case.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I believe that this note will resolve your issue.
Regards,
Abhishek