Re: NTBACKUP error

Have you always had this error when backing up this system, particularly the Oracle datafiles .DBFs ?

Are you putting the oracle tablespaces in backup mode before doing the tape backup if you are doing a hot backup ?

It looks like NT backup is noticing these files have changed since the start of the backup which they will be doing if the database is opened. What you can do is do a restore on another box and do a database recovery. If the database tablespaces are in backup mode whilst this is in process it would have been logging whole blocks to allow recovery of the datafiles. Best way would be to do a test restore on a test box and see if can restore the database up to the most recent archived log available from the restored data.

More details on your backup strategy will also help. Looking at your alert log, I can't see anything bad and can see the database shutdown and startup. Is this a cold backup (you are shutting down the database before starting the NTbackup to tape/disk ?)

If this is a cold backup, look at the alert log, we can see that the database started the dismount of the database at Fri Aug 14 04:22:52 2009, did the tape backup start after this or before this ?

Essentially I would check if you are doing a cold backup if the database was shut down before the tape backup started which could explain the errors.

regards
Vin

On Aug 15, 10:36 am, pinchol <pinch..._at_gmail.com> wrote:
> I am facing this issue when i perform full ntsystem backup using
> adimistrator account for backup.
>
> WARNING: Portions of "\oracle\oradata\orcl\SAIBGNL_INDX02.DBF" cannot
> be read.  The backed up data is corrupt or incomplete.
> This file will not restore correctly.
> WARNING: Portions of "\oracle\oradata\orcl\SAIBGNL_TEMP01.DBF" cannot
> be read.  The backed up data is corrupt or incomplete.
> This file will not restore correctly.
> WARNING: Portions of "\oracle\oradata\orcl\SAIBGNL_TEMP02.DBF" cannot
> be read.  The backed up data is corrupt or incomplete.
> This file will not restore correctly.
> WARNING: Portions of "\oracle\oradata\orcl\SAIBGNL_TEMP03.DBF" cannot
> be read.  The backed up data is corrupt or incomplete.
> This file will not restore correctly.
> WARNING: Portions of "\oracle\oradata\orcl\SAIBLOG_DATA01.DBF" cannot
> be read.  The backed up data is corrupt or incomplete.
> This file will not restore correctly.
>
> Alert Log
> Fri Aug 14 04:20:24 2009
> SMON: enabling tx recovery
> Fri Aug 14 04:20:24 2009
> Database Characterset is AR8MSWIN1256
> replication_dependency_tracking turned off (no async multimaster
> replication found)
> Completed: alter database open
> Fri Aug 14 04:22:51 2009
> Shutting down instance: further logons disabled
> Shutting down instance (immediate)
> License high water mark = 1
> Fri Aug 14 04:22:52 2009
> ALTER DATABASE CLOSE NORMAL
> Fri Aug 14 04:22:52 2009
> SMON: disabling tx recovery
> SMON: disabling cache recovery
> Fri Aug 14 04:22:52 2009
> Shutting down archive processes
> Archiving is disabled
> Archive process shutdown avoided: 0 active
> Thread 1 closed at log sequence 67613
> Successful close of redo thread 1
> Fri Aug 14 04:22:52 2009
> Completed: ALTER DATABASE CLOSE NORMAL
> Fri Aug 14 04:22:52 2009
> ALTER DATABASE DISMOUNT
> Completed: ALTER DATABASE DISMOUNT
> ARCH: Archiving is disabled
> Shutting down archive processes
> Archiving is disabled
> Archive process shutdown avoided: 0 active
> ARCH: Archiving is disabled
> Shutting down archive processes
> Archiving is disabled
> Archive process shutdown avoided: 0 active
> Dump file d:\oracle\admin\orcl\bdump\alert_orcl.log
> Fri Aug 14 05:21:29 2009
> ORACLE V9.2.0.5.0 - Production vsnsta=0
> vsnsql=12 vsnxtr=3
> Windows 2000 Version 5.0 Service Pack 4, CPU type 586
> Fri Aug 14 05:21:29 2009
> Starting ORACLE instance (normal)
> LICENSE_MAX_SESSION = 0
> LICENSE_SESSIONS_WARNING = 0
> SCN scheme 2
> Using log_archive_dest parameter default value
> LICENSE_MAX_USERS = 0
> SYS auditing is disabled
> Starting up ORACLE RDBMS Version: 9.2.0.5.0.
> System parameters with non-default values:
>   processes                = 1021
>   timed_statistics         = TRUE
>   event                    = 10511 trace name context forever, level
> 2, 10841 trace name context forever
>   shared_pool_size         = 528482304
>   large_pool_size          = 16777216
>   java_pool_size           = 16777216
>   enqueue_resources        = 8000
>   control_files            = D:\oracle\oradata\orcl\control01.ctl, D:
> \oracle\oradata\orcl\control02.ctl, D:\oracle\oradata\orcl
> \control03.ctl
>   db_block_size            = 8192
>   db_writer_processes      = 2
>   db_cache_size            = 1048576000
>   compatible               = 9.2.0.5.0
>   log_buffer               = 10485760
>   log_checkpoint_interval  = 5242880
>   log_checkpoint_timeout   = 1800
>   db_files                 = 512
>   db_file_multiblock_read_count= 16
>   fast_start_mttr_target   = 300
>   log_checkpoints_to_alert = TRUE
>   dml_locks                = 2000
>   undo_management          = AUTO
>   undo_tablespace          = UNDOTBS1
>   undo_retention           = 10800
>   max_enabled_roles        = 96
>   O7_DICTIONARY_ACCESSIBILITY= TRUE
>   remote_login_passwordfile= EXCLUSIVE
>   db_domain                =
>   global_names             = FALSE
>   instance_name            = orcl
>   utl_file_dir             = *
>   cursor_sharing           = FORCE
>   background_dump_dest     = D:\oracle\admin\orcl\bdump
>   user_dump_dest           = D:\oracle\admin\orcl\udump
>   core_dump_dest           = D:\oracle\admin\orcl\cdump
>   sort_area_size           = 1572864
>   sort_area_retained_size  = 65536
>   db_name                  = orcl
>   open_cursors             = 5000
>   star_transformation_enabled= FALSE
>   query_rewrite_enabled    = FALSE
>   pga_aggregate_target     = 524288000
> PMON started with pid=2
> DBW0 started with pid=3
> DBW1 started with pid=4
> LGWR started with pid=5
> CKPT started with pid=6
> SMON started with pid=7
> RECO started with pid=8
> Fri Aug 14 05:21:33 2009
> alter database mount exclusive
> Fri Aug 14 05:21:38 2009
> Successful mount of redo thread 1, with mount id 1222658013
> Fri Aug 14 05:21:38 2009
> Database mounted in Exclusive Mode.
> Completed: alter database mount exclusive
> Fri Aug 14 05:21:38 2009
> alter database open
> Fri Aug 14 05:21:40 2009
> Thread 1 opened at log sequence 67613
>   Current log# 3 seq# 67613 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO03A.LOG
>   Current log# 3 seq# 67613 mem# 1: D:\ORACLE\ORADATA\ORCL\REDO03B.LOG
> Successful open of redo thread 1
> Fri Aug 14 05:21:40 2009
> LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
> Fri Aug 14 05:21:40 2009
> SMON: enabling cache recovery
> Fri Aug 14 05:21:42 2009
> Undo Segment 1 Onlined
> Undo Segment 2 Onlined
> Undo Segment 3 Onlined
> Undo Segment 4 Onlined
> Undo Segment 5 Onlined
> Undo Segment 6 Onlined
> Undo Segment 7 Onlined
> Undo Segment 8 Onlined
> Undo Segment 9 Onlined
> Undo Segment 10 Onlined
> Successfully onlined Undo Tablespace 1.
> Fri Aug 14 05:21:42 2009
> SMON: enabling tx recovery
> Fri Aug 14 05:21:42 2009
> Database Characterset is AR8MSWIN1256
> replication_dependency_tracking turned off (no async multimaster
> replication found)
> Completed: alter database open
> Sat Aug 15 07:32:24 2009
> Beginning log switch checkpoint up to RBA [0x1081e.2.10], SCN:
> 0x0000.81bc2ea0
> Thread 1 advanced to log sequence 67614
>   Current log# 4 seq# 67614 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO04A.LOG
>   Current log# 4 seq# 67614 mem# 1: D:\ORACLE\ORADATA\ORCL\REDO04B.LOG
>
> Can anyone help me in this matter.
Received on Sun Aug 16 2009 - 09:25:12 CDT