Query to check how far RMAN backup completed?
is there a way to check how far RMAN backup been completed. What is through put etc.
Let me know if you know any.
Thanks,
RK
Additional info...Monitoring RMAN Through V$ Views and Query V$ Views to Identify Bottlenecks.
Similar Messages
-
How to RMAN backup in RAC with OCFS
hi,
Iam using RAC 10.2.0 in windows 2003 server with OCFS .. i want to take backup using RMAN utility. can any sugest me how take RMAN backup..
Thanks
harishThe only real consideration in RMAN on RAC is a one-off configuration issue as to whether the snapshot controlfile is written to the shared disk or not (it needs to be on the shared disk, or on a location that is common to all nodes, otherwise a backup that includes the control file will fail at the point a node tries to write it to a destination directory that only made sense to another node).
Otherwise, there's not a lot that's different about an RMAN backup in RAC versus non-RAC.
Simple answer, as a result: open a DOS window, type rman target /, then type backup database; -
Long sys session active after rman backup completed
Hi all,
We use Oracle DB 11g in RAC and the Rman backups running on SLES 11 SP1.
All days the backup jobs are executed normally, but, sometimes some SYS sessions (used during the backup, i think) remains ACTIVE by hours (day, weeks...)
At this moment, we have 3 sessions running (actives) since Nov, 04. Their LOGON_TIME is the same backup job start time.
The current statement is empty. I think that is relationed with the backup Job. The processes are ORAOxxx and there are sessions in ASM instance with the same LOGON_TIME.
What can we DO? Kill these sessions?
The last time we restarted the Oracle DB instance, but the "zombies" sessions came back soon, after a backup job. :(
Thanks!Thanks,
but I know how to query the sessions, I use Gv$session because it´s an oracle cluster.
I Want to Know: What do we have to do with the long sessions? To kill? Simply?
--> Below the query to see the sessions:
'ACTIVE' or 'INACTIVE':
SELECT 'kill -9 '
|| b.spid
|| ' # '
|| a.inst_id
|| ' - '
|| a.username
|| ' - '
|| a.program
|| ' - '
|| TO_CHAR (a.logon_time, 'DD-MM-YYYY HH24:MI:SS')
|| ' - '
|| TRUNC (a.last_call_et / 60 / 60, 0)
|| ' horas - '
|| a.status
FROM gv$session a, gv$process b
WHERE a.username IS NOT NULL
AND a.last_call_et / 60 / 60 > 4
AND a.status = 'INACTIVE'
AND a.paddr = b.addr
AND a.inst_id = 1
ORDER BY a.last_call_et DESC
---------- The result is:
kill -9 20516 # 3 - SYS - oracle@art (O003) - 04-11-2011 01:07:51 - 88 horas - ACTIVE
kill -9 26562 # 3 - SYS - oracle@art (O003) - 04-11-2011 01:07:51 - 88 horas - ACTIVE
kill -9 13213 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
kill -9 26021 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
kill -9 21749 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
kill -9 1844 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
kill -9 2214 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
kill -9 21759 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE -
How is RMAN backup different than the other conventional methods of backup
Hello to all,
I have a question if somebody can please answer my queries
How & Why is RMAN backup different than the other conventional methods of backup.
What is different in the way a database is backed up using RMAN.
I am very well aware of the capabilites of RMAN to recover from a loss , but I did like to know as to how RMAN makes it possible to go about it.
Please answer
AltafYou can start with the reading of the Oracle docs:
Backup and Recovery Basics
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/toc.htm
Backup and Recovery Quick Start Guide
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm
Backup and Recovery Reference
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/toc.htm -
How to find out when last rman backup was made in 9i
Hello,
i have an oracle 9i database running on windows here. Is there a way to find out when the last rman backup was done with a sql query?
I would like to create a job inside the database that regulary checks if a rman backup ran sucessfully instead of using scripts in the operating system.
But i only know about commands in the rman utility (that i can not execute as a job, right?) - is something similar possible with for example sqlplus?Hello,
this gives some results, but none of the views begins with RC:
ALL_DIM_HIERARCHIES
ALL_SOURCE
ALL_SOURCE_TABLES
ALL_SOURCE_TAB_COLUMNS
DBA_DIM_HIERARCHIES
DBA_RCHILD
DBA_REGISTRY_HIERARCHY
DBA_RSRC_CONSUMER_GROUPS
DBA_RSRC_CONSUMER_GROUP_PRIVS
DBA_RSRC_MANAGER_SYSTEM_PRIVS
DBA_RSRC_PLANS
DBA_RSRC_PLAN_DIRECTIVES
DBA_SOURCE
DBA_SOURCE_TABLES
DBA_SOURCE_TAB_COLUMNS
USER_DIM_HIERARCHIES
USER_RESOURCE_LIMITS
USER_RSRC_CONSUMER_GROUP_PRIVS
USER_RSRC_MANAGER_SYSTEM_PRIVS
USER_SOURCE
Edited by: user590072 on 22.06.2010 05:49 -
How to find the compression algorithm used on a RMAN Backup
I have list of backups taken using different compression alogrithms. I need to query and find out the compression algorithm used on existing RMAN Backup. I tried querying the view V$RMAN_BACKUP_JOB_DETAILS.
For Example I ran script below for backing up database with compressed backupsets;
On RMAN
connect target /
connect catalog rman/sqw1298@rcat
set COMPRESSION ALGORITHM 'HIGH'
backup filesperset 1 format '<%d_%s:%t:%p:%f>.df' incremental level 0 database;Edited by: Sivaprasad S on Sep 1, 2012 12:32 AM
Edited by: Sivaprasad S on Sep 1, 2012 12:36 AMI used the query below to get the RMAN backup details, here I am missing detail of compression algorithm
SELECT SESSION_KEY, INPUT_TYPE, STATUS,
TO_CHAR(START_TIME,'mm/dd/yy hh24:mi') start_time,
TO_CHAR(END_TIME,'mm/dd/yy hh24:mi') end_time,
ELAPSED_SECONDS/3600 hrs,
COMPRESSION_RATIO ,
INPUT_BYTES_DISPLAY, OUTPUT_BYTES_DISPLAY, TIME_TAKEN_DISPLAY
FROM V$RMAN_BACKUP_JOB_DETAILS
ORDER BY SESSION_KEY;Output
SESSION_KEY INPUT_TYPE STATUS START_TIME END_TIME HRS COMPRESSION_RATIO INPUT_BYTE OUTPUT_BYTES_DI TIME_TAKEN_DISP
417 DB INCR COMPLETED 8/23/2012 16:01 8/23/2012 16:33 0.529444444 1.06917899 244.67G 228.84G 0:31:46
423 DB INCR COMPLETED 8/23/2012 16:43 8/23/2012 17:14 0.510277778 1.0692043 244.59G 228.76G 0:30:37
435 DB INCR COMPLETED 8/24/2012 11:39 8/24/2012 12:13 0.571666667 1.06899247 244.64G 228.85G 0:34:18
441 DB INCR COMPLETED 8/24/2012 13:52 8/24/2012 14:23 0.511666667 1.0690053 244.60G 228.81G 0:30:42
447 DB INCR COMPLETED 8/24/2012 16:30 8/24/2012 16:58 0.467222222 2609.07178 244.60G 96.00M 0:28:02
457 DB INCR COMPLETED 8/25/2012 12:30 8/25/2012 13:01 0.527222222 1.06896188 244.68G 228.90G 0:31:38
467 DB INCR COMPLETED 8/26/2012 16:30 8/26/2012 16:56 0.4325 739.556573 244.65G 338.75M 0:25:57On the output I need to have the compression algorithm used for each backup.
Hope this is crystal clear now. -
I have one 10g SE database running on Linux x86_64; I have migrated this database resently with upgrade;
I used export-import utilities for perform this task;
Some information about this database:
OS version: "Linux xxx.qqq.ru 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux"
SQL> select * from v$version;
BANNER
Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
I noticed that rman perform backup operation too long; For example here I place piece of rman log from one database backup operation:
executing script: backup_db_nfs
allocated channel: nfs
channel nfs: sid=1275 devtype=DISK
Starting backup at 31-07-10 04:00:04
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00028 name=/db/u12/oradata/billing/excellent_02.dbf
input datafile fno=00030 name=/db/u12/oradata/billing/excellent_04.dbf
input datafile fno=00032 name=/db/u12/oradata/billing/excellent_06.dbf
input datafile fno=00034 name=/db/u12/oradata/billing/excellent_08.dbf
input datafile fno=00029 name=/db/u11/oradata/billing/excellent_03.dbf
input datafile fno=00031 name=/db/u11/oradata/billing/excellent_05.dbf
input datafile fno=00033 name=/db/u11/oradata/billing/excellent_07.dbf
input datafile fno=00035 name=/db/u11/oradata/billing/excellent_09.dbf
channel nfs: starting piece 1 at 31-07-10 04:00:05
channel nfs: finished piece 1 at 31-07-10 04:34:21
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 04:34:21
channel nfs: finished piece 2 at 31-07-10 05:08:36
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 3 at 31-07-10 05:08:36
channel nfs: finished piece 3 at 31-07-10 07:38:43
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2615.3.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:38
channel nfs: throttle time: 3:###:42
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00036 name=/db/u12/oradata/billing/excellent_10.dbf
input datafile fno=00038 name=/db/u12/oradata/billing/excellent_12.dbf
input datafile fno=00040 name=/db/u12/oradata/billing/excellent_14.dbf
input datafile fno=00042 name=/db/u12/oradata/billing/excellent_16.dbf
input datafile fno=00037 name=/db/u11/oradata/billing/excellent_11.dbf
input datafile fno=00039 name=/db/u11/oradata/billing/excellent_13.dbf
input datafile fno=00041 name=/db/u11/oradata/billing/excellent_15.dbf
input datafile fno=00043 name=/db/u11/oradata/billing/excellent_17.dbf
channel nfs: starting piece 1 at 31-07-10 07:38:43
channel nfs: finished piece 1 at 31-07-10 08:13:18
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 08:13:18
channel nfs: finished piece 2 at 31-07-10 08:47:24
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 3 at 31-07-10 08:47:24
channel nfs: finished piece 3 at 31-07-10 11:17:20
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2636.3.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:37
channel nfs: throttle time: 3:###:59
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00044 name=/db/u12/oradata/billing/excellent_18.dbf
input datafile fno=00046 name=/db/u12/oradata/billing/excellent_20.dbf
input datafile fno=00047 name=/db/u12/oradata/billing/index_all_02.dbf
input datafile fno=00049 name=/db/u12/oradata/billing/index_all_04.dbf
input datafile fno=00045 name=/db/u11/oradata/billing/excellent_19.dbf
input datafile fno=00048 name=/db/u11/oradata/billing/index_all_03.dbf
input datafile fno=00050 name=/db/u11/oradata/billing/index_all_05.dbf
input datafile fno=00052 name=/db/u11/oradata/billing/index_all_07.dbf
channel nfs: starting piece 1 at 31-07-10 11:17:20
channel nfs: finished piece 1 at 31-07-10 12:16:46
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2655.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 31-07-10 12:16:46
channel nfs: finished piece 2 at 31-07-10 14:55:53
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2655.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:33
channel nfs: throttle time: 3:###:02
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00051 name=/db/u12/oradata/billing/index_all_06.dbf
input datafile fno=00053 name=/db/u12/oradata/billing/index_all_08.dbf
input datafile fno=00055 name=/db/u12/oradata/billing/index_all_10.dbf
input datafile fno=00057 name=/db/u12/oradata/billing/index_all_12.dbf
input datafile fno=00054 name=/db/u11/oradata/billing/index_all_09.dbf
input datafile fno=00056 name=/db/u11/oradata/billing/index_all_11.dbf
input datafile fno=00058 name=/db/u11/oradata/billing/index_all_13.dbf
input datafile fno=00060 name=/db/u11/oradata/billing/index_all_15.dbf
channel nfs: starting piece 1 at 31-07-10 14:55:53
channel nfs: finished piece 1 at 31-07-10 18:34:30
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2674.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:38:37
channel nfs: throttle time: 3:###:44
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00019 name=/db/u12/oradata/billing/excellent_big_02.dbf
input datafile fno=00021 name=/db/u12/oradata/billing/excellent_big_04.dbf
input datafile fno=00068 name=/db/u12/oradata/billing/support_excl_04.dbf
input datafile fno=00024 name=/db/u11/oradata/billing/excellent_big_07.dbf
input datafile fno=00026 name=/db/u11/oradata/billing/excellent_big_09.dbf
input datafile fno=00012 name=/db/u13/oradata/billing/pay_assist_01.dbf
input datafile fno=00004 name=/db/u13/oradata/billing/users_01.dbf
input datafile fno=00023 name=/db/u12/oradata/billing/excellent_big_06.dbf
input datafile fno=00025 name=/db/u12/oradata/billing/excellent_big_08.dbf
input datafile fno=00027 name=/db/u12/oradata/billing/excellent_big_10.dbf
channel nfs: starting piece 1 at 31-07-10 18:34:30
channel nfs: finished piece 1 at 31-07-10 21:59:27
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2695.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 03:24:57
channel nfs: throttle time: 3:###:13
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00059 name=/db/u12/oradata/billing/index_all_14.dbf
input datafile fno=00061 name=/db/u12/oradata/billing/index_all_16.dbf
input datafile fno=00063 name=/db/u12/oradata/billing/index_all_18.dbf
input datafile fno=00065 name=/db/u12/oradata/billing/index_all_20.dbf
input datafile fno=00062 name=/db/u11/oradata/billing/index_all_17.dbf
input datafile fno=00064 name=/db/u11/oradata/billing/index_all_19.dbf
input datafile fno=00015 name=/db/u12/oradata/billing/monitor_01.dbf
channel nfs: starting piece 1 at 31-07-10 21:59:27
channel nfs: finished piece 1 at 01-08-10 00:50:14
piece handle=/db/backup/billing/rman_nfs/full_20100731.BILLING.2712.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:50:47
channel nfs: throttle time: 2:###:07
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00002 name=/db/u12/oradata/billing/undotbs_01.dbf
input datafile fno=00011 name=/db/u12/oradata/billing/index_all_01.dbf
input datafile fno=00009 name=/db/u12/oradata/billing/mviewlog_01.dbf
input datafile fno=00008 name=/db/u11/oradata/billing/support_excl_01.dbf
input datafile fno=00010 name=/db/u11/oradata/billing/excellent_01.dbf
input datafile fno=00067 name=/db/u11/oradata/billing/support_excl_03.dbf
input datafile fno=00007 name=/db/u11/oradata/billing/tpcctab_01.dbf
input datafile fno=00013 name=/db/u11/oradata/billing/tpchtab_01.dbf
input datafile fno=00005 name=/db/u13/oradata/billing/web_01.dbf
input datafile fno=00006 name=/db/u13/oradata/billing/alien_users_01.dbf
channel nfs: starting piece 1 at 01-08-10 00:50:14
channel nfs: finished piece 1 at 01-08-10 02:08:00
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2729.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: starting piece 2 at 01-08-10 02:08:00
channel nfs: finished piece 2 at 01-08-10 03:40:46
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2729.2.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:50:32
channel nfs: throttle time: 2:###:12
channel nfs: starting full datafile backupset
channel nfs: specifying datafile(s) in backupset
input datafile fno=00016 name=/db/u12/oradata/billing/excellent_big_01.dbf
input datafile fno=00017 name=/db/u12/oradata/billing/monitor_lob_01.dbf
input datafile fno=00066 name=/db/u12/oradata/billing/support_excl_02.dbf
input datafile fno=00020 name=/db/u11/oradata/billing/excellent_big_03.dbf
input datafile fno=00022 name=/db/u11/oradata/billing/excellent_big_05.dbf
input datafile fno=00069 name=/db/u11/oradata/billing/support_excl_05.dbf
input datafile fno=00001 name=/db/u13/oradata/billing/system_01.dbf
input datafile fno=00003 name=/db/u13/oradata/billing/sysaux_01.dbf
input datafile fno=00018 name=/db/u13/oradata/billing/excl_addition_01.dbf
input datafile fno=00014 name=/db/u13/oradata/billing/arm_xml_01.dbf
channel nfs: starting piece 1 at 01-08-10 03:40:46
channel nfs: finished piece 1 at 01-08-10 06:02:03
piece handle=/db/backup/billing/rman_nfs/full_20100801.BILLING.2742.1.1 tag=BACKUP_DB_NFS comment=NONE
channel nfs: backup set complete, elapsed time: 02:21:17
channel nfs: throttle time: 2:###:51
Finished backup at 01-08-10 06:02:03
Size of this database:
SQL> select sum(user_bytes)/1024/1024/1024 from dba_data_files;
SUM(USER_BYTES)/1024/1024/1024
456.025085
I have another database that runs on the same hardware platform, eith the same configuration, and under the same OS. and oracle instance has the same configuration (except oracle version: there is 9.2.0.8);
Size of this, database is ~700Gb, and this database load is heavier that database with slow rman;
But on this database rman makes full-db backup in 10 hours, usually;
I read note 360443.1, and I checked - how long rman perform full database backup with validate option;
This time, practicaly, is equal database backup time ~24 hours;
Almost all database datafiles are splaced on disk array - stripe 10 and /db/u11 and /db/u12 - are mount points of two partitions created on this disk array;
/db/u13 - this is raid 5;
Now I wish to know in details - where time is spent and my question is: can anybody suggest me - what should I do for find it;Instance configuration
audit_file_dest /var/log/oracle/billing/audit
audit_sys_operations TRUE
audit_trail OS
background_dump_dest /var/log/oracle/billing/bdump
compatible 10.2.0.3.0
control_files /db/u11/oradata/billing/ctrl00.ctl, /db/u12/oradata/billing/ctrl01.ctl, /db/u00/oradata/billing/ctrl02.ctl, /db/u13/oradata/billing/ctrl03.ctl
core_dump_dest /var/log/oracle/billing/cdump
db_block_checking TRUE
db_block_checksum TRUE
db_block_size 8192
db_cache_advice ON
db_cache_size 24696061952
db_file_multiblock_read_count 64
db_keep_cache_size 3221225472
db_name billing
db_recycle_cache_size 3221225472
db_writer_processes 4
disk_asynch_io FALSE
dispatchers (protocol=tcp)(listener=mts_1522)(dispatchers=2), (protocol=tcp)(listener=mts_1523)(dispatchers=2)
filesystemio_options DIRECTIO
global_names FALSE
java_pool_size 1342177280
job_queue_processes 10
large_pool_size 536870912
lock_sga TRUE
log_archive_dest /db/archive/billing
log_archive_format %T_%S_%r.arclog
log_buffer 144326144
log_checkpoint_interval 10000
log_checkpoints_to_alert TRUE
log_checkpoint_timeout 0
max_dispatchers 5
max_dump_file_size 100M
max_shared_servers 350
nls_date_format DD.MM.RR
nls_language AMERICAN
nls_numeric_characters .,
nls_territory RUSSIA
open_cursors 1500
open_links 17
open_links_per_instance 34
optimizer_index_caching 90
optimizer_index_cost_adj 15
optimizer_mode RULE
pga_aggregate_target 24696061952
processes 1200
query_rewrite_enabled TRUE
remote_login_passwordfile EXCLUSIVE
resource_limit TRUE
session_cached_cursors 900
sessions 1500
sga_max_size 38654705664
sga_target 38654705664
shared_pool_size 3221225472
shared_servers 150
shared_server_sessions 1000
star_transformation_enabled FALSE
timed_statistics TRUE
undo_management AUTO
undo_retention 10800
undo_tablespace UNDOTBS1
user_dump_dest /var/log/oracle/billing/udump
workarea_size_policy AUTO
You can see here that parameter filesystemio_options has value DIRECTIO;
This is becouse last week I had accident on this database and, as result, I had to turn off async io for oracle;
All time before, since database mirgate moment, this parameter had value SETALL, and disk_asynch_io parameter had value true;
And rman has kept his inappropriate behaviour since this time (e.g.: since database mirgate); -
RMAN backup on the physical standby database.
Hello,
11.2.0.3 EE database. Is it a requirement to open the database in read only mode in order to take a hot backup?
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER DATABASE OPEN READ ONLY;
I've initiated a rman backup without opening the db in read only and the following output is so far:
RMAN> backup format '/dbstor2/LTS/LTS_rman/%d_set%s_piece%p_%T_%U' check logical database plus archivelog;
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
I plan on taking this backup and using it to refresh our Dev and QA dbs. Do you see any issues with taking a backup without opening the db in ready only mode?
-SteveVNo we are not using Active Dataguard. An issue I am investigating is why can't I perform an archivelog backup from the standby?
RMAN> backup archivelog all format '/dbstor2/LTS/LTS_rman/arc.rman.bak';
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 15-OCT-12 -
How to check RMAN backup report or log
Hi Guys,
I have RMAN schduled to backup my database daily.
Please what are the steps to check the report of the backup to see what was actually backed up and if it backup up ok
ThanksUse "LIST BACKUP" to display information about backup sets, proxy copies, and image copies. With LIST command you can list the following:
- Backups and copies that do not have the status AVAILABLE in the RMAN repository
- Backups and copies of datafiles that are available and can possibly be used in a restore operation
- Specified archived logs, backup sets, backup pieces, control file copies, datafile copies, and proxy copies
- Backups and copies restricted by tag, completion time, recoverability, or device
- Incarnations of a specified database or of all databases known to the repository
- Stored scripts in the recovery catalog
Examples on how to use LIST command are listed below:
RMAN> LIST BACKUP;
RMAN> LIST EXPIRED BACKUP;
RMAN> LIST BACKUP OF DATABASE;
RMAN> LIST BACKUP SUMMARY;
RMAN> LIST BACKUP BY FILE;
RMAN> LIST ARCHIVELOG ALL;
RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;
RMAN> LIST COPY OF DATAFILE 1, 2, 3;
RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437;
RMAN> LIST BACKUPSET OF DATAFILE 1;You can use the VALIDATE keyword of the BACKUP command to do the following:
- Check datafiles for physical and logical corruption
- Confirm that all database files exist and are in the correct locations
For example, you can validate that all database files and archived redo logs can be backed up by running a command as follows:
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;I suggest you read Oracle® Database Backup and Recovery Manuals:
http://www.oracle.com/pls/db102/portal.portal_db?selected=3 -
How to check the size of rman backups to tape
instead of asking tsm person to check, how do I check how big is a rman backup sent to tape?
query to find the backupset sizes
SQL> select ctime "Date"
2 , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
3 , bsize "Size MB"
4 from (select trunc(bp.completion_time) ctime
5 , backup_type
6 , round(sum(bp.bytes/1024/1024),2) bsize
7 from v$backup_set bs, v$backup_piece bp
8 where bs.set_stamp = bp.set_stamp
9 and bs.set_count = bp.set_count
10 and bp.status = 'A'
11 group by trunc(bp.completion_time), backup_type)
12 order by 1, 2;
Date BACKUP_TYPE Size MB
03-JUL-10 Archive Log 7.31
03-JUL-10 Full 29.81
03-JUL-10 Incremental 2853.85
04-JUL-10 Archive Log 3.59
04-JUL-10 Full 7.45
04-JUL-10 Incremental 3.05 -
How to check & resolve block corruption if no RMAN backup is there?
*<<+MY Findings+>>*
to check block corruption :
(run command)
select * from v$database_block_corruption;
DB_VERIFY is useful in these situations:
When block corruption is expected;
Forecast any future problems w.r.t. database file/ block corruption;
When you restore files from a tape. It will help knowing if the first file pulled from tape is corrupt, instead of spending hours to extract all of them.
to check block corruption
DBVerify
C:\>dbv userid=nfadmin/nfadmin file=+DG1/nfdb/datafile/low_s_data.304.782536883 feedback=10000 blocksize=8192
can use DBMS_REPAIR to detect and repair corrupt blocks in tables and indexes
BEGIN
DBMS_REPAIR.admin_tables (
table_name => 'REPAIR_TABLE',
table_type => DBMS_REPAIR.repair_table,
action => DBMS_REPAIR.create_action,
tablespace => 'USERS');
DBMS_REPAIR.admin_tables (
table_name => 'ORPHAN_KEY_TABLE',
table_type => DBMS_REPAIR.orphan_table,
action => DBMS_REPAIR.create_action,
tablespace => 'USERS');
END;
Question* :::how to check & resolve block corruption if no RMAN backup is there?http://www.oracle.com/technetwork/database/focus-areas/availability/maa-datacorruption-bestpractices-396464.pdf
http://www.oracle-base.com/articles/misc/detect-and-correct-corruption.php -
How to verify RMAN backup ?
How to verify and validate the RMAN backups on daily basis?One more doubt at this point - if we can't locate any RMAN script in crontab(crontab -l) but still backup is occuring regularly, how can we see the script behind this?
Thanks in advance.
Edited by: 916438 on May 27, 2012 8:47 PM916438 wrote:
How to verify and validate the RMAN backups on daily basis?One more doubt at this point - if we can't locate any RMAN script in crontab(crontab -l) but still backup is occuring regularly, how can we see the script behind this?
What you want see? If backup was executed without error or make sure that there is a valid backup on tape or disk.
So, If you want see if backup was executed successfull you must find the logs of backup or query "V$RMAN_OUTPUT" (check it on documentation).
If you want check if Database is Valid on Disk or TAPE as mentioned previously "RESTORE VALIDATE DATABASE" (check it on documentation).
Where we can locate RMAN SCRIPT? It's hard to answer.
It' your env, you should find out. The options are: Crontab / Oracle Enteprise Manager / Third-Party Backup Software / Job Scheduler.
Also you can try : Take a time of backup was executed and check on shell a time of exection of backup " ps -ef |grep rman" you will find from where script was started.
Regards,
Levi Pereira -
Manually check the rman backup output
Can anybody guide me how to manually check the rman backup output,
There are like 300+ DBs and we are using recovery catalog .....
Plz send me some example to do that....like i have to check list, report or rman logs?1) set environment variable
$ export NLS_DATE_FORMAT='DD-MON-YYYY HH24:MI:SS'
RMAN> connect target * connect catalog *
RMAN> list backup summary;
RMAN> list backup of database completed between "to_date('2007-12-20 03:00:00','YYYY-MM-DD HH24:MI:
SS')" and "to_date('2007-12-20 06:00:00','YYYY-MM-DD HH24:MI:SS')";
My manager ask me to check rman backup report manually & this is what i am forwarding him that i will check , let me know if its not right........ -
RMAN backup files are still exist since long time, how to delete?
Dear sir;
I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
============Daily RMAN script=========
rman target /<<!
backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
backup current controlfile format '/u15/rman/control_%U.rman';
delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
delete noprompt obsolete;
================================END
Thanks and best regards
AliHi;
Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
All files are exist in /u15/rman/
-rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
-rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
-rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
-rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
-rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
-rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
-rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
-rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
-rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
-rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
-rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
-rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
-rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
-rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
-rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
-rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
-rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
-rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
-rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
-rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
above is a short list of contents.
to do our daily backup we perform the following script (in daily)
==================
backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
backup current controlfile format '/u15/rman/control_%U.rman';
delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
delete noprompt obsolete;
==================
Thanks and best regards
Ali -
How to restore a Rman backup from Tape
Hi,
We need to restore the database backup taken through RMAN on 24-JUNE-2013 from tape as this backup is not currently available on disk.
Can you please help me on the following,
1) how i can check if the same backup on 24-JUNE-2013 is available on Tape.
2) If yes how i can restore to Disk.
Because we need to create a new Clone instance from the backup taken on 24-JUNE-2013.
We are having 12.1.3 Application on Exalogic and 11.2.0.3 Database on Exadata machine.
Our support is highly appreciated.
Thanksuser11969666 wrote:
Hi,
We need to restore the database backup taken through RMAN on 24-JUNE-2013 from tape as this backup is not currently available on disk.
Can you please help me on the following,
1) how i can check if the same backup on 24-JUNE-2013 is available on Tape.
2) If yes how i can restore to Disk.
Because we need to create a new Clone instance from the backup taken on 24-JUNE-2013.
We are having 12.1.3 Application on Exalogic and 11.2.0.3 Database on Exadata machine.
Our support is highly appreciated.
Thanks
Your questions are answered in the Backup and Recovery User's Guide -- Contents
Thanks,
Hussein
Maybe you are looking for
-
HOW CAN I TRANSFER MY SONGS FROM OLD COMPUTER TO NEW???? PLEASE READ
MY OLD COMPUTER IS TOO SLOW AND I NEED MY SONGS TO GO ON MT NEW LAPTOP (YAY ME)... I DONT WANT TO WASTE A MILLION CD'S JUST TO GET MY NEW SONGS ON THERE SO WHAT CAN I DO....I TRIED USING A JUMO DRIVE AND THAR DOESNT WORK EITHER CUZ AS AS SOON AS I DI
-
Question about entries in 3KEH table
Hello gurus, I would like to ask you 1 thing, there are more than 4000 entries in table 3KEH but nowm the customer asked me to enter only range fromm 1000000000 to 2999999999. Which means I need to delete all the entries and then place this range, Bu
-
Just got my Macbook this week and was looking forward to the "lightening" fast MAc I had heard of. It is not so ! My old PC wa faster an cost about a quarter of the price !! Am I doing something wrong ?
-
Way to retrieve report ID / CUID within crystal report?
Hello, Is there a way I can retrieve the report ID / CUID / something unique within CR for a report that is stored on BOE? Similiar to how the currentCEUserID function pulls for user? Thanks...
-
Hide/Show Dynamic Action Stopped Working
Good Morning, Once I upgraded my application to Apex 4.2.2, my dynamic action stopped working. It worked fine in 4.1. I also used javascript to hide/show my fields. code below <script language="JavaScript" type="text/javascript"> function onPgLoad()