Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

RMAN Scenarios

-
1.How will you restore a backupset into new server from different location Using Rman.
  • Create the pfile in the new server.
  • startup the database in nomount stage;
  • connect to rman and restore the controlfile using the below command.
[oracle@rman ~]$ rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jul 27 20:04:10 2012
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
connected to target database: nijam (not mounted)
RMAN> list backup;
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 07/27/2012 20:04:21
ORA-01507: database not mounted
RMAN> restore controlfile from '/nijam1/rman/c-1406605833-20120727-00';
Starting restore at 27-JUL-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=39 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/gopi/nijam.ctl
Finished restore at 27-JUL-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list backup;
List of Backup Sets
===================
BS Key  Type LV Size   Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
1     Full  247.37M     DISK        00:00:10    27-JUL-12      
BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20120727T190801
Piece Name: /nijam/rman/NIJAM_01nh5moh_1
List of Datafiles in backup set 1
File LV Type Ckp SCN  Ckp Time  Name
---- -- ---- ---------- --------- ----
1         Full 167927       27-JUL-12 /nijam/oradata/system.dbf
2         Full 167927       27-JUL-12 /nijam/oradata/undotbs1.dbf
3         Full 167927       27-JUL-12 /nijam/oradata/sysaux.dbf
RMAN> catalog backuppiece '/nijam1/rman/NIJAM_01nh5moh_1';    
cataloged backuppiece
backup piece handle=/nijam1/rman/NIJAM_01nh5moh_1 recid=2 stamp=789768718
RMAN> list backup;
List of Backup Sets
===================
BS Key  Type LV Size
------- ---- -- ----------
1     Full  247.37M
List of Datafiles in backup set 1
File LV Type Ckp SCN  Ckp Time  Name
---- -- ---- ---------- --------- ----
1         Full 167927       27-JUL-12 /nijam/oradata/system.dbf
2         Full 167927       27-JUL-12 /nijam/oradata/undotbs1.dbf
3         Full 167927       27-JUL-12 /nijam/oradata/sysaux.dbf
  Backup Set Copy #1 of backup set 1
Device Type Elapsed Time Completion Time Compressed Tag
----------- ------------ --------------- ---------- ---
DISK      00:00:10    27-JUL-12         NO          TAG20120727T190801
      List of Backup Pieces for backup set 1 Copy #1
BP Key  Pc# Status      Piece Name
------- --- ----------- ----------
1     1   AVAILABLE   /nijam/rman/NIJAM_01nh5moh_1
  Backup Set Copy #2 of backup set 1
Device Type Elapsed Time Completion Time Compressed Tag
----------- ------------ --------------- ---------- ---
DISK      00:00:10    27-JUL-12         NO          TAG20120727T190801
      List of Backup Pieces for backup set 1 Copy #2
BP Key  Pc# Status      Piece Name
------- --- ----------- ----------
2     1   AVAILABLE   /nijam1/rman/NIJAM_01nh5moh_1
RMAN>  run {
set newname for datafile 1 to '/nijam1/stsrem1.dbf';
set newname for datafile 2 to '/nijam1/file2.dbf';
set newname for datafile 3 to '/nijam1/file3.dbf';
sql "alter database rename file ''/nijam/oradata/redo1.log'' to ''/nijam1/redo1.log'' ";
sql "alter database rename file ''/nijam/oradata/redo2.log'' to ''/nijam1/redo2.log'' ";
restore database from tag='TAG20120727T190801';
switch datafile all;
recover database  from tag='TAG20120727T190801';
alter database open resetlogs;
}
2.Recovery Manager Backups
How will take the database backup.
Taking database level backup
BACKUP DATABASE;
BACKUP CURRENT CONTROLFILE;
backup database plus archivelog;
Datafiles backup :
backup as backupset datafile '/DATA/pad/oradata/system.dbf','/DATA/pad/oradata/undotbs1.dbf';
configure retention policy to redundancy 1
configure retention policy to recovery windows of 10 days
backup archivelog time between sysdate-1 and sysdate;
backup archivelog time between sysdate-1 and sysdate;
backup tablespace system;
backup spfile;
backup backupset all  - takes all the backup including the backup;
validate
 backup validate database archivelog all; - to check the logical and physical corruption for  database and archivelog;
backup validate tablespace system;
backup validate datafile 'path';
backup validate spfile;
BACKUP DATABASE UNTIL 'SYSDATE+365' NOLOGS;
crosscheck
RMAN> CROSSCHECK BACKUP;
RMAN> CROSSCHECK COPY;
RMAN> CROSSCHECK backup of database; 
RMAN> CROSSCHECK backup of controlfile;
RMAN> CROSSCHECK archivelog all;
crosscheck backup of spfile;
crosscheck backup of tablespace users1;
restore

restore ARCHIVELOG FROM TIME 'SYSDATE-1' UNTIL TIME 'SYSDATE';
delete backup no.
list backup;
report obsolete;
3.Views
V$FLASHBACK_DATABASE_LOGFILE
V$FLASHBACK_DATABASE_LOG
V$FLASHBACK_DATABASE_STAT
V$BACKUP
V$BACKUP_SET
V$BACKUP_PIECE
V$BACKUP_DATAFILE
V$BACKUP_SPFILE
V$BACKUP_REDOLOG
V$BACKUP_CORRUPTION
V$BACKUP_DEVICE
V$BACKUP_SYNC_IO
V$BACKUP_ASYNC_IO
V$LOGMNR_CALLBACK
V$BACKUP_FILES
V$RMAN_BACKUP_SUBJOB_DETAILS
V$RMAN_BACKUP_JOB_DETAILS
V$BACKUP_SET_DETAILS
V$BACKUP_PIECE_DETAILS
V$BACKUP_COPY_DETAILS
V$BACKUP_DATAFILE_DETAILS
V$BACKUP_CONTROLFILE_DETAILS
V$BACKUP_ARCHIVELOG_DETAILS
V$BACKUP_SPFILE_DETAILS
V$BACKUP_SET_SUMMARY
V$BACKUP_DATAFILE_SUMMARY
V$BACKUP_CONTROLFILE_SUMMARY
V$BACKUP_ARCHIVELOG_SUMMARY
V$BACKUP_SPFILE_SUMMARY
V$BACKUP_COPY_SUMMARY
V$UNUSABLE_BACKUPFILE_DETAILS
V$RMAN_BACKUP_TYPE


Comments

Post a comment

Popular posts from this blog

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

-
In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL.
Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor.

1. Checking table size excluding table dependency:
SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 238 MB (1 row)2. Checking table size including table dependency:
SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 268 MB (1 row)3. Finding individual postgresql database size
SELECT pg_size_pretty(pg_database_size('db_name'));4. Finding individual table size for postgresql database -including dependency index:
SELECT pg_size_pretty(pg_total_relation_size(…
Read more

ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated ORA-01262: Stat failed on a file destination directory Linux-x86_64 Error: 2: No such file or directory

-
While I start my database with my initialization parameter it fails with oracle error
Solution :- su oracle
run environment variable
sqlplus / as sysdba

SQL>create pfile from spfile; Then remove or comment below line in pfile db_recovery_file_dest Save and exit su oracle
run environment variable
sqlplus / as sysdba

SQL>startup mount;
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size 2166536 bytes
Variable Size 427819256 bytes
Database Buffers 624951296 bytes
Redo Buffers 14000128 bytes

it should became the mount stage then open the DB as follows SQL>alter database open;
Database altered.
Read more

PostgreSQL pgBadger

-
pgBadger is a PostgreSQL log analyzer built for speed with fully reports from your PostgreSQL log file. It's a single and small Perl script that outperforms any other PostgreSQL log analyzer.It is written in pure Perl and uses a JavaScript library (flotr2) to draw graphs so that you don't need to install any additional Perl modules or other packages. Furthermore, this library gives us more features such as zooming. pgBadger also uses the Bootstrap JavaScript library and the FontAwesome webfont for better design. Everything is embedded.pgBadger is able to autodetect your log file format (syslog, stderr or csvlog). It is designed to parse huge log files as well as gzip compressed files. See a complete list of features below. Supported compressed format are gzip, bzip2 and xz. For the xz format you must have an xz version upper than 5.05 that supports the --robot option.All charts are zoomable and can be saved as PNG images.You can also limit pgBadger to only report errors or rem…
Read more

PostgreSQL Database startup / shutdown /restart

-
Pg_ctl Utility & Postgresql Service to do the same thing: Start the postgres server in the background. Without PGDATA set, “pg_ctl start” needs needs the additional -D /datadirargument in order to start.you can start/stop the postgresql server as root user as well as postgres userroot user: “service postgresql start““/etc/init.d/postgresql  start“, or “systemctl start postgresql-10” – this is for redhat linux above version 6postgres or edb user: Pg_ctl is only applicable for postgres user or edb user if you are a Enterprisedb su – postgres./pg_ctl start  -D /opt/PostgreSQL/9.3/data By using following anyone methods you can start,stop,reload else restart the postgresql server By using Pg_ctl UtilityPostgresl -9.3 ScriptBy using Postgresql Service1. pg_ctl utility – as postgres user:
using pg_ctl you can start/stop/reload/restart the postgresql server this utility can only permitted to access as postgres user ./pg_ctl stop -D /opt/PostgresPlus/9.3AS/data/ ./pg_ctl start -D /opt/PostgresPl…
Read more

How to configure Replication Manager (repmgr) ?

-
`repmgr` is a suite of open-source tools to manage replication and failover within a cluster of PostgreSQL servers. It enhances PostgreSQL's built-in replication capabilities with utilities to set up standby servers, monitor replication, and perform administrative tasks such as failover or switchover operations. The current `repmgr` version (3.3) supports all PostgreSQL versions from 9.3 to 9.6. Overview The repmgr suite provides two main tools:1.repmgr - a command-line tool used to perform administrative tasks such as: - setting up standby servers - promoting a standby server to master - switching over master and standby servers - displaying the status of servers in the replication cluster 2.repmgrd is a daemon which actively monitors servers in a replication cluster and performs the following tasks: - monitoring and recording replication performance - performing failover by detecting failure of the master and promoting the most suitabl…
Read more