Information Center:Demantra Install, Upgrade, Patching,Technical Config (Doc ID 1400207.2)
Install Demantra ~ How to UPGRADE ~ Main Release Patches List And Recommended Patches (Doc ID 1342064.1)
Demantra - Development Sponsored Document Library. CRITICAL Updates, Comprehensive, Effective Technical Briefs, Guides, Notes +! (Doc ID 2245610.1)
E-Business Suite R12 Concurrent Processing, Concurrent Manager and Request issues
Provide documentation and resources for the new cpadmin.sh command line utility.
The cpadmin.sh script is a command-line tool which consolidates various existing tools for concurrent processing into a single menu-based utility run via a shell script.
The new cpadmin.sh utility initial announcement was provided in the following blog article released by development:
The cpadmin.sh utility is formally documented by development in the following user guide:
https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T575591.htm#8159578
This adadmin style utility was designed to integrate the following Concurrent Processing features in one script.
It has the following menu options:
Manager Status
This option is used to view the status of concurrent managers and services.
Use this option to display running managers (with or without process IDs) or display all managers.
The same status information is shown in Administer Concurrent Managers form and OAM Concurrent Managers page.
Clean CP Tables
Use this option to clean up the concurrent processing tables. This utility replaces cmclean.sql. Use this option when the Internal Concurrent Manager (ICM) fails to start due to corrupted/conflicted tables. Note the following actions when choosing this option:
Managers must be stopped first (the utility will verify this).
Clean up inconsistencies in manager tables; remove corruption.
Reset manager states for clean start-up.
Clean and reset Advanced Queue tables for the Output Post-Processor and FNDSM Service Manager.
Reset request conflicts for the Conflict Resolution Manager (CRM).
Identify and clean orphaned requests.
This option is supported by Oracle for use on client systems.
Important: DO NOT USE the cmclean.sql script.
Set Manager Diagnostics
Turn diagnostics on or off for individual managers with this option. You can use this option to turn diagnostics on/off for specific managers without bouncing all services.
This option is available for:
ICM
CRM
Output Post-Processor
Request Processing Managers
Transaction Managers
Each option will display the current diagnostic status (ON or OFF) of the running managers/services and allow you to change the status.
Manager Control
Use this option to send a request such as start, stop, or verify to an individual manager.
Use to send a control request to a manager or service.
This option does the following:
Displays current status of all managers and processes.
Once a manager or service is chosen, offers valid control options for that specific choice.
Valid options for managers: activate, deactivate, verify, restart, abort, shut down.
Valid options for services also include: suspend and resume. Any service can be programmed to respond appropriately to each option; but if one is not, then the service will not respond.
Rebuild Manager Views
Use when Manager Views must be rebuilt.
This option rebuilds the FND_CONCURRENT_WORKER_REQUEST and FND_CONCURRENT_CRM_REQUESTS views with the following steps:
Managers must be stopped first. The utility verifies that these are stopped.
Rebuilds FND_CONCURRENT_WORKER_REQUESTS.
Rebuilds FND_CONCURRENT_CRM_REQUESTS.
Running this option is the same action as running FNDCPBWV.
Move Request Files
Change request log and output file locations with this option.
Use to update the concurrent processing tables for changing the following values for request LOG file, OUT file, or BOTH:
Individual requests: fully qualified file name or node name
Range of requests: directory name or node name
Range of requests can be selected by minimum/maximum date or minimum/maximum request_id
Important: The cpadmin utility changes only the concurrent processing database table values to support movement. The files must be manually moved by an administrator.
Analyze Request
Use this option to analyze a concurrent request.
Use when analyzing a request for any reason. This is non-destructive.
Managers need not be shut down for this option.
This option does the following:
Checks the manager's status.
Analyzes the request's status.
Provides a detailed report on concurrent program.
Gives a detailed report on request's current status.
Running the cpadmin utility:
Complete the steps below to run the command-line utility and its maintenance tasks.
1. Set the environment. in order to apply the environment variables defined for the system. See Setting the Environment, Oracle E-Business Suite Maintenance Guide for more information.
2. From any directory, start cpadmin with the below command:
$ cpadmin.sh
The utility starts and prompts you for the APPS password (required).
3. Respond to prompts. Supply the information requested by cpadmin prompts. Prompts unique to an option are described with the option. When you complete the prompts, the Main Menu appears.
4.Choose one of the tasks listed above.
5. Exit the cpadmin utility.
Note:
CPADMIN utility is designed only for interactive mode, and there is no documentation for it to be used otherwise.
https://apexapps.oracle.com/pls/apex/f?p=133:180:106932995936354::::wid:753
Deploying Oracle E-Business Suite Cloud Manager Version 20.1.1.X on Oracle Cloud Infrastructure (Doc ID 2434500.1)
Someone changed apps password using 'alter user' which is not a good practice.
this Document
| Purpose |
| Scope |
| Automatic Workload Repository (AWR) Overview |
| Details |
| Frequently Asked Questions |
| Collecting AWR reports |
| AWR Interpretation |
| AWR setup and Troubleshooting setup Issues |
| AWR Setup |
| AWR Troubleshooting |
| AWR Storage Management |
| Common Issues |
| If awrinfo.sql hangs, use following script: |
| Community Discussions |
| References |
Automatic Workload Repository (AWR) is a licensed feature that allows information to be recorded on a database for multiple purposes including detection and elimination of performance issues.
For a general overview of Performance Advisors and Manageability Features, see:
Assuming you have the appropriate licenses for AWR, you may gather and examine Automatic Workload Repository (AWR) reports for the system.
Without the appropriate licenses, Statspack provides a legacy solution:
A video entitled: "Introduction to Performance Analysis Using AWR and ASH" is available here providing a comprehensive guided tour using an actual problem.
This section covers the setup of AWR and troubleshooting of problems related to that:
Still have questions? Use the communities window below to search for similar discussions or start a new discussion on this subject.
Click here to open in main browser window.
This document looks at several key aspects of upgrading Oracle E-Business Suite Release 12.
The core of this document is the set of six attachments that contain information on the following topics: tablespace sizing, schema sizing, post-upgrade historical Financials documents (optional), best practices to manage the upgrade of Release 12, required post-upgrade concurrent jobs, and sample upgrade timings.
The database upgrade statistics are from the upgrade of a 6.5 TB Oracle E-Business Suite Release 11.5.10 CU2 database.
There is a change log at the end of this document.
Click on one of the following links to open or download an attachment:
These attachments are also listed at the bottom of this document.
| Years of Data Migrated | Database Size (GB) Before Upgrade | Database Size (GB) After Upgrade | Delta (GB) | % Growth |
|---|---|---|---|---|
| 3 | 6609.97 | 6808.44 | 198.47 | 3 |
| 12 | 6609.97 | 7161.61 | 551.64 | 8.3 |
The first column, "Years of Data Migrated" refers to the number of financial periods (in units of years) selected to be migrated during the actual upgrade phase. For example, three years of Financials data refers to upgrading Financials documents such as Payables, Receivables, Costing, Projects, and Fixed Assets for the periods from 2004 through to 2006.
 |
|
In This Document Section 1: Overview of the EBS System Schema Section 2: Requirements for Using the EBS System Schema Section 3: Migrating t...
