Error Ora-16664 Unable To Receive The Result From A Database
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
Failed To Send Message To Site Error Code Is Ora-16501
ORA-16664: unable to receive the result from a failed to connect to remote database error is ora-12514 database Oracle Database Tips by Burleson Consulting May 20, 2016 Question: What do I resolve this data guard error? DGM-17016: data guard error ora-16664 unable to receive the result from a database failed to retrieve status for database "XXX" ORA-16664: unable to receive the result from a database Is there any known issues with two Data Guard brokers running on same server on teo homes? This configuration
Ora 16664 Unable To Receive The Result From A Database Standby
works OK in 12c but fails in 11g. Answer: The oerr utility shows this for the ORA-16664 error: ORA-16664: unable to receive the result from a databaseCause: During execution of a command, a database in the Data Guard broker configuration failed to return a result. Action: Check the Data Guard broker logs for the details of the failure. Ensure network communication is working properly amongst the members of the
Site Returned Ora-16664
configuration. Fix any possible network problems and reissue the command. As we see, you need to check your Data Guard Broker log to see the actual cause for this error. The real error is likely related to the network, and you should follow these steps to test network connectivity. One user fixed the issue by registering the 11g and 12c instances on one single listener in the 12c home and removing the 11g listener. Now everything works fine. Also, this query can give details on the ORA-16667 error: DGMGRL> show show database verbose 'XXX'; col severity for a15 col message for a70 col timestamp for a20 select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') "timestamp", message from v$dataguard_status where dest_id=2; Because you indicate that it works OK in 12c, you should open a SR on MOSC and see if you may be hitting a bug. Other possible causes for the ORA-16667 error include. - A logon triggerwas preventing the connection from the standby databaseduring a switchover. Fix: disable the logon trigger in primary database. (MOSC id 1530881.1) - Check the non default port used in connect string of both primary and standby(tnsnames.ora). MOSC id 1228797. - The protection level does not match: select protectio
any loss suffered as a result of following ora-16664 dgmgrl any of this blog posts.. Happy Learning... Friday, June 6,
Ora-16664 Dataguard
2014 DGMRL shows ORA-16664: unable to receive the result from a database We have configured dgm-17016 a new dataguard database. So we want to verify whether the dataguard configuration is set up good. So we have used 12c Cloud control to verify http://www.dba-oracle.com/t_ora_16664_unable_to_receive.htm the Data Guard Configuration and it has ended with the above error. How to Verify Dataguard Configuration using 12c Cloud Control? http://stepintooracledba.blogspot.com/2014/06/verify-data-guard-configuration-using.html ########################## ## Error ########################## ORA-16664: unable to receive the result from a database ### Full Error DGMGRL> show configuration; Configuration - oralin_dg Protection Mode: MaxPerformance Databases: http://stepintooracledba.blogspot.com/2014/06/ora-16664-unable-to-receive-result-from.html oralin - Primary database oralin_stdby - Physical standby database Error: ORA-16664: unable to receive the result from a database Fast-Start Failover: DISABLED Configuration Status: ERROR DGMGRL> ########################## # Error Occurred ########################## Error occured while running a "show configuration" command in DGMGRL in 11.2.0.3.0 version ########################## ## Command Executed ########################## In DGMGRL, show configuration; **************************************** Step By Step Analysis ****************************************************** ######################################### # 1) Verify Data Guard Configuration in 12c Cloud Control ######################################### Initializing Connected to instance host01:oralin Starting alert log monitor... Updating Data Guard link on database homepage... WARNING: Broker name (oralin) and target name (oralin_host01) do not match. WARNING: The broker name will be renamed to match the target name. WARNING: Broker name (oralin_stdby) and target name (oralin_stdby_host02) do not match. WARNING: The broker name will be renamed to match the target name. Skipping verification of fast-start failover static services check. Data Protection Set
and sendemailEmail alert log ORA:errorsNew objects created in lastweekOracle InstanceĀ StatusRMANRMAN (Windows Script)RMAN Duplicating (for a Standby Database10g)RMAN https://easyoradba.com/tag/dataguard-broker/ Full(Weekly)RMAN Incremental(Daily)RMAN Simple (FullBackup)Script to Check RMAN Backup Status https://weidongzhou.wordpress.com/2014/10/05/different-results-from-data-guards-show-configuration-command/ inReal-TimeUnix ScriptsCheck mount point status and sendemailGenerate HTML ReportSQL*PLUSSend Birthday EmailAlertsSpool Table output to CSV | ExcelfileWindows Scripts DATAGUARD BROKER Oracle Dataguard Broker 12c with password file inASM July 17, 2016 ~ easyoradba ~ Leave a unable to comment Configure 12c dataguard broker using the below command onPrimary database server primeprd - > tnsnames for primary database primedr-> tnsnames for standby database /home/oracle::11g->dgmgrl DGMGRL> connect sys/******** DGMGRL> create configuration dg_primeprd as primary database is primeprd connect identifier is primeprd; DGMGRL> add database primedr as unable to receive connect identifier is primedr maintained as physical; Configuration "dg_primeprd" created with primary database "primeprd" DGMGRL> add database primedr as connect identifier is primedr maintained as physical; Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set Failed. DGMGRL> remove configuration; Removed configuration Set the log_archive_dest_2 settings from both the Primary and Standby databases to be nothing. alter system set log_archive_dest_2=" scope=both sid='*'; Disable then Enable the broker parameter on both the Primary and Standby databases. -- Primary alter system set dg_broker_start=false scope=both sid='*'; alter system set dg_broker_start=true scope=both sid='*'; -- Standby alter system set dg_broker_start=false scope=both sid='*'; alter system set dg_broker_start=true scope=both sid='*'; On the Primary database create the broker configuration for the Primary and Standby database and this time it should work fine with no issues since the log archive destination 2 set
Posted on October 5, 2014 by Weidong Zhou 0 Recently I built a Data Guard environment on two Exadatas with three RAC databases and did a lot of tests. The Show Configuration is probably the most frequent command I used in DG Broker. When running show configuration from dgmgrl, we usually see the same result no matter where the command is executed, primary or any standby databases. During one switchover test, I run into a weird situation. The show configuration command can return me three different results from one primary database and two standby databases, just like above the image above (cat changes into a lion from the mirror). Here are the result: Primary Database (wzxdb) DGMGRL> show configuration Configuration - DG_Config Protection Mode: MaxPerformance Databases: wzxdb - Primary database wzsdb - Physical standby database Error: ORA-16664: unable to receive the result from a database wzpdb - Physical standby database Fast-Start Failover: DISABLED Configuration Status: ERROR Checked the DG Broker log at /u01/app/oracle/diag/rdbms/wzxdb/wzkdb1/trace/drcwzkdb1.log, it has something below 07/16/2014 09:30:20 Site wzsdb returned ORA-16664. Data Guard Broker Status Summary: Type Name Severity Status Configuration DG_Config Warning ORA-16607 Primary Database wzxdb Success ORA-00000 Physical Standby Database wzsdb Error ORA-16664 Physical Standby Database wzpdb Success ORA-00000 Let's continue to check status for the standby databases. 1st Standby Database, wzpdb DGMGRL> show configuration Configuration - DG_Config Protection Mode: MaxPerformance Databases: wzxdb - Primary database wzsdb - Physical standby database wzpdb - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS 2nd Standby Database, wzsdb DGMGRL> sho