Password less authentication between linux servers

Password less authentication between linux servers:-
Source server:-192.168.2.11
Target server:-192.168.2.12

Hostfile entry On both source and target server:

cat /etc/hosts
192.168.2.11 server1.soumya.com server1
192.168.2.12 server2.soumya.com server2

On source server:-

# ssh-keygen -t rsa
# ssh-keygen -t dsa
# cd /root/.ssh
# cat id_rsa.pub >>authorized_keys
# cat id_dsa.pub >>authorized_keys
# scp authorized_keys root@server2:/root/.ssh/

On target server:-
# ssh-keygen -t rsa
# ssh-keygen -t dsa
# cd /root/.ssh
# cat id_rsa.pub >>authorized_keys
# cat id_dsa.pub >>authorized_keys
# scp authorized_keys root@server1:/root/.ssh/


Now lets test if both servers can ssh each other w/o password or not:-

on source server:-
[root@server1 ~]# ssh server2
Last login: Fri May 29 08:32:06 2015 from 192.168.2.50

[root@server1 ~]# ssh server2 date
Fri May 29 08:37:28 IST 2015


on target server:-

[root@server2 ~]# ssh server1
Last login: Fri May 29 08:38:00 2015 from server2.soumya.com

[root@server1 ~]# ssh server1 date
Fri May 29 08:38:14 IST 2015

So we can see both servers can connect each other without prompting for any password.

Happy learning...




Please share your ideas and opinions about this topic.

If you like this post, then please share with others.
Please subscribe on email for every updates on mail.

Switchover of Databases (Primary to standby and standby to primary) in Dataguard oracle 11g.

Switchover of Databases (Primary to standby and standby to primary) in  Dataguard  oracle 11g.

Oracle Version:- Enterprise Edition Release 11.2.0.1
OS:- Rhel 6.4
Primary database:- Prim
Standby database:- Stand


Switchover is a planned event, it is ideal when we might want to upgrade the primary database or change
the storage/hardware configuration (add memory, cpu networking), we may even want to upgrade the
configuration to Oracle RAC .

What happens during a switchover is the following :

1.) Notifies the primary database that a switchover is about to occur
2.) Disconnect all users from the primary database
3.) Generate a special redo record that signals the End of Redo (EOR)
4.) Converts the primary database into a standby database
5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost,
converts the standby database into the primary database.



Before doing the switchover lets run few select queries to find out some info:-
In primary:-

SQL> select status,INSTANCE_NAME ,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
OPEN         prim             PRIMARY

In standby:-

SQL> select status,INSTANCE_NAME ,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
MOUNTED      stand            PHYSICAL STANDBY


In primary:-
Archive log destination of Prim:-

SQL> show parameter log_archive_dest_1;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_1                   string      LOCATION=/u01/app/oracle/flash
                                                 _recovery_area VALID_FOR=(ALL_
                                                 LOGFILES,ALL_ROLES) DB_UNIQUE_
                                                 NAME=prim


SQL> show parameter log_archive_dest_2;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2                   string      SERVICE=stand LGWR ASYNC VALID
                                                 _FOR=(ALL_LOGFILES,PRIMARY_ROL
                                                 E) DB_UNIQUE_NAME=stand

*Archivelog Destination 1 of Primary Database is "/u01/app/oracle/flash_recovery_area" and Archivelog
destination 2 of Primary database is pointing to the service-name of the standby database.


In standby:-
Archive log destination of Stand:-
SQL> show parameter log_archive_dest_1;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_1                   string      LOCATION=/u01/app/oracle/flash
                                                 _recovery_area VALID_FOR=(ALL_
                                                 LOGFILES,ALL_ROLES) DB_UNIQUE_
                                                 NAME=stand


SQL> show parameter log_archive_dest_2;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2                   string      SERVICE=prim LGWR ASYNC VALID_
                                                 FOR=(ALL_LOGFILES,PRIMARY_ROLE
                                                 ) DB_UNIQUE_NAME=prim

*Archivelog Destination 1 of Standby database is "/u01/app/oracle/flash_recovery_area" and archivelog
destination 2 of standby database is pointing to the service-name of the primary database.
(Note: destination 2 in standby database is not mandatory. It is required only if the standby database
would be running in as primary database during switchover or failover. Hence it would be a good practice
to set this parameter to avoid problems during the switchover or failover.)

Pre-Switchover Checks:-

In standby database:-

Verify whether Managed Recovery process is running on the standby database

Use the following query to check if the managed recovery process is running on the standby database.

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CLOSING              27
RFS       IDLE                  0
RFS       IDLE                 28
MRP0      WAIT_FOR_LOG         28

The above result shows that the Managed Recovery Process (MRP0) is running on the standby database.
If MRP is not running, then start the process with real time enabled using the below query in the
standby database.

SQL>alter database recover managed standby disconnect from session;

Once when the MRP has started on the standby database, make sure that the archive logs generated at the
primary database end are shipped and getting applied to the standby database.

At primary database:-
SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------
            27

At standby database:-
SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------
            27

In the above case, sequence# 27 is the maximum sequence generated at the primary database and the
same has been applied to the standby database.So both database's log files are in sync.

*Verify primary and standby tempfiles match :-

For each temporary tablespace on the standby, verify that temporary files associated with that
tablespace on the primary database also exist on the standby database. Tempfiles added after initial
standby creation are not propagated to the standby. Run this query on both the primary and target
physical standby databases and verify that they match.

In primary database:-
SQL> select ts#, name ,status from v$tempfile;
      TS# NAME                                     STATUS
---------- ---------------------------------------- -------
         3 /u01/app/oracle/oradata/prim/temp01.dbf  ONLINE

SQL> select ts#,name from v$tablespace;

       TS# NAME
---------- ----------------------------------------
         0 SYSTEM
         1 SYSAUX
         2 UNDOTBS1
         4 USERS
         3 TEMP
         6 EXAMPLE


In Standby database:-
SQL> select ts#, name ,status from v$tempfile;
       TS# NAME                                     STATUS
---------- ---------------------------------------- -------
         3 /u01/app/oracle/oradata/stand/temp01.dbf ONLINE


SQL> select ts#,name from v$tablespace;

       TS# NAME
---------- ----------------------------------------
         0 SYSTEM
         1 SYSAUX
         2 UNDOTBS1
         4 USERS
         3 TEMP
         6 EXAMPLE

*Verify that all datafiles are online on both primary and standby databases:-

On both primary and standby database:-

SQL> select name from v$datafile where status='OFFLINE';

no rows selected

If there are any offline datafiles, then bring them online using the below query
SQL>alter database datafile<datafile name> online;


Switchover Steps:

These steps are performed during the switchover process at the primary database side.

Check if there are any jobs running on the primary database using the below query.

SQL>select * from dba_jobs_running;
no rows selected

If there are any jobs running on the primary database and if it’s execution is not very important,
then terminate the job to continue further.

Block further job submission by setting the job_queue_processes parameter to 0 so that there would be no
jobs running during switchover.

SQL> show parameter job_queue_process;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes                  integer     1000

Set this parameter to the value 0.
SQL> alter system set job_queue_processes=0 scope=spfile;                  

System altered.


*Verify that the primary database can be switched over to the standby

In primary database:-

SQL> select switchover_status from v$database;

SWITCHOVER_STATUS
--------------------
TO STANDBY

A value of TO STANDBY or SESSIONS ACTIVE (which requires the WITH SESSION SHUTDOWN clause on the switchover command)
indicates that the primary database can be switched to the standby role. If neither of these values is
returned, a switchover is not possible because redo transport is either mis-configured or is not functioning
properly.


*Switchover the primary database to standby

Once when value of switchover_status returns “TO STANDBY” or “SESSIONS ACTIVE” on the primary database,
then perform the switchover using the below query

In primary:-
SQL> alter database commit to switchover to physical standby with session shutdown;

Database altered.

Now the primary database is switched over to the standby database. The execution of the above command
may take some time and the archive logs generated during its execution would be automatically applied to
the standby database. Once when the command is executed with the output as “Database altered”, it means
that the primary database has been switched over to the standby.

Note: Always perform the switchover of the primary database to standby database first and then
switchover the standby database to primary. If not, then you would end up landing with two primary
databases.


*Switchover the standby database to primary
Query the switchover_status column from the v$database view at the standby side to determine whether
the standby database can be switched over to the primary database.

In standby database:-
SQL> select switchover_status from v$database;

SWITCHOVER_STATUS
--------------------
TO PRIMARY

A value of TO PRIMARY or SESSIONS ACTIVE indicates that the standby database is ready to be switched to
the primary role. If neither of these values is returned, verify that redo apply is active and that redo
transport is configured and working properly. Continue to query this column until the value returned is
either TO PRIMARY or SESSIONS ACTIVE.

Once when the value of switchover_status returns “TO PRIMARY” or “SESSIONS ACTIVE” on the standby
database, then perform the switchover using the below query

Run following in standby database;-

SQL>alter database commit to switchover to primary with session shutdown;

Now the standby database has been switched over to the primary database.

*Open the new primary database (stand)

The new primary database will be in mount state. Open this new primary database using the below query.

SQL>alter database open;

SQL> select status,INSTANCE_NAME ,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
OPEN         stand            PRIMARY


*Restart the new standby database
Restart the new standby database (old primary database prim), bring it to the mount stage and
start the managed recovery process.

Shutdown the new standby database (prim)
SQL> shutdown immediate;
ORA-01507: database not mounted

ORACLE instance shut down.

Startup the new standby database (prim) in mount stage
SQL>startup mount;
ORACLE instance started.

Total System Global Area  413372416 bytes
Fixed Size                  2213896 bytes
Variable Size             335546360 bytes
Database Buffers           71303168 bytes
Redo Buffers                4308992 bytes
Database mounted.

Start the managed recovery process on the the new standby database (prim)
SQL>alter database recover managed standby database disconnect from session;
Database altered.

QL> select status,INSTANCE_NAME ,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
MOUNTED      prim             PHYSICAL STANDBY

*Post-Switchover tasks

Reset the job_queue_processes parameter to its previous value
Set the job queue processes to its original value on the new standby (prim).

SQL> show parameter job_queue

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes                  integer     0

SQL> alter system set job_queue_processes=1000 scope=spfile;

System altered.


Now the roles of the databases have been changed. The primary database (prim) has been changed to
standby database and the standby database (stnd) has been changed to primary database.
The archive logs that get generated in the new primary database (stnd) get shipped automatically to the
new standby database (prim) and they are applied on it automatically.

Maximum archivelog generated at the new primary database (stnd)

SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------
            34

Maximum archivelog that has been shipped and applied to the new standby database (prim)
SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------
            34


*Now if we want the real time apply enabled on new standby database(prim)
Perform the following queries on new standby database(prim)
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter database open;

Database altered.

SQL> alter database recover managed standby database using current logfile disconnect from session;

Database altered.

SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ ONLY WITH APPLY

 

Please share your ideas and opinions about this topic. If you like this post, then please share with others. Please subscribe on email for every updates on mail.

Table Point In Time Recovery (PITR) in Oracle Database 12c Release

Oracle version : 12.1.0.2.0  Enterprise Edition
OS : Rhel 6.4
Database Name : ORA12C


sqlplus soumya/soumya

SQL> create table xyz (id number);
SQL> insert into xyz values (1);
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created
SQL> commit;


SQL> SELECT * FROM xyz;

        ID
----------
         1
         1
         1
         1
         1
         1

SQL> select to_char(sysdate,'DD-MON-YYYY HH24:MI:SS') from dual;

TO_CHAR(SYSDATE,'DD-MON-YYYYH)
-----------------------------
2015-05-22:23:16:36

*Make sure that you have a valid RMAN level 0 backup to proceed.
Now lets drop the table and purge recyclebin too.

SQL> drop table xyz;

Table dropped.

SQL> purge recyclebin;

Recyclebin purged.

SQL> select * from xyz;
select * from xyz
              *
ERROR at line 1:
ORA-00942: table or view does not exist

Now We will perform the tablespace point in time recovery until the time before the table was dropped.

For TSPITR, we need to specify the auxiliary destination where RMAN would create a temporary database by restoring the controlfile, SYSTEM tablespace, UNDO tablespace, SYSAUX tablespace and finally the tablespace that needs to be recovered. 

Once the temporary database is restored and recovered, RMAN automatically exports the contents of tablespace to be recovered from the temporary tablespace to a dump file and imports this dump into the Target(Main) database where the table was dropped.

RMAN> RECOVER TABLE 'SOUMYA'.'XYZ' until time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')" AUXILIARY DESTINATION '/u01'
REMAP TABLE 'SOUMYA'.'XYZ':'XYZ1_PREV';

Starting recover at 22-MAY-15
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified Point-in-Time

List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1

Creating automatic instance, with SID='vkqb'

initialization parameters used for automatic instance:
db_name=ORA12C
db_unique_name=vkqb_pitr_ORA12C
compatible=12.1.0.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/u01/app/oracle
_system_trig_enabled=FALSE
sga_target=600M
processes=200
db_create_file_dest=/u01
log_archive_dest_1='location=/u01'
#No auxiliary parameter file used


starting up automatic instance ORA12C

Oracle instance started

Total System Global Area     629145600 bytes

Fixed Size                     2927528 bytes
Variable Size                184550488 bytes
Database Buffers             436207616 bytes
Redo Buffers                   5459968 bytes
Automatic instance created

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')";
# restore the controlfile
restore clone controlfile;

# mount the controlfile
sql clone 'alter database mount clone database';

# archive current online log
sql 'alter system archive log current';
}
executing Memory Script

executing command: SET until clause

Starting restore at 22-MAY-15
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=22 device type=DISK

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/inc_level_1_cum/220515_224615/control_ORA12C_c-254883632-20150522-01
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/inc_level_1_cum/220515_224615/control_ORA12C_c-254883632-20150522-01 tag=TAG20150522T224704
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/ORA12C/controlfile/o1_mf_boyv53cn_.ctl
Finished restore at 22-MAY-15

sql statement: alter database mount clone database

sql statement: alter system archive log current

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile  1 to new;
set newname for clone datafile  4 to new;
set newname for clone datafile  3 to new;
set newname for clone tempfile  1 to new;
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile  1, 4, 3;

switch clone datafile all;
}
executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

renamed tempfile 1 to /u01/ORA12C/datafile/o1_mf_temp_%u_.tmp in control file

Starting restore at 22-MAY-15
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/ORA12C/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u01/ORA12C/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/ORA12C/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/full_backup/220515_223941/full_ORA12C_20150522_880411183_1_1
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/full_backup/220515_223941/full_ORA12C_20150522_880411183_1_1 tag=TAG20150522T223943
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 22-MAY-15

datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=880413765 file name=/u01/ORA12C/datafile/o1_mf_system_boyv5bb4_.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=7 STAMP=880413765 file name=/u01/ORA12C/datafile/o1_mf_undotbs1_boyv5bcz_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=8 STAMP=880413765 file name=/u01/ORA12C/datafile/o1_mf_sysaux_boyv5bcp_.dbf

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')";
# online the datafiles restored or switched
sql clone "alter database datafile  1 online";
sql clone "alter database datafile  4 online";
sql clone "alter database datafile  3 online";
# recover and open database read only
recover clone database tablespace  "SYSTEM", "UNDOTBS1", "SYSAUX";
sql clone 'alter database open read only';
}
executing Memory Script

executing command: SET until clause

sql statement: alter database datafile  1 online

sql statement: alter database datafile  4 online

sql statement: alter database datafile  3 online

Starting recover at 22-MAY-15
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/ORA12C/datafile/o1_mf_system_boyv5bb4_.dbf
destination for restore of datafile 00004: /u01/ORA12C/datafile/o1_mf_undotbs1_boyv5bcz_.dbf
destination for restore of datafile 00003: /u01/ORA12C/datafile/o1_mf_sysaux_boyv5bcp_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/inc_level_1_cum/220515_224615/inc_level_1_cum_ORA12C_20150522_880411578_4_1
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/inc_level_1_cum/220515_224615/inc_level_1_cum_ORA12C_20150522_880411578_4_1 tag=TAG20150522T224618
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

starting media recovery

archived log for thread 1 with sequence 46 is already on disk as file /u01/app/oracle/fast_recovery_area/1_46_877084402.dbf
archived log file name=/u01/app/oracle/fast_recovery_area/1_46_877084402.dbf thread=1 sequence=46
Executing: alter database datafile 5 offline
archived log file name=/u01/app/oracle/fast_recovery_area/1_46_877084402.dbf thread=1 sequence=46
media recovery complete, elapsed time: 00:00:01
Finished recover at 22-MAY-15

sql statement: alter database open read only

contents of Memory Script:
{
   sql clone "create spfile from memory";
   shutdown clone immediate;
   startup clone nomount;
   sql clone "alter system set  control_files =
  ''/u01/ORA12C/controlfile/o1_mf_boyv53cn_.ctl'' comment=
 ''RMAN set'' scope=spfile";
   shutdown clone immediate;
   startup clone nomount;
# mount database
sql clone 'alter database mount clone database';
}
executing Memory Script

sql statement: create spfile from memory

database closed
database dismounted
Oracle instance shut down

connected to auxiliary database (not started)
Oracle instance started

Total System Global Area     629145600 bytes

Fixed Size                     2927528 bytes
Variable Size                184550488 bytes
Database Buffers             436207616 bytes
Redo Buffers                   5459968 bytes

sql statement: alter system set  control_files =   ''/u01/ORA12C/controlfile/o1_mf_boyv53cn_.ctl'' comment= ''RMAN set'' scope=spfile

Oracle instance shut down

connected to auxiliary database (not started)
Oracle instance started

Total System Global Area     629145600 bytes

Fixed Size                     2927528 bytes
Variable Size                184550488 bytes
Database Buffers             436207616 bytes
Redo Buffers                   5459968 bytes

sql statement: alter database mount clone database

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')";
# set destinations for recovery set and auxiliary set datafiles
set newname for datafile  5 to new;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile  5;

switch clone datafile all;
}
executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

Starting restore at 22-MAY-15
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=21 device type=DISK

creating datafile file number=5 name=/u01/VKQB_PITR_ORA12C/datafile/o1_mf_testtbs_%u_.dbf
restore not done; all files read only, offline, or already restored
Finished restore at 22-MAY-15

datafile 5 switched to datafile copy
input datafile copy RECID=12 STAMP=880413824 file name=/u01/VKQB_PITR_ORA12C/datafile/o1_mf_testtbs_boyv95p7_.dbf

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2015-05-22:23:16:36','YYYY-MM:DD:HH24:MI:SS')";
# online the datafiles restored or switched
sql clone "alter database datafile  5 online";
# recover and open resetlogs
recover clone database tablespace  "TESTTBS", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
}
executing Memory Script

executing command: SET until clause

sql statement: alter database datafile  5 online

Starting recover at 22-MAY-15
using channel ORA_AUX_DISK_1

starting media recovery

archived log for thread 1 with sequence 46 is already on disk as file /u01/app/oracle/fast_recovery_area/1_46_877084402.dbf
archived log file name=/u01/app/oracle/fast_recovery_area/1_46_877084402.dbf thread=1 sequence=46
media recovery complete, elapsed time: 00:00:00
Finished recover at 22-MAY-15

database opened

contents of Memory Script:
{
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01''";
}
executing Memory Script

sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01''

sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01''

Performing export of tables...
   EXPDP> Starting "SYS"."TSPITR_EXP_vkqb_Dzlo":
   EXPDP> Estimate in progress using BLOCKS method...
   EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
   EXPDP> Total estimation using BLOCKS method: 64 KB
   EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE
   EXPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
   EXPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
   EXPDP> . . exported "SOUMYA"."XYZ"                              5.062 KB       2 rows
   EXPDP> Master table "SYS"."TSPITR_EXP_vkqb_Dzlo" successfully loaded/unloaded
   EXPDP> ******************************************************************************
   EXPDP> Dump file set for SYS.TSPITR_EXP_vkqb_Dzlo is:
   EXPDP>   /u01/tspitr_vkqb_17217.dmp
   EXPDP> Job "SYS"."TSPITR_EXP_vkqb_Dzlo" successfully completed at Fri May 22 23:25:04 2015 elapsed 0 00:00:30
Export completed


contents of Memory Script:
{
# shutdown clone before import
shutdown clone abort
}
executing Memory Script

Oracle instance shut down

Performing import of tables...
   IMPDP> Master table "SYS"."TSPITR_IMP_vkqb_dagD" successfully loaded/unloaded
   IMPDP> Starting "SYS"."TSPITR_IMP_vkqb_dagD":
   IMPDP> Processing object type TABLE_EXPORT/TABLE/TABLE
   IMPDP> Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
   IMPDP> . . imported "SOUMYA"."XYZ1_PREV"                        5.062 KB       2 rows
   IMPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
   IMPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
   IMPDP> Job "SYS"."TSPITR_IMP_vkqb_dagD" successfully completed at Fri May 22 23:25:28 2015 elapsed 0 00:00:07
Import completed


Removing automatic instance
Automatic instance removed
auxiliary instance file /u01/ORA12C/datafile/o1_mf_temp_boyv7n1j_.tmp deleted
auxiliary instance file /u01/VKQB_PITR_ORA12C/onlinelog/o1_mf_3_boyv9h6g_.log deleted
auxiliary instance file /u01/VKQB_PITR_ORA12C/onlinelog/o1_mf_2_boyv9fc9_.log deleted
auxiliary instance file /u01/VKQB_PITR_ORA12C/onlinelog/o1_mf_1_boyv9bwh_.log deleted
auxiliary instance file /u01/VKQB_PITR_ORA12C/datafile/o1_mf_testtbs_boyv95p7_.dbf deleted
auxiliary instance file /u01/ORA12C/datafile/o1_mf_sysaux_boyv5bcp_.dbf deleted
auxiliary instance file /u01/ORA12C/datafile/o1_mf_undotbs1_boyv5bcz_.dbf deleted
auxiliary instance file /u01/ORA12C/datafile/o1_mf_system_boyv5bb4_.dbf deleted
auxiliary instance file /u01/ORA12C/controlfile/o1_mf_boyv53cn_.ctl deleted
auxiliary instance file tspitr_vkqb_17217.dmp deleted
Finished recover at 22-MAY-15

[oracle@server3 bin]$ sqlplus soumya/soumya
OUMYA@ORA12C> SQL> SELECT * FROM xyz;

        ID
----------
         1
         1
         1
         1
         1
         1

Please share your ideas and opinions about this topic.

If you like this post, then please share with others.
Please subscribe on email for every updates on mail.

Recovering A Dropped Table Using Tablespace Point In Time Recovery (TSPITR) in Oracle 11g

Oracle version : 11.2.0.1.0 Enterprise Edition
OS : Rhel 6.4
Database Name : orcl
Tablespace Name : TESTTBS

A user reported a table named "TSPITR" was accidentally dropped . There was no flashback enabled on this
database and the recyclebin too was purged out. As a result, the table could not be recovered using
flashback method. The other methods to recover the dropped table would be:

Using Tablespace Point In Time Recovery. Here, the tablespace associate with the table that is dropped
would be recovered until the time. The main disadvantage of this method is that any other successful
transactions that were carried out on this tablespace after the time the
table was dropped, would be lost when you do a point in time recovery.

Here we are trying to create the same scenario by creating and dropping the table TSPITR.

sqlplus soumya/soumya

SQL> create table xyz (id number);
SQL> insert into xyz values (1);
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created.
SQL> /
1 row created
SQL> commit;


First lets find out the tablespace where the table resides:-
SQL> select table_name ,tablespace_name from user_tables where table_name ='XYZ';

TABLE_NAME               TABLESPACE_NAME
------------------------------ ------------------------------
XYZ                                 TESTTBS

SQL> SELECT * FROM xyz;

        ID
----------
         1
         1
         1
         1
         1
         1

SQL> select to_char(sysdate,'DD-MON-YYYY HH24:MI:SS') from dual;

TO_CHAR(SYSDATE,'DD-MON-YYYYH
-----------------------------
20-SEP-2014 07:22:29

*Make sure that you have a valid RMAN level 0 backup to proceed.
Now lets drop the table and purge recyclebin too.

SQL> drop table xyz;

Table dropped.

SQL> purge recyclebin;

Recyclebin purged.

SQL> select * from xyz;
select * from xyz
              *
ERROR at line 1:
ORA-00942: table or view does not exist

Now We will perform the tablespace point in time recovery until the time before the table was dropped.

For TSPITR, we need to specify the auxiliary destination where RMAN would create a temporary database
by restoring the controlfile, SYSTEM tablespace, UNDO tablespace, SYSAUX tablespace and finally the
tablespace that needs to be recovered.Once the temporary database is restored and recovered, RMAN
automatically exports the contents of tablespace to be recovered from the temproary tablespace to a dump
file and imports this dump into the Target(Main) database where the table was dropped.

[oracle@server2 ORCL]$ RMAN> run
2> {
3> recover tablespace TESTTBS until time "to_date('2014-09-20:07:22:29','YYYY-MM:DD:HH24:MI:SS')" auxiliary destination '/u01';
4> };

Starting recover at 20-SEP-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=29 device type=DISK
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time

List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1

Creating automatic instance, with SID='DFCz'

initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=DFCz_tspitr_ORCL
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/u01
log_archive_dest_1='location=/u01'
#No auxiliary parameter file used


starting up automatic instance ORCL

Oracle instance started

Total System Global Area     292278272 bytes

Fixed Size                     2212736 bytes
Variable Size                100666496 bytes
Database Buffers             184549376 bytes
Redo Buffers                   4849664 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2014-09-20:07:22:29','YYYY-MM:DD:HH24:MI:SS')";
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
}
executing Memory Script

executing command: SET until clause

Starting restore at 20-SEP-14
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=19 device type=DISK

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/full_backup/200914_071833/control_ORCL_c-1366623577-20140920-08
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/full_backup/200914_071833/control_ORCL_c-1366623577-20140920-08 tag=TAG20140920T072109
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/ORCL/controlfile/o1_mf_b1sqnht0_.ctl
Finished restore at 20-SEP-14

sql statement: alter database mount clone database

sql statement: alter system archive log current

sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2014-09-20:07:22:29','YYYY-MM:DD:HH24:MI:SS')";
plsql <<<-- tspitr_2
declare
  sqlstatement       varchar2(512);
  offline_not_needed exception;
  pragma exception_init(offline_not_needed, -01539);
begin
  sqlstatement := 'alter tablespace '||  'TESTTBS' ||' offline immediate';
  krmicd.writeMsg(6162, sqlstatement);
  krmicd.execSql(sqlstatement);
exception
  when offline_not_needed then
    null;
end; >>>;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile  1 to new;
set newname for clone datafile  3 to new;
set newname for clone datafile  2 to new;
set newname for clone tempfile  1 to new;
set newname for datafile  8 to
 "/u01/app/oracle/oradata/orcl/testtbs.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile  1, 3, 2, 8;
switch clone datafile all;
}
executing Memory Script

executing command: SET until clause

sql statement: alter tablespace TESTTBS offline immediate

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

renamed tempfile 1 to /u01/ORCL/datafile/o1_mf_temp_%u_.tmp in control file

Starting restore at 20-SEP-14
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00002 to /u01/ORCL/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/full_backup/200914_065249/full_ORCL_20140920_858754372_17_1
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/full_backup/200914_065249/full_ORCL_20140920_858754372_17_1 tag=TAG20140920T065252
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/ORCL/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/ORCL/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00008 to /u01/app/oracle/oradata/orcl/testtbs.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/full_backup/200914_071833/full_ORCL_20140920_858755915_24_1
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/full_backup/200914_071833/full_ORCL_20140920_858755915_24_1 tag=TAG20140920T071834
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:56
Finished restore at 20-SEP-14

datafile 1 switched to datafile copy
input datafile copy RECID=5 STAMP=858756425 file name=/u01/ORCL/datafile/o1_mf_system_b1sqot67_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=6 STAMP=858756425 file name=/u01/ORCL/datafile/o1_mf_undotbs1_b1sqot9h_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=7 STAMP=858756425 file name=/u01/ORCL/datafile/o1_mf_sysaux_b1sqnphr_.dbf

contents of Memory Script:
{
# set requested point in time
set until  time "to_date('2014-09-20:07:22:29','YYYY-MM:DD:HH24:MI:SS')";
# online the datafiles restored or switched
sql clone "alter database datafile  1 online";
sql clone "alter database datafile  3 online";
sql clone "alter database datafile  2 online";
sql clone "alter database datafile  8 online";
# recover and open resetlogs
recover clone database tablespace  "TESTTBS", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
}
executing Memory Script

executing command: SET until clause

sql statement: alter database datafile  1 online

sql statement: alter database datafile  3 online

sql statement: alter database datafile  2 online

sql statement: alter database datafile  8 online

Starting recover at 20-SEP-14
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00002: /u01/ORCL/datafile/o1_mf_sysaux_b1sqnphr_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/backups/rman_backup/inc_level_1/200914_071502/inc_level_1_ORCL_20140920_858755714_21_1
channel ORA_AUX_DISK_1: piece handle=/u01/backups/rman_backup/inc_level_1/200914_071502/inc_level_1_ORCL_20140920_858755714_21_1 tag=TAG20140920T071513
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

starting media recovery

archived log for thread 1 with sequence 18 is already on disk as file /u01/1_18_838842842.dbf
archived log for thread 1 with sequence 19 is already on disk as file /u01/1_19_838842842.dbf
archived log for thread 1 with sequence 20 is already on disk as file /u01/1_20_838842842.dbf
archived log file name=/u01/1_18_838842842.dbf thread=1 sequence=18
archived log file name=/u01/1_19_838842842.dbf thread=1 sequence=19
archived log file name=/u01/1_20_838842842.dbf thread=1 sequence=20
media recovery complete, elapsed time: 00:00:00
Finished recover at 20-SEP-14

database opened

contents of Memory Script:
{
# make read only the tablespace that will be exported
sql clone 'alter tablespace  TESTTBS read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01''";
}
executing Memory Script

sql statement: alter tablespace  TESTTBS read only

sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01''

sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01''

Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_DFCz":
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
   EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
   EXPDP> Master table "SYS"."TSPITR_EXP_DFCz" successfully loaded/unloaded
   EXPDP> ******************************************************************************
   EXPDP> Dump file set for SYS.TSPITR_EXP_DFCz is:
   EXPDP>   /u01/tspitr_DFCz_62260.dmp
   EXPDP> ******************************************************************************
   EXPDP> Datafiles required for transportable tablespace TESTTBS:
   EXPDP>   /u01/app/oracle/oradata/orcl/testtbs.dbf
   EXPDP> Job "SYS"."TSPITR_EXP_DFCz" successfully completed at 07:28:42
Export completed


contents of Memory Script:
{
# shutdown clone before import
shutdown clone immediate
# drop target tablespaces before importing them back
sql 'drop tablespace  TESTTBS including contents keep datafiles';
}
executing Memory Script

database closed
database dismounted
Oracle instance shut down

sql statement: drop tablespace  TESTTBS including contents keep datafiles

Performing import of metadata...
   IMPDP> Master table "SYS"."TSPITR_IMP_DFCz" successfully loaded/unloaded
   IMPDP> Starting "SYS"."TSPITR_IMP_DFCz":
   IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
   IMPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
   IMPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
   IMPDP> Job "SYS"."TSPITR_IMP_DFCz" successfully completed at 07:29:27
Import completed


contents of Memory Script:
{
# make read write and offline the imported tablespaces
sql 'alter tablespace  TESTTBS read write';
sql 'alter tablespace  TESTTBS offline';
# enable autobackups after TSPITR is finished
sql 'begin dbms_backup_restore.AutoBackupFlag(TRUE); end;';
}
executing Memory Script

sql statement: alter tablespace  TESTTBS read write

sql statement: alter tablespace  TESTTBS offline

sql statement: begin dbms_backup_restore.AutoBackupFlag(TRUE); end;

Removing automatic instance
Automatic instance removed
auxiliary instance file /u01/ORCL/datafile/o1_mf_temp_b1sqqxbb_.tmp deleted
auxiliary instance file /u01/ORCL/onlinelog/o1_mf_3_b1sqqsvf_.log deleted
auxiliary instance file /u01/ORCL/onlinelog/o1_mf_2_b1sqqql5_.log deleted
auxiliary instance file /u01/ORCL/onlinelog/o1_mf_1_b1sqqo4d_.log deleted
auxiliary instance file /u01/ORCL/datafile/o1_mf_sysaux_b1sqnphr_.dbf deleted
auxiliary instance file /u01/ORCL/datafile/o1_mf_undotbs1_b1sqot9h_.dbf deleted
auxiliary instance file /u01/ORCL/datafile/o1_mf_system_b1sqot67_.dbf deleted
auxiliary instance file /u01/ORCL/controlfile/o1_mf_b1sqnht0_.ctl deleted
Finished recover at 20-SEP-14

Once the import is done successfully, RMAN automatically deletes the temporary database that it had
created earlier.Now, lets connect to the main database and check if we are able to access the dropped
table. But, before that, we need to bring the tablespace online.


SQL>  set linesize 100
SQL> col name for a60
SQL> select name,status from v$datafile;

NAME                                                         STATUS
------------------------------------------------------------ -------
/u01/app/oracle/oradata/orcl/system01.dbf                    SYSTEM
/u01/app/oracle/oradata/orcl/sysaux01.dbf                    ONLINE
/u01/app/oracle/oradata/orcl/undotbs01.dbf                   ONLINE
/u01/app/oracle/oradata/orcl/users01.dbf                     ONLINE
/u01/app/oracle/oradata/orcl/example01.dbf                   ONLINE
/u01/app/oracle/oradata/orcl/TS_HYBRIS_DATA.dbf              OFFLINE
/u01/app/oracle/oradata/orcl/TS_HYBRIS_INDEX.dbf             ONLINE
/u01/app/oracle/oradata/orcl/testtbs.dbf                     OFFLINE

8 rows selected.

SQL> select tablespace_name,status from dba_tablespaces;

TABLESPACE_NAME                STATUS
------------------------------ ---------
SYSTEM                         ONLINE
SYSAUX                         ONLINE
UNDOTBS1                       ONLINE
TEMP                           ONLINE
USERS                          ONLINE
EXAMPLE                        ONLINE
TS_HYBRIS_DATA                 OFFLINE
TS_HYBRIS_INDEX                ONLINE
TESTTBS                        OFFLINE


We can notice that the tablespace TESTTBS and TS_HYBRIS_DATA are offline. Before proceeding, this
tablespaces needs to be made online.

QL> alter tablespace TS_HYBRIS_DATA online;

Tablespace altered.

SQL> alter tablespace testtbs online;

Tablespace altered.

SQL> select tablespace_name,status from dba_tablespaces;

TABLESPACE_NAME                STATUS
------------------------------ ---------
SYSTEM                         ONLINE
SYSAUX                         ONLINE
UNDOTBS1                       ONLINE
TEMP                           ONLINE
USERS                          ONLINE
EXAMPLE                        ONLINE
TS_HYBRIS_DATA                 ONLINE
TS_HYBRIS_INDEX                ONLINE
TESTTBS                        ONLINE

SQL> conn soumya/soumya;
Connected.

SQL> SELECT * FROM xyz;

        ID
----------
         1
         1
         1
         1
         1
         1

Finally we can see the dropped table is back with its data inside it.




Please share your ideas and opinions about this topic. If you like this post, then please share with others. Please subscribe on email for every updates on mail.