Skip to main content

How to check whether JVM for Oracle is installed or not in database?

During a PSU check I saw a list of patches that are recommended. I saw a list that has JVM and the DB bundled. I wasn't sure what this was and which one I should apply. After some digging around I understood that I could check whether I had JVM installed on the database although now I understand that with EBS it will probably be used by the database. This quick and dirty SQL will give you a list of components loaded into the database. One of which will be JServer JAVA Virtual Machine Release XXXXXXX. If its not there you probably don't have it installed.

SQL> set pages 100
SQL> select * from all_registry_banners;
BANNER
--------------------------------------------------------------------------------
Oracle Database Catalog Views Release 11.2.0.4.0 - 64bit Production
Oracle Database Packages and Types Release 11.2.0.4.0 - Development
JServer JAVA Virtual Machine Release 11.2.0.4.0 - Development
Oracle XDK Release 11.2.0.4.0 - Development
Oracle Database Java Packages Release 11.2.0.4.0 - Development
Oracle Expression Filter Release 11.2.0.4.0 - Development
Oracle XML Database Release 11.2.0.4.0 - Development
Oracle Multimedia Release 11.2.0.4.0 - Development
Spatial Release 11.2.0.4.0 - Development
OLAP Analytic Workspace Release 11.2.0.4.0 - Development
Oracle OLAP API Release 11.2.0.4.0 - Development
OLAP Catalog Release 11.2.0.4.0 - Development
Oracle Data Mining Release 11.2.0.4.0 - Development
Oracle Text Release 11.2.0.4.0 - Development
Oracle Application Express Release 4.0.2.00.07 - Production
Oracle Enterprise Manager Release 11.2.0.4.0 - Development


References:

Comments

Popular posts from this blog

Cancel or abort adop session

ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session.
adop phase=abort
adop phase=cleanup cleanup_mode=full

Creating new WLS domain ends with exit code 255

Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file.
START: Creating new WLS domain.
Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt
Script Executed in 1903 milliseconds, returning status 255
ERROR: Script failed, exit code 255

Dig a bit deeper into the log files
cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply
cat CLONE2016-01-10_04-37-11PM.log

Failed to initialize the application 'EBSDataSource' due to error weblogic.application.ModuleException after FNDCPASS apps change

Started testing password changes in our clone environments. Weblogic seems to love throwing you curve balls and when I changes the apps password with the below:
FNDCPASS apps/$APPS_PASS 0 Y system/system SYSTEM APPLSYS $APPS_PASS
I was not able to start the weblogic managed servers. A look in the log an I found this:

weblogic.application.ModuleException:
        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
        at weblogic.application.internal.BaseDep…