{"id":4244,"date":"2013-05-24T13:48:31","date_gmt":"2013-05-24T17:48:31","guid":{"rendered":"https:\/\/pitss.org\/us\/2013\/05\/24\/frm-93618-fatal-error-reading-data-from-runtime-process\/"},"modified":"2017-05-15T13:59:57","modified_gmt":"2017-05-15T17:59:57","slug":"frm-93618-fatal-error-reading-data-from-runtime-process","status":"publish","type":"post","link":"https:\/\/pitss.org\/us\/2013\/05\/24\/frm-93618-fatal-error-reading-data-from-runtime-process\/","title":{"rendered":"FRM-93618: Fatal error reading data from runtime process"},"content":{"rendered":"

Oracle HTTP Server (OHS) can be used as a load balancer between two Oracle Forms and Reports environments. One of our customers had run into a error when using JRE 7 when logging into the Oracle Forms application. They were receiving the following error:<\/p>\n

\u201cFRM-93618: fatal error reading data from runtime process<\/p>\n

Contact your system administrator.\u201d<\/p>\n

\"FRM-93618\"<\/a><\/p>\n

The production environment had the following multi-server architecture (NOTE: The error may occur if not using OAM as no errors were detected in the OAM or OID side):<\/p>\n

Front-end Server (Point of entry for end-users):<\/strong><\/p>\n

    \n
  1. Oracle HTTP Server (11.1.2.1) (load balancing occurs here using forms.conf and mod_wl_ohs.conf) \u2013 Using SSL<\/li>\n<\/ol>\n

    Two Middle-Tier Servers<\/strong><\/p>\n

      \n
    1. Oracle Forms and Reports 11.1.2.1<\/li>\n
    2. Oracle WebLogic Server 10.3.6<\/li>\n<\/ol>\n

      Back-end Infrastructure Server<\/strong><\/p>\n

        \n
      1. Oracle Internet Directory 11.1.1.5.0<\/li>\n
      2. Oracle Access Manager 11.1.1.5.0<\/li>\n
      3. Oracle WebLogic Server 10.3.5<\/li>\n<\/ol>\n

        The scenario was that the OHS and Forms\/Reports environments were upgraded from 11.1.2.0 to 11.1.2.1 in order to support the use of Java 7 (JRE 7) for end users. End-users would log into the front-end and would log into OAM (using single sign-on). After the user is authenticated in OAM, the user would be directed (by a round-robin approach) to one of the two middle-tier servers where the Oracle Forms application is. However, if the user used JRE 6, they could access Forms without a problem. If the user used JRE 7, the FRM-93618 error appeared instead, preventing the user from continuing. Whenever a direct connection to the middle-tier server was performed (again using OAM to authenticate), no errors would occur regardless of the JRE used.<\/p>\n

        SOLUTION:<\/strong><\/p>\n

        The load balancing in OHS for Oracle Forms is performed using forms.conf (located in %ORACLE_INSTANCE%\\config\\OHS\\ohs1\\moduleconf). A parameter called \u201cCookieTracking\u201d needs to be set to \u201cOn\u201d within the <Location \/forms> tags. In order to apply this, you will need to do the following steps:<\/p>\n

          \n
        1. Make a backup of forms.conf in the load balancing server<\/li>\n
        2. Open up forms.conf in a text editor<\/li>\n
        3. Locate <Location \/forms>. In between this tag and the <\/Location> tag, add the following parameter: CookieTracking On<\/strong><\/li>\n
        4. Save and close the file<\/li>\n
        5. Restart OHS (the load balancing server)<\/li>\n<\/ol>\n

          After applying the above changes, FRM-93618 will no longer appear when using JRE 7. This will work using the Internet Explorer, Firefox, and Chrome browsers.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Oracle HTTP Server (OHS) can be used as a load balancer between two Oracle Forms and Reports environments. One of our customers had run into a error when using JRE 7 when logging into the Oracle Forms application. They were receiving the following error: \u201cFRM-93618: fatal error reading data from runtime process Contact your system […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[22,36,14,10],"tags":[16,25,12,23,47,46,52,37,24],"class_list":["post-4244","post","type-post","status-publish","format-standard","hentry","category-forms","category-reports","category-resolve-issues","category-windows","tag-11gr2","tag-customer-support-request","tag-error","tag-forms","tag-oam","tag-ohs","tag-oid","tag-reports","tag-windows"],"_links":{"self":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4244","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/comments?post=4244"}],"version-history":[{"count":3,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4244\/revisions"}],"predecessor-version":[{"id":8500,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4244\/revisions\/8500"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/media?parent=4244"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/categories?post=4244"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/tags?post=4244"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}