Oninit cdi / Archive
Talk to an expert →

Why the command "set lock mode to wait 5" can't work?

Posted in 1999

Topics: Networking & sqlhosts Configuration

Liu Jiachuan — — source: Informix-list mailing list archive (1991-1998)

Hi,everybody. I need your help for my question. I have a process which is running on a host. It will access local data and remote data on on another host. When it startup, it open the local database, and only when it exit, it will close the local database. This afternoon when it access remote data, it report error 908(attemp to connect remote system failed), and then it wait at that point, it doesn't continue as if it is dead, but the process is still exist by using "ps" command. Finally the only way for me to kill it, and the result of kill is successful.I don't know why. And I have set it's lock mode to wait(SQL statement "set lock mode to wait 5"). Have you ever meet with this error? If so, could you tell me why and how to settle this problem? My running environment is: OS platform is SCO unix 3.2Release 5.0.4, and the Informix is 7.22.UC3. Local database and remote database are all accessed by TCP/IP means. Wait for your help.

↪ replying to Liu Jiachuan
M00n321 — — source: Informix-list mailing list archive (1991-1998)

> I have a process which is running on a host. It will access local data >and remote data on on another host. When it startup, it open the local >database, and only when it exit, it will close the local database. This >afternoon when it access remote data, it report error 908(attemp to connect >remote system failed), and then it wait at that point, it doesn't continue >as if it is dead, but the process is still exist by using "ps" command. >Finally the only way for me to kill it, and the result of kill is >successful.I don't know why. And I have set it's lock mode to wait(SQL >statement "set lock mode to wait 5"). Have you ever meet with this error? >If so, could you tell me why and how to settle this problem? Look to the error checking in your application. The failure to connect will cause any subsequent attempt to access the remote data to also generate an error. If you do not halt the execution when such an error occurs it will continue to spin its wheels unproductively - a 'sunny day' program. None of this has much to do with lock mode however as you aren't even getting to the database let alone the data.