Sunday, May 22, 2016

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.7 and R12.TXK.C.Delta.7

I was under the impression that dualfs option during cloning of EBS is available only from EBS 12.2.5. After discussing with one of the Oracle Community member, i come to know that it is available from latest AD/TXK Release 7. So even if i use EBS 12.2.4 and then apply the latest AD/TXK patches, i can get the dualfs option.


The features which are new in AD/TXK release 7 are:

1.1 Enhanced adop Console Messages

The adop utility has been significantly enhanced, to display more selective information on the console. Messages, prompts and other UI elements have also been extensively refined to increase ease of use of patching commands.

1.2 New adop Monitoring Tool

Progress of an online patching cycle can be followed by running the new Online Patching Monitoring utility (adopmon). This utility can be used to follow the overall progress of a patching cycle, as well as identifying the various individual adop actions being taken.

1.3 New adop 'validate' Option

Before you start a new patching cycle by running the prepare phase, you can optionally check your system's readiness by running adop with the 'validate' option. If you do this while a patching cycle is in progress, validation will take place for the cutover phase.

1.4 Support for Middle Tier EBS Technology Checker

The new middle tier checker (MT-ETCC) technology script complements the original ETCC database checker script (now called DB-ETCC). The scripts report respectively on any missing middle tier and database tier bugfixes and patches that are required for Release 12.2.

1.5 Support for EBS Installation Central Inventory

Support for an instance-specific EBS Installation Central Inventory has been introduced as an option for the application tier on UNIX platforms. The inventory is identified by <s_base>/oraInventory/oraInst.loc. This feature is useful where multiple Oracle E-Business Suite installations exist on the same host, helping to avoid issues when fs_clone is run simultaneously on different instances.

To use the EBS Installation Central Inventory, all application tier Oracle Homes registered in the global inventory for the instance must be migrated to the new inventory. This is done by running the following steps on the primary application tier node:

Source the run edition file system.
Edit the context file and set the value of the context variable s_ebs_central_inventory to 'true'.
Run AutoConfig.
Run the following command:
$ perl <FND_TOP>/patch/115/bin/txkMigrateInventory.pl -contextfile=<CONTEXT_FILE>
Ensure that all application tier Oracle Homes have been migrated to the EBS Installation Central Inventory.

Repeat all the above steps on any non-shared nodes and shared master nodes (for example, in a hybrid setup). For all shared slave nodes, perform Steps 1 to 3 (only) on each node.

Once the inventory is migrated, any subsequently added nodes will be automatically configured to use the EBS Installation Central Inventory, and any new target instance cloned from this instance will automatically be configured to use it.

1.6 Script to Automate Changing Oracle WebLogic Server Administration User Password

The procedure used to change the Oracle WebLogic Server Administration User Password has been simplified and largely automated by the introduction of a new utility that performs what were previously manual steps.

You can set the Oracle WebLogic Server Administration User password to a non-default value during Oracle E-Business Suite installation. if you need to change the password at a later time, you can do so on the run file system by shutting down all application tier services except the Admin Server, then running the new $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl script with the -action=updateAdminPassword option.

1.7 Oracle WebLogic Server Performance Enhancements

Several related enhancements have been made to Oracle WebLogic Server:
A new -DserverType=wlx start argument for managed servers reduces their memory footprint, by preventing startup of the Enterprise JavaBeans (EJB), Java EE Connector Architecture (JCA), and Java Message Service (JMS) services.
The default value of s_forms-c1wsstatus is now set to 'Disabled'.Thus, the formsc1-ws servers are no longer started during a 'start all' operation.
To reduce oacore startup time, the Portlet Producer libraries are no longer deployed to the EBS domain. A new context variable, s_deploy_portlet, has been introduced to cater for cases where portlet-related configuration is required, such as in instances needing Webcenter integration.

1.8 Simplified Procedure for Changing WLS Data Source

Changing the APPS schema password in the WLS Data Source with FNDCPASS or AFPASSWD has now been simplified and partially automated. The required sequence of actions on the run file system of the primary node includes shutting down the application tier services; starting AdminServer with the adadminsrvctl.sh script; running the txkManageDBConnectionPool.pl script and choosing the 'updateDSPassword' option; and finally restarting the application tier services. Reference: Chapter 6, Basic DBA Tasks, Oracle E-Business Suite Maintenance Guide.

1.9 New 'dualfs' Option in Standard Cloning

A new 'dualfs' option is available when performing a standard clone, as well as while adding a new node. With the 'dualfs' option, both the run and patch file systems are cloned and configured in a single operation.

1.10 Improved Delete Node and Delete Managed Server APIs

The improvements include addition of more validations.


1.11 Mandatory Definitions of Context Variables

Definition of the following is mandatory in the pairs file used for standard clone and for addition of nodes:
s_webentryurlprotocol
s_webentryhost
s_webentrydomain
s_active_webport

1.12 Various Fixes for Oracle Database 12c

These include cleanup of existing integrations following run of Rapid Clone.

1.13 Automatic Execution of ETCC on Database Tier After Cloning

This now takes place automatically, instead of as a manual step after database tier cloning.

References: metalink note:2033780.1


No comments:

Post a Comment