ORA-01599 Error Resolution

Error | Troubleshoot symptoms:
The database could not be started or the cluster system could not switch. View database log Files $oracle_base/admin
Orcl/bdump/alert_orcl.log has similar ora-01599:failed to acquire rollback
Segment (in), Cache space is full (currently has () entries) Error 1599
happened during DB Open, shutting down database for similar error messages.


Failure Analysis:
Orale There is an initialization parameter max_rollback_segments it represents a rollback segment that can be online at the same time
Number of. Its default value is Max (30,transactions/transactions_per_rollback_segment)
。 Number of rollback segments specified in initialization parameters (via rollback_segments parameter) or default online
The database will not start after max_rollback_segments this parameter. This error is often caused by the user
The rollback_segments parameter was modified only after the rollback segment was added but not modified Max_rollback_se
caused by the gments parameter. Or the user adds a public rollback segment, and the Max is commented out in the initialization parameter
_rollback_segments parameters can also cause this problem.

Fault handling:
You can modify the max_rollback_segments in the Oracle initialization parameter to be larger than the current rollback segment
Total after the database can be reset. If you do not know how many rollback segments are currently in place, you can set this value first
Try again to restart the database for 100. If you also report the same error, increase the value until successful. When the data
The library can be started with the select COUNT (*) from Dba_rollback_segs to get the exact back
Roll the number of segments before you modify the initialization parameters.

Daily Maintenance:
Note the max_rollback_segments and rollback_segments parameters when increasing the rollback segment
The interaction between the two, preferably at the same time on two nodes see.