The following entries in table ‘TAORA’ do not represent existing DB containers: [TABART, DBSPACE]

Posted on


During SUM upgrade in the extraction phase PREP_INIT/INIT_CNTRANS_PRE the following error was encountered:

The following entries in table ‘TAORA’ do not represent existing DB containers: [TABART, DBSPACE]

DODS PSAPDATODS

The following entries in table ‘IAORA’ do not represent existing DB containers: [TABART, DBSPACE]

DODS PSAPDATODS

 

 

 

 

 

 

 

 

 

 

From the description of the error we can draw the conclusion that the TABART DODS is assingned to the tablespace PSAPDATODS, that does not exist.
I checked at database level and all tablespaces were present, including PSAPDATODS:

sqlplus / as sysdba
select TABLESPACE_NAME from USER_TABLESPACES;
TABLESPACE_NAME
------------------------------
PSAPDAT
PSAPDAT740
PSAPDATFACT
PSAPDATODS
PSAPDATUSR
PSAPTEMP
PSAPUNDO
SYSAUX
SYSTEM

Also in SAP all of them could be visible in table TSORA:

 

 

 

 

This sounds very strange, so let’s also verify the SUM logs to check exactly what it checks:
The tool runs 3 scripts (that can be found in /usr/sap/SID/SUM/abap/control/dbs/ORA): SELTAIA.ORA, TAIORA.SAP that list the correspondents between TABART and tablespaces and SELDBS.ORA that lists the name of available tablespaces. The output of the first 2 scripts seems ok but SELDBS.LOG, the log from SELDBS.ORA does not display all the tablespaces available in the database:

># cat SELDBS.LOG

tp_exec_statement: select TABLESPACE_NAME from USER_TABLESPACES
DBS>>> PSAPDAT
DBS>>> PSAPDAT740
DBS>>> PSAPDATFACT
DBS>>> PSAPDATUSR

tp_exec_dbscript: 1 statement(s) successfully processed.

The reason why the output is different, is because SUM executes the sql statement under user schema owner, which lists a different output because in this case the database specific preparations mentioned in the SUM upgrade guide haven’t been checked.

The resource quotas of Oracle user SAP<SCHEMA-ID> or SAPSR3 have to be checked with the statement:

select * from dba_sys_privs where grantee="SAPSR3/SAP<SCHEMA-ID>";

As this does not exist, it has to be granted:

grant unlimited tablespace to sapsr3/SAP<SCHEMA-ID>;

After the grant was given the error was solved, SUM tool could see all the available tablespaces and jumped to the next step.

 

 



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *