5 Replies Latest reply: Feb 19, 2014 5:16 AM by Partha Sarathy S RSS

    Replicate timing differ from source

    Sami

      Hi All,

       

      Currently am replicating both DDL & DML from source database to target database. which has 1 extract, 1 datadump at source and 1 Both operations are working fine.

      But there is time difference in replicate, Both machine timing are same. detail log follows

       

      Extract log from source:

       

      
      TABLEWildcard  resolved (entry RUBIKONDEV.*):
        TABLE RUBIKONDEV.ENTITY;
      Using the following key columns for source table RUBIKONDEV.ENTITY: ENTITY_ID.
                       129 records processed as of 2014-02-19 11:59:38 (rate 0,delta 0)
      
      

       

      Replicate log from target :

       

      Using the following key columns for target table RUBIKONDEV.ENTITY: ENTITY_ID.
      129 records processed as of 2014-02-19 11:59:47 (rate 0,delta 0)
      

       

      from above log we can able to see that there was 9 Seconds difference between extract & replicate.

       

      Is it 9 seconds difference will be oaky? or will it be performance problem? If it is performance problem what should i check.

       

      Thanks & Regards

      Sami

        • 1. Re: Replicate timing differ from source
          onkar.nath

          it is fine. sometimes in our production replicat lag behind few hours because of heavy transaction rate but then it catches up.

           

          Onkar

          • 2. Re: Replicate timing differ from source
            Partha Sarathy S

            It depends on your network strength. It is not an issue as onkar said it may catch up later compromising the lag

            • 3. Re: Replicate timing differ from source
              Sami

              Hi All,

               

              Thanks for your replies,

               

              Parth272025 wrote:

               

              It depends on your network strength. It is not an issue as onkar said it may catch up later compromising the lag

               

              How do i check the network strength, being its my local network with 100 mbps by default.

               

              @onkar:

               

              it is fine. sometimes in our production replicat lag behind few hours because of heavy transaction rate but then it catches up.


              I need to immediate replicate from source to target...


              If there is lag. what are all the parameter I need to check for performance improvement.


              Thanks& Regards

              Sami

              • 4. Re: Replicate timing differ from source
                onkar.nath

                Sami,

                 

                I dont think there is much you can do. Generally, GG replicats the data in near to real time and lag is really near to zero but Parth said, if network is busy or slow then replicat will lag behind. If there is no queue of transactions to be replicated then your transactions will appear in target almost at the same time when it is committed in source.

                 

                Onkar

                • 5. Re: Replicate timing differ from source
                  Partha Sarathy S

                  Hi another way possible is, you can split the range of data being processed like if instead of a single replicat processing 5,00,000 records, you can create multiple replicats(say 5 for example) to process parallely which can improve performance. But if it is due to network traffic, then you cannot do anything on it.