Skip navigation.

Senthil Rajendran

Syndicate content
The voice in my head may not be real , but they have some good ideas !!!Senthilkumar Rajendranhttps://plus.google.com/106215216686965173274noreply@blogger.comBlogger246125
Updated: 9 hours 5 min ago

EBS R12.2 Delta 6 Feature Review : Single File System Instance

Mon, 2015-04-27 04:40
With one of the main feature in 12.2 dual file system, there was always a need about having a single file system in 12.2 like 12.1.x and get away with the ADOP patching cycle. With Delta 6 AD and TXK you can. It is important to understand the feature and know its limitations.

There are two advantages of this single file system feature in 12.2

  • no more synchronization of run and patch file system
  • save storage
Still it operates with same ADOP engine and it is NOT CERTIFIED for PRODUCTION.This feature will be interesting for development team where they need an EBS 12.2 instance where they can test their custom code.
Here is how to setup 
  • Install R12.2 Instance with dual file system or Clone an existing environment with dual file system. No option available in the Rapid Installer to select single file system instance.
  • Remove the PATCH_BASE using operating system remove command rm -rf $PATCH_BASE
  • Apply the patch using in ADOP downtime mode and run cleanup phase as required
So what is not possible ?
  • You cannot clone the single file system to build another environment.
  • You cannot enable the dual file system back and start a patching cycle
Note : please refer to the recent product documentation to know the latest changes.

EBS 12.2 do not ignore the database patches on top of AD Delta 5 and TXK Delta 5

Sun, 2015-04-05 08:13

Make sure all the recommended patches are in place as a part of the bundle patch. Your EBS 12.2 ADOP cycle could go unstable with out the database patches.

EBS 12.2 Essential Bundle Fixes for AD Delta 5 and TXK Delta 5 (Doc ID 1934471.1)

Thu, 2015-01-22 07:38
EBS 12.2 Essential Bundle Fixes for AD Delta 5 and TXK Delta 5 (Doc ID 1934471.1)

if any of the below features are interesting to your deployment then please review the doc and apply the essential bundle patches on 12.2.5 environment. Hope this helps to stabilize your environment.

Section 4: Features and Fixes in the Current Code level
The bundle fixes include implementation of the following AD and TXK features and fixes.

4.1: AD Features and Fixes

  • The database connection module has been enhanced such that the former multiple connections during adop execution have been reduced to only two connections for all embedded SQL actions.
  • Concurrency issues during multi-node configuration have been fixed.
  • Redundancy issues have been addressed:
    • When calling validation on all nodes.
    • Unnecessary calls to the TXK API, have been removed from the cleanup phase.
    • Time-consuming database actions have been centralized, instead of being performed on all nodes.
  • Multinode logic has been changed to depend on a new table, adop_valid_nodes, instead of fnd_nodes.
  • An issue where AD Admin and AD Splice actions were not synchronized on shared slave nodes has been fixed.
  • Reporting capabilities have been improved for:
    • Abandon nodes and failed nodes.
    • Uncovered objects not being displayed after actualize_all in adopreports.
    • Out of sync nodes during fs_clone and abort.
  • Cutover improvements:
    • Restartability of cutover.
    • An obsoleted materialized view has been removed from processing during cutover.
  • xdfgen.pl has been enhanced to support execution against Oracle RAC databases where ipscan is enabled.
  • Support for valid comma-separated adop phases has been provided.
  • Several database-related performance issues have been fixed.
  • Improvements have been made in supporting hybrid, DMZ, non-shared, and shared configurations.
  • The adop utility has been enhanced to support host name containing the domain name.

4.2: TXK New Features and Fixes

  • Enhancements have been made to the provisioning tools used in multi-tier environments to perform operations such as adding or deleting nodes and adding or deleting managed servers.
  • An enhancement has been made to allow customization of the s_webport and s_http_listen_parameter context variables when adding a new node.
  • Performance improvements have been made for cloning application tier nodes, particularly in the pre-clone and post-clone phases.
  • Fixes related to cloning support for Oracle 12c Database have been provided.
  • Performance improvements have been made for managing application tier services, including implementation of the Managed Server Independence Mode feature (-msimode parameter to adstrtal.sh) to allow application tier services to be started or stopped without the WebLogic Administration Server running.
  • On a multi-node application tier system configuration, remote connectivity is no longer required for packaging the Oracle E-Business Suite WebLogic Server domain.
  • JVM heap size (-Xms and -Xmx) has been increased to 1 GB for the WebLogic Administration Server and all managed servers.


EBS 12.2 Blocking a Concurrent Program while Online Patching

Sat, 2015-01-10 22:36
Will there be a need to Blocking a Concurrent Program while Online Patching in EBS 12.2 , if so then here are the steps.

  • Use the Concurrent Program window or page to edit your concurrent program definition.
  • Select the Incompatibilities button to open the Incompatible Programs window.
  • Add a new global incompatibility rule for your program with the following program:
    • Application Name: Applications DBA
    • Program Name: Online Patching In Progress (internal name: ADZDPATCH) concurrent program