I recently profiled the CPADMIN utility for EBS 12.2.6 that consolidates various CP management functions into a single menu-based tool.  This ADADMIN-style utility can:

• View Concurrent Manager status
• Clean CP tables
• Set Concurrent Manager diagnostics
• Start, stop, or verify an individual Concurrent Manager
• Rebuild Concurrent Manager views
• Move request files
• Analyze requests
• Configure request log/out file directory locations

This tool has been backported to EBS 12.2.3, 12.2.4, and 12.2.5 via Patch 24408550:

• Oracle E-Business Suite System Administration Release Notes for Release 12.2.3 (Note 1605970.1)
• Oracle E-Business Suite System Administration Release Notes for Release 12.2.4 (Note 1911290.1)
• Oracle E-Business Suite System Administration Release Notes for Release 12.2.5 (Note 2059809.1)

In case you missed it, this tool is also available for EBS 12.1.3.

Related Articles

• CPADMIN Utility for Managing Concurrent Processing Available for EBS 12.1
• New CPADMIN Utility for Managing Concurrent Processing Now Available for EBS 12.2
• Check Concurrent Processing’s Health with CP Analyzer

Source:https://blogs.oracle.com/stevenchan/cpadmin-utility-now-available-for-ebs-1223%2c-1224%2c-1225

Oracle has been shipping an Oracle Exadata configuration that runs Oracle’s T and M-series (SPARC) microprocessors for more than 2 years. This database machine is called Oracle SuperCluster.

Technically, SuperCluster has always included every single Exadata feature of note. This is because every SuperCluster configuration is built around the same Exadata Storage Serversand InfiniBand switches that are used in every other Exadata system configuration.

In the case of the SuperCluster configurations, however, we have added Oracle T and M-series microprocessors to the compute nodes (used for running Oracle Database and other software) and ZS3-ES storage (used for pre-11gR2 Oracle Database storage, virtual machine images and other data needed by the system). SuperCluster is a ‘hybrid’ system that integrates both x86 processors and Oracle’s T and M-series microprocessors in the interest of achieving the greatest flexibility, performance, efficiency and reliability possible.
Both SuperCluster and Exadata X-series configurations are equally well suited to all of the major classes of Oracle Database use cases: OLTP, Data Warehouse, Database Consolidation and Database-as-a-Service (DBaaS). There are technical differences, however, which make SuperCluster the right first choice for some customers or projects.

SuperCluster offers several important features that are not available today in other Exadata configurations:

• Support for multi-tenancy through virtualization (which some customers prefer, rather than using the Plug-able Database (PDB) approach pioneered in Oracle Database 12c, for example)
• Oracle’s T and M-series microprocessors (which deliver world-record-breaking Oracle Database performance)
• Larger blocks of contiguous memory (ECC DRAM) and more memory per processor (ideal for in-memory workloads and large vertically scaled databases)
• Support for multiple database versions concurrently, including pre 11gR2 Oracle Database
• Direct integration with existing Storage Area Networks via the optional addition of Fibre Channel Host Bus Adapters (FC HBAs)
• Support for running application-tier workloads along with Oracle Database, to further improve overall application performance, reliability and consolidation density where desired
• More compute power per gigabyte of included Exadata Storage Server capacity (although Exadata Storage Expansion Racks may be added if desired)

Exadata configurations, on the other hand, offer some capabilities that are essential in some cases:

• They can run either Oracle Linux and Oracle Solaris operating systems, whereas SuperCluster only supports Solaris
• They have more Exadata Storage Server capacity per processor than SuperCluster in their factory configurations
• They come in very small Quarter Rack or Eighth Rack configurations, while the smallest SuperCluster configuration is a Half Rack.

So which configuration should you choose?
The guidance we offer customers about whether to choose an Exadata or SuperCluster configuration is fairly simple: both Exadata and SuperCluster configurations are equally optimized for Oracle Database and can, in fact, be deployed together to create a single system for customers that require maximum flexibility.  For customers currently running Oracle Database (or other databases) in mission-critical deployments on UNIX/RISC platforms (such as Power, SPARC or Itanium), SuperCluster would be the natural first candidate because of it’s familiarity, technical similarity and feature set.  Conversely, customers running Oracle Database with Oracle Real Application Cluster (RAC) in commodity x86 server environments will likely find the Exadata X-series configurations to be the most natural first choice. In most cases, the decision about which configuration to deploy will be driven by technical needs, and the distinctions outlined above are sufficiently straightforward to interpret without appreciable risk or uncertainty.

Source: https://blogs.oracle.com/oracle-systems/oracle-has-a-sparc-powered-exadata-configuration-called-supercluster

Database ParaIn addition to helping customers resolve issues via Service Requests, Oracle Support also builds over 60 free diagnostic tools for Oracle E-Business Suite 12.2, 12.0, 12.1, and 11i. These Support Analyzers are non-invasive scripts that run health-checks on your EBS environments. They look for common issues and generate standardized reports summarizing that provide solutions for known issues and recommendations on best practices.

Here’s an index to these tools:

• Get Proactive with Oracle E-Business Suite – Product Support Analyzer Index (Note 1545562.1)

Spotlight on Database Parameter Settings Analyzer

We publish a definitive list of Oracle Database initialization parameter settings for the optimal performance of Oracle E-Business Suite 12.2, 12.1, and 12.0:

• Database Initialization Parameters for Oracle E-Business Suite Release 12 (Note 396009.1)

This document is updated regularly; for example, it was recently updated to account for changes introduced by the April 2017 updates to the AD and TXK utilities.

It can be challenging to keep up with those changes simply by scanning Note 396009.1 yourself.  You can automate this process by using the Database Parameter Settings Analyzer:

• EBS Database Parameter Settings Analyzer (Note 1953468.1)

The Database Parameter Settings Analyzer compares your database’s parameter settings to the latest recommendations in Note 396009.1.  It reports on any differences, and makes recommendations about your sga_target, shared_pool_size, shared_pool_reserved_size and processes parameters based upon the number of active users for your environment.

This tool can be run manually or configured to run as a concurrent request, so it can be scheduled to be run periodically and included in regular database maintenance cycles.

Can this script be run against Production?

Yes. There is no DML in the Analyzer Script, so it is safe to run against Production instances to get an analysis of the environment for a specific instance. As always it is recommended to test all suggestions against a TEST instance before applying to Production.

Source: https://blogs.oracle.com/stevenchan/check-your-ebs-database-configuration-with-database-parameter-settings-analyzer