adop fs_clone phase fails after upgrading FMW to 11.1.1.7

The adop fs_clone phase fails after upgrading FMW to 11.1.1.7 with the following error:

Error:

Log file located at /u01/ebs/apps/fs1/inst/apps/ebs/admin/log/clone/FSCloneStageAppsTier_11270942.log
Exception in thread "main" java.lang.NoSuchMethodError: oracle.jdbc.driver.PhysicalConnection.getDefaultAutoRefetch()Z
at oracle.jdbc.driver.OracleStatement.(OracleStatement.java:762)
at oracle.jdbc.driver.T4CStatement.(T4CStatement.java:1255)
at oracle.jdbc.driver.T4CDriverExtension.allocateStatement(T4CDriverExtension.java:48)
at oracle.jdbc.driver.PhysicalConnection.createStatement(PhysicalConnection.java:3460)
at oracle.jdbc.driver.PhysicalConnection.createStatement(PhysicalConnection.java:3425)
at oracle.apps.ad.clone.util.CloneUtil.getServerNamesFromDB(CloneUtil.java:950)
at oracle.apps.ad.clone.util.CloneUtil.getAllServerNamesFromDB(CloneUtil.java:903)
at oracle.apps.ad.clone.FSCloneStageAppsTier.doStage(FSCloneStageAppsTier.java:362)
at oracle.apps.ad.clone.FSCloneStageAppsTier.(FSCloneStageAppsTier.java:149)
at oracle.apps.ad.clone.FSCloneStageAppsTier.main(FSCloneStageAppsTier.java:667)

Fix:

To resolve the issue test the following steps in a development instance and the migrate accordingly:

1. Take a backup of any involved files.

2. Download clean version of the file ojdbc6.jar via the following link:

https://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html

3. Replace the corrupted ojdbc6.jar jdbc driver file.

4. Confirm the file is correct via the following commands:

•    java -jar ojdbc6.jar -getversion
•    md5sum ojdbc6.jar

5. Retest adop fs_clone and confirm it now progresses successfully.

URL validation failed. The error could have been caused through the use of the browser's navigation buttons ( the browser Back button or refresh, for example). If the error persists, Please contact system administrator.

When we are trying to access the Oracle E-Business Suite R12.2.5 forms in Internet Explorer 10, we are getting below error.

Error:

'URL validation failed. The error could have been caused through the use of the browser's navigation buttons ( the browser Back button or refresh, for example). If the error persists, Please contact system administrator.'

Fix:

There could be multiple reasons for the issue, but in our scenario adding this Login URL into trusted sites can resolved my issue. 

Navigation:

• Goto Internet Options
• Security
• Trusted sites
• Sites
• Add this website to the zone.

ORA-06512: at "APPS.HR_API_USER_HOOKS_UTILITY", line 891

When attempting to apply 12.2.6 patch: 21900901:oracle e-business suite 12.2.6 release update pack
the following error occurs.

ERROR:

(XX_HR_USER_HOOK_PKG.POSITION_BEFORE_UPDATE_BK2) The call_package does not ex

ist in the database. Code to carry out this hook call has not been created.

DELETE_POSITION(Business Process API) successful.

BEGIN hr_api_user_hooks_utility.clear_hook_report; END;

*

ERROR at line 1:

ORA-06501: PL/SQL: program error

ORA-06512: at "APPS.HR_API_USER_HOOKS_UTILITY", line 891

ORA-06512: at line 1

To implement the solution, please execute the following steps:

1. Run the following sql.

SQL> select CALL_PACKAGE, CALL_PROCEDURE, ENABLED_FLAG from HR_API_HOOK_CALLS;

This will provide you a list of the user hooks, procedures and enabled_flag values

From this table, update the user hook in question and set it to 'N.'

2. Run the following in sql:

cd $PER_TOP/admin/sql

Log into SQLPLUS as the APPS user

SQL> @hrahkall.sql

This will clear up the child process that are still enabled.

3. Restart the failed worker and allow the patch to complete.

4. Properly create your user hook

Oracle E-Business Suite R12.2 major technology components

Oracle E-Business Suite uses the following major technology components in Release 12.2:

Oracle E-Business Suite R12.2.6 New and Changed Features

Oracle E-Business Suite Technology Stack and Oracle E-Business Suite Applications DBA contain the following new or changed features in Release 12.2.6.

Reorganized Patch Log File Directory Structure

Category	Description	Parameters
New feature	The adop log files, located on the non-editioned file system (fs_ne), are now organized in a logical hierarchical structure, where you drill down to the subdirectory that corresponds to the the action for which you wish to see the activities.	Not applicable.

Enhanced Seed Data Management

Category	Description	Parameters
New feature	A new architecture greatly increases the speed and efficiency with which seed data is synchronized as part of an online patching cycle. No additional storage is required, and seed data tables are upgraded on demand to the new architecture.	Not applicable.

Longer Custom Application Short Names

Category	Description	Parameters
New feature	If you deploy custom applications in Release 12.2, you must run AD Splicer to ensure they are registered correctly. This utility now supports application short names of up to sixteen (16) characters. For more information, refer to My Oracle Support Knowledge Document 1577707.1, Creating a Custom Application in Oracle E-Business Suite Release 12.2.	Not applicable.

Warning for Missing Application Tier Patches

Category	Description	Parameters
New feature	The adop utility now displays a warning message when a required application tier patch is identified as not having been applied. As this is a warning rather than an error, the utility does not exit as a result.	Not applicable.

Java Mission Control and Java Flight Recorder

Category	Description	Parameters
New feature	Java Mission Control and Java Flight Recorder can be now enabled for use with many Oracle E-Business Suite processes. For more information, refer to Java Mission Control and Java Flight Recorder in Chapter 13, Running Diagnostics, of Oracle E-Business Suite Maintenance Guide.	Not applicable.

Support for Platform Migration

Category	Description	Parameters
New feature	Platform migration is now certified with Oracle E-Business Suite Release 12.2. For more information, refer to My Oracle Support Knowledge Document 2048954.1, Application Tier Platform Migration with Oracle E-Business Suite Release 12.2.	Not applicable.

Enhanced Pairsfile Support

Category	Description	Parameters
New feature	Pairsfile support has been now extended to include the Windows platform as well as UNIX platforms. In addition, the pairsfile for the 'dualfs' option of adcfgclone.pl has been enhanced to support entries for the patch file system context variables. The context variable names for the patch file system should be prefixed with 'patch_'. For example, to customize the value of the context variable s_wls_oacoreport for the patch file system to 7235, the entry patch_s_wls_oacoreport=7235 should be used.	Not applicable.

Support for Longer Node Names in Rapid Clone

Category	Description	Parameters
New feature	The Rapid Clone utility now supports node names of up to sixty-three (63) characters. For more information about Rapid Clone, refer to My Oracle Support Knowledge Document 1383621.1, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone.	Not applicable.

Delta Synchronization of File Systems

Category	Description	Parameters
New feature	The fastest way to synchronize the two application tier file systems, the new option of delta synchronization uses your choice of third-party utility to synchronize the file systems by copying files as applicable from the source directory to the destination directory, optionally ignoring any files and directories you may decide to specify in an exclusion file.	$ adop phase=prepare sync_mode=delta

Applications DBA Online Patching Tool (adop)

Oracle E-Business Suite Maintenance Guide for a full description of adop features, operation, and usage.

The phase parameter specifies the parts (phases) of the online patching cycle to be executed. The five standard phases are executed in the order shown below.

Standard phases:

prepare      - Prepare the instance for patch application.

apply        - Apply patches (to the patch edition).

finalize     - Ready the instance for cutover.

cutover     - Make the patch edition the new run edition.

cleanup     - Drop obsolete objects and data from old editions.

There are also three special phases, for use when needed.

Special phases:

abort             - Abort the current online patching cycle.

actualize_all - Create actual copies of all code objects in the patch edition.

fs_clone        - Copy the run file system to the patch file system.

General parameters applicable to all phases:

workers=<number> [default: computed]

Number of parallel workers used to execute tasks.  Default value is computed principally according to number of available CPU cores.

input_file=<file_name>

As well as being entered directly on the command line, adop parameters can be specified in a text file, with one <parameter>=<value> on each line of the file.  Command line parameters override input file parameters.

loglevel=(statement|procedure|event|warning|error|unexpected)

[default: event]

Controls the level of diagnostic log detail displayed on the console.

prompt=(yes|no)  [default: yes]

Specifies whether adop should prompt for user input on warnings. By default adop will ask user whether to continue or exit on some warning messages.  If this parameter is set to "no" adop will remain fully non-interactive, and will continue past any warning messages without user confirmation.

Phase-specific parameters control operation of a particular phase:

Apply parameters:

patches=<patch#>[,<patch#>...]

patches=<patch_directory>:<driver>[,<patch_directory>:<driver>...]

This parameter specifies a comma-separated list of patches to be applied.  Patches can be specified either as the patch number or by the patch directory and driver file.  All patches are expected to be in the $PATCH_TOP directory on all tiers.  Patches are applied serially unless the merge=yes parameter is specified.

restart=(yes|no)  [default: no]

Use restart=yes to resume the previous failed apply command from where processing terminated.

abandon=(yes|no)  [default: no]

Use abandon=yes to abandon the previous failed apply command and start a new apply command.

apply_mode=(online|downtime|hotpatch)  [default: online]

Use online mode to apply a patch to the patch edition during an online patching cycle; downtime mode to apply a patch to the run edition when application services are down; and hotpatch mode to apply a patch to the run edition when application services are up. Only use hotpatch mode when explicitly directed by documentation.

apply=(yes|no)  [default: yes]

To run adop in test mode (without applying any patches), use apply=no

 options=<patch_option>[,<patch_option>...]

 Advanced options to control patching behavior.

       

See adop -examples for details.

flags=<patch_flag>[,<patch_flag>...]

 Advanced flags to control patching behavior.

 See adop -examples for details.

Finalize parameters:

finalize_mode=(full|quick)  [default: quick]

Quick mode will provide the shortest execution time, by skipping non-essential actions. Full mode performs additional actions such as gathering statistics that may improve performance after cutover.

Cutover parameters:

mtrestart=(yes|no)  [default: yes].

Specifies whether to restart application tier servers after cutover. Leave at default unless you need to perform manual steps during the cutover downtime.

cm_wait=<minutes>  [default: forever]

Specifies the number of minutes to wait for Concurrent Manager shutdown.  Adop cutover starts by requesting a concurrent manager shutdown and then waits for in-progress requests to complete.

If Concurrent Manager does not shutdown within the specified time limit, remaining concurrent requests will be killed and cutover will proceed.

Cleanup parameters:

cleanup_mode=(full|standard|quick)  [default: standard]

Quick mode provides the shortest execution time, by skipping non-essential actions. Standard mode performs additional processing to drop obsolete code objects from old editions.

Full mode performs additional processing to drop empty database editions and unused table columns.

Fs_clone parameters:

force=yes/no [default: no]

Use force=yes to restart a previous failed fs_clone command from the beginning.  By default fs_clone will restart where it left off.

Command flags:

-status [<session_id>]

Display status of the latest adop session, or a specified session.

-validate

Runs ADOP validations for verifying the current system state.

-examples

Display extended help information with common usage examples.

-help

This help screen.

How to check the adgrants version in oracle database

Below script to check the adgrants version in oracle database.

Script:

SELECT DISTINCT RPAD(h.filename,15) ,
  RPAD(g.version,20) ,
  RPAD(TRUNC(c.end_date),12) ,
  RPAD(a.bug_number,10) ,
  RPAD(e.patch_name,10) ,
  RPAD(b.applied_flag,4) "File:vers:Date:Bug:Patch:Apply"
FROM ad_bugs a,
  ad_patch_run_bugs b,
  ad_patch_runs c,
  ad_patch_drivers d ,
  ad_applied_patches e,
  ad_patch_run_bug_actions f ,
  ad_file_versions g,
  ad_files h
WHERE a.bug_id              = b.bug_id
AND b.patch_run_id          = c.patch_run_id
AND c.patch_driver_id       = d.patch_driver_id
AND d.applied_patch_id      = e.applied_patch_id
AND b.patch_run_bug_id      = f.patch_run_bug_id
AND f.patch_file_version_id = g.file_version_id
AND g.file_id               = h.file_id
AND h.filename LIKE 'adgrants.sql'
ORDER BY 1 DESC;

Output:

How to check Oracle Application Modules Licensed or Not.

Below script to find Oracle Application Modules are Licensed or Not.

Script:

SELECT fat.application_name
      ,fa.application_id
      ,fpi.patch_level
      ,decode(fpi.STATUS,'I','Licensed', 'N','Not Licensed','S','Shared','Undetermined') STATUS
      ,fpi.*
FROM fnd_product_installations fpi
      ,fnd_application fa
      ,fnd_application_tl fat
WHERE fpi.application_id = fa.application_id
AND fat.application_id = fa.application_id
AND fat.LANGUAGE = 'US';

Output:

How to verify the Nodemanager password is working or not?

We can verify the Nodemanager password by using below steps:

$ cd /u01/app/fmw/oracle_common/common/bin
$ wlst.sh
wls:/offline> nmConnect(domainName='test_domain', username='NMUser', password='NMPasswd')
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/test_domain> nmDisconnect()
Successfully disconnected from Node Manager.
wls:/offline> exit()

How to change the Nodemanager Password in Oracle Apps R12.2

There are two ways to change the Nodemanger password in Oracle apps R12.2 (or) Weblogic.

Weblogic Console:

1. Log in to Admin Console (http://hostname:7001/console).
2. Goto DomainName
3. Security tab
4. General subtab
5. Advanced Options
6. Then change the property Credentials with the new password.

Select Domain

Change password from backend:

1. Go to directory: domain_directory/config/nodemanager
2. Open the file: nm_password.properties
3. Find an entry looking like hashed=abgJGH\= and remove it
4. Fill the following properties with real values as simple text:

• password=
• username=

When you finish your changes remember to restart AdminServer and NodeManager.

If the Admin Password of an EBS WebLogic Domain is lost or forgotten

As noted earlier, the EBS WebLogic domain uses Node Manager to control startup of the AdminServer and Managed Servers. For the EBS WebLogic domain, the Node Manager and WebLogic AdminServer passwords must be same. If the passwords are different, the AD control scripts will not work properly.

If the AdminServer password has been lost or forgotten, it can be reset by carrying out the following steps on the run file system. As described in the final step, an fs_clone operation should then be performed to synchronize the run and patch file systems.

Shut down all running services. Since the AdminServer password is not known, the servers cannot be stopped from the console and so must be killed as follows.

Connect to the Oracle E-Business Suite instance and source the application tier environment file.

Identify the PIDs of Node Manager, AdminServer, and all running Managed Servers:

$ ps -ef | grep "NodeManager"
$ ps -ef | grep "weblogic.Name=AdminServer"
$ ps -ef | grep "weblogic.Name=forms-c4ws_server"
$ ps -ef | grep "weblogic.Name=forms_server"
$ ps -ef | grep "weblogic.Name=oafm_server"
$ ps -ef | grep "weblogic.Name=oacore_server"
Kill all these processes, starting with Node Manager and followed by the Managed Servers.

Back up these folders, and then delete them:

<EBS_DOMAIN_HOME>/security/ DefaultAuthenticatorInit.ldift
<EBS_DOMAIN_HOME>/servers/<server_name>/data/ldap
<EBS_DOMAIN_HOME>/servers/<server_name>/security/boot.properties
<EBS_DOMAIN_HOME>/servers/<server_name>/data/nodemanager/boot.properties

Where:

<EBS_DOMAIN_HOME> is the absolute path of the EBS WebLogic domain

<server_name> is the name of the server directory under <EBS_DOMAIN_HOME>.

If the password is not reset correctly, the backed up files and folders can be restored.

Note: For certain servers, the boot.properties file may be present in only one location of the two specified above. In such a case, back it up and then delete it.

Set up a new environment to change the WLS AdminServer password.

Start a new session and connect to the Oracle E-Business Suite instance.

Do not source the application tier environment file.

Run the following command to source the WebLogic Server domain environment:

$ cd <EBS_DOMAIN_HOME>/bin
$ source setDomainEnv.sh
Run the following commands:

$ cd <EBS_DOMAIN_HOME>/security
$ java weblogic.security.utils.AdminAccount <wls_adminuser> <wls_admin_new_password> .
Where:

<wls_adminuser> is the same as the value of context variable s_wls_admin_user

<wls_admin_new_password> is the new WLS AdminServer password you wish to set.

Note: Do not omit the trailing period ('.') in the above command: it is needed to specify the current domain directory.

Start AdminServer from the command line. You will be prompted for the WebLogic Server username and password, so that the AdminServer boot.properties file can be generated.

Go to the EBS Domain Home:

$ cd <EBS_DOMAIN_HOME>
Start AdminServer:

$ java <s_nm_jvm_startup_properties> -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server
Where:

<s_nm_jvm_startup_properties> is the same as the value of context variable ss_nm_jvm_startup_properties

The above command prompts for the WebLogic Server username and password:

Enter username to boot WebLogic server:
Enter password to boot WebLogic server:
Provide the same credentials as you provided in Step 3.

Change Node Manager password

Log in to the WebLogic Administration console.

Click the 'Lock & Edit' button.

In the left panel, click on the EBS Domain link.

Select the 'Security' tab.

Click on the 'Advanced' link.

Edit the 'Node Manager password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.

Edit the 'Confirm Node Manager Password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.

Save and activate the changes.

The first time, AdminServer has to be stopped from the Admin console. Follow these steps:

Log in to the WebLogic Administration console.

Shut down AdminServer.

Set up your environment to start AdminServer again. AdminServer should now be started using the normal AD script, which will also start Node Manager using the new password.

Launch a new session and connect to the Oracle E-Business Suite instance.

Source the application tier environment file.

Start AdminServer with the following command:

$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
Start the Managed Servers. For the first time, all Managed Servers should be started from the WebLogic Server Admin console. This step will create boot.properties files for the respective Managed Servers. Follow these steps:

Log in to the WebLogic Server Administration Console

Start all Managed Servers, one at a time

Shut down all the Managed Servers. This is so the new credentials will be picked up at the next startup. Follow these steps:

Log in to the WebLogic AdminServer console.

Shut down all Managed Servers.

Shut down AdminServer.

Shut down Node Manager using the normal AD script.

$ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

Copy the boot.properties file for each Managed Server.

WebLogic Server native scripts use the boot.properties file. The above steps have created the boot.properties file under <EBS_DOMAIN_HOME>/servers/<Managed Server name>/data/nodemanager, which is used by Node Manager. For each Managed Server, copy the newly-generated boot.properties file from<EBS_DOMAIN_HOME>/servers/<Managed Server name>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<Managed Server name>/security.

The EBS WebLogic Server domain password has now been changed, and all servers can now be started using the normal AD scripts.

To start AdminServer:

$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

To start the Managed Servers:

$ $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start <managed_server_name>

The above steps have changed the Oracle WebLogic AdminServer password on the run file system. You now need to perform an fs_clone operation, to change the WebLogic EBS Domain password on the patch file system:

Launch a new session and connect to the Oracle E-Business Suite instance.

Source the application tier environment file.

Run the command:

$ adop phase=fs_clone

How to change the Oracle WebLogic Server Administration User Password

The option to set the Oracle WebLogic Server Administration User password to a non-default value is available during Oracle E-Business Suite installation. This section describes the procedure to use (on the run file system) if you need to change the password at a later time.

The EBS WebLogic Domain uses Node Manager to control the Administration Server and the managed servers. For the EBS WebLogic Domain, the Node Manager and WebLogic Server Administration User passwords must be same, otherwise the AD control scripts will not work properly.

Tip: If you need to change the Administration User password, you must change the Node Manager password first. If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The instructions that follow should be performed on the run file system. The password change will be automatically propagated to the patch file system during the next adop prepare phase or fs_clone operation..

Shut down all application tier services except the Admin Server.

On the primary node, run the command:
 $ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

On all secondary nodes, run the command:
 $ <ADMIN_SCRIPTS_HOME>/adstpall.sh

Note: The above examples are for UNIX. If you are using Windows, employ the appropriate equivalent syntax.

Change the Oracle WebLogic Server Administration User password by performing the following steps on the run file system of the primary node.

Source the environment on the run file system.

Run the commands appropriate for your platform:

On UNIX, run the command:

$ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword

Start Node Manager.

When prompted, enter the new password you just set.

Start all services on all nodes, using the command:

 $ <ADMIN_SCRIPTS_HOME>/adstrtal.sh

FRM-92095: Oracle JInitiator version too low.

Getting below error while trying to access the oracle forms.

Cause:

Latest version of Java installed and forms version is not compatible with currently installed JAVA.

Fix:

1. Check and validate the version of java installed in your system.
2. If you already installed latest version of JAVA, Please go and uninstall(via Control Panel > Add/Remove Software)
3. Download the latest version of 1.8 (like 1.8.0_25 to 1.8.0_29) and install.
4. Then try open the application again with same browser.

Navigation:

• Goto Control Panel.
• Search Java
• Click on Java
• Goto Java --> User
• And add runtime parameters.

• We need to set -Djava.vendor="Sun Microsystems Inc." under Run-time Parameters.
• Click ok and click Apply.
• And clear the java cache.
• Try to open the forms.