Results 1 to 5 of 5
  1. #1
    Join Date
    Mar 2003
    Location
    Paris
    Posts
    1

    Unhappy Unanswered: Data replication

    I need your help/comment on an issue regarding replication. We have executed the command onstat -g dri on both primary and secondary machines. the output was...

    [informix@VTT10 inet/67]$ onstat -g dri

    Informix Dynamic Server Version 7.31.UC6 -- On-Line (Prim) -- Up 43 days 11:58:15 -- 172496
    Kbytes

    Data Replication:
    Type State Paired server Last DR CKPT (id/pg)
    primary on voms2_tli 1934 / 9292

    DRINTERVAL 10
    DRTIMEOUT 30
    DRAUTO 2
    DRLOSTFOUND /home/informix/etc/dr.lostfound

    [informix@VTT20 inet/63]$ onstat -g dri

    Informix Dynamic Server Version 7.31.UC6 -- Read-Only (Sec) -- Up 43 days 11:40:42 -- 172496
    Kbytes

    Data Replication:
    Type State Paired server Last DR CKPT (id/pg)
    secondary on voms1_tli 1460 / 8433

    DRINTERVAL 10
    DRTIMEOUT 30
    DRAUTO 2
    DRLOSTFOUND /home/informix/etc/dr.lostfound

    The checkpoint is currently 1934 on primary and 1460 on secondary, but the logical log ids seams to be consistant with each other on both VTT when you do the onstat -l....

    [informix@VTT10 inet/67]$ onstat -l

    Informix Dynamic Server Version 7.31.UC6 -- On-Line (Prim) -- Up 43 days 11:55:58 -- 172496
    Kbytes

    Physical Logging
    Buffer bufused bufsize numpages numwrits pages/io
    P-2 13 16 2314647 150409 15.39%
    phybegin physize phypos phyused %used
    200035 25000 13719 45 0.18

    Logical Logging
    Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io
    L-1 0 16 28391383 1313455 346146 21.6 3.8
    Subsystem numrecs Log Space used
    OLDRSAM 28391383 2266775216

    address number flags uniqid begin size used %used
    2152e48c 4 U-B---- 1924 2061dd 10000 10000 100.00%
    2152e4a8 5 U-B---- 1925 2088ed 10000 10000 100.00%
    2152e4c4 6 U-B---- 1926 20affd 10000 10000 100.00%
    2152e4e0 7 U-B---- 1927 20d70d 10000 10000 100.00%
    2152e4fc 8 U-B---- 1928 20fe1d 10000 10000 100.00%
    2152e518 9 U-B---- 1929 21252d 10000 10000 100.00%
    2152e534 10 U-B---- 1930 214c3d 10000 10000 100.00%
    2152e550 11 U-B---- 1931 21734d 10000 10000 100.00%
    2152e56c 12 U-B---- 1932 219a5d 10000 10000 100.00%
    2152e588 13 U-B---- 1933 21c16d 10000 10000 100.00%
    2152e5a4 14 U---C-L 1934 21e87d 10000 9304 93.04%
    2152e5c0 15 U-B---- 1923 220f8d 10000 10000 100.00%

    The question is, is this checkpoint critical?
    I tried to restore by bringing the secondary server OFF LINE then to ONLINE, but there still was no difference...
    I think the IDS is using full checkpoints instead of fussy checkpoints therefore the command onmode -c may force the checkpoint....
    Whats your opinion on this besides going through a tape backup and restore procedure?

    Thanks in advance,

    Dave

  2. #2
    Join Date
    Jan 2008
    Posts
    4

    HDR replication issue

    Hello There,

    This is my first post, I am also having the same issue. The HDR is ON on both Primary and secondary servers but the log id/ Check point id is lagging behind on the secondary server.

    What are the effects of this and How can I correct it apart from a 0 level restore on secondary??

    Thanks.

    Rajesh.

  3. #3
    Join Date
    Jun 2005
    Location
    Santa Fe, Argentina
    Posts
    27
    Hi, in HDR, the engine don´t use fuzzy checkpoint, may be in IDS 11...

    They are some I/O activity on the secondary?

  4. #4
    Join Date
    Jan 2008
    Posts
    4
    Hi

    Thanks for replying, I am sorry I didn't get you completely. There may be some I/O activity on the secondary as the secondary is read only and some large queries being run on the secondary to extract data.

    But the question is, does this means that replication is not proper or the data differs between primary and secondary? what are the other effects of this??? And is there any way to resolve this??

  5. #5
    Join Date
    Jun 2005
    Location
    Santa Fe, Argentina
    Posts
    27
    if the data is not sync, then they differ from the primary to the secondary. you must have the same log/checkpoint, see DRINTERVAL too. Sorry, my english is very basic...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •