Logical Standby - Application Express Recovery
Ive asked a similar question in the following threads:-
Re: Recovering Logical Standby - Non-Guarded Schemas
Logical Standby - Application Express Recovery
Were using 10g Logical Standby database for our reporting environment and within it we have Oracle Application Express. i initially installed APEX into the logical after it was created. We then had to recover the primary RESETLOGS and reinstantiate the Logical - but since the APEX components were not-guarded by Data Guard they werent recreated after the reinstantiation. So it got me thinking.
Q1) Is it best to install Apex into the primary so the schema objects get recreated if we have to reinstantiate the Logical
Q2) If you do 1) this means you have to manually copy the files on the OS across - are there issues with this?
Does anyone else have this issue with an Apex installation?
Thanks for you help
Simon
you may want to try this one on the database general forum as well
Similar Messages
-
Best Way to setup a disaster Recovery site for a logical standby database
I have a logical standby DB (L1DB) as a reporting db on the same machine as the primary (P1DB). We are planning on building a disaster recovery site with similar hardware and potentially have disk mirroring of atleast the redo log files.
The DR site can hold an additional physical standby (S1DB) for the primary (P1DB). I am trying to understand what would be the best way to setup the Disaster Recovery site for the L1DB logical stdby. Ideally, when the disaster happens, and I no longer have P1DB and L1DB, I should be able to switch to S1DB as the new primary. But how do I setup to have a L2DB that takes the place of L1DB and has its contents and can be setup as a logical standby of S1DB?If you already setup one logical standby, then you know how it works, so not sure what question you are asking ?
Personally I would setup L2DB as a standby of the original primary P1DB. Having downstream standby databases complicates things, and adds additional lag between primary transaction time and L2DB apply. -
Recovery Logical Standby with RMAN
Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data GuardYou might get better responses in the DataGuard forum ("space").
I am sceptical if this plan would work.
Hemant K Chitale -
Logical standby: ORA-01031: insufficient privileges
Dear Colleagues,
Today in my Logical Standby don't apply archivelogs and I see an error in alert.log:
ORA-26808: Apply process AS01 died unexpectedly.
ORA-01031: insufficient privileges
Also I see next logs in trace files:
h4.
1)
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
ORACLE_HOME = /ora/Ora11203
System name: Linux
Node name: base
Release: 2.6.18-308.20.1.el5
Version: #1 SMP Tue Nov 6 04:38:29 EST 2012
Machine: x86_64
Instance name: oracle
Redo thread mounted by this instance: 1
Oracle process number: 43
Unix process pid: 16634, image: oracle@base (AS01)
*** 2013-04-04 16:58:47.062
*** SESSION ID:(146.16811) 2013-04-04 16:58:47.062
*** CLIENT ID:() 2013-04-04 16:58:47.062
*** SERVICE NAME:(SYS$USERS) 2013-04-04 16:58:47.062
*** MODULE NAME:(Streams) 2013-04-04 16:58:47.062
*** ACTION NAME:( - Apply Server) 2013-04-04 16:58:47.062
knasplcr: eager error was not rolled back
++ LCR Dump Begin: 0x2b0cf2a6d168 - ddl
op: 5, Original op: 5, baseobjn: 0, objn: 0, objv: 0
DF: 0x00000002, DF2: 0x00000010, MF: 0x00020810, MF2: 0x00000000
PF: 0x00000000, PF2: 0x08000000
MergeFlag: 0x00, FilterFlag: 0x00
Id: 0, iotPrimaryKeyCount: 0, numChgRec: 1
NumCrSpilled: 0
RedoThread#: 1, rba: 0x0213d7.00023455.01ac
scn: 0x0002.fc0f8769, (scn: 0x0000.00000000, scn_sqn: 0, lcr_sqn: 0)xid: 0x0019.00e.0007f8d9, parentxid: 0x0019.00e.0007f8d9, proxyxid: 0x0000.000.00000000
ncol: 0 newcount: 24, oldcount: 0
LUBA: 0x4.1000ad1.e.0.0
++ LCR Dump Begin: 0x59b1afdc8 - commit
op: 7, Original op: 7, baseobjn: 0, objn: 0, objv: 0
DF: 0x00000002, DF2: 0x00000010, MF: 0x00220000, MF2: 0x02000000
PF: 0x00100000, PF2: 0x08040000
MergeFlag: 0x03, FilterFlag: 0x00
Id: 3, iotPrimaryKeyCount: 0, numChgRec: 0
NumCrSpilled: 0
RedoThread#: 1, rba: 0x0213d7.00023456.0108
scn: 0x0002.fc0f876b, (scn: 0x0002.fc0f876b, scn_sqn: 1, lcr_sqn: 1)xid: 0x0019.00e.0007f8d9, parentxid: 0x0019.00e.0007f8d9, proxyxid: 0x0000.000.00000000
ncol: 0 newcount: 0, oldcount: 0
LUBA: 0x4.1000ad1.e.0.0
Apply Slave is exiting due to error ORA-1031KSV 1031 error in slave process
*** 2013-04-04 16:58:47.067
ORA-01031: insufficient privileges
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01031: insufficient privileges
h4.
2)
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
ORACLE_HOME = /ora/Ora11203
System name: Linux
Node name: base
Release: 2.6.18-308.20.1.el5
Version: #1 SMP Tue Nov 6 04:38:29 EST 2012
Machine: x86_64
Instance name: oracle
Redo thread mounted by this instance: 1
Oracle process number: 30
Unix process pid: 16404, image: oracle@base (LSP0)
*** 2013-04-04 16:41:58.401
*** SESSION ID:(294.35251) 2013-04-04 16:41:58.401
*** CLIENT ID:() 2013-04-04 16:41:58.401
*** SERVICE NAME:(SYS$BACKGROUND) 2013-04-04 16:41:58.401
*** MODULE NAME:() 2013-04-04 16:41:58.401
*** ACTION NAME:() 2013-04-04 16:41:58.401
knahcapplymain: encountered error=26808
*** 2013-04-04 16:41:58.401
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
----- Error Stack Dump -----
ORA-26808: Apply process AS02 died unexpectedly.
ORA-01031: insufficient privileges
KNACDMP: *******************************************************
KNACDMP: Dumping apply coordinator's context at 25487cb0
KNACDMP: Apply Engine # 0
KNACDMP: Apply Engine name
KNACDMP: Coordinator's Watermarks ------------------------------
KNACDMP: Apply High Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Apply Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Recovery Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Fetch Low Watermark = 0002fc0f876b (SCN=0x0002.fc0f876b)
KNACDMP: Fetch Low Watermark Time = 811857327
KNACDMP: Oldest SCN = (SCN=0x0000.00000000)
KNACDMP: Oldest XID =
KNACDMP: Oldest Create Time = 0
KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000
KNACDMP: Last syncpoint at primary SCN = 0x0002.fc0f875f
KNACDMP: First partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
KNACDMP: Last partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
KNACDMP: Last processed = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Conservative pos = 0002fc0f8cb2 (SCN=0x0002.fc0f8cb2)
KNACDMP: Recovery start pos = (SCN=0x0000.00000000)
KNACDMP: Recovery high watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Spill LWM = (SCN=0x0000.00000000)
KNACDMP: Spill LWM Create Time = 0
KNACDMP: Coordinator's constants -------------------------------
KNACDMP: number of apply slaves = 5
KNACDMP: min number of apply slaves = 5
KNACDMP: max number of apply slaves = 5
KNACDMP: safety level (K) = 1
KNACDMP: max txns in memory = 400
KNACDMP: max constraints per table = 620
KNACDMP: hash table size (in entries) = 10000000
KNACDMP: Coordinator's intervals -------------------------------
KNACDMP: syncpoint interval (ms) = 0
KNACDMP: write low watermark interval(ms)= 1
KNACDMP: Coordinator's timers/counters -------------------------
KNACDMP: current time = 1365082918
KNACDMP: low watermark timer = 0
KNACDMP: syncpoint timer = 1365082918
KNACDMP: txnbufsize timer = 1365082220
KNACDMP: Coordinator's txn counts -------------------------
KNACDMP: total txns applied = 0
KNACDMP: number of unassigned comp txns = 0
KNACDMP: number of unassigned incomp txns= 0
KNACDMP: avg number of unassigned txns = 0.00
KNACDMP: total applied at last plwm write= 0
KNACDMP: apply prog. entries below plwm = 0
KNACDMP: total unassigned lcrs = 0
KNACDMP: Coordinator's State/Flags -----------------------------
KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_END
KNACDMP: Coordinator's Flags = 0x408004
KNACDMP: Slave counts ------------------------------------------
KNACDMP: number of reserved slaves = 0
KNACDMP: number of admin slaves = 0
KNACDMP: number of slaves in wait cmt = 1
KNACDMP: number of slaves suspended = 0
KNACDMP: number of safe slaves = 1
KNACDMP: avg number of idle slaves = 0.00
KNACDMP: number of slaves initializing = 0
KNACDMP: number of slaves terminating = 0
KNACDMP: Slave Lists -------------------------------------------
KNACDMP: Dumping All Slaves :-
Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 1, State = 9, Flags = 2, Assigned Xid = 0x001e.006.0005d213 1 txns 0 lcrs
Slave id = 2, State = 5, Flags = 1, Assigned Xid = 0x0019.00e.0007f8d9 1 txns 0 lcrs
Slave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
KNACDMP: End dumping all slaves
KNACDMP: syncdep slaves = { }
KNACDMP: cont chunk slaves = { }
KNACDMP: cont slaves = { }
KNACDMP: exec txn slaves = { }
KNACDMP: Active slaves (2) = { 1 2 }
KNACDMP: Idle slaves (3) = { 3 4 5 }
KNACDMP: Txn Lists ---------------------------------------------
KNACDMP: Dumping all txns :-
XID = 0x001e.006.0005d213 Commit pos = 0002fc06718c (SCN=0x0002.fc06718c) State = 0
Lcr cnt = 0
Assigned to slavid = 1
Fetched chunks = 142
depslaves = { } wm depslaves = { }
XID = 0x0019.00e.0007f8d9 Commit pos = 0002fc0f876b (SCN=0x0002.fc0f876b) State = 1
Lcr cnt = 0
Assigned to slavid = 2
Fetched chunks = 1
depslaves = { } wm depslaves = { }
KNACDMP: End dumping all txns.
KNACDMP: Complete txns = { 0x0019.00e.0007f8d9 ** NO UNASS ** }
KNACDMP: Unassigned txns = { }
KNACDMP: *******************************************************
Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.
knahcapplymain: encountered error=26808
*** 2013-04-04 16:58:47.073
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
----- Error Stack Dump -----
ORA-26808: Apply process AS01 died unexpectedly.
ORA-01031: insufficient privileges
KNACDMP: *******************************************************
KNACDMP: Dumping apply coordinator's context at 25487cb0
KNACDMP: Apply Engine # 0
KNACDMP: Apply Engine name
KNACDMP: Coordinator's Watermarks ------------------------------
KNACDMP: Apply High Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Apply Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Recovery Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Fetch Low Watermark = 0002fc0f876b (SCN=0x0002.fc0f876b)
KNACDMP: Fetch Low Watermark Time = 811857327
KNACDMP: Oldest SCN = (SCN=0x0000.00000000)
KNACDMP: Oldest XID =
KNACDMP: Oldest Create Time = 0
KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000
KNACDMP: Last syncpoint at primary SCN = 0x0002.fc0f875f
KNACDMP: First partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
KNACDMP: Last partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
KNACDMP: Last processed = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Conservative pos = 0002fc0f8cb2 (SCN=0x0002.fc0f8cb2)
KNACDMP: Recovery start pos = (SCN=0x0000.00000000)
KNACDMP: Recovery high watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
KNACDMP: Spill LWM = (SCN=0x0000.00000000)
KNACDMP: Spill LWM Create Time = 0
KNACDMP: Coordinator's constants -------------------------------
KNACDMP: number of apply slaves = 5
KNACDMP: min number of apply slaves = 5
KNACDMP: max number of apply slaves = 5
KNACDMP: safety level (K) = 1
KNACDMP: max txns in memory = 400
KNACDMP: max constraints per table = 620
KNACDMP: hash table size (in entries) = 10000000
KNACDMP: Coordinator's intervals -------------------------------
KNACDMP: syncpoint interval (ms) = 0
KNACDMP: write low watermark interval(ms)= 1
KNACDMP: Coordinator's timers/counters -------------------------
KNACDMP: current time = 1365083926
KNACDMP: low watermark timer = 0
KNACDMP: syncpoint timer = 1365083926
KNACDMP: txnbufsize timer = 1365083218
KNACDMP: Coordinator's txn counts -------------------------
KNACDMP: total txns applied = 0
KNACDMP: number of unassigned comp txns = 0
KNACDMP: number of unassigned incomp txns= 1
KNACDMP: avg number of unassigned txns = 0.00
KNACDMP: total applied at last plwm write= 0
KNACDMP: apply prog. entries below plwm = 0
KNACDMP: total unassigned lcrs = 0
KNACDMP: Coordinator's State/Flags -----------------------------
KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_END
KNACDMP: Coordinator's Flags = 0x8204
KNACDMP: Slave counts ------------------------------------------
KNACDMP: number of reserved slaves = 0
KNACDMP: number of admin slaves = 0
KNACDMP: number of slaves in wait cmt = 0
KNACDMP: number of slaves suspended = 0
KNACDMP: number of safe slaves = 1
KNACDMP: avg number of idle slaves = 0.00
KNACDMP: number of slaves initializing = 0
KNACDMP: number of slaves terminating = 0
KNACDMP: Slave Lists -------------------------------------------
KNACDMP: Dumping All Slaves :-
Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 1, State = 5, Flags = 1, Assigned Xid = 0x0019.00e.0007f8d9 1 txns 0 lcrs
Slave id = 2, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
Slave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
KNACDMP: End dumping all slaves
KNACDMP: syncdep slaves = { }
KNACDMP: cont chunk slaves = { }
KNACDMP: cont slaves = { }
KNACDMP: exec txn slaves = { }
KNACDMP: Active slaves (1) = { 1 }
KNACDMP: Idle slaves (4) = { 2 3 4 5 }
KNACDMP: Txn Lists ---------------------------------------------
KNACDMP: Dumping all txns :-
XID = 0x001e.006.0005d213 Commit pos = 0002fc06718c (SCN=0x0002.fc06718c) State = 0
Lcr cnt = 0
Not Assigned
Fetched chunks = 142
depslaves = { } wm depslaves = { }
XID = 0x0019.00e.0007f8d9 Commit pos = 0002fc0f876b (SCN=0x0002.fc0f876b) State = 1
Lcr cnt = 0
Assigned to slavid = 1
Fetched chunks = 1
depslaves = { } wm depslaves = { }
KNACDMP: End dumping all txns.
KNACDMP: Complete txns = { 0x0019.00e.0007f8d9 ** NO UNASS ** }
KNACDMP: Unassigned txns = { 0x001e.006.0005d213 }
KNACDMP: *******************************************************
*** 2013-04-04 16:58:47.513
Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.
I watched this link http://docs.oracle.com/cd/E11882_01/server.112/e17069/strms_trapply.htm#i1014714 and I checked grants of schemas owners. These grants identical as on Primary DB Server.
I don't know what I need to do. It's very critical Server. Please help me.So, my problem is solved very easy.
Logical Standby didn't work because I added grant SYSDBA to temporary user and revoked this grant at once and I didn't change orapwSID file on Logical Standby from Primary.
http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#SBYDB00424Note:
Whenever you grant or revoke the SYSDBA or SYSOPER privileges or change the login password of a user who has these privileges, you must replace the password file at each physical or snapshot standby database in the configuration with a fresh copy of the password file from the primary database.
>
So, I deleted temporary user on Logical Standby and it solved the problem.
Thanks a lot to all who helped me! -
NEED HELP!!!! Logical Standby and RMAN.
Hello,
I have a Data Guard env setup on win 2000 with 9.2.0.4.
I now have primary and standby. I was wondering if I create a logical standby to achieve transparent application failover. What I am saying is if the primary node dies, then in tnsnames I want to point to the logical standby, since it is an open database, the users can still perform without knowing the db went down. Then if we indeed need a failover we can failover to the physical standby. This would ensure availability without having to implement RAC or AQ, Right? Also, I read that you should create rman schema (recovery catalog) on standby db. Any thoughts?Were you able to figure this one out?
I have a similar configuration as you - the same motherboard and an eVga Geforce 3 6600 fanless. With the latest BIOS (3.8) and this video card, the system will not go into Standby completely. I hear the HDD head park and the video goes black, but the LEDs on the front of the PC chassis and the case/PS fans do not stop. Pressing the button to bring the PC out of Standby, rather, whatever state it is in, works. -
Physical Standby database Vs. Logical Standby database
I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin -
Logical Standby on Standard Edition
Hey,
I have to setup an enviroment with 10gR2 on Linux.
I can only use standard edition.
I will have a manual physical standby in place.
Now I get a new requirement: I need to have an additional db for read only access.
Now logical standby is not possible with standard edition.
I found shareplex for oracle (quest) - would that be an alternative ?
Do you have other ideas how to realize an standby database which can be read by an application -- the database should be sync with the primary as possible
thxIt is possible to setup a schedule for your standby database to switch between READ ONLY mode and recovery mode.
For example, from 8am till 12pm, you can have your physical standby database be in read only mode, so that users can run reports. The standby database will not be updated during this time.
From 12pm till 2pm, the standby is switched to normal recovery mode and all the latest changes are applied.
At 2pm the standby is switched back into read only mode for reporting purposes.
At 6pm the standby database is put back into recovery mode until 8am the next morning to ensure the standby database is fully up to date for the next reporting day.
For this to work well, and to make sure you are also covered for DR at all times, it is important that your primary database keeps sending the archive redo logs to the standby server.
The archive redo logs are then queued up and ready to be applied on the standby server. So if you do suffer a major outage and have to activate the standby database, all the archive logs are available on the standby server.
This is how http://www.dbvisit.com works to enable physical standby for Standard Edition (SE).
Regards,
Edited by: Arjen Visser on 07-Sep-2010 09:08
Edited by: Arjen Visser on 07-Sep-2010 09:20 -
Logical Standby Database in NOARCHIVE Mode
Hi,
I have configured a Logical Standby Database for Reporting purposes. A Physical Standby Database is running for MAA. i.e. in case of Role Transition (switch/Failover) the Physical Stdby Db will get the role of the Primary.
The logical standby database is creating a lot of Archive Redologs files, nearly every minute. Redolog files are 50MB and there is no work done in db during the time. I'm NOT using Standby Redolog files.
Is there a need for logical standby database to be in NOARCHIVELOG mode? The Primary is definatley in ARCHIVELOG mode.
Thanks for any responses.
regards
Sahbahi,
well there are two things to the above:-
1. there was an archive file nearly every minute:
this is due to a db recovery. for some reason, the db was in inconsistent state, after a sudden shutdownof the OS. I was on a test environment, on windows vista, unfortunately. unimportant ... a reboot solved it.
2. Logical standby db in NOARCHIVE MODE when setup for the purpose of Reporting.
As long as the MAA configured for the primary db, such as physical standby db, and a second, the logical standby db setup purely for the purpose of reporting, which then can run with NOARCHIVELOG mode, after converting the physical standby db to logical.
logical standby db uses Streams architecture, so this method brings cost, time and performance advantages to the customer.
regards
Sahba -
How to delete the foreign archivelogs in a Logical Standby database
How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923 -
Hi,
When we say "Logical Standby Databases are logically identical to primary databases although the physical organization and structure of the data can be different." what does it exactly means?
Does it mean that in logical standby tablespace name, schema name, table name, column names etc can be different and still has the same data as primary?
Does it mean that we can exclude indexes and constraints as present in primary?
Only the data should match with primary word by word, value by value?
I am asking this as i have never worked in a logical standby database but i seriously want to know.
Please answer.
Regards,
SIDPhysical standby differs from logical standby:
Physical standby schema matches exactly the source database.
Archived redo logs and FTP'ed directly to the standby database which is always running in "recover" mode. Upon arrival, the archived redo logs are applied directly to the standby database.
Logical standby is different from physical standby:
Logical standby database does not have to match the schema structure of the source database.
Logical standby uses LogMiner techniques to transform the archived redo logs into native DML statements (insert, update, delete). This DML is transported and applied to the standby database.
Logical standby tables can be open for SQL queries (read only), and all other standby tables can be open for updates.
Logical standby database can have additional materialized views and indexes added for faster performance.
Installing Physical standbys offers these benefits:
An identical physical copy of the primary database
Disaster recovery and high availability
High Data protection
Reduction in primary database workload
Performance Faster
Installing Logical standbys offer:
Simultaneous use for reporting, summations and queries
Efficient use of standby hardware resources
Reduction in primary database workload
Some limitations on the use of certain datatypes -
Logical Standby....
Hi, I have Created Logical Standby data base on my windows 2003 Advance Server Machine and Oracle 10.2.0.3.
now I am having some problem that my LOGSTDBY is not in sync with the Primary DB from few days and in alertlog it is showing this error....
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, builder process P001 started with pid=18 OS id=2820
LOGMINER: session# = 1, reader process P000 started with pid=17 OS id=2816
LOGSTDBY Analyzer process P003 started with pid=20 OS id=2828
LOGSTDBY Apply process P005 started with pid=39 OS id=2984
LOGSTDBY Apply process P006 started with pid=40 OS id=2988
Fri Aug 21 11:56:17 2009
LOGMINER: Begin mining logfile: G:\ORACLE\ORADATA\SOS\ARCHIVE\SOST001S63660.ARC
Fri Aug 21 11:56:17 2009
LOGMINER: Turning ON Log Auto Delete
LOGSTDBY Apply process P004 started with pid=22 OS id=2980
LOGSTDBY Apply process P008 started with pid=42 OS id=2996
LOGMINER: session# = 1, preparer process P002 started with pid=19 OS id=2824
LOGSTDBY Apply process P007 started with pid=41 OS id=2992
Fri Aug 21 11:56:26 2009
Errors in file d:\oracle\admin\sos\bdump\logstdby_p004_2980.trc:
ORA-00604: error occurred at recursive SQL level 2
ORA-00955: name is already used by an existing object
Fri Aug 21 11:56:26 2009
LOGSTDBY status: ORA-00955: name is already used by an existing object
LOGSTDBY Apply process P004 pid=22 OS id=2980 stopped
Fri Aug 21 11:56:29 2009
Errors in file d:\oracle\admin\sos\bdump\logstdby_lsp0_2944.trc:
ORA-12801: error signaled in parallel query server P004
ORA-00955: name is already used by an existing object
LOGSTDBY Apply process P006 pid=40 OS id=2988 stopped
LOGSTDBY Analyzer process P003 pid=20 OS id=2828 stopped
LOGSTDBY Apply process P005 pid=39 OS id=2984 stopped
LOGSTDBY Apply process P007 pid=41 OS id=2992 stopped
LOGSTDBY Apply process P008 pid=42 OS id=2996 stopped
Fri Aug 21 11:58:50 2009
Redo Shipping Client Connected as PUBLIC
Plz rply ASAPHere are the steps to identify the object in question:
1) Start the replication on logical standby
2) Once the replication starts it will show you the same error in the alert log file as you mentioned above.
3) Query DBA_LOGSTDBY_EVENTS order by EVENT_TIMESTAMP. The last event will capture the name of the object that is creating the problem.
4) Based on your knowledge of database /application objects, you can skip that table using DBMS_LOGSTADBY.SKIP and start the replication again without any issue.
5) If you dont need that object in the logical DB to be replicated then let it be skipped, otherwise reinstate the object again in logical standby.
Amar. -
I am evaluating Logical standby for an application, but I need to confirm if there is a prerequisite that both source and target databases need to be on the same os platform. My source server is HP UX 11.11 and Target server is HP Itanium ia64 11.31. Can I setup Logical standby between these 2 platforms?
Read the Note:413484.1 Data Guard Support for Heterogeneous Primary and Standby Systems in Same Data Guard Configuration.
Examples of different platform combinations supported within a Data Guard configuration include:*
Different combinations of operating system word size (e.g. 32bit and 64bit)**
HP-UX PA-RISC and HP-UX Itanium
Beginning with Data Guard 11g, a mixture of Linux and Windows operating systems as noted in the table below.
Platform combinations not listed in the table below are not supported.
Platform_ID | Platform Name | PLATFORM_IDs supported within the same Data Guard configuration
3 | HP-UX (64-bit) & HP-UX PA-RISC | 3 & 4 (see MetaLink Notes 395982.1 and 414043.1)
4 | HP-UX IA (64-bit) & HP-UX Itanium | 4 & 3 (see MetaLink Notes 395982.1 and 414043.1)
NOTE:395982.1 Data Guard Support for Mixed HP PA-RISC 64-bit and HP Itanium Environments
NOTE:414043.1 Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries
HTH
Enrique -
Logical Standby working issues Oracle 9i, Windows
Hi,
Set up Oracle 9i Logical Standby on Windows. (instructions as per Oracle Documentation)
Did not have any issues setting up.
While setting up the Logical Standby, Recovered the Primary Database until Oct 10/09 8:16 pm
Registered the archive log in the logical standby generated hence and the FAL took care of copying/registering the rest of the archivelogs.
Created and inserted some records in Primary database and could see them in Standby.
So far so good.
On Oct11 data was entered into Primary database. Archivelogs were shipped to Standby, I could see them registered in DBA_LOGSTDBY_LOG.
The APPLIED_SCN,NEWEST_SCN were in sync as per DBA_LOGSTDBY_PROGRESS.
Today, we had some issues with data and when we queried the user tables: (no skip settings)
Couldn't see any data in standby past the recovery...
No errors reported in DBA_LOGSTDBY_EVENTS. No errors in Alert log also.
What could be happening?
Thanks,
MadhuriI figured it out...
Today, we had some issues with data and when we queried the user tables: (no skip settings)
Couldn't see any data in standby past the recovery...I was using two tables as random spot check and both did not get updated. So, I was under the impression SQL APPLY did not do anything.
But, it did apply the redo on the rest of the tables.
These 2 tables in question were skipped because both of them had Function Based indexes.
They are very huge individual tables .
So, exporting them from Primary database and Importing them into Standby Database. Skipping DML in DataGuard.
That solved the problem.
--Madhuri -
Logical Standby SQL Apply Using Incorrect Decode Statement
We are seeing statements erroring out on our logical standby that have been rewritten (presumably by sql apply) with decode statements that don't appear to be correct. For example, here is one of the rewritten statements.
update /*+ streams restrict_all_ref_cons */ "CADPROD"."OMS_SQL_STATEMENT" p
set *"APPLICATION"=decode(:1,'N',"APPLICATION",:2)*,
"STATEMENT"=dbms_reputil2.get_final_lob(:3,"STATEMENT",:4)
where (:5='N' or(1=1 and (:6='N' or(dbms_lob.compare(:7,"STATEMENT")=0)or(:7 is null and "STATEMENT" is null)))) and(:8="APPLICATION")
The problem comes in, we believe, with the attempt to write the value "APPLICATION" to the application column which is only a 10 character field. the value for the :1 bind variable is "N" and the value for :2 is null.
We see the following error on the logical standby:
ORA-00600: internal error code, arguments: [kgh_heap_sizes:ds], [0x01FCDBE60], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [kxtoedu+54] [PC:0x2542308] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ] []
ORA-12899: value too large for column "CADPROD"."OMS_SQL_STATEMENT"."APPLICATION" (actual: 19576, maximum: 10)
Is this a configuration issue or is it normal for SQL Apply to convert statements from logminer into decode statements?
We have an Oracle 10.2.0.4 database running on windows 2003 R2 64-bit os. We have 3 physical and 2 logical standby's, no problems on the physical standbys.Hello;
I noticed some of your parameters seem to be wrong.
fal_client - This is Obsolete in 11.2
You have db_name='test' on the Standby, it should be 'asadmin'
fal_server=test is set like this on the standby, it should be 'asadmin'
I might consider changing VALID_FOR to this :
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
Document 278371.1 is showing its age in my humble opinion.
-----Wait on this until you fix your parameters----------------------
Try restarting the SQL Apply
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
Use these statements to trouble shoot :
SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
mseberg
Edited by: mseberg on Feb 14, 2012 7:37 AM -
Logical Standby recover with RMAN
Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data GuardHello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg
Maybe you are looking for
-
Screen inverter model no. - Macbook 3.1
The backlight in my macbook recently turned defect. The computer is out of warranty and it can only pay to DIY. I am interested in buying a new 'inverter' for the screen or the cable that it uses. I have diagnosed the problem to being a defect invert
-
E71 signal hampered by holding the phone??????
I have an E71 on O2, and the signal is massively affected by whether I am holding the phone or not!!!! There is only one part of the house I can get 3G (close against my office window), and the rest of the house, especially downstairs I get a 1-3 bar
-
I have just downloaded itunes 10.6 and in the process my "podcast" option under library has disappeared! THe files are still on my laptop. I can also see some of my recorded music in the itunes library but can't play them - there is an exclamation ma
-
something about the pushpin, but it's not there, where the heck would I find the music?
-
How to add scroll bars to a panel
Hi Can anyone plz tell me how to add a scroll bar to a panel created within a JFrame Regards ats