Correlation Issue while using Oracle R12 application with Mozilla Firefox

Correlation Issue while using Oracle R12 application with Mozilla Firefox

 

Below mentioned correlation expection is raising while replaying the script.

 

//icx_ticket&gv15=y0YpO3r4VRKppZNrWeeKbA..&

 web_reg_save_param("icx_txct",
        "LB=icx_ticket&gv15=",
        "RB=&",
        "ORD=1",
        "IgnoreRedirections=Yes",
        "Search=Body",
        "RelFrameId=1",LAST);
 

 web_url("RF.jsp_4",
  "URL=http://us1-rherp-d01.corp.resmed.org:8084/OA_HTML/RF.jsp?function_id=5521&resp_id=55930&resp_appl_id=20105&security_group_id=0&lang_code=US&oas=89pDThhS9D48fWkO-c1oDA..",
  "TargetFrame=",
  "Resource=0",
  "RecContentType=text/html",
  "Referer=http://us1-rherp-d01.corp.resmed.org:8084/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE",
  "Snapshot=t7.inf",
  "Mode=HTML",
  EXTRARES,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndforms.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndformsi18n.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndewt.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndswing.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndbalishare.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndaol.jar", ENDITEM,
  "URL=../OA_JAVA/oracle/apps/fnd/jar/fndctx.jar", ENDITEM,
  LAST);

 

 

"Error -26377: No match found for the requested parameter "icx_txct". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size   [MsgId: MERR-26377]
Action.c(247): Notify: Saving Parameter "icx_txct = "
Action.c(247): web_url("RF.jsp_4") highest severity level was "ERROR", 4618830 body bytes, 4405 header bytes, 36 chunking overhead bytes   [MsgId: MMSG-26387]"

 

Please any provide solution.

Tags:

  • You have to keep checking your boundaries, and maybe see if there is another place where you can try and capture the icx_ticket.

     

    Regards,

    Mario M.

  • Try looking at your recording log and spot the exact request for which the response contains your ICX TICKET.

    The correlation statement should then be applied above the request which gets that request, and not below it.

     

    As Mario suggests, it could also be that the LB and RB are not accurate. Turn on extended logging and look at the replay log to see the return data for the request and check if the response has the ICX TICKET in the response and if the LB and RB are matching.

     

    Regards,

    AJ