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.

ENABLE_DDL_LOGGING

ENABLE_DDL_LOGGING enables or disables the writing of a subset of data definition language (DDL) statements to a DDL log.

The DDL log is a file that has the same format and basic behavior as the alert log, but it only contains the DDL statements issued by the database. The DDL log is created only for the RDBMS component and only if the ENABLE_DDL_LOGGING initialization parameter is set to true. When this parameter is set to false, DDL statements are not included in any log.

The DDL log contains one log record for each DDL statement issued by the database. The DDL log is included in IPS incident packages.

There are two DDL logs that contain the same information. One is an XML file, and the other is a text file. The DDL log is stored in the log/ddl subdirectory of the ADR home.

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> show parameter enable_ddl_loggingshow parameter enable_ddl_logging
SQL> show parameter enable_ddl_logging;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
enable_ddl_logging                   boolean     FALSE
SQL> alter system set enable_ddl_logging=TRUE scope=both;

System altered.

SQL> show parameter enable_ddl_logging;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
enable_ddl_logging                   boolean     TRUE

SQL> select value from v$diag_info where name='ADR Home';

VALUE

--------------------------------------------------------------------------------

/u01/app/oracle/12.1.0/admin/diag/rdbms

SQL> select value from v$diag_info where name='ADR Home';

VALUE

--------------------------------------------------------------------------------

/u01/app/oracle//12.1.0/admin//diag/rdbms/

SQL>  create table test(name number);

Table created.

[oracle@test26 ddl]$ pwd

/u01/app/oracle//12.1.0/admin/diag/rdbms/log/ddl

[oracle@test26 ddl]$ cat log.xml

<msg time='2017-02-28T18:01:57.657+05:30' org_id='oracle' comp_id='rdbms'

 msg_id='opiexe:4407:2946163730' type='UNKNOWN' group='diag_adl'

 level='16' host_id='srv-vimats26-int.com' host_addr='172.17.1.226'

 version='1'>

 <txt> create table test(name number)

 </txt>

</msg>

EBS R12.2.5 To R12.2.6 Upgrade Patch: 21900901-peposasd.sql Errors with "The call_procedure does not e xist in the call_package" ORA-06512

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 exist 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

Fix:

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.

Ref  Doc ID 2196150.1

How To Grant / Revoke Privileges For Multiple Discoverer Applications Users / Responsibilities In Batch Mode

In an Oracle Application mode EUL, privileges are usually granted or revoked using Discoverer Administration Edition.
The Discoverer Administration Edition will process one user or responsibility at a time.
Is is possible to grant or revoke the privileges for multiple users / responsibilities in batch mode?

Solution:

Privileges can also be granted or revoked using a Java Command Line utility called EULAPI.
This EULAPI utility is shipped with the Oracle Application Server and has to be executed from the Discoverer server / middle tier environment.

For more information, please refer to the following document:

Oracle Business Intelligence Discoverer EUL Command Line for Java User's Guide 10g Release 2 (10.1.2.1)
Part # B13919-03
Ch 2 Discoverer EUL Command Line for Java Reference

Example 1: To revoke save workbook to database from a responsibility:

$ORACLE_HOME/bin/eulapi \
-connect SYSADMIN/<sysadmin_password>@database \
-eul EUL_US \
-apps_user \
-apps_responsibility "System Administrator" \
-apps_gwuid "APPLSYSPUB/PUB" \
-apps_fndnam APPS \
-revoke_privilege \
-privilege save_workbook_database -role "Discoverer Workbook Management"

Example 2: To grant schedule privilege to users JOE and JCHAN

$ORACLE_HOME/bin/eulapi \
-connect SYSADMIN/<sysadmin_password>@database \
-eul EUL_US \
-apps_user \
-apps_responsibility "System Administrator" \
-apps_gwuid "APPLSYSPUB/PUB" \
-apps_fndnam APPS \
-grant_privilege \
-privilege schedule_workbook \
-user JOE \
-user JCHAN

Example 3: To revoke Save workbook to database, scheduling and sharing workbook in Applications mode EUL

$ORACLE_HOME/bin/eulapi \
-connect SYSADMIN/<sysadmin_password>@database \
-eul EUL_US \
-apps_user \
-apps_responsibility "System Administrator" \
-apps_gwuid "APPLSYSPUB/PUB" \
-apps_fndnam APPS \
-revoke_privilege \
-privilege save_workbook_database \
-privilege schedule_workbook \
-privilege grant_workbook  \
-user "Joe Smith"

NOTE:
1.The above commands need to be in one continuous line. or separated into multiple lines with continuation character "\" .

2. Roles and Responsibilities should be case sensitive and enclosed in double quotes as long as they have multiple words.

Ref Doc ID 420357.1

How to change the apps password in Oracle E-Business Suite R12.2

Below steps to change the apps password in Oracle E-Business Suite R12.2

Step 1:

Shut down all the application services by using below script.
$INST_TOP/admin/scripts/adstpall.sh

Step 2:
Change the APPLSYS password by using FNDCPASS
$FNDCPASS apps/<appspwd> 0 Y system/manager SYSTEM APPLSYS WELCOME

Step 3:
Run autoconfig with the newly changed password.

Step 4:
Start AdminServer using the $INST_TOP/admin/scripts/adadminsrvctl.sh script. (Do not start any other application tier services).

Step 5:
Change the "apps" password in WLS Datasource as follows:

a) Log in to WLS Administration Console.
b) Click Lock & Edit in Change Center.
c) In the Domain Structure tree, expand Services, then select Data Sources.
d) On the "Summary of JDBC Data Sources" page, select EBSDataSource.
e) On the "Settings for EBSDataSource" page, select the Connection Pool tab.
f) Enter the new password in the "Password" field.
g) Enter the new password in the "Confirm Password" field.
h) Click Save.
i) Click Activate Changes in Change Center.

Step 6:
Start all the application tier services using the below script
$INST_TOP/admin/scripts/adstrtal.sh

Step 7:
Verify the WLS Datastore changes as follows:

a) Log in to WLS Administration Console.
b) In the Domain Structure tree, expand Services, then select Data Sources.
c) On the "Summary of JDBC Data Sources" page, select EBSDataSource.
d) On the "Settings for EBSDataSource" page, select Monitoring > Testing.
e) Select "oacore_server1".
f) Click Test DataSource
g) Look for the message "Test of EBSDataSource on server oacore_server1 was successful".

weblogic.nodemanager.common.ConfigException: Identity key store file not found: DemoIdentity.jks (SOA 12c)

We are getting below error while starting Node-manager in weblogic 12c server. Below is the steps to resolve the issue.

Error Message:

+ /usr/java/jdk1.8.0_112/bin/java -server -Xms32m -Xmx200m -Dweblogic.RootDirectory=/u01/soa_12c/Middleware/MW_Home/wlserver/../oracle_common/common/nodemanager -Dcoherence.home=/u01/soa_12c/Middleware/MW_Home/wlserver/../coherence -Dbea.home=/u01/soa_12c/Middleware/MW_Home/wlserver/.. -Xverify:none -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.security.policy=/u01/soa_12c/Middleware/MW_Home/wlserver/server/lib/weblogic.policy -Dweblogic.nodemanager.JavaHome=/usr/java/jdk1.8.0_112 weblogic.NodeManager -v

<Nov 29, 2016 9:25:18 AM IST> <INFO> <Loading domains file: /u01/soa_12c/Middleware/MW_Home/oracle_common/common/nodemanager/nodemanager.domains>

<Nov 29, 2016 9:25:18 AM IST> <WARNING> <Domains file not found: /u01/soa_12c/Middleware/MW_Home/oracle_common/common/nodemanager/nodemanager.domains>

<Nov 29, 2016 9:25:22 AM IST> <INFO> <Loading identity key store: FileName=/u01/soa_12c/Middleware/MW_Home/oracle_common/common/nodemanager/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>

<Nov 29, 2016 9:25:22 AM IST> <SEVERE> <Fatal error in NodeManager server>

weblogic.nodemanager.common.ConfigException: Identity key store file not found: /u01/soa_12c/Middleware/MW_Home/oracle_common/common/nodemanager/security/DemoIdentity.jks

        at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.java:225)

        at weblogic.nodemanager.server.SSLConfig.access$000(SSLConfig.java:33)

        at weblogic.nodemanager.server.SSLConfig$1.run(SSLConfig.java:118)

        at java.security.AccessController.doPrivileged(Native Method)

        at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:115)

        at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:143)

        at weblogic.nodemanager.server.NMServer.main(NMServer.java:527)

        at weblogic.NodeManager.main(NodeManager.java:31)

+ status=1

+ set +x

Fix:

Copy the file <domainhome>/security/DemoIdentity.jks to  <domainhome>/nodemanager/security/DemoIdentity.jks

Copy the file <domainhome>/security/DemoIdentity.jks to  <MW_Home>/oracle_common/common/nodemanager/security/DemoIdentity.jks

How to find weblogic server version in E-Business Suite R12.2.5

Below steps to find the Weblogic server version in E-Business Suite R12.2.5

Step 1:

Goto $FMW_HOME

[applmgr@test26 FMW_Home]$ pwd
/u01/app/applmgr/TEST/fs1/FMW_Home

[applmgr@test26 FMW_Home]$ grep -I version registry.xml

<?xml version="1.0" encoding="UTF-8"?><bea-product-information xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:gpr="http://www.bea.com/ns/cie/gpr">

        <component name="Common Infrastructure Engineering" version="7.4.0.0" InstallDir="">

        <component name="WebLogic Server" version="10.3.6.0" InstallDir="/u01/app/applmgr/BODHTREE/fs1/FMW_Home/wlserver_10.3">

        <component name="Oracle Configuration Manager" version="10.3.5.0" InstallDir="">

Step 2:

Login to http://<server_name>:port/console

BI AppS ETL fails with the 'ORA-01792: maximum number of columns in a table or view is 1000' Error Message

We are getting below error while loading the data into BI APPS server .

Error:

Caused By: java.sql.SQLSyntaxErrorException: ORA-01792: maximum number of columns in a table or view is 1000

                at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
                at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
                at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
                at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
                at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
                at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
                at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
                at oracle.jdbc.driver.T4CPreparedStatement.executeForRows => ORA-20942:

Fix:

The workaround is to set "_fix_control"='17376322:OFF'

SQL> alter session set "_fix_control"='17376322:OFF';

or at system level :

SQL> alter system set "_fix_control"='17376322:OFF';

 

OR

Apply Patch 19509982 if available for your DBVersion and Platform

Weblogic Server 12.1.2 Performance Issue Due To weblogic.socket.NIOSocketMuxer

Weblogic server 12.1.2 in a runnable state consuming high CPU resources.

Error:

"LDAPConnThread-579 ldaps://ldapserver.us.oracle.com:636" daemon prio=10 tid=0x00000000041f6800 nid=0x56d7 runnable [0x00007f9b6b9f8000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.IOUtil.drain(Native Method)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:90)
- locked <0x000000078a2f6e48> (a java.lang.Object)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
- locked <0x000000078a2f6b48> (a sun.nio.ch.Util$2)
- locked <0x000000078a2f6b38> (a java.util.Collections$UnmodifiableSet)
- locked <0x000000078a2f6910> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
at weblogic.socket.NIOSocketMuxer$NIOInputStream.readInternal(NIOSocketMuxer.java:815)
at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:759)
at weblogic.socket.NIOSocketMuxer$NIOInputStream.read(NIOSocketMuxer.java:742)
at weblogic.socket.JSSEFilterImpl.readFromNetwork(JSSEFilterImpl.java:462)
at weblogic.socket.JSSEFilterImpl.read(JSSEFilterImpl.java:424)
at weblogic.socket.JSSESocket$JSSEInputStream.read(JSSESocket.java:64)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
- locked <0x000000079c2dc630> (a java.io.BufferedInputStream)
at netscape.ldap.ber.stream.BERElement.getElement(Unknown Source)
at netscape.ldap.LDAPConnThread.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)


Fix:

In this case, as customer was using Linux x86-64, changing the MuxerClass from weblogic.socket.NIOSocketMuxer to weblogic.socket.PosixSocketMuxer worked.

In WLS Admin Console

Go to Environment > Servers > Server Name > Tuning, under Advanced, set the Muxer Class based on the OS and Reboot the server.

Solaris/HP-UX Native Muxer : weblogic.socket.DevPollSocketMuxer
POSIX Native Muxer : weblogic.socket.PosixSocketMuxer
Windows Native Muxer : weblogic.socket.NTSocketMuxer

Java Muxer : weblogic.socket.JavaSocketMuxer

You may also set the above in the Weblogic startup scripts via the JAVA_OPTIONS:
-Dweblogic.MuxerClass=weblogic.socket.PosixSocketMuxer

Weblogic console page is not coming up after server reboot

We have bounced the server and restarted the weblogic services. After restating the services we are unable to access the console page.

Cause:

We found that Linux firewalls are enabled the server. When we rebooted the server, by detault iptables got restarted.

To check the status of your firewall and all rules, enter:
# iptables -L -n (as root user)

Fix:

Stop the ipchains service(as root user):
# service ipchains stop

Stop the iptables service:
# service iptables stop

Stop the ipchains service from starting when you restart the server:
# chkconfig ipchains off

Stop the iptables service from starting when you restart the server:
# chkconfig iptables off

Ora-12547: tns:lost contact 12c

We are unable to access the jdbc url and sql developer after configuring E-Business suite R12.2.5

Error:

I/O Error: Connection Reset
ora-12547: tns:lost contact 12c

Fix:

Backup the sqlnet.ora file from both DB and Apps side and comment the below parameters.

#tcp.validnode_checking = yes
#tcp.invited_nodes=(hostname)

libmawt.so: libXi.so.6: cannot open shared object file: No such file or directory

We are getting below error while installing BI APPS rcu.

Error:

[oracle@test-krishna bin]$ ./rcu
Exception in thread "main" java.lang.UnsatisfiedLinkError: /u01/Softs/weblogic/rcu_obi/jdk/jre/lib/i386/xawt/libmawt.so: libXi.so.6: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703)
at java.lang.Runtime.load0(Runtime.java:770)
at java.lang.System.load(System.java:1003)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.loadLibraries(Toolkit.java:1605)
at java.awt.Toolkit.<clinit>(Toolkit.java:1627)
at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:484)
at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249)
at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135)
at oracle.sysman.assistants.rcu.ui.InteractiveRCUModel.<init>(InteractiveRCUModel.java:117)
at oracle.sysman.assistants.rcu.Rcu.execute(Rcu.java:307)
at oracle.sysman.assistants.rcu.Rcu.main(Rcu.java:363)


Fix:

[root@test-krishna Desktop]# yum install libXtst.i686

Resolving Dependencies
--> Running transaction check
---> Package libXtst.i386 0:1.0.1-3.1 will be updated
---> Package libXtst.i686 0:1.2.2-2.1.el6 will be an update
--> Processing Dependency: libXi.so.6 for package: libXtst-1.2.2-2.1.el6.i686
--> Running transaction check
---> Package libXi.i686 0:1.7.4-1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================
 Package                                 Arch                                 Version                                        Repository                            Size
========================================================================================================================================================================
Updating:
 libXtst                                 i686                                 1.2.2-2.1.el6                                  base                                  19 k
Installing for dependencies:
 libXi                                   i686                                 1.7.4-1.el6                                    base                                  37 k

Transaction Summary
========================================================================================================================================================================
Install       1 Package(s)
Upgrade       1 Package(s)

Total download size: 55 k
Is this ok [y/N]: Y
Downloading Packages:
(1/2): libXi-1.7.4-1.el6.i686.rpm                                                                                                                |  37 kB     00:00
(2/2): libXtst-1.2.2-2.1.el6.i686.rpm                                                                                                            |  19 kB     00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                    55 kB/s |  55 kB     00:01
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing : libXi-1.7.4-1.el6.i686                                                                                                                               1/3
  Updating   : libXtst-1.2.2-2.1.el6.i686                                                                                                                           2/3
  Cleanup    : libXtst-1.0.1-3.1.i386                                                                                                                               3/3
  Verifying  : libXi-1.7.4-1.el6.i686                                                                                                                               1/3
  Verifying  : libXtst-1.2.2-2.1.el6.i686                                                                                                                           2/3
  Verifying  : libXtst-1.0.1-3.1.i386                                                                                                                               3/3

Dependency Installed:
  libXi.i686 0:1.7.4-1.el6

Updated:
  libXtst.i686 0:1.2.2-2.1.el6

Complete!