Difference between cmclean.sql and fnd_conc_clone.setup_clean


fnd_conc_clone.setup_clean:

fnd_conc_clone is the package name

setup_clean is procedure name

After clone we must need to run the fnd_conc_clone.setup_clean script

It will be clear the below tables in target node information in to source node table

fnd_concurrent_queue_size
fnd_concurrent_queues_tl
fnd_concurrent_queue_size
fnd_concurrent_queues
fnd_nodes

Syntax:

$sqlplus apps/<apps_password>

SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.

Once the script was executed must run the autoconfig in DB and Middle-Tier  

Cmclean.sql

We use the cmclean.sql scrip clean the running and pending requests

Down the concurrent manager and check if any concurrent program running/not(ps- ef |grep FNDLIBR, ps- ef |grep FNDOPP)

Cmclean.sql script is not recommended by oracle. R12 will user cpadmin.sh and 

concurrent manager recovery wizard.

It will be clear the below tables

 fnd_concurrent_processes
 fnd_concurrent_queues
 fnd_concurrent_requests
 fnd_conflicts_domain
 fnd_concurrent_conflict_sets


Refer:
EBS R12.2 Cloning Step by step àClickhear
DOC ID:134007.1

Comments

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

How to run Gather Schema Statistics in R12.2

How to clear weblogic stuck threads in R12.2