Oracle Error Case: ORA-00235

ORA-00235 controlfile Fixed table inconsistent due to concurrent update

ORA-00235 Control file fixed table inconsistent due to concurrent update

Cause Concurrent update activity in a control file caused a query on a control file fixed table to read inconsistent infor Mation.

Action Retry the operation.

Case one: Use Rman Level 0 Hot Backup Program

We are using the Rman level 0 Hot Backup program. 0-level backups are always faulted when processing errors related to "ORA-00235: Control file fixed tables due to concurrent updates causing inconsistencies". We are not using the recovery directory. We have added the redo log so that the checkpoint occurs after 8-10 minutes. The problem still floats on the surface. Do you have any suggestions on how to prevent this problem from being used in our normal database?

I've met the same thing. Unfortunately, even Oracle's Web site has no information about the problem. In the case I encountered, I found that I was performing a backup and that an automatic task would periodically synchronize the restore directory or perform some other rman operation. All of these Rman operations update the control files, whether or not you use the recovery directory. So, make sure that this is the only thing that Rman is dealing with.

If you receive a ORA-235 error, your database is not affected, but your Rman backup failed. You can restart the backup, then everything will be fine.

Case TWO: TSM backup error

Please ask me to do backup. SH is reported the following error:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06003: ORACLE error from target database: ORA-00235: controlfile fixed table inconsistent due to concurrent update
RMAN-06097: text of failing SQL statement: select device ,node from x$krbaff where fno=:b1
RMAN-06099: error occurred in source file: krmk.pc, line: 4869
　　Recovery Manager complete.

Looks like you're using the Nocatalog pattern, Rman.

So for the SCN to be taken from the mirror of Contolfile, but this time met the ckpt, such as the process of contolfile, such as the head of the file to write, consistency is not guaranteed, so the error

Suggestions

1, using Rman catalog server

2, do not use catalog server when the business is not busy for Rman