Monday 16 January 2012

ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format

ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format

Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly.

Action: Investigate the internal error; may have to reload the Version 7 database (from backup) and shutdown the database cleanly.

ORA-01591: lock held by in-doubt distributed transaction string

ORA-01591: lock held by in-doubt distributed transaction string

Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state.

Action: DBA should query the pending_trans$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, DBA should contact DBA at commit point if known or end user for correct outcome, or use heuristic default if given to issue a heuristic commit or abort command to finalize the local portion of the distributed transaction.

ORA-01590: number of segment free list (string) exceeds maximum of string

ORA-01590: number of segment free list (string) exceeds maximum of string

Cause: storage parameter FREELIST GROUPS is too large.

Action: Reduce storage parameters FREELIST GROUPS

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.

Action: Specify the appropriate option.

ORA-01588: must use RESETLOGS option for database open

ORA-01588: must use RESETLOGS option for database open

Cause: An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup, or a FLASHBACK DATABASE was done.

Action: Use the RESETLOGS option when opening the database.

ORA-01586: database must be mounted EXCLUSIVE and not open for this operation

ORA-01586: database must be mounted EXCLUSIVE and not open for this operation

Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE.

Action: Mount the database in EXCLUSIVE mode.

ORA-01585: error identifying backup file string

ORA-01585: error identifying backup file string

Cause: An operating system error occurred when attempting to identify the file to be used for control file backup.

Action: Check the error stack for more detailed information

ORA-01584: unable to get file size of control file to be backed up

ORA-01584: unable to get file size of control file to be backed up

Cause: An operating system error occurred while attempting to get the file size of a control file for backup.

Action: Check the error stack for more detailed information

ORA-01583: unable to get block size of control file to be backed up

ORA-01583: unable to get block size of control file to be backed up

Cause: An operating system error occurred while attempting to get the block size of a control file for backup.

Action: Check the error stack for more detailed information

ORA-01582: unable to open control file for backup

ORA-01582: unable to open control file for backup

Cause: An operating system error occurred while attempting to open a control file for backup.

Action: Check the error stack for more detailed information

ORA-01581: attempt to use rollback segment (string) new extent (string) which is being allocated

ORA-01581: attempt to use rollback segment (string) new extent (string) which is being allocated

Cause: Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated.

Action: The rollback segment extending will be rollbacked by the system, no more extension will be possible untill the next extent is freed up by rolling back or committing other transactions.

ORA-01580: error creating control backup file string

ORA-01580: error creating control backup file string

Cause: An operating system error occurred while attempting to create a control file backup.

Action: Check the error stack for more detailed information

ORA-01579: write error occurred during recovery

ORA-01579: write error occurred during recovery

Cause: A write error occurred during recovery

Action: Consult trace files for the nature of the write error, and correct error.

ORA-01578: ORACLE data block corrupted (file # string, block # string)

ORA-01578: ORACLE data block corrupted (file # string, block # string)

Cause: The data block indicated was corrupted, mostly due to software errors.

Action: Try to restore the segment containing the block indicated. This may involve dropping the segment and recreating it. If there is a trace file, report the errors in it to your ORACLE representative.

ORA-01577: cannot add log file string - file already part of database

ORA-01577: cannot add log file string - file already part of database

Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database.

Action: Use a different file name.

ORA-01576: The instance string is not enabled

ORA-01576: The instance string is not enabled

Cause: The thread associated with instance is not enabled.

Action: Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command.

ORA-01575: timeout waiting for space management resource

ORA-01575: timeout waiting for space management resource

Cause: failed to acquire necessary resource to do space management.

Action: Retry the operation.

ORA-01574: maximum number of concurrent transactions exceeded

ORA-01574: maximum number of concurrent transactions exceeded

Cause: the limit on the number of concurrent transactions has been hit

Action: shutdown the system, increase the INIT.ORA parameter transactions , and then restart the system.

ORA-01573: shutting down instance, no further change allowed

ORA-01573: shutting down instance, no further change allowed

Cause: Some process tries to make changes while the db is being shutdown

Action: None

ORA-01572: rollback segment string cannot be brought online, string extents exceeded

ORA-01572: rollback segment string cannot be brought online, string extents exceeded

Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.

Action: Drop and recreate the rollback segment.

ORA-01571: redo version string incompatible with ORACLE version string

ORA-01571: redo version string incompatible with ORACLE version string

Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.

Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.

ORA-01570: MINEXTENTS must be no larger than the string extents currently allocated

ORA-01570: MINEXTENTS must be no larger than the string extents currently allocated

Cause: The number of extents allocated is smaller than the MINEXTENTS specified.

Action: Specify a smaller MINEXTENTS value.

ORA-01569: data file too small for system dictionary tables

ORA-01569: data file too small for system dictionary tables

Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables.

Action: Recreate the database by specifying a larger file or more files.

ORA-01568: cannot set space quota on PUBLIC

ORA-01568: cannot set space quota on PUBLIC

Cause: Trying to set space quota on a tablespace for PUBLIC.

Action: If trying to grant system-wide or tablespace-wide space priviledges to all users, use GRANT RESOURCE (ON lamp;lt;lamp;nbsp;tablespacelamp;gt;( TO PUBLIC.

ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string)

ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string)

Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread.

Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.

ORA-01566: file specified more than once in ALTER DATABASE

ORA-01566: file specified more than once in ALTER DATABASE

Cause: The list of files supplied to the command contained at least one duplicate.

Action: Remove the duplicate file specification and retry.

ORA-01565: error in identifying file string

ORA-01565: error in identifying file string

Cause: An error occurred while trying to identify a file.

Action: Check the error stack for detailed information.

ORA-01564: rollback segment is not PUBLIC

ORA-01564: rollback segment is not PUBLIC

Cause: The rollback segment segment identified is not public

Action: Do not use the keyword PUBLIC when identifying private rollback segment

ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC

ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC

Cause: Did not use the keyword PUBLIC to identified public rollback segment

Action: Use the keyword PUBLIC when identifying public rollback segment

ORA-01562: failed to extend rollback segment number string

ORA-01562: failed to extend rollback segment number string

Cause: Failure occurred when trying to extend rollback segment

Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command to take the rollback segment offline.

ORA-01561: failed to remove all objects in the tablespace specified

ORA-01561: failed to remove all objects in the tablespace specified

Cause: Failed to remove all objects when dropping a tablespace

Action: Retry the drop tablespace until all objects are dropped

ORA-01560: LIKE pattern contains partial or illegal character

ORA-01560: LIKE pattern contains partial or illegal character

Cause: like pattern is not formed correctly

Action: make sure like pattern is specified correctly

ORA-01559: MAXEXTENTS for rollback segment must be greater than 1

ORA-01559: MAXEXTENTS for rollback segment must be greater than 1

Cause: Specified MAXEXTENTS of less than 2 for rollback segment

Action: Specify larger MAXEXTENTS

ORA-01558: out of transaction ID s in rollback segment string

ORA-01558: out of transaction ID s in rollback segment string

Cause: All the available transaction id s have been used

Action: Shutdown the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction id s.

ORA-01557: rollback segment extents must be at least string blocks

ORA-01557: rollback segment extents must be at least string blocks

Cause: Specified extent of less than minimum size for rollback segment

Action: Specify larger extents

ORA-01556: MINEXTENTS for rollback segment must be greater than 1

ORA-01556: MINEXTENTS for rollback segment must be greater than 1

Cause: Specified MINEXTENTS of less than 2 for rollback segment

Action: Specify larger MINEXTENTS

ORA-01555: snapshot too old: rollback segment number string with name string too small

ORA-01555: snapshot too old: rollback segment number string with name string too small

Cause: rollback records needed by a reader for consistent read are overwritten by other writers

Action: If in Automatic Undo Management mode, increase undo_retention setting. Otherwise, use larger rollback segments

ORA-01554: out of transaction slots in transaction tables

ORA-01554: out of transaction slots in transaction tables

Cause: Too many concurrent transactions

Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again

ORA-01553: MAXEXTENTS must be no smaller than the string extents currently allocated

ORA-01553: MAXEXTENTS must be no smaller than the string extents currently allocated

Cause: The number of extents allocated is greater than the MAXEXTENTS specified.

Action: Specify a larger MAXEXTENTS value.

ORA-01552: cannot use system rollback segment for non-system tablespace string

ORA-01552: cannot use system rollback segment for non-system tablespace string

Cause: Tried to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.

Action: Create one or more private or public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. If the non-system tablespace has AUTO segment space management, then create an undo tablespace.

ORA-01551: extended rollback segment, pinned blocks released

ORA-01551: extended rollback segment, pinned blocks released

Cause: Doing recursive extent of rollback segment, trapped internally by the system

Action: None

ORA-01550: cannot drop system tablespace

ORA-01550: cannot drop system tablespace

Cause: Tried to drop system tablespace

Action: None

ORA-01549: tablespace not empty, use INCLUDING CONTENTS option

ORA-01549: tablespace not empty, use INCLUDING CONTENTS option

Cause: Tried to drop a non-empty tablespace

Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option

ORA-01548: active rollback segment string found, terminate dropping tablespace

ORA-01548: active rollback segment string found, terminate dropping tablespace

Cause: Tried to drop a tablespace that contains active rollback segment(s)

Action: Shutdown instances that use the active rollback segments in the tablespace and then drop the tablespace

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

Cause: Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.

Action: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.

ORA-01546: tablespace contains active rollback segment string

ORA-01546: tablespace contains active rollback segment string

Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read only

Action: Shutdown instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only

ORA-01545: rollback segment string specified not available

ORA-01545: rollback segment string specified not available

Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.

Action: Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). 5) Remove the name from the _ corrupted_rollback_segments parameter.

ORA-01544: cannot drop system rollback segment

ORA-01544: cannot drop system rollback segment

Cause: Tried to drop system rollback segment

Action: None

ORA-01543: tablespace string already exists

ORA-01543: tablespace string already exists

Cause: Tried to create a tablespace which already exists

Action: Use a different name for the new tablespace

ORA-01542: tablespace string is offline, cannot allocate space in it

ORA-01542: tablespace string is offline, cannot allocate space in it

Cause: Tried to allocate space in an offline tablespace

Action: Bring the tablespace online or create the object in other tablespace

ORA-01541: system tablespace cannot be brought offline; shut down if necessary

ORA-01541: system tablespace cannot be brought offline; shut down if necessary

Cause: Tried to bring system tablespace offline

Action: Shutdown if necessary to do recovery

ORA-01540: tablespace string is not offline

ORA-01540: tablespace string is not offline

Cause: Failed to bring a tablespace online because it is not offline

Action: Check the status of the tablespace

ORA-01539: tablespace string is not online

ORA-01539: tablespace string is not online

Cause: Failed to either make a tablespace read only or offline because it is not online. A tblespace must be online before it can become read only or offline normal.

Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read only.

ORA-01538: failed to acquire any rollback segment

ORA-01538: failed to acquire any rollback segment

Cause: Failed to acquire any rollback segment during startup in shared mode

Action: Startup in exclusive mode to create one more public segment or specify available private segments in the INIT.ORA parameter rollback_segments_ required, then startup in shared mode

ORA-01537: cannot add file string - file already part of database

ORA-01537: cannot add file string - file already part of database

Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database.

Action: Use a different file name.

ORA-01536: space quota exceeded for tablespace string

ORA-01536: space quota exceeded for tablespace string

Cause: The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.

Action: Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner.

ORA-01535: rollback segment string already exists

ORA-01535: rollback segment string already exists

Cause: Specified rollback segment already exists.

Action: Use a different name.

ORA-01534: rollback segment string doesn t exist

ORA-01534: rollback segment string doesn t exist

Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.

Action: Use the correct rollback segment name.

ORA-01533: cannot rename file string ; file does not belong to tablespace

ORA-01533: cannot rename file string ; file does not belong to tablespace

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.

Action: Specify the correct file name or the correct tablespace name.

ORA-01532: cannot create database; instance being started elsewhere

ORA-01532: cannot create database; instance being started elsewhere

Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance.

Action: Make sure no one else is simultaneously altering the instance. If no one is, contact your customer support representative; otherwise, retry the operation.