ORA-29548: Java system class reported: release of Java system classes in the database (12.1.0.2.0 1.6) does not match that of the oracle executable (12.1.0.2.180116 1.6)

We have faced the below error while applying the below patch in Oracle E-Business Suite 12.2.7 (Upgrade).

Patch: adop phase=apply patches=25828573 hotpatch=yes

Issue: 
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at line 6
ORA-29548: Java system class reported: release of Java system classes in the
database (12.1.0.2.0 1.6) does not match that of the oracle executable

(12.1.0.2.180116 1.6)

Fix:
SQL> sho user
USER is "SYS"
SQL> @?/javavm/install/update_javavm_db.sql
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL>
SQL> alter session set "_ORACLE_SCRIPT"=true;

Session altered.

SQL>
SQL> -- If Java is installed, do CJS.
SQL>
SQL> -- If CJS can deal with the SROs inconsistent with the new JDK,
SQL> -- the drop_sros() call here can be removed.
SQL> call initjvmaux.drop_sros();

Call completed.

SQL>
SQL> create or replace java system;
  2  /

Java created.

SQL>
SQL> update dependency$
  2    set p_timestamp=(select stime from obj$ where obj#=p_obj#)
  3    where (select stime from obj$ where obj#=p_obj#)!=p_timestamp and
  4          (select type# from obj$ where obj#=p_obj#)=29  and
  5          (select owner# from obj$ where obj#=p_obj#)=0;

0 rows updated.

SQL>
SQL> commit;

Commit complete.

SQL>
SQL> alter session set "_ORACLE_SCRIPT"=false;

Session altered.

SQL> select dbms_java.get_jdk_version() from dual;

DBMS_JAVA.GET_JDK_VERSION()
--------------------------------------------------------------------------------
1.6.0_181

1 row selected.


SQL> select dbms_java.longname('TEST') from dual;

DBMS_JAVA.LONGNAME('TEST')
--------------------------------------------------------------------------------
TEST

1 row selected.

Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded : bsu.sh

We have faced java memory issue while applying weblogic patches in Oracle E-Business Suite R12.2.7

Error:
[applmgr@test bsu]$ ./bsu.sh -install -patch_download_dir=/u01/app/applmgr/TEST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=EQDE -prod_dir=/u01/app/applmgr/TEST/fs1/FMW_Home/wlserver_10.3
Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
        at org.apache.xmlbeans.impl.schema.SchemaTypeImpl.getProperties(SchemaTypeImpl.java:704)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.loadPropertyMap(XBeanDataHandler.java:775)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.<init>(XBeanDataHandler.java:99)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.createDataHandler(XBeanDataHandler.java:559)
        at com.bea.cie.common.dao.xbean.XBeanDataHandler.getComplexValue(XBeanDataHandler.java:455)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:442)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)
        at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)
        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)
        at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)
        at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)
        at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)
        at com.bea.plateng.patch.Patch.main(Patch.java:281)
[

Reason:

The default java memory arguments  provided in bsu.sh file are not sufficient for patching activity (./bsu.sh)

Fix:

Increase the Java memory values in bsu.sh file (under $MW_HOME/utils/bsu) by increasing the value MEM_ARGS values.

Default Value:

MEM_ARGS="-Xms512m -Xmx1024m"

Changed Values:

MEM_ARGS="-Xms1024m -Xmx2048m"

Save the bsu.sh file and restart the patching activity.

How to find the Weblogic Admin Console URL Location in Oracle OEM?

 We can find the details from setupinfo.txt file. This file is created during the installation time.

 Location: $ORACLE_HOME/oms/install/setupinfo.txt 

 Output: 

Use the following URL to access:

        1. Enterprise Manager Cloud Controls URL: https://test.oracle.com:7802/em
        2. Admin Server URL: https://test.oracle.com:7102/console

The following details need to be provided during the additional OMS install:

        1. Admin Server Hostname: test.oracle.com

        2. Admin Server Port: 7102

IO Error: Got minus one from a read call vendor code 17002

When we are trying to connect database by using Sql developer, we got below error.

Error:

IO Error: Got minus one from a read call vendor code 17002

Fix:

You can follow these steps to avoid the error:

1. Go to directory $ORACLE_HOME/network/admin
2. Make sure you have backup of sqlnet.ora
3. Modify sqlnet.ora file with the parameter: (tcp.validnode_checking = no)
4. If you don't want to disable this, you can put the machine names as follows:  tcp.invited_nodes=(machine1, machine2)
5. Bounce the listener or reload the listner (lsnrctl reload)

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

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

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!

How to Configuring Node Manager to Start Managed Servers

If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter Portal, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, which are located in the following directory:

$DOMAIN_HOME/bin

If the Managed Servers are started by Node Manager (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control), Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true.

There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true to the nodemanager.properties file:

$ORACLE_COMMON_HOME/common/bin/setNMProps.sh.

For example, on Linux, execute the setNMProps script and start Node Manager:

ORACLE_COMMON_HOME/common/bin/setNMProps.sh
MW_HOME/wlserver_n/server/bin/startNodeManager.sh

When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.

Also note that when the StartScriptEnable property is set to true, the Node Manager reads the startWebLogic script, which in turns reads the setDomainEnv script. As a result, you must make any tuning changes by editing the setDomainEnv script. Any changes that are performed using the command line or Administration Console will not be implemented when Node Manager starts the servers. For example, if you use the Administration Console to change the server start arguments, those changes are written to config.xml, but the Node Manager ignores these settings and uses those in setDomainEnv.

RCU/jdk/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory

I got this error while installing RCU on OEL6.

$ ./rcu
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/Installation/rcu/rcuHome/jdk/jre/lib/i386/xawt/libmawt.so:
libXtst.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:1778)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1674)
        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:1778)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1695)
        at java.lang.Runtime.loadLibrary0(Runtime.java:823)
        at java.lang.System.loadLibrary(System.java:1028)

Cause: 
libXtst rpm for 32 bit is missing.

Fix:
Please check that the libXtst-xx.el6.i686.rpm (32 bit) installed.
rpm -qa |grep libXtst
If it is not installed the need to install:
rpm -ivh libXtst-xx.el6.i686.rpm

INST-08109: An ORACLE_HOME environment variable should not be defined

I got the below error while installing Oracle BI 11.1.1.9 on Linux 5.7.

Error :

INST-08109: An ORACLE_HOME environment variable should not be defined

Fix:

unset ORACLE_HOME and try to re-install.

Insufficient free space in /tmp while installing SOA 12c

$JAVA_HOME/java -jar fmw_12.1.3.0.0_soa_quickstart.jar

Insufficient free space in /tmp/orcl4316142800341622207.tmp to extract the installer.  Actual 365 MB.  Required 3053 MB.

In my case we don't have free space under /tmp mount. So i have created /tmp directory under different location.

Fix:

1. mkdir -p /u01/tmp
2. chmod -R 777 /u01/tmp
3. export _JAVA_OPTIONS="-Djava.io.tmpdir=/u01/tmp"
4. java -jar fmw_12.1.3.0.0_soa_quickstart.jar

CXF Error Deploying Updated p6ws.war File

Getting below error message while deploying the p6ws.war File

Error:

Servlet: "cxf" failed to preload on startup in Web application: "p6ws.war".
java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in URL [zip:/home/weblogic/Oracle/Middleware/user_projects/domains/iALM/servers/AdminServer/tmp/_WL_user/p6ws/nmdpik/war/WEB-INF/lib/cxf-bundle.jar!/META-INF/cxf/cxf.fixml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: javax/wsdl/WSDLException

Cause:

The wsdl4j-1.6.2.jar is missing from the p6ws.ear/p6ws.war file.

Fix:

1. In the <P6 Web Services Home Directory> edit the updateWSWar.cmd or updateWSWar.sh file. Ensure the CXF_HOME path is set to the folder where wsdl4j-1.6.2.jar has been copied.
2. Save and execute the updateWSWar file to update the p6ws.ear/p6ws.war file.
3. Redeploy the p6ws.ear/p6ws.war file.

How to install and uninstall weblogic bsu patches

Install .bsu patch in weblogic:

bsu.sh -install -patch_download_dir=/u002/app/applmgr/RYSAAV3/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=FCX7 -prod_dir=/u002/app/applmgr/RYSAAV3/fs1/FMW_Home/wlserver_10.3

Uninstall .bsu patch in weblogic:

bsu.sh -remove -patchlist=BLTG -prod_dir=/u002/app/applmgr/RYSAAV3/fs1/FMW_Home/wlserver_10.3

bsu.sh -remove -patchlist=FCX7 -prod_dir=/u002/app/applmgr/RYSAAV3/fs1/FMW_Home/wlserver_10.3