MarkView Application Server – Process Monitor shows a blank page and unable to code in the Viewer

Applies To

• ERP System : Oracle, SAP
• MarkView Versions: MarkView 8.1 and higher
• Application Server: WebLogic Server 12.1.3 and higher

Behavior

When opening Process Monitor a blank page appears, coding in the Viewer also fails. In both cases errors similar to the following may appear in the log files:

• javax.servlet.ServletException: java.lang.OutOfMemoryError: Java heap space
• java.lang.NullPointerException at Oracle.jdbc.driver.DynamicByteArray.get
• javax.servlet.ServletException: java.lang.NoClassDefFoundError: oracle/jdbc/internal/XMLTypeIntf
• javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class oracle.jdbc.driver.ScrollableResultSet

Known Causes

• WebLogic 12.1.3 ships with version 12 of the JDBC drivers by default. Due to Oracle bug# 21043834 version 12 of the JDBC driver was not initially supported with MarkView. Oracle has released a series of patches to resolve this issue and if you are using Oracle JDBC drivers version 12.1, please be sure Oracle patches 21043834, 20692348, 19028811 are applied.

Resolution

• If using the 12.1 version of the JDBC Drivers please be sure Oracle patches 21043834, 20692348, and 19028811 are applied
• Alternatively, downgrading the JDBC driver will also resolve the issue.
  • We recommend using the 11.2.0.3 version of the JDBC Driver which can be downloaded directly from Oracle.
    • Note you will need to download the ojdbc6.jar file as well as the xdb6.jar file.
    • http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html
  • Stop Node Manager and the Weblogic Server (Admin and the MarkView Managed Server)
  • Backup and Delete all the jar files (except for the “aqpi” jar file) found under: $WL_HOME/oracle_common/modules/oracle.jdbc_12.1.0/. Backup and Delete oracle.xdb_12.1.0.jar from $WL_HOME/oracle_common/modules
  • Backup and Delete oracle.xdb_12.1.0.jar from $WL_HOME/oracle_common/
  • Copy the ojdbc6.jar file (downloaded above – version 11.2.0.3) to: $WL_HOME/oracle_common/common/lib/ojdbc6.jar (If this file is not named ojdbc6.jar please rename it)
  • Copy the xdb6.jar file (downloaded above – version 11.2.0.3) to $WL_HOME/oracle_common/common/lib/xdb6.jar (If this file is not named xdb6.jar please rename it)
  • Edit the env file $WL_HOME/oracle_common/common/bin/commEnv.sh and update the WEBLOGIC_CLASSPATH by adding the paths “$WL_HOME/oracle_common/common/lib/xdb6.jar${CLASSPATHSEP}$WL_HOME/oracle_common/common/lib/ojdbc6.jar${CLASSPATHSEP}” to the beginning of the variable definition

Start Node Manager and WebLogic server (Admin and the MarkView Managed Server).

• Verification Steps
  • If the issue persists after taking the above steps:
    • Try restarting the Server where WebLogic is running.
    • Review the markview_server.log file for a line similar to the following showing the current JDBC Driver being used: Data source connection pool "MarkViewDS" using Driver: "Oracle JDBC driver", Version: "12.1.0.1.0"
    • If the version is showing 12.x then please ensure you are using the correct version of the ojdbc6.jar file by running the following from a command prompt:
      • java -jar ojdbc6.jar
    • If the correct version of the JDBC driver is being used please open a new ticket with Technical Support including the behavior you are seeing as well as the markview_server.log and markview_server.out log files.