Arssockd process is automatically terminated with remote DB

[swat_is_back]

I have a remote oracle database, the thing that I observed that when ever there is a database connection glitch the arssockd process terminates automatically.
Is this a new feature with 9.0 version?older version 8.4 searies were not killing the arssockd process.
Is there any setting to avoid that? 

Appreciate your response.

Thanks,
Swat

[kbsiva]

Hi -  Did you check this post?

http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21474367

Thanks
Siva

[Justin Derrick]

I always recommend the database be kept on the local machine to reduce the number of 'moving parts' that can cause these sorts of issues.  By having the database live on a remote server you add risk in the following ways:

• Higher latency / lower performance
• Outages due to network outages
• Outages due to router configuration changes
• Doubling the chance of a hardware failure
• Contention for Disk I/O with other I/O heavy apps
• CMOD Table corruption due to connectivity issues inbetween transactions

I'm sure others could come up with more reasons...  But these are the biggest risks I can think of.  Consider getting an exception to the 'remote database' rule if that's possible.