DataGuard passage 2
Hi all
9i
RHEL5
I am show passage on our dataguard configuration.
The following command are reversed:
SQL > archive logs list;
Database log mode Archive Mode
Active AutoArchive
Archive destination /u02/oradev/devdb/9.2.0/dbs/arch
More old sequence of journal on line 113
Log sequence archive 115
Current log sequence 115
SQL > ALTER DATABASE COMMIT to SWITCH mode STANDBY;
ALTER DATABASE COMMIT TO THE PASSAGE IN STANDBY MODE
*
ERROR on line 1:
ORA-16014: log 3 sequence # 115 not archived, not available destinations
ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03a.dbf'
ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03b.dbf'
ORA-16014: log 3 sequence # 115 not archived, not available destinations
ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03a.dbf'
ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03b.dbf'
Why is the error?
I tested before the digital switchover and it was good.
Help, please.
Thank you very much
JC
Jenna, run swithover using this guide:
-1 in the original primary:
change the database for validation to the passage in standby mode with the end of the session;
stop immediately;
startup nomount;
ALTER database base_de_donnees eve of Mount;
ALTER system set aq_tm_processes is 0 scope = both;.
ALTER system set log_archive_dest_state_2 = reporter;
Select switchover_status in the database of v$.
2 original to standby mode:
change the database for validation to the passage at the elementary level with the end of the session;
stop immediately;
startup
ALTER system set aq_tm_processes is 5 scope = both;.
ALTER system set log_archive_dest_state_2 = enable;
NOW IT IS ELEMENTARY, BUT YOU STILL HAVE NOT ALL EXPECTATIONS!
-3 primary and future old standby:
recover managed standby database disconnect;
check V$ Archived_log and v$ Archive_Gap
If you find an error, please report it.
Concerning
Tags: Database
Similar Questions
-
DataGuard passage failed: impossible to failover, primary database is always "PRIM".
Hi all
DataGuard digital switchover is Getting failed with the below error:
DGMGRL > passage to the "dry";
Continue to pass, please wait...
Error: ORA-16664: impossible to receive the result of a database
Failed.
Impossible to failover, primary database is always "PRIM".
Note:it comes to node unique database with physical styandby.
=====================================================
In alert log file provides, I am getting below the error during the failover operation:
Fatal OR connect 12514 error, connect to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rac1.localdomain)(PORT=1524)))(CONNECT_DATA=(SERVICE_NAME=PRIM_DGB)(INSTANCE_NAME=PRIM)(CID=(PROGRAM=oracle)(HOST=rac2.localdomain)(USER=oracle)))
Please suggest to solve this problem.
Thank you.
Problem is fixed - value StaticConnectIdentifier checked to a database of primary and standby in dgmgrl ==> primary port and standby was wrong wrt to the listening port value.
Step 1 > error ORA-16664 and ora-12514
==> check StaticConnectIdentifier value for a primary database and a standby in dgmgrl ==> primary port and standby had value default IE 1521
Primary:
SEE THE VERBOSE "PRIM" DATABASE
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'
Standby time:
SEE THE DETAILED "DRY" DATABASE
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)
Step 2 > listening port for the primary and standby is 1524 and 1525, so change these manually.
Primary:
SQL > show parameter local_listener
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
LOCAL_LISTENER chain
SQL > alter system set local_listener ='(ADRESSE = (PROTOCOL = TCP) (HOST = rac1.localdomain) (PORT = 1524))
Standby time:
ALTER system set local_listener = '(ADDRESS = (PROTOCOL = TCP) (HOST = rac2.localdomain) (PORT = 1525))';
#edit database 'PRIM' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac1.localdomain) (PORT = 1524)) (CONNECT_DATA = (SERVICE_NAME = PRIM_DGMGRL) (INSTANCE_NAME = PRIM)(SERVER=DEDICATED)))'
#edit database 'DRY' set the property StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac2.localdomain) (PORT = 1525)) (CONNECT_DATA = (SERVICE_NAME = SEC_DGMGRL)(INSTANCE_NAME=SEC) (SERVER = DEDICATED)))'
-
Hi all
9i
RHEL5
I'm testing the 2nd passage to the so that my original PRIMARY will return.
The current primary (original Eve), I run the following:
SQL > ALTER DATABASE COMMIT to SWITCH mode STANDBY;
Database altered.
SQL > SQL > shutdown immediate;
ORA-01507: database not mounted
ORACLE instance stops.
SQL > STARTUP NOMOUNT;
ORACLE instance started.
Total System Global Area 581506668 bytes
Bytes of size 452204 fixed
402653184 variable size bytes
167772160 of database buffers bytes
Redo buffers 10629120 bytes
SQL > ALTER DATABASE MOUNT STANDBY DATABASE;
But the above command is suspended and did not complete
I checked the (primary) alerts log and all I can see are:
ALTER DATABASE MOUNT STANDBY DATABASE
Kills Jul 29 21:59:44 2015
Mount of redo thread 1, with mount id 3964660556
Kills Jul 29 21:59:44 2015
Eve, mounted database.
Completed: ALTER DATABASE MOUNT STANDBY BASE
Kills Jul 29 21:59:54 2015
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
Start of recovery media: managed standby recovery
Media Recovery wait thread 1 seq # 93
Sea 29 22:04:27 Jun 2015
Restart the background process dead QMN0
QMN0 started with pid = 9
What causes the command hang? He explains the background process QMN0 is dead?
Help, please...
Thank you very much
JC
Hello
Then, you can try bouncing the instance once more and make sure aq_tm_processes is to have any value, since you can calm him down.
ALTER system set aq_tm_processes is 0 scope = both;.
-Pavan Kumar N
-
Active Dataguard passage puts new Eve in time real query
Hi gurus,
If you use Active Dataguard, after swicthover/failover using observer and dg broker no sthe new Eve will be time real query mode (ADG) or manually having to open the db in read-only mode.
Please let me know.
Thank youYes, it is:
[uhesse]$ dgmgrl sys/oracle@prima DGMGRL for Linux: Version 11.2.0.1.0 - Production Copyright (c) 2000, 2009, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. Connected. DGMGRL> show configuration Configuration - myconf Protection Mode: MaxAvailability Databases: prima - Primary database logst - Logical standby database physt - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS DGMGRL> show database physt Database - physt Role: PHYSICAL STANDBY Intended State: APPLY-ON Transport Lag: 0 seconds Apply Lag: 0 seconds Real Time Query: ON Instance(s): physt Database Status: SUCCESS DGMGRL> switchover to physt; Performing switchover NOW, please wait... New primary database "physt" is opening... Operation requires shutdown of instance "prima" on database "prima" Shutting down instance "prima"... ORA-01109: database not open Database dismounted. ORACLE instance shut down. Operation requires startup of instance "prima" on database "prima" Starting instance "prima"... ORACLE instance started. Database mounted. Database opened. Switchover succeeded, new primary is "physt" DGMGRL> show configuration Configuration - myconf Protection Mode: MaxAvailability Databases: physt - Primary database prima - Physical standby database logst - Logical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS DGMGRL> show database prima Database - prima Role: PHYSICAL STANDBY Intended State: APPLY-ON Transport Lag: 0 seconds Apply Lag: 0 seconds Real Time Query: ON Instance(s): prima Database Status: SUCCESSKind regards
Uwe Hessehttp://uhesse.WordPress.com
-
Passage of Oracle Dataguard and DNS
Hi, a few days ago, we planned a passage in a configuration of 10g dataguard (dataguard pasive) between the 2 servers.
primary: Europe.com APP
secondary: APP1 in Asia.com
The two databases was Oracle 10.2.0.3 in Redhat (single instance)
Everything is going well with databases and the digital switchover but what happened with the web-based applications?
I have a lot of web PHP applicattion provided with a string of connection with OIC and oracle customer, all have the connection as user/pass@dbname where dbname is defined in the local tnsnames.ora with DNS host names.
(All have xxx/xxx@APP), and was APP (host:europe.com and SID = APP)
Europe.com was ip 1.1.1.1
Asia.com has been ip 2.2.2.2
My primary instance was APP (name sid) and the standby APP1 (name sid) but what happened when I pass the dataguard?
Yes, because we have a lot of requests and we don t change the connection string, each of them tries to connect to the new basis of Eve physics APP which is in Europe.com. (and the main news is APP1 in Asia.com)
Well, first of all, I must change the SID in the database (same as the primary database) waiting for the connection string, for which I have: (thus development are don't want to change the string of connection...)
(1) immediate stop aid database
(2) remove the dataguard broker configuration,
(3) change the instance name in the spfile APP1 to APP.
(4) change the name of db in the spfile APP1 to APP.
(5) change the setting fal_client (INSTANCE_NAME = APP1) to (INSTANCE_NAME = APP)
(6) change the app APP1 orapwd file
(7) Exchange configuration bash_profile APP and re start the database pending.
(8) check the listener.ora, so that the new listening service is APP and no APP1
(8) with respect to the dataguard broker configuration config
OK, everything works very well and we have the main and the database pending with the same SID.
But what happened with the dns servers? because the web-based applications will try to connect to APP but APP has been defined as Europe.com and I want to redirect Asia.com as primary database.
Well, first of all, I changed all my settings and broker dataguard over IP and not dns configuration files, so I made a guide to procedure for the passage to the then when we said that, first we must transition to digital, data bases and then the surface NET must change the DNS for new Europe.com dns point to 2.2.2.2 ip
After that, everything works great!
So in conclusion, to forward a permutation with dataguard (which was an excellent feature) check the connection of the chain of applications and take care of them) and if necessary, use the same SID for the two (databases) and emergency
(In Oracle 12 c, we have a lot of thing to use as a continuation of the app for that)
Kind regards
Hernan
Hi Herman,.
Maybe I'm mistaken, please correct me if this is the case.
Assuming you are using oracle customer why not just use the construction in the mechanism for this purpose? DNS has nothing to do with it, but I see people using it yet for this - it is not only suitable for failovers, I do not have my TTL of 60 seconds or less to my recordings of A.
I had a project for banking HA where after permutation is launched the application (Tomcat) could in a minute to connect automatically to the database of watch on the Internet. First, you must use the database instead of SID service, so you can have the same service on the previous day. What more have a service, you can be sure that it will run the day before until it becomes primary, otherwise you can find yourself in a funny situation. Secondly, why not using built in failover of the connection string parameter, this way you can queue db (s) and in the case where your primary does not that the oracle client will simply try to connect to the waiting (to search for the same service). To ensure that the standby database does not have the service at any time, you can deploy trigger (AFTER startup) to check the role of database, if it is 'primary' it starts just the database service.
Kind regards
EVS
-
Hi all
We use Oracle10g.
We have configured the Oracle Dataguard with two databases (a primary and standby).
We perform a failover, like this for example:
On the primary database:
On the basis of data on hold:ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN; SHUTDOWN IMMEDIATE; STARTUP MOUNT;
So, when I perform this failover, what happens with the main data bases and rescue incarnation?ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN; ALTER DATABASE OPEN; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
Incarnation is updated? No problem with that?
Another question: our idea is to create another database of physical standby on the other server.
perform a failover for this new physical expectation change your primary role and disable the former primary database.
no problem with this procedure? no problem with the first database pending created?
Thank you very much!!!OK, it's big enough.
If she was smaller, I would consider a move SCP cold of it on the new server.
In theory, you should be able to make a pass to the you standby current. With her in the lead role, create a new standby with RMAN duplicate on the new server after changing your listener and tnsnames. Then make another pass and switch the spfile.
I never did and I would like to test, test, test.
One of the concerns is the eve runs with a Standby controlfile and this could make this failure.
But that sense?
I could set up a few databases to test for something like that.
In the meantime a few permutations of practice is not a bad idea.
Otherwise, you could try a clone RMAN of your primary on the new server. It is perhaps the best way to go long term.
The two latest databases Oracle 10 that I moved were much smaller. I have set up the structure of files on the new server the same as the old server and the closing of the database and move all the files including the spfile and password file using SCP. After a quick listen and tnsnames on both sides, I restarted and Data Guard never missed a beat.
Also, I moved a database ensures Oracle 10 once and while I do not have a document that I rough notes:
Step 1 On the primary database alter system set log_archive_dest_state_2=defer; Step 2 On the current standby alter database recover managed standby database cancel; ( Then shut it down ) Step 3 Create database directories on the new server. ( The FRA, the admin udump etc. and system and data ) Step 4 Edit the tnsnames.ora file on the current primary Step 5 Add tnsnames.ora and listener.ora to the new server. Step 6 Move password and spfile files to the new server. Step 7 Tnsping both servers Step 8 Use scp to move the database to the new server. scp my.host.com:/u01/app/oracle/oradata/ORCL/sysaux01.dbf /u01/app/oracle/oradata/ORCL/ and so on... Step 9 Double check all files Step 10 Start the database and enable the standby destination and recoveryIt was a gesture of the day before, but a primary movement in this way is very similar. My shop has a fast network and I was able to move a database of 100 GB in about 2 hours.
You could do a permutation, stop the old elementary school and move it using the SCP. Then when he did raise MOUNT and set log_archive_dest_state_2 = reporter on it. Start the collection and if it work all just switch back to it. This way your old server is ready like the back where everything turns to dust. But with your Eve launched, you have almost no downtime. I would test it a few more times on small test systems.
Best regards
mseberg
-
Hello!
I have a functional configuration of Dataguard 10 g created by EM 10.
I have a number of clients connected to the primary. Customers use tnsnames to connect.
When the main breaks down all my contacts to loose customers.
Is it possible to configure my tnsnames on customers so that they also passes the current database?
/ RogerRoger,
We have a similar situation where we implemented when the connection failover in tnsnames.ora
You must save the two databases with two listeners and add the backup database in the entrance of the NER for primary.
http://www.Oracle.com/technology/deploy/availability/PDF/MAA_WP_10gR2_ClientFailoverBestPractices.PDF
can help if this isn't your needs (we have a simple web-based application so CTF is fine for us)If this isn't for you then you will probably need to speak with the developers of applications and choose one of the options in the file above.
Greg
-
DataGuard broker not starting not not instances after passage in the
I've implemented dataguard broker.
Primary (Server1)
instance name: test
dbname: sf_test
Standby (Server2)
instance name: test
DB: test
I want to do the test from server2 as main and server1 sf_test as before.
DGMGRL > switchover to test
Continue to pass, please wait...
Operation requires the stop of the instance 'test' on database 'sf_test '.
Instance closing 'test '...
ORA-01109: database is not open
The database is dismounted.
ORACLE instance stops.
Operation requires the judgment of the instance 'test' on the 'test' database
Instance closing 'test '...
ORA-01109: database is not open
The database is dismounted.
ORACLE instance stops.
Operation requires the start the instance 'test' on database 'sf_test '.
Start the instance 'test '...
Unable to connect to the database
ORA-12514: TNS:listener is not currently of service requested in connect descriptor
failed. You are no longer connected to ORACLE
Please log in again.
Could not start the instance 'test '.
You must start the instance 'test' manually
Operation requires the start the instance 'test' on the 'test' database
You must start the instance 'test' manually
Successful, the new principal is 'test '.
DGMGRL > outputHello..
Refer to Metalink Doc ID: Note: 308943.1 -automatic restart of databases over the failure of the transition to digital with ORA-12514 in DGMGRL
>
Cause:-the cause of this problem is that without the necessary entry listener.ora, DGMGRL is unable to connect to the databases once they were arrested during the failover operation.
>
[http://blogs.oracle.com/AlejandroVargas/gems/DataGuardBrokerandobserverst.pdf]
HTH
AnandPublished by: Anand... on November 1st, 2008 04:17:-added 2 links
-
Passage to the doubts DataGuard
Hi all
I have a gr 10, 2 primary and 2 databases on hold (standby1 and standby2). We have a plan to do a test of transition to digital. If we do a permutation between primary and standby1, what will the status of the standby2?
The standby2 database themselves will continue to receive its new primary (old standb1) archive logs?
Thank you
Mark
Thank you. So you mean the standby2 database FAL_SERVER I should it to point to the new primary? Also the log_archive_dest_X of the first news I have to make sure it points to the Standby2 database?
Thank you
Mark
-
Scenario is...
Host A is the main
Host B is a sleep mode
Host C is a standby
Now, I know that we can define a-> B and A-> C
Can we define a-> B-> C?
Essentially using as a transition between A B and C. Or you can see as being in a DMZ b.
B shall be Active Data Guard or something special?
I guess what I'm really asking is a standby can be used as a source for another standby.See http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/cascade_appx.htm#i638620 for more information on cascading standby Destinations. There are a few restrictions:
Cascade has the following restrictions:
* Logical and snapshots of databases pending cannot cascade primary database recovery.
* SYNC destinations cannot cascade primary database recovery in a Maximum Protection Data Guard configuration.
* Cascading is not supported in Data Guard configurations that contain a primary database to Oracle Applications Cluster RAC (Real).
* Cascading is not supported in the Data Guard Broker configurations.Keep an eye on this chapter and Note 409013.1 "Cascaded Standby Databases" in the next update for 11.2 spell :^)
Larry
-
Stop listener as part of the transition to the DataGuard?
I have a database of primary and Standby, configured with DataGuard. A third server runs the process of observation to monitor from the database when the principal becomes unavailable. It all works and we are happy with it from the point of the DB of the things. The database version is 11.2.0.4 running on RedHat 6.4
The demand side, we use WebLogic and have set up the connection string of JDBC using the following format:
(DESCRIPTION=(ADDRESS_LIST=(FAILOVER=ON)(LOAD_BALANCE=OFF)(ADDRESS=(PROTOCOL=TCP)(HOST=production-db-a)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=production-db-b)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=abc)))
When the primary database server is stopped, then the observer notices and will be a change occurs and just continues to work.
However, what's happened is that there are delays in network that caused the observer make the pass on the eve (production-db-b) and makes it the main. What is expected (except for wait times of network that is under review). Finally, the network problem disappeared and the original primary server (production-db-a) is back on the network and he opted to be a watch. So far so good. If all goes well on the side of the things database. However, on the side of the demand of the things, the application attempts to connect to production-db-a, since it is now available again, but service is on production-db-b because he has fallen.
If we move off the coast of the production-db-a listener, then all is good again. We have configured listeners, LISTENER to database service and LISTENER_DGMGRL for dataguard that runs on port 1522. So just stop LISTENER while LISTENER_DGMGRL running on production-db-a seems to fix the problem.
The question is now, peut LISTENER stop automatically DataGuard during the passage of the day before and started for the primary, or is there another solution for this problem?
Your tnsnames.ora connection string refers to
(CONNECT_DATA = (SERVICE_NAME = abc))
What is the deault for the database service? If so, do not use it. On the contrary, create another service with and start it by calling DBMS_SERVICE. START_SERVICE in a trigger to start (or after triggering change in role) which checks if the database is currently a primary or secondary.
-
Passage of the roles - ensures primary school
Hi all
We have a requirement in our environment to switch mode on primary eve. This is to stop the machine from primary database since it is now more than 350 days.
I have a few crossing the reg of doubts.
We have two servers
1 Server1-Prim - main database hosts with SID - LPBT
LISTENER - WITH SID-LPBT ON 1521 PORT WITH HOST = 80.0.1.187
TNSNAMES with entries for the two services LPBT and STBYLPBT
2 Server2-Stby - secondary database hosts with SID - STBYLPBT
LISTENER - WITH SID-STBYLPBT ON PORT 1521 WITH HOST = 80.0.0.240
TNSNAMES with entries for the two services LPBT and STBYLPBT
Our is a physical standby and passage procedure below of the manually using SQL commands instead of dataguard
Digital allows a primary and standby to switch roles without data loss.
No need to recreate the old primary school. Conducted for a scheduled maintenance.
Steps to follow:
1. check if primary can be switched to sleep mode
SQL > select switchover_status from database v$.
If returns the value "TO_STANDBY", its good to pass the primary role of Eve.
2 convert primary to standby
SQL > alter database validation to the transition to physical standby mode;
If the value is "ACTIVE SESSIONS" in step 1, then
SQL > alter database validation to the transition to physical standby with the stop of the session;
3. stop and restart the old primary as before
SQL > shutdown immediate;
SQL > startup nomount;
At this point, we now have two databases, such as the day before.
4. on the basis of data target standby, check status of the digital switchover. If the value is "TO_PRIMARY" then
SQL > alter database validation at the grade crossing;
If the value is "ACTIVE SESSIONS", then add "WITH the STOP of the SESSION" to above the command.
5. stop and restart the new primary database
SQL > shutdown immediate; start-up;
6. start back on new database (former primary) pending
SQL > alter database mount standby
SQL > alter recover managed standby database disconnect log file using current;
----------------------------------------------------------------------------------------------------------------------------------------
My question is after the transition to digital, if we connect as 'conn sys@lpbt as sysdba' since sqlplus window from another pc, how the request will go to the new primary database server (80.0.0.240) since tnsnames only will point to the old principal server (80.0.1.187).
can you please explain how it works, or should we add a few more entries to the listener or files tnsnames.
Please notify
We have three databases and we use the db_links inside these three db for transactions
so can we not use as main stbylpbt, as db_links does refer to db_link-host - lpbt solve in tnsnames who will fail.
Yes, you are right. You have to re-create these links db to point to your new primary database ("old Standby") using guests as "STBYLPBT".
As mentioned previously, you must redirect all your applications and users to point to the new primary database by making use of the "STBYLPBT" entry TNS.
in this case, after the success, if we need to change db_names (vice_versa) and listeners as was before
You don't have to do anything with regard to the 'db_name' or with the listener. Db_name remains the same on the primary and implementing standby.
I don't understand the reason for you to change the listener. 1 listener on the server must be able to accept connections.
80.0.0.240 is your host before and there is a listener on this. After a failover, it becomes your primary database. You would try to connect to the new primary database with input TNS "STBYLPBT." It reminds the host '80.0.0.240' which is your new primary database. Hope this clears.
STBYLPBT =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 80.0.0.240)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = stbylpbt)
)
)
-Shivananda
-
Passage of custody of data with broker fails with ORA-16570 / ORA-16665
I'm using Data Guard 11 g on Windows Server 2012 64 Bit. Recently, I have configured the broker to manage the permutations more uncomfortable.
Unfortunately the digital switchover does not work. Broker Setup seems fine, since I can activate t and redo apply works perfectly...
Now, the behavior is as follows... Once I put the passage through brokers, it shows the following:
DGMGRL > passage to the smart_stb
Continue to pass, please wait...
Error: ORA-16665: wait for the result of a database
Failed.
Unable to failover, primary database is always "smart".
The digital switchover happens, there is no restart of the primary database well! Does not appear to be linked to a DGMGRL buggy service entrance. In fact the database will not yet descended. The principal is supending all processes while trying to do so. Broker runs into a timeout, of course, but the principal remains in a State of supending. The primary doesn't seem to be able to cominicate with side standby or vice versa. Which is strange since the restoration of log shipping and apply is workng fine as mentioned... do a manual failover. I don't know what could cause this kind of behavior... Double checked everything. Once I restart the two databases and align on the rule of law that the digital transition is complete. But Needless to say that it is not intending to use the broker...
Primary DRC.log States the following:
2014-09-10 746441090-02000000 MICHAEL 09:13:01.378: PASSAGE to smart_stb
2014-09-10 746441090-02000000 MICHAEL 09:13:01.378: start execution of the task: the DIGITAL switchover
2014-09-10 09:13:01.378 NSV1: using RFIUPI_DGCI_CDESC
2014-09-10 09:13:01.409 NSV1: using RFIUPI_DGCI_CDESC
2014-09-10 09:13:01.409 02001000 746441090 notifier Oracle Clusterware to the primary database of disassembly for the DIGITAL switchover
2014-09-10 09:13:01.425 ACLS: not configured CRS, config = 2
.
2014 09-10 02001000 746441090 MICHAEL 09:13:01.425: display primary instances for PASSAGE of phase 1
2014 09-10 02001000 746441090 MICHAEL 09:13:01.425: State of rfi_post_instances() for CTL_SWITCH = ORA-00000
2014-09-10 09:13:01.425 INSV: message received for publication of inter - the instance
2014 09-10 02001000 746441090 MICHAEL 09:13:01.425: dispersants message to STANDBY for TRANSITION phase BEGIN
2014-09-10 09:13:01.425 req ID 1.1.746441090, CTL_SWITCH opcode, phase BEGIN, 5 flags
2014-09-10 09:13:01.425 NSV1: using RFIUPI_DB_INST_CDESC
2014 09-10 02001000 746441090 MICHAEL 09:13:01.425: entered rfmsoexinst() for phase BEGIN
2014-09-10 09:13:01.425 INSV: response for message with
2014-09-10 09:13:01.425 req ID 1.1.746441090, CTL_SWITCH opcode, phase BEGIN
2014 09-10 02001000 746441090 MICHAEL 09:13:01.425: primary instances display for transition to THE phase 2
2014 09-10 02001000 746441090 MICHAEL 09:13:01.440: State of rfi_post_instances() for CTL_SWITCH = ORA-00000
2014-09-10 09:13:01.440 INSV: message received for publication of inter - the instance
2014 09-10 02001000 746441090 MICHAEL 09:13:01.440: dispersants message to STANDBY for transition to THE phase of DISMANTLING
2014-09-10 09:13:01.440 req ID 1.1.746441090, opcode CTL_SWITCH, disassembling, 5 flags
2014 09-10 02001000 746441090 MICHAEL 09:13:01.440: entered rfmsoexinst() for disassembling
2014-09-10 09:13:01.440 RSM0: received the State value ask: rid = 0 x 01041001, sid = 0, phid = 1, econd = 2, sitehndl = 0 x 02001000
2014-09-10 09:13:01.440 Log transport resources: SetState OFFLINE, DISASSEMBLY phase, external Cond SWITCH-OVER-PHYS_STBY
2014-09-10 09:13:01.440 RSM0: received the State value ask: rid = 0 x 01011001, sid = 4, phid = 1, econd = 2, sitehndl = 0 x 02001000
2014-09-10 09:13:01.440 of database Resource [IAM = PRIMARY]: 0 x 02001000 SetState PHYSICAL-APPLY-ON, DISASSEMBLY phase, external Cond SWITCH-OVER-PHYS_STBY, handful of Site target
2014-09-10 09:13:01.440 RSM0: execution of SQL [ALTER DATABASE COMMIT to SWITCH STANDBY mode PHYSICS WITH the STOP of the SESSION]
2014-09-10 09:13:06.630 SQL [ALTER DATABASE COMMETTRE at PHYSICS CROSSING SHALL WITH SESSION SHUTDOWN] executed successfully
2014-09-10 09:13:06.630 RSM: compensation IncarnationTable internal property of the site 0 x 01010000
2014 09-10 02001000 746441090 MICHAEL 09:13:06.630: Broker determines this restart of the instance is necessary: operation = status = ORA-16570
2014 09-10 02001000 746441090 09:13:06.630 resources: smart (01011001) State: PHYSICAL-APPLY-ON
2014-09-10 09:13:06.630 INSV: response for message with
2014-09-10 09:13:06.630 req ID 1.1.746441090, CTL_SWITCH, disassembling opcode
2014 09-10 02001000 746441090 MICHAEL 09:13:06.630: Instance 'smart' (ID 1) returned ORA-16570
2014-09-10 09:13:06.630 02001000 746441090 for disassembling of the CTL_SWITCH operation
2014-09-10 09:13:06.646 NSV1: using RFIUPI_DGCI_CDESC
2014 09-10 02001000 746441090 MICHAEL 09:13:06.646: primary instances display for transition to THE phase 2
2014-09-10 09:13:06.646 INSV: message received for publication of inter - the instance
2014 09-10 02001000 746441090 MICHAEL 09:13:06.646: State of rfi_post_instances() for CTL_SWITCH = ORA-00000
2014-09-10 09:13:06.646 req ID 1.1.746441090, opcode CTL_SWITCH, disassembling, 5 flags
2014 09-10 02001000 746441090 MICHAEL 09:13:06.646: dispersants message to STANDBY for transition to THE phase of DISMANTLING
2014 09-10 02001000 746441090 MICHAEL 09:13:06.646: entered rfmsoexinst() for disassembling
2014-09-10 09:13:06.646 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:13:06.646 INSV: response for message with
2014-09-10 09:13:06.646 req ID 1.1.746441090, CTL_SWITCH, disassembling opcode
2014 09-10 02001000 746441090 MICHAEL 09:13:06.646: Instance 'smart' (ID 1) returned ORA-16570
2014-09-10 09:13:06.646 02001000 746441090 for disassembling of the CTL_SWITCH operation
2014-09-10 09:13:28.619 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:13:28.619 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:13:43.620 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:13:43.620 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:13:58.639 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:13:58.639 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:14:13.657 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:14:13.657 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:14:28.674 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:14:28.674 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:14:43.676 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:14:43.676 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:14:58.693 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:14:58.693 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:15:13.695 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:15:13.695 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:15:28.707 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:15:28.707 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:15:43.724 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:15:43.724 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:15:58.726 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:15:58.726 NSV1: smart_stb returned ORA-16665 Site.
2014-09-10 09:16:13.727 NSV1: using RFIUPI_DB_INST_CDESC
2014-09-10 09:16:13.727 NSV1: smart_stb returned ORA-16665 Site.
2014 09-10 02001000 746441090 MICHAEL 09:16:28.729: database smart_stb returned ORA-16665
2014-09-10 09:16:28.729 02001000 746441090 opcode = CTL_SWITCH, phase = DISASSEMBLY, req_id = 1.1.746441090
2014-09-10 09:16:28.729 02001000 746441090 CTL_SWITCH operation cancelled during phase 2, error = ORA-16665
2014 09-10 02001000 746441090 MICHAEL 09:16:28.729: ORA-16665 stateful failover operation failed
2014-09-10 09:16:28.729 NSV1: using RFIUPI_DGCI_CDESC
2014 09-10 02001000 746441090 MICHAEL 09:16:28.744: display primary instances for PASSAGE of phase 5
2014-09-10 09:16:28.744 INSV: message received for publication of inter - the instance
2014 09-10 02001000 746441090 MICHAEL 09:16:28.744: State of rfi_post_instances() for CTL_SWITCH = ORA-00000
2014-09-10 09:16:28.744 req ID 1.1.746441090, CTL_SWITCH opcode, phase END, 5 flags
2014 09-10 02001000 746441090 MICHAEL 09:16:28.744: passage to the aborted due to errors
2014 09-10 02001000 746441090 named Site 09:16:28.744: smart is always primary school
2014 09-10 02001000 746441090 error 09:16:28.744 = ORA-16665
DRC.log Eve shows the following:
2014-09-10 09:13:01.352 02001000 746441090 notify Oracle Clusterware base ensures target disassembly of passing data to the
2014-09-10 09:13:01.367 ACLS: not configured CRS, config = 2
.
2014 09-10 02001000 746441090 MICHAEL 09:13:01.367: display of bodies sleep for transition to THE phase 1
2014-09-10 09:13:01.367 INSV: message received for publication of inter - the instance
2014-09-10 09:13:01.367 req ID 1.1.746441090, CTL_SWITCH opcode, phase BEGIN, 5 flags
2014 09-10 02001000 746441090 MICHAEL 09:13:01.367: entered rfmsoexinst() for phase BEGIN
2014-09-10 09:13:01.367 INSV: response for message with
2014-09-10 09:13:01.367 req ID 1.1.746441090, CTL_SWITCH opcode, phase BEGIN
2014 09-10 02001000 746441090 MICHAEL 09:13:01.367: entered rfm_release_chief_lock() for CTL_SWITCH
2014 09-10 02001000 746441090 MICHAEL 09:13:06.571: entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
2014 09-10 02001000 746441090 MICHAEL 09:13:06.571: start execution of the task: the DIGITAL switchover
2014 09-10 02001000 746441090 MICHAEL 09:13:06.586: display of bodies sleep for transition to THE phase 2
2014-09-10 09:13:06.586 INSV: message received for publication of inter - the instance
2014-09-10 09:13:06.586 req ID 1.1.746441090, opcode CTL_SWITCH, disassembling, 5 flags
2014 09-10 02001000 746441090 MICHAEL 09:13:06.586: entered rfmsoexinst() for disassembling
2014-09-10 09:13:06.586 RSM0: received the State value ask: rid = 0 x 02031001, sid = 0, phid = 1, econd = 2, sitehndl = 0 x 02001000
2014-09-10 09:13:06.586 redo apply the resource: SetState OFFLINE, DISASSEMBLY phase, external Cond SWITCH-OVER-PHYS_STBY
2014-09-10 09:13:06.586 RSM0: received the State value ask: rid = 0 x 02012001, sid = 9, phid = 1, econd = 2, sitehndl = 0 x 02001000
2014-09-10 09:13:06.586 of database Resource [IAM = PHYSICS]: handle target SetState-READ-WRITE-XPTON Site, DISMANTLING phase, external SWITCH-OVER-PHYS_STBY, 0 x 02001000 Cond
2014-09-10 09:13:06.586 RSM0: execution of SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL]
2014-09-10 09:13:07.602 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL] executed successfully
2014-09-10 09:13:07.711 RSM0: execution of SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE through FINAL passage to THE NODELAY]
2014-09-10 09:13:09.509 SQL [ALTER DATABASE RECOVER MANAGED STANDBY DATABASE BY LAST crossing THE NODELAY] executed successfully
2014-09-10 09:13:09.509 RSM0: execution of SQL [ALTER DATABASE COMMIT to SWITCHING to the MAIN WAITING WITH the STOP of the SESSION]
2014-09-10 09:13:11.345 SQL [ALTER DATABASE COMMETTRE to TRANSITION to PRIMARY WAIT WITH SESSION SHUTDOWN] executed successfully
2014-09-10 09:13:11.345 of database Resource successful SetState
2014-09-10 09:13:11.345 INSV: response for message with
2014-09-10 09:13:11.345 req ID 1.1.746441090, CTL_SWITCH, disassembling opcode
2014 09-10 02001000 746441090 MICHAEL 09:13:11.345: entered rfm_release_chief_lock() for CTL_SWITCH
2014-09-10 09:13:28.555 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:13:43.555 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:13:58.571 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:14:13.590 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:14:28.605 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:14:43.606 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:14:58.622 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:15:13.625 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:15:28.641 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:15:43.646 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:15:58.652 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014-09-10 09:16:13.653 drcx: found the task req_id = 1.1.746441090, PROBE, but the phase is carried out
2014 09-10 02001000 746441090 MICHAEL 09:16:27.606: Data Guard Broker ending NSV0, timed out waiting for a response from the smart database
2014 09-10 02001000 746441090 MICHAEL 09:16:27.825: smart database returned ORA-16662
2014-09-10 09:16:27.825 02001000 746441090 opcode = CTL_SWITCH, phase = RESYNCHRONIZATION, req_id = 1.1.746441090
2014 09-10 02001000 746441090 MICHAEL 09:16:42.840: Data Guard Broker ending NSV0, timed out waiting for a response from the smart database
2014 09-10 02001000 746441090 MICHAEL 09:16:42.840: smart database returned ORA-16662
2014-09-10 09:16:42.840 02001000 746441090 opcode = CTL_SWITCH, phase = RESYNCHRONIZATION, req_id = 1.1.746441090
2014 09-10 02001000 746441090 MICHAEL 09:16:57.861: Data Guard Broker ending NSV0, timed out waiting for a response from the smart database
2014 09-10 02001000 746441090 MICHAEL 09:16:57.861: smart database returned ORA-16662
2014-09-10 09:16:57.861 02001000 746441090 opcode = CTL_SWITCH, phase = RESYNCHRONIZATION, req_id = 1.1.746441090
2014-09-10 09:16:58.705 746441091 00001000 MICHAEL: entered rfm_get_chief_lock() for HEALTH_CHECK, reason 0
2014-09-10 09:16:58.705 746441091 00001000 MICHAEL: task to free the 1.1.746441090 orphans, opcode = CTL_SWITCH.
2014-09-10 09:16:58.705 746441091 00001000 MICHAEL: start the task execution: automated healthcheck
2014-09-10 09:16:58.720 746441091 00001000 MICHAEL: start-up of the health check
2014-09-10 09:16:58.720 INSV: message received for publication of inter - the instance
2014-09-10 09:16:58.720 746441091 00001000 MICHAEL: rfi_post_instances() status = ORA-00000
2014-09-10 09:16:58.720 req ID 1.1.746441091, HEALTH_CHECK opcode, phase BEGIN, 5 flags
2014 09-10 00000000 746441091 MICHAEL 09:16:58.720: entered rfmhcexinst
2014 09-10 00000000 746441091 MICHAEL 09:16:58.720: rfmhcexinst call transfer
2014-09-10 09:16:58.720 RSM0: receipt get status request: rid = 0 x 02012001, sid = 4
2014-09-10 09:16:58.720 RSM0: HEALTH CHECK ERROR: ORA-16816: incorrect database role
2014-09-10 09:16:58.720 WARNING: given RCS 281474976710655 with resetlogs_id = 851952614 is less than resetlogs_change # 744657 of the incarnation.
2014-09-10 09:16:58.736 current IncarnationTable value is:
2014-09-10 09:16:58.736 2,744657,851952614,1, * 851351631, 1, 1, 0, #.
2014-09-10 09:16:58.736 RSM0: HEALTH CHECK ERROR: ORA-16700: the standby database has diverged from the primary database
2014-09-10 09:16:58.970 00000000 746441091 HEALTH_CHECK operation cancelled during phase 1, error = ORA-16810
2014-09-10 09:16:58.970 RSM0: receipt get status request: rid = 0 x 02031001, sid = 1
2014-09-10 09:16:58.970 00000000 746441091 MICHAEL: standby Instance completed the health check
2014-09-10 09:16:58.970 INSV: response for message with
2014-09-10 09:16:58.970 req ID 1.1.746441091, HEALTH_CHECK opcode, phase BEGIN
2014-09-10 09:16:58.970 MICHAEL: HEALTH CHECK ERROR: ORA-16766: redo apply is stopped
2014-09-10 09:16:58.970 MICHAEL: aggregation based on H/C, db 0 x 02001000 has gravity = 16501, status = 16810
2014-09-10 09:16:58.970 00000000 746441091 HEALTH_CHECK operation cancelled during phase 1, error = ORA-16810
2014-09-10 09:16:58.970 INSV: message received for publication of inter - the instance
2014-09-10 09:16:58.970 req ID 1.1.746441091, HEALTH_CHECK opcode, phase BEGIN, flags 20005
2014-09-10 09:16:58.970 MICHAEL: aggregation based on H/C, db 0 x 02001000 has gravity = 16501, status = 16810
2014-09-10 09:16:58.970 INSV: response for message with
2014-09-10 09:16:58.970 req ID 1.1.746441091, HEALTH_CHECK opcode, phase BEGIN
2014 09-10 00000000 746441091 MICHAEL 09:17:02.017: entered rfm_release_chief_lock() for HEALTH_CHECK
2014-09-10 09:17:13.724 drcx: task req_id is not found = 1.1.746441091 for PROBE.
2014-09-10 09:17:28.730 drcx: task req_id is not found = 1.1.746441091 for PROBE.
Primary alert.log indicates the following:
LNS: Standby redo log file selected for thread 1 sequence 12046 for destination LOG_ARCHIVE_DEST_2
My Nov 10 09:13:01, 2014
ALTER DATABASE COMMIT TO SWITCH STANDBY MODE PHYSICS WITH THE STOP OF THE SESSION
My Nov 10 09:13:01, 2014
Thread 1 Advanced to record the sequence 12047 (switch LGWR)
Currently Journal # 2 seq # 12047 mem # 0: X:\SMART\LOG1\SMART_21.LOG
Currently Journal # 2 seq # 12047 mem # 1: Y:\SMART\LOG2\SMART_22.LOG
Stop background QMNC process
My Nov 10 09:13:01, 2014
Arc1: Evaluating archive log 1 thread 1 sequence 12046
CLOSING: kill the server sessions.
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 15708 user ' ORACLE. EXE (W000)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
Program 'SYSTEM' of active processes 13372 user ' ORACLE. EXE (W001)"
CLOSED: all the closing of sessions successfully.
krss_find_arc: selection ARC2 to receive the message as a last resort
Waiting for all non-current archive ORLs...
Waiting for thread 1 sequence 12046 ORL to archive...
My Nov 10 09:13:02 2014
Arc0: Assessment of 1 thread 1 sequence 12046 log archives
My Nov 10 09:13:02 2014
ARC2: Evaluating archive log 1 thread 1 sequence 12046
Arc0: Unable to archive the thread 1 sequence 12046
Newspapers archived by another process
ARC2: Impossible to archive the thread 1 sequence 12046
Newspapers archived by another process
Involved the creation of the archivelog 'W:\SMART\ARC\SMART_12046_1_851952614.ARC '.
Archived journal 19372 extra for each sequence 1 12046 0xab72f94c dest ID thread entry 1:
ENT for thread 1 12046 sequence have been archived...
All non-current ORLs have been archived.
Waiting for all FAL entries to archive...
All FAL entries were archived.
Waiting for dest_id 2 can be synchronized...
OCISessionBegin with PasswordVerifier succeeded
Client pid [12320] annexed to the RFS pid [3648] number of the remote instance [1] to dest "smart_dg_stb."
Physical passage target Active, synchronized sleep has been identified
Transition to the end-of-Redo Log thread 1 sequence 12047 has been fixed
The digital switchover: primary YVERT seen above the value 0x0.0x22345d2
ARCH: Noswitch of archiving the thread 1, sequence 12047
ARCH: End-of-Redo archive thread 1 sequence 12047 branch
ARCH: Evaluating archive log 2 thread 1 sequence 12047
ARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Transmitting the activation 0xab72f94c ID
OCISessionBegin with PasswordVerifier succeeded
Client pid [12244] annexed to the RFS pid [9972] number of the remote instance [1] to dest "smart_dg_stb."
ARCH: Standby redo log file selected for thread 1 sequence 12047 for destination LOG_ARCHIVE_DEST_2
Involved the creation of the archivelog 'W:\SMART\ARC\SMART_12047_1_851952614.ARC '.
Archived journal 19373 extra for each sequence 1 12047 0xab72f94c dest ID thread entry 1:
Archived journal 19374 extra for each sequence 1 12047 0xab72f94c dest ID thread entry 2:
ARCH: Archiving is disabled due to the current archive log file
Primary will check some generator of target of receiving of alls again
Final inspection for a target standby synchronized. Verification will be made once.
ARCH: Transmitting the activation 0xab72f94c ID
LOG_ARCHIVE_DEST_2 is a potential target of the transition to physical standby
Active, synchronized target has been identified
Target has received also redo all the
-----------------------------------------------------------
| Target the waking state.
| LOG_ARCHIVE_DEST_1: NO ACTIVE |
| LOG_ARCHIVE_DEST_2: RECEIVED ALL DATA.
| LOG_ARCHIVE_DEST_3: NO ACTIVE |
| LOG_ARCHIVE_DEST_4: NO ACTIVE |
| LOG_ARCHIVE_DEST_5: NO ACTIVE |
| LOG_ARCHIVE_DEST_6: NO ACTIVE |
| LOG_ARCHIVE_DEST_7: NO ACTIVE |
| LOG_ARCHIVE_DEST_8: NO ACTIVE |
| LOG_ARCHIVE_DEST_9: NO ACTIVE |
| LOG_ARCHIVE_DEST_10: NO ACTIVE |
| LOG_ARCHIVE_DEST_11: NO ACTIVE |
| LOG_ARCHIVE_DEST_12: NO ACTIVE |
| LOG_ARCHIVE_DEST_13: NO ACTIVE |
| LOG_ARCHIVE_DEST_14: NO ACTIVE |
| LOG_ARCHIVE_DEST_15: NO ACTIVE |
| LOG_ARCHIVE_DEST_16: NO ACTIVE |
| LOG_ARCHIVE_DEST_17: NO ACTIVE |
| LOG_ARCHIVE_DEST_18: NO ACTIVE |
| LOG_ARCHIVE_DEST_19: NO ACTIVE |
| LOG_ARCHIVE_DEST_20: NO ACTIVE |
| LOG_ARCHIVE_DEST_21: NO ACTIVE |
| LOG_ARCHIVE_DEST_22: NO ACTIVE |
| LOG_ARCHIVE_DEST_23: NO ACTIVE |
| LOG_ARCHIVE_DEST_24: NO ACTIVE |
| LOG_ARCHIVE_DEST_25: NO ACTIVE |
| LOG_ARCHIVE_DEST_26: NO ACTIVE |
| LOG_ARCHIVE_DEST_27: NO ACTIVE |
| LOG_ARCHIVE_DEST_28: NO ACTIVE |
| LOG_ARCHIVE_DEST_29: NO ACTIVE |
| LOG_ARCHIVE_DEST_30: NO ACTIVE |
| LOG_ARCHIVE_DEST_31: NO ACTIVE |
------------------------------------------------------------
Backup controlfile written to find the D:\ORACLE\ORA_DBA\SMART\TRACE\diag\rdbms\smart\smart\trace\smart_rsm0_12244.trc file
Compensation pending activation ID 2876438860 (0xab72f94c)
The primary database controlfile is created using the
Clause 'MAXLOGFILES 255'.
There is space for the log files waiting for redo up to 251
Use the following SQL commands on the standby database to create
waiting for redo logfiles that correspond to the primary database:
ALTER DATABASE add STANDBY LOGFILE 'srl1.f' SIZE 52428800.
ALTER DATABASE add STANDBY LOGFILE 'srl2.f' SIZE 52428800.
ALTER DATABASE add STANDBY LOGFILE 'srl3.f' SIZE 52428800.
ALTER DATABASE add STANDBY LOGFILE 'srl4.f' SIZE 52428800.
ALTER DATABASE add STANDBY LOGFILE 'srl5.f' SIZE 52428800.
ARCHIVELOG for thread 1 sequence 12047 required for recovery of the eve
The digital switchover: converted primary Controlfile controlfile standby successfully.
The digital switchover: Complete - closing of the database required
Completed: ALTER DATABASE COMMIT to SWITCH STANDBY mode PHYSICS WITH the STOP of the SESSION
My Nov 10 09:13:20 2014
(Ospid 12320) process is suspended due to the transition to a physical relief operation.
My Nov 10 09:16:58 2014
(Ospid 12244) process is suspended due to the transition to a physical relief operation.
My Nov 10 09:17:08 2014
Process (ospid 3080) is suspended due to the transition to a physical relief operation.
My Nov 10 09:17:09 2014
Process (ospid 12636) is suspended due to the transition to a physical relief operation.
My Nov 10 09:17:10 2014
Process (ospid 5292) is suspended due to the transition to a physical relief operation.
My Nov 10 09:17:43 2014
RSM0, PID = 12244 process, will be killed
My Nov 10 09:17:44 2014
RSM0 started with pid = 27, OS id = 16280
My Nov 10 09:20:56 2014
minact-RCS: received the error during the scan e:12751 usn:6 useg
minact-SNA: useg scan slip on with error e:12751
My Oct 10 09:21:19 2014
Process (ospid 16280) is suspended due to the transition to a physical relief operation.
My Nov 10 09:22:04 2014
RSM0, PID = 16280 process, will be killed
My Nov 10 09:22:05 2014
RSM0 started with pid = 27, OS id = 10528
My Nov 10 09:25:39 2014
(Ospid 10528) process is suspended due to the transition to a physical relief operation.
My Nov 10 09:26:03 2014
minact-RCS: received the error during the scan e:12751 usn:6 useg
minact-SNA: useg scan slip on with error e:12751
My Nov 10 09:26:24 2014
RSM0, PID = 10528 process, will be killed
My Nov 10 09:26:25 2014
RSM0 started with pid = 27, OS id = 15752
My Nov 10 09:29:59 2014
Process (ospid 15752) is suspended due to the transition to a physical relief operation.
My Nov 10 09:30:44 2014
RSM0, PID = 15752 process, will be killed
My Nov 10 09:30:45 2014
RSM0 started with pid = 27, OS id = 1972
My Nov 10 09:31:09 2014
minact-RCS: received the error during the scan e:12751 usn:6 useg
minact-SNA: useg scan slip on with error e:12751
Suspend action 'Block Cleanout Optim, Undo Segment Scan' MMON 82800 seconds
My Nov 10 09:34:19 2014
Process (ospid, 1972) is suspended due to the transition to a physical relief operation.
alert-journal sleep shows the following:
My Nov 10 09:13:01, 2014
ARC3: Evaluating archive log 5 thread 1 sequence 12046
Involved the creation of the archivelog 'W:\SMART\ARC\SMART_12046_1_851952614.ARC '.
Archived journal 5932 extra for each sequence 1 12046 0xab72f94c dest ID thread entry 1:
My Nov 10 09:13:01, 2014
Media, recovery waiting for thread 1 sequence 12047
My Nov 10 09:13:04 2014
Again shipping customer logged in as PUBLIC
-User is valid
RFS [6]: assigned to the process 3648 RFS
RFS [6]: identified the type of database such as 'physical' standby: customer is ARCH pid 12320
My Nov 10 09:13:06 2014
Again shipping customer logged in as PUBLIC
-User is valid
RFS [7]: assigned to the process 9972 RFS
RFS [7]: identified the type of database such as 'physical' standby: Client is in the foreground pid 12244
RFS [7]: end-of-Redo for thread archiving 1 sequence 12047
RFS [7]: Eve successfully opened journal 5: "Y:\SMART\LOG2\SMART_S_5.LOG."
RFS [7]: Journal selected 5 for thread 1 sequence 12047 dbid-1425016497 branch of the 851952614
My Nov 10 09:13:06 2014
Arc1: Evaluating archive log 5 thread 1 sequence 12047
Involved the creation of the archivelog 'W:\SMART\ARC\SMART_12047_1_851952614.ARC '.
Archived journal 5933 extra for each sequence 1 12047 0xab72f94c dest ID thread entry 1:
My Nov 10 09:13:06 2014
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
MRP0: Background Media Recovery cancelled with status 16037
Errors in the D:\ORACLE\ORA_DBA\SMART\TRACE\diag\rdbms\smart_stb\smart\trace\smart_pr00_13804.trc file:
ORA-16037: user has requested the cancellation of the managed recovery
Managed Standby recovery not using real time applies
Recovery interrupted!
Errors in the D:\ORACLE\ORA_DBA\SMART\TRACE\diag\rdbms\smart_stb\smart\trace\smart_pr00_13804.trc file:
ORA-16037: user has requested the cancellation of the managed recovery
My Nov 10 09:13:07 2014
Errors in the D:\ORACLE\ORA_DBA\SMART\TRACE\diag\rdbms\smart_stb\smart\trace\smart_mrp0_11168.trc file:
ORA-10877: error reported in parallel recovery slave
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
Data not available for the digital switchover
End-of-REDO the archived log file was not found
Incomplete recovery SCN:0:35846057 archive SCN:0:35866066
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH FINAL PASSAGE TO THE NODELAY
has started the process of logmerger
My Nov 10 09:13:07 2014
Managed Standby recovery not using real time applies
Parallel Media Recovery started with 8 slaves
Media W:\SMART\ARC\SMART_12047_1_851952614.ARC recovery log
Identified the SNA 0x0.22345d2 end-of-Redo (failover) for thread 1 sequence 12047
Activation reset sleep ID 2876438860 (0xab72f94c)
Met Media Recovery end Redo indicator
Media recovery applied through change 35866066
Attempt to limbo arscn 0:35866066 irscn 0:35866066
Completed: ALTER DATABASE RECOVER MANAGED STANDBY database through FINAL passage to THE NODELAY
ALTER DATABASE COMMIT TO SWITCHING TO THE MAIN WAITING WITH THE STOP OF THE SESSION
Waiting for the transition from role maximum is 15 minutes.
krsv_proc_kill: kill 2 process (all the RFS)
Backup controlfile written to find the D:\ORACLE\ORA_DBA\SMART\TRACE\diag\rdbms\smart_stb\smart\trace\smart_rsm0_14652.trc file
Passage to the after complete recovery through change 35866066
X:\SMART\LOG1\SMART_11.LOG online journal: thread 1 Group 1 had been previously authorized
Y:\SMART\LOG2\SMART_12.LOG online journal: thread 1 Group 1 had been previously authorized
X:\SMART\LOG1\SMART_21.LOG online journal: thread 1 group 2 was previously disabled
Y:\SMART\LOG2\SMART_22.LOG online journal: thread 1 group 2 was previously disabled
X:\SMART\LOG1\SMART_31.LOG online journal: thread 1 Group 3 has been previously authorized
Y:\SMART\LOG2\SMART_32.LOG online journal: thread 1 Group 3 has been previously authorized
X:\SMART\LOG1\SMART_41.LOG online journal: thread 1 Group 4 has been previously authorized
Y:\SMART\LOG2\SMART_42.LOG online journal: thread 1 Group 4 has been previously authorized
Standby became primary YVERT: 35866064
The digital switchover: completed - mounted as primary database
Completed: ALTER DATABASE COMMIT to SWITCHING to the MAIN WAITING WITH the STOP of the SESSION
My Nov 10 09:13:45 2014
Arc0: become the "no SRL" ARCH
My Nov 10 09:13:46 2014
ARC3: become the "no SRL" ARCH
My Nov 10 09:13:46 2014
Arc1: become the "no SRL" ARCH
My Nov 10 09:16:58 2014
NSV0 started with pid = 26, OS id = 15900
My Oct 10 09:21:20 2014
MICHAEL: NSV0 network call timeout. Kill it now.
The Setup is as follows:
DGMGRL > see the configuration;
Configuration - dg_smart
Protection mode: MaxPerformance
Databases:
Smart - primary database
smart_stb - physical of the standby database
Fast-Start Failover: DISABLED
The configuration status:
SUCCESS
DGMGRL > see the detailed chip database
-Smart database
Role: PRIMARY
State of destination: TRANSPORT-WE
Occurrence (s):
Smart
Properties:
DGConnectIdentifier = "smart_dg_prim".
ObserverConnectIdentifier = "
LogXptMode = "ASYNC".
DelayMins = '0'
Binding = "optional."
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = "300"
NetTimeout = "30"
RedoCompression = "DISABLE."
LogShipping = 'ON '.
PreferredApplyInstance = "
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO '.
StandbyFileManagement = 'AUTO '.
ArchiveLagTarget = "300"
LogArchiveMaxProcesses = "4"
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = "
LogFileNameConvert = "X:\SMART\LOG1, X:\SMART\LOG1, Y:\SMART\LOG2, Y:\SMART\LOG2.
FastStartFailoverTarget = "
InconsistentProperties = "(monitor).
InconsistentLogXptProps = "(monitor).
SendQEntries = "(monitor).
LogXptStatus = "(monitor).
RecvQEntries = "(monitor).
Nom_sid = "smart."
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST=host02) (PORT = 1599)) (CONNECT_DATA = (SERVICE_NAME = smart_DGMGRL)(INSTANCE_NAME=smart) (SERVER = DEDICATED)))'
StandbyArchiveLocation = "W:\SMART\arc\".
AlternateLocation = "
LogArchiveTrace = '8191'
LogArchiveFormat = "smart_%s_%t_%r.arc".
TopWaitEvents = "(monitor).
State of the database:
SUCCESS
DGMGRL > see the detailed database smart_stb
Database - smart_stb
Role: STANDBY PHYSICS
State of destination: apply
Transport Lag: 0 seconds
Apply the Lag: 0 seconds
Real-time query: OFF
Occurrence (s):
Smart
Properties:
DGConnectIdentifier = "smart_dg_stb".
ObserverConnectIdentifier = "
LogXptMode = "ASYNC".
DelayMins = '0'
Binding = "optional."
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = "300"
NetTimeout = "30"
RedoCompression = "DISABLE."
LogShipping = 'ON '.
PreferredApplyInstance = "
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO '.
StandbyFileManagement = 'AUTO '.
ArchiveLagTarget = "300"
LogArchiveMaxProcesses = "4"
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = "
LogFileNameConvert = "X:\SMART\LOG1, X:\SMART\LOG1, Y:\SMART\LOG2, Y:\SMART\LOG2.
FastStartFailoverTarget = "
InconsistentProperties = "(monitor).
InconsistentLogXptProps = "(monitor).
SendQEntries = "(monitor).
LogXptStatus = "(monitor).
RecvQEntries = "(monitor).
Nom_sid = "smart."
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST=host01) (PORT = 1599)) (CONNECT_DATA = (SERVICE_NAME = smart_stb_DGMGRL)(INSTANCE_NAME=smart) (SERVER = DEDICATED)))'
StandbyArchiveLocation = "W:\SMART\arc\".
AlternateLocation = "
LogArchiveTrace = '8191'
LogArchiveFormat = "smart_%s_%t_%r.arc".
TopWaitEvents = "(monitor).
State of the database:
SUCCESS
tnsnames.ora:
smart_dg_stb = (Description = (Address = (Protocol = TCP)(Host=host01) (port = 1599)) (CONNECT_DATA = (Server = Dedicated) (SID = Smart)))
smart_dg_prim = (Description = (Address = (Protocol = TCP)(Host=host02) (port = 1599)) (CONNECT_DATA = (Server = Dedicated) (SID = Smart)))
Primary listner.ora:
LISTENER_REDO_SMART =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP (PORT = 1599))(HOST = host02))
)
)
SID_LIST_LISTENER_REDO_SMART =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\oracle\11.2.0)
(= Extproc PROGRAM)
(ENVS = "EXTPROC_DLLS=ONLY:D:\oracle\11.2.0\bin\oraclr11.dll")
)
(SID_DESC =
(SID_NAME = smart)
(ORACLE_HOME = D:\oracle\11.2.0)
)
(SID_DESC =
(SID_NAME = smart)
(GLOBAL_DBNAME = smart_DGMGRL)
(ORACLE_HOME = D:\oracle\11.2.0)
)
)
Listener.ora ensures
LISTENER_REDO_SMART =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP (PORT = 1599))(HOST = host01))
)
)
SID_LIST_LISTENER_REDO_SMART =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\oracle\11.2.0)
(= Extproc PROGRAM)
(ENVS = "EXTPROC_DLLS=ONLY:D:\oracle\11.2.0\bin\oraclr11.dll")
)
(SID_DESC =
(SID_NAME = smart)
(ORACLE_HOME = D:\oracle\11.2.0)
)
(SID_DESC =
(SID_NAME = smart)
(GLOBAL_DBNAME = smart_stb_DGMGRL)
(ORACLE_HOME = D:\oracle\11.2.0)
)
)
LSNRCTL > status listener_redo_smart
Connection to (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP (PORT = 1599))(HOST=host02)))
STATUS of the LISTENER
------------------------
Alias LISTENER_REDO_SMART
TNSLSNR for Windows 64-bit version: Version 11.2.0.3.0 - Production
Start date August 30, 2014 20:46:12
Uptime 10 days 13 h 11 min 15 sec
Draw level off
Security ON: OS Local Authentication
SNMP OFF
Listener parameter File D:\oracle\11.2.0\network\admin\listener.ora
Listener log file D:\oracle\diag\tnslsnr\host02\listener_redo_smart\alert\log.xml
Summary of endpoints listening...
(DESCRIPTION = (ADDRESS = (PROTOCOL = tcp (PORT = 1599))(HOST=host02)))
Summary of services...
Service 'CLRExtProc' has 1 instance (s).
Instance of 'CLRExtProc', status UNKNOWN, has 1 operation for this service...
Service 'HA_SMART' has 1 instance (s).
'Smart' instance, State LOAN, has 1 operation for this service...
'Smart' service has 2 occurrences.
'Smart' instance, status UNKNOWN, has 1 operation for this service...
'Smart' instance, State LOAN, has 1 operation for this service...
Service 'smart_DGB' has 1 instance (s).
'Smart' instance, State LOAN, has 1 operation for this service...
Service 'smart_DGMGRL' has 1 instance (s).
'Smart' instance, status UNKNOWN, has 1 operation for this service...
The command completed successfully
I would be most grateful if someone would have an idea of how solve it!
Thanks in advance and best regards...
Solved!
A logon trigger that makes an insert in a table for each log in the appearance of this behavior. Since dataguard brings the standby database open mode ReadOnly cannot insert the trigger and the strange behavior as described happens!
Hope that could help someone in the future...
Kind regards
-
DataGuard broker 11 GR 2 - StaticConnectIdentifier
OK, I read that in 11 GR 2 you do have more to put in a static in your listener.ora with < SID > _DGMGRL file entry if you use the Dataguard Broker: StaticConnectIdentifier. I used this new setting, and it was automatically created to be:
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=DB1) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = prod_sb_DGMGRL) (INSTANCE_NAME = prod_sb)(SERVER=DEDICATED)))'
My question is that there is no entry anywhere that specifies the SERVICE_NAME as prod_sb_DGMGRL. My passage to the work without SERVICE_NAME is not defined any where? Am I missing a step? Thank you people.Hello;
I think that the digital switchover will fail with an ORA-12514. Without the listener.ora entry DGMGRL won't be able to connect to the databases once that they were arrested.
You must therefore always the _DGMGRL or at least a static entry in the listener.ora. In any State to cause the static entry will not cause a problem.
* Passage failed with ORA-12521 using Dataguard broker [1380949.1 ID] *.
For more information, see - 8.3.40 StaticConnectIdentifier in "broker Data Guard 11 g Release 2 (11.2) E17023-04.
"A connect identifier that refers to a service that is registered statically.
Best regards
mseberg
Published by: mseberg on Sep 20, 2012 04:04
-
How to test the failover of dataguard environment?
I would like to test failover (no pass) in dataguard environment.
How to get there?
Thank you.Hello;
Happy to share my test notes:
http://www.Visi.com/~mseberg/Data_Guard_Failover_Test_using_SQL.PDF
These oracle notes can also help:
Can I use manual SQL * PLUS measures for (passage, failover, etc...), if DataGuard broker has already activated and GridControl is also used? [744396.1 ID]
Oracle10g: Passage to the custody of data and failover best practices [ID 387266.1]
Step by step guide on how to restore doesn't have a primary database standby physics [ID 738642.1]
Best regards
mseberg
Maybe you are looking for
-
Synth-> Mac Line in-> AppleTV?
So I have everything on the LAN to function as it should: Mac and AppleTV: Ethernet; iPhone and iPad: wifi. What I want to do, however, is the flow of my modular synth audio of live (mix-> Mac Line In table) for the AppleTV. Is it still possible?
-
Shockwave for Director 12.1.1.151 does not start, just with that. This application requires Xtra (text), which either do not exist or initialization failed, make sure that appropriate Xtras are in the Xtras folder. Reinstalled but made no difference.
-
After installation cannot find the printer driver on my mac
I downloaded hpprinterdriver3.1.dmg from the site web from apple and installed. Installation was successful. However I can't find the driver on my computer. Is there something wrong? Thank you Owen
-
Computer hangs, reboot, can only start in safe mode
Original title:-i can only start in safe mode Ive tried to use several restore points but when I try to reboot the computer freezes and I have to start in safe mode
-
I run MGADiag.exe but I still have the same problem. Thank you very much! Keith