NEWS AND UPDATES
Check BI Publisher’s Health with BIP Analyzer for E-Business Suite
In 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:
Spotlight on BIP Analyzer
BI Publisher for EBS (BIP, previously called XML Publisher) is integrated into the E-Business Suite technology stack. The BIP Analyzer is available here:
- EBS BI Publisher (BIP) Analyzer (Note 2032715.1)
The BI Publisher Analyzer reviews BIP configurations and compares them against Oracle’s best practices. It provides troubleshooting advice for common issues, such as:
- Java Heap sizing
- OPP memory optimization
- Issues with threads and processes
- Out of Memory issues
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 Workflow 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.
Related Articles
Can Nologging Be Enabled for EBS 12.2?
The nologging Oracle database feature is used to enhance performance in certain areas of Oracle E-Business Suite. For example, it may be used during patch installation, and when building summary data for Business Intelligence.
What are the tradeoffs of using nologging?
Use of nologging in an operation means that the database redo logs will contain incomplete information about the changes made, with any data blocks that have been updated during the nologging operation being marked as invalid. As a result, a database restoration to a point in time (whether from a hot backup or a cold backup) may require additional steps in order to bring the affected data blocks up-to-date, and make the restored database usable. These additional steps may involve taking new backups of the associated datafiles, or by dropping and rebuilding the affected objects. The same applies to activation of a standby database.
Can nologging be enabled for EBS 12.2?
Yes. See the following documentation for additional considerations and operational implications of using nologging:
Related Articles
- Check Your EBS Database Configuration with Database Parameter Settings Analyzer
- Webcast: Getting Optimal Performance from Oracle E-Business Suite
- Enabling an EBS Global Diagnostics Trace
- Recommended Database Parameters Updated for EBS 12.2
Source: https://blogs.oracle.com/stevenchan/can-nologging-be-enabled-for-ebs-122
CPADMIN Utility Now Available for EBS 12.2.3, 12.2.4, 12.2.5
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 a SPARC-powered Exadata Configuration Called SuperCluster
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.