Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2002
    Posts
    2

    Unanswered: How to arrest ATS File Generation?

    We have 2 database servers using INFORMIX version 9.30.UC1, physically loacted at 2 different places. And...replication is set between these 2 servers.

    Whenever any transaction fails during replication, ATS files get generated. We recently noticed that one particular type of ATS file, with sql code:0 and ISAM code:154, get created very often. As a result,we are manually fixing the replication stuffs, for those transactions.

    The ISAM code:154 talks about the distributed deadlock. The CDR_DSLOCKWAIT configuration parameter specifies the number of
    seconds the data synchronization component waits for database locks to be released. The default was set to 5 seconds and we increased it to 10 seconds, so that the transactions will not fail during replication. But , its of no help.
    Still we get to see ATS files with that ISAM code.

    Am I missing anything important in the analysis? Should I try re-configuring any other parameters?

  2. #2
    Join Date
    Dec 2002
    Location
    Pakistan
    Posts
    31

    Re: How to arrest ATS File Generation?

    Are both servers on LAN OR WAN?
    How you are sync time between two servers (As ER required)?



    Originally posted by BDN
    We have 2 database servers using INFORMIX version 9.30.UC1, physically loacted at 2 different places. And...replication is set between these 2 servers.

    Whenever any transaction fails during replication, ATS files get generated. We recently noticed that one particular type of ATS file, with sql code:0 and ISAM code:154, get created very often. As a result,we are manually fixing the replication stuffs, for those transactions.

    The ISAM code:154 talks about the distributed deadlock. The CDR_DSLOCKWAIT configuration parameter specifies the number of
    seconds the data synchronization component waits for database locks to be released. The default was set to 5 seconds and we increased it to 10 seconds, so that the transactions will not fail during replication. But , its of no help.
    Still we get to see ATS files with that ISAM code.

    Am I missing anything important in the analysis? Should I try re-configuring any other parameters?

  3. #3
    Join Date
    Aug 2002
    Location
    Belgium
    Posts
    534
    Maybe you could try the latest version: IDS.9.30.UC4. Just came out.
    Lots of ER stuff fixed.
    rws

Posting Permissions

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