oracle7天前的数据怎么恢复,如何把Oracle数据库恢复到2天前的状态？ - Oracle数据库管理 - Oracle数据库数据恢复、性能优化来问问AskMaclean - Parnassus...

OERR: ORA-353 "log corruption near block %s change %s time %s" Reference Note

PURPOSE

This is a brief reference note to show the meaning of database error "ORA-353". It includes the error text, "Cause" and "Action" from message files for each database version from 9.2 onwards, along with search links and details of any database bug issues related to the error.

SCOPE

This note is intended for general audience as a starting point to check the meaning of "ORA-353". It does not give detailed information about the error and does not give error message text for versions below 9.2 .

DETAILS

Error Text, Cause and Action from Message File/s for ORA-00353

Versions 9.2, 10.1, 10.2, 11.1, 11.2, 12.1

Error:  ORA-00353 log corruption near block %s change %s time %s

---------------------------------------------------------------------------

Cause:  Some type of redo log corruption has been discovered. This error

describes the location of the corruption. Accompanying errors describe

the type of corruption.

Action: Do recovery with a good version of the log or do incomplete recovery

up to the indicated change or time.

Search Links for ORA-00353

The links below can be used to locate ORA-353 in the documentation, and to search for documents that give more information about the error.

Search MOS for "ORA-00353 Troubleshooting"

Search 12.1 documentation for ORA-00353

Search 11.2 documentation for ORA-00353

Search 11.1 documentation for ORA-00353

Search 10.2 documentation for ORA-00353

Database Bugs Related to ORA-00353

Errors are usually due to usage, application or configuration issues but in some cases they may be caused by a bug issue. This section lists any database bugs that have been linked to error "ORA-353" .

You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

10.2.0.2 10.2.0.3 10.2.0.4 11.1.0.6 11.1.0.7 11.2.0.1 11.2.0.2 11.2.0.3 12.2.0.1 Show all Bugs

NB        Prob        Bug        Fixed        Description

II        14533497        11.2.0.4, 12.1.0.1        ORA-353 Redo Log Corruption messages from ASYNC Redo Shipping or Log Miner

III        13840711        11.2.0.3.14, 11.2.0.3.BP27, 11.2.0.4, 12.1.0.1        ORA-353 in Standby / Streams Data Capture or ORA-272 in PRIMARY: Redo log corruption by ASYNC redo shipping

I        9549707        11.2.0.2, 12.1.0.1        11g with COMPATIBLE=10.2 produces redo which is not 10.2 compatible (ORA-399)

II        9098116        10.2.0.5, 11.2.0.2, 12.1.0.1        ORA-368 ORA-353 in Standby for incomplete archive log when max_connections > 1

*        III        8768374        10.2.0.5, 11.1.0.7.8, 11.2.0.1.BP11, 11.2.0.2, 12.1.0.1        RFS in Standby with a wrong location for archived log corrupting/overwriting database files when max_connections > 1

I        13357662        11.2.0.2        ORA-353 ORA-354 Redo corruption by Archive although Dump Logfile is sucessfully done

II        6039415        10.2.0.4, 11.1.0.7, 11.2.0.1        ORA-355 can occur during real time apply

*        -        3806172        10.1.0.4, 10.2.0.1        Logical standby apply may stop with ORA-355 / ORA-353

*        -        554516        7.3.4.1        Silently corrupt ARCH logs using Async IO