:

RSSData Guard

ORA-01552: cannot use system rollback segment

The Problem When running a script into a refreshed database, I received the following error message: ORA-01552: cannot use system rollback segment for non-system tablespace ‘string’ The Cause The database was a clone of a physical standby database, and having recently “synced” to that clone to it matched the source database data exactly and required some additional post-clone steps to […]

Continue Reading

File Added to Control File as ‘UNNAMED’ Because it was Created Under Name Already Used in this Database

Platform: Windows server 2003, SP2 Oracle: 10.2.0.4, patchset 3 (base release) The Problem You have a primary database and a physical standby database which has the standby_file_management parameter set to AUTO. You have been adding files to your primary database, and are expecting them to be added to the physical standby database automatically. Unfortunately, you notice […]

Continue Reading

ORA-16037: Message 16037 not found

These errors were appearing very regularly on our physical standby databases. They are shown when you stop the recovery operation on the  standby database and we were doing this at regular intervals per day to open the physical standby database for read only access. These errors are not an issue and no further action is required. MRP0: […]

Continue Reading

Data Guard Becomes out of Sync

If your Data Guard database gets out of sync and the archive log files are available, you can restore the log files at your primary DB (usually PRODUCTION), put the Data Guard database into recovery mode and then the logs will get shipped to your standby database automatically. If you still have the archive logs but they are […]

Continue Reading

ORA-16146 Standby Destination Control File Enqueue Unavailable

When configuring your database using data guard, it is recommended in the Oracle documentation that you set the log_archive_dest_2 parameter on the physical standby database to a value that it will take if it were to be running in the primary role mode. This is so that at failover/switchover time, you have fewer things to worry […]

Continue Reading

Using a Physical Standby Database in Read Write Mode

Using a Physical Standby Database in Read Write Mode OS: Windows Server 2003, SP2 DB: 10.2.0.4, patchset 3 (base release) Requirements We currently have two physical standby databases, one of which is at a physically different location several hundreds of miles away from the primary database site. We use these physical standby databases in case of a […]

Continue Reading

Open a Physical Standby Database for Read Only

Once you have configured your physical standby database and it is functioning as you require, you may consider opening the database at certain times for read only access. Why would and wouldn’t you want to do this? Benefits You can reduce the load on the primary database if there are reporting jobs which are required […]

Continue Reading

Data Guard Sessions

From my experience, it is common practice to open up a physical standby database for read only, reporting purposes. If you’re running the data guard set up in maximum performance mode, it makes sense to allow some use of the physical standby DB so as to reduce load on the primary database server. You can […]

Continue Reading