SQL apply is very slow on Logical Standby..!!

Hello all,
We are having Data Guard setup in our environment where we are having Primary, Physical Standby as well as logical standby databases..
DB Version : 10.2.0.1 in all databases (Pri, Phy and Logical)
OS : RHEL4
Only Oracle is running on this Box..
Since last month we are facing problems in Logical Standby database where it seems SQL apply has become very slow..
Archive log files are successfully transferring from Primary but since SQL apply has become slow logical standby is lagging behind primary by two days..
How do i speed up this SQL apply..?? Any ideas and suggestions are most welcome..
I checked TOP command to find out which oracle processes are consuming maximum CPU and i have found ora_p000_oracle, ora_p001_oracle, ora_p002_oracle, ora_p003_oracle, ora_p004_oracle, ora_p005_oracle, etc processes are consuming highest CPU and Load Average has always been above 1..
Any help would be greatly appreciated..
Thanks - HP

Hello;
These Oracle notes might help :
Slow Performance In Logical Standby Database Due To Lots Of Activity On Sys.Aud$ [ID 862173.1]
Oracle10g Data Guard SQL Apply Troubleshooting [ID 312434.1]
Developer and DBA Tips to Optimize SQL Apply [ID 603361.1]
Best Regards
mseberg

Similar Messages

SQL Developer is very slow...

I'm having performance issues with Oracle SQL Developer. I tried both and 1.5.4 and 2.1.0 (installed in Windows XP Professional) and both work very slow. When I connect to the same database in Apex or just the webconsole, performance is OK, so I think it's SQL Developer that's slow, not the database.
The problem is that the "Connected To Database..." screen with the "knightrider-bar" appears for some seconds for almost every action I want to perform (retrieving all views, showing constraints, triggers, etc...). Always the waiting screen appears for 3 - 5 seconds, which is very annoying.
Anybody knows what could be the problem? Working through the SQL Console in APEX is much more performant at this moment, but SQL Developer is more handy (if it would work faster).

thefurryone wrote:
Tom,
As well as the ide/bin folder, there is a sqldeveloper/bin folder, which has a sqldeveloper.exe as well as the one in the root folder.
Just as another thought - where is SQL Developer installed? Is it local on your PC or on a network drive? Especially when using the version with the included JDK, running off a network drive can be much slower.
theFurryOneOK, found it now. I opened SQLDeveloper there and the console didn't show any messages. When I connect to the database I got this message in the console:
Finished parsing = 15+
UsersCache.fillIn() time = 0 ret==null?: true+
I don't run SQLDeveloper from a network drive, it's installed locally on my C:\ drive. The database however is on a server, but I have a gigabit connection to it and applications don't have performance issues. So I suppose it's actually SQLDeveloper that's slow. Are there any tools in SQLDeveloper that could cause the bad performance, and that I could switch off?

Sql is running very slow

hello everyone
here is my procedure
in procedure select statement is running very slow it takes 20min
DECLARE
y10_pad_sd_1 number;
y10_sad_sd_1 number;
y10_sad_oe_1 number;
y10_she18_avg_1 number;
y10_she_avg_1 number;
y10_o_pad_sd_1 number;
y10_e_pad_sd_1 number;
y10_o_sad_sd_1 number;
y10_e_sad_sd_1 number;
y15_pad_sd_1 number;
y15_sad_sd_1 number;
y15_sad_oe_1 number;
y15_she18_avg_1 number;
y15_she_avg_1 number;
y15_o_pad_sd_1 number;
y15_e_pad_sd_1 number;
y15_o_sad_sd_1 number;
y15_e_sad_sd_1 number;
y20_pad_sd_1 number;
y20_sad_sd_1 number;
y20_sad_oe_1 number;
y20_she18_avg_1 number;
y20_she_avg_1 number;
y20_o_pad_sd_1 number;
y20_e_pad_sd_1 number;
y20_o_sad_sd_1 number;
y20_e_sad_sd_1 number;
CURSOR c_pn IS
SELECT
pn_id pn_id
,pn_dm pn_dm
,arch_id arch_id
,o_ink o_ink
,o_color o_color
,e_ink e_ink
,e_color e_color
FROM pn_list_iqp_95cl;
type c7 is table of c_pn%rowtype;
c8 c7;
BEGIN
open c_pn;
fetch c_pn bulk collect into c8;
close c_pn;
for i in 1..c8.last loop
SELECT /*+ use_hash(pmo pme) */
LEAST(MAX ( pmo.y10_pad_sd ), MAX ( pme.y10_pad_sd ))
,LEAST(MAX ( pmo.y10_sad_sd ), MAX ( pme.y10_sad_sd ))
,LEAST(MAX ( pmo.y10_sad_oe ), MAX ( pme.y10_sad_oe ))
,LEAST(MAX ( pmo.y10_she18_avg), MAX ( pme.y10_she18_avg ))
,LEAST(MAX ( pmo.y10_she_avg ), MAX ( pme.y10_she_avg ))
,LEAST(MAX ( pmo.y10_o_pad_sd ), MAX ( pme.y10_o_pad_sd ))
,LEAST(MAX ( pmo.y10_e_pad_sd ), MAX ( pme.y10_e_pad_sd ))
,LEAST(MAX ( pmo.y10_o_sad_sd ), MAX ( pme.y10_o_sad_sd ))
,LEAST(MAX ( pmo.y10_e_sad_sd ), MAX ( pme.y10_e_sad_sd ))
,LEAST(MAX ( pmo.y15_pad_sd ), MAX ( pme.y15_pad_sd ))
,LEAST(MAX ( pmo.y15_sad_sd ), MAX ( pme.y15_sad_sd ))
,LEAST(MAX ( pmo.y15_sad_oe ), MAX ( pme.y15_sad_oe ))
,LEAST(MAX ( pmo.y15_she18_avg), MAX ( pme.y15_she18_avg ))
,LEAST(MAX ( pmo.y15_she_avg ), MAX ( pme.y15_she_avg ))
,LEAST(MAX ( pmo.y15_o_pad_sd ), MAX ( pme.y15_o_pad_sd ))
,LEAST(MAX ( pmo.y15_e_pad_sd ), MAX ( pme.y15_e_pad_sd ))
,LEAST(MAX ( pmo.y15_o_sad_sd ), MAX ( pme.y15_o_sad_sd ))
,LEAST(MAX ( pmo.y15_e_sad_sd ), MAX ( pme.y15_e_sad_sd ))
,LEAST(MAX ( pmo.y20_pad_sd ), MAX ( pme.y20_pad_sd ))
,LEAST(MAX ( pmo.y20_sad_sd ), MAX ( pme.y20_sad_sd ))
,LEAST(MAX ( pmo.y20_sad_oe ), MAX ( pme.y20_sad_oe ))
,LEAST(MAX ( pmo.y20_she18_avg), MAX ( pme.y20_she18_avg ))
,LEAST(MAX ( pmo.y20_she_avg ), MAX ( pme.y20_she_avg ))
,LEAST(MAX ( pmo.y20_o_pad_sd ), MAX ( pme.y20_o_pad_sd ))
,LEAST(MAX ( pmo.y20_e_pad_sd ), MAX ( pme.y20_e_pad_sd ))
,LEAST(MAX ( pmo.y20_o_sad_sd ), MAX ( pme.y20_o_sad_sd ))
,LEAST(MAX ( pmo.y20_e_sad_sd ), MAX ( pme.y20_e_sad_sd ))
INTO
y10_pad_sd_1
,y10_sad_sd_1
,y10_sad_oe_1
,y10_she18_avg_1
,y10_she_avg_1
,y10_o_pad_sd_1
,y10_e_pad_sd_1
,y10_o_sad_sd_1
,y10_e_sad_sd_1
,y15_pad_sd_1
,y15_sad_sd_1
,y15_sad_oe_1
,y15_she18_avg_1
,y15_she_avg_1
,y15_o_pad_sd_1
,y15_e_pad_sd_1
,y15_o_sad_sd_1
,y15_e_sad_sd_1
,y20_pad_sd_1
,y20_sad_sd_1
,y20_sad_oe_1
,y20_she18_avg_1
,y20_she_avg_1
,y20_o_pad_sd_1
,y20_e_pad_sd_1
,y20_o_sad_sd_1
,y20_e_sad_sd_1
FROM pm_list_iqp_95cl pmo ,pm_list_iqp_95cl pme
WHERE pmo.pn_id = pme.pn_id
AND pme.pn_id = c8(i).pn_id
AND pmo.slot_cd = 'O'
AND pme.slot_cd = 'E';
END LOOP;
END;

EXPLAIN PLAN FOR THIS QUERY
cached plan :cost all rows(cost:4)
step name step cost rows
select statement 6 4
sort(aggregate) 5 1
merge join(cartesian) 4 4 1
tellatel.pm_list_iqp_95cl table access(full) 1 2 1
buffer(sort) 3 2 1
tellatel.pm_list_iqp_95cl_table access(full) 2 2 1

SQL in statement very slow any help please

Hi guys forgive me if i dont give enough information we dont normally have many problems with slow queries as our data does not usually get to a level that is effected by speed.
I have a query that does a search of a view with approx 30k records. I then use a connect by to find all the relevent records that apply to this scenerio and place the results into an oracle form.
I have hard coded an example ('ACT' and 6089) into this code, but usually the numbers/code will be a parameter thats passed in.
Individually the select itemcode,notes from v_allitems takes approx 0.1 seconds to run
and the IN statement takes approx 0.007 seconds to run.
Together they take over 6 seconds which is a little too slow. So i assume its the IN thats causing me the problem as i am returning over 100 records to search IN. Is there an alternate way other than IN that anyone can think of to achieve the desired result?
Thanks in advance
select ITEMCODE, notes from v_allitems
where ITEMCODE = ( 'ACT'||','||6089) OR ITEMCODE IN
    (SELECT pcchildcode
      ||','
      || pcchild item
       FROM afpc
      CONNECT BY pcparent = prior pcchild
    AND pcparentcode        = prior pcchildcode START
    WITH pcparent           = 6089
    AND pcparentcode        = 'ACT'
UNION ALL
     SELECT pcparentcode
      ||','
      || pcparent item
       FROM afpc
      CONNECT BY pcchild = prior pcparent
    AND pcchildcode        = prior pcparentcode START
    WITH pcchild           = 6089
    AND pcchildcode        = 'ACT'
    )

I have just found another thread talking about the EXISTS condition, ill look into whether this will speed it up

SQL Query Report Very slow

Hi I have a sql query report that is taking very long to render.The query on sql developer comes back in less than a second.Any ideas on what could be wrong?

Hi
When posting code on the forum, put {noformat}{noformat} (with the curly brackets and the word code in lowercase) above and below your code like this...
{noformat}{noformat}
SELECT *
FROM emp
{noformat}{noformat}
It will then appear like this, preserving formatting...SELECT *
FROM emp
Next, how many rows are returned in total, it may be that you have SQL Developer set up to fetch only the first x number of rows?
Why have you put a CHOOSE hint in there?
Is it a classic report or an interactive report?
It looks like you're going over a database link, you really need to provide an explain plan (formatted as I have detailed above), a DRIVING_SITE hint may help you but it's impossible to know without seeing the plan...
Cheers
Ben

Sql statment is VERY slow

Hi all
I am facing a very big problem in my database.
when I execute the below select statement, it takes to much time to finish.
The value of cust_no is equal to 10.
SELECT fname, lname, pcode
FROM cust
WHERE id = :cust_no;
And I execute the same statement as shown below,it does NOT take too much time
SELECT fname, lname, pcode
FROM cust
WHERE id = 10;
the differnce between the above statements are WHERE id = :cust_no; and
WHERE id = 10;
Do you think that there is somethink change in the oracle optimizer behavior or in sql parsing?
recently I've done an analyze for all table accept sys and system users.
please could anyone help me?
by.
Edited by: user1089169 on Nov 13, 2012 11:45 AM

Hi,
while we cannot be 100% without seeing the execution plan, the most likely explanation for your problem is that the id column is skewed, i.e. some of the values in it are far more popular than others. Because of that, there is no one optimal plan: for popular values, a full table scan would be preferred (because it's good for handling large volumes of data), for less popular values, index access becomes a better choice.
When you are using a literal, the optimizer has enough information to come up with a good plan. When you're using a bind variable, the optimizer has to guess (in one way or another -- depending on your settings, it may rely on built-in defaults or use so-called bind peeking), so there is a good chance that it would pick a bad plan.
Best regards,
Nikolay

SQL Developer starting very slow

Im using SQL Developer 1.5.4 on Windows XP pro service pack 3
It had been working fine for a long time. Then suddenly starting take a very long time to start.
It is taking about 1 minute to load the splash screen, then about 1 more minute for the progress bar to display and start, then a while to actually show the window. All together its taking 2 to 4 minutes to load.
Could this be something with reading TNSNames? I find it strange that it is taking so long to show the splash screen. This is also happening on other computers in my office. They all started doing this at the same time.
And ideas or suggestions will be greatly appreciated.
thanks in advance!

Have your systems recently had new Microsoft applications, updates, or patches installed? That happened here last weekend and one of the new items caused a noticeable slowdown (things were taking about twice as long). Once I totally disabled the offending item (Microsoft Desktop Search) and re-booted, things were back to normal.
HTH.
Ed. H.

Logic is slow and computer is very slow with logic open

Ok so I Reset P-RAM parameters. appleoption+pr. I understand that I probably need to run it for a while to get things rolling again. but i have been doing that for a few days now and it is slower than ever. audio is continuously dropping out and i hear the processor starting up very slowly when it should be kicking in full gear. battery 2 is always saying that memory is low upon opening a song file. i need this bad boy in lubed lighting action. what do we do here?
Powermac G5 Dual 2.5, Mac OS X (10.4.3)

Hi adamluv,
- Which version of LogicPro are you running?
- How much RAM do you have?
- Upgrade to Mac OSX 10.4.8
- Never open another application (and then leave it open) before you launch LP.
- Turn off airport and get rid of redundant apps like widgets etc..
- Trash your LP preferences.
- Get Onyx and perform at least weekly maintenance on your computer.
Good luck,
sonther

SQL Query is very slow

Hello ,
I have a table like employee having more than 80 Lakhs records .
In the table there is a country column (country_name) having 234 distinct countries .
I have created index on Country_name column to make it fast .
I have created a view (employee_country) which is having distinct countries . The view is populating the country_name from employee table .
So , in the view (employee_country) have 234 distinct countries .
Now if I run select count(*) from employee_country ; then the query is taking ( 320.391 seconds ) time to show result ..
I am using one query which is taking the country_name from this view and comparing to another table with the country names .
like for example :
select ec.country_name from employee_country ec where ec.country_name not in (select cdf.country_name from country_dnb_full cdf)
I am using this query in APEX page to get the country name . But this query is very samll and taking 350.725 seconds to show the result . Therefore the APEX page when we run is showing time out error because the query is taking too much time .
I don't know why this problem is ?? I already created a index on country_name column to speed up the result . But still its not happening .
Please some one guide me where the problem is .??
Thanks
Prashant Dwivedi

Hi Prashant
First thing the view does not store any data. Its just a definition and the select query gets excuted on the original table whenever the view is referred.
Probabaly you can check for Materialized View.
Alternatively you can have a Look Up table if you think the values for the country_name is constant.
Regards
Arun

Determining the last archive applied on Logical Standby

Hi,
I am trying to determine the last log received and applied on my Logical Standby
SQL> select thread#, max(sequence#) "Last Standby Seq Received"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
group by thread# order by 1;
THREAD# Last Standby Seq Received
1 14
SQL> select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
Does not return anything
These statements work ok on a physical standby.
I know Sql Apply is enabled on my logical standby - my broker configuration is enabled and for the logical standby database, it is showing the Intended State as APPLY-ON with no Transport or Apply Lag on any of the databases
Q. How do I determine the last seq applied on my logical standby ?
thanks,
Jim

Hello;
I have this from my notes:
SELECT
L.SEQUENCE#,
L.FIRST_TIME,
(CASE WHEN L.NEXT_CHANGE# < P.READ_SCN THEN 'YES'WHEN L.FIRST_CHANGE# < P.APPLIED_SCN THEN 'CURRENT' ELSE 'NO' END) APPLIED
FROM
DBA_LOGSTDBY_LOG L, DBA_LOGSTDBY_PROGRESS P
ORDER BY SEQUENCE#;
Best Regards
mseberg

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 King

OK, 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

Apply CPUOCT2008 with both a physical and logical standby in place

Hello All,
I'm trying to compile a decent set of steps for applying the CPUOCT2008 patch to our production RAC cluster which has both a logical and physical standby in place. I've read a tonne of documentation, including the CPU readme, DOCID 437276.1 and 278641.1. I''ve also read through the Upgrading Databases in a Data Guard Configuration chapter of Dataguard Concepts and Administration. The last doc mentioned is really for upgrading a full version of Oracle rather than applying a CPU (at least I think that's the case). DocID 437276.1 is rather sparse on details.
I guess what I'm trying to understand is the proper method for applying the patch with the logical standby in place. The physical standby looks pretty straightforward. After running opatch on it as well, it will basically have all of the changes applied to the primary shipped over and applied as per the normal primary/standby relationship. Will the same be true for the logical (having applied the patch, and then re-enabling SQL apply)? Should I aim to have it work that way? By that I mean start it up and re-enable sql apply and then upgrade the primary. Or, am I to apply the catcpu.sql script to it as well before re-enabling the sql apply? Am I wrong in regards to the physical standby as well i.e. should the catcpu also be applied directly to it?
Thanks very much in advance.
Cheers,
Chris

Given the fact that your system is far from main-stream I'd recommend opening an SR with Oracle Support Services (metalink) and asking them.
If you would like to publish a White Paper on your experience after you have successfully completed the project let me know off-line.

DATA Guard Logical Standby v.s. Streams Apply (10gR2, rac -- rac )

Greetings -
We currently have a 3 node cluster, doing a 'Schema' capture, with a 2 node cluster serving as the apply side. Both are on 10gR2 (solaris 10)
We have been experiencing apply latency due to large transactions. The way logminer/streams evaluates the arch logs, it converts each updated row into a transaction as part of a transaction set, using 'decode (' statements.
I am under the impression a physical standby will do the same thing. But what about a logical Standby ?
(this from the Oracle Documentation)
[10g Concepts|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#SBYDB00010]
...Contains the same logical information as the production database, although the physical organization and structure of the data can be different. The logical standby database is kept synchronized with the primary database though SQL Apply, which transforms the data in the redo received from the primary database into SQL statements and then executing the SQL statements on the standby database.
Does anyone know firsthand if SQL APPLY re-issues the original sql, or if it relies on the 'decode' command as well ?
Thanks
The Nets Edge

A Physical standby does not do anything with SQL. It is running media recovery under the covers. A Logical standby uses the Logminer to read the redo, converts it to SQL and Data and applies those transactions to the Logical standby.
The both build logical change records, figure out order, dependencies etc etc and applies the transaction. Both are susceptible to long running transactions on the Primary (source) database.
Streams uses Logminer, Logical Standby use part of the Streams apply so as Mr. Morgan said, they are very similar :^)
If you are having apply performance issues you may want to look at Active data Guard.
Larry

Real-time apply cascaded logical standby database

Hi
I have a primary database orcl
Pysical standby database orcl_std
Cascaded logical standby database orcl_tri which receives archivelogs from orcl_std
Real time apply is enabled both in orcl_std (physical standby) and orcl_tri (logical standby)
When I create a table in primary orcl, I am unable to see it on orcl_tri (Although real time apply is enabled)
However, when I switch log in primary, I can see the new table on orcl_tri.
My question is, why realtime apply is not working in my scenerio ?
orcl_std : ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION USING CURRENT LOGFILE;
orcl_tri: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Oracle 11.2.0.3.0

Hi mseberg,
Thanks for your reply.
There is no load or network issue as I`ve just created these databases for the experiement.
I have the same output from standby and primary databases.
SQL> select bytes/1024/1024 from v$standby_log;
BYTES/1024/1024
             10
             10
             10I can see below output in standby alertlog
Fri Nov 16 08:39:51 2012
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
ALTER DATABASE START LOGICAL STANDBY APPLY (orcl)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Fri Nov 16 08:39:51 2012
LSP0 started with pid=37, OS id=16141
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 1953318, ResetLogScn 995548
LOGMINER: summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 1955287 (0x0000.001dd5d7)
LOGMINER: session_flag: 0x1
LOGMINER: Read buffers: 16
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=30 OS id=16145 sid=49 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=39 OS id=16149 sid=44 started
Fri Nov 16 08:39:55 2012
LOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=40 OS id=16153 sid=50 started
LOGMINER: Turning ON Log Auto Delete
LOGMINER: Begin mining logfile during commit scan for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
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 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
LOGMINER: End   mining logfile for session 1 thread 1 sequence 202, +DATA/orcl_std/archivelog/2012_11_15/thread_1_seq_202.349.799450179
Fri Nov 16 08:40:04 2012
LOGSTDBY Analyzer process AS00 started with server id=0 pid=41 OS id=16162
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS03 started with server id=3 pid=45 OS id=16175
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS04 started with server id=4 pid=46 OS id=16179
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS01 started with server id=1 pid=42 OS id=16167
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS05 started with server id=5 pid=47 OS id=16183
Fri Nov 16 08:40:05 2012
LOGSTDBY Apply process AS02 started with server id=2 pid=44 OS id=16171Do you think real-time apply wasnt setup properly ?

Sql Apply on standby stops on error

hi all,
I have run into problem I can't figure out.
There are test and production databases, for both there are logical standby databases.
For example, when materialized view is created on primary database, I see error "ORA-16226: DDL skipped due to lack of support", which is ok.
When I try to create index on test database, I got message "ORA-16227: DDL skipped due to missing object", so far OK.
However, when I try to create index on this materialized view, on production database SQL Apply stops at this point, because materialized view does not exist on standby.
Any clues why SQL apply doesn't stop on one standby but on the another standby database it stops after the same statement?
Are there any parameters or smth for this?
Thanks

yes, they are both same version and compatible parameter is the same - 11.1.0, they should be created same way on both.
only difference - prod is on solaris, test is on linux.
Problem in this case is not with mviews, but in fact, that if we have some table which is skipped and some index or other object is added on primary, SQL apply stops on standby.
Anyway, what should be the default action if SQL apply encounters an error - is it stopping apply ?

SQL apply is very slow on Logical Standby..!!

Similar Messages

Maybe you are looking for