RMAN Validate

Hi
I need some help on deciding the best course of action.
Database: Oracle 11.2 standard Edition.
OS : RHEL Linux
We currently have RMAN backups that have only 1 day retention period (Due to storage cost limitations we cannot exceed this currently).
One of our databases experienced block corruption on the sysman tablespace a couple of weeks ago.
Fortunately this was on the sysman tablespace and not on of our critical tablespaces.
Rman has the "backup validate check online" command, which as I see in the log files, backups the database and validates it for logical or physical corruption.
I want to be able to validate both physical and logical corruption, before I do a backup.
The primary reason being that , since I have retention policy set to 1 day, I will lose the good backup, if current backup with the block corruption completes.
Anyone have any suggestions how to validate for block corruption, before doing a backup?
changing the retention policy is not an option at this time.
Div

You can try
VALIDATE DATABASE ---->Validates all datafiles and controlfiles
BACKUP VALIDATE DATABASE--->RMAN reads the files to be backed up in their entirety, as it would during a real backup. It does not, however, actually produce any backup sets or image copies. If the backup validation discovers corrupt blocks, then RMAN updates the V$DATABASE_BLOCK_CORRUPTION view with rows describing the corruptions.
http://docs.oracle.com/cd/B19306_01/backup.102/b14192/bkup005.htm

Similar Messages

RMAN Validate backup from a location

Hi All,
I need to validate a set of RMAN backup files that I took to a disk say /ora_tmp.
Do I need to catalogue those files to validate or I can validate the files connecting to the target and provide a location to validate the backups.
Please let me know.
Thanks,
Chilakamarthi.

You can use the BACKUP VALIDATE command to do the following:
Check datafiles for physical and logical block corruption
Confirm that all database files exist and are in the correct locations
When you run BACKUP VALIDATE, RMAN reads the files to be backed up in their entirety, as it would during a real backup. RMAN does not, however, actually produce any backup sets or image copies.
To validate files with the BACKUP VALIDATE command:
Start RMAN and connect to a target database and recovery catalog (if used).
Run the BACKUP VALIDATE command.
For example, you can validate that all database files and archived logs can be backed up by running a command as shown in the following example. This command checks for physical corruptions only.
BACKUP VALIDATE
DATABASE
ARCHIVELOG ALL;
To check for logical corruptions in addition to physical corruptions, run the following variation of the preceding command:
BACKUP VALIDATE
CHECK LOGICAL
DATABASE
ARCHIVELOG ALL;
Hope this will help you

Validate rman backups

Hi,
oracle 9.2.0.1
rman Incremental cumalative backups
HI,
i do incremental cumalative backups. Full Level 0 on friday, level 1 incremental done Mon - Thurs.
i noticed that if i run a RESTORE DATABASE VALIDATE command, it checks/uses all the pieces that are part of the FULL LEVEL 0 only. But this does not tell me if the incremental backup pieces created are good or not.
How (without actually restoring to test server) can i test/validate up-to the latest incremental daily backup?
J

RESTORE VALIDATE will only do full backups, LEVEL 0 backups, controlfiles, spfile, datafile copies and archivelogs. However, you can VALIDATE a LEVEL 1 backupset with simply:
RMAN> VALIDATE BACKUPSET <backupset_#>;

Restore database validate ERROR

I configure RMAN yesterday with the following parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u02/rman/prod1/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/prod1/backup_db/%U' MAXPIECESIZE 2000M;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/backup/prod1/backup_db/%U' MAXPIECESIZE 2000M;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/rman/prod1/scontrolfile.ctl';
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/prod1/backup_db/%U' MAXPIECESIZE 2000M;
I performed a full backup after this and was trying to verify it this morning. But I am getting the following errors:
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "equal": expecting one of: "double-quoted-string
, identifier, newline, ;, single-quoted-string"
RMAN-01007: at line 1 column 16 file: standard input
RMAN> connect target /
connected to target database: PROD (DBID=444452)
RMAN> restore database validate;
Starting restore at 11-SEP-07
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=950 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1136 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 09/11/2007 09:59:44
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 258 found to restore
RMAN-06023: no backup or copy of datafile 257 found to restore
I listed RMAN back and my full backup is showing. Please help your sister out.

RMAN> connect target /
connected to target database: PROD (DBID=35109652)
using target database controlfile instead of recovery catalog
RMAN> report schema;
Report of database schema
File K-bytes Tablespace RB segs Datafile Name
1 523264 SYSTEM *** /dev/rprod_sys_000
2 1047552 UNDO *** /dev/rprod_und_001
3 130048 MISC *** /dev/rprod_msc_000
4 4193280 D_R_SMALL *** /dev/rdprod_0000001
5 3872768 I_R_SMALL *** /dev/riprod_0000001
6 916480 I_R_LARGE *** /dev/riprod_0000002
7 637952 D_R_LARGE *** /dev/rdprod_0000002
RMAN> backup database;
#This was successful/completed although I don’t have the output.
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size
1 Full 3G
List of Datafiles in backup set 1
File LV Type Ckp SCN Ckp Time Name
19 Full 2241992994123 10-SEP-07 /dev/rlprod_0000001
25 Full 2241992994123 10-SEP-07 /dev/rdprod_0000010
30 Full 2241992994123 10-SEP-07 /dev/riprod_0000012
31 Full 2241992994123 10-SEP-07 /dev/riprod_0000013
36 Full 2241992994123 10-SEP-07 /dev/riprod_0000015
Backup Set Copy #1 of backup set 1
Device Type Elapsed Time Completion Time Compressed Tag
DISK 00:07:20 10-SEP-07 NO TAG20070910T225622
List of Backup Pieces for backup set 1 Copy #1
BP Key Pc# Status Piece Name
1 1 AVAILABLE /backup/prod1/backup_db/0girkfgo_1_1
3 2 AVAILABLE /backup/prod1/backup_db/0girkfgo_2_1
Backup Set Copy #2 of backup set 1
Device Type Elapsed Time Completion Time Compressed Tag
DISK 00:07:20 10-SEP-07 NO TAG20070910T225622
List of Backup Pieces for backup set 1 Copy #2
BP Key Pc# Status Piece Name
2 1 AVAILABLE /backup/prod1/backup_db/0girkfgo_1_2
4 2 AVAILABLE /backup/prod1/backup_db/0girkfgo_2_2
BS Key Type LV Size
2 Full 3G
List of Datafiles in backup set 2
File LV Type Ckp SCN Ckp Time Name
4 Full 2241992994124 10-SEP-07 /dev/rdprod_0000001
8 Full 2241992994124 10-SEP-07 /dev/riprod_0000003
12 Full 2241992994124 10-SEP-07 /dev/rdprod_0000005
17 Full 2241992994124 10-SEP-07 /dev/rdprod_0000007
24 Full 2241992994124 10-SEP-07 /dev/rdprod_0000009
27 Full 2241992994124 10-SEP-07 /dev/riprod_0000011
Backup Set Copy #1 of backup set 2
Device Type Elapsed Time Completion Time Compressed Tag
DISK 00:07:37 10-SEP-07 NO TAG20070910T225622
List of Backup Pieces for backup set 2 Copy #1
BP Key Pc# Status Piece Name
5 1 AVAILABLE /backup/prod1/backup_db/0hirkfgp_1_1
7 2 AVAILABLE /backup/prod1/backup_db/0hirkfgp_2_1
Backup Set Copy #2 of backup set 2
Device Type Elapsed Time Completion Time Compressed Tag
DISK 00:07:37 10-SEP-07 NO TAG20070910T225622
List of Backup Pieces for backup set 2 Copy #2
BP Key Pc# Status Piece Name
6 1 AVAILABLE /backup/prod1/backup_db/0hirkfgp_1_2
8 2 AVAILABLE /backup/prod1/backup_db/0hirkfgp_2_2
RMAN> validate backupset 1;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=950 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=949 devtype=DISK
channel ORA_DISK_1: starting validation of datafile backupset
channel ORA_DISK_1: restored backup piece 1
piece handle=/backup/prod1/backup_db/0girkfgo_1_1 tag=TAG20070910T225622
channel ORA_DISK_1: restored backup piece 2
piece handle=/backup/prod1/backup_db/0girkfgo_2_1 tag=TAG20070910T225622
channel ORA_DISK_1: validation complete
The problem is that I can’t perform: restore database validate; or test.

Validate command syntax

Hello,
I need to validate if a database has been backed up succesfully so I want to execute rman validates command.
I checked oracle manuals and I found validates command is a parameter of restore command:
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10770/rcmsynta65.htm#86797
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10770/rcmsynta51.htm#85191
I already duplicated databases using rman, but I'm not sure about syntax for validating. Is the following code right if I want just to validate database backup?
rman rcvcat rman/rman@rman target sys/password@database auxiliary / cmdfile /home/oracle/restore_dup.sh
Where restore_dup.sh is:
run {
allocate auxiliary channel 'dev_0' type 'sbt_tape';
allocate auxiliary channel 'dev_1' type 'sbt_tape';
allocate auxiliary channel 'dev_2' type 'sbt_tape';
allocate auxiliary channel 'dev_3' type 'sbt_tape';
restore target database validates;
Note that...
- OS is HP-UX 11.00
- Database is Oracle 8.1.7
- I CANNOT recover anything as database I want to validate is a production environment.
Thanks in advance for your help.
Regards,
Carles

I never worked with RMAN 8.1.7 (only newer versions)
According the documentation you can validate only a backupset in RMAN 8.1.7:
- validate backupset <bs_number>;
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/rmansy50.htm#6148
http://download-east.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/preparer.htm#435378
The validation for the full DB in a new feature in RMAN 9i.
Bye, Aron

How to validate a manual standby

Hi all,
I am setting up a manual physical standby and I want to periodically check the standby database for physical and logical corruption.
I am not sure what is the best way to do it:
1) should I only use dbv?
2) should I open the database read only and use RMAN "validate database check logical ;" ?
3) should I open the database read only and use anlter table ... validate structure cascade ; for every table?
4) Do steps 2 and 3 do the same checks?
Thanks,
Andrea

user585511 wrote:
Hi all,
I am setting up a manual physical standby and I want to periodically check the standby database for physical and logical corruption.
I am not sure what is the best way to do it:
1) should I only use dbv?
2) should I open the database read only and use RMAN "validate database check logical ;" ?
3) should I open the database read only and use anlter table ... validate structure cascade ; for every table?
4) Do steps 2 and 3 do the same checks?May be physical corruption can occur, But logical corruption only on standby have less chances..
as always, Standby is image copy so if any logical corruption in primary you will have those in standby too..
May be due to some mount point issues (or) any other there is chance for physical corruption.
So either you can go for DBV, Even you can check by RMAN too.
Better, if you perform some tests like creating a user with tables(schema) & open standby and keep track the status. I think if you able to open and count is same. You are fine.
Another point , If any corruption in your database, MRP process will be died and no recovery will be performed, So until unless you able to perform Recover, then there is no issue at the most.+
Edited by: CKPT on May 18, 2012 4:22 PM

BACKUP VALIDATE vs VALIDATE in checking logical/physical corruption

Hello all,
I am checking if our 10gR2 database has any physical or logical corruption. I have read in some places where they state that VALIDATE command is enough to check database for physical corruption. Our database was never backed up by RMAN specifically before. Are any configuration settings needed for running BACKUP VALIDATE command? The reason I am asking is because just the VALIDATE command returns an error and BACKUP VALIDATE command runs without error but it is not showing the
"File Status Marked Corrupt Empty Blocks Blocks Examined High SCN" lines.
I used the command in two different formats and both do not show individual data file statuses:
RMAN> run {
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 10 BACKUP TYPE TO BACKUPSET;
BACKUP VALIDATE CHECK LOGICAL DATABASE FILESPERSET=10;
RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE
RMAN> VALIDATE DATABASE;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "database": expecting one of: "backupset"
RMAN-01007: at line 1 column 10 file: standard input
However on a different database already being backed up by RMAN daily, BACKUP VALIDATE output shows list of datafiles and STATUS = OK as below:
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
How can we check every individual datafile status. Appreciate your responses. Thanks.

Hi,
After you have run:
BACKUP VALIDATE CHECK LOGICAL DATABASE You can use sqlplus and run:
select * from v$database_block_corruption.The output will tell you which block in which datafile is corrupt.
Regards,
Tycho
Edited by: tychos on 8-sep-2011 18:34

VALIDATE and RESTORE VALIDATE

What are the major differences between VALIDATE DATABSAE and RESTORE DATABASE VALIDATE?
Thanks!

Hello Hemant,
Thanks for your inputs. You said there is no VALIDATE DATABASE. Here is hte test that I did -
RMAN> VALIDATE DATABASE;
Starting validate at 14-OCT-09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=139 device type=DISK
channel ORA_DISK_1: starting validation of datafile
channel ORA_DISK_1: specifying datafile(s) for validation
input datafile file number=00014 name=/oracle1/data01/TESTDB/TESTDB_compress_test_01.dbf
input datafile file number=00003 name=/oracle/TESTDB/data02/TESTDB_undo_01.dbf
input datafile file number=00004 name=/oracle/TESTDB/data01/TESTDB_users_01.dbf
input datafile file number=00002 name=/oracle/TESTDB/data01/TESTDB_sysaux_01.dbf
input datafile file number=00001 name=/oracle/TESTDB/data01/TESTDB_system_01.dbf
input datafile file number=00005 name=/oracle/TESTDB/data01/TESTDB_sysaud_tab_1m_01.dbf
input datafile file number=00013 name=/oracle/TESTDB/data01/TESTDB_roop_01.dbf
input datafile file number=00012 name=/oracle/TESTDB/data01/TESTDB_example_01.dbf
input datafile file number=00006 name=/oracle/TESTDB/data01/TESTDB_shau_01.dbf
input datafile file number=00015 name=/oracle/product/11.1/dbs/ILM_TOOLKIT_IML_TEST_TAB_A.f
channel ORA_DISK_1: validation complete, elapsed time: 00:02:30
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
1 OK 0 14512 88320 39900747
File Name: /oracle/TESTDB/data01/TESTDB_system_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 58987
Index 0 11601
Other 0 3220
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
2 OK 0 17646 93704 39900668
File Name: /oracle/TESTDB/data01/TESTDB_sysaux_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 26782
Index 0 27830
Other 0 21446
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
3 OK 0 0 509440 39900747
File Name: /oracle/TESTDB/data02/TESTDB_undo_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 0
Index 0 0
Other 0 509440
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
4 OK 0 35933 195472 39351902
File Name: /oracle/TESTDB/data01/TESTDB_users_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 127352
Index 0 31181
Other 0 1006
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
5 OK 0 760 13056 39900721
File Name: /oracle/TESTDB/data01/TESTDB_sysaud_tab_1m_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 12143
Index 0 0
Other 0 153
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
6 OK 0 403 1280 27639971
File Name: /oracle/TESTDB/data01/TESTDB_shau_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 0
Index 0 749
Other 0 128
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
12 OK 0 1579 3200 38965080
File Name: /oracle/TESTDB/data01/TESTDB_example_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 278
Index 0 316
Other 0 1027
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
13 OK 0 12636 12800 30559315
File Name: /oracle/TESTDB/data01/TESTDB_roop_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 0
Index 0 0
Other 0 164
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
14 OK 0 57371 1008224 38826365
File Name: /oracle1/data01/TESTDB/TESTDB_compress_test_01.dbf
Block Type Blocks Failing Blocks Processed
Data 0 950654
Index 0 28
Other 0 171
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
15 OK 0 237 1152 16399927
File Name: /oracle/product/11.1/dbs/ILM_TOOLKIT_IML_TEST_TAB_A.f
Block Type Blocks Failing Blocks Processed
Data 0 450
Index 0 53
Other 0 412
channel ORA_DISK_1: starting validation of datafile
channel ORA_DISK_1: specifying datafile(s) for validation
including current control file for validation
including current SPFILE in backup set
channel ORA_DISK_1: validation complete, elapsed time: 00:00:01
List of Control File and SPFILE
===============================
File Type Status Blocks Failing Blocks Examined
SPFILE OK 0 2
Control File OK 0 624
Finished validate at 14-OCT-09
*******************END********************
So, it does validate the database. In such case, how much different it is to VALIDATE a BACKUP than saying RESTORE DATABASE VALIDATE?
I want to use RESTORE DATABASE CHECK LOGICAL VALIDATE for checking the restorability of the database but I want to know what the real difference between these two are. Seems like both are doing the same work in the background.
Will be great to know your point of view.
Thanks,
Roopesh

Rman Backup time error

Today i saw this error in our production backup time .
Please let me know how to leave out from this.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/27/2011 01:13:47
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 05/27/2011 01:10:52
ORA-19566: exceeded limit of 0 corrupt blocks for file
N:\USERS01.DBF
Regs,
Brij

Also, be aware that rman: backup validate (check logical) command could not show the corrupted blocks if that block are newer used(or used before, but freed later for example). In this case, rman validate does not populate V$database_block_corruption but it also does not allows you to continue with your backup.
So the solution will be, as previous posters said, either set the limit for the sustained number of corrupted blocks or format/repair the corrupted block.
For checking the corrupted blocks you could also use db verify utility(dbv). This will definitely show you the details about corrupted blocks, even they are not used ever.

How can I test RMAN

Hi,
how can I test RMAN ? How can I verify if my RMAN backups are correct and in the case of problem can be helpful ? Apearently we can not recover the dropped objects !!! Then how to test recovery by RMAN ? Any scenari ?
Many thanks before.

How can I verify if my RMAN backups are correct rman>crosscheck backup;
rman>validate daafile "no"
in the case of problem can be helpful ? Apearently we can not recover the dropped objects for point in time recovery
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10769/toc.htm
http://download-uk.oracle.com/docs/cd/B14117_01/server.101/b10770/toc.htm
Message was edited by:
Mohammadi52

RMAN backup restore leads to the error "ORA-00600: internal error code, arguments: [kccsbck_first], [2], [2349545192]" on DB startup

Hi All,
DB:11.2.0.3.0
OS: Sun Solaris SPARC 64 bits
I am facing an issue - RMAN backup restore leads to the error "ORA-00600: internal error code, arguments: , , " on DB startup. Restored from RMAN backup DB test2 to DB test1.
 $ sqlplus / as sysdba
 SQL*Plus: Release 11.2.0.3.0 Production on Sun Oct 6 09:31:28 2013
 Copyright (c) 1982, 2011, Oracle. All rights reserved.
 Connected to an idle instance.

SQL> startup
ORACLE instance started.
Total System Global Area 4277059584 bytes
Fixed Size 2166160 bytes
Variable Size 1493176944 bytes
Database Buffers 2768240640 bytes
Redo Buffers 13475840 bytes
ORA-00600: internal error code, arguments: , , ,
SQL> exit
DB test2 database validated:
RMAN> validate Database;
No issues reported.
Could anyone please let me the what's the cause of this error
Thanks for your time
Regards,
user10088255

HI,
CASE : I
C:\>set ORACLE_SID=xxxx
C:\>sqlplus sys/XXXXX@rosen as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:28:00 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
ORA-00600: internal error code, arguments: [kccsbck_first], [1], [3978145973],
Solution: AFTER GETTING ORA-00600, SHUT THE DATABASE AND STARTUP IT INTO MOUNT STAGE AND THEN ALTER DATABASE TO OPEN STAGE .
SQL> shut immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
Database mounted.
SQL> alter database open;
Database altered.
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
ROSEN READ WRITE
CASE :: II
C:\>sqlplus sys/XXXX@royalton as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:37:37 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 1979714112 bytes
Database Buffers 1426063360 bytes
Redo Buffers 16007168 bytes
ORA-00600: internal error code, arguments: [kccsbck_first], [1], [73515151],[], [], [], [], [], [], [], [], []
Solution : As in above case, I have started the database in mount and then alter it to the open mode but it doesnot work out. After some analysis ,troubleshooting and googling, we have decided to flush the shared pool component of the SGA . So, we have started the database in mount stage and then flush the shared pool and further alter it to open stage . Below are the steps performed to solve this issue .
SQL> shut immediate
ORA-01507: database not mounted
ORACLE instance shut down.
C:\>set ORACLE_SID= royalton
C:\>sqlplus sys/xxxxxxxx@royalton as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jan 29 12:28:00 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2180544 bytes
Variable Size 2080377408 bytes
Database Buffers 1325400064 bytes
Redo Buffers 16007168 bytes
Database mounted.
SQL> alter system flush shared_pool;
SQL> alter database open
Database altered.
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
ROYALTON READ WRITE
Conclusion : Though this is not the solution but a workaround to solve ORA-00600 which is having same argument as above, then you may follow the above steps.
Please chek this link : One Can Succeed at Almost Anything For Which He Has Enthusiasm...: ORA-00600: internal error code, arguments: [kccsbck_f…

ORA-00600: internal error code, arguments: [6122], [0], [4], [0], [], [], [

Hi All,
I Got ORA-00600: internal error code, arguments: [6122], [0], [4], [0], [], [], [], [], [], [], [], []
today i check for Oracle knowledge but i can see only until 9i version.
I am pasting my OS AND database version below
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
I didn't find any knowledge for my database base version please any one help me on this
Thanks in Advance
Kind Regards
Venkat

980323 wrote:
Hi Vishal,
No not yet i will paste my trace file please can you have a look on it
Dump continued from file: /oracle/admin/diag/rdbms/ewahed13/EWAHED13/trace/EWAHED13_ora_14503.trc
ORA-00600: internal error code, arguments: [6122], [0], [4], [0], [], [], [], [], [], [], [], []
========= Dump for incident 22995 (ORA 600 [6122]) ========
*** 2013-05-16 12:36:32.933
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=6zcs0sc3nhj85) -----
UPDATE "CS_ACTUALS"."APPLICATIONSTATE" SET "DEFINITION"=:1,"DEFINITIONDT"=:2 WHERE "DEFINITIONDT"=:3 AND "ROWID"=:4 RETURNING ROWID into :5Depending upon the platform version see bugs:
Bug 12926930
Bug 15907953
Bug 16374276
I thinks its the Index block corrupt - So you have following options
1) Apply the patch - which is possible by seeing the exact bud
2) Try to recover the block
3) Try to drop and recreate the index - If its a non sys object.
You need to check and populate V$DATABASE_BLOCK_CORRUPTION for blocks which are marked corrupt.
Use dbv,rman validate commands to populate V$DATABASE_BLOCK_CORRUPTION view
Use - Identify the corruption extension using RMAN/DBV/ANALYZE etc [ID 836658.1] note for identifying the blocks that are corrupt.

Interpration of DBVerify zero block errors

Hello Oracle-experts,
after DBVerify check on my Oracle DB 10.2.0.2 i get the several following errors:
Completely zero block found during dbv:
Page 286685 is marked corrupt
After these warnings I get the error:
BR0398E DBVERIFY detected corrupted blocks in /oracle/<sid>/sapdata4/sr3_8/sr3.data8
Question:
1) How should these zero block errors be interpreted? Is my database therefore corrupt or can these errors be neglected? If not, what is the approach to solve these errors?
The problem is that I have a lot of these errors and do not have a valid backup.
Any helpful information information will be very appreciated!

Hi Holger,
didn't you like the replies of your other threads?
Block Corruption (BR0398E DBVERIFY detected corrupted blocks in /oracle/TS2
BR0398E DBVERIFY detected corrupted blocks in TS SAPSR3
Honestly, handling corruptions is really not that difficult.
You figure out what kind of data is supposed to be stored in the corrupted blocks and take your actions accordingly.
So if you can regenerate the content (like you can do that by rebuilding indexes), you do that.
If you cannot regenerate the content, you need a backup.
That's it. It's all lengthly described in the SAP notes on corruptions. Maybe you should read them ...
> Question:
> 1) How should these zero block errors be interpreted? Is my database therefore corrupt or can these errors be neglected? If not, what is the approach to solve these errors?
> The problem is that I have a lot of these errors and do not have a valid backup.
Ok, having no backups always puts you in dire straits. It's the single one error no DBA is allowed to make.
However, what you should do is to perform a FULL consistency check.
That is:
run ANALYZE TABLE VALIDATE STRUCTURE CASCADE on ALL tables
run a FULL db export to /dev/nul
run DBVerify/RMAN validate on the complete database (looks like you've already done that)
Don't skip a check, don't shortcut - just do them.
Maybe the "completely zero filled blocks* don't belong to any object and you've no data loss.
Then you may (as I already told you in the other thread) reorganize the tablespace to get rid of the warnings.
If there was some data in these blocks that you cannot regenerate then you have to face it: you lost that data.
It's gone and won't come back.
regards,
Lars

Oracle giving Block corruption errors when using CDC for sending the data to SQL Server 2012

Hello Friends,
We are facing an error while using CDC with Oracle. It is a "Block corruption" error, which indicates at some level of data corruption. We ran RMAN validate command to scan the database for corruption but it returned with no errors, however he
Alert Log in Oracle is still coming up with the following error. Has anyone experienced this error when using Oracle Standard Edition and SQL 2012 ?
Trace file e:\app\pulse-ad\diag\rdbms\orcl\orcl\trace\orcl_ora_5992.trc
Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 4 - type 8664, 4 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:6782M/24575M, Ph+PgF:12203M/30844M
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 151
Windows thread id: 5992, image: ORACLE.EXE (SHAD)
*** 2013-12-12 03:04:33.655
*** SESSION ID:(1281.3832) 2013-12-12 03:04:33.655
*** CLIENT ID:() 2013-12-12 03:04:33.655
*** SERVICE NAME:(orcl) 2013-12-12 03:04:33.655
*** MODULE NAME:(xdbcdcsvc.exe) 2013-12-12 03:04:33.655
*** ACTION NAME:() 2013-12-12 03:04:33.655
Lost-write detected for sequence 70856. The lost-write starts occurring in block 11193. The current block being validating is 12930.
Block dump of the first lost-write block:
Flag: 0x1 Format: 0x22 Block: 0x00002bb9 Seq: 0x000114bf Beg: 0x94 Cks:0x68ee
Dump of memory from 0x0000000598D06C00 to 0x0000000598D06E00
598D06C00 00002201 00002BB9 000114BF 68EE8094 [."...+.........h]
598D06C10 00085BF1 0023BDA1 000DE19C 000DE19C [.[....#.........]
598D06C20 0000000C 00000000 2209160A 5BF10000 [..........."...[]
598D06C30 3EB10502 00C0F5CA 0031BDA1 00010205 [...>......1.....]
598D06C40 02B22C6A 038A6D69 00000001 00000000 [j,..im..........]
598D06C50 4D554407 30373230 35BB0206 001100AE [.DUM0270...5....]
598D06C60 0001040A 000D000E 038A6D69 56B25735 [........im..5W.V]
598D06C70 729C0003 E19C0001 000C0006 000D0006 [...r............]
598D06C80 02BB0502 00C0F5CD 0023BDA1 000A0002 [..........#.....]
598D06C90 00C00013 000000D0 00030201 56B25736 [............6W.V]
598D06CA0 03890001 00000000 00000000 002E0105 [................]
598D06CB0 FFFF0003 00C0F5CD 56B25736 3EB10003 [........6W.V...>]
598D06CC0 FFFF0024 0014000C 000C0018 00120014 [$...............]
598D06CD0 09CC0058 E75B0022 0009000F 00085BF1 [X...".[......[..]
598D06CE0 0024BDA1 000DE19D 000DE19D 0000000C [..$.............]
598D06CF0 00000000 2309160A 5BF10000 3EB10502 [.......#...[...>]
598D06D00 00C0F5CD 0020BDA1 00010205 02B22C72 [...... .....r,..]
598D06D10 03900974 00000019 00000000 3030300A [t............000]
598D06D20 33303030 06323132 AE35BB02 0B441100 [0003212...5...D.]
598D06D30 0001040A 000D000E 03900974 56B25736 [........t...6W.V]
598D06D40 729C0003 E19D0011 000C0006 000D0006 [...r............]
598D06D50 02BB0502 00C0F5CD 0024BDA1 00EA0002 [..........$.....]
598D06D60 00270016 000001FC 00032C01 56B25736 [..'......,..6W.V]
598D06D70 00000001 00000000 30393007 002E0105 [.........090....]
598D06D80 FFFF0003 00C0F5CD 56B25736 00000003 [........6W.V....]
598D06D90 FFFF0025 00140052 000C0018 00070035 [%...R.......5...]
598D06DA0 0003000A 00070003 0001001D 00030001 [................]
598D06DB0 00010001 00010001 00010001 00010001 [................]
598D06DC0 00010001 00010001 00010001 00010001 [................]
598D06DD0 00010001 00000001 00010001 00010001 [................]
598D06DE0 00010001 00000014 09720174 00000022 [........t.r."...]
598D06DF0 0009000F 00085BF1 0025BDA1 000DE19A [.....[....%.....]
Block dump of the current block being validating:
Flag: 0x1 Format: 0x22 Block: 0x00003282 Seq: 0x000114c8 Beg: 0x0 Cks:0x312a
Dump of memory from 0x0000000598DDFE00 to 0x0000000598DE0000
598DDFE00 00002201 00003282 000114C8 312A8000 [."...2........*1]
598DDFE10 50424703 31303607 34353335 69745319 [.GBP.6015354.Sti]
598DDFE20 6E696C72 72502067 6375646F 4C207374 [rling Products L]
598DDFE30 4E206474 C3025650 0380013D 0457454E [td NPV..=...NEW.]
598DDFE40 4E1E09C2 1E09C204 10C2024E 1E09C204 [...N....N.......]
598DDFE50 09C2044E C2024E1E 03C30510 021B0929 [N....N......)...]
598DDFE60 C3053DC3 0F192602 2602C305 C3050F19 [.=...&.....&....]
598DDFE70 0C1A6203 5102C105 C2041F4E 044E1E09 [.b.....QN.....N.]
598DDFE80 4E1E09C2 0410C202 4E1E09C2 1E09C204 [...N.......N....]
598DDFE90 10C2024E 2903C305 78071B09 011D0B71 [N......)...xq...]
598DDFEA0 BF020101 1FBF0215 4E018001 53014E01 [...........N.N.S]
598DDFEB0 0723002C 0B0C7178 0A3C3C18 30303030 [,.#.xq...<<.0000]
598DDFEC0 33373030 4D033337 47034255 36075042 [007373.MUB.GBP.6]
598DDFED0 38333936 4E113331 2065776B 74616C50 [693813.Nkwe Plat]
598DDFEE0 6D756E69 56504E20 0B0AC303 4E038001 [inum NPV.......N]
598DDFEF0 C2045745 0459512E 59512EC2 5253C203 [EW...QY...QY..SR]
598DDFF00 512EC204 2EC20459 C2035951 C3055253 [...QY...QY..SR..]
598DDFF10 1B092903 0B0AC303 3C04C305 C3053239 [.).........<92..]
598DDFF20 32393C04 4F08C305 C105114F 1F4E5102 [.<92...OO....QN.]
598DDFF30 512EC204 2EC20459 C2035951 C2045253 [...QY...QY..SR..]
598DDFF40 0459512E 59512EC2 5253C203 2903C305 [.QY...QY..SR...)]
598DDFF50 78071B09 01190A71 C0030101 C0034709 [...xq........G..]
598DDFF60 8001330A 4E014E01 002C5301 71780723 [.3...N.N.S,.#.xq]
598DDFF70 3C180B0C 30300A3C 30303030 33373337 [...<<.0000007373]
598DDFF80 42554D03 50424703 31304207 344C5131 [.MUB.GBP.B011QL4]
598DDFF90 6F725020 63657073 614A2074 206E6170 [ Prospect Japan ]
598DDFFA0 646E7546 64724F20 44535520 30302E30 [Fund Ord USD0.00]
598DDFFB0 04C30331 03800133 0557454E 5B1603C3 [1...3...NEW....[]
598DDFFC0 03C30521 04215B16 1F4004C3 1603C305 [!....[!...@.....]
598DDFFD0 C305215B 215B1603 4004C304 03C3051F [[!....[!...@....]
598DDFFE0 031B0929 043304C3 4D245AC2 245AC204 [).....3..Z$M..Z$]
598DDFFF0 02C3054D 040A1A18 494002C1 1603C305 [M.........@I....]
*** 2013-12-12 03:05:07.984
** LOGMINER WARNING - Invalidated 6 LCRs **
Complete dump of first invalid START LCR follows:
++ LCR Dump Begin: 0x0000000532C004E0 - CANNOT_SUPPORT
 op: 255, Original op: 3, baseobjn: 0, objn: 233316, objv: 1
 DF: 0x00000002, DF2: 0x00000000, MF: 0x00000000, MF2: 0x00000000
 PF: 0x40000001, PF2: 0x00002000
 MergeFlag: 0x00, FilterFlag: 0x00
 Id: 0, iotPrimaryKeyCount: 3, numChgRec: 4
 NumCrSpilled: 0
 RedoThread#: 1, rba: 0x0114c8.0001c6ce.00d4
 scn: 0x0003.56b593be, xid: 0x0008.00c.00100d85, pxid: 0x0008.00c.00100d85
 ncol: 0newcount: 0, oldcount: 0
 LUBA: 0x3.c109c0.c.15.38f64
Thanks
Dee

Hi Dee,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Mike Yin
TechNet Community Support

Block corruption in Free Space

Hi,
Environment:-
Oralce 10.2.0
Windows platform
I am facing problem of Logical block corruption.
RMAN validate block corruption (DBVerify as well) But no entry in Alert log file.
When I check Which segment has block corruption I found that block corruption are in free blocks of tablespace (DBA_FREE_SPACE).
To Fix it I create table and allocate corrupted block to that table. I confirm corrupted block allocation in table (using DBA_EXTENTS).
But when I insert rows in that table to reuse corrupted block Oracle give error of ora-1578 Block corruption, and I am not able to reuse corrupted block(as many expert suggest to overcome block corruption in free space).
I dropped table and recreate and repeat this process many times but still no success.
So. can anybody help me on this.
I appreciate your efforts and time you spend to read this
Thanks

Hello,
Please check the link i posted.
Example: Detecting Corruption
The CHECK_OBJECT procedure checks the specified object, and populates the repair table with information about corruptions and repair directives. You can optionally specify a range, partition name, or subpartition name when you want to check a portion of an object.
Validation consists of checking all blocks in the object that have not previously been marked corrupt. For each block, the transaction and data layer portions are checked for self consistency. During CHECK_OBJECT, if a block is encountered that has a corrupt buffer cache header, then that block is skipped.
The following is an example of executing the CHECK_OBJECT procedure for the scott.dept table.
SET SERVEROUTPUT ON
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'SCOTT',
OBJECT_NAME => 'DEPT',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
SQL*Plus outputs the following line, indicating one corruption:
number corrupt: 1

RMAN Validate

Similar Messages

Maybe you are looking for