Opatch java.lang.UnsatisfiedLinkError: no oraInstaller in java.library.path wrong ELF class: ELFCLASS64

I got this error when trying to deploy an interim patch for soa installation using opatch on Solaris.




Opatch java.lang.UnsatisfiedLinkError: no oraInstaller in java.library.path wrong ELF class: ELFCLASS64


oracle@xxxxxxx:[/u01/app/oracle/product/11.1.1.5/ofm1/fms/soa/patch_top/13683187]# opatch apply

The above error indicates that the opatch has encountered a 64 bit library while it was expecting a 32 bit, that means opatch was started as a 32 bit jvm. The java installation in the solaris box had both 32 bit and 64 bit jvms. So by default OPatch was starting as a 32 bit jvm , while the soa installation/ora installer on the ORACLE_HOME was 64 bits. The fix for this is to update the opatch script to add the “-d64″ flag so that opatch starts as a 64 bit jvm.




$JAVA -d64 $JAVA_VM_OPTION $JRE_MEMORY_OPTIONS -cp $BASE/ocm/lib/emocmutl.jar:$BASE/ocm/lib/emocmclnt.jar:$CP/OraInstaller.jar:$CP/OraPrereq.jar:$CP/share.jar:$CP/srvm.jar:$CP/orai18n-mapping.jar:$CP/xmlparserv2.jar:$BASE/jlib/opatch.jar:$BASE/jlib/opatchutil.jar:$BASE/jlib/opatchprereq.jar:$BASE/jlib/opatchactions.jar:$BASE/jlib/opatchext.jar:$BASE/jlib/opatchfmw.jar:$WEBLOGIC_CLASSPATH -DOPatch.ORACLE_HOME=$OH -DOPatch.DEBUG=$DEBUGVAL -DOPatch.RUNNING_DIR=$BASE -DOPatch.MW_HOME=$MWH -DOPatch.WL_HOME=$WL_HOME -DOPatch.COMMON_COMPONENTS_HOME=$COMMON_COMPONENTS_HOME ${oracleOcmService} ${_bootClassPath} oracle/opatch/OPatch $@      

One more possible cause of Unsatisfied linked error in linux is incorrect LD_LIBRARY_PATH, if .so files are not there you may get this error. see http://javarevisited.blogspot.sg/2012/03/javalangunsatisfiedlinkerror-no-dll-in.html for more details

This host is VT-capable, but VT is disabled

While starting VM on 64 bit, got following error -

This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.

This host is VT-capable, but VT is disabled.

VT might be disabled if it has been disabled in the BIOS settings or the host has not been power-cycled since changing this setting.

(1) Verify that the BIOS settings enable VT and disable 'trusted execution.'

(2) Power-cycle the host if either of these BIOS settings have been changed.

(3) Power-cycle the host if you have not done so since installing VMware Player.

(4) Update the host's BIOS to the latest version.

For more detailed information, see http://vmware.com/info?id=152.

Continue without 64-bit support?

Resoulution -

We are still trying to determine what causes this problem on some systems.  In the meantime, as a workaround, please add the following line to C:\ProgramData\VMware\VMware Workstation\config.ini:

hv.assumeEnabled = TRUE

Note that ProgramData is a hidden folder.

new error - 

*** VMware Player internal monitor error ***

vcpu-0:VT is disabled and locked on this CPU.

Solution -


Go to BIOS setup- 
- Restore CMOS factory default setting
- Make sure to enable Virtulization Technology
- Cold boot the system

Issue solved ... :)

DIP Issue :Unable to locate the DIP Sync profile mbean

Dip shows two red down arrows in EM for both Quartz Scheduler and MBeans, yet the DIP(11.1.1.2.0) shows a green up arrow.

When I try to perform a connection test (right click on DIP--->Administration---->Server Properties), I get the following error.

The connection test could not be performed.
The test aborted with the message : Unable to locate the DIP Sync profile mbean - :oracle.idm.integration.sync.config:*:
Unable to locate the DIP Sync profile mbean - :oracle.idm.integration.sync.config:*:
java.lang.Exception: Unable to locate the DIP Sync profile mbean - :oracle.idm.integration.sync.config:*:
at oracle.sysman.emas.model.iam.dip.utl.DIPJMXHelper.getSyncProfileObjectName(DIPJMXHelper.java:244)
at oracle.sysman.emas.model.iam.dip.utl.DIPJMXConfigSetHelper.testEndPoint(DIPJMXConfigSetHelper.java:706)
at oracle.sysman.emas.model.iam.dip.utl.DIPJMXConfigSetHelper.testEndPointConnection(DIPJMXConfigSetHelper.java:684)
at oracle.sysman.emas.view.iam.dip.DIPIntgProfileView.testConfigSetLDAPConnection(DIPIntgProfileView.java:2436)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)



Sloution :

the issue was related to the order in which I started the components.


http://docs.oracle.com/cd/E15523_01/oid.1111/e10029/app_stopstart.htm

As per this link:

Start admin server

Start OID instance (opmnctl startall)

Start managed server

OAM11.1.1.5 Issue -Obrareq Query String Integrity Check Failed

Refer below article on oracle support-

OAM 11g Obrareq Query String Integrity Check Failed [ID 1463026.1]

RCU Error - SYS account can’t login remotely

When Setup OID/OAM, not able to use sys or system account to create as reqired as SYS/SYSTEM can’t login remotely.

Workarround solution is to create temporally dba account for the setup.

When Setup OID using RCU, failed on following statement due to SYS account can’t login remotely.

Grant job execute right to ODS.

Modify /var/opt/oracle/inventoryLoc

Dir=/u01/iam/inventoryDirecotry

Group=fmw

Issue with OID install and Configure

I found following issue while installing OID11.1.1.6 -

During IDM installation, I selected the option "Install and Configure".
Installation set up is successful. But it failed while configuring Oracle Identity Management Components - step2 - Start Oracle Internet Directory - Failed.
Checked the log -
0000JezC4hb4iogEtF2jKH1G^noc000003,0] Failed to start component oid1[[
oracle.as.config.ProvisionException: HTTP status code = 400 : The request parameters did not match any components

Check the oidmon diagnostics log file  oidmon-0000.log and oidldapd01-0000.log, and I see this:

Connected to incorrect OID base schema version, (version=11.1.1.4.0). WARNING: OID server (version 11.1.1.6.0) is now operating in read_only mode

Solution:

I did some checking, and ran this SQL, e.g.:

SQL> SELECT owner, version, status FROM schema_version_registry;

OWNER VERSION STATUS

---

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

---

DEV_IAU 11.1.1.6.0 VALID
DEV2_IAU 11.1.1.6.0 VALID
DEV2_MDS 11.1.1.6.0 VALID
ODS 11.1.1.6.0 VALID

which seems to show that the ODS schema is 11.1.1.6 now, but, this:

SQL>select attrval from ods.ds_attrstore where entryid =1 and attrname = 'orcld
irectoryversion';

ATTRVAL

---

OID 11.1.1.4.0

seems to indicate that the schema is still setup for 11.1.1.4?

I finally found this:
http://newappsdba.blogspot.com/2009_09_01_archive.html

where it suggested running an update to force the orcldirectoryversion:

So, I did that:

SQL> update ods.ds_attrstore set attrval='OID 11.1.1.6.0' where entryid=1 and attrname='orcldirectoryversion';

1 row updated.

SQL> commit;

Commit complete.

SQL> select attrval from ods.ds_attrstore where entryid=1 and attrname='orcldirectoryversion';

ATTRVAL

---

OID 11.1.1.6.0

Then, I tried starting the OID processes, and got:

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
ohs1 | OHS | 1584 | Alive
ovd1 | OVD | 1592 | Alive
oid1 | oidldapd | 1820 | Alive
oid1 | oidldapd | 1752 | Alive
oid1 | oidmon | 1600 | Alive
EMAGENT | EMAGENT | 1576 | Alive
All the best... :)

If ODS schema version is correct then try recreating the schema or recreating the database.

Regards
Santosh Shukla