ShowDoc Page 1 of 6

Bookmarks Admin Profile Feedback Sign Out Help

Headlines Knowledge Service Request Configuration Support Manager Patches & Updates Forums Certify

Knowledge Browser Advanced Search Bug Search Secure Enterprise Search

Quick Knowledge Base Go Secure Enterprise Search Advanced Saved Searches

Find

Did this article help solve your Would you recommend this document to
Select Select Submit
problem? others?

TIP: Click help for a detailed explanation of this page. Bookmark Go to End

Subject: Concurrent Managers on NT

Doc ID: Note:68993.1 Type: TROUBLESHOOTING
Last Revision Date: 03-JAN-2005 Status: PUBLISHED

CONCURRENT MANAGER ON NT
========================

This note relates to Oracle Applications Concurrent Manager running on

Windows NT server.

Although the references in this note refer to Release 11, this note can also
be used for Release 10.7 and 10.7 NCA on NT.

Creating
========
Documented in 'Release 11 for Windows NT Oracle Applications Install' manual
(Part # A57978)

The Autoinstall process will create the required registry entries automatically
for you, however you need to create the Concurrent Manager service manually,
described on page 4-20 of the install manual.

NOTE - if you use an existing <APPL_CONFIG> name, then the existing registry
entries will lost and replaced with a newly generated version.

a) You need to have rebooted your server after running autoinstall.

b) Ensure you are logged in as the Applications user account (typically 'applmgr')
c) From the command prompt run the command 'cmsrvadm add <APPL_CONFIG> manual'
where <APPL_CONFIG> is the appropriate value for the service you wish to add.
The 'manual' at the end tells NT not to start the service automatically on
the Server startup. See notes below on this subject.
d) You will be prompted to enter the username/password for the APPS schema.
e) You will be asked for the NT Domain, or press ENTER if installed on the
local machine. Be aware of the correct response here as the Concurrent
Manager will run with the privilages of the user/domain you specify here.
If you have installed Applications whilst logged in as a Domain user, then
you would normally specify the Domain name you have logged into at this
point also.
f) Finally you will be prompted to enter the password for the NT user account
you have logged in as (this should be the Applications user account - typically
'applmgr')

You may get an error at this stage either 'Internal error 2140' or 'Not able to
start service....No Logon as Service right' or similar. It is not necessarily

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007
ShowDoc Page 2 of 6

a problem at this stage. Simply check whether the service has been created or
not and if so, try starting it manually.

Problems
--------
No log on as Service Right - check User set-up to ensure they have the NT 'Log
on as a service' right. This can be checked using NT's 'User manager' utility.
Select 'Policies-->User Rights' then select 'Show Advanced User Rights' and then
select 'Log on as a service' right from the drop down list. See you Windows NT
documentation for further details.

Login problems - go into the Service's 'Startup' options in Control Panel-->Services.

Check that the 'Log on as' is set to 'This Account' and re-enter the
username and password manually. The username will normally be the Applications
user account (typically 'applmgr') if using the local account, or 'DOMAIN1/applmgr'
if using the domain user account (where DOMAIN1 is the NT Domain Name)

Removing
========
If you need to get rid of the Concurrent Manager Service, this is documented on
page A-12 of the install manual

a) Ensure the Concurrent Manager service is not running.

b) From the Command prompt, run the following 'cmsrvadm remove <APPL_CONFIG>'
where <APPL_CONFIG> is the appropriate value for the service you wish to
remove.

Starting
========
The only official, supported way of starting the Concurrent Manager is to login
to your NT server, go to control panel-->services, select the OracleConcMgr
service and click on start.

My own experience has shown that 'net start' to start the service works equally
well (i.e. - you login to the server then run
'net start OracleConcMgr<APPL_CONFIG>')

Setting the OracleConcMgr service to Automatic startup will not necessarily

work consistantly, if at all. The reason for this is that the RDBMS must be
available when the Concurrent Manager starts or it will time out and fail.
Setting startup to Automatic seems to work OK if your RDBMS is on a different
machine which is up and running before the Concurrent Manager machine is booted,
but if the RDBMS is on the same NT machine, it is unlikely to be available when
the OracleConcMgr service is looking for it. There is no easy answer to this
situation. Changing the 'DependOnService' doesn't necessarily have the desired
effect (rumours suggest this often works with Release 11 but doesnt work at all
with Release 10.7) and is not recomended. The best workaround seems to be to
have a batch file that executes the 'net start' command when the user logs in or
to convert this batch file to a service using the NT Resource kit utility srvany.
This is not supported by Oracle but may enable starting up the concurrent managers
to be automated.

An emergency way of starting the Concurrent Managers could be to manually run

the CM_<SID>.cmd batch file that is located in the %FND_TOP%\bin directory.
You must be logged in as the Applications user account (typically 'applmgr') to do
this and will need to leave a DOS session running on the Server as it isnt running
as a service. This should only be used as a last resort.

Problems
--------
Service starts with no errors, but only the Internal and Conflict managers

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007
ShowDoc Page 3 of 6

start. Check the log files for all managers, including those that have not
started, to see if there are any useful error messages that may indicate the
reason it isnt starting.

If using NTFS rather than FAT, check directory permissions on the

%APPLCSF% %LOG% and %OUT% directories. Ensure the user who is starting the
Concurrent Manager service has read/write permissions to these directories.
If in doubt, set permissions on the LOG and OUT directories to 'Everyone'
having 'Full Control'

Internal Error 2140 - can be almost anything, check the NT Event Viewer for the
actual error generated by the OracleConcMgr service. (Programs-->Administrative
Tools-->Event Viewer) Also check the Manager Log files for any errors.

Invalid login - check the Registry keys SERVICE_SID, ORACLE_SID and LOCAL
(where set) are ALL set to the TNS alias for the database (even if it is a
local database). Try connecting to the database via SQLPLUS using the
username/password from the 'sysmgr' registry key and the TNS alias from
SERVICE_SID.

No log on as Service Right - check User set-up to ensure they have the NT 'Log
on as a service' right. This can be checked using NT's 'User manager' utility.
Select 'Policies-->User Rights' then select 'Show Advanced User Rights' and then
select 'Log on as a service' right from the drop down list. See you Windows NT
documentation for further details.

Stopping
========
The recomended way of stopping Concurrent Manager is:-
1. Stop the concurrent manager (from an Apps point of view).
Either login to Applications and deactivate it, or run CONCSUB command to stop
the concurrent manager. These methods will finish processing the currently
running jobs, then stop the Concurrent Manager. (It wont process any Pending
jobs before shutting down) You can use 'terminate' instead of 'deactivate' from
the Applications screen which will stop the currently running jobs and closedown.
See 'Concsub Usage' section below for example of Concsub command.

2. Stop the concurrent manager service.

Once Applications thinks the concurrent manager is down, then issue the net stop
command or stop the service from within the Control Panel.
However make sure there are no FNDLIBR processes still running before doing
this, otherwise you may get errors when you try to restart.

In the Release 11 manuals, it states that you can stop the concurrent manager
by going straight to Control Panel-->Services, select the OracleConcMgr service
and click on stop. Although this is correct, and has the same effect as 'deactivate'
described above (in that it will stop the Concurrent Manager correctly) you have
no way of knowing what processes are running or waiting to run. The jobs that are
running at the time of the de-activate will be completed, but no other jobs in
the queue will be processed.

In a similar vein to the above, you can just use the 'net stop' command to stop
the service, however bear in mind the points raised above. To do this, run
'net stop OracleConcMgr<APPL_CONFIG>', however you may get a message saying
unable to stop processes. Use NT Task manager to monitor the Processes
running - you should see the FNDLIBR.exe and other processes gradually stop....
once the 'concmgr.exe' process has disappeared then the Concurrent Managers
have been brought down succesfully. This can take several minutes to complete
and is no quicker than the recommended method. It also uses 'deactivate' rather
than 'terminate' See 'Processes' section below for list of process names.

Another way of stopping the Concurrent Managers should be to manually run the
CS_<SID>.cmd batch file that is located in the %FND_TOP%\bin directory.
This will go through the normal processes to stop the service, however I have
yet to get this method to work succesfully. This is the batch file that is run
when the Concurrent Manager is terminated, so will run a 'deactivate' on the

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007
ShowDoc Page 4 of 6

Concurrent Managers.

A not recommended, emergency only way of stopping the Concurrent Manager is to

use the 'End Process' in the NT Task Manager, but this may not satisfactorily
clear all processes or FND database tables and may leave the system unstable.
ONLY use this method if no other method works and you have a pressing need to stop
the Concurrent Managers. Ideally you should speak to Oracle Support before doing
this, but will certainly need to after.

You will need to reboot the server before attempting to restart the Concurrent
Manager if you use this method and potentially will need to maunally update dtabase
tables, seek advise from Oracle Support.

Useful Registry Entries

=======================
WARNING
WARNING - Do not change Registry Entries lightly, as incorrectly updating the
WARNING Registry can cause your NT Server to never boot again, or your
WARNING application to not work. If you do need to make a change -
WARNING ALWAYS ENSURE YOU HAVE TAKEN A BACKUP COPY OF THE REGISTRY.
WARNING

HKEY_LOCAL_MACHINE-->Software-->Oracle-->Applications-->11.0.0--><APPL_CONFIG>

APPLLOG Format and location of the output and log files.

APPLOUT
APPLCSF
APPCPNAM

APPLPTMP Location of temporary file

APPLTMP
REPORTS25_TMP

CS_LOGFILE Name and location of the startup/shutdown scripts and logfiles

CS_CMDFILE
CM_LOGFILE
CM_CMDFILE

diag Parameters used to startup Concurrent Manager

pmon
sleep
quesiz

SERVICE_SID TNS alias for connecting to RDBMS. If LOCAL or ORACLE_SID

defined, should be same as SERVICE_SID
LOCAL
ORACLE_SID

HKEY_CURRENT_USER-->Software-->Oracle-->Applications-->11.0.0--><APPL_CONFIG>
sysmgr=apps/apps This is the login name/password that the Conc Mgr will
be using to connect to the RDBMS.
NOTE - you should check this key when logged in as the user that created the
Conc Mgr service originally.

Processes
=========
Processes can be viewed by using the NT program 'taskmgr.exe'

concmgr.exe One main process

FNDLIBR.exe One per manager using FNDLIBR library
FNDCRM.exe One for conflict resolution manager

POXCON.exe One per manager using this library

INVLIBR.exe

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007
ShowDoc Page 5 of 6

MRCLIB.exe
PALIBR.exe
ARLIBR.exe
CYQLIB.exe
INCTM.exe
OESHTM.exe
RCVOLTM.exe

CONCSUB.exe Present if running jobs via CONCSUB

F45SRV32.exe Forms Server process
F45WEB32.exe Forms runtime process. Present if users logged in.
R25RUN32.exe Report runtime process. Present if reports currently being run.
WWWLSNR30.exe Web Server Listener process. One per web listener.

Concsub usage
=============
The concsub usage for specifying start times are not particularly clear in the
manuals. The following script works OK on NT Release 11 to submit a System
Administrator responsibility report as the SYSADMIN user. Enter the CONCSUB
command line without line breaks (Unfortunality, we cannot display lines with
more than 80 characters.)

set appl_config=<ORACLE_SID>
set local=<TNS_alias>
D:\APPLR11\fnd\11.0.28\bin\CONCSUB.EXE apps/apps SYSADMIN "System
Administrator" SYSADMIN WAIT=N CONCURRENT FND <REPORT_SHORT_NAME>
START="""19-FEB-99 11:00:00"""

Yes, there really are three double quotes either side of the start time.....
this is required as there is a space between the start date and start time,
and concsub also needs the double quotes to be sent to it... If you only specify
a date, then only one set of double quotes is required. (and the job will be
scheduled for a start time of 00:00:00)

Troubleshooting
===============
In addition to the problem solving noted in the sections above, the following
points may give useful information.

General
-------
Always check the NT event viewer for additional related errors, especially the
'Application' section.

Check the CM log files for any error messages.

Try starting the Conc Mgr with the registry variable Diag=Y as this gives more
detail in the log files.

Problem cancelling requests, followed by problems restarting Concurrent Manager.

--------------------------------------------------------------------------------
If you were cancelling a request that was at 'Pending/Normal' status, and you
get an error 'FRM-40654 Record has been updated. Requery block to see change'
then you find that the process is 'Running/Normal' sometimes this causes a
locking problem.
The symptoms of the locking problem are that however often you requery the list,
the process doesnt change status from 'Running' yet when you check the server,
there are no R25RUN32.exe processes running, which would indicate that no report
is being processed.
You decide to bounce the Concurrent Manager the managers do not start and a
'ORA-1403 no data found' is shown in the CM log file.
This problem seems to be that an erronious lock is being held on the database.
The solution to this problem is either

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007
ShowDoc Page 6 of 6

(a) if you have sqlnet.expire_time set on the RDBMS server, simply shutdown
the Concurrent Manager service, wait for the Expire Time period and try
starting up again.
(b) If Expire Time is not set, either finding the lock and manually removing
it, or bouncing the RDBMS will solve the problem.

References
==========
Note 1011039.102 Adding second concurrent manager service to NT
Note 74717.1 Troubleshooting concurrent manager startup problems

Bug 766811 FNDLIBR Exception Access Violation errors

Bug 705010 Internal Conc Mgr dies after starting all Conc Mgrs.
Bug 660258 Concurrent Manager cannot terminate requests running
indefinitely
Bug 515027 'No Logon as a Service' error on Backup Domain Controller.
Bug 335049 Standard Managers dont come up unless APPLCSF is set.
Bug 636823 Internal Error re-starting concurrent manager.
Bug 615568 Running batch file through Concurrent Manager on NT

Managers.

Bookmarks Admin Profile Feedback Sign Out Help

Copyright © 2006, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

https://metalink.oracle.com/metalink/plsql/f?p=130:14:6756985800772202491::::p14_dat... 24/01/2007