on 01-31-2011 12:19 AM
I received the above while applying EHP4 to my ERP 6.0 system. I checked the contents of the TAORA and IRAORA tables as per note 541542 but really can't decide what I am supposed to do. From reading the notes I would think I could ignore them but I do not want any post EHP inconsitencies if I can avoid them. Attached are the errors and contents of the tables. This is a Windows 2003 R2 64 bit system with an Oracle 11G database. The matching index tablespace was not created during out upgrade to ERP60. Any help will be appreciated.
Thank You
Troy
Container pair 'PSAPEL700D'/'PSAPEL700D' for tabart 'SLDEF' not different.
Container pair 'PSAPEL700D'/'PSAPEL700D' for tabart 'SLEXC' not different.
Container pair 'PSAPES700D'/'PSAPES700D' for tabart 'SSDEF' not different.
Container pair 'PSAPES700D'/'PSAPES700D' for tabart 'SSEXC' not different.
contents taora
TABAR TABSPACE PCTI OFR OF OP OP
-
-
-
--- -- -- --
APPL0 PSAPSTABD 0000 001 01 10 40
APPL1 PSAPBTABD 0000 1 1 10 40
APPL2 PSAPPOOLD 0000 1 1 10 40
CLUST PSAPCLUD 0000 1 1 10 40
DDIM PSAPDIMD 0000 001 01 00 60
DFACT PSAPFACTD 0000 004 01 10 60
DODS PSAPODSD 0000 004 01 00 60
POOL PSAPPOOLD 0000 1 1 10 40
SDIC PSAPDDICD 0 1 1 10 40
SDOCU PSAPDOCUD 0000 1 1 10 40
SLDEF PSAPEL700D 0000 1 1 10 40
TABAR TABSPACE PCTI OFR OF OP OP
-
-
-
--- -- -- --
SLEXC PSAPEL700D 0000 1 1 10 40
SLOAD PSAPLOADD 0000 1 1 10 40
SPROT PSAPPROTD 0000 1 1 10 40
SSDEF PSAPES700D 0000 1 1 10 40
SSEXC PSAPES700D 0000 1 1 10 40
SSRC PSAPSOURCED 0000 1 1 10 40
TEMP PSAPSOURCED 0000 1 1 10 40
USER PSAPUSER1D 0000 1 1 10 40
USER1 PSAPUSER1D 0000 1 1 10 40
USER2 PSAPUSER1D 0000 001 01 10 40
USER6 PSAPUSER1D 0000 001 01 10 40
TABAR TABSPACE PCTI OFR OF OP OP
-
-
-
--- -- -- --
USER7 PSAPUSER1D 0000 001 01 10 40
USER8 PSAPUSER1D 0000 001 01 10 40
USER9 PSAPUSER1D 0000 001 01 10 40
USR00 PSAPUSER1D 0000 001 01 10 40
USR01 PSAPUSER1D 0000 001 01 10 40
USR02 PSAPUSER1D 0000 001 01 10 40
USR03 PSAPUSER1D 0000 001 01 10 40
USR04 PSAPUSER1D 0000 001 01 10 40
USR05 PSAPUSER1D 0000 001 01 10 40
USR06 PSAPUSER1D 0000 001 01 10 40
USR07 PSAPUSER1D 0000 001 01 10 40
TABAR TABSPACE PCTI OFR OF OP OP
-
-
-
--- -- -- --
USR10 PSAPUSER1D 0000 001 01 10 40
USR08 PSAPSOFFD 0000 001 01 10 40
USR09 PSAPUSER1D 0000 001 01 10 40
USR11 PSAPBTABD 0000 001 01 10 40
USR12 PSAPSTABD 0000 001 01 10 40
USR13 PSAPPOOLD 0000 001 01 10 40
USR19 PSAPUSER1D 0000 001 01 10 40
USR16 PSAPDOCUD 0000 001 01 10 40
USR17 PSAPPROTD 0000 001 01 10 40
USR20 PSAPLOADD 0000 001 01 10 40
USR15 PSAPCLUD 0000 001 01 10 40
TABAR TABSPACE PCTI OFR OF OP OP
-
-
-
--- -- -- --
USR18 PSAPSOURCED 0000 001 01 10 40
USR14 PSAPDDICD 0000 001 01 10 40
46 rows selected.
contents of IAora
TABAR TABSPACE PCTI OFR OP
-
-
-
--- --
SLOAD PSAPLOADI 0000 001 10
USR08 PSAPSOFFI 0000 001 10
SDIC PSAPDDICI 0000 001 10
USR14 PSAPDDICI 0000 001 10
USR20 PSAPLOADI 0000 001 10
USR10 PSAPUSER1I 0000 001 10
CLUST PSAPCLUI 0000 001 10
USR15 PSAPCLUI 0000 001 10
SSRC PSAPSOURCEI 0000 001 10
TEMP PSAPSOURCEI 0000 001 10
USR18 PSAPSOURCEI 0000 001 10
TABAR TABSPACE PCTI OFR OP
-
-
-
--- --
USER PSAPUSER1I 0000 001 10
USER1 PSAPUSER1I 0000 001 10
USER2 PSAPUSER1I 0000 001 10
USER6 PSAPUSER1I 0000 001 10
USER7 PSAPUSER1I 0000 001 10
USER8 PSAPUSER1I 0000 001 10
USER9 PSAPUSER1I 0000 001 10
USR00 PSAPUSER1I 0000 001 10
USR01 PSAPUSER1I 0000 001 10
USR02 PSAPUSER1I 0000 001 10
USR03 PSAPUSER1I 0000 001 10
TABAR TABSPACE PCTI OFR OP
-
-
-
--- --
USR04 PSAPUSER1I 0000 001 10
USR05 PSAPUSER1I 0000 001 10
USR06 PSAPUSER1I 0000 001 10
USR07 PSAPUSER1I 0000 001 10
USR19 PSAPUSER1I 0000 001 10
APPL0 PSAPSTABI 0000 001 10
USR12 PSAPSTABI 0000 001 10
SDOCU PSAPDOCUI 0000 001 10
USR16 PSAPDOCUI 0000 001 10
SPROT PSAPPROTI 0000 001 10
USR17 PSAPPROTI 0000 001 10
TABAR TABSPACE PCTI OFR OP
-
-
-
--- --
DDIM PSAPDIMI 0000 001 10
DFACT PSAPFACTI 0000 004 10
DODS PSAPODSI 0000 004 10
SLDEF PSAPEL700D 0000 1 10
SLEXC PSAPEL700D 0000 1 10
SSDEF PSAPES700D 0000 1 10
SSEXC PSAPES700D 0000 1 10
USR09 PSAPUSER1I 0000 001 10
APPL1 PSAPBTABI 0000 001 10
USR11 PSAPBTABI 0000 001 10
APPL2 PSAPPOOLI 0000 001 10
TABAR TABSPACE PCTI OFR OP
-
-
-
--- --
POOL PSAPPOOLI 0000 001 10
USR13 PSAPPOOLI 0000 001 10
Basically IAORA is pointing to the data tablespace rather than index tablespace.
You should change the D's for I's in IAORA via SE16 to avoid the issue. If ignored you might end with a lot of indexes in the wrong tablespace (which is not a show stopper but it will create lots of errors on the logs) and you'll have to move the indexes manually later.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Look at below quote from the note,
Solution
Maintain the contents of the tables, either using transaction se16 in the SAP system
ORACLE:
Standard layout: TABART: TAORA-TABSPACE, IAORA-TABSPACE
SSDEF: PSAPES<rel>D, PSAPES<rel>I
SSEXC: PSAPES<rel>D, PSAPES<rel>I
SLDEF: PSAPEL<rel>D, PSAPEL<rel>I
SLEXC: PSAPEL<rel>D, PSAPEL<rel>I
You need to replace the D's for I's in IAORA
Perhaps you should read farther, as you can see from the statement below the case I am under is the first case. In which case the note implys you should NOT create the tablespace. If I change the D for an I in IAORA then R3UP generates a different error pertaining to the tablespace not existing.
The R3up error message indicates that there is an inconsistency. This always means that one of the TABSPACEs/DBSPACEs does not exist on the database. In this case, creating the tablespace or container is not always the correct solution:
You should differentiate between the following cases:
The container of an exchange TABART does not exist. Exchange TABARTs are SSDEV, SSEXC, SLDEV, SLEXC. You must always enter an exchange container here. In fact, the exchange container always exists. You can identify these containers by the release name. Enter the name of the corresponding exchange container.
The container of a non-exchange SAP TABART does not exist. Determine whether a container exists on the database with the common name and enter this container. Alternatively, create the container, which is maintained in the TA<dba>/IA<dbaA> table. Do not use an exchange container.Troy
Hi Eric
I wanted to hear from someone who had the same issue. Unlike Juan, when we ran our 4.7 to ERP 6.0 upgrade we asked why the index tablespace wasn't created and were told SAP started storing both types of objects in the same tablespace. Interstingly enough, after I created the index tablespaces brtools adjust IAORA on it's own as I did not have to update the table. Thanks for sharing our experience
Troy
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.