3 Replies Latest reply: Apr 17, 2011 10:25 AM by Khalid-Oracle RSS

    Latency apply for Streams Process APPLY_STREAM exceeds the thresholds set

    835233
      Hi,

      Apply process is working, but it shows error in enterprise manager that *"Latency apply for Streams Process APPLY_STREAM exceeds the thresholds set"*

      i have changed parallelism to 5 and commit_serialization to FULL. but still error remains.

      how to resolve the error?

      can any tell me what is the problem in apply process. am i need to change the parameter.


      urgent!!!!!!


      please
        • 1. Re: Latency apply for Streams Process APPLY_STREAM exceeds the thresholds set
          734707
          It is not saying there is an error, it is just saying your apply site is slow.
          Tune the apply site, look for full table scan or any other reason why your machine is slow.
          If you don't know what to do, browse this forum.
          The question arise quite often and I posted guidelines and queries to sort it out.
          • 2. Re: Latency apply for Streams Process APPLY_STREAM exceeds the thresholds set
            Usman.M
            Hi!


            Can you please specify the Following.

            1-streams pool size of Database where capture process is running.
            2-Redo logs size of both Source database and Target Database.
            3-Are you using Local Capture or Downstream Capture.
            4-Real time or Achived-log


            Regards
            Usman
            • 3. Re: Latency apply for Streams Process APPLY_STREAM exceeds the thresholds set
              Khalid-Oracle
              You can tune your apply server by tracing on the apply process. To do this: identify the PID (Process ID)

              APPLY SERVER:
              select SID from V$STREAMS_APPLY_SERVER;


              With above SIDs, query V$PROCESS to get the PIDs:

              select a.pid, b.sid
              from v$process a, v$session b
              where a.addr=b.paddr and b.sid in(the list of sids from above);

              With the PIDs found:
              $ sqlplus /nolog
              connect / as sysdba
              oradebug setorapid <PID>
              oradebug unlimit
              oradebug Event 10046 trace name context forever, level 12
              wait for 10-15 mins
              oradebug tracefile_name -- gives pathname / filename to file being written to
              oradebug Event 10046 trace name context off

              run TKPROF on trace file
              you may have to add some indexes on your tables . If possible, each table for which changes are applied by an apply process should have a primary key.
              read more in

              http://download.oracle.com/docs/cd/B19306_01/server.102/b14228/gen_rep.htm
              Section Substitute Key Columns

              Edited by: user596799 on Apr 17, 2011 8:24 AM