Tuesday, March 12, 2013

Running AutoConfig On DB Node Fails with: UnsatisfiedLinkError Exception Loading Native Library: njni11

Running AutoConfig On DB Node Reports: UnsatisfiedLinkError Exception Loading Native Library: njni11 after database cloning while running autoconfig below is the error.


Context Value Management will now update the Context file
UnsatisfiedLinkError exception loading native library: njni11
java.lang.UnsatisfiedLinkError: njni11 (No such file or directory)

        Updating Context file...COMPLETED

        Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db112
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

This issue because of Database 11.2 it only comes with 64bit libraries, but we are still trying to use 32bit java as defined by context variables s_jdktop and s_jretop which points to ORACLE_HOME/appsutil/jre

Therefore changed the s_jdktop and s_jretop in $CONTEXT_FILE  to point to $ORACLE_HOME/jdk/jre and executed the autoconfig and it was successful without any error.

Context Value Management will now update the Context file

        Updating Context file...COMPLETED

        Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db112
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

1 comment:

  1. I am not sure where you're getting your information, but
    great topic. I needs to spend some time learning more or understanding more.
    Thanks for excellent information I was looking for this info for my mission.


    my webpage Payday Loan Windsor Ontario, shaunscribner.pen.io,

    ReplyDelete