Skip to main content

Querying V$ Views to Obtain Backup Information

Querying V$ Views to Obtain Backup Information

Before making a backup, you must identify all the files in your database and decide what to back up. Several V$ views can provide the necessary information.

Listing Database Files Before a Backup


select name from v$datafile
union all
select member from v$logfile
union all
select name from v$controlfile;


Determining Datafile Status for Online Tablespace Backups

You can check V$BACKUP views to determine datafile is part of backup or not.
it is also usefull when you database startup after instance failure through this view you can know datafile is part of online backup when database is open.

V$backup view is not useful when current controlfile is created from restored backup or RE-CREATE statment becuase it is not content information about backup datafile.

Through below query we can know status of datafile backup status

SELECT t.name AS "TB_NAME", d.file# as "DF#", d.name AS "DF_NAME", b.status
FROM V$DATAFILE d, V$TABLESPACE t, V$BACKUP b
WHERE d.TS#=t.TS#
AND b.FILE#=d.FILE#
AND b.STATUS='ACTIVE'

Comments

Popular posts from this blog

CLSRSC-430: Failed to start rolling patch mode

############################################################ GRID PSU Failed on Node2: =========================== [root@server1 tmp]# /oracrs/oracle/product/12102/OPatch/opatchauto apply /path1/patches/23273629 -oh /oracrs/oracle/product/12102 -ocmrf /tmp/ocm.rsp OPatch Automation Tool Copyright (c)2014, Oracle Corporation. All rights reserved. OPatchauto Version : 12.1.0.1.10 OUI Version        : 12.1.0.2.0 Running from       : /oracrs/oracle/product/12102 opatchauto log file: /oracrs/oracle/product/12102/cfgtoollogs/opatchauto/23273629/opatch_gi_2016-11-25_06-13-44_deploy.log Parameter Validation: Successful Configuration Validation: Successful Patch Location: /path1/patches/23273629 Grid Infrastructure Patch(es): 21436941 23054246 23054327 23054341 DB Patch(es): 23054246 23054327 The following patch(es) are duplicate patches with patches installed in the Oracle Home.  [ 20299023] You hav...

ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device

Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device (Doc ID 301830.1) Issue: ====== ORA-27102: out of memory Linux-x86_64 Error: 28: No space left on device Solution: ========= 1. Ask SA to increase "kernel.shmall" in /etc/sysctl.conf     Formula:     RAM * 1024 * 1024 * 1024 / page_size     Ex:-     RAM = 50GB     $getconf PAGE_SIZE ==> 4096     50*1024*1024*1024/4096 = 13107200 ==> kernel.shmall 2. After updating kernel.shmall, ask SA to do "sysctl -p" to activate changes. 3. Start the DB Note: ==== Kernel values will be set in below files 1. Updating below files doesn't require system reboot.     /proc/sys/kernel/shmmax     /proc/sys/kernel/shmall     /proc/sys/kernel/shmmni     Usage:  # echo "536870912" > /proc/sys/kernel/shmmax       ...