Concurrent Manager appears FS-NCROINT FAILED error, can not start

Posted on 2009-06-22 filed under: Oracle (RSS) 29 views

The day before yesterday in the pub around the time when users encounter a problem as follows:

Concurrent Manager appears FS-NCROINT FAILED error, can not start

Concurrent Manager can not start, may I ask how to deal with?
Starting ZJPROD_0619 @ ZJPROD Internal Concurrent Manager - shell process ID 27148
logfile = / app/zjprod/zjprodcomn/admin/log/ZJPROD_erp1/ZJPROD_0619.mgr
PRINTER = noprint
mailto = applmgr
restart = N
diag = N
sleep = 60 (default)
pmon = 20 (default)
quesiz = 1 (default)
Found dead process: spid = (61548), cpid = (1113091), ORA pid = (30), manager = (0 / 1)
+------------------------------------------------- --------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
Internal Concurrent Manager started: 19-JUN-2009 10:14:27
+------------------------------------------------- --------------------------+
Process monitor session started: 19-JUN-2009 10:14:27
FS-NCROINT FAILED
Service Manager FNDSM_ERP1_ZJPROD could not initialize. The Service Manager has been unable to verify its environment and create its log file.
FS-NCROINT FAILED
Service Manager FNDSM_ERP1_ZJPROD could not initialize. The Service Manager has been unable to verify its environment and create its log file.

Thread as follows:

The problem is not so in the following sentence, the how do we solve this
The Service Manager has been unable to verify its environment and create its log file.

1 did not see the hard disk is full?
2 check folder permissions.

df-m read the hard drive is empty.
Folder did not turn over.
Host death occurred yesterday, shut down after the restart on the emergence of this fault.
Application system can log in normally, and is unable to start concurrent manager.

I have noticed that here there is a death process, the return is as follows:

Found dead process: spid = (61548), cpid = (1113091), ORA pid = (30), manager = (0 / 1)
Clear how tips are to die process
solution:
1 the closure of complicated adcmctl.sh stop apps / apps
2 ps-ef | grep FNDLIBR
3, wait a little longer and you will find a number of concurrent processes can not be turned off, and then kill -9 pid
4 ps-ef | grep FNDLIBR complicated process has been to date no
4 adcmctl.sh start apps / apps
Problem to get

Reply landlord as follows:

Oh, thank you back upstairs.
But
Found dead process: spid = (61548), cpid = (1113091), ORA pid = (30), manager = (0 / 1)
This message from time to time.
I have read some of the backup application log, this message appears frequently.
In addition, I restart the host, has died at this time but the process should be, ah, but the concurrent manager is still not start.

Metalink inquiry found that the final could be a bug

GSM this profile is enalbe? Look set to disable it?
If we can start, your version is 11.5.9 or lower? If so, congratulations to you, run into a bug
Applies to:
Oracle Application Object Library - Version: 11.5.6 to 11.5.9
This problem can occur on any platform.
Checked for relevance on 08-Aug-2007
Applications Install 11.5.6 to 11.5.9
Symptoms
After upgrading to 11.5.9 the ICM does not come up.
If GSM is disabled then the managers come up fine.
The following error is seen in the ICM log file:
Starting STANDARD Concurrent Manager: 10-MAY-2004 12:17:46
FS-NCROINT FAILED
Service Manager FNDSM_TERATIKI_iqa could not initialize. The Service Manager
has been unable to verify its environment and create its log file.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD
with library / iqa/appl3/fnd/11.5.0/bin/FNDLIBR.
Changes
Upgrade to Oracle Applications Release 11.5.9.
Cause
The cause of this problem has been identified in Bug 3263843: FNDLIBR COREDUMPS WHEN GSM IS ENABLED.
When starting the concurrent managers, a memory corruption issue was causing the Service Manager to die after trying to start the first manager. This would result in the ICM continuously trying to restart the service manager until it would also die.
Solution
1. Download and review the readme for Patch 3263843
2. Download and review any pre-requisite patches required
3. Apply Patch 3263843 plus any required pre-requisite patches to a Test environment
4. Retest the issue
5. Migrate the resolution to other instances as required.

Reply landlord as follows:

Which turns out to be a master.
Our version is 11. 5.9.
GSM can be disabled after the start.
Last year, we OAF architecture in order to install the FND have upgrade, do not know what hit the patch package has more than 3,263,843 patch, it was able to start normal.
Patch:
1. 11I.AD.I.1 4038964
2. 2917019 - New Profile Hierarchies: Security, Server and Organization
3. 3313291 - AOL JAVA ROLL UP PATCH J
4,13262919 1i.FWK.H

And he do not play these patch contains 3,263,834

If you do not have any patch had the following, you will have to hit the 3,263,843

remen From the Annex:

2009-6-22 10:04

500) this.width = 500; "border =" 0 ">

This is when he can be sure of this bug

2009.6.22

The original with the following address:

http://www.itpub.net/viewthread.php?tid=1179342&extra=&page=1