Backup validate :Error

Hi Expert,
while executing backup validate database archivelog all in one of the server i received this
RMAN> backup validate database archivelog all;
Starting backup at 04-JUL-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=18 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/04/2007 06:21:34
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati
on does not match any archive log in the recovery catalog
What this means and is it any major concern?
Thanks
Shaan

this means you didn't have any archives and rman is unable to validate them.
RMAN does not actually produce backup sets, but rather reads the specified files in their entirety, to determine whether they can be backed up and are not corrupted.
found at:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp008.htm#sthref672

Similar Messages

Rman backup validate error

DBGSQL: RCVCAT> begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; [10:37:16.635]
DBGSQL: sqlcode = 6550 [10:37:16.635]
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command restore : 600
RMAN-00600: internal error, arguments [9302] [6550] [begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; ] [] []
RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'FINDSPFILEBACKUP'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
pls any one help me out
Thanks!

Since you say nothing about your OS and database version and we also don't know,which command produces this error, only a vague guess is possible, COULD be
Bug 7633694: RESTORE SPFILE LS-00306: WRONG NUMBER OR TYPES OF ARGUMENTS 'FINDSPFILEBACKUP' .
IF this bug is hit possible workarounds are:
1) Don't use a 11gR1 catalog
2) don't use spfile,keep a text based pfile
3) upgrade to 11gR2 (IF your OS is Linux or Solaris)
Werner

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

Backup validate command

I have few questions to clear my confusion.Can anyone please clarify it.
1)Does Backup validate check logical database plus archivelog all takes same time as real backup?
2)does database needs to be in archivelog mode?
3)can this validate command run mount state?
Thanks

Here is a simple illustration for you;
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 17-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=/db/OPTIMA/oradata/opttest/opttest/UNDOTBS1.dbf
input datafile fno=00341 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_02.dbf
input datafile fno=00369 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_GROUP_D_03.dbf
input datafile fno=00307 name=/db/OPTIMA/oradata/opttest/data/NORS_TONES_D_02.dbf
input datafile fno=00311 name=/db/OPTIMA/oradata/opttest/data/NORS_SINGLE_UNIT_PM_D_02.dbf
input datafile fno=00313 name=/db/OPTIMA/oradata/opttest/data/NORS_PM_D_02.dbf
input datafile fno=00318 name=/db/OPTIMA/oradata/opttest/data/NORS_RTLTSUM_D_02.dbf
input datafile fno=00319 name=/db/OPTIMA/oradata/opttest/data/NORS_SOTS_D_02.dbf
input datafile fno=00320 name=/db/OPTIMA/oradata/opttest/data/NORS_SYSPERF_D_02.dbf
input datafile fno=00328 name=/db/OPTIMA/oradata/opttest/data/NORS_TREATMENT_D_02.dbf
input datafile fno=00329 name=/db/OPTIMA/oradata/opttest/data/NORS_TRUNK_MODULES_D_02.dbf
input datafile fno=00123 name=/db/OPTIMA/oradata/opttest/data/NORS_SINGLE_UNIT_PM_D_01.dbf
input datafile fno=00129 name=/db/OPTIMA/oradata/opttest/data/NORS_TONES_D_01.dbf
input datafile fno=00147 name=/db/OPTIMA/oradata/opttest/data/NORS_C7LKSET_D_01.dbf
input datafile fno=00149 name=/db/OPTIMA/oradata/opttest/data/NORS_C7MTP_D_01.dbf
input datafile fno=00151 name=/db/OPTIMA/oradata/opttest/data/NORS_C7ROUTE_D_01.dbf
input datafile fno=00155 name=/db/OPTIMA/oradata/opttest/data/NORS_CALL_CONTROL_D_01.dbf
input datafile fno=00157 name=/db/OPTIMA/oradata/opttest/data/NORS_CDIVGRP_D_01.dbf
input datafile fno=00159 name=/db/OPTIMA/oradata/opttest/data/NORS_COMPUTING_MODULE_D_01.dbf
input datafile fno=00163 name=/db/OPTIMA/oradata/opttest/data/NORS_DTSRPM_D_01.dbf
input datafile fno=00165 name=/db/OPTIMA/oradata/opttest/data/NORS_EXND_CALL_CONTROL_D_01.dbf
input datafile fno=00167 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_GROUP_D_01.dbf
input datafile fno=00169 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_STATS_D_01.dbf
input datafile fno=00171 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_TRAFFIC_D_01.dbf
input datafile fno=00173 name=/db/OPTIMA/oradata/opttest/data/NORS_IWUCGRP_D_01.dbf
input datafile fno=00179 name=/db/OPTIMA/oradata/opttest/data/NORS_MPCLINK3_D_01.dbf
input datafile fno=00183 name=/db/OPTIMA/oradata/opttest/data/NORS_OFFICE_TRAFFIC_ROUT_D_01.dbf
input datafile fno=00185 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_01.dbf
input datafile fno=00349 name=/db/OPTIMA/oradata/opttest/data/NORS_LINE_ACCESS_D_02.dbf
input datafile fno=00011 name=/db/OPTIMA/oradata/opttest/opttest/OPTIMA_ALARMS_I.dbf
input datafile fno=00012 name=/db/OPTIMA/oradata/opttest/opttest/SAMPLE_VENDORD.dbf
input datafile fno=00013 name=/db/OPTIMA/oradata/opttest/opttest/SAMPLE_VENDORI.dbf
input datafile fno=00110 name=/db/OPTIMA/oradata/opttest/system/DEF_NORTEL_SWITCHING_S_01.dbf
input datafile fno=00115 name=/db/OPTIMA/oradata/opttest/data/NORS_PM_D_01.dbf
input datafile fno=00177 name=/db/OPTIMA/oradata/opttest/data/NORS_LINE_TRAFFIC_D_01.dbf
input datafile fno=00347 name=/db/OPTIMA/oradata/opttest/data/NORS_MPCLINK3_D_03.dbf
input datafile fno=00350 name=/db/OPTIMA/oradata/opttest/data/NORS_EXND_CALL_CONTROL_D_03.dbf
input datafile fno=00351 name=/db/OPTIMA/oradata/opttest/data/NORS_OWCTTS_D_03.dbf
input datafile fno=00354 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_STATS_D_03.dbf
input datafile fno=00355 name=/db/OPTIMA/oradata/opttest/data/NORS_SYSPERF_D_03.dbf
input datafile fno=00357 name=/db/OPTIMA/oradata/opttest/data/NORS_TRUNK_MODULES_D_03.dbf
input datafile fno=00358 name=/db/OPTIMA/oradata/opttest/data/NORS_TREATMENT_D_03.dbf
input datafile fno=00359 name=/db/OPTIMA/oradata/opttest/data/NORS_SOTS_D_03.dbf
input datafile fno=00360 name=/db/OPTIMA/oradata/opttest/data/NORS_RTLTSUM_D_03.dbf
input datafile fno=00362 name=/db/OPTIMA/oradata/opttest/data/NORS_OFFICE_TRAFFIC_ROUT_D_03.dbf
input datafile fno=00363 name=/db/OPTIMA/oradata/opttest/data/NORS_C7ROUTE_D_03.dbf
input datafile fno=00365 name=/db/OPTIMA/oradata/opttest/data/NORS_CDIVGRP_D_03.dbf
input datafile fno=00368 name=/db/OPTIMA/oradata/opttest/data/NORS_CALL_CONTROL_D_03.dbf
input datafile fno=00370 name=/db/OPTIMA/oradata/opttest/data/NORS_COMPUTING_MODULE_D_03.dbf
input datafile fno=00371 name=/db/OPTIMA/oradata/opttest/data/NORS_C7MTP_D_03.dbf
input datafile fno=00372 name=/db/OPTIMA/oradata/opttest/data/NORS_IWUCGRP_D_03.dbf
input datafile fno=00376 name=/db/OPTIMA/oradata/opttest/data/NORS_C7LKSET_D_03.dbf
input datafile fno=00377 name=/db/OPTIMA/oradata/opttest/data/NORS_ISUP_TRAFFIC_D_03.dbf
input datafile fno=00378 name=/db/OPTIMA/oradata/opttest/data/NORS_DTSRPM_D_03.dbf
input datafile fno=00352 name=/db/OPTIMA/oradata/opttest/data/NORS_ANN_D_03.dbf
user interrupt received
Finished backup at 17-AUG-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03099: job cancelled at user request
RMAN> --> It was validating with the archivelog mode
RMAN> exit
Recovery Manager complete.
$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Aug 17 16:29:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1375731712 bytes
Fixed Size                  2056088 bytes
Variable Size             704643176 bytes
Database Buffers          654311424 bytes
Redo Buffers               14721024 bytes
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> exit;
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Aug 17 16:30:00 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: OPTTEST (DBID=750193206)
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 17-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1461 devtype=DISK
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:07
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:08
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:09
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:09
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:10
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:11
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:11
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:12
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:13
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:13
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:14
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:15
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:15
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:16
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/17/2010 16:30:17
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting compressed archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=297 recid=7633 stamp=727146412
input archive log thread=1 sequence=298 recid=7634 stamp=727221971
input archive log thread=1 sequence=299 recid=7635 stamp=727222952
input archive log thread=1 sequence=300 recid=7636 stamp=727281385Regards.
Ogan

Restore Validate Database vs Backup Validate Database

Hi,
I want to add the following sentence after taking the backup using following command (backup as compressed backupset database plus archivelog;)
restore database validate;
or
backup validate database;
which one is best?

It depends on what you are trying to accomplish, as per documentation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#sthref141BACKUP .. VALIDATE: Causes RMAN to scan the specified files and verify their contents, testing whether this file can be backed up. RMAN creates no output files. Use this command periodically to check for physical and logical errors in database files.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta051.htm#sthref796
RESTORE... VALIDATE causes RMAN to select existing backups that it would use to perform a RESTORE operation, and scan them all to ensure that they are present and free of corruption.>
Guessing what you're trying to do, I recommend:
backup check logical as compressed backupset database plus archivelog;
restore validate database;
CHECK LOGICAL. Tests data and index blocks that pass physical corruption checks for logical corruption, for example, corruption of a row piece or index entry. If RMAN finds logical corruption, then it logs the block in the alert.log and server session trace file. HTH
Enrique
PS If you have access to Metalink see Note:388422.1 Top 10 Backup and Recovery best practices.
Edited by: Enrique Orbegozo on Dec 17, 2008 4:21 PM

PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN

제품 : RMAN
작성날짜 : 2002-05-30
PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN
=====================================================
PURPOSE
RMAN을 이용하여 Test Backup을 수행하기 위한 정보를 제공한다.
EXPLANATION
8.1.7 부터 RMAN에서 BACKUP command에 VALIDATE keyword를 사용할 수 있게 되었다
이 명령의 수행은 다음과 같은 작업을 수행한다.
- Datafile의 physical and logical corruption을 check한다.
- 모든 database file들이 존재하는지, 그리고 올바른 위치에 있는지를 검증한다.
RMAN은 실제적으로 backupset을 생성하지 않는다 그러나 그것들이 backup될 수
있는지 없는지를 결정하기 위해서 기술된 file들을 scan한다.
BACKUP VALIDATE 는 backup job을 수행시 수행되는 것을 제외하고는
RESTORE VALIDATE와 거의 비슷하다.
EXAMPLE
아래와 같은 command들을 수행하여 backup하고자 하는 database file과 archived redo
log들이 실제로 backup될 수 있는지를 검증할 수 있다.
RUN {
ALLOCATE CHANNEL ch1 TYPE 'sbt_tape';
BACKUP VALIDATE
DATABASE
ARCHIVELOG ALL;
Note: MAXCORRUPT or PROXY parameter는 VALIDATE option과 함께 사용할 수 없다.
REFERENCE DOCUMENTS
NOTE:121109.1

Clint,
I ran the command lines you wrote me after i placed the database in Startup MOUNT state, RMAN gave error messages that the database needs to be open:
RMAN> SQL 'ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE';
sql statement: ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 11/04/2005 15:31:33
RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
ERTB2 OFFLINE IMMEDIATE
ORA-01109: database not open
Then I ran the same command lines after I opened the database, RMAN gave error messages that "offline immediate disallowed unless media recovery enabled":
RMAN> SQL 'ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE';
sql statement: ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 11/04/2005 15:48:17
RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
ERTBS2 OFFLINE IMMEDIATE
ORA-01145: offline immediate disallowed unless media recovery enabled
I am stuck again and need your help!
Thank you,
Mitra

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 to get ALL validate-errors while insert xml-file into xml_schema_table

How to get all validate-errors while using insert into xml_schema when having a xml-instance with more then one error inside ?
Hi,
I can validate a xml-file by using isSchemaValid() - function to get the validate-status 0 or 1 .
To get a error-output about the reason I do validate
the xml-file against xdb-schema, by insert it into schema_table.
When more than one validate-errors inside the xml-file,
the exception shows me the first error only.
How to get all errors at one time ?
regards
Norbert
... for example like this matter:
declare
     xmldoc CLOB;
     vStatus varchar
begin
-- ... create xmldoc by using DBMS_XMLGEN ...
-- validate by using insert ( I do not need insert ;-) )
     begin
     -- there is the xml_schema in xdb with defaultTable XML_SCHEMA_DEFAULT_TABLE
     insert into XML_SCHEMA_DEFAULT_TABLE values (xmltype(xmldoc) ) ;
     vStatus := 'XML-Instance is valid ' ;
     exception
     when others then
     -- it's only the first error while parsing the xml-file :
          vStatus := 'Instance is NOT valid: '||sqlerrm ;
          dbms_output.put_line( vStatus );
     end ;
end ;

If I am not mistaken, the you probably could google this one while using "Steven Feuerstein Validation" or such. I know I have seen a very decent validation / error handling from Steven about this.

Trying to copy iPhoto Library to external hard drive for backup. Error message: The Finder can't complete the operation because some data in "iPhoto Library" can't be read or written (Error code -36).

Trying to copy iPhoto Library to external hard drive for backup. Error message: The Finder can't complete the operation because some data in "iPhoto Library" can't be read or written (Error code -36).

That code is
-36
ioErr
I/O error (bummers)
Make sure the EHD is formatted OS X Extended (journaled) and run Disk Utilty on the EHD and repair the disk. If that fails to help I'd try the following:
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button,
navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the Library ➙ Rebuild Library menu option
In the next window name the new library and select the external HD as the location of the newly rebild library.
Click on the Create button.
Note 1: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments. However, books, calendars, cards and slideshows will be lost.
Note 2: Your current library will be left untouched for further attempts at a fix if so desired.
OT

Offline Backup got error Status Finished with error

Dear all ,
OS AIX , DB Oracle , SAP ECC6.0 , Tivoli Storage Manager
Offline Backup got error Status shows Finished with Error   (Backups are fired through DB13)
Retune Code :0005 Error during processing
Detail Logs:
BKI0027I: Time: 12/10/09 05:19:06 Object: 47 of 47 in process: /oracle/IRP/origlogA/cntrl/cntlrIRP.dbf Size: 14.422 MB, MGMNT-CLASS: WEEKLYMGM
BKI5005E: Tivoli Storage Manager Error:
ANS1312E (RC12)   Server media mount not possible
BKI1208W: The object '/oracle/IRP/origlogA/cntrl/cntlrIRP.dbf' will be retried [4].
BKI0027I: Time: 12/10/09 05:19:38 Object: 47 of 47 in process: /oracle/IRP/origlogA/cntrl/cntlrIRP.dbf Size: 14.422 MB, MGMNT-CLASS: WEEKLYMGM
BKI5005E: Tivoli Storage Manager Error:
ANS1312E (RC12)   Server media mount not possible
BKI1231E: Maximum number of retries for file /oracle/IRP/origlogA/cntrl/cntlrIRP.dbf exceeded.
BR0233E Backup utility has reported an error while saving file /oracle/IRP/origlogA/cntrl/cntlrIRP.dbf
BR0280I BRCONNECT time stamp: 2009-12-10 05.20.07
#END /oracle/IRP/origlogA/cntrl/cntlrIRP.dbf
BR0280I BRCONNECT time stamp: 2009-12-10 05.20.07
BR0304I Starting and opening database instance IRP ...
BR0280I BRCONNECT time stamp: 2009-12-10 05.20.26
BR0305I Start and open of database instance IRP successful
BR0280I BRCONNECT time stamp: 2009-12-10 05.20.26
BKI1215I: Average transmission rate was 237.735 GB/h (67.622 MB/sec).
BKI1227I: Average compression factor was 1.000.
BKI0405I: TDP waited 497 sec. for BRBACKUP in util_file_online communication.
BKI0020I: End of program at: Thu Dec 10 05:20:33 IST 2009 .
BKI0021I: Elapsed time: 02 h 20 min 31 sec .
BKI0024I: Return code is: 2.
BR0280I BRBACKUP time stamp: 2009-12-10 05.20.33
BR0279E Return code from '/usr/sap/IRP/SYS/exe/run/backint -u IRP -f backup -i /oracle/IRP/sapbackup/.beccdcmb.lst -t file_online -p /oracle/I
BR0232E 0 of 47 files saved by backup utility
BR0280I BRBACKUP time stamp: 2009-12-10 05.20.33
BR0231E Backup utility call failed
BR0056I End of database backup: beccdcmb.aff 2009-12-10 05.20.33
BR0280I BRBACKUP time stamp: 2009-12-10 05.20.35
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-12-10 05.20.35
BR0291I BRARCHIVE will be started with options '-U -jid ALGOF20091210030000 -d util_file -c force -p initIRPweekly.sap -cds'
BR0280I BRBACKUP time stamp: 2009-12-10 05.23.07
BR0292I Execution of BRARCHIVE finished with return code 5
regards

Hi,
> BKI5005E: Tivoli Storage Manager Error:
> ANS1312E (RC12)   Server media mount not possible
Have you checked tape is properly mounted on TSM ?
Check below guide on page 69.
http://www.redbooks.ibm.com/redbooks/pdfs/sg246554.pdf
Thanks
Sunny
Edited by: Sunny Pahuja on Dec 12, 2009 12:25 PM

HT3275 Time machine couldn't complete the backup. an error occured while creating the backup folder

Time machine couldn't complete the backup. an error occured while creating the backup folder Why does this happen?

hello,
http://pondini.org/TM/C10.html
http://Pondini.org/TM/FAQ.html
http://pondini.org/TM/Troubleshooting.html
Can't imaging something not being covered there.

Backup validate check logical database

What is exactly the following RMAN command do? I want to know Is it doing a full backup or not?
rman> backup validate check logical database' . Kindly help me.

RMAN does not physically backup the database with this command. But it reads all blocks and checks for corruptions.
If it finds corrupted blocks it will place the information about the corruption into a view:
v$database_block_corruption;
Now we can tell RMAN to recover all the blocks which it has found as being corrupt:
RMAN> blockrecover corruption list; # (all blocks from v$database_block_corruption)
Use below link for reference.
http://luhartma.blogspot.com/2006/04/how-to-check-for-and-repair-block.html
-Bharath

Time Machine backups hanging -- error message included

Hello. I've read a bunch of the previous topics and tried some other recommendations, but I'm still having trouble. I haven't had a good backup in 10 days now. I'm backup directly via USB to a Western Digital Passport drive.
So it wasn't until today that I found the TM Buddy. I installed that and systematically excluded certain .plist files that were apparently causing problems. Then I followed Pondini's advice and made the changes in Spotlight and Energy Saver preferences. I also renamed my computer in Sharing to just one word. I even tried a different USB cable, which actually seems to help a bit because my previous cable would cause immediate 'ejections' if it was breathed upon. And of course, I did a Repair Disk in Disk Utility which showed a normally functioning drive.
Anyway, so I was getting the 'Waiting to be indexed (100) and (101)' errors and the TM job hanging on 'Indexing...'. I finally had one run successfully after 20+ tries, but it only said it backed up around 735MB -- very low number after 10 days since the last successful backup.
Now, I'm trying a new backup and it's stuck on 'Cleaning Up' according to the spinning menubar icon. The TM widget shows the following:
Starting standard backup
Backing up to: /Volumes/Back-up HDD/Backups.backupdb
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) Creating directory 14EB9137-94AE-44B6-BD8A-9283EC9C943D
Failed to make snapshot.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandl
Wow - as I'm writing this, my drive gets ejected again and the backup stops and drive disappears in Finder. I'm trying to find any other solution besides throwing $100 at another drive. My WD Passport is less than 1.5 yrs old. If it's the drive, then so be it but I'd like to be sure.
Any help, please? Thanks so much in advance.

MichaelEB wrote:
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) Creating directory 14EB9137-94AE-44B6-BD8A-9283EC9C943D
Failed to make snapshot.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandl
All various ways of saying "cannot write to the drive." It either couldn't create the (hidden) log file on the TM drive, then couldn't create the folder for the backups, then couldn't write to the log again.
It's probably the drive.
Less likely (but possible considering the cable issue) is a port (try others), or other connections (hook it up directly; no hubs or daisy-chaining.
Another long shot is another USB device taking too much power intermittently. Disconnect all other USB devices.

RMAN Parallel Backup Validate

Hi,
OS= Solaris 10
Database = 10gR2
I am using following script to validate the physical and logical corruption in the database through RMAN:
rman target /
RMAN> RUN {
CONFIGURE DEVICE TYPE DISK PARALLELISM 8;
ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
BACKUP VALIDATE DATABASE;
RELEASE CHANNEL;
My machine has 4 CPUs.
I just want to verify that will the above RMAN script open up 4 channels in parallel and validate the database?
regards

Hi Fahd,
Can you please study the below link also from the forum.
Backup Time
Best regards,
Rafi.
http://rafioracledba.blogspot.com/

Backup failed error code o8x100037

any ideas?

Hi,
>>Backup Failed Error Code 2155348129 Volume Shadow Copy Service error:
As the following article suggests, this error can be caused by the incorrect Active volume.
Troubleshooting VSS Writer Failure
http://social.technet.microsoft.com/wiki/contents/articles/1261.troubleshooting-vss-writer-failure.aspx
If the issue persists, we can follow the article below to re-register the dlls that are needed by the VSS service to see if it helps.
Volume Shadow Copy Service and DLLs
http://blogs.technet.com/b/sdoakes/archive/2006/02/03/418722.aspx
In addition, the following thread focused on the similar issue and can be referred to as reference.
Failed Full System Backup Error: 2155348129
https://social.technet.microsoft.com/Forums/windowsserver/en-US/7eaba8d9-2fc8-41fd-a2ef-18a8d8b9186e/failed-full-system-backup-error-2155348129?forum=windowsbackup
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Backup validate :Error

Similar Messages

Maybe you are looking for