Inactive no manager in oracle apps R12.2.4

concurrent requests show inactive no manager





Solution:-


sqlplus apps/apps

sql>exec fnd_conc_clone.setup_clean;

PL/SQL procedure successfully completed.

sql>commit;

Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers to repopulate the required system tables.

DB_Tier:-
[ora@chintels PREPROD_chintels]$ ./adautocfg.sh apps

[applmgr@sujeet~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@sujeet scripts]$ ./adautocfg.sh apps

sql>@/u02/cmclean.sql

Started the concurrent manager on the application tier and it worked

Check Node name:-
SQL> select node_name, node_mode, support_cp, support_web, support_admin,support_forms from FND_NODES;

Check CM Status:-
[applmgr@sujeet ~]$ ps -ef |grep FNDLIBR

503      24327 24321  0 12:09 pts/1    00:00:02 FNDLIBR                        
503      24679 24493  0 12:09 ?        00:00:00 FNDLIBR                                                                                                        
503      24683 24493  0 12:09 ?        00:00:00 FNDLIBR   

How to clean FND_NODES table

How to clean FND_NODES table in R12.2.4
Step 1:   
Always apply the latest cloning patches to avoid all the bugs and fixes
Step 2:  
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
It will delete all old data from the table.
Step 3:  
Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers to repopulate the required system tables.

NOTE:-

fnd_conc_clone.setup_clean & cmclean.sql scripts detailed below.

fnd_conc_clone.setup_clean

fnd_conc_clone  ===> is package
setup_clean ====> it is procedure name
When we run fnd_conc_clone.setup_clean it deletes the information from the below tables.
Delete from fnd_concurrent_queue_size
Delete from fnd_concurrent_queues_tl
Delete from fnd_concurrent_queuesDelete from fnd_nodes;

We use fnd_conc_clone.setup_clean to cleanup fnd_nodes table in the target to clear source node information as part of cloning.

below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
First run the autoconfig on DB tier and middle tier this will regiser the nodes in fnd_nodes tables.

cmclean.sql

If we stop conc manager using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.
To cleanup running and pending requests we use cmclean.sql this script will update the below tables.
UPDATE fnd_concurrent_processes
UPDATE fnd_concurrent_queues
UPDATE fnd_concurrent_requests
UPDATE fnd_conflicts_domain
UPDATE fnd_concurrent_conflict_sets
Download cmclean.sql: 


Concurrent Processing - cmclean.sql - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
Note: cmclean.sql and fnd_conc_clone.setup_clean touch different set of concurrent request tables.
Its better idea to run both during the clone. 

While Running AutoConfig, txkSetConfig.pl Failed

While Running AutoConfig, txkSetConfig.pl Failed (Doc ID 374135.1)


APPLIES TO:

Oracle Applications Manager - Version: 11.5.8 to 11.5.10.2 - Release: 11.5 to 11.5
Information in this document applies to any platform.


SYMPTOMS

On 11.5.8, while running autoconfig, the program txkSetConfig.pl failed with the following error.



Error :

[ Config tool : /oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl ]
Command: /oracle/HRT/hrtora/iAS/Apache/perl/bin/perl -I
/oracle/HRT/hrtora/iAS/Apache/perl/lib/5.00503:/oracle/HRT/hrtora/iAS/Apache/perl/lib/site_perl/5.00
5:/oracle/HRT/hrtappl/au/11.5.0/perl
/oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl
contextfile=/oracle/HRT/hrtappl/admin/HRT_cacsdb2.xml /oracle/HRT/hrtappl/au/11.5.0/perl
OAMJAVASPACE JDK DISCO XMLParser

Action : 
execute

SCRIPT RETURNED:
Configuring OAMJAVASPACE settings ...
Configuring JDK settings ...
Configuring DISCO settings ...
Configuring XMLParser settings ...
Configuring MOVEJSPPAGEREPOS settings ...
/oracle/HRT/hrtcomn/_pages directory exists. No further action required.
ERRORCODE = 1 ERRORCODE_END

.end std out.
java was not found in /oracle/HRT/hrtcomn/util/jre/1.1.8/bin/../bin/i686/green_threads/java
*******FATAL ERROR*******
PROGRAM : (/oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl)
TIME: Mon Jun 5 10:57:07 2006
FUNCTION: [ Level 1 ]
ERRORMSG: *******FATAL ERROR*******
PROGRAM : (/oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl)
TIME: Mon Jun 5 10:57:07 2006
FUNCTION: TXK::Process::run [ Level 3 ]
MESSAGES:
Command error: <rc> = 256, <command> = /oracle/HRT/hrtcomn/util/jre/1.1.8/bin/java -Xmx256M
-classpath
/oracle/HRT/hrtcomn/util/jre/1.1.8/lib/rt.jar:/oracle/HRT/hrtcomn/java:/oracle/HRT/hrtcomn/java/apps
.zip:/oracle/HRT/hrtappl/ad/11.5.0/java/adconfig.zip:/oracle/HRT/hrtcomn/java/appsborg.zip
oracle.apps.ad.context.UpdateContext /oracle/HRT/hrtappl/admin/HRT_cacsdb2.xml s_oamname_space
oracle.apps.fnd.oam


STACK TRACE
TXK::Error::abort('TXK::Error', 'HASH(0x816b11c)') called at
/oracle/HRT/hrtappl/au/11.5.0/perl/TXK/Common.pm line 299
TXK::Common::doError('TXK::Process=HASH(0x847328c)', 'Command error: <rc> = 256, <command> =
/oracle/HRT/hrtcomn/util/...', undef) called at /oracle/HRT/hrtappl/au/11.5.0/perl/TXK/Common.pm
line 314
TXK::Common::setError('TXK::Process=HASH(0x847328c)', 'Command error: <rc> = 256, <command> =
/oracle/HRT/hrtcomn/util/...') called at /oracle/HRT/hrtappl/au/11.5.0/perl/TXK/Process.pm line 434
TXK::Process::run('TXK::Process=HASH(0x847328c)', 'HASH(0x80cf198)') called at
/oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl line 173
main::updateContext('s_oamname_space', 'oracle.apps.fnd.oam') called at
/oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl line 418
main::OAMJAVASPACE called at /oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl line 89
eval {...} called at /oracle/HRT/hrtappl/fnd/11.5.0/patch/115/bin/txkSetConfig.pl line 87

CAUSE

According to Oracle MetaLink Note 130091.1 and Bug 3938217 (This bug is internal) TXKSETCONFIG.PL FAILS WITH JDK 1.1.8.  The JDK 1.3 should be used instead of JDK 1.1.8.

SOLUTION

To implement the solution, please execute the following steps:

1.Use java from the JDK_TOP 1.3

Change the JRE_TOP in application tier Context File as below:
Replace <JRE_TOP oa_var="s_jretop">$COMMON_TOP/util/jre/1.1.8</JRE_TOP>
with       <JRE_TOP oa_var="s_jretop">replace here with JDK_TOP </JRE_TOP>

2.Run Autoconfig.

Internal Concurrent Manager has Terminated with status 139 giving up


Internal Concurrent Manager has Terminated with status 139 giving up (Doc ID 223761.1)

Apps: R12.1.3
OS: OEL6.5
symptom: Segmentation Fault starting Concurrent Managers
symptom: adcmctl.sh fails
symptom: Internal Concurrent Manager has Terminated with status 139 giving 
up
symptom: Segmentation Fault - core dumped
change: Cloned instance
cause: Unix patches were applied on the system



Solution:

Down CM after that run cmclean.sql scripts.

GET CMCLEAN SCRIPT FROM ORACLE NOTEID:
Concurrent Processing – cmclean.sql – Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]

Down the Application

Run apps enviorment

Connect to sqlplus

Sql>@cmclean

Type dual to Continue

start CM.

OR

Relink of all FND executables.
1) Logon as applmgr

2) Set your application environment

3) run the following command

[applmgr@sujeet ~]$ cd /u02/apps/fs1/EBSapps/appl/ad/12.0.0/bin

[applmgr@sujeet ~]$ adrelink.sh force= y ranlib=y "FND all"

4) Start concurrent managers.
adcmctl.sh

APP-FND-00204

RCVOLTM Fails with Error APP-FND-204 (Doc ID 311884.1)





SYMPTOMS

Unable to perform receipts due to error:

APP-FND-204 Concurrent Manager encountered an error while running the spawned concurrent program Receiving Transaction Manager - RCVOLTM for your concurrent request XXXXXX. TM-SVC LOCK HANDLE FAILED

RCV: Processing Mode is Online  (problem occurs in ONLINE mode)
The problem happens with any type of routing and any type of receiving document.

CAUSE

This is happening because of large number of receiving processes being spawned at the same time.

Check the number of process running for the RCVOLTM. If  the number of  Running and Max processes are the same, this means the Max number of processes are reached and issue will occur.

SOLUTION

Increase the Max number of processes associated with the receiving transaction manager.

Navigation:

  System Administrator (or comparable) Responsibility > Concurrent > Manager > Define
  Query for Manager='Receiving Transaction Manager'
  Click Work Shifts button and review value in Processes field

ORA-01400

Autoconfig errors on adgentns.pl ORA-01400: cannot insert NULL into
FND_APPS_SYSTEM.CSI_NUMBER (Doc ID 1209823.1)


CAUSE

A null value for parameter s_systemcsi in APPS Context XML File This makes autoconfig script
to insert NULL value to ("APPLSYS"."FND_APPS_SYSTEM"."CSI_NUMBER") generating the error message : ORA-01400: cannot insert NULL into ("APPLSYS"."FND_APPS_SYSTEM"."CSI_NUMBER")


SOLUTION

To implement the solution, please execute the following steps:

1. Source the APPS Tier environment file $APPL_TOP/APPS_.env.
2. Backup the APPS Tier Context File
3. Edit APPS Tier tier context XML file,

Replace:
<AFSYSCSI oa_var="s_systemcsi"/>

With:
<AFSYSCSI oa_var="s_systemcsi">0</AFSYSCSI>

4. Save the changes.
5. Run autoconfig to re-test the issue.

This record cannot be reserved for update. It has already been reserved by another user





Solution:-

First login with apps user after that find lock on table level.

SQL>  select
   c.owner,
   c.object_name,
   c.object_type,
   b.sid,
   b.serial#,
   b.status,
   b.osuser,
   b.machine
from
   v$locked_object a ,
   v$session b,
   dba_objects c
where
   b.sid = a.session_id
and
   a.object_id = c.object_id;


OWNER                          OBJECT_NAME                                                                                                                   O   BJECT_TYPE                 SID    SERIAL# STATUS   OSUSER                         MACHINE
------------------------------ -------------------------------------------------------------------------------------------------------------------------------   - ------------------- ---------- ---------- -------- ------------------------------ ----------------------------------------------------------------
APPLSYS                        FND_CONCURRENT_REQUESTS                                                                                                       T   ABLE                       768         27 INACTIVE applmgr                   sujeet.oracle.com
PO                             PO_DISTRIBUTIONS_ALL                                                                                                          T   ABLE                       821      11141 ACTIVE   applmgr                   sujeet.oracle.com

18 rows selected.

In my case i am going to kill below lock.

SQL> alter system kill session '821,11141';

System altered.

Issue resolved check and try again..





ERROR 1396 (HY000): Operation ALTER USER failed for 'Mysql'@'%'

 This MySQL error — ERROR 1396 (HY000): Operation ALTER USER failed for 'Mysql'@'%' — means that MySQL cannot find the user ...