Recovery: Index Tablespace Missing
Generally, Oracle treats an index tablespace just like a user tablespace. You can therefore apply the recovery procedure for a user tablespace as described above. An additional recovery option also exists for SAP databases, however; it is described below.
Recovery Procedure
Use the following SQLPLUS command to shut down the database:
shutdown abort
Find out which data file is affected by the media error, using the information in the ALERT and trace files and/or the Check function from the SAPDBA recovery menu.
Mount the database. Enter the following SQLPLUS commands:
connect internal
startup mount
Set the data files to OFFLINE with:
alter database datafile '<complete file name>' offline;
Open the database with:
alter database open;
First make sure that the index tablespaces do not contain any tables (you can check this using the Oracle tables DBA_SEGMENTS and DBA_TABLES).
Use the corresponding SAPDBA function to export the affected index tablespace (Export of table and index definitions with options Compress extents: no, Use SAP DDIC for NEXT: no, Reduce object size: no, Change storage manually: no).
Determine the default storage parameters that apply to this tablespace by examining Oracle table DBA_TABLESPACES. Write down these values.
Enter the following SQLPLUS commands to delete the index tablespace and create it again:
alter tablespace <tablespace name> offline;
drop tablespace <tablespace name> including contents;
Delete the files belonging to the tablespace at operating system level, if any still exist.
create tablespace <tablespace name>
datafile '<complete file name>' size <n>M
default storage (<storage parameters>);
For more information on these Oracle commands, see the Oracle documentation.
Use the SAPDBA import functionality to import the indexes (script ind<TSP>.sql). The recovery of the index tablespace is complete.