- adautocfg.sh - This script is used for running AutoConfig.
- adchkcfg.sh - This script may be run before running AutoConfig to review the changes on running AutoConfig.
- admkappsutil.pl - This script is used while applying patches to the database tier. Running this (more...)
- In previous Oracle E-Business Suite releases, the Applications services were categorized into service groups according to the type of service provided.
- In Oracle E-Business Suite Release 12.2, this concept has been extended by the introduction of additional services and service groups.
Oracle E-Business Suite Release 12.2 requires WebLogic Server Basic.
This is a license-constrained version of WebLogic Server that is available in licenses for certain Oracle products.
WebLogic Server Basic is used in Oracle E-Business Suite Release 12.2 to support the following features:
- This release is largely focused on providing new technology stack components, new configuration options, and new system management tools.
- Supports for Online Patching.
- Use of Oracle WebLogic Server instead of AutoConfig for many (but not all) of AutoConfig's previous functions.
- Use of Oracle WebLogic Server instead of (more...)
This method applies to RHEL; let’s first install the VNC Server. Through yum command # yum install tigervnc-server Or Through RPM command First, locate and mount your RHEL 6.3 install media. [root@oraerp ~]# cd “/media/RHEL_6.3 x86_64 Disc 1/Packages” [root@oraerp Packages]# pwd /media/RHEL_6.3 x86_64 Disc 1/Packages Install (more...)
If you pay any attention to the Oracle enterprise applications space, you’re likely aware of the fuss being raised over the impending demise of Oracle Discoverer. Discoverer is a pretty nifty ad hoc reporting tool used for both enterprise (more...)
- It is a stand-alone command used for file system cloning.
- Standard cloning (using adcfgclone.pl) cannot be used to synchronize the run and patch file systems.
- This special phase must be run from the run file system, and cannot be specified with any other phase.
- It should be (more...)
If for some reason either the prepare or apply phase failed or gave problems, you can abort the patching cycle.
After running abort, you must always run a full cleanup
adop phase=cleanup cleanup_mode=full
This will remove any columns that were added by the patch but are no longer (more...)
Drops now-redundant columns and other objects which are not required after the cutover phase.
It is important that we do not omit the cleanup phase.
This step can be done after instance is released to Customer
The following actions are performed during cleanup:
- Drop covered objects
- Drop indexes
- How do we do it?
- Pre-Health Check
Performs the actions needed to make the former patch edition the new run edition, and the former run edition the new patch edition.
Cutover also prepares the environment for users.
This is the only phase that involves a (brief) period of downtime.
- Application Tier (more...)
Perform the final operations like Compile Invalids , Generate Derived Objects and Pre-compute DDL to be run at the Cutover phase.
Facilitates verification of customizations or other objects that may be affected by a patch.
If you skip this phase it will be called automatically (more...)
This phase applies the specified patches to the PATCH Edition.
While patches are being applied to the patch edition, the run edition of the application remains fully operational.
Ongoing changes from the run edition are either automatically inherited by the patch edition, or they are transformed and propagated (more...)