9 Replies Latest reply: Jul 13, 2012 6:46 AM by Chrisjenkins-Oracle RSS

    TT replication : the subscriber cannot achieve synchronization

    946042
      on timesten1:

      #ping timesten2
      timesten2 is alive

      Command> create replication wf
      > element e datastore
      > master wf on "timesten1"
      > subscriber wf on "timesten2";
      Command> call ttrepstart;

      on timesten2:

      # ttrepadmin -duplicate -from wf -host "timesten1" -uid tt -pwd tt -verbosity 2 "dsn=wf"
      10:43:28 Contacting remote main daemon at 192.163.10.72 port 53396
      10:43:28 Contacting the replication agent for WF ON TIMESTEN1 (192.163.10.72) port 48778
      10:43:28 Beginning transfer from WF ON TIMESTEN1 to WF ON TIMESTEN2
      10:43:36 Checkpoint transfer 10 percent complete
      10:43:36 Checkpoint transfer 20 percent complete
      10:43:36 Checkpoint transfer 100 percent complete
      10:43:36 Checkpoint transfer phase complete
      10:43:37 Log transfer 100 percent complete
      10:43:37 Log transfer phase complete
      10:43:38 Transfer complete
      10:43:42 Duplicate Operation Ends

      # /opt/TimesTen/tt1122/bin/ttisql wf
      Command> call ttrepstart;
      Command> select * from tt.test;
      < 1 >
      < 2 >
      < 3 >
      < 4 >
      < 5 >
      5 rows found.

      However,
      on timesten1:
      Command> delete from tt.test where id =4;
      1 row deleted.
      Command> commit;
      on timesten2:
      Command> select * from tt.test;
      < 1 >
      < 2 >
      < 3 >
      < 4 >
      < 5 >
      5 rows found.
      why the data on "timesten2" doesnot change?
        • 1. Re: TT replication : the subscriber cannot achieve synchronization
          Chrisjenkins-Oracle
          After performing the duplicate, did you start the replication agent on timesten2? The agent must be running on both stores for replication to occur. It is not started automatically by default.

          Chris
          • 2. Re: TT replication : the subscriber cannot achieve synchronization
            946042
            yes!

            # /opt/TimesTen/tt1122/bin/ttisql wf
            Command> call ttrepstart;
            • 3. Re: TT replication : the subscriber cannot achieve synchronization
              946042
              on "timesten1"

              ttmesg.log:
              13:16:57.95 Err : REP: 5864: [10, 0, noAwt] WF:transmitter.c(1784): TT12038: Could not connect to TimesTen daemon on remote host 192.163.10.34

              ps: "192.163.10.34" is the IP of the "timesten2"
              • 4. Re: TT replication : the subscriber cannot achieve synchronization
                946042
                when I try this :

                on timesten2(192.163.10.34):
                */etc/hosts*
                *192.163.10.34 timesten2 loghost*
                *192.163.10.72 timesten1*
                #ping timesten2
                timesten2 is alive
                Command> call ttrepstop;
                Command> create replication wf
                element e datastore
                master wf on "timesten1"
                subscriber wf on "timesten2";
                Command> call ttrepstart;

                on timesten1(192.163.10.72):
                */etc/hosts*
                *192.163.10.72 timesten1 loghost*
                *192.163.10.34 timesten2*

                # ttrepadmin -duplicate -from wf -host "timesten2" -uid tt -pwd tt -verbosity 2 "dsn=wf"
                17:06:57 Contacting remote main daemon at 192.163.10.34 port 53396
                17:07:02 Duplicate Operation Ends
                TT12038: Could not connect to TimesTen daemon on remote host 192.163.10.34 -- file "repDuplicate.c", lineno 2235, procedure "ExecDup"

                Then, the ttmesg.log:

                when I try this :

                on timesten2(192.163.10.34):
                #ping timesten2
                timesten2 is alive
                Command> call ttrepstop;
                Command> create replication wf
                element e datastore
                master wf on "timesten1"
                subscriber wf on "timesten2";
                Command> call ttrepstart;

                on timesten1(192.163.10.72):
                # ttrepadmin -duplicate -from wf -host "timesten2" -uid tt -pwd tt -verbosity 2 "dsn=wf"
                17:06:57 Contacting remote main daemon at 192.163.10.34 port 53396
                17:07:02 Duplicate Operation Ends
                TT12038: Could not connect to TimesTen daemon on remote host 192.163.10.34 -- file "repDuplicate.c", lineno 2235, procedure "ExecDup"

                Then, the ttmesg.log:

                17:07:11.38 Info: : 23691: maind got #33778.68576, hello: pid=13206 type=utility payload=%00%00%00%00 protocolID=TimesTen 11.2.2.2.0.tt1122 remote ident=%00%00%00%00
                17:07:11.38 Info: : 23691: Got hello from pid 13206, type utility
                17:07:11.38 Info: : 23691: Accepting incoming message from *192.163.10.96* with remote protocol (we are TimesTen 11.2.2.2.0.tt1122, they are TimesTen 11.2.2.2.0.tt1122 remote)
                17:07:11.38 Info: : 23691: 13206 ------------------: Utility program registering
                17:07:11.38 Info: : 23691: maind: done with request #33778.68576
                17:07:11.38 Info: : 23691: maind 33778: socket closed, calling recovery (last cmd was 68577)
                17:07:11.38 Info: : 23691: Starting daRecovery for 13206
                17:07:11.38 Info: : 23691: Finished daRecovery for pid 13206.

                why?
                • 5. Re: TT replication : the subscriber cannot achieve synchronization
                  Chrisjenkins-Oracle
                  Can you please provide the following information:

                  1. Run the ttVersion command on both machines and post the full output from both executions of the command.

                  2. Provide the full DSN defintion (from sys.odbc.ini) of the DSN 'wf' from both machines

                  3. Confirm that there is no firewall or other security softare that may affect connectivity between the machines.

                  Thanks,

                  Chris
                  • 6. Re: TT replication : the subscriber cannot achieve synchronization
                    946042
                    on timesten1:
                    #/opt/TimesTen/tt1122/bin/ttversion
                    TimesTen Release 11.2.2.2.0 (64 bit Solaris) (tt1122:53396) 2011-12-29T00:34:51Z
                    Instance admin: root
                    Instance home directory: /opt/TimesTen/tt1122
                    Group owner: root
                    Daemon home directory: /var/TimesTen/tt1122
                    PL/SQL enabled.

                    [wf]
                    Driver = /opt/TimesTen/tt1122/lib/libtten.so
                    DataStore=/var/TimesTen/tt1122/datastore/wf
                    DatabaseCharacterSet=ZHS16GBK

                    on timesten2:
                    bash-3.00#ttversion
                    TimesTen Release 11.2.2.2.0 (64 bit Solaris) (tt1122:53396) 2011-12-29T00:34:51Z
                    Instance admin: root
                    Instance home directory: /opt/TimesTen/tt1122
                    Group owner: root
                    Daemon home directory: /var/TimesTen/tt1122
                    PL/SQL enabled.

                    [wf]
                    Driver=/opt/TimesTen/tt1122/lib/libtten.so
                    DataStore=/var/TimesTen/tt1122/datastore/wf
                    DatabaseCharacterSet=ZHS16GBK

                    The firewall is closed.

                    bash-3.00# svcs -a |grep network |egrep "pfil|ipf"
                    disabled 6月_29 svc:/network/ipfilter:default
                    online 6月_29 svc:/network/pfil:default
                    • 7. Re: TT replication : the subscriber cannot achieve synchronization
                      Chrisjenkins-Oracle
                      Two things:

                      1. With the TimesTen daemon started on both machines, can you try to connect to the daemon port in both directions using telnet to verify connectivity:

                      From timesten1: telnet timesten2 53396
                      From timesten2: telnet timesten1 53396

                      2. I see you have installed TimesTen as 'root'. This is deprecated and is strongly discouraged. There is no valid reason nowadays why you should install/run TimesTen as root. Can you please uninstall TimesTen on both machines and re-install as a regular (non-root) user and see if that makes any difference.

                      Thanks,

                      Chris
                      • 8. Re: TT replication : the subscriber cannot achieve synchronization
                        946042
                        Thanks very much! The connectivity does have some problemes!
                        I will take your advice to install TT as another user.
                        Well, as I had installed TT as 'root', is there any impact on the performance of TimesTen? how much?
                        • 9. Re: TT replication : the subscriber cannot achieve synchronization
                          Chrisjenkins-Oracle
                          There is no performance impact related to the user who has installed TimesTen but there are several other serious impacts.

                          1. Installation / operation as root is a security risk in general for any product and should not be used unless essential.

                          2. Installing and operating TimesTen as root is deprecated (you should have received some warning at install time I believe) and will not be allowed / supported in the next release so if you start down this path now you will need to change when you upgrade.

                          3. Because of (2) we do not test this mode as much and there are some known corner case issues where some things may not work properly when installed / operated as root. You may also encounter support issues with this setup.

                          Basically, just don't do this...

                          Chris