system copy - load into newly created tablespaces

[martin_juen2]

Hi,

we want to migrate our databases to exadata. at the moment we are using standard tablespace layout. we are asking ourselves if there is a possibility to load the biggest tables into new customer defined tablespaces when importing data into the new database (during the systemcopy load process).

maybe there is a possibility to edit a config file of the export and change the tablespacename to a new one.

thanks,

martin

[HuseyinBilgen]

Hi,

Sure it is possible.

TAORA keeps the information of Tablespace for each TABART (Table Data Class).

IAORA doest it for the indices.

DD09L keeps the Table & TABART & TABKAT (Size category) information.

R3LDCTL extracts the corresponding TABART and size category (TABKAT) for each table from table DD09L of the ABAP Dictionary. This information is written to the *.STR files.

Creating New TABARTs

If tables have been moved to customer-defined database storage units (that is, tablespaces) in the source database, during a migration, these tables are only reloaded into the correct storage units when tables DARTT, DDART, TS<DBS>, IA<DBS>, TA<DBS>, and DD09L have been maintained correctly.

The technical configuration of all tables (stored in DD09L) must include the correct TABART. After the tables have been unloaded, the files “DDL<Target DBS>.TPL” and “DDL<Source DBS>.TPL”  should contain the customer-specific TABART and database storage unit names.

A fast check can be performed by calling R3LDCTL without parameters. R3LDCTL generates the files “SAP<TABART>.STR” and “DDL<DBS>.TPL” in the current directory. Duration: some minutes.

See SAP Note 46272 Implement new data class in technical settings.