Triggers not Fire in Logical Standby
Hi,
I'still have this question even after reading some post in this forum concerning creating Triggers in a Logical Standby
Let's see this Case.
MY Primary
Table A Trigger A1 Fire into > Table A1
MY Logical - Just Created as New
Table A Trigger A1 Fire into > Table A1 >>>> This Is a copy of the Primary Structire
IF I want to add a new Trigger into Table A I get :
Table A Trigger A2 Fire into > Table A2 >>>>> This is after
My Logical Structure will become:
Table A Trigger A1 Fire into > Table A1 >>>>> This belongs to the initail Strcuture
Trigger A2 Fire into > Table A2 >>>>> This Added After
My Question?
When the log are being applied on the Logical and obviously inserts into TABLE A will occur ... will Trigger A2 Fire into Table A2 ?
I hope I make myself understandable ...
Thxs for your Help
I know it's quite a long-time that anyone replied this post, but I just need to report our attempts to workaround that.
Dropping function-based indexes in primary database, just before creation of Logical Dataguard hasn't solved our problem, neither dropping indexes in logical database.
In my opinion and after some docs in metalink, I think there's no way to solve it.
Or you drop them or you migrate to 10g.
Regards.
Similar Messages
-
Redo data not applied on logical standby database 10g
after a network problem within the primary and the logical standby database. The redo data is not applied on the logical standby even if all the archived log are sent to it.
The below is the output from v$archive_gap and DBA_LOGSTDBY_LOG
SQL> select * from v$archive_gap;
no rows selected
SQL> SELECT SEQUENCE#, FIRST_TIME, APPLIED
FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#; 2 3
SEQUENCE# FIRST_TIME APPLIED
3937 24-FEB-10 01:48:23 CURRENT
3938 24-FEB-10 10:31:22 NO
3939 24-FEB-10 10:31:29 NO
3940 24-FEB-10 10:31:31 NO
3941 24-FEB-10 10:33:44 NO
3942 24-FEB-10 11:54:17 NO
3943 24-FEB-10 12:05:30 NO
Any help?
ThanksORA-00600: internal error code, arguments: [krvxgirp], [], [], [], [], [], [], []
LOGSTDBY Analyzer process P003 pid=48 OS id=8659 stopped
Wed Feb 24 16:49:04 2010
Errors in file /oracle/product/10.2.0/admin/umarket/bdump/oradb_lsp0_8651.trc:
ORA-12801: error signaled in parallel query server P003
ORA-00600: internal error code, arguments: [krvxgirp], [], [], [], [], [], [], []
and below an Warning: Apply error received: ORA-26714: User error encountered while applying. Clearing. from oradb_lsp0_8651.trc
Thanks -
When do Navigation triggers not fire?
hi there! I read this statements below, but i cannot understand. Can anybody give more illustration or example? tx.
"The Pre- and Post-navigation triggers do not fire if they belong to a unit that is lower in the hierarchy than the current validation unit. For instance, if the validation unit is Record, Pre- and Post-Text-Item triggers do not fire."At design time in property palette, and also at runtime with Set_Form_Property( VALIDATION_UNIT ).
Look at the online help documentation.
Francois -
Why could not Oracle replicates tables which includes Spatial Data to Logical Standby?
Hi all,
Nowadays, i am working on Oracle Logical Standby Databases which includes Spatial Data? But i could not achieve to transport a table with multimedia data (with spatial data types ). But Logical Standby Databases can not support this type of tables? Is this a restriction of modelling Spatial and Geometry in data blocks? And how do i achieve this because i should use this secondary for query-only?
Kind Regards,Some data types are simply not supported by logical standby replication. Depending on the version, this might or might not include Spatial.
11.2: https://docs.oracle.com/cd/E11882_01/server.112/e41134/data_support.htm#SBYDB4936
12.1: https://docs.oracle.com/database/121/SBYDB/data_support.htm#SBYDB4936
If you need to replicate Spatial data, you need to look at other mechanisms. E.g., physical standby, materialized views, or GoldenGate. -
Dataguard Problem(logical standby database)
Hi,
I have successfully created logical standby database, and everything is working fine, all of the SQL is applying and archiving is also shipping.
Until I create a new tablespace for e.g. pay in the primary database, and suddenly SQL applying is stopped, but the archive is shipping.
I am using Windows XP SP2 and Oracle 10gRel2.
The contents of AlertLog file are as
Wed Jul 23 22:52:19 2008
Thread 1 cannot allocate new log, sequence 133
Checkpoint not complete
Current log# 3 seq# 132 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
Wed Jul 23 22:52:23 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:52:23 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:52:23 2008
Thread 1 advanced to log sequence 133 (LGWR switch)
Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
Thread 1 cannot allocate new log, sequence 134
Checkpoint not complete
Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
Wed Jul 23 22:52:29 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:52:29 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:52:29 2008
Thread 1 advanced to log sequence 134 (LGWR switch)
Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
Wed Jul 23 22:55:49 2008
Thread 1 cannot allocate new log, sequence 135
Checkpoint not complete
Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
Wed Jul 23 22:55:54 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:55:54 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:55:54 2008
Thread 1 advanced to log sequence 135 (LGWR switch)
Current log# 3 seq# 135 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
When i use this command, the SQL Apply starts again but the tablespace is not created on Logical standby database.
kindly give me a solution.
Thanks in advanced.In Standy database also you need to add TB details for it to recognise Primary DB new TB .
try adding it and retry your operation . -
Data Guard Logical Standby Skip Handler bug
Does anyone know of a documented bug concerning the skip handler not skipping a grant on a view in a schema with a SCHEMA_DDL skip handler defined?
Here is my test case.
On Primary:
Create table scott.junk (x number) tablespace users; (created successfully on logical standby)
On logical standby:
exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
On Primary:
grant select on scott.junk to public; (successfully skipped due to missing object)
On Primary:
create view scott.v_junk as select * from scott.junk; (successfully skipped on logical standby)
On Primary:
grant select on scott.v_junk to public; (received 'ora-00942 table or view does not exist' on logical standby and SQL Apply stopped).
I'm running version 10.2.0.4 but have not applied the recommended patch bundle for logcal standby #7937113.8.
If anyone knows whether this has been documented or not, please let me know. If not, I will submit an SR to get this documented.
Thanks,
Michael Anderson
OCP - Bank of the WestWhen I look at the syntax for the package
http://www.morganslibrary.org/reference/dbms_logstdby.html
what I see is:
dbms_logstdby.skip(
stmt IN VARCHAR2,
schema_name IN VARCHAR2 DEFAULT NULL,
object_name IN VARCHAR2 DEFAULT NULL,
proc_name IN VARCHAR2 DEFAULT NULL,
use_like IN BOOLEAN DEFAULT TRUE,
esc IN CHAR1 DEFAULT NULL);So looking at your code:
exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
'SCHEMA_DDL' is your statement.
'SCOTT' is your schema name.
'%' indicates all objects
and ... shouldn't there be a comma before the NULL?
In the future don't provide values where the default's will suffice. It makes thing's far simpler. -
Resynchronization in logical standby db
hi,
i am new in oracle 10g logical standby database.
last night i have updated some new tables & views on primary database. but new tables & views are not showing at logical standby database for last 20 hours.
please tell how can i retrieve new tables on logical standby serverHi;
For your issue i suggest close your thread here as changing thread status to answered and move it to Forum Home » Database » Data Guard which you can get more quick response
Regard
Helios -
Restoring Logical standby rman backup on production
Hi ,
I have One Production and one logical standby database .
Due to tape problem we are unable to take backups of promary . And due to businness , we cannot take back up on disk in hot period(Bank database ) .
Can anyone tell me , if i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? .
Logical standby is in sync with primary .user12045405 wrote:
Can anyone tell me , if i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? .
No. http://docs.oracle.com/cd/E11882_01/server.112/e25608/rman.htm#SBYDB4848 says:
>
Note:
Backups of logical standby databases are not usable at the primary database. -
Forward physical standby archivelog files to a logical standby database
Hi,
We have a production database (1) and we have a physical standby database (2) for it.
Is it possible to forward the archivelogs files from (2) to a logical standby database (3). We want to use the (3) as a UAT - Ad Hoc read only Database.
Thanks.Hi,
The following Data Guard configurations using cascaded destinations are supported.
A. Primary Database > Physical Standby Database with cascaded destination > Physical Standby Database
B. Primary Database > Physical Standby Database with cascaded destination > Logical Standby Database
A physical standby database can support a maximum of nine (30 as of Version 11.2) remote destinations.
Physical Standby Forwarding Redo to a Logical Standby :
Advantages :
1. Users can connect to Logical Standby database and they can access
2. Instead of querying primary database they can use logical standby database.
3. without any additional overhead on your primary system, and without consuming any additional transatlantic bandwidth.
Disadvantages :
The following data types will not support in Logical standby database just check your application before implementing logical standby
a. BFILE
b. Collections (including VARRAYS and nested tables)
c. Multimedia data types (including Spatial, Image, and Oracle Text)
d. ROWID, UROWID
e. User-defined types
f. LOBs stored as SecureFiles
g. XMLType stored as Object Relational
h. Binary XML
Thanks
LaserSoft -
Interesting issue with Logical Standby and database triggers
We have a Logical Standby that each month we export (expdp) a schema (CSPAN) that is being maintained by SQL Apply and import (impdp)it to a 'frozen copy' (eg CSPAN201104) using REMAP_SCHEMA.
This works fine although we've noticed that because triggers on the original schema being exported have the original schema (CSPAN) hard-referenced in the definition are imported into and owned by the new 'frozen' schema but are still 'attached' to the original schema's tables.
This is currently causing the issue where the frozen schema trigger is INVALID and causing the SQL Apply to fail. This is the error:
'CSPAN201104.AUD_R_TRG_PEOPLE' is
invalid and failed re-validation
Failed SQL update "CSPAN"."PEOPLE" set "ORG_ID" = 2, "ACTIVE_IND" = 'Y', "CREATE_DT" = TO_DATE('22-JUL-08','DD-MON-RR'),"CREATOR_NM" = 'LC', "FIRST_NM" = 'Test', "LAST_PERSON" ='log'...
Note: this trigger references the CSPAN schema (...AFTER INSERT ON CSPAN.PEOPLE...)
I suspect that triggers on a SQL Apply Maintained schema in a Logical Standby do not need to be valid (since they do not fire) but what if they reference a SQL Apply schema but are 'owned' by a non-SQL Apply schema? This trigger references a SQL Apply table so it should not fire
This is 10gR2 (10.2.0.4) on 64 bit Windows.
Regards
Graeme KingOK, I've finally got around to actually test this and it looks like you are not quite correct Larry in this statement...
'Since this trigger belongs to a new schema that is not controlled by SQL Apply (CSPAN201105) it will fire. But the trigger references a schema that is controlled by SQL Apply (CSPAN) so it will fail because it has to be validated.'
My testing concludes that even though the trigger belongs to a schema CSPAN201105 (not controlled by SQL Apply) and references a schema controlled by SQL Apply - it does not fire. However it DOES need to be valid or it breaks SQL Apply.
My testing was as follows:
Primary DB
Create new EMP table in CSPAN schema on Primary
Create new table TRIGGER_LOG in CSPAN schema on Primary
Create AFTER INSERT/UPDATE trigger on CSPAN.EMP table (that inserts into TRIGGER_LOG table)
**All of the above replicates to Standby**
Standby DB
Create new table TRIGGER_LOG_STNDBY in CSPAN201105 schema on Primary
Create new trigger in CSPAN201105 schema that fires on INSERT/UPDATE on CSPAN.EMP but that inserts into CSPAN201105.TRIGGER_LOG_STNDBY table)
Primary DB
Insert 4 rows into CSPAN.EMP
Update 2 rows in CSPAN.EMP
TRIGGER_LOG table has 6 rows as expected
Standby DB
TRIGGER_LOG table has 6 rows as expected
TRIGGER_LOG_STNDBY table has **0 rows**
Re-create trigger in CSPAN201105 schema that fires on INSERT/UPDATE on CSPAN.EMP but that inserts into CSPAN201105.TRIGGER_LOG_STNDBY table) **but with syntax error**
Primary DB
Update 1 row in CSPAN.EMP
TRIGGER_LOG table has 7 rows as expected
Standby DB
SQL Apply is broken - ORA-04098: trigger 'CSPAN201105.TEST_TRIGGER_TRG' is invalid and failed re-validation -
Creating triggers in a logical standby database
Does anyone know if its possible to create and enable a trigger in a logical standby database on a 'guarded' table? I've been able to create the trigger (as an after insert trigger) and it appears to be valid but it never seems to fire, despite inserts taking place. Are there any other steps involved to activate this, or is it just plain not possible in a logical standby? My primary and logical standby databases are 10.2.0.3
HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR> -
Hi,
i have configured logical standby in 11gr2. IT replicates properly. Now the replication get stopped and it show the below error. Please suggest me to start the replication.
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 10618, //u01/primary_2345.dbf
Fri Mar 30 13:06:14 2012
LOGMINER: End mining logfiles during commit scan for session 1
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 10618, /u01/primary_2345.dbf
Fri Mar 30 13:06:15 2012
LOGSTDBY Analyzer process AS00 started with server id=0 pid=39 OS id=8993
Fri Mar 30 13:06:15 2012
LOGSTDBY Apply process AS01 started with server id=1 pid=40 OS id=8995
Fri Mar 30 13:06:15 2012
LOGSTDBY Apply process AS02 started with server id=2 pid=41 OS id=8997
Fri Mar 30 13:06:15 2012
LOGSTDBY Apply process AS03 started with server id=3 pid=43 OS id=8999
Fri Mar 30 13:06:15 2012
LOGSTDBY Apply process AS04 started with server id=4 pid=45 OS id=9001
Fri Mar 30 13:06:15 2012
LOGSTDBY Apply process AS05 started with server id=5 pid=46 OS id=9003
LOGSTDBY Apply process AS01 server id=1 pid=40 OS id=8995 stopped
Errors in file /oracle/oracle/diag/rdbms/lgdb/lgdb/trace/lgdb_as01_8995.trc:
ORA-01418: specified index does not exist
Errors in file /oracle/oracle/diag/rdbms/lgdb/lgdb/trace/lgdb_lsp0_8930.trc:
ORA-26808: Apply process AS01 died unexpectedly.
ORA-01418: specified index does not exist
LOGSTDBY Analyzer process AS00 server id=0 pid=39 OS id=8993 stopped
LOGSTDBY Apply process AS02 server id=2 pid=41 OS id=8997 stopped
LOGSTDBY Apply process AS05 server id=5 pid=46 OS id=9003 stopped
LOGSTDBY Apply process AS03 server id=3 pid=43 OS id=8999 stopped
LOGSTDBY Apply process AS04 server id=4 pid=45 OS id=9001 stopped
LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=34 OS id=8985 sid=22 stopped
LOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=36 OS id=8987 sid=23 stopped
LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=37 OS id=8989 sid=1910 stopped
=====================================================================================================================
In in the trace file, It show as
ORA-01418: specified index does not exist
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01418: specified index does not existknasplcr: eager error was not rolled back
++ LCR Dump Begin: 0x9ffffffffd3f8070 - ddl
op: 5, Original op: 5, baseobjn: 0, objn: 1607159, objv: 65535
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: 0x00297a.0000a2ec.03b0
scn: 0x0000.0d2761ba, (scn: 0x0000.00000000, scn_sqn: 0, lcr_sqn: 0)xid: 0x0004.014.00013503, parentxid: 0x0004.014.00013503, proxyxid: 0x0000.000.00000000
ncol: 0 newcount: 24, oldcount: 0
LUBA: 0x10.4000d6a.14.7.92
++ LCR Dump Begin: 0xc0000002197a6580 - 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: 22, iotPrimaryKeyCount: 0, numChgRec: 0
NumCrSpilled: 0
RedoThread#: 1, rba: 0x00297a.0000a303.0070
scn: 0x0000.0d2761c8, (scn: 0x0000.0d2761c8, scn_sqn: 1, lcr_sqn: 1)xid: 0x0004.014.00013503, parentxid: 0x0004.014.00013503, proxyxid: 0x0000.000.00000000
ncol: 0 newcount: 0, oldcount: 0
LUBA: 0x10.4000d6e.14.14.34
Apply Slave is exiting due to error ORA-1418KSV 1418 error in slave process
ORA-01418: specified index does not exist
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01418: specified index does not exist -
Logical Standby Database Not Getting Sync With Primary Database
Hi All,
I am using a Primary DB and Logical Standby DB configuration in Oracle 10g:-
Version Name:-
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
We have build the logical standby last week and till date the Logical DB is not sync. I have checked the init parameters and I wont see any problems with it. Also archive log destinations are also fine enough.
We have a important table named "HPD_HELPDESK" where record count is growing gradually whereas in logical standby it's not growing. There are some 19K record difference in the both the tables.
I have checked the alert log but it is also not giving any error message. Please find the last few lines of the alert log in logical Database:-
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1703_790996778.arc] to LogMiner session id [1]
Tue Aug 28 14:56:52 GMT 2012
RFS[2853]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 14:56:58 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 14:57:00 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1704_790996778.arc] to LogMiner session id [1]
Tue Aug 28 15:06:40 GMT 2012
RFS[2854]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 15:06:47 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 15:06:49 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1705_790996778.arc] to LogMiner session id [1]
I am not able to trace the issue that why the records are not growing in logical DB. Please provide your inputs.
Regards,
ArijitHow do you know that there's such a gap between the tables?
If your standby db is a physical standby, then it is not open and you can't query your table without cancelling the recovery of the managed standby database.
What does it say if you execute this sql?
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;The ARCH processes should be connected and MRP waiting for a file.
If you query for the archive_gaps, do you get any hits?
select * from gv$archive_gapIf you're not working in a RAC environment you need to query v$archive_gap, instead!
Did you check whether the archives generated from the primary instance are transferred and present in the file system of your standby database?
I believe your standby is not in recovery_mode anymore or has an archive_gap, which is the reason why it doesn't catch up anymore.
Hope it helps a little,
Regards,
Sebastian
PS: I'm working on 11g, so unfortunately I'm not quite sure if the views are exist in 10gR2. It's worth a try though!
Edited by: skahlert on 31.08.2012 13:46 -
Hi,
I'm not sure if anyone is using the logical standby database because it appears to me to be complete rubbish. The apply of redo data just does not appear to work. for example I have this table:
create table test29(
BP_ID NUMBER(10) NOT NULL,
BP_K_ID NUMBER(10) NOT NULL,
BP_TYP CHAR(2) NOT NULL,
BP_U_ID NUMBER(10),
BP_ACTIVE DATE NOT NULL,
BP_USED NUMBER(6) NOT NULL,
BP_STATUS CHAR(1) NOT NULL,
BP_LASTUPDATE DATE NOT NULL
and insert this data:
insert into test29
select 10643,291904,'O ',1,TO_DATE('01/05/2003 00:44:18', 'MM/DD/YYYY HH24:MI:SS'),0,'A',TO_DATE('01/06/2004 20:13:08', 'MM/DD/YYYY HH24:MI:SS') from dual
When this information is transfered to the logical standby and it attempts to read it i get a ORA-26689: column datatype mismatch in LCR. But wait! If I change the name of column 6 (BP_PUNKTE) to say (BP_AAAAA) and try again it works!!! The logical standby fails on many tables just because of the name (updates, inserts anything)...did anyone at oracle test this? Is anyone using the logical standby have any ideas how and if I could ever get this working.
Using Oracle 9.2.0.4. on Redhat 2.1.
Thanks!
Steve.unfortunately not. the oracle licence was purchased before i arrived and when I attempted to get a support contact they want the money since we purchased the licence 3 years ago. 3 years of cash for free! why should I pay for their bugs anyway, when we buy this expensive software it should work. when I buy a new car from ford and radio does not work I don't have to pay ford to fix it. rip-off!
-
Fast Start Failover has broken my Logical Standby and Flashback has not helped
I have a primary ( PRIMARYP ), a physical standby ( STANDBYP ) and a logical standby ( STANDBYL ).
I configured Fast Start Failover ( with STANDBYP as the target ) and started an Observer. I did a shutdown abort on my primary and the Fast Start Failover did make STANDBYP the primary. I was able to reinstate PRIMARYP as a physical standby.
However when I checked my broker config it gave for STANDBYL
ORA-16795: the standby database needs to be recreated
Strange I though, since I would have expected STANDBYL to survive ok given that the new primary, STANDBYP was a physical standby of PRIMARYP.
Not to worry I thought, I simply will flashback STANDBYL to the beginning of the day and SQL APPLY will reapply all the redo.
This is where the problem begins
I mount STANDBYL
RMAN> connect target /
connected to target database: STANDBYL (DBID=440422466, not open)
RMAN> flashback database to time "TO_DATE('05/12/13 09:30:00','DD-MM-YY HH24:MI:SS')";
Starting flashback at 05-DEC-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=11 device type=DISK
starting media recovery
archived log for thread 1 with sequence 24 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_04/o1_mf_1_24_99yqwog0_.arc
archived log for thread 1 with sequence 25 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_05/o1_mf_1_25_9b0mlyvr_.arc
media recovery complete, elapsed time: 00:00:04
Finished flashback at 05-DEC-13
RMAN> quit
Recovery Manager complete.
oraclel[STANDBYL]>dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/manager
Connected.
DGMGRL> shutdown;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
DGMGRL>
DGMGRL>
DGMGRL> startup;
ORACLE instance started.
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
ORA-01589 - that a nasty surprise ! I didn't think I would need to do anything with the log sequences after a flashback
Any ideas of what is going on ?
thanks,
JimHello;
This pdf might meet your needs :
http://blogs.oracle.com/AlejandroVargas/resource/DATAGUARD-FSFO-IMPLEMENTATION.pdf
Additional info :
http://oracle-tech.blogspot.com/2008/08/fast-start-failover-it-is-reliable.html
http://jakub.wartak.pl/blog/?p=80
http://www.databasejournal.com/features/oracle/article.php/3849106/Fast-Start-Failover-in-Oracle-11g-Data-Guard.htm
Best Regards
mseberg
Maybe you are looking for
-
Getting error while updating data element using Xquery Automator
Hi, I am getting following error while i am trying to update a data element in my task. <Nov 28, 2011 5:02:40 PM IST> <Error> <oms> <BEA-000000> <automation.AutomationDispatcher: Failed to execute on/plugin/external/ACOI_TMIP_POC/1.0.0/CLARIFY_Task.a
-
I would like to know the process of those third party order. 1. Create SO with item cat is thrid party 2. assign PR to PO 3. MIGO <------ I don't know whether need good received or not 4. PGI 5. Billing. Above steps is correct or not. Thanks!
-
Sharing an imported PDF via a link
I uploaded/imported an AcroForm to my FormCentral (FC) account, added the submit button in FC and now I'd like to share a link to the file for users to access the form, vs me having to send them a the Submission-Enabled PDF version that I downloaded.
-
Hi, SQL> select database_role from v$database; DATABASE_ROLE PRIMARY SQL> select applied,status from v$archived_log where applied='NO' and status='A'; APP S NO A NO A NO A NO A NO A NO A NO A NO A NO A NO A NO A APP S NO A NO A NO A NO A NO A NO A NO
-
Match EQ. Good plug, but there's something that dosen't add up..
I tried Match EQ plug and I find it useful to observe and compare Mixes and tracks, but there's something I can't understand. Here it is: I made a match EQ between a source and a destination Mix in 2 different way: 1. The source Mix was louder than t