Standby database upgrade process
Hi
I have a 11gR1 database with dataguard setup.I have successfully upgraded the primary database to 11gR2 using dbua.
Although 11gR2 software is installed on standby server,I realized archivelogs were not shipped to standby server during the database upgrade.
When I switch logfile in primary, I see below errors in standby alertlog:
RFS: 'Attach' request version mismatchWhat is the best way to sort out standby database regarding database upgrade ?
Do I need to manually add oratab entry, new pfile, etc in standby server ?
or
Do I have to rebuild DR ?
Both primary and standby compatible parameter is 11.1.0.0.0
However, rman is giving this error:
rman target sys/sys@orcl auxiliary sys/sys@orcl_std
Recovery Manager: Release 11.2.0.3.0 - Production on Sun Dec 11 08:53:34 2011
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1297219823)
Recovery Manager incompatible with AUXILIARY database: RMAN 8.0.4.0 to 11.1.0.7 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: AUXILIARY database is not compatible with this version of RMANLike I said, after the database upgrade pirmary became 11.2.0.3, standby is still 11.1
I upgraded primary with dbua.
Do I need to mount standby from new 11.2 home , copy pwd file, add oratab entry etc ?
These were done automatically on primary via dbua
Similar Messages
-
Standby database upgrade scenario
Hi all
I have to databases. One 10.1.3 and second 10.1.5
I created standby database for 10.1.3 database. And now want to create second standby database for my second 10.1.5 database...
How I must do it?
Can I convert (or how can I convert) my installed 10.1.3 standby database to preapre creating another 10.1.5 standby database?
Thanks...I have to say that's not very clear for me.
You have one 10.1.3 database with a standby.
You have one 10.1.5 database you want to build a standby on.
Right ?
So, why do you need to "convert" the 10.1.3 standby to 10.1.5 ?
Keep in mind, it's better having the standby database in same verion/release/patchset as the primary db.
Nicolas. -
Database upgrade process and step
Hi,
I am trying to do as following:
I have old server with 10.2.0.3 32 bits on Linux.
We are trying to have RH Linux 5.4 64 bits and oracle 10.2.0.3 64 bits.
How can i restore from 10.2.0.3 32 bits cold backup to new server?
Thanks
Pat
Edited by: user12020966 on Feb 4, 2010 10:49 AMPl see your other post - Re: step to upgrade 10.2.0.3 to on new server 10.2.0.4
Srini -
Error while trying to setup a standby database.
While tring to setup a standby database (with version 8.1.7.0.0) i am running the command:
recover managed standby database timeout 20;
Here is the errors i'm getting:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/data/syndicate/standby/system/dup75_system01.dbf'
ORA-16016: archived log for thread 1 sequence# 6518 unavailable
Although it says that file 1 was not restored from sufficiently old backup I've copied all the datafiles from the primary database at once - using a script.
The archived log sequence it asks for is non-existant - the last one i have is # 6517.
Thank you guys in advance for any ideas.
GregI am having the same problem as you are when I am applying the current logs after successfully mounting standby database as seen below:
SVRMGR> alter database mount standby database;
Statement processed.
SVRMGR> recover standby database ;
ORA-00279: change 2939586 generated at 07/28/2002 01:09:33 needed for thread 5718
ORA-00289: suggestion : C:\ORACLE\ORADATA\STANDBY\ARCHIVE\STANDBYT571S00362.ARC
ORA-00280: change 2939586 for thread 5718 is in sequence #362
Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\STANDBY\SYSTEM01.DBF'
SVRMGR>
Just before copying the datafiles from the primary database I did the following:
Connected to the primary database:
1. alter database create standby controlfile as .....
2. alter system switch logfile
3. shutdown normal
4. took a cold backup (including archived redo logs)
Copied the data files, redolog files, archived redo logs and standby controlfile to standby database:
1. made copies of standby controlfile over current standby ones.
2. startup nomount (the standby database)
3. alter database mount standby database;
4. recover standby database;
That's when it asks for an archived redo log that does'nt exist and when I enter cancel, that's when I get the above error?
Am I not applying the latest redo logs to the latest cold backup of the primary database?
Your help would be much appreciated! -
Upgrade PHYSICAL STANDBY database to 10g from 9i
Hello everybody,
Please can you provide me the details for Manual upgrading 9i STANDBY database to 10g. Any special parameters that we have to set on the Primary database..
Any sites with the information available would be great.
Thanks everybody for your help.There is no in-place upgrade process to move from 9i to 10g. You have to upgrade your primary and then reinstantiate your standby (using Oracle10g). You may like to keep your 9i standby in tact until your upgrade of 9i primary to 10g is completely successful.....just to ensure that you have a fast, easy and reliable fall-back plan.
Thanks
Chandra -
I'd like to upgrade my standby database form 8.0.6 to 9.2.
Is anyone having a manual or procedure to upgrade a standby database ?
Thank you.
EricI believe that the process is basically identical to the process outlined in the Migration Guide http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96530/toc.htm.
For a standby database, though, you have to ensure that you apply all the 8.0.6 log files first, then upgrade the primary, then update the standby, then start applying the 9.2 log files.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC -
Error in starting MRP process in Standby database.
Hi All,
OS:Windows server 03
DB:11g
I am creating a Standby database, everything is fine until i fire the below command to start the MRP process to start the recovery of the database.
alter database recover managed standby database disconnect from session;MRP0 started with pid=27, OS id=6640
2013-02-07 17:59:48.515000 +05:30
started logmerger process
Managed Standby Recovery not using Real Time Apply
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSAUX01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\APP\ORACLE\ORADATA\TEST\TEST\UNDOTBS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\APP\ORACLE\ORADATA\TEST\TEST\USERS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
MRP0: Background Media Recovery terminated with error 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_pr00_7984.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Recovery Slave PR00 previously exited with exception 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_mrp0_6640.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Completed: alter database recover managed standby database disconnect from session
Can anyone tell me why is this comming?
Regards,
SphinxHi ,
Yes, it is on the same server.
I have used the below mentioned parameters to rename the files
At Primary Pfile:
*.db_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\datafiles\')
*.log_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\redologs\')
At Standby:
*.db_file_name_convert=('D:\app\oracle\testdr\oradata\datafiles\','D:\app\oracle\oradata\test\test\')
*.log_file_name_convert=('D:\app\oracle\testdr\oradata\redologs\','D:\app\oracle\oradata\test\test\')
But the output of v$datafile at standby is showing the path of Primary datafiles
I manually tried recovering them but it is prompting me the same error.
Regards
Edited by: $phinx19 on Feb 7, 2013 6:23 AM -
Upgrading the primary and physical standby database
Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835Read this Metalink Note:407040.1
-
Upgrading with a physical standby database in place
Hi all
I am planning to upgrade my database which is 11.2.0.1 (Windows 32 platform) to 11.2.0.3. It has a primary standby database. I only have 1 server for testing the primary database, so I am looking for some help.
I was reading http://docs.oracle.com/cd/B28359_01/server.111/b28294/upgrades.htm#CHDBJAGG and I confuse about step 4 and 5
+4. Install the new release of the Oracle software into a new Oracle home on the physical standby database system, as described in the Oracle Database Upgrade Guide.+
+5. Mount the physical standby database.+
My question is in step 5, when I mount the physical standby database, does it mounted using new Oracle binary or still using the old version? From my understanding what is step 4 doing is to copying files to new home only. Changing the service to use the new oracle binary is done by dbua. I know this when I test upgrading the primary database.
Regards
Stanley.Hello;
new Oracle binary or the new Oracle home if you will.
So you install the new software on the standby only, all the upgrade SQL gets done on the Primary and then you ENABLE and startup mount on the new oracle home and the standby gets upgraded from the Primary redo.
Its pretty simple ( My exact plan )
1. Disable log shipping from the Primary
2. Shutdown Standby
3. Install 11.2.0.3 on Standby - Just the software
4. Startup Standby in recovery mode - do NOT run r any SQL at the standby
5. Shutdown Primary
6. Install 11.2.0.3 on Primary
7. Run Upgrade SQL or DBUA at Primary
8. Re-enable log shipping
9. Monitor the redo apply from Primary to Standby - this will also upgrade the Standby data dictionary
Make sure your tnsnames and listener files move to the new Oracle home and edit as needed.
Another oracle note is 278641.1
Best Regards
mseberg
Edited by: mseberg on Jan 29, 2013 8:21 PM -
Recovery process applies old archivelogs on standby database
Right now my standby database is in sync with my primary database and is waiting for the archived log sequeuence# 8378 to arrive.
But when I stop the recovery process (alter database recover managed standby database cancel;) and re-start it (alter database recover managed standby database disconnect), it starts all over again and starts applying archive logs starting from the sequence# 5739 (looks like its scanning thru the logs). To catchup with primary it takes 2+ hours as it need to skim thru all the logs starting from 5739 to 8377.
Please let me know if you need any further information to fix this.
Thank you
Sunny boy
Details:
Database version: 11.2.0.3
OS : RHEL 5
On Standby Database
SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
FROM V$LOG_HISTORY
GROUP BY THREAD#; 2 3
THREAD# LAST_APPLIED_LOG
1 8377
Alert log
alter database recover managed standby database disconnect
Attempt to start background Managed Standby Recovery process (MNODWDR)
Tue May 08 16:13:09 2012
MRP0 started with pid=28, OS id=26150
MRP0: Background Managed Standby Recovery process started (MNODWDR)
started logmerger process
Tue May 08 16:13:15 2012
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 8 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Completed: alter database recover managed standby database disconnect
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/arch/mnodw_1_5739_765032423.arc
Tue May 08 16:13:48 2012
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5740.1466.781015749
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5741.1468.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5742.1474.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5743.1473.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5744.1477.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5745.1478.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5746.1472.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5747.1475.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5748.1469.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5749.1470.781017203
Tue May 08 16:13:57 2012
Edited by: Sunny boy on May 8, 2012 5:29 PMHello;
V$LOG_HISTORY is the information from the control file. I would use a different query to check :
From the Primary :
SET PAGESIZE 140
COL DB_NAME FORMAT A10
COL HOSTNAME FORMAT A14
COL LOG_ARCHIVED FORMAT 999999
COL LOG_APPLIED FORMAT 999999
COL LOG_GAP FORMAT 9999
COL APPLIED_TIME FORMAT A14
SELECT
DB_NAME, HOSTNAME, LOG_ARCHIVED, LOG_APPLIED, APPLIED_TIME, LOG_ARCHIVED-LOG_APPLIED LOG_GAP
FROM
( SELECT
NAME DB_NAME
FROM
V$DATABASE
SELECT
UPPER(SUBSTR(HOST_NAME,1,(DECODE(INSTR(HOST_NAME,'.'),0,LENGTH(HOST_NAME), (INSTR(HOST_NAME,'.')-1))))) HOSTNAME
FROM
V$INSTANCE
SELECT
MAX(SEQUENCE#) LOG_ARCHIVED
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=1
AND
ARCHIVED='YES'
SELECT
MAX(SEQUENCE#) LOG_APPLIED
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=2
AND
APPLIED='YES'
SELECT
TO_CHAR(MAX(COMPLETION_TIME),'DD-MON/HH24:MI') APPLIED_TIME
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=2
AND
APPLIED='YES'
);Change DEST_ID as needed for your system. I would also bump the parameter LOG_ARCHIVE_MAX_PROCESSES assuming its set to default to a higher value up to 30.
Maybe instead of stopping the recovery process you should DEFER on the Primary
alter system set log_archive_dest_state_2=defer;Change the _n from 2 to what your system requires. I use this and have watch DG catch up 200 archives in about 15 minutes.
You have Standby Redo setup and are using the same size as your redo right?
Have never seen the Standby try to apply twice.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1] ( But I do not see your issue )
Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
Best Regards
mseberg
Edited by: mseberg on May 8, 2012 5:16 PM -
How to upgrade standby database
All,
how to upgrade standby DB if we are going to upgrade Primary DB from 9.2.0 to 10.2.0.4?
what will be the steps to upgrade stand by?Upgrading Oracle Database with a Physical Standby Database In Place
=> http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/upgrades.htm#sthref2051
Upgrading Oracle Database with a Logical Standby Database In Place
=> http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/upgrades.htm#sthref2056
Nicolas. -
Upgrading Installations that use Standby Databases
I have applied patch 6810189 and upgraded Oracle10g Database on my local machine, Now I am planing to apply it on test machine for that I need additional steps for upgrading Physical Standby database as said in README.html of p6810189_10204_Win32.zip
*7.1.2 Upgrading Installations that use Physical or Logical Standby Databases*
For information about physical standby databases, review document 278641.1.
Can anybody forward me this document or any suggestions for upgrading physical standby database..
THanks.thanks :)
but I am looking for complete steps, starting from applying patch to production then at standby database.... etc..etc -
Hello Expert !!
Once again I need you expert advice. We have a production database on 9.2.0.5, which we would like to upgrade to 10.2.0.3. A Physical Data Guard configuration is present for this database. The size of the database is more than 1 TB.
Upgrading Primary database is straight forward but how do I upgrade the standby database and continue the Data Guard configuration.
While upgrading the primary we would startup database with upgrade option and then startup-shutdown database couple of times. While upgrading standby how do I startup-shutdown it? (I mean normally we would normally mount the database and then open it as standby database and then place it in recovery mode).
Thanks for sharing your expertise !!!
RegardsPlease read it, rather than asking others to abstract it for free.
This is a forum where people exchange their experiences, if you are really looking to make money then please this is not the place you should be in.
If you are not capable enough or haven't performed yourself then its better to be quiet.
Metalink document (Note Id: 316889.1 Complete checklist for manual upgrades to 10gR2) discusses on upgrading from 9i to 10g but unfortunately doesn't mention a word about Standby Databases. So, I was looking for people who has actually performed the upgrade themselves and who could actually point to a URL which discusses more on this issue. I dont want you to walk-in and perform the upgrade for me.
Please, never ever take time to answer any of my questions. Remember my username "Oracle_Lover".
Thanks anyways.... -
Why process 'timestenrepd' on the standby database keep consuming 600% CPU?
Hi all, I have just created a empty active standby pair where there are 14 regular AWT cache groups.
After call of ttRepStart on the standby database, it takes 600% CPU(24 cores CPU) all the time.
There is no data in the cache groups and I found the error logs in the tterrors.log file:
14:01:28.32 Warn: : 27703: 27710/0xf83c50: Recovery started
14:01:31.62 Warn: : 27703: 27710/(nil): Another checkpoint is in progress. The final checkpoint will continue when the other checkpoint finishes.
14:01:44.96 Warn: REP: 25580: [139865850070784, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'FAILOVER' (context 0x7f2f580008c0) starting
14:01:44.97 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPLISTENER' (context 0x7f2f600008c0) starting
14:01:44.97 Warn: REP: 25580: [139865846920960, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'XLA_PARENT' (context 0x7f2f680008c0) starting
14:01:44.97 Warn: REP: 25580: [139865853220608, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPHOLD' (context 0x7f35040008c0) starting
14:01:45.04 Warn: REP: 25580: [139865840621312, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'LOGFORCE' (context 0x7f3500000c50) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f540008c0) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 0 got repSlave object 0x5406d9a0
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f500008c0) starting
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 0 got repSlave object 0x5006d9a0
14:01:45.05 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.12 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:45.13 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:45.13 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f400008c0) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 1 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f3c0008c0) starting
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 2 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:46.15 Err : REP: 25580: [139841666549504, 0, noAwt] EPPDB:meta.c(3134): TT16999: receiver slot alloc: 16289484001462337649 15530743840010091109
14:01:46.15 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:46.83 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:46.83 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f340008c0) starting
14:01:46.83 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:47.04 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600888.3 with prev as 0 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:47.05 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:47.43 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:47.43 Warn: REP: 25580: [139840591431424, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f200008c0) starting
14:01:47.43 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.46 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. select() timed out isAwt (false) parallelism (3) trackId (0) socket (17)
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (1) socket (19)
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Err : REP: 25580: [139841522874112, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (2) socket (23)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1870): TT16999: stopRcvrThreads (track 0) set to 0
14:01:48.66 Err : REP: 25580: [139840594581248, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Err : REP: 25580: [139841663399680, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:49.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:49.05 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:49.05 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:49.06 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context 0x7f2f00000000) starting
14:01:49.22 Warn: : 27703: 25580/0x7f2f3c0008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:01:50.17 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:53.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:53.54 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f440008c0) starting
14:01:53.54 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f200008c0) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 2 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.20 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f180008c0) starting
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 1 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f080008c0) starting
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #4 started
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef40008c0) starting
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #1 started
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2efc0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #3 started
14:01:54.21 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.21 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef80008c0) starting
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #0 started
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f040008c0) starting
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #5 started
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_SORTER' (context 0x7f2f0c0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:awt.c(144): TT16999: Parallel AWT Sorter started
14:01:54.21 Warn: REP: 25580: [139841399117568, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2eec0008c0) starting
14:01:54.22 Warn: REP: 25580: [139841392817920, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841395967744, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ef00008c0) starting
14:01:54.22 Warn: REP: 25580: [139841389668096, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f000008c0) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #2 started
14:01:55.87 Warn: REP: 25580: [139841663399680, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:56.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:56.55 Warn: REP: 25580: [139841182365440, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ed80008c0) starting
14:01:56.55 Warn: REP: 25580: [139841179215616, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600759.70 with prev as 63 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:57.26 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:57.27 Warn: REP: 25580: [139841176065792, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ecc0008c0) starting
14:01:57.27 Warn: REP: 25580: [139841172915968, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:57.90 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600759.71 with prev as 68 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600759.69 with prev as 64 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600888.1 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600888.0 with prev as 4294967295 hdr.firstCTN 1354600888.0expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
Please note that this is a newly active standby pair where there is no data or workload while the problem occurs, it makes me very depressed.Ok, Chirs, here are my steps to set up the active stnadby pair:
1.steps on the active database:
% ttIsql eppdb;
command> @init_user_grant.sql
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
command> call ttCacheUidPwdSet('cacheuser','oracle');
command> call ttGridCreate('myGrid');
command> call ttGridNameSet('myGrid');
command> call ttCacheStart;
command> @create_all_cache_groups.sql
command>
CREATE ACTIVE STANDBY PAIR eppdb ON "baal", eppdb ON "diablo"
RETURN TWOSAFE
STORE eppdb ON "baal" DISABLE RETURN ALL 5 RESUME RETURN 20
STORE eppdb ON "diablo" DISABLE RETURN ALL 5 RESUME RETURN 20;
command>call ttRepStart;
command>call ttRepStateSet('active');
command>@load_cache_groups.sql
command>exit
2.steps on the standby database:
% ttRepAdmin -duplicate -from eppdb -host "baal" -uid cacheuser -pwd timesten -cacheuid cacheuser -cachepwd oracle -keepCG eppdb
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
Command> CALL ttCacheUidPwdSet('cacheuser','oracle');
Command> CALL ttCacheStart;
Command> CALL ttRepStart;
After the replication agent is started on the standby database, issuing a 'top' command in the bash on the standby database server,
I can see the process 'timestenrepd' consumes 600%+ CPU all the time except for stopping the replication agent. -
Start recovery process on standby database after Windows reboot
Hi all,
I have a data guard configuration on Oracle 10.2.0.4 for Windows.
What I need is to mount and start recovery process automatically after Windows Server restart.
How can I do that ?
Thanks in advance.Here's what I found :
sleep 60
REM Start the database
%ORACLE_HOME%\bin\sqlplus -s "/ as sysdba" @startup.sql
exit
startupmount.sql -- Copy this under ORACLE_HOME/bin directory
-- start the database
startup mount
alter database recover managed standby database disconnect from session;
exitSorry, no way to test on my end.
The other thought is to hack oradim
But I'm thinking this might only do the startup mount.
Best Regards
mseberg
Edited by: mseberg on Feb 15, 2012 1:10 PM
This would need some work but it may help
@echo off
sc query "OracleOraDb11g_home1TNSListener" | findstr /i running
IF "%ERRORLEVEL%"=="0" (GOTO :RUNNING) ELSE (GOTO :STOPPED)
:STOPPED
ECHO NOT RUNNING
net start "OracleOraDb11g_home1TNSListener" | sc query "OracleServiceSCT" | findstr /i running | if NOT "%errorlevel%"=="0" net start oracleservicesct
GOTO :END
:RUNNING
ECHO RUNNING
net stop "OracleOraDb11g_home1TNSListener" | sc query "OracleServiceSCT" | findstr /i running | if "%errorlevel%"=="0" net stop oracleservicesct
GOTO :END
:ENDEdited by: mseberg on Feb 15, 2012 1:17 PM
Maybe you are looking for
-
ITunes 10 - Crashes when importing CD or from RIP'd file/folder
Windows Vista. There is no error, iTunes stops working and Microsoft Windows Message pops-up ITunes has stopped working A problems caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
-
TDS Certificate, Challan Payment Issue and BSR Code Issue
Hi All, I have configured Extended withholding tax as follows and encountered some issues 1. Specify Document Type (Accounts Payable): Here I have given Document type as SA and I am able to Pay the remittance challan through Post Vendor challan trans
-
Abstract Class Compiling Problem
This is my first time using the code tags, I apologize if I didn't do it right. I can't seem to get the subclass to compile properly. I have defined an abstract class TemplateLoginCommand that encapsulates all of the login functionality. I have defin
-
Hi, I have installed latest release of obiee on my linux server and trying to connect 11g database from it. But I am getting the following error: libclntsh.so.10.1: cannot open shared object file: No such file or directory [nQSError: 46029] Failed to
-
Hi, My dashboard page has 3 section the first section has yearly prompt,yearly report second section has monthly prompt ,monthly report third has daily prompt and report when i click on my dashboard only first section should be visible that is yearly