IN_WRONG_TABLESPACE, object: table/index

[Former Member]

Hi all,

Apologies for the repost of this topic. I have seen it a few times but without resolutions. My problem is as follows.

BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (index) SAPSR3.D010INC~1, value: PSAPSR346C

BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPSR3.D010L, value: PSAPSR346C

This is IAORA.

-

---

TABART

TABSPACE

PCTINC

OFREELIST

OPCTFREE

-

---

	APPL0	PSAPSR3	0000	1	10
	APPL1	PSAPSR3	0000	1	10
	APPL2	PSAPSR3	0000	1	10
	CLUST	PSAPSR3	0000	1	10
	POOL	PSAPSR3	0000	1	10
	SDIC	PSAPSR3	0	1	10
	SDOCU	PSAPSR3	0000	1	10
	SLDEF	PSAPSR346D	0000	1	10
	SLEXC	PSAPSR346D	0000	1	10
	SLOAD	PSAPSR3	0000	1	10
	SPROT	PSAPSR3	0000	1	10
	SSDEF	PSAPSR346D	0000	1	10
	SSEXC	PSAPSR346D	0000	1	10
	SSRC	PSAPSR3	0000	1	10
	TEMP	PSAPSR3	0000	1	10
	USER	PSAPSR3USR	0000	1	10
	USER1	PSAPSR3USR	0000	1	10

This is TAORA.

TABART

TABSPACE

PCTINC

OFREELIST

OFREEGROUP

OPCTFREE

OPCTUSED

-

---

	APPL0	PSAPSR3	0000	001	01	10	40
	APPL1	PSAPSR3	0000	1	1	10	40
	APPL2	PSAPSR3	0000	1	1	10	40
	CLUST	PSAPSR3	0000	1	1	10	40
	POOL	PSAPSR3	0000	1	1	10	40
	SDIC	PSAPSR3	0	1	1	10	40
	SDOCU	PSAPSR3	0000	1	1	10	40
	SLDEF	PSAPSR346D	0000	1	1	10	40
	SLEXC	PSAPSR346D	0000	1	1	10	40
	SLOAD	PSAPSR3	0000	1	1	10	40
	SPROT	PSAPSR3	0000	1	1	10	40
	SSDEF	PSAPSR346D	0000	1	1	10	40
	SSEXC	PSAPSR346D	0000	1	1	10	40
	SSRC	PSAPSR3	0000	1	1	10	40
	TEMP	PSAPSR3	0000	1	1	10	40
	USER	PSAPSR3USR	0000	1	1	10	40
	USER1	PSAPSR3USR	0000	1	1	10	40

select tablespace_name from dba_tablespaces;

SYSTEM,PSAPUNDO,SYSAUX,PSAPTEMP,PSAPSR3,PSAPSR346C,PSAPSR3USR

Tablespace does exist as you can see above now to determine type of tablespace, and as per below query you can see it contains

both data and indexes.

select distinct(segment_type), tablespace_name from dba_segments order by tablespace_name;

SEGMENT_TYPE TABLESPACE_NAME

-

---

-

---

INDEX PSAPSR3

TABLE PSAPSR3

INDEX PSAPSR346C

TABLE PSAPSR346C

TABLE PSAPSR3USR

TYPE2 UNDO PSAPUNDO

INDEX SYSAUX

INDEX PARTITION SYSAUX

LOB PARTITION SYSAUX

LOBINDEX SYSAUX

LOBSEGMENT SYSAUX

As per note 655162 option 1 and 2 are applicable to me. But as this tablespace seems to be both a data and index tablespace I am thinking I need to create the tablespace entry in IAORA and TAORA.

How would I correctly edit these table entries and which of the following tables might also have to be edited?

DDART and DARTT are used to maintain the classes ( tabarts)

DD09L maps the tables to each class ( tabart)

TAORA/IAORA maps the classes to the tablespaces

TSORA lists the tablespaces.

As a non dba I find the sap note a bit confusing please advise.

Kind Regards,

Johan

[Former Member · Accepted solution]

Apparently SAPSR3.D010INC~1, value: PSAPSR346C is not defined in TAORA an IAORA, you have to create according to 655162.

THanks

SM

[Former Member · Accepted solution]

Hi,

Since tablespace PSAPSR346C does exist and PSAPSR346D does not exist. Would it work if I rename entries in IAORA and TAORA from PSAPSR346D to PSAPSR346C.

Or should I DELETE the entries for PSAPSR346D and create new entries for PSAPSR346C ?

Kind Regards,

J

[Former Member · Accepted solution]

Hello Johan,

it is possible and easier if you rename the entries in TAORA/IAORA.

It doesn't make sense to have some unexistent tablespace name there,

so rename PSAPSR346D to PSAPSR346C and check again whether your

messages BR0970W now disappear.

Regards,

Mark

[Former Member · Accepted solution]

Hi mark,

Would this not affect anything else in related tables maybe if I only edit:

DDART and DARTT are used to maintain the classes ( tabarts)

DD09L maps the tables to each class ( tabart)

TAORA/IAORA maps the classes to the tablespaces

TSORA lists the tablespaces.

If not I will edit the entries and let you know of results.

J

[Former Member · Accepted solution]

Hi Johan,

the tablespaces are only mentioned in TAORA/IAORA/TSORA. So you can safely manually

change the tablespace name from PSAPSR346D to PSAPSR346C without breaking anything.

I have already done that several times.

Regards,

Mark

[Former Member · Accepted solution]

After going through the note, I would create Tablesapce PSAPSR346D and move the objects from PSAPSR346C to PSAPSR346D.

In this way I;m not chaning anything at SAP level.

You can use BRTOOLS to create Tablesapce.

Thanks

SM

[Former Member · Accepted solution]

Creating tablespace PSAPSR346D is an option, but it does not follow the SAP convention. The system at hand is a 4.6C version (see table SVERS). The SAP kernel is 4.6D, but that doesn't matter. If you have 4.6C sources + loads then they should reside in a tablespace called 46C and not 46D, right?

[Former Member · Accepted solution]

Agreed with Foerster, but

I was under the assumption that the system release is 46D.

Example:

Basis Release 4.6D: SAPKB46D07

In this case I will adapt my Tablespace name to PSAPSR346D rather than PSAPSR346C.

Thanks

SM

[Former Member · Accepted solution]

Hi guys,

For clarification:

disp+work information

-

---

kernel release 46D

kernel make variant 46D_EXT

DBMS client library OCI_920__OCI_7_API

DBSL shared library version 46D.00

compiled on Linux 2.6.5-7.202.5-smp #1_SMP_Thu_Aug_25_06:20:45_UTC_2005 x86_64

compiled for 64 BIT

compile time Aug 10 2008 21:39:12

update level 0

patch number 2415

source id 0.2415

-

---

supported environment

-

---

database (SAP, table SVERS) 46A

46B

46C

46D

DBMS server ORACLE 8.0.5..

ORACLE 8.0.6..

ORACLE 8.1.6..

ORACLE 8.1.7..

ORACLE 9.2.0..

ORACLE 10.2.0..

operating system Linux 2.6

System build information:

-

---

LCHN :

System components:

ST-PI 2008_1_46C

ST-A/PI 01J_R3_46C

SAP_NOTES 46C

SAP_HR 46C

SAP_BASIS 46C

SAP_APPL 46C

SAP_ABA 46C

Regards,

J

[Former Member · Accepted solution]

As you can see in SVERS 46D is present, so I would recommend you to create tablespace PSAPSR346D and move the objects from PSAPSR346C to PSAPSR346D.

You might wanna start with DEV and post the progress.

Thanks

SM

[Former Member · Accepted solution]

The information so far is not sufficient to decide whether this is a basis 4.6C or 4.6D system. My assumption was that this is a R/3 system, which would make it basis 4.6C, but there are still some (few) basis 4.6D out there in the wild. Johan, could you please check the content of table SVERS (e.g. via SE16) and tell us the result?

[Former Member · Accepted solution]

Hi Guys,

My system is 46C as I mentioned running 46D kernel no confusion there.

There was already a note existing with was only recently released confirming what a a few of you said and correcting others.

1578001 - BR0970W IN_WRONG_TABLESPACE, BR0989W Unknown tablespace

Please note also you will have to modify your se06/scc4 settings to modify the table entries as required.

This is as per note Note 666061 - FAQ: Database objects, segments and extents and point 14 in the note.

Kind Regards,

J