Concurrent Manager pointing to singel database in RAC

Hi,
I have a situation where I need to point one of my concurrent manager to a single database instance in a RAC environment, when I run the concurrent request the concurrent manager should run and spawn the DB sessions only on one database instance, how to achive this.
Architecture
R12, 4 node rac and 4 node applications servers, full load balanced.

Please check Metalink ID:762024.1, although it is not same but might give a starting point.
Thanks,
JD

Similar Messages

Re: concurrent manager quest

Hello,
Sometimes even we kill the concurrent manager process at os level but that session still exits in the database.So now how can we verify the control code of concurrent managers in the database.Kindly tell me.
Thanks ,
928714.

Sometimes even we kill the concurrent manager process at os level but that session still exits in the database.So now how can we verify the control code of concurrent managers in the database.Kindly tell me.If you kill the CM process from the OS, you do not need to kill any concurrent manager sessions from the database.
If you terminate a concurrent request, then you can kill the database sessions (if any exist) from the database using (Concurrent Processing - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running. [ID 735119.1]).
Thanks,
Hussein

CONCURRENT MANAGER SETUP AND CONFIGURATION REQUIREMENTS IN AN 11I RAC ENVIR

제품 : AOL
작성날짜 : 2004-05-13
PURPOSE
RAC-PCP 구성에 대한 Setup 사항을 기술한 문서입니다.
PCP 구현은 CM의 workload 분산, Failover등을 목적으로 합니다.
Explanation
Failure sceniro 는 다음 3가지로 구분해 볼수 있습니다.
1. The database instance that supports the CP, Applications, and Middle-Tier
processes such as Forms, or iAS can fail.
2. The Database node server that supports the CP, Applications, and Middle-
Tier processes such as Forms, or iAS can fail.
3. The Applications/Middle-Tier server that supports the CP (and Applications)
base can fail.
아래부분은 CM,AP 구성과
CM과 GSM(Global Service Management)과의 관계를 설명하고 있습니다.
The concurrent processing tier can reside on either the Applications, Middle-
Tier, or Database Tier nodes. In a single tier configuration, non PCP
environment, a node failure will impact Concurrent Processing operations do to
any of these failure conditions. In a multi-node configuration the impact of
any these types of failures will be dependent upon what type of failure is
experienced, and how concurrent processing is distributed among the nodes in
the configuration. Parallel Concurrent Processing provides seamless failover
for a Concurrent Processing environment in the event that any of these types of
failures takes place.
In an Applications environment where the database tier utilizes Listener (
server) load balancing is implemented, and in a non-load balanced environment,
there are changes that must be made to the default configuration generated by
Autoconfig so that CP initialization, processing, and PCP functionality are
initiated properly on their respective/assigned nodes. These changes are
described in the next section - Concurrent Manager Setup and Configuration
Requirements in an 11i RAC Environment.
The current Concurrent Processing architecture with Global Service Management
consists of the following processes and communication model, where each process
is responsible for performing a specific set of routines and communicating with
parent and dependent processes.
아래 내용은 PCP환경에서 ICM, FNDSM, IM, Standard Manager의 역활을 설명하고
있습니다.
Internal Concurrent Manager (FNDLIBR process) - Communicates with the Service
Manager.
The Internal Concurrent Manager (ICM) starts, sets the number of active
processes, monitors, and terminates all other concurrent processes through
requests made to the Service Manager, including restarting any failed processes.
The ICM also starts and stops, and restarts the Service Manager for each node.
The ICM will perform process migration during an instance or node failure.
The ICM will be
active on a single node. This is also true in a PCP environment, where the ICM
will be active on at least one node at all times.
Service Manager (FNDSM process) - Communicates with the Internal Concurrent
Manager, Concurrent Manager, and non-Manager Service processes.
The Service Manager (SM) spawns, and terminates manager and service processes (
these could be Forms, or Apache Listeners, Metrics or Reports Server, and any
other process controlled through Generic Service Management). When the ICM
terminates the SM that
resides on the same node with the ICM will also terminate. The SM is ？hained?
to the ICM. The SM will only reinitialize after termination when there is a
function it needs to perform (start, or stop a process), so there may be
periods of time when the SM is not active, and this would be normal. All
processes initialized by the SM
inherit the same environment as the SM. The SM environment is set by APPSORA.
env file, and the gsmstart.sh script. The TWO_TASK used by the SM to connect
to a RAC instance must match the instance_name from GV$INSTANCE. The apps_<sid>
listener must be active on each CP node to support the SM connection to the
local instance. There
should be a Service Manager active on each node where a Concurrent or non-
Manager service process will reside.
Internal Monitor (FNDIMON process) - Communicates with the Internal Concurrent
Manager.
The Internal Monitor (IM) monitors the Internal Concurrent Manager, and
restarts any failed ICM on the local node. During a node failure in a PCP
environment the IM will restart the ICM on a surviving node (multiple ICM's may
be started on multiple nodes, but only the first ICM started will eventually
remain active, all others will gracefully terminate). There should be an
Internal Monitor defined on each node
where the ICM may migrate.
Standard Manager (FNDLIBR process) - Communicates with the Service Manager and
any client application process.
The Standard Manager is a worker process, that initiates, and executes client
requests on behalf of Applications batch, and OLTP clients.
Transaction Manager - Communicates with the Service Manager, and any user
process initiated on behalf of a Forms, or Standard Manager request. See Note:
240818.1 regarding Transaction Manager communication and setup requirements for
RAC.
Concurrent Manager Setup and Configuration Requirements in an 11i RAC
Environment
PCP를 사용하기위한 기본적인 Setup 절차를 설명하고 있습니다.
In order to set up Setup Parallel Concurrent Processing Using AutoConfig with
GSM,
follow the instructions in the 11.5.8 Oracle Applications System Administrators
Guide
under Implementing Parallel Concurrent Processing using the following steps:
1. Applications 11.5.8 and higher is configured to use GSM. Verify the
configuration on each node (see WebIV Note:165041.1).
2. On each cluster node edit the Applications Context file (<SID>.xml), that
resides in APPL_TOP/admin, to set the variable <APPLDCP oa_var="s_appldcp">
ON </APPLDCP>. It is normally set to OFF. This change should be performed
using the Context Editor.
3. Prior to regenerating the configuration, copy the existing tnsnames.ora,
listener.ora and sqlnet.ora files, where they exist, under the 8.0.6 and iAS
ORACLE_HOME locations on the each node to preserve the files (i.e./<some_
directory>/<SID>ora/$ORACLE_HOME/network/admin/<SID>/tnsnames.ora). If any of
the Applications startup scripts that reside in COMMON_TOP/admin/scripts/<SID>
have been modified also copy these to preserve the files.
4. Regenerate the configuration by running adautocfg.sh on each cluster node as
outlined in Note:165195.1.
5. After regenerating the configuration merge any changes back into the
tnsnames.ora, listener.ora and sqlnet.ora files in the network directories,
and the startup scripts in the COMMON_TOP/admin/scripts/<SID> directory.
Each nodes tnsnames.ora file must contain the aliases that exist on all
other nodes in the cluster. When merging tnsnames.ora files ensure that each
node contains all other nodes tnsnames.ora entries. This includes tns
entries for any Applications tier nodes where a concurrent request could be
initiated, or request output to be viewed.
6. In the tnsnames.ora file of each Concurrent Processing node ensure that
there is an alias that matches the instance name from GV$INSTANCE of each
Oracle instance on each RAC node in the cluster. This is required in order
for the SM to establish connectivity to the local node during startup. The
entry for the local node will be the entry that is used for the TWO_TASK in
APPSORA.env (also in the APPS<SID>_<HOSTNAME>.env file referenced in the
Applications Listener [APPS_<SID>] listener.ora file entry "envs='MYAPPSORA=<
some directory>/APPS<SID>_<HOSTNAME>.env)
on each node in the cluster (this is modified in step 12).
7. Verify that the FNDSM_<SID> entry has been added to the listener.ora file
under the 8.0.6 ORACLE_HOME/network/admin/<SID> directory. See WebiV Note:
165041.1 for instructions regarding configuring this entry. NOTE: With the
implementation of GSM the 8.0.6 Applications, and 9.2.0 Database listeners
must be active on all PCP nodes in the cluster during normal operations.
8. AutoConfig will update the database profiles and reset them for the node
from which it was last run. If necessary reset the database profiles back to
their original settings.
9. Ensure that the Applications Listener is active on each node in the cluster
where Concurrent, or Service processes will execute. On each node start the
database and Forms Server processes as required by the configuration that
has been implemented.
10. Navigate to Install > Nodes and ensure that each node is registered. Use
the node name as it appears when executing a nodename?from the Unix prompt on
the server. GSM will add the appropriate services for each node at startup.
11. Navigate to Concurrent > Manager > Define, and set up the primary and
secondary node names for all the concurrent managers according to the
desired configuration for each node workload. The Internal Concurrent
Manager should be defined on the primary PCP node only. When defining the
Internal Monitor for the secondary (target) node(s), make the primary node (
local node) assignment, and assign a secondary node designation to the
Internal Monitor, also assign a standard work shift with one process.
12. Prior to starting the Manager processes it is necessary to edit the APPSORA.
env file on each node in order to specify a TWO_TASK entry that contains
the INSTANCE_NAME parameter for the local nodes Oracle instance, in order
to bind each Manager to the local instance. This should be done regardless
of whether Listener load balancing is configured, as it will ensure the
configuration conforms to the required standards of having the TWO_TASK set
to the instance name of each node as specified in GV$INSTANCE. Start the
Concurrent Processes on their primary node(s). This is the environment
that the Service Manager passes on to each process that it initializes on
behalf of the Internal Concurrent Manager. Also make the same update to
the file referenced by the Applications Listener APPS_<SID> in the
listener.ora entry "envs='MYAPPSORA= <some directory>/APPS<SID>_<HOSTNAME>.
env" on each node.
13. Navigate to Concurrent > Manager > Administer and verify that the Service
Manager and Internal Monitor are activated on the secondary node, and any
other addititional nodes in the cluster. The Internal Monitor should not be
active on the primary cluster node.
14. Stop and restart the Concurrent Manager processes on their primary node(s),
and verify that the managers are starting on their appropriate nodes. On
the target (secondary) node in addition to any defined managers you will
see an FNDSM process (the Service Manager), along with the FNDIMON process (
Internal Monitor).
Reference Documents
Note 241370.1

What is your database version? OS?
We are using VCP suite for Planning Purpose. We are using VCP environment (12.1.3) in Decentralized structure connecting to 3 differect source environment ( consisting 11i and R12). As per the Oracle Note {RAC Configuration Setup For Running MRP Planning, APS Planning, and Data Collection Processes [ID 279156]} we have implemented RAC in our test environment to get better performance.
But after doing all the setups and concurrent programs assignment to different nodes, we are seeing huge performance issue. The Complete Collection which takes generally on an avg 180 mins in Production, is taking more than 6 hours to complete in RAC.
So I would like to get suggestion from this forum, if anyone has implemented RAC in pure VCP (decentralized) environment ? Will there be any improvement if we make our VCP Instance in RAC ?Do you PCP enabled? Can you reproduce the issue when you stop the CM?
Have you reviewed these docs?
Value Chain Planning - VCP - Implementation Notes & White Papers [ID 280052.1]
Concurrent Processing - How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration [ID 762024.1]
How to Setup and Run Data Collections [ID 145419.1]
12.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling) [ID 746824.1]
APSCHECK.sql Provides Information Needed for Diagnosing VCP and GOP Applications Issues [ID 246150.1]
Thanks,
Hussein

Concurrent manager not working on multi tier apps r12.1

Hi All,
I've created clone environment from our production environment, following details of the environment:
DB: 11.1.0.7 - 2 nodes RAC
APPS: 11.1.3 - 2 nodes
OS: LINUX 64bit
hosnames: terbdb1, terbdb2
my problem is any request immediately appear as inactive nomanager.
here's cm log file of both nodes:
TERBDB1:
========================================================================
Starting TEST_0620@TEST Internal Concurrent Manager -- shell process ID 22842
          logfile=/app1/TEST/inst/apps/TEST_terbdb1/logs/appl/conc/log/TEST_0620.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
Routine &ROUTINE has attempted to start the internal concurrent manager. The ICM is already running. Contact you system administrator for further assistance.afpdlrq r
eceived an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 20-JUN-2013 00:57:38 -
Shutting down Internal Concurrent Manager : 20-JUN-2013 00:57:38
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The TEST_0620@TEST internal concurrent manager has terminated with status 1 - giving up.
You have new mail in /var/spool/mail/applmgr
TERBDB2:
========================================================================
Starting TEST_0620@TEST Internal Concurrent Manager -- shell process ID 24424
          logfile=/app1/TEST/inst/apps/TEST_terbdb2/logs/appl/conc/log/TEST_0620.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
Internal Concurrent Manager started : 20-JUN-2013 00:53:21
+---------------------------------------------------------------------------+
                   Process monitor session started : 20-JUN-2013 00:53:21
Starting INVTMRPM Concurrent Manager               : 20-JUN-2013 00:53:21
Starting RCVOLTM Concurrent Manager                : 20-JUN-2013 00:53:21
Starting FFTM Concurrent Manager                   : 20-JUN-2013 00:53:21
Starting C_AQCT_SVC Concurrent Manager             : 20-JUN-2013 00:53:21
Starting FNDCPOPP Concurrent Manager               : 20-JUN-2013 00:53:21
Starting DownloadProcessorMigrationMode Concurrent Manager : 20-JUN-2013 00:53:22
Starting DownloadProcessorNormalMode Concurrent Manager : 20-JUN-2013 00:53:22
Starting FNDCRM Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting FNDSCH Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting AMSDMIN Concurrent Manager                : 20-JUN-2013 00:53:22
Starting OAMCOLMGR Concurrent Manager              : 20-JUN-2013 00:53:22
Starting IEU_WL_CS Concurrent Manager              : 20-JUN-2013 00:53:22
Starting PASMGR Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting IEU_SH_CS Concurrent Manager              : 20-JUN-2013 00:53:22
                     Process monitor session ended : 20-JUN-2013 00:53:22
Kindly advice.
Regards,
Ahmed

Salam Hussein,
this's output of PROD:
SQL> select concurrent_queue_name, p.node_name, db_instance
2 from fnd_concurrent_processes p, fnd_concurrent_queues q, fnd_cp_services s
3 where p.queue_application_id = q.application_id
4 and p.concurrent_queue_id = q.concurrent_queue_id
5 and q.manager_type = s.service_id
6 and p.process_status_code = 'A';
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
FNDCRM                         ERPAPP1                        MCITERP1
FNDICM                         ERPAPP1                        MCITERP1
FNDSCH                         ERPAPP1                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
RCVOLTM                        ERPAPP1                        MCITERP1
PASMGR                         ERPAPP2                        MCITERP1
INVMGR                         ERPAPP2                        MCITERP1
INVTMRPM                       ERPAPP1                        MCITERP1
WFALSNRSVC                     ERPAPP1                        MCITERP2
WFMLRSVC                       ERPAPP1                        MCITERP1
FTE_TXN_MANAGER                ERPAPP2                        MCITERP1
IEU_SH_CS                      ERPAPP1                        MCITERP1
IEU_WL_CS                      ERPAPP1                        MCITERP1
OAMCOLMGR                      ERPAPP1                        MCITERP1
FNDSM_ERPAPP2                  ERPAPP2                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
FNDSM_ERPAPP1                  ERPAPP1                        MCITERP1
WFWSSVC                        ERPAPP1                        MCITERP2
AMSDMIN                        ERPAPP1                        MCITERP1
FNDCPOPP                       ERPAPP2                        MCITERP2
FFTM                           ERPAPP1                        MCITERP1
38 rows selected.
Regards,
Ahmed

Renaming Set Code and Stage Code for a refresh set in Concurrent Manager

Hi,
We're using Oracle Applications 11.5.10.2 on a 10.2.0.4 Database:
Would anyone know how to rename the Set Code for the Refresh Set and Stage Code for the Stage for a Refresh Set in Concurrent Manager? I’ve seen it done in the two Report Sets but when I try to so it in the Report Set I’m creating, those fields are grayed out. How do I get around that?
Thanks!

950950 wrote:
Hello folks.
There is a request set that has three stages. I've got to remove the final stage but I don't seem to be able to do this.
I'm logged in with a System Administrator role and I believe we're on 11.5.10.2.
I'll keep poking around but I'm hoping one of you gurus has the information at the tip of your fingers, or could at least point me in the right direction.
Thanks,
GeorgeWhat is the error you get?
Please make sure you remove the link stages for this particulare stage (from "Link Stages" window) before you delete it from the "Define Stages" window.
Thanks,
Hussein

Where to put Concurrent Manager?

Hello,
We are currently running our production EBS (11.5.10.2) as a 2-Tier system on 32 bit Red Hat Linux. We have Web, Forms, Discoverer running on one server and Concurrent Manager, Admin and Database running on another. We will be upgrading the database server to RAC and would like to change to 64 bit.
Also we will be running multiple app servers using shared appl top. Since we cannot leave the Concurrent Manager on the database server once it is 64 bit how to best decide where to put the Concurrent Manager?
I know a couple of options are:
1) Run the Concurrent Manager on a standalone server (no redundancy).
2) Run the Concurrent Manager on 2 standalone servers using Parallel Concurrent Processing (provide redundancy but increase costs/maintenance).
3) Run the Concurrent Manager on the same servers as the Web, Forms, Discoverer using shared appl top.
I'm leaning towards option 3 but would like to hear others opinions. Could we still use PCP in this scenario? Any reasons not to do # 3?
Thanks,
Alfredo

How many servers will you be running?I believe we have 4 total available for the Application Tier. They are fairly robust servers (HP DL-580 (4 CPU each) with 24 Gig of RAM).
I have not seen PCP with Shared APPL_TOP. If you are running multiple Web, Forms, Discoverer servers, it is a good option to run them with their own APPL_TOP and run PCP with hardware based load balancing. Can we just skip PCP and run the 4 servers with Shared APPL_TOP but include everything on the Shared APPL_TOP (Web, Forms, Discoverer, Concurrent Manager)?
I'm trying to do these upgrades in phases and I'm thinking maybe we can get 2 additional servers later and implement PCP then (keeping the 4 Apps servers for Web, Forms, Discoverer).
Thanks,
Alfredo

The Internal Concurrent Manager has encountered an error.

Routine &ROUTINE has attempted to start the internal concurrent manager. The ICM is already running. Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 06-JUN-2012 00:51:22 -
Shutting down Internal Concurrent Manager : 06-JUN-2012 00:51:22
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PPD_0606@PPD internal concurrent manager has terminated with status 1 - giving up.
Edited by: sahil jain on Jun 6, 2012 10:10 PM

Hi;
1. What is EBS version?
2. Did you check:
Concurrent Managers Will Only Start on One Node in PCP/RAC Environment [ID 264296.1]
Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM [ID 245563.1]
Regard
Helios

Concurrent manager problem on Cloud

Hi
I did the clone on cloud machine.
Iam getting issues with concurrent manager.Below is the error in the log file.
establish_icm - Unable to insert ICM record
Call to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 07-MAY-2011 03:29:04 -
Shutting down Internal Concurrent Manager : 07-MAY-2011 03:29:04
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01564: ORACLE error 12899 in insert_icm_record
Cause: insert_icm_record failed due to ORA-12899: value too large for column "APPLSYS"."FND_CONCURRENT_PROCESSES"."NODE_NAME" (actual: 31, maximum: 30).
The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid2, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
sh: line 63: mail: command not found
The DEMO_0507@DEMO internal concurrent manager has terminated with status 1 - giving up.
[root@domU-12-q1-39-1A-05-F3 log]# hostname
domU-12-3q-39-1A-05-F3.compute-1.internal
SQL> select node_name from fnd_nodes;
NODE_NAME
AUTHENTICATION
RDCORACLEAPP
RDCORACLEDB
Where does this get the hostname or node name from.
Pls help.
Sree

Where does this get the hostname or node name from.From the hosts file and from the source instance that you have cloned from -- Concurrent Managers Fail To Start After New Install of Release 12 [ID 413164.1]
Please purge FND_NODES table as per (Concurrent Processing - Steps To Clean Nonexistent Nodes or IP Addresses From FND_NODES [ID 260887.1]) and after correcting all the entries in the hosts file, and check then (make sure you run AutoConfig on the database/application tier nodes).
Thanks,
Hussein

Concurrent manager log CONC-SM TNS FAIL ICM failed to start for target MSOA

Hi all,
We are doing cloning from two node PCP with loadbalancer to single node application tier.
I did preclone in database and one of the node of application,
Run adcfgclone.pl in dbTier and AppsTier everything went smooth, But the Three managers are not coming up,
1. Internel manager
2.Standar manager
3.standard manager
Thease three managers are pointing to node" Prymary node of PCP
We followed the note: 555081.1 still the issue is same
The manager logfile shows:
"Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:22
Starting STANDARD Concurrent Manager : 15-NOV-2008 21:20:22
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:23
Starting Internal Concurrent Manager Concurrent Manager : 15-NOV-2008 21:20:23
CONC-SM TNS FAIL
: ICM failed to start for target MSOAAPPL2. Review ICM log files for additional information.
Process monitor session ended : 15-NOV-2008 21:20:23"
Please help me out in resolving this
many thanks in advance..

Hi all,
Sorted out by changing the Primary node as thhe corect node and run cmclean.sql..
Now the managers are working file..
Thanks and Regards
Vasu

11i Concurrent Manager server bluescreens intermittently

We had the following configuration:
10.7character on VMS.
We upgraded to:
11.5.4 with database on VMS and middle tiers on NT boxes (conc mgr on one NT server and four other NT boxes for Forms servers).
The first 6 weeks of being on 11i, things were OK. In the last 6 weeks, however, whenever our load of concurrent requests on out NT box gets "high" (unscientific specification), the box blue screen's. Oracle support says that we should pursue Microsoft with our memory dump file from the blue screen.
Has anyone else had intermittent blue screen's of the concurrent manager server when the load on it gets high?
Thanks in advance.

Here it is
Process monitor session ended : 02-OCT-2009 07:30:04
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 02-OCT-2009 07:43:16 -
Shutting down Internal Concurrent Manager : 02-OCT-2009 07:45:56
Reviver is not enabled, not spawning a reviver process.
List of errors encountered:
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01041: internal error.
hostdef extension doesn't exist
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPSMG encountered an ORACLE error. ORA-03114: not connected
to ORACLE
Review your error messages for the cause of the error. (=<POINTER>)
_ 3 _
Routine FDPCRQ encountered an ORACLE error. ORA-03113: end-of-file on
communication channel
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01564: ORACLE error 1041 in fdudat
Cause: fdudat failed due to ORA-01041: internal error. hostdef extension doesn't exist.
The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROPTRN_1002@PROPTRN internal concurrent manager has terminated with status 1 - giving up.

SCCM 2012 R2 - Management Point deployment to untrusted domain

Hi all,
we've got two domains in our environment which have no trust relationship. I have sccm 2012 r2 installed on a Windows 2012 R2 server in the larger domain
and have just installed a DP and MP on a Windows 2008 R2 server in the second, smaller domain. The Management Point installed ok according to mpmsi.log but the problem i'm having is that the mpcontrol.log is now repeatedly throwing up the following message:
Call to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error
On the dp/mp server in the smaller domain i can browse to http://sccm-dp1/ ok. I can also browse to http://sccm-dp1/sms_mp/.sms_aut?MPCert ok. I cannot
browse to http://sccm-dp1/sms_mp/.sms_aut?MPList (receive a HTTP 500 error).
In additon to this, every now and again the MP tries to connect to the SQL DB in the other domain. This fails with the following errors:
MPStart(): RegisterWithWINS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
CMPControlManager::PublishInDNS: DnsReplaceRecordsInSet() failed with status 9002.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): PublishInDNS() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
EnableBranchCache(): configuration has not been changed.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): EnableBranchCache() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Successfully Registered for IP Address Change notifications.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
MPStart(): RegisterForIPAddressChangeNotification() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to register the SQL connection type for the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Registered connection type for SQL Server 'xxxxxxxxx' and database 'xxxx\xxx_xxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
MPStart(): RegisterSqlDatabaseConnectionType() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Checking the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04 1924 (0x0784)
Getting the CLR Enabled value from the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Attempting to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
Impersonating using the SQL connection account; user name is now 'xxxxxxxxx'.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:23:04
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to
respond.        SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** [08001][10060][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more information see SQL Server Books Online.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
*** Failed to connect to the SQL Server, connection type: MP_CONTROL_ACCESS.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get connection to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to connect to the configured SQL database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Reverting back from using the SQL connection account.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Failed to get the current CLR Enabled configuration setting for the configured SQL Server hosting the database.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CheckSqlDatabaseClrEnabled() returned 0x800720d9
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Waiting up to 300 seconds for the SMS Agent Host service to be running.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
Stopped waiting for the SMS Agent Host service to be running; Result = 0x0.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): WaitOnSmsAgentHostRunning() returned 0x0
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10
1924 (0x0784)
MPStart(): CreateThread() succeeded with id 0x2fc.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
SMS_MP_CONTROL_MANAGER successfully STARTED.
SMS_MP_CONTROL_MANAGER
01/04/2015 17:28:10 1924 (0x0784)
Can anyone provide any suggestions as to where i should begin troubleshooting this issue? When i deployed the MP to the smaller domain i ensured it
had a Management Point Connection Account which could access the SQL DB in the larger domain. I'm wondering if the two error messages i'm receiving are related or whether i have two separate issues here?
Thanks for the help!

Hi Paul,
thanks for taking the time to help. I registered asp.net v4 with IIS as per your suggestion, unfortunately it hasn't made much difference and i'm still seeing the "Call
to HttpSendRequestSync failed for port 80 with status code 500, text:Internal Server Error"
message repeating in mpcontrol.log. Have you got any further suggestions of things
to try? Seems like an error message i really need to fix!
As far as the MP to SQL issue goes, the network team assured me the connection is allowed
but i might get them to double check this just in case.
Thanks

Management Point fails after installing SCCM 2012 SP1

I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
1. Newly built Windows Server 2012 box
2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
[19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
[19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
[19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
[19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result.
Would really appreciate some help if anyone's fixed this issue

I'm still struggling, I've uninstalled MP
<04/16/14 08:06:59> SMSMP Setup Started....
<04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
<04/16/14 08:06:59> Deinstalling the SMSMP
<04/16/14 08:06:59> No versions of SMSMP are installed. Returning Success.
<04/16/14 08:06:59> ~RoleSetup().
Ran the command, Invoke-Command {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
Checked Namespace Instances to ensure '= ccm' is not longer there.
Rebooted Server and re-installed MP but it still fails
<04/16/14 08:37:26> ====================================================================
<04/16/14 08:37:26> SMSMP Setup Started....
<04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
<04/16/14 08:37:26> Installing Pre Reqs for SMSMP
<04/16/14 08:37:26> ======== Installing Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP
<04/16/14 08:37:26> Pre Req MSXML60 found.
<04/16/14 08:37:26> No versions of MSXML60 are installed. Would install new MSXML60.
<04/16/14 08:37:26> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
<04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
<04/16/14 08:37:26> Pre Req SqlNativeClient found.
<04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
<04/16/14 08:37:26> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Installing the SMSMP
<04/16/14 08:37:26> Passed OS version check.
<04/16/14 08:37:26> IIS Service is installed.
<04/16/14 08:37:26> No versions of SMSMP are installed. Installing new SMSMP.
<04/16/14 08:37:26> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE
SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04/16/14 08:37:26> mp.msi exited with return code: 1603
<04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
<04/16/14 08:37:26> ~RoleSetup().
On checking I don't seem to have anything in IIS, no default web site.
I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
Any assistance would be greatly appreciated.
Thanks

Internal concurrent manager is not up

HI
db : 11g
apps : 11.5.10.2
I found this error in internal conc mgr log file.
APP-FND-01564: ORACLE error 1 in insert_icm_record
Cause: insert_icm_record failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) violated.
The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROJ2_0907@PROJ2 internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting PROJ2_0907@PROJ2 Internal Concurrent Manager -- shell process ID 7041
logfile=/oracle/instance/proj2/proj2comn/admin/log/PROJ2_rh53vm01/PROJ2_0907.mgr
PRINTER=noprint
mailto=oracle
restart=N
diag=N
sleep=60 (default)
pmon=20 (default)
quesiz=1 (default)
establish_icm - Unable to insert ICM record
Call to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 07-SEP-2009 06:36:25 -
Shutting down Internal Concurrent Manager : 07-SEP-2009 06:36:25
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01564: ORACLE error 1 in insert_icm_record
Cause: insert_icm_record failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) violated.
The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROJ2_0907@PROJ2 internal concurrent manager has terminated with status 1 - giving up.
=============
_ 1 _
Routine AFPEIM encountered an ORACLE error. ORA-00001: unique
constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) vio.
Review your error messages for the cause of the error. (=<POINTER>)
Where as all other conc mgr are up and when i submit one conc request it completed normal.
How should i bring the ICM up?
Thanks a lot................

Hi,
Please refer to (Note: 552142.1 - Error APP-FND-01564 ORA-00001 when Starting the Concurrent Managers).
Regards,
Hussein

Issue when opening a report from concurrent manager

Hi all,
Our EBS instance worked well and stable. But two days ago, we met a strange issue as below description:
When user clicks "View Output" or "View log" from concurrent manager, they see the error in the pop-up: "Authentication failed" or "File server could not identify source file". The link in the pop-up is in "http://hostname/OA_CGI/FNDWRR.exe?temp_id=<number>" format.
After some attempts to refresh this pop-up page or close pop-up - re-click "View output" our user can see the correct output as normal. Sometimes, they click view output once and get the correct output immediately. The messages we've got is not same during these attempts, it could be authentication failed or "File server could not identify source file" randomly.
We've tried to find the solutions from metalink and from some threads in this forum but nothing can help. It's our production system.
Hope to see the solution from you
Our environment: Oracle EBS 11.5.10.2 on RHEL 4.6 32bit, Database Oracle 10.2.0.4 on RHEL 4.6 64bit

When user clicks "View Output" or "View log" from concurrent manager, they see the error in the pop-up: "Authentication failed" or "File server could not identify source file". The link in the pop-up is in "http://hostname/OA_CGI/FNDWRR.exe?temp_id=<number>" format.
Have you checked "File Server Could Not Identify Source File [ID 1073863.1]"?
After some attempts to refresh this pop-up page or close pop-up - re-click "View output" our user can see the correct output as normal. Sometimes, they click view output once and get the correct output immediately. The messages we've got is not same during these attempts, it could be authentication failed or "File server could not identify source file" randomly.Any changes have been done recently?
Can you find any errors in the CM/Database/OS log files?
Can you confirm that the concurrent requests output/log files have been generated successfully at the OS level? Does this issue happen with all concurrent requests or specific ones only?
We've tried to find the solutions from metalink and from some threads in this forum but nothing can help. What solutions have you tried?
Did you run AutoConfig?
It's our production system.For production issues, please log a SR.
Thanks,
Hussein

Concurrent Manager service cant be started

Good day
-I installed Apps 11i 11.5.0 on my PC for learning purpose , My OS is (Win XP SP2) .
-The Concurrent Manager service in windows cant be started although it was fine directly after installation ( i tried to submit request for one report and it worked ) .
-If i start the service manually it returns the error :
Error 1065 : the database specified is dose not exist .
-In the event viewer i find two errors :
Cannot connect to database (APPS/_‚ ?ٹ„‚•ٹگڈ”@VIS). ORA-error:1033.
OR
Cannot connect to database (APPS/_‚ ?ٹ„‚•ٹگڈ”@VIS). ORA-error:1017.
-I didn’t change any database password .
-I can log on to the application using (operation/welcome) .
Any idea …
Thanx in advance .
Edited by: Hassan Abazid on Jan 21, 2009 6:45 AM

Source the application env file (envshell.cmd) under %APPL_TOP%, and run the following script to remove the existing Concurrent Manager Service:
adsvcm.cmd -deinstallTo create a new Concurrent Manager Service:
adsvcm.cmd apps <appspassword>Oracle® Applications Maintenance Procedures
http://download.oracle.com/docs/cd/B11454_01/11.5.9/acrobat/11iadproc.pdf

Concurrent Manager pointing to singel database in RAC

Similar Messages

Maybe you are looking for