CP Admin in R12.2.

5
This new Adadmin-style utility for managing concurrent managers is available from
12.2.5. I was expecting this kind of tool to manage the concurrent manager for a
long time now.
Cpadmin utility could easily facilitate managing concurrent processes for Apps DBAs
who otherwise follow a tedious procedure of logging in, opening forms and checking
concurrent manager processes every single time. It is going to be the alternative for
cmclean.sql, and hence this script need not be searched in the newly cloned
instances. No need to search for the cmclean.sql script in the new cloned instances.
Procedure:
Run cpadmin.sh in the command mode. This executable is available in
$FND_TOP/bin, as it is already in the executable path it can be invoked from any
directory. It prompts for the apps password in console mode
[applmgr@major VIS]$ cpadmin.sh
Copyright (c) 2015 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite CP Administration
$Revision: 120.0.12020000.5 $
Logging to file
/u01/app/VIS/fs_ne/inst/VIS_major/logs/appl/conc/log/cpadmin.021720160857
Enter the password for your APPS ORACLE schema:
Connecting to database
CP Administration Main Menu

1. Administer Concurrent Managers

2. Administer Concurrent Requests
E. (E)xit CP Administration
Enter your choice: [E] :
In the menu option 1 Administer the managers has lot of handy apps dba scripts
Administer Concurrent Managers

1. Manager Status
Show status of all managers
2. Clean concurrent processing tables
Ensure concurrent processing tables are cleaned and reset for ICM startup

3. Set Manager Diagnostics

Turn diagnostics on/off for specific managers
4. Control a manager or service
Send a control request to a manager or service
5. Rebuild Concurrent Manager Views
Rebuild Views for Fnd_Concurrent_Worker_Requests and
Fnd_Concurrent_CRM_Requests
R. (R)eturn to previous menu
E. (E)xit CP Administration
I am impressed with the option 2. Clean concurrent processing tables
Alternative for cmclean.sql
Enter your choice: [R] : 2
Running command: Clean concurrent processing tables (120.0.12020000.5)

This utility should be used when the Internal Concurrent

Manager fails to start due to corrupted internal state
information.
The Internal Concurrent Manager must not be running at
this time. The utility will verify the Internal
Concurrent Manager is not running before making changes.
Continue (Y or N)
Below option also very useful for us. We can set the debug for the below critical
managers and identify the cause of an issue quickly
Option 3. Set Manager Diagnostics
Enter your choice: [R] : 3
Running command: Set Manager Diagnostics (120.0.12020000.1)

1.
2.
3.
4.
5.
6.

ICM
CRM
Output Post-Processor
Request-Processing Managers
Transaction Managers
Cancel and return to menu

Set diagnostics for:

In the main menu of cpadmin.sh

Option 2 Administer Concurrent Requests have lot of interesting options. Below
example will really thrills you.
Administer Concurrent Requests

1. Analyze Concurrent Requests

Analyze Concurrent Requests and print out details
2. Move Request Files
Commands to change request log and output file locations
R. (R)eturn to previous menu
E. (E)xit CP Administration
Enter your choice: [R] : 1
Running command: Analyze Concurrent Requests (120.0.12020000.1)

Analyze a Concurrent Request

This utility analyzes a concurrent request and returns details
EnterRequest ID: 7444720
7444720 is a valid request ID
Analyzing request 7444720

Program information:
Program: Active Users (FNDSCURS)
Application: Application Object Library
Executable type: Oracle Reports (P)
Executable file name or procedure: FNDSCURS
Run alone flag: N
SRS flag: Q
NLS compliant: Y
Output file type: TEXT

Submission information:
It was submitted by user: SYSADMIN
Using responsibility: System Administrator
It was submitted on: 02-17-16 09:24:45AM
It was requested to start on: 02-17-16 09:24:45AM
Parent request id: -1
Language: AMERICAN
Territory: AMERICA

Priority: 50
Arguments: (0) null

Analysis:
Request 7444720 has completed with status: Normal
It began running on: 02-17-16 09:24:47AM
It completed on: 02-17-16 09:25:13AM
It was run by : Standard Manager
Logfile: /u01/app/VIS/fs_ne/inst/VIS_major/logs/appl/conc/log/l7444720.req
Outfile: /u01/app/VIS/fs_ne/inst/VIS_major/logs/appl/conc/out/o7444720.out
It produced completion message: Normal completion
2. Move Request Files also give lot of options for apps dba to manage the concurrent
request
Administer Concurrent Requests

1. Analyze Concurrent Requests

Analyze Concurrent Requests and print out details
2. Move Request Files
Commands to change request log and output file locations
R. (R)eturn to previous menu
E. (E)xit CP Administration
Enter your choice: [R] : 2
Move Request Files

1. Set new filenames for a single request

Set new filenames for a single request to a new complete path and filename
2. Set node for a single request
Set node for a single request to a different node
3. Move files for a single request
Move files for a single request to a different directory
4. Move files for multiple requests within date range
Move files for multiple requests within date range to a different directory
5. Set node for multiple requests within date range
Set node for multiple requests within date range to a different node

6. Move files for multiple requests within request id range

Move files for multiple requests within request id range to a different directory
7. Set node for multiple requests within request id range
Set node for multiple requests within request id range to a different node
R. (R)eturn to previous menu
E. (E)xit CP Administration
Enter your choice: [R] : 1
Running command: Set new filenames for a single request (120.0.12020000.2)

Enter single request_id: 7444720

Enter new complete path and filename for logfile(or no input to leave logfile
unchanged):
I strongly assume that it would be worth checking all the options and quite sure
about the use of it all.