Oracle version: 18.104.22.168
I have the following error: "Transaction recovery: lock conflict caught and ignored"
I can't upgrade my database now.
I had a RAC. Removed one node, but the undo tablesapce of the removed node left. Because it contained active rollback segments.
Now I want to drop this undo tablespace manually.
I want to mention that, I tried to offline this undo tablesapce and some SQL-s were returning the error message:
ORA-00376: file string cannot be read at this time
When I made the undo tablespace online then SQLs were returning results successfully.
I found Burleson's post about "Repair UNDO log corruption" and decided to follow these steps.
status = 'NEEDS RECOVERY';
Return 0 rows
Segments in UNDOTBS2 tablespace has OFFLINE and PARTLY AVAILABLE statuses.
- Bounce the instance with the hidden parameter “_offline_rollback_segments”, specifying the segment names in UNDOTBS2:
- Bounce database, nuke the corrupt segment and tablespace:
SQL> drop rollback segment "_SYSSMU22$";
SQL > drop tablespace undotbs2 including contents and datafiles;
I wander to know what problems can I encounter If I delete these rollback segments manually?