Loss or damage processing method for oracle rollback segment table space data file (1)

Problem Description: This is a losing segment table space data file lost or corrupted scenario, and Oracle cannot identify the corresponding data file. ORA-1157, ORA-1110 will be reported when you try to startup data files, and may be accompanied by errors that identify operating system levels, such as ORA-7360. When you try to turn off the database in Shutdown Normal or Shutdown Immediate mode, it will be guided to ORA-1116, ORA-1110, and may be accompanied by errors that identify operating system levels, such as ORA-7368, sometimes in the normal Shutdown database. SHUTDOWN.

WARNING: The steps mentioned in the article are for Oracle's global technical support. In particular, the _corrupted_rollback_segments parameter in step 6 is required, and the database needs to be rebuilt, and all other options are observed before using this participation.

Solution explanation:

The following solution is taken in the status of the database when the detection problem occurs:

I. The database is in turn off. Try to open the Database Time ORA-1157 and ORA-1110 errors, the solution is taken in the database is normal Shutdown (using the Normal or Immediate option.

I.a. Database is normal Shutdown

If the data database is normal Shutdown, the easiest solution is to delete lost or corrupted data files with the Offline DROP option, and the Rock scroll space to which the data file belongs is deleted and rebuilt by the RESTRICETED mode. If the database is shipped with ShutDown Abort or crashes yourself, don't follow this process.

Proceed as follows:

1. Verify that the database is normal Shutdown. You can check this file for ALTER.LOG, locate if you can see if you can see the following information: "Alter Database Dismbount"

This, of course, also includes the condition of SHUTDOWN in normal way, attempting to start the database. If you are close to the shutdown abort, you are shut down the database or the database is your own CRASHED, you apply the following I.B method.

2. Remove the rollback segment belonging to the lost data file from the ROLLBACK_SEGMENTS parameter in INIT . OA. If you can't be confident, you can simply comment on the parameter of Rollback_SEGMENTS.

3. That data file that is lost or corrupted by the RESTRICTED MOUNT database Startup Restrict Mount; 4, Offline DROP. Alter Database DataFile '' Offline DROP; 5, open the database ALTER DATABASE Open; if you return to "Statement Processed", go to step 7. If you get ORA-604, ORA-376, and ORA-1110 error Go to step 6.

6, because the database failed, shutdown off the database and edits the INT . OA file. Note This parameter is removed, and in the init . Ota file is added as follows: _Corrupted_rollback_segments = (, ..., ) This parameter should contain all the rollback segments in Rollback_SEGMENTS.

It should be noted that this parameter can only be used under the specified situation or under the guidance of Oracle's global persistent support, then open the database in a restrical mode:

STARTUP RESTRICT 7, delete the rollback segment table space you belong to that file. Drop tablespace Including Contents; 8, rebuilding the split grouse table space and rollback segments, after the creation, make them online.9, making the database all users available. ALTER System Disable Restricted Session;

10. Inin init . Otrase, you recreate the rollback segment, if you use step 6 to remove the corrupted_rollback_segments this parameter.

I.b. Database is not normal Shutdown

In this case, the database has been closed with Shutdown Abort or CraShed, and there must be an active transaction in the rollback segment. Therefore, the bad data file cannot be offline (offline) or DROP, you must restore this file from backup. If the data is in non-archive mode, only the recent transaction log has not been rewritten, you can successfully restore this file. If the backup of this file is also invalid, contact Oracle's technical support.

Proceed as follows:

1. Restore the lost data file from the backup.

2, MOUNT on the database

3, execute the following query: SELECT FILE #, Name, Status from v $ datafile; if the status of the data file is OFFLINE, you must first take it online: Alter Database DataFile '' Online; 4, executing Query:

Select v1.group #, member, sequence #, first_change # from v $ log v1, v $ logfile v2 where v1.group # = v2.group #; this will list all online redo logs and their serial number and First change number. 5. If this database is non-archive mode, execute the following query: SELECT FILE #, Change # from V $ Recover_File; if the CHANG # is the smallest first first_change # big in 4 If you use the online log to complete the recovery. 6. If chang # is smaller than the minimum first_change # in 4, the database cannot be recovered, you can contact Oracle's technical support.

Translator insert: If you are really non-archived mode and the backup of this file is also invalid, if you think that you can lose the transaction in the roll, you can use the method from step 6 in the IA, you can open the database, You should be a backup immediately because the data in the library is somewhat inconsistent.

Recover datafile ''

7. Confirm that all logs are recovered, only to "Media Recovery Complete" information.

8, open the database

to be continued