Troubleshooting Blank Screen on EBS R12 on OCI Post Cloning

Troubleshooting Blank Screen
Oracle

Share Post Now :

HOW TO GET HIGH PAYING JOBS IN AWS CLOUD

Even as a beginner with NO Experience Coding Language

Explore Free course Now

Table of Contents

Loading

In this blog post, we’ll be seeing how to troubleshoot the blank screen at AppsLocalLogin.jsp post cloning an EBS R12 on OCI with database tier on Exadata Cloud Service.

This was an error encountered by one of our trainees of EBS On OCI Training while performing the cloning EBS 12.1.3 manually (without EBS Cloud Manager).

Registered for the Free Masterclass on How To Transition From An Oracle Apps DBA To Oracle Cloud Apps DBA?

If you don’t know about EBS Cloud Manager, check our previous blog post on Oracle EBS(R12) Cloud Manager Overview: What & How & also check our hands-on guide on Oracle Exadata Cloud Service

Problem Statement

After cloning EBS 12.1.3 manually (without EBS Cloud Manager) from Exadata On-Premise to Oracle Cloud (OCI),  all services are up and functional. However, when we type the URL we are redirected to /OA_HTML/AppsLocalLogin.jsp and the page was blank.

Troubleshooting 

Step 1(a). Check the application log
$INST_TOP/logs/ora/10.1.3/j2ee/oacore/oacore_default_group_1/application.log
No error found
Step 1(b). Increase OC4J logging for oacore and Enable debugging mode
i) edit j2ee-logging.xml, adjust the following in the file:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/j2ee-logging.xml
<logger name=’oracle’ level=’TRACE:32′ useParentHandlers=’false’>
ii) edit orion-web.xml, adjust the following in the file:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml
param-name>debug_mode</param-name>
<param-value>true</param-value>
No error in application log even after debugging mode is enabled
Step 2.  Check DB alert log
/u02/app/oracle/diag/rdbms/prd_exacs1/PRD/trace/alert_PRD.log
joxcsys: release mismatch 12.1.0.2.190716 1.6 in database (classes.bin) vs 12.1.0.2.190416 1.6 in executable
SQL> select dbms_java.get_jdk_version() from dual;
select dbms_java.get_jdk_version() from dual
*
ERROR at line 1:
ORA-29548: Java system class reported: release of Java system classes in the
database (12.1.0.2.190716 1.6) does not match that of the oracle executable
(12.1.0.2.190416 1.6)
Error is found in the alert log

Root Cause

The JVM is found to be corrupted in the process of cloning which can be verified by using the above command

Fix

We recreate the JVM in order to fix the error
SQL> @?/javavm/install/update_javavm_db.sql
SQL> select dbms_java.get_jdk_version() from dual;
DBMS_JAVA.GET_JDK_VERSION()
——————————————————————————–
1.6.0_211
1 row selected.
Test login again. The error has now been fixed.

Related/References

  • 2189241.1  After Recent Clone Login Page Not Loading, Received Java Error Message
  • 2199288.1  Joxcsys: Release Mismatch 11.2.0.4.2 In Database (classes.bin) Vs 11.2.0.4.6 In Executable
  • 422419.1  R12, 12.1 How To Enable and Collect Debug for HTTP, OC4J and OPMN
  • 734692.1  Blank Page Accessing R12 – Application.log shows “html: chain failed”, “Unable to create user session”
  • 832568.1  After Upgrade to R12 Login Displays a Blank Page

Next Task For You

If you are an Oracle AppsDBA and would like to learn about migrating Oracle E-Business Suite from On-Premises to Oracle Cloud and earn more, then attend our FREE CLASS which includes topics like Migration Strategy & Checklist, EBS Migration (Lift & Shift) Options, Near Zero Downtime, 8-week roadmap to upgrade from Apps DBA to Cloud Apps DBA, being an Expert on Oracle Cloud and many more.

Click on the below image to join the Free Masterclass Now!

Picture of mike

mike

I started my IT career in 2000 as an Oracle DBA/Apps DBA. The first few years were tough (<$100/month), with very little growth. In 2004, I moved to the UK. After working really hard, I landed a job that paid me £2700 per month. In February 2005, I saw a job that was £450 per day, which was nearly 4 times of my then salary.