Quantcast
Channel: Cloud Training Program
Viewing all articles
Browse latest Browse all 1902

[Troubleshooting] Blank Screen on EBS R12 on OCI Post Cloning

$
0
0

In this blog, 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

Next Task For You

If you are an Oracle Apps DBA and would like to upgrade yourself to a Cloud Apps DBA and earn more, then attend our free masterclass which includes topics like Database Deployment Options in Oracle Cloud, Certification for DBAs in Oracle Cloud, 12 Weeks Roadmap to being an Expert on Oracle Cloud Apps DBA and many more.

Click on the below image to access the FREE Masterclass.

The post [Troubleshooting] Blank Screen on EBS R12 on OCI Post Cloning appeared first on Oracle Trainings.


Viewing all articles
Browse latest Browse all 1902

Trending Articles