RE: Logical standby mode - Dataguard - 9.2.0.4
OR is it so that logical Standby mode is just NOT possible for the Entire Database if the Database has even 1 Table with a LONG field datatype ? -Original Message- From: VIVEK_SHARMA Sent: Monday, September 29, 2003 1:25 PM To: Multiple recipients of list ORACLE-L Subject: Logical standby mode - Dataguard - 9.2.0.4 A Basic Qs. On Logical standby mode - Dataguard - 9.2.0.4 . Is the following statement correct ? From the Primary Database the DMLs on tables NOT having LONG columns are successfully applied across to the Logical Standby database while those tables containing LONG columns fail . Query to find Objects which are NOT supported ;- Select * from DBA_LOGSTDBY_UNSUPPORTED;
RE: Logical standby mode - Dataguard - 9.2.0.4
A Basic Qs. On Logical standby mode - Dataguard - 9.2.0.4 . Is the following statement correct ? From the Primary Database the DMLs on tables NOT having LONG columns are successfully applied across to the=20 Logical Standby database while those tables containing LONG columns fail Query to find Objects which are NOT supported ;- Select * from DBA_LOGSTDBY_UNSUPPORTED; I have done a number of tests for a customer, although I cannot *swear* I was on 9.2.0.4. All I can say is that, trying to see how things were going on when doing an import, I exported data I didn't know. As it happened, they were LONG columns in it - and I was unaware of it. So, yes, indeed it failed. Not systematically though, since some tables went through. And no, nothing was listed in DBA_LOGSTDBY_UNSUPPORTED. And I also find the statement according to which everything goes well if there is no LONG a tad optimistic, because even with a nominally 'safe' set of data to replicate I had ORA-00600 errors. Looks interesting, promising - and totally immature. The lack of proper monitoring facility is scary (very difficult to say when and why something goes wrong - and you see it at only one end, not both). Except for tests, I shall wait for a stable 10g before playing with logical standby databases again. Regards, Stephane Faroult Oriole -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Stephane Faroult INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Logical standby mode - Dataguard - 9.2.0.4
Can anyone who has successfully used Logical Standby Database share the ENTIRE Commands set? I shall share our entire current commands set which is being used to bring up the Logical standby database ( without any errors ) with anyone who asks. NOTE Though there are NO Errors (in alert_SID.log) all Our Commands complete successfully, DMLs on Primary tables are NOT getting applied to Standby Database We have raised a few Oracle TARs too. Thanks -Original Message- From: VIVEK_SHARMA Sent: Monday, September 29, 2003 1:40 PM To: Multiple recipients of list ORACLE-L Subject: RE: Logical standby mode - Dataguard - 9.2.0.4 OR is it so that logical Standby mode is just NOT possible for the Entire Database if the Database has even 1 Table with a LONG field datatype ? -Original Message- From: VIVEK_SHARMA Sent: Monday, September 29, 2003 1:25 PM To: Multiple recipients of list ORACLE-L Subject: Logical standby mode - Dataguard - 9.2.0.4 A Basic Qs. On Logical standby mode - Dataguard - 9.2.0.4 . Is the following statement correct ? From the Primary Database the DMLs on tables NOT having LONG columns are successfully applied across to the Logical Standby database while those tables containing LONG columns fail . Query to find Objects which are NOT supported ;- Select * from DBA_LOGSTDBY_UNSUPPORTED;
