Database Solutions

For Security reasons, DBA have been asked multiple time not to use sys user for DBA activity or replication. In this blog, We will list down to step to setup replication user for oracle standby database.  1) Create user for redo shipping on Primary database.  2)Backup password file on primary and secondary side.  3) Grant below privileges to redo ship user      grants sysoper to redoship;      grant create session to redoship;  4) Copy the password file to remailing nodes. 5)Confirm redoship user is reflecting on all instanced.    select * from gv$pwfile_users where username='REDOSHIP'; 6) Confirm user have been created on the standby database.      select * from gv$pwfile_users where username='REDOSHIP'; 7) Defer the log shipping to standby database.      alter system set log_archive_dest_state_2=enable scope=both sid='*'; 8) Copy the password file from primary node to all standby db nodes.  ...

Oracle Standby - Rolling Upgrade using Transient Logical Standby database In Database world, Getting downtime for mission critical database is very difficult. Specially for activity like upgrading database where downtime can be easily vary from 4 Hours to 8 Hours. We can reduce the downtime significantly , using Rolling Upgrade using Transient Logical Standby database .  In this blog ,We will  illustrates how we can perform a rolling upgrade from Oracle 12c Release 1 to Oracle 12c Release 2 using a Transient Logical Standby database. This approach will miminise the downtime required for an upgrade which can potentially run into several hours down to just the time required to perform a switchover which could be a few minutes in most cases. A rolling upgrade using a Transient Logical Standby database at a very high level will involve three main stages or steps: 1) Temporarily convert a physical standby database to a logical standby database using the new KEEP IDENTITY claus...

Oracle Standby - Roll Forwarding Standby Database - Over the Service In cases where a physical standby database is far behind the primary database, an RMAN incremental backup can be used to roll the standby database forward faster than redo log apply. In this procedure, the RMAN BACKUP INCREMENTAL FROM SCN command is used to create an incremental backup on the primary database that starts at the current SCN of the standby and is used to roll forward the standbydatabase. With Oracle 12c database , We can roll forward or restore standby database over the service. So primarily , there are two method to roll forward database 1) Using Conventional Incremental RMAN Backup and 2) Using RMAN Recovery of the standby database over the Service(of primary Database).  In this blog , We will discuss about Second method of Roll forwarding i.e RMAN recovery of the standby database over the service. F ollow the below steps to Roll Forward your Standby database: 1) Stop the MRP process on the stan...

Oracle Standby - Roll Forwarding Standby Database - Conventional RMAN Incremental In cases where a physical standby database is far behind the primary database, an RMAN incremental backup can be used to roll the standby database forward faster than redo log apply. In this procedure, the RMAN BACKUP INCREMENTAL FROM SCN command is used to create an incremental backup on the primary database that starts at the current SCN of the standby and is used to roll forward the standby database. With Oracle 12c database , We can roll forward or restore standby database over the service. So primarily , there are two method to roll forward database 1) Using Conventional Incremental RMAN Backup and 2) Using RMAN Recovery of the standby database over the Service(of primary Database).  In this blog , We will discuss about first method of Roll forwarding i.e Conventional Incremental RMAN Backup. F ollow the below steps to Roll Forward your Standby database: 1) Stop the MRP process on the standby ...