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

PostgreSQL Pgbadger Installation On Linux

-
Image
PgBadger is a tool that analyzes PostgreSQL log files and generates reports on execution of SQL and server operation. Statistical reports analyzed from a number of perspectives can be useful not only for grasping the usual database operation but also as a hint for performance improvement.

The report output by pgBadger has the following features. Graph output in HTML format Many statistical objects Daily, Weekly unit creation possible 1.Graph output in HTML format
Many of the analysis results can be displayed in graph form by outputting the report in HTML format (output in text format or JSON format is also possible). By analyzing the log information graphed, it is much more prospective for people to see than the raw log data. So, if you do not need to handle it with another tool separately, we recommend report output in HTML format.

2.Many statistical objects A lot of data useful for database performance analysis is output in the report as shown below. Queries (total number of executions, maxi…
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

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

Migrating From Oracle to PostgreSQL using ora2pg open source tools

-
In this blog we are going to talk about migrating from oracle to postgresql using ora2pg.
After installing ora2pg tool, we will see how to configure and to run it to migrate our data. We are using an oracle 12C database and a postgresql edb 9.6, The server is runing on OEL 7.2,The oracle database and the postgresql server are running on the same server.

we are going to talk about migrating from oracle to postgresql using ora2pg open source tool
before migrating you need to know little bit knowledge of functions,procedure,trigger and  Difference between oracle vs postgresql data types

1.Oracle Installation 12C
2.Oracle instalaltion 11gr2
3.postgresql installation 9.3
4.postgresql installation 10.3
-------------------------At Oracle---------------------------------------------------
PREREQUEST:
1.In a database all schema size:
set linesize 150 set pagesize 5000 col owner for a15 col segment_name for a30 col segment_type for a20 col TABLESPACE_NAME for a30 clear breaks clear computes compute sum of…
Read more

How To Schedule PostgreSQL Jobs using pgAgent on Linux plateform

-
Image
Taking regular SQL database backup is one of the most important responsibilities of a database administrator. By setting up automatic database backup we can get rid of the additional overhead of doing it manually, every day, week or month. When it comes to PostgreSQL running in any Unix distributions or in Windows, there are at least two ways to do it. Using the built in CronJobs/ CronTabs in case of  Linux, and Windows scheduled tasks in Windows .Using PostgreSQL’s own scheduling agent, pgAgent.Often DBAs tends to rely on CronTabs or Scheduled tasked because of the ease of use it offers. But there are several advantages if you use pgAgent instead. Though it takes a little effort to install pgAgent, it is much better than Cron jobs or Scheduled tasks.
Why use pgAgent over CronJob:Compared to CronTab, PgAgent has the following advantages: 

You can have multiple steps for a job without having to resort to a batch script.You can have multiple schedules for a job without having to repeat the…
Read more