Tab class mapping changed after reorganization

[Former Member]

Hi Experts

I have doing the reorganization of PI system of PSAPSR3 tablespace. I have followed the below steps. I had followed completely 646681 note.

1. create a new tablespace with old tablespace tabart class with option -l.

2. Reorg form the Old tablespace to new tablespace.(here while reorganization it has skipped SAPSR3.PLAN_TABLE due to LONG field)

3. Hence I had done through long2lob conversion but it has failed since it was there in new tablespace when i checked it was as "PLAN_TABLE#$" hence i dropped the table and again i tried this longtolob which was successful. When i check the columns in new tablespace it still shows LONG column?

4. After this i had dropped old tablespace.

5. Renamed the new tablespace name to old tablespace name

6. Ran full stats .

Now I have 2 doubts.

I had extracted the DD09L table list and their tab art mapping in an excel sheet and after reorg again i took the same.

Now when i compared i could see the follwoing issues.

1. certain tables which was not assigned with any tab class mapping now it has been assigned with APPL0 tab class.

2. Certain tables assigned with SSEXC tab class before reorg now it has been assigned with APPL0 tab class.

3. As per TAORA the tab class mapping has not been changed.

Queries:

1. How come the tab class has been changed or wrongly assigned?

2. There was no change in the tablespace mapping in TAORA table then how come SSEXC tab clas swhich is mapped to PSAPSR3701 in TAORA now converted to APPL0 which PSAPSR3 tablespace?

3. when i have done for only particular tablespace how the reorg touched the SSEXC tab class which was referring to PSAPSR3701 tablespace?

4. why does the PPLAN_TABLE which has LONG field created in the new tablespace when it was skipped in the reorg phase adn why it shouold expilicitlty to be done like above?

I have provide few table list as per my extract

Before Reorg After Reorg

TABNAME TABART TABNAME TABART

DD05S SSEXC DD05S APPL0

DD08L SSEXC DD08L APPL0

DD08T SSEXC DD08T APPL0

DD12L SSEXC DD12L APPL0

DD12T SSEXC DD12T APPL0

DD16S SSEXC DD16S APPL0

DD17S SSEXC DD17S APPL0

DD20T SSEXC DD20T APPL0

DD21S SSEXC DD21S APPL0

DD23L SSEXC DD23L APPL0

DD23T SSEXC DD23T APPL0

DD24S SSEXC DD24S APPL0

DD25T SSEXC DD25T APPL0

DD29T SSEXC DD29T APPL0

DELM DELM APPL0

DSYCR DSYCR APPL0

EDFIL EDFIL APPL0

EDIE5 EDIE5 APPL0

FINS FINS APPL0

INDX INDX APPL0

PAKDATBUF PAKDATBUF APPL0

SSPUMK SSPUMK APPL0

Kindly guide

Regards

Bala

[former_member529174]

expdp \'/ as sysdba\' directory=plan_tab_mv dumpfile=plan_table.dmp logfile=plan_table.log tables=SAPSR3.PLAN_TABLE parallel=1

drop table SAPSR3.PLAN_TABLE purge;

impdp \'/ as sysdba\' directory=plan_tab_mv dumpfile=plan_table.dmp logfile=plan_table.log.imp remap_tablespace=PSAPSR3:PSAPSR3D parallel=1

[Former Member]

Hi Dey

sorry for the delay in replying.

I had sorted out the issue on that day iteslelf and resolved the issues.

I had moved certain tables of brtools to another tablespace and started the export and import successfully. however when i checked all the tables in the database after reorg i found certain SYSLOB $tables were missing. I think this happened because of the dyanmic tables. i have provide few samples of the same

Before Reorg After Reorg

Table Name Type Tablespace Table Name Type Tablespace

SAPSR3SYS_IL0000009931C00014$$ LOBINDEX PSAPSR3710 SAPSR3SYS_IL0000020712C00009$$ LOBINDEX PSAPSR3710

SAPSR3SYS_IL0000010065C00010$$ LOBINDEX PSAPSR3 SAPSR3SYS_IL0000022899C00009$$ LOBINDEX PSAPSR3710

SAPSR3SYS_IL0000010082C00007$$ LOBINDEX PSAPSR3 SAPSR3SYS_IL0000023865C00005$$ LOBINDEX PSAPSR3710

SAPSR3SYS_IL0000010095C00012$$ LOBINDEX PSAPSR3 SAPSR3SYS_IL0000023865C00006$$ LOBINDEX PSAPSR3710

SAPSR3SYS_IL0000010239C00008$$ LOBINDEX PSAPSR3 SAPSR3SYS_IL0000023865C00007$$ LOBINDEX PSAPSR3710

SAPSR3SYS_IL0000010250C00006$$ LOBINDEX PSAPSR3 SAPSR3SYS_IL0000024071C00007$$ LOBINDEX PSAPSR3710

SAPSR3SYS_LOB0000038509C00005$$ LOBSEGMENT PSAPSR3 SAPSR3SYS_LOB0000150175C00008$$ LOBSEGMENT PSAPSR3

SAPSR3SYS_LOB0000038516C00005$$ LOBSEGMENT PSAPSR3 SAPSR3SYS_LOB0000150181C00015$$ LOBSEGMENT PSAPSR3

SAPSR3SYS_LOB0000038523C00002$$ LOBSEGMENT PSAPSR3 SAPSR3SYS_LOB0000150187C00009$$ LOBSEGMENT PSAPSR3

SAPSR3SYS_LOB0000038538C00007$$ LOBSEGMENT PSAPSR3 SAPSR3SYS_LOB0000150191C00015$$ LOBSEGMENT PSAPSR3

SAPSR3SYS_LOB0000038538C00008$$ LOBSEGMENT PSAPSR3 SAPSR3SYS_LOB0000150195C00040$$ LOBSEGMENT PSAPSR3

Regards

Balaji

[Former Member]

Hi

I have dropped the tablespace in SQL prompt then also the same error came. this license error comes after i am droppping the PSAPSR3 tablespace step. Is there any steps for the tablespace reorganization without any issues ..please provide me.

Regards

Bala

[former_member189725]

You can follow these steps:

CREATE TABLE SAPLIKEYTEMP AS (SELECT * FROM SAPLIKEY) in PSAPSR3701;

Drop the tablespace PSAPSR3

remane the table SAPLIKEYTEMP

alter table SAPLIKEYTEMP rename to SAPLIKEY;

Rename the New Tablespace name to old tablespace using sqlplus.

alter table SAPLIKEY move tablespace PSAPSR3;

Import the tables to PSAPSR3 tablespace using brspace.

Edited by: Ratnajit Dey on Jan 3, 2012 7:32 AM

[Former Member]

Hi Dey

Is this error of TAORA Table update? However is there any side effect for the previous method where the Tab Class has been changed. There is valid license is for the system the main issue is the error triggered when i executed the drop tablespace.

Could you validate the steps of the both methods i used for reorg. or please provide the steps so that i could check.

Regards

Bala

[former_member189725]

Please check this thread

[;

Should be helpful in your scenerio. Check the SAP Note 400241 as well.

[Former Member]

HI experts

I had not taken the tables of the respective tablespaces.Is there any consequences will happen because of tis tab class mpping during any transports or any upgrade.

Moreover i tried a export / import method of reorganization by following steps.

1. Create a new tablespace referring to old tablespace

brspace -u / -f tscreate -t <New_tsp> -d both -l <reorg_tsp>

2. Export the all the tables from the reorg_tsp i.e PSAPSR3 tablespace to a dumpdirectory

brspace -u / -f tbexport -s <reorg_tsp> -t "*" -u <dump_dir>

3. Drop the Old tablespace Now --> PSAPSR3

brspace -u / -f tsdrop -t PSAPSR3 -f

4. Rename the New Tablespace name to old tablespace

brspace -u / -f tsalter -a rename -t PSAPSR3NEW -n PSAPSR3

5. Now Import the tables to PSAPSR3 tablespace

brspace -u / -f tbimport

But in this method Export was succesfully completed in the dump directory. But while droping the reorg_tablespace i.e PSAPSR3 igot the following error:

BR0280I BRSPACE time stamp: 2011-12-30 16.20.33

BR1016I SQL statement 'drop tablespace PSAPSR3 including contents and datafiles cascade constraints' executed successfully

BR1069I Tablespace PSAPSR3 dropped successfully

BR0280I BRSPACE time stamp: 2011-12-30 16.20.33

BR0301W SQL error -980 at location BrsDblogWrite-2, SQL statement:

'INSERT INTO SAP_SDBAD (BEG, FUNCT, SYSID, POS, LINE) VALUES ('20111230160204', 'tsd', 'PDR', '0001', '20111230162033A PSAPSR3 8 15940')'

ORA-00980: synonym translation is no longer valid

BR0325W Writing to database log failed

BR0480I Directory /oracle/PDR1/sapdata3/sr3_7 deleted

BR0480I Directory /oracle/PDR/sapdata3/sr3_8 deleted

BR0280I BRSPACE time stamp: 2011-12-30 16.20.33

BR0301W SQL error -942 at location BrTspInfoDelete-3, SQL statement:

'PREPARE stmt_20 STATEMENT FROM'

'SELECT NVL(TABART, ' ') FROM "SAPSR3".TAORA WHERE TABSPACE = 'PSAPSR3''

ORA-00942: table or view does not exist

BR1067W Deleting of table data class 'UNKNOWN' failed for tablespace PSAPSR3 of owner SAPSR3

BR0280I BRSPACE time stamp: 2011-12-30 16.20.33

After this i had ran the tbimport phase where i had got the follwoing error

brspace -u / -f tbimport

BR1001I BRSPACE 7.10 (42)

BR1002I Start of BRSPACE processing: sehoasix.tbi 2011-12-30 16.29.59

BR0484I BRSPACE log file: /oracle/PDR/sapreorg/sehoasix.tbi

BR0925I Public synonym SAP_SDBAH created successfully for table SAPSR3.SDBAH

BR0925I Public synonym SAP_SDBAD created successfully for table SAPSR3.SDBAD

BR0925I Public synonym SAP_DBSTATC created successfully for table SAPSR3.DBSTATC

BR0925I Public synonym SAP_DBSTATTORA created successfully for table SAPSR3.DBSTATTORA

BR0925I Public synonym SAP_DBSTATIORA created successfully for table SAPSR3.DBSTATIORA

BR0925I Public synonym SAP_DBSTATHORA created successfully for table SAPSR3.DBSTATHORA

BR0925I Public synonym SAP_DBSTAIHORA created successfully for table SAPSR3.DBSTAIHORA

BR0925I Public synonym SAP_DBCHECKORA created successfully for table SAPSR3.DBCHECKORA

BR0925I Public synonym SAP_DBMSGORA created successfully for table SAPSR3.DBMSGORA

BR1304E Checking SAP license failed at location BrLicCheck-103

BR0602E No valid SAP license found - please contact SAP

BR0700E Fatal errors occurred - terminating processing...

BR0280I BRSPACE time stamp: 2011-12-30 16.30.01

BR0301W SQL error -980 at location BrsDblogOpen-1, SQL statement:

'INSERT INTO SAP_SDBAH (BEG, FUNCT, SYSID, OBJ, RC, ENDE, ACTID, LINE) VALUES ('20111230162959', 'tbi', 'PDR', ' ', '9999', ' ', 'sehoasix', '7.10 (42)')'

ORA-00980: synonym translation is no longer valid

BR0324W Insertion of database log header failed

BR1008I End of BRSPACE processing: sehoasix.tbi 2011-12-30 16.30.01

BR0280I BRSPACE time stamp: 2011-12-30 16.30.01

BR1007I BRSPACE terminated with errors

Please suggest what is the issue here

Regards

Bala

[former_member189725]

As an workaround , drop the tablespace using the sql

drop tablespace <Tablespace_name> including contents and datafiles;

This would avoid updating the TAORA table.

Carry out the other steps as usual.

Also check if the license in the system is valid.

[former_member189725]

Can you check if the tables starting with DD (which are repository tables) are in tablespace PSAPSR3701 or PSAPSR3?

These tables DD* should ideally be the release specific table PSAPSR3701.

If you find inconsistency , please refer Note 778784 - Inconsistencies between data class and database container.

Or if the tables are actually in SAPSR3 , move them to PSAPSR3701. You can use the system without any issues but any subsequent upgrade(both EHP and version) will fail.

Brspace does adjust the TABARTS in DD09L . refer to this link on further info .

[http://www.saptechies.com/faq-reorganizations/]

[Former Member]

1-3. Maybe these tables were sitting in the old PSAPSR3 tablespace instead of PSAPSR3701 before the reorg.

4. PLAN_TABLE gets automatically re-created from various transactions like for example ST05. You should not worry to much if it has that long column again.

Cheers Michael