Tag Archives: FNDLIBR

After R12 Vision Installation, Concurrent Manager Not Starting

Posted by on November 11, 2009 No comments

Problem: Oracle E-Business Suite R12 was installed on appswindows3. After installation, the Concurrent Manager is not starting.

Solution: Checked Event Viewer. The following messages appear:

Restart ICM (Retries left:0)
ICM process exited with error(1)
FNDLIBR Stopped(1)

Reference:
http://forums.oracle.com/forums/thread.jspa?threadID=591003&start=15&tstart=0

Checked directory: %APPLCSF%%APPLLOG%
G:oracleVIS12instappsVIS12_appswindows3logsapplconclog>

G:oracleVIS12instappsVIS12_appswindows3logsapplconclog>type CM_VIS12_appswindows3.log

List of errors encountered:
………………………………………………………..

_ 1 _
Routine AFPCAL received a return code of failure from routine spiini.

Review your concurrent request log file for more information.
………………………………………………………..

G:oracleVIS12instappsVIS12_appswindows3logsapplconclog>

Type CM_VIS12_appswindows3.log:
Routine AFPCAL received a return code of failure from routine spiini.

To reproduce error, source apps environment and run:

FNDCPUCF apps/apps 0 Y %AD_TOP%admintemplateadctxinf.tmp

Metalink Reference:
Subject: Concurrent Manager Service Fails To Start With Error Code 1067
Doc ID: 434444.1

Cause
The issue is caused because of uninitialized string (New Value #1) in the registry under APPL_CONFIG.

The uninitialized key is causing Concurrent Managers not to come up. In the Task manager FNDLIBR.exe comes up briefly and dies.

Solution
To implement the solution, please execute the following steps:

1. Go into the registry

2. Delete uninitialized key under APPL_CONFIG

3. Retest the issue by starting concurrent manager service

Ran AutoConfig on the database tier:

The above did not work, as there was no uninitialized key under APPL_CONFIG.

Stopped all Oracle application tier services and ran AutoConfig:
cd G:oracleVIS12instappsVIS12_appswindows3adminscripts
adautocfg.cmd

[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:

[PROFILE PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: G:oracleVIS12instappsVIS12_appswindows3admininstall
afcpctx.cmd INSTE8_PRF 1

AutoConfig is exiting with status 1

Metalink Reference:
Bug No: 3815440 (AFCPCTX.CMD FAILS WHEN AUTOCONFIG IS RUN)

Subject: After Doing a Clone All the Concurrent Managers Do Not Start
Doc ID: 555081.1

Subject: After Doing a Clone All the Concurrent Managers Do Not Start
Doc ID: 555081.1

Subject: 11i : Oracle Application Object Library Concurrent Manager Setup Test
Doc ID: 200360.1

Subject: Oracle9i Application Server (9iAS) with Oracle E-Business Suite Release 11i Troubleshooting
Doc ID: 216208.1

Invalid responsibility running patch 3262159

Posted by on September 10, 2008 1 comment

Problem:

When running patch 3262159, the following message appears:

ATTENTION: All workers either have failed or are waiting:
FAILED: file FNDLIBR      on worker  1.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.
Checked adwork001.log:
/u0/oracle/prodappl/fnd/11.5.0/bin/FNDLIBR FND FNDCPBWV &ui_apps SYSADMIN 'System Administrator' SYSADMIN
List of errors encountered:
.......................................................................
_ 1 _
Please enter a valid responsibility.  The responsibility System
Administrator does not exist or is not active.  Check that the correct
application short name is specified for your responsibility.
(ROUTINE=AFPSSC)
.......................................................................
AD Worker error:
The above program failed with error code 1.
See the AD Worker log file and/or the program log file for details.

Solution:

In adctrl, used option 8 to skip the worker. Needed to disable, then enable maintenance mode. Then sourced the environment and ran:

/u0/oracle/prodappl/fnd/11.5.0/bin/FNDLIBR FND FNDCPBWV apps/apps SYSADMIN ‘System Administrator’ SYSADMIN

Reference:

Note 259319.1 – Adpatch Fails With Sysadmin Does Not Exist Or Not Active

Resolving Non-Starting Servers

Posted by on July 18, 2006 No comments

Problem: In Oracle Applications Manager, in Applications Dashboard, on the database is appearing up. The remaining servers are shown as down.

Solution:

  1. Tried stopping and restarting the entire system (stopPROD.sh and startPROD.sh).

Executing service control script:

/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adrepctl.sh stop

script returned:

****************************************************
You are running adrepctl.sh version 115.29
Reports Server for PROD is already stopped.
adrepctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmcctl.sh stop
script returned:
****************************************************
You are running adfmcctl.sh version 115.16
forms load balancing client for PROD already stopped.
adfmcctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmsctl.sh stop
script returned:
****************************************************

Subject:  Summary of Possible Reasons and Solutions for the Problem Where All Concurrent Requests Stuck in Pending Phase Doc ID:  Note:182154.1

2.  When shutting down the concurrent manager are there any FNDLIBR processes still running at the OS level?   If so, do a kill -9 on them.  Then restart the concurrent manager.

Tried this, but CM stopped successfully with no need to kill FNDLIBR.

3.  Rebuild the concurrent manager views.  As applmgr run the following from the OS:

This is non-destructive.

Concurrent Manager views can be rebuild by running the following command at the command line:

Ensure that concurrent manager is shutdown.

FNDLIBR FND FNDCPBWV apps/apps SYSADMIN 'System Administrator' SYSADMIN

Restart the concurrent manager.

Executed the above, but no change.

Executed the code:

update fnd_concurrent_queues
set control_code = 'A'
where concurrent_queue_name = 'FNDCRM';
commit;
SQL> update fnd_concurrent_queues
2  set control_code = 'A'
3  where control_code = 'N'
4  /
SQL> select control_code, target_node, concurrent_queue_name
2  from fnd_concurrent_queues
3  where control_code = 'N'
4  /
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                FNDCRM
N                                FNDSCH
N                                STANDARD
N                                PODAMGR
N                                RCVOLTM
N                                PASMGR
N                                INVMGR
N                                INVTMRPM
N                                IEU_SH_CS
N                                IEU_WL_CS
N                                OAMCOLMGR
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                OAMGCS_LINUX-BLADE

updated /etc/hosts file:

[applmgr@linux-blade etc]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain   localhost
128.x.x.x      linux-blade.domainname  linux-blade
SQL> create table fnd_concurrent_queues_vseeram
2        as select * from fnd_concurrent_queues;