Internal 500 Error frequently in Oracle EBS 12.1.3 due to Long running JVM

Internal 500 Error frequently in Oracle EBS 12.1.3

Symptoms: Sometimes those kind of error is also caused by firewall between concurrent manager node vs web node or database vs web node. Hence ensure to open the required firewall port.

Alternative Solution(Turn off Long running JVM) using below steps)

In case the above solutions does not solve the issue, then following steps can also be carried out after taking proper backup of the system

1. Remove any *.lock files in $ORA_CONFIG_HOME/10.1.3/j2ee//persistence//

2. Set the parameter LONG_RUNNING_JVM=false present in $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/oc4j.properties and bounce oacore and test the result.

appsdbahelp

17+ years of experience in Oracle Database, Oracle Cloud Infrastructure(OCI), Oracle EBS on Cloud, Oracle E-Business Suite, DevOps tools, Oracle WebLogic, Oracle Application Server, Oracle Access Manager and various Operating System flavors including Redhat Linux, UNIX (Solaris, HP-UX) and Windows. Expert in Oracle9i/10g/11g/12c/19c database administration, upgrade, configuration and tuning. Experience in Oracle E-Business Suite technological stack, including architecture, installation, configuration, maintenance, tuning, cloning and patching procedures. Expert in Oracle Cloud Infrastructure(OCI), Oracle EBS On Cloud and Oracle EBS Cloud Manager Experience with Oracle Cloud Solution and Expert of Oracle ERP/Oracle HCM Cloud deployment Experience in Terraform, JSON and chef cloud infrastructure automation framework Knowledge of ASM, Data Guard, Real Application Cluster, Exadata and Exalogic Knowledge of Oracle Enterprise Manager(OEM) Grid Control, Oracle WebLogic, Oracle Internet Directory, Oracle Access Manager and Apache Ability to analyze problem, develops solutions and bring program/project execution to completion.

Post a Comment

Previous Post Next Post