Connecting or querying an informix database during checkpoint by using an esql/c program

Dear all, I have a with an esql/c program. During a checkpoint our esql/c programs fails to connect to database or fail to query the database. It fails to connect or query the database, because we have a time-out period which is 5 seconds. After 5 seconds the returns the calling program that it fails to query or connect to database. This condition only occurs during a checkpoint. This program is just used for inquring the database. It doesn't update a reconds. I don't know why it fails to connect or query the database during a checkpoint. There is one more problem. During a backup checkpoint time increases. again and again I don't know checkpoint time increases. We are using onstat -z followed by onstat -u, looking for any write activity. Evenif there is no write activity, the dirty buffers are increasing gradually. I don't why there is so many dirty buffers. Because there doesn't exists any write activity. There is only a backup running on the system. Any idea regarding to the above issues. Help please !!! Regards, Yener KILIC Sent via Deja.com http://www.deja.com/ Before you buy.

yener@my-deja.com wrote: > Dear all, > > I have a with an esql/c program. During a checkpoint our esql/c > programs fails to connect to database or fail to query the database. It > fails to connect or query the database, because we have a time-out > period which is 5 seconds. After 5 seconds the returns the calling > program that it fails to query or connect to database. This condition > only occurs during a checkpoint. > > This program is just used for inquring the database. It doesn't update > a reconds. I don't know why it fails to connect or query the database > during a checkpoint. > > There is one more problem. During a backup checkpoint time increases. > again and again I don't know checkpoint time increases. We are using > onstat -z followed by onstat -u, looking for any write activity. Even onstat -u is not a good indicator of write activity (it only indicatespagwrits). Use onstat -p to check on write activity at the Instance level (bufwrits, in particular). If you want to identify the sessions doing the writing, examine sysmaster:syssesprof. Rudy