Hot answers tagged

3

If the database is setup correct: no direct path load. If a standby database is depending on the changes captured on the primary database, the primary database should be setup with force logging. If for some reason the force logging setting is not in place, after such an operation the affected datafiles should be transferred to the standby site[s]. Failing ...


2

Fault-tolerant storage, a stand-by database (Data Guard in your case), and the database backup are three different solutions to different types of problems. Depending on how much downtime you can afford, you may need to implement all three.


2

I simply do not believe. It's impossible. There is process called FAL (Fetch Archive Log), it can happen that redo-logs are not TRANSFERRED in chronological order, but anyway they must be APPLIED in chronological order. Also logical standby has can have some gotchas but those are not related to network link. (For example for some reason LOCK TABLE statement ...


2

There aren't any special considerations that need to be taken into account when setting up a RAC->No RAC Primary->Standby configuration. In fact, there's a White Paper written by Oracle which explains the setup. The Oracle documentation is here.


2

Try adding (SERVICE=Dedicated) to your TNS entry on the client computer that you are using and then run your query again. There could be other causes but this is the most common: you are trying to access data using a shared connection when a dedicated connection is required. Edit: Are there any other log or trace file entries when this error happens?


2

The unique names of the databases in a Data Guard configuration are listed in the log_archive_config parameter in the following form: log_archive_config='DG_CONFIG=(PDB10,PDB10_STBY)' You can remove the old one and add the new one as: alter system set log_archive_config='DG_CONFIG=(PDB10,PDB10SBY)'; After this, you can set log_archive_dest_N to the new ...


2

You can try using: ps -ef | grep -v grep | grep ora_pr Or if data guard is in use: ps -ef | grep -v grep | grep ora_rsm


2

The notes about this in Oracle 12.1.0.2 state that it is not required to move/copy the files from the primary during the plugin. The note also states that in this release the copy of the standby files of the source can be postponed using the standbys=none clause. This makes it possible to plugin a large primary database in a primary container database and ...


2

You can not do this with a physical standby, you will need some kind of logical replication. With a logical standby, you can skip DMLs, but that would skip all DMLs. With Oracle Goldengate, you can easily skip deletes, as you can specify the IGNOREDELETES option: IGNOREDELETES Ok, now let's assume you have configured your system to ignore deletes. Imagine ...


2

If the standby site becomes unreachable, the primary site will not delete archivelogs as they will be still needed by the standby site. If you try to backup and delete these archivelogs, you will receive an ORA-08137 error, and eventually your archive area will become full and your database will stall. Setting log_archive_dest_state_n to DEFER lifts this ...


1

The initialization parameters are not supposed to change while bouncing the database except in one case, that is if the modification was only for currently running instance(SCOPE=MEMORY). The following are the steps to modify initialization parameters using Enterprise Manager. To modify initialization parameters for the currently running instance, and ...


1

Can standby database of a non-container database be pluggable or vice versa? In order to plugin a non-CDB standby database into a CDB, the non-CDB standby database needs to be of version 12c as well. So existing non-CDB databases will need to be upgraded to 12c before they can be part of a 12c CDB. Suppose there are 2 CDBs on 2 different server. ...


1

My procedures seem valid... I was able to test the logical DB, then bring it back into an exact copy Logical Standby and re-enable SQL Apply without issues. However, there was a minor change to my procedures: flashback database requires that the DB is in mount state and that alter database open requires resetlogs or noresetlogs. Therefore, the amended ...


1

In this Oracle page entitled Database High Availability Best Practices it discusses Data Guard Deployment Options: Requirement of Zero data loss protection and availability for Oracle Database: Data Guard Maximum Protection or Maximum Availability (SYNC transport) and Redo Apply (physical standby) Requirement for Near-zero data loss (single-digit ...


1

NOAFFIRM means the redo transport will be acknowledged before writing the received redo to disk (standby redo logs). ASYNC noaffirm means the log transfer method is ARCH right? No, it does not. Without specifying LGWR or ARCH, LGWR is the default. You can check it on the primary database by: select archiver from v$archive_dest where dest_id = 5; ...


1

You can check some options like checking FAL_SERVER parameter, LOG_ARCHIVE_DEST_n parameters, Dataguard Broker, Recovery Catalog, Cloud Control, etc.. if they are used, but none of them are mandatory for a DataGuard configuration. In fact, the standby nodes doesn't need to send any kind of information to the Primary db at all. Since the heartbeat is ...


1

Ok, so I had some time to waste, and this is just for the "fun" or "interesting" factor. It's nowhere near that I would use in a real scenario, I have played with it in my lab environment on x86-64 Linux platform, with a few 10g, 11g and 12c databases. At least you can do this even if the database is shut down. When you do a controlfile dump with: alter ...


1

The message indicates that no archivelog exists with this sequence in the current incarnation. Failover starts a new incarnation, and log sequences start from 1 again. Let's say your database is at sequence 10 now, and the log sequence was 159 before the failover. V$ARCHIVED_LOG at this point still contains entries about previous incarnation, so the above ...


1

Without opening the standby for read-only, you won't be able to identify specific changes to specific physical objects, instead you'll have to verify that a specific set of changes have been applied to the remote standby. Views including v$standby_apply_snapshot, v$archived_log, v$archive_gap, v$dataguard_stats, v$managed_standby are all ones that I use on a ...


1

When you drop user on primary then this will be also reflected on secondary site. Also impdp will work as expected. But when you are about to import large amount of data MAA might slow down the whole procedure significantly. If you have enough experience with RMAN you might try: shutdown and disconnect the secondary import data into master backup master ...


1

If you setup a logical standby, then you can change the data in the logical standby. You will probably have trouble supporting the kind of change that you seem to want. Have you thought about talking to the vendor to see if they can add the logic that you want to the product you pay them for? If the vendor makes the change, then they will/should support it. ...


1

From the documentation: startup_clauses The startup_clauses let you mount and open the database so that it is accessible to users. MOUNT Clause Use the MOUNT clause to mount the database. Do not use this clause when the database is already mounted. MOUNT STANDBY DATABASE You can specify MOUNT STANDBY DATABASE to mount a ...


1

Yes, no issue at all. This is done over and over. For instance two servers taking each others database(s) in standby mode.


1

You cannot run any DML in a logical standby database unless you deactivate, temporary, the guard feature. To overcome you isse you can do: SQL> ALTER DATABASE GUARD NONE; SQL> SELECT GUARD_STATUS FROM V$DATABASE; GUARD_STATUS -------------------- NONE And then run your dbms_stats.



Only top voted, non community-wiki answers of a minimum length are eligible