Home » RDBMS Server » Backup & Recovery » I've got some thing wrong with my backupset RMAN (Oracle 10.2.0.1 RAC, Windows 2003 Server 64bit)
I've got some thing wrong with my backupset RMAN [message #366200] Fri, 12 December 2008 02:08 Go to next message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Oracle 10.2.0.1
Windows 2003 Server 64bit
sys@RATING> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE    10.2.0.1.0      Production
TNS for 64-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

sys@RATING>

And my database is RAC, 2 nodes are current running normaly
sys@RATING>host crs_stat -t
Name           Type           Target    State     Host
------------------------------------------------------------
ora....SM1.asm application    ONLINE    ONLINE    ora-01
ora....01.lsnr application    ONLINE    ONLINE    ora-01
ora.ora-01.gsd application    ONLINE    ONLINE    ora-01
ora.ora-01.ons application    ONLINE    ONLINE    ora-01
ora.ora-01.vip application    ONLINE    ONLINE    ora-01
ora....SM2.asm application    ONLINE    ONLINE    ora-02
ora....02.lsnr application    ONLINE    ONLINE    ora-02
ora.ora-02.gsd application    ONLINE    ONLINE    ora-02
ora.ora-02.ons application    ONLINE    ONLINE    ora-02
ora.ora-02.vip application    ONLINE    ONLINE    ora-02
ora.rating.db  application    ONLINE    ONLINE    ora-02
ora....g1.inst application    ONLINE    ONLINE    ora-01
ora....g2.inst application    ONLINE    ONLINE    ora-02

sys@RATING>


Hi all!
Today, when I review my backupset, I were very suprised, when I force to run the level 0 backupset, it was successfully.
But, when I crosscheck them, I found that

C:\>rman target sys/dielippen@rating

Recovery Manager: Release 10.2.0.1.0 - Production on Fri Dec 12 14:31:44 2008

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: RATING (DBID=2199254731)


RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'D:\arc_backup\arc_%d_%s_%p.bkp';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\BACKUP\CONTROLFILE\SNAPSHOT_RATING.F';

RMAN> crosscheck backup;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1074 instance=rating1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=985 instance=rating1 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267658_292_1.BKP recid=28
9 stamp=673267658
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267678_294_1.BKP recid=29
3 stamp=673267680
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673277297_298_1.BKP recid=29
5 stamp=673277297
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673277319_300_1.BKP recid=29
6 stamp=673277319
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673277340_301_1.BKP recid=29
7 stamp=673277340
Crosschecked 5 objects

crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267698_293_1.BKP recid=28
8 stamp=673267698
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267717_295_1.BKP recid=29
0 stamp=673267720
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673272003_296_1.BKP recid=29
1 stamp=673272004
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673272005_297_1.BKP recid=29
2 stamp=673272005
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=D:\BACKUP\WEEKLY\LEVEL_0_RATING_673277336_299_1.BKP recid=29
4 stamp=673277337
Crosschecked 5 objects

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found

RMAN>


-- I really did not understand why some of them was marked as expiration
RMAN> list backup of database;


List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
286     Incr 0  13.29G     DISK        01:11:23     12-DEC-08
        BP Key: 290   Status: EXPIRED  Compressed: YES  Tag: TAG20081212T104837
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267717_295_1.BKP
  List of Datafiles in backup set 286
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  4    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/undotbs2.263.66212342
7
  6    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/subadmin
  8    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/prepaid
  9    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/fundial
  10   0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/neo
  11   0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/lstb

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
289     Incr 0  34.04G     DISK        02:39:58     12-DEC-08
        BP Key: 293   Status: AVAILABLE  Compressed: YES  Tag: TAG20081212T10483
7
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267678_294_1.BKP
  List of Datafiles in backup set 289
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1    0  Incr 24357584057 12-DEC-08 +DATA/rating/datafile/system.259.662123415
  2    0  Incr 24357584057 12-DEC-08 +DATA/rating/datafile/undotbs1.260.66212342
1
  3    0  Incr 24357584057 12-DEC-08 +DATA/rating/datafile/sysaux.261.662123423
  5    0  Incr 24357584057 12-DEC-08 +DATA/rating/datafile/users.264.662123429
  7    0  Incr 24357584057 12-DEC-08 +DATA/rating/datafile/subhist

RMAN> validate backupset 290;

using channel ORA_DISK_1
using channel ORA_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of validate command at 12/12/2008 13:36:11
RMAN-06160: no backup pieces found for backup set key: 290


-- You see above code, the backupset with key 290 was not found because it was marked as expiration.

RMAN> list expired backup;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
284     7.97M      DISK        00:00:01     12-DEC-08
        BP Key: 288   Status: EXPIRED  Compressed: YES  Tag: RATING_LEVEL_0
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267698_293_1.BKP

  List of Archived Logs in backup set 284
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  2    17147   24357118670 12-DEC-08 24357577359 12-DEC-08

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
286     Incr 0  13.29G     DISK        01:11:23     12-DEC-08
        BP Key: 290   Status: EXPIRED  Compressed: YES  Tag: TAG20081212T104837
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673267717_295_1.BKP
  List of Datafiles in backup set 286
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  4    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/undotbs2.263.66212342
7
  6    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/subadmin
  8    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/prepaid
  9    0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/fundial
  10   0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/neo
  11   0  Incr 24357584143 12-DEC-08 +DATA/rating/datafile/lstb

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
287     Incr 0  2.81M      DISK        00:00:02     12-DEC-08
        BP Key: 291   Status: EXPIRED  Compressed: YES  Tag: TAG20081212T104837
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673272003_296_1.BKP
  Control File Included: Ckp SCN: 24358427922   Ckp time: 12-DEC-08

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
288     Incr 0  80.00K     DISK        00:00:00     12-DEC-08
        BP Key: 292   Status: EXPIRED  Compressed: YES  Tag: TAG20081212T104837
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673272005_297_1.BKP
  SPFILE Included: Modification time: 11-DEC-08

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
290     31.29M     DISK        00:00:06     12-DEC-08
        BP Key: 294   Status: EXPIRED  Compressed: YES  Tag: RATING_LEVEL_0
        Piece Name: D:\BACKUP\WEEKLY\LEVEL_0_RATING_673277336_299_1.BKP

  List of Archived Logs in backup set 290
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  2    17148   24357577359 12-DEC-08 24358498994 12-DEC-08
  2    17149   24358498994 12-DEC-08 24359179364 12-DEC-08


RMAN> exit


-- Hmm, I must query to find something wrong
Recovery Manager complete.

C:\>sqlplus sys/dielippen@rating as sysdba

SQL*Plus: Release 10.2.0.1.0 - Production on Fri Dec 12 14:18:43 2008

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options

sys@RATING> select to_char(sysdate,'DD-MM-YYYY HH24:MI:SS') from dual;

TO_CHAR(SYSDATE,'DD-MM-YYYYHH
---------------------------------------------------------------------------
12-12-2008 14:19:00

sys@RATING> SELECT   bs.recid bs_key,
  2           DECODE (backup_type,
  3                   'L', 'Archived Logs',
  4                   'D', 'Datafile Full',
  5                   'I', 'Incremental'
  6                  ) backup_type,
  7           device_type device_type,
  8           DECODE (bs.controlfile_included,
  9                   'NO', NULL,
 10                   bs.controlfile_included
 11                  ) controlfile_included,
 12           sp.spfile_included spfile_included,
 13           bs.incremental_level incremental_level, bs.pieces pieces,
 14           TO_CHAR (bs.start_time, 'mm/dd/yy HH24:MI:SS') start_time,
 15           TO_CHAR (bs.completion_time, 'mm/dd/yy HH24:MI:SS') completion_tim
e,
 16           bs.elapsed_seconds elapsed_seconds, bp.tag tag,
 17           bs.block_size block_size
 18      FROM v$backup_set bs,
 19           (SELECT DISTINCT set_stamp, set_count, tag, device_type
 20                       FROM v$backup_piece
 21                      WHERE status IN ('A', 'X')) bp,
 22           (SELECT DISTINCT set_stamp, set_count, 'YES' spfile_included
 23                       FROM v$backup_spfile) sp
 24     WHERE bs.set_stamp = bp.set_stamp
 25       AND bs.set_count = bp.set_count
 26       AND bs.set_stamp = sp.set_stamp(+)
 27       AND bs.set_count = sp.set_count(+)
 28  ORDER BY bs.recid
 29  /

BS_KEY	BACKUP_TYPE	DEVICE_TYPE	CONTROLFILE_INCLUDED	SPFILE_INCLUDED	INCREMENTAL_LEVEL	PIECES	START_TIME	COMPLETION_TIME	ELASPED_SECONDS	TAG	BLOCK_SIZE
284	Archived Logs 	DISK 	    	    	                                      	1	12/12/2008 10:48	12/12/2008 10:48	1	RATING_LEVEL_0     	512
285	Archived Logs 	DISK 	    	    	                                      	1	12/12/2008 10:47	12/12/2008 10:47	12	RATING_LEVEL_0     	512
286	Datafile Full 	DISK 	    	    	0	1	12/12/2008 10:48	12/12/2008 12:00	4283	TAG20081212T104837 	8192
287	Datafile Full 	DISK 	YES 	    	0	1	12/12/2008 12:00	12/12/2008 12:00	2	TAG20081212T104837 	16384
288	Datafile Full 	DISK 	    	YES 	0	1	12/12/2008 12:00	12/12/2008 12:00	0	TAG20081212T104837 	16384
289	Datafile Full 	DISK 	    	    	0	1	12/12/2008 10:47	12/12/2008 13:27	9598	TAG20081212T104837 	8192
290	Archived Logs 	DISK 	    	    	                                      	1	12/12/2008 13:28	12/12/2008 13:29	6	RATING_LEVEL_0     	512
291	Archived Logs 	DISK 	    	    	                                      	1	12/12/2008 13:28	12/12/2008 13:28	22	RATING_LEVEL_0     	512
292	Archived Logs 	DISK 	    	    	                                      	1	12/12/2008 13:28	12/12/2008 13:28	15	RATING_LEVEL_0     	512
293	Datafile Full 	DISK 	YES 	    	                                      	1	12/12/2008 13:29	12/12/2008 13:29	2	TAG20081212T132939 	16384

sys@RATING>


Nothing wrong occurred with my backupset. Why have somes of them been being marked as expiration?

May you clarify more?

P/S:
-- I've just clear the RMAN's configuration lines with SBT_TAPE, and I created a new tablespace, so that, I force to run backup full.
-- And this is the rman's code to backup level 0.
run{
allocate channel d1 type disk format
'D:\backup\weekly\Level_0_%d_%t_%s_%p.bkp'
connect 'sys/dielippen@rating1';
allocate channel d2 type disk format
'D:\backup\weekly\Level_0_%d_%t_%s_%p.bkp'
connect 'sys/dielippen@rating2';
backup as compressed backupset incremental level 0 database
plus archivelog delete input
tag=RATING_LEVEL_0
filesperset 6;
backup current controlfile;
crosscheck backup;
delete obsolete;
delete expired backup;
release channel d1;
release channel d2;
}


Re: I've got some thing wrong with my backupset RMAN [message #366266 is a reply to message #366200] Fri, 12 December 2008 08:51 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
It would appear that the EXPIRED backupsets were deleted from disk. Check your filesystem for the backupsets marked as EXPIRED.
Re: I've got some thing wrong with my backupset RMAN [message #376068 is a reply to message #366266] Mon, 15 December 2008 22:25 Go to previous message
trantuananh24hg
Messages: 668
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Thank you for your reply!

That's my mistake!
Because my script to backup in both of node, the day RMAN ran, someone erased one backup_piece in one node by OS command. And I found that, then I re-backup, it's normally today.

Thanks again!
Previous Topic: deleting the flashback recovery area and the files
Next Topic: Test a backup copy
Goto Forum:
  


Current Time: Sun Dec 11 08:23:11 CST 2016

Total time taken to generate the page: 0.08003 seconds