|
Index >
ORACLE Server Parameters >
rollback_segments
rollback_segments
Oracle 10.0.1:
| Paramter Name: | rollback_segments
| | Description: | undo segment list
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 9.2.0:
| Paramter Name: | rollback_segments
| | Description: | undo segment list
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.1.7:
| Paramter Name: | rollback_segments
| | Description: | undo segment list
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.0.6:
| Paramter Name: | rollback_segments
| | Description: | undo segment list
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 7.3.4:
| Paramter Name: | rollback_segments
| | Description: | undo segment list
| | Type: | CHAR
| Obsoleted: | FALSE
| | Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Related Error Messages:
ORA-01545: rollback segment '%s' specified not availableCause: 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-01552: cannot use system rollback segment for non-system tablespace '%s' 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/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-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
This parameter is documented in the
Oracle Server Reference Guide.
Search for more info about
[ rollback_segments ]
on the Oracle FAQ.
| 
