CANT MAKE TEMP CONNECTION, ORA:12516 and dm_bear_trap: Unexpected exception, (SIGSEGV: segmentation

aaisupport

Hi Experts,

I am getting the below error in  docbase log file .

Error: dm_bear_trap: Unexpected exception, (SIGSEGV: segmentation violation: (11) at (Connection Failure)),  during new session creation in module dmapply.cxx after line 492.  Process exiting.
Fri Feb 25 16:15:06 2011 472258 [DM_SESSION_E_CANT_MAKE_TEMP_CONNECTION]error:  "Could not establish an internal, temporary database connection (database_name = , docbase_owner = AAICMS, connection_string = AAIDB); database system error was: ORA-12516: TNS:listener could not find available handler with matching protocol stack.

PID(29044) failure during processing of request: NewSessionByAddr_string.

Current Session ID: 01003039802bcb7f
Last SQL statement executed by DB was:

My findings are :

One of possible reason you have received the error message, DM_SESSION_E_CANT_MAKE_TEMP_CONNECTION, is that the number of available Oracle processes is not enough. Increasing

MAX number of Oracle process helps correct this problem. Below is a sample of the error message that will appear in the server log.

in my server.ini number of concurrent_sessions are; 250.

Do I have to increase or double the number in init.ora or i have to increase th e number of processes in oracle.Number of processes could be inceresed through init.ora or we have to do something else.

For the segmentation error :I have read the below link but not able to find the current session_id.log  file in my documentum/dba/log directory.

https://solutions.emc.com/emcsolutionview.asp?id=esg96476

Kindly suggest ...

Regards,

Neelesh

agboan

Neelesh

Is your SIGSEGV in the content server log only occuring when you have a high load? If so, then yes, you can look to increase the number of allowable connections in Oracle. A single content server session generally uses 2 Database connections (sessions with data dictionary may use up to 3), so you want to have your Oracle to handle 2.5 * the number of allowed content server sessions.

ORA-12516 is error TNS-12516 occuring intermittently in the clients. This is because the listener, which relies on Automatic Instance Registration (or AIR) for configuring the services the listener should listen for, gets a lot of client requests and thus runs out of handles to open with the dbserver and hence this error.

Action Points :

1.) As a Fix increase the value for PROCESSES in the init<SID>.ora file of the instance.

2.) You can have static registration for this instance by having a SID_LIST in the listener.ora file in addition to the automatic instance registration.