Cron Job Fails to Stop Oracle concurrent manager

[Clint Gibler]

We have an older HP-UX 10.20 server that runs a cronjob every night to shutdown our oracle concurrent managers for the nightly backup and it has worked successfully for several years. We recently performed a minor upgrade and the name of the concurrent manager has changed so the script it runs has changed. Now all I did was change the name of the script the crontab runs to the name of the new script, there isn't any difference in this script other than the names from the other concurrent manager we shutdown and if you run the script manually it works fine but when the crontab runs the same script it gives errors in the log and doesn't shutdown the concurrent manager. Any ideas why?

[Patrick Wallek]

What errors does it give?

The first thing that springs to mind is something with the environment. Some varialbe may not be set quite right for the "new" concurrent manager.

Posting the errors and the script(s) you use would help us to determine what is happening.

[Clint Gibler]

This is the error message in the log

APP-01055 Concurrent Manager cannot connect to database
Previous Messages (for Support Purposes)
APP-00988 ORACLE error 12162 in fducsq

and this is the script

#export ORACLE_SID=CRP8
export ORACLE_HOME=/u01/oracle/product/7.3.4
export PATH=/usr/bin:/usr/ccs/bin:/usr/sbin:.:/usr/local/bin:/usr/contrib/bin:/o
pt/upgrade/bin:/opt/lrom/bin:/opt/hpnp//bin:/:/u01/oracle/local:/u01/oracle/prod
uct/7.3.4/bin:/u10/applmgr/10.7/fnd/6.1.1/bin:/u10/applmgr/10.7/ad/2.3.19/bin
#ORAENV_ASK=NO
#. /usr/local/bin/oraenv
ORAENV_ASK=YES
export ORACLE_SID=
. /u10/applmgr/10.7/APPCRP8.env
$FND_TOP/bin/CONCSUB apps/apps SYSADMIN 'System Administrator' SYSADMIN CONCURRE
NT FND DEACTIVATE

[Warren_9]

Hi,

is the script run fine in normal shell?

If the script run fine in oracle user, it probably is some env setting problem.

also you can try to put to job in the cron of root

"su - oracle -c [script] "

GOOD LUCK!

[Joseph Loo]

hi clint,

not sure if u have amended the paasword to APPS or APPLSYS?

from your reply, it seems the APPS password is still the default, i.e. APPS.

regards.

[Joseph Loo]

hi,

also, r u now running Release 10.7?

if so, i came across something in Oracle Metalink (Note:2087268.6) which describes your problem:

This problem occurs when the NLS_LANG variable is set to AMERICAN as an environment variable and not in the APPLSYS.env file.

When not defined in the APPLSYS.env, the value for the NLS_LANG will default to 'Undefined' and override the environment variable that is set.

The solution is to remove the NLS_LANG variable as well as the "export NLS_LANG" from the APPLSYS.env or set the value to AMERICAN, then re-run the environment file.

Now, the client should be able to start the concurrent managers using startmgr.

regards.