Getting dm_connect_failed Error After Timos Installation
(Doc ID 1296310.1)
Last updated on AUGUST 17, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
After installation of TIMOS no calls are accepted (through the AAAGw-CM-DM-DMTIMOS chain), giving "dm_connect_failed" error, with the following error messages reported in timos.log:
03.02.2011 20:23:00 xxxx dm_timos DMT NORMAL [T:6] 00527 - (timosMgr.TimosDataManager.AcceptorPool.NetworkListener) Info for High Availability: 'Accept client connection<60000000034cdc70>'
03.02.2011 20:23:00 xxxx dm_timos DMT NORMAL [T:12] 00527 - (timosMgr.TimosDataManager.ConnectorPool.NetworkListener) Info for High Availability: 'Connect to my.wi-tribe.pk:12950 succeeded.'
03.02.2011 20:23:01 xxxx dm_timos DMT NORMAL [T:1] 00000 - (timosMgr) INF_SYSTEM_SHUTDOWN
A similar issue is also described in <Note 565550.1> too, where it's suggested to review the process size limit set at the OS level (maxdsiz_64, on an HP-UX Itanium OS), by providing a size which fits the largest expected process size.
Below is the snapshot of the system memory:
Active VM: 4.1gb Buf Cache: 0mb Free Mem: 13.3gb FileCache: 4.5gb
Actual RAM SIZE of the server: 32GB
Current Free Mem : 13GB.
Below is the current value of maxdsiz_64bit parameter. 30 -45 Calls expected per minute.
maxdsiz_64bit Dynamic 2147483648 2147483648 4294967296
A suggestion is needed to fine tune this parameter.
TIMOS crashed after less than 10 minutes run time during the deployment. Even if we assume 30 calls per minute, that’s less than 300 calls before the crash. How TIMOS process can allocate 2 GB of physical memory for just 300 calls?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!