Resolving ORA-600[3020] Raised During Recovery (Doc ID 361172.1)
Information in this document applies to any platform.
SYMPTOMS
Recovery session fails:
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [13204236], [1], [1],
[33082], [236], [], []
ORA-10567: Redo is inconsistent with data block (file# 3, block# 621324)
ORA-10564: tablespace DATA
ORA-01110: data file 3: '
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 25535
CAUSE
This is stuck recovery - redo cannot be applied to a block because the scn of the block, when
read from disk is NOT the scn that we expect it to be.
SOLUTION
If the affected file belongs to SYSTEM or UNDO tablespace you should restore the database from backup and do point in time recovery to just before the problem log is applied.
If you do not have a backup available, than the options are VERY limited. Please open a Service Request with Oracle Support Services for assistance on this.
If the affected file belongs to SYSAUX, this is the ONLY file affected and it is offline then a better option than point in time recovery of the whole database would be to create a NEW database and then use Transportable Tablespace feature to plug in all other tablespaces. Another point worth noting: if SYSAUX is ONLINE but contains corrupt blocks, then before considering restore and recovery, use the SQL in point 3 below to identify the affected object and raise a call with Oracle Support Services to ask if it is possible to drop and recreate the object (unpublished Note 333665.1).
For Data Guard environments, refer to Note:1265884.1
Otherwise:
1. Use Trial Recovery to determine the extent of the problem:
This will tell you how many blocks (n) would be left corrupted after recovery - check the alert
log for details of the blocks affected. If there are a large number of corruptions reported you may decide to restore from backup and issue point in time recovery. However, if only a few blocks are reported as corrupt you could proceed with recovery :
2. Skip the corrupted block(s)
Do this
This will allow recovery to continue, 'skipping' the blocks that cannot be recovered and leaving them marked as 'corrupt' after which the database can be opened.
3. Take the corrupt blocks reported in the alert log and for each, identify the object that the block belongs to::
FROM dba_extents
WHERE file_id =
and
Replacing
For each object identified - take steps to resolve the corruption:
- if it belongs to an index then simply drop and recreate the index
- if it belong to a user object then consider recreating the object or extracting what you can from the object; if necessary raise a Service Request with Oracle and request assistance with extracting data from a corrupt object.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/15747463/viewspace-769595/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Stuck recovery of database ORA-00600[3020] (Doc ID 283269.1)Database
- Backup and Recovery Scenarios (Doc ID 94114.1)iOS
- RAC Instance Crash with ORA-600: [Kjbmprlst:Shadow] (Doc ID 740028.1)
- ORA-600 [kcblasm_1] In 10.2.0.5. (Doc ID 1133845.1)ASM
- RMAN : Consistent Backup, Restore and Recovery using RMAN (Doc ID 162855.1)REST
- Rust Reference Cycles: Resolving and Avoiding themRust
- 修改vip (Doc ID 276434.1)
- HANGFG User Guide (Doc ID 362094.1)GUIIDE
- How to Prepare Storage for ASM (Doc ID 452924.1)ASM
- 【recovery】android使用串列埠列印recovery除錯日誌Android串列埠除錯
- ServeRAID disk drive error recoveryServerAIError
- ORA-600(kjxgrdecidemem1)錯誤IDE
- ORA-600(kfioUnidentify01)錯誤IDE
- Error IMP-32 Obtained During Import (文件 ID 846397.1)ErrorAIImport
- Best Practices for failover during server failures [ID 1323472.1]AIServer
- Android開發簡單教程.docAndroid
- SQLT Diagnostic Tool (Doc ID 215187.1)SQL
- Oracle Text Health Check (Doc ID 823649.1)Oracle
- The DBMS_SUPPORT Package (Doc ID 62294.1)Package
- DBMS_REPAIR example (Doc ID 68013.1)AI
- Overview of Parameter Reference Notes (Doc ID 68462.1)View
- Linux OS Service 'ntpd' (Doc ID 551704.1)Linux
- Listener Hanging -Get For Resolving or Troubleshooting [ID 230156.1]
- ORA-600 [13011] on Delete [ID 456361.1]delete
- ORA-600(kkoipt:invalid join method)錯誤
- sysman.emcp.agent.AgentPlugIn raised by the Agent CA-740628.1PluginAI
- Oracle 最新PSU (Doc ID 2118136.2)Oracle
- * Master Note: Database Performance Overview (Doc ID 402983.1)ASTDatabaseORMView
- HP-UX: Asynchronous i/o (Doc ID 139272.1)UX
- Troubleshooting Database Hang Issues (Doc ID 1378583.1)Database
- No Response from the Server, Does it Hang or Spin? (Doc ID 68738.1)Server
- Common Diagnostic Scripts for AUM problems (Doc ID 746173.1)
- How to Duplicate a Database in NOARCHIVELOG mode (Doc ID 275480.1)DatabaseHive
- Remote Diagnostic Agent (RDA) - RAC Cluster Guide (Doc ID 359395.1)REMGUIIDE
- Troubleshoot Grid Infrastructure Startup Issues (Doc ID 1050908.1)ASTStruct
- ORA-600 [4553] Being Hit [ID 1243704.1]
- 使用Recovery ID恢復密碼(ZT)密碼
- SERVICE_NAME Parameter - Resolving The ORA-12514 Error [ID 77640.1]Error