HPE 9000 and HPE e3000 Servers
1825541 Members
2137 Online
109681 Solutions
New Discussion

CMN_1139 ERROR accessing synchronization object

 
Zhenhao He
Occasional Contributor

CMN_1139 ERROR accessing synchronization object

Platform: HP9000 L2000 4CPU, 2G Memory

I am running Informatica (a data warehouse extraction, transformation, and loading software) to load data into an
Oracle database, which uses system resources - semphore and shared memory, I setup my kernel parameters controling semphore and shard memory according to the Informatica vendor suggestion. I encountered the following errors. Attached is the log file from Informatica session.


CMN_1010 System shared memory [11] allocated for [12000000] bytes.
CMN_1132 Semaphore [11815] created.
CMN_1569 Server Mode: [ASCII]
CMN_1570 Server Codepage: [ISO 8859-1 Western European]
TM_6151 Session Sort Order: [Binary]
TM_6050 Executing pre-session shell commands: session [s_SGF2_PR_CUSTOMER_DIMENSION]
TM_6051 Completed pre-session shell commands: session [s_SGF2_PR_CUSTOMER_DIMENSION]
Mon Mar 05 17:00:45 2001
CMN_1139 ERROR accessing synchronization object: shared memory lock failed with error [28]: No space left on device
Mon Mar 05 17:00:45 2001
CMN_1008 Internal error.
1 REPLY 1
Rita C Workman
Honored Contributor

Re: CMN_1139 ERROR accessing synchronization object

I saw this same question at the other section.
I have read and re-read your error. But I am not familiar with such error codes as CMN_1139 and haven't been able to find anything, anywhere on it. Now Oracle error codes I can check on. Does Informatica supply a listing of what these codes entail...(like ora_xxx Oracle does)??
An error saying there is not enough space, on it's own, can have a few answers.
The first thing you might do...since you said it's an Oracle DB...check your Oracles ~init.ora file and confirm that the processes being called for agree with what you've set up for semaphores. Check this thread for calc:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x10ca6af52b04d5118fef0090279cd0f9,00.html

and keep in mind, with Informatica, I am not sure what consideration you have to give to these parms for that s/w. But I will say that I have learned to be wary of vendors suggested settings on kernel parms.

Sorry I couldn't be more help,
/rcw