Saturday, March 27, 2010

Oracle Release 12 : Diagnostic Test errors with HTTP 400 - Bad Request

Dear Readers,

One of my application team compliant about the Diagnostic Test for Assets module failed with HTTP 400 - Bad Request.

As per the oracle note, this is the bug in Release 12 and Patch 8283135 is available for fixing this issue.

Current Version of file in the system,

Q$Header: FACheckSetup.java 120.0.12000000.2 2007/08/03 05:24:37 spooyath noship $
N$Header: FAUtility.java 120.0.12000000.2 2007/08/03 05:49:32 spooyath noship $


Patch provides the following version,

$fa/java/diag/FaCheckSetup.java - 120.0.12000000.3
$Header: FAUtility.java 120.0.12000000.3 2009/07/22 10:05:27 glchen noship $;

Finally issue got fixed by applying the patch.

Yours comments are most welcome !!!
Posted by at
Labels:

2 comments:

  1. djayJune 19, 2012 at 9:09 AM

    This comment has been removed by the author.

    ReplyDelete
    Replies
    1. djayJune 19, 2012 at 9:17 AM

      Hi Sasi,

      We also ran in same issue for Revenue(R12).
      Steps :
      Select the Diagnostic Tools menu option
      Select Application "Projects" from the list of values displayed
      Click the "Advanced" tab
      Scroll down to group "Revenue"
      Select test name "Revenue

      $Header: jtfqaadv.jsp 115.12 2006/04/20 01:21:33 rudas ship $ -->

      But solution didn't match our issue.

      Delete

Subscribe to: Post Comments (Atom)