FRM-41480

error in FSCRATCHPAD.EXPAND_TEMPLATE: syntax error in URI template {0} at offset {1} [characters]

Category:

Data

Cause:

The URI template specified by the 'uri_template' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE was not syntactically correct [RFC 6570, level 4].

Action:

Correct the URI template.

FRM-41484

error in FSCRATCHPAD.EXPAND_TEMPLATE: ''parameters'' contains an element of unexpected type; its JSON pointer is {0}

Category:

Data

Cause:

The values of the children of the JSON object specified by the 'parameters' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE must be strings, arrays of strings, or objects whose child values are strings or arrays of strings. A violation of this constraint was detected.

Action:

Correct the offending element.

FRM-41486

error in FSCRATCHPAD.EXPAND_TEMPLATE: ''parameters'' contains an element with an object key containing an invalid %-encoding; the element''s JSON pointer is {0}

Category:

Data

Cause:

A child element of the JSON object specified by the 'parameters' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE corresponded to a variable in a '+' or '#' expression in the URI template specified by the 'uri_template' parameter, and the object key of the child element or an element within it contained an invalid sequence of 3-byte %-encodings. Each %-encoding must consist of '%' followed by 2 hex digits, and the sequence of bytes denoted by the %-encodings must be a valid AL32UTF8 representation of a Unicode character.

Action:

Correct the offending element.

FRM-41487

error in FSCRATCHPAD.EXPAND_TEMPLATE: ''parameters'' contains a STRING element with a value containing an invalid %-encoding; the element''s JSON pointer is {0}

Category:

Data

Cause:

A child element of the JSON object specified by the 'parameters' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE corresponded to a variable in a '+' or '#' expression in the URI template specified by the 'uri_template' parameter, and the value of the child element or an element within it contained an invalid sequence of 3-byte %-encodings. Each %-encoding must consist of '%' followed by 2 hex digits, and the sequence of bytes denoted by the %-encodings must be a valid AL32UTF8 representation of a Unicode character.

Action:

Correct the offending element.

FRM-41492

error in runtime process: FSCRATCHPAD contents or FJSON string value not a valid base64 encoding: invalid byte detected at offset {0} [bytes]

Category:

Data

Cause:

'base64_decode := true' was specified for FSCRATCHPAD.TO_FILE or FJSON.STRING_VALUE_TO_FILE, but the scratchpad contents (up to the string specified by the 'stop_at' parameter, if specified) or the JSON string value did not constitute a valid base64 encoding. A valid base64 encoding must contain only white space [blank, tab, carriage return, or line feed] or base64 alphabet characters ['A'-'Z', 'a'-'z', '0'-'9', '+', '/', or '=']. '=' characters are not required, but if present, they must occur only at the end, and they must ensure that the total number of base64 alphabet characters is a multiple of 4. If the invalid base64 encoding was obtained from a string element retrieved from a REST endpoint, a subsequent FRM-41592 provides the offending string element's JSON pointer.

Action:

Correct application logic that populates the scratchpad.

FRM-41493

error in runtime process: FSCRATCHPAD contents or FJSON string value could not be written to {0}

Category:

Files

Cause:

FSCRATCHPAD.TO_FILE or FJSON.STRING_VALUE_TO_FILE was unable to successfully write the contents to the location specified by the 'file_name' parameter.

Action:

Verify that the file name is spelled correctly and that the application has permission to write a file to the specified directory, and that the specified directory has adequate space.

FRM-41494

error in runtime process: could not find file {0} for FSCRATCHPAD or FJSON package

Category:

Files

Cause:

The 'file_name' parameter passed to FSCRATCHPAD.APPEND_FILE or FJSON.NEW_STRING_FROM_FILE specified a file that could not be found.

Action:

Verify that the file name is spelled correctly and that the application has permission to read the file.

FRM-41495

error in runtime process: error reading file {0} for FSCRATCHPAD or FJSON package

Category:

Files

Cause:

The 'file_name' parameter passed to FSCRATCHPAD.APPEND_FILE or FJSON.NEW_STRING_FROM_FILE specified a file that could not be read successfully.

Action:

Verify that the file name is spelled correctly and that the application has permission to read the file.

FRM-41516

loop in JSON parse tree

Category:

Data

Cause:

Application design error. An attempt to produce a JSON pointer for a diagnostic message detected a loop in the JSON parse tree [so it wasn't really a tree at all]: the root of the JSON parse tree was encountered while traversing its descendent elements. The production of the JSON pointer was aborted and the memory it consumed was released. The JSON pointer is shown as '?' in the diagnostic message. This condition was caused by an earlier call to FJSON.ADD, FJSON.SET, or FJSON.PUT that added a child element C to an array or object A, where C was equal to A or was an ancestor of A.

Action:

Correct the application logic.

FRM-41530

error in runtime process: {0} was passed an unexpected retrieved {1} {2}; its JSON pointer was {3}

Category:

Data

Cause:

Application design error. An FJSON.ELEMENT_T value retrieved from a REST endpoint was passed as the first parameter to a function or procedure in the FJSON package or as the second parameter to the POPULATE_GROUP_FROM_JSON procedure, and specified an element whose element type is not supported by the specified function or procedure. An FJSON.CONTENT exception was raised (except for POPULATE_GROUP_FROM_JSON). Additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41531

error in runtime process: unexpected retrieved {0} element found by {1}, which was passed a {2} whose JSON pointer was {3}, and a {4} whose value was {5}

Category:

Data

Cause:

Application design error. An FJSON.FIND_x or FJSON.GET_x function produced an element of an unexpected type that was retrieved from a REST endpoint. An FJSON.CONTENT exception was raised. Additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41532

error in runtime process: no element found where expected by {0}, which was passed a retrieved {1} whose JSON pointer was {2}, and a {3} whose value was {4}

Category:

Data

Cause:

Application design error. An FJSON.FIND_ARRAY, FJSON.FIND_OBJECT, FJSON.GET_ARRAY, or FJSON.GET_OBJECT function produced no element, and the FJSON.ELEMENT_T value passed as the first parameter to the function was retrieved from a REST endpoint. An FJSON.CONTENT exception was raised. Additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41533

error in runtime process: {0} was passed a {1} that contained an unexpected {2} element whose JSON pointer was {3}

Category:

Data

Cause:

Application design error. One of the following occurred:\n1. The JSON array passed as the first parameter to the FJSON.JOIN function contained an element that was not a JSON string.\n2. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained an initial element that was a JSON object, but also contained an element that was not a JSON object.\n3. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained an initial element that was a JSON array or scalar element, but also contained an element that was a JSON object.\n4. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a scalar element, or a JSON array or JSON object that in turn contained a scalar element, and the type of the scalar element did not match the corresponding record group column. [DATE columns are a special case: if a null epoch_unit was passed to POPULATE_GROUP_FROM_JSON, the corresponding scalar element must be a JSON string (representing an ISO 8601 date/time string); otherwise, it must be a JSON number (representing "epoch": seconds since 1970-01-01).]\nIn case 1, an FJSON.CONTENT exception was raised.\nIf the offending element was retrieved from a REST endpoint, additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41534

error in runtime process: {0} was passed a {1} that contained a {2} element whose JSON pointer was {3}. The element was expected to represent a date, but an ORA-0{4} exception was encountered when the conversion to date was attempted.

Category:

Data

Cause:

Application design error. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a scalar element, or a JSON array or JSON object that in turn contained a scalar element, and the corresponding record group column was of type DATE. Either a null epoch_unit was passed to POPULATE_GROUP_FROM_JSON and the scalar element was a JSON string which was not in valid ISO 8601 format, or a non-null epoch_unit was specified and the scalar element was a JSON number which was not a valid epoch. If the exception was not ORA-06502 and the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 2 or more, the offending value is displayed [FRM-41537]. If the offending element was retrieved from a REST endpoint, additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41535

error in runtime process: {0} was passed a {1} that contained a STRING element whose value was unexpectedly too large. The full JSON pointer was {2}

Category:

Data

Cause:

Application design error. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a JSON string element, or a JSON array or JSON object that in turn contained a JSON string element, and the value of the string element exceeded 32767 bytes. If the offending element was retrieved from a REST endpoint, additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41536

error in runtime process: {0} was passed a {1} that contained an element whose object key was unexpectedly too large, or was not (when expected) a valid number. The full JSON pointer was {2}

Category:

Data

Cause:

Application design error. A JSON object was passed as the second parameter to the POPULATE_GROUP_FROM_JSON function. It contained an element whose object key exceeded 32767 bytes or, in the case where the first record group column was of type NUMBER, could not be converted to a number. If the offending element was retrieved from a REST endpoint, additional information was written to ODL, starting with FRM-41539.

Action:

Correct the application logic.

FRM-41537

The value which could not be converted was {0}

Category:

Data

Cause:

This message follows FRM-41534 and displays the offending value if the exception was not ORA-06502 and the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 2 or more.

Action:

No action is required.

FRM-41539

The unexpected JSON content was produced by a {0} request to the URL generated from the URI template {1}

Category:

Data

Cause:

This message provides additional information about unexpected JSON content in the JSON text response from a REST endpoint. It may be followed by a dump of the request and the response [FRM-41690 and FRM-41691], depending on the value of the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable.

Action:

No action is required.

FRM-41540

error in runtime process: unexpected content detected in JSON document: {0}

Category:

Data

Cause:

The application called the FJSON.UNEXPECTED_CONTENT procedure with a null target element, presumably because its logic detected unexpected content of some sort. An FJSON.CONTENT exception was raised.

Action:

Try to determine what is producing the unexpected JSON content, e.g. by contacting the owner of the REST service from which the JSON document was retrieved. Correct application logic if necessary.

FRM-41541

error in runtime process: unexpected content detected in JSON document at {0}: {1}

Category:

Data

Cause:

The application called the FJSON.UNEXPECTED_CONTENT procedure with a non-null target element, presumably because its logic detected unexpected content of some sort. An FJSON.CONTENT exception was raised. If the offending element was retrieved from a REST endpoint, additional information was written to ODL, starting with FRM-41539.

Action:

Try to determine what is producing the unexpected JSON content, e.g. by contacting the owner of the REST service from which the JSON document was retrieved. Correct application logic if necessary.

FRM-41549

error in runtime process: unexpected scalar conversion exception ORA-0{0} encountered while processing JSON document

Category:

Data

Cause:

The application called the FJSON.ANALYZE_EXCEPTION procedure within a PL/SQL exception block, and it tentatively determined that the exception could plausibly have been produced by a PL/SQL assignment from a scalar derived from a REST endpoint response, to a PL/SQL variable (or an assignment from that variable to another using a conversion function such as TO_DATE). An FJSON.CONTENT exception was raised. Additional information was written to ODL, starting with FRM-41550 or FRM-41551.

Action:

Try to determine what is causing the scalar conversion exception. It could be due to an application design error unrelated to the REST service; if so, correct the application logic. Otherwise, try to determine what is producing the unexpected JSON content, e.g. by contacting the owner of the REST service from which the JSON document was retrieved. Correct application logic if necessary.

FRM-41550

The last scalar-producing FJSON function executed prior to calling FJSON.ANALYZE_EXCEPTION was FJSON.{0}, with a {1} whose JSON pointer was {2}, and with a {3} whose value was {4}

Category:

Data

Cause:

This message follows FRM-41549 in the case where the last scalar-producing FJSON function was a "composite" function: get_string_value, get_number_value, get_boolean_value, find_string_value, find_number_value, find_boolean_value, or find_object_key. It specifies the arguments passed to the function: target object or array, and object key or array position.

Action:

No action is required.

FRM-41551

The last scalar-producing FJSON function executed prior to calling FJSON.ANALYZE_EXCEPTION was FJSON.{0}, with a {1} whose JSON pointer was {2}

Category:

Data

Cause:

This message follows FRM-41549 in the case where the last scalar-producing FJSON function was not a composite function. It specifies the JSON element passed to the function.

Action:

No action is required.

FRM-41552

The returned value was null, because no element was found.

Category:

Data

Cause:

This message follows FRM-41550 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 1 or more and the composite scalar-producing FJSON function found no element.

Action:

No action is required.

FRM-41553

The returned value was null, obtained from a {0} element.

Category:

Data

Cause:

This message follows FRM-41550 or FRM-41551 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 1 or more and the scalar-producing FJSON function found or was passed a NULL element or a STRING element whose value was the empty string.

Action:

No action is required.

FRM-41554

The returned value was {0}

Category:

Data

Cause:

This message follows FRM-41550 or FRM-41551 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 2 or more and the scalar-producing FJSON function found or was passed a BOOLEAN element, a NUMBER element, or a STRING element whose value was non-empty and whose AL32UTF8 representation did not exceed 4095 bytes.

Action:

No action is required.

FRM-41555

The returned value was a non-null VARCHAR2 containing {0} characters and {1} bytes (in the NLS_LANG charset: {2}).

Category:

Data

Cause:

This message follows FRM-41550 or FRM-41551 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 1 and the scalar-producing FJSON function found or was passed a STRING element whose value was non-empty, or if FORMS_HTTP_DIAGNOSTIC_LEVEL is set to 2 or more and the scalar-producing FJSON function found or was passed a STRING element whose AL32UTF8 representation exceeded 4095 bytes.

Action:

No action is required.

FRM-41556

The returned value was a non-null NUMBER{0} (when rounded to an integer).

Category:

Data

Cause:

This message follows FRM-41550 or FRM-41551 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 1 and the scalar-producing FJSON function found or was passed a NUMBER element. It indicates whether the value was zero, positive, or negative, and whether it would fit in a PLS_INTEGER.

Action:

No action is required.

FRM-41557

The returned value was a non-null BOOLEAN.

Category:

Data

Cause:

This message follows FRM-41550 or FRM-41551 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 1 and the scalar-producing FJSON function found or was passed a BOOLEAN element.

Action:

No action is required.

FRM-41560

error in runtime process: syntax error in retrieved JSON text at offset {0} [bytes]

Category:

Data

Cause:

A parse of the JSON text response from a REST endpoint encountered a violation of RFC 7159. The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.PARSE_FAILURE exception was raised. Additional information was written to ODL, starting with FRM-41569.

Action:

Try to determine why the erroneous JSON text is being returned, e.g. by contacting the owner of the REST service.

FRM-41561

error in runtime process: oversize object key in retrieved JSON text, ending at offset {0} [bytes]

Category:

Data

Cause:

A parse of the JSON text response from a REST endpoint encountered an oversize object key in an object member definition. By default, Oracle Forms does not support object keys whose AL32UTF8 representation exceeds 32767 bytes. [Larger keys cannot be used in PL/SQL VARCHAR2 variables.] The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.PARSE_FAILURE exception was raised. Additional information was written to ODL, starting with FRM-41569.

Action:

FRM-41562

error in runtime process: oversize array or object in retrieved JSON text, detected at offset {0} [bytes]

Category:

Data

Cause:

A parse of the JSON text response from a REST endpoint encountered an array or object which contained 2G elements or more. The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.PARSE_FAILURE exception was raised. Additional information was written to ODL, starting with FRM-41569.

Action:

Try to determine why the oversize array or object is being returned, e.g. by contacting the owner of the REST service.

FRM-41569

The JSON text which could not be parsed was produced by a {0} request to the URL generated from the URI template {1}

Category:

Data

Cause:

This message provides additional information about a parse error in the JSON text response from a REST endpoint. It may be followed by a dump of the request and the response [FRM-41690 and FRM-41691], depending on the value of the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable.

Action:

No action is required.

FRM-41570

error in runtime process: JSON parse memory limit exceeded

Category:

Memory

Cause:

A parse of the JSON text response from a REST endpoint required more memory than the JSON parse memory limit (4Gb or the limit specified by the FORMS_JSON_PARSE_MEMORY_LIMIT environment variable). The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.PARSE_ALLOCATION exception was raised.

Action:

Modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response, or increase the value of the FORMS_JSON_PARSE_MEMORY_LIMIT environment variable.

FRM-41571

error in runtime process: JSON new memory limit exceeded

Category:

Memory

Cause:

An attempt to programmatically create a JSON element (using e.g. FJSON.CLONE or an FJSON.NEW_x function) would have caused the memory consumed by all programmatically created JSON elements to exceed the new memory limit (4Gb or the limit specified by the FORMS_JSON_NEW_MEMORY_LIMIT environment variable). An FJSON.GLOBAL_ALLOCATION exception was raised.

Action:

Revise application logic so as to programmatically create fewer JSON elements, or increase the value of the FORMS_JSON_NEW_MEMORY_LIMIT environment variable.

FRM-41572

error in runtime process: JSON memory allocation failed

Category:

Memory

Cause:

An operation to create, update, or generate a JSON parse tree was unable to allocate adequate memory. An FJSON.GLOBAL_ALLOCATION exception was raised..

Action:

Modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response, or revise application logic so as to programmatically create fewer JSON elements.

FRM-41573

error in runtime process: JSON parse trees require excessive memory for element values

Category:

Memory

Cause:

This error arises only if both the following occur:\n1. The FORMS_JSON_KEY_LENGTH_BITS environment variable [which defaults to 15, limiting object keys to 32767 bytes] was set to a value N in the range 16..30 [the maximum allowed].\n2. The total number of bytes required for all strings, numbers, and hash arrays for all elements in all JSON parse trees exceeded 2 raised to the power of 64-N.\nIf this error occurred, then an FJSON.GLOBAL_ALLOCATION exception was raised.

Action:

Modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response, or revise application logic so as to programmatically create fewer JSON elements.

FRM-41574

error in runtime process: too many elements in JSON parse trees

Category:

Memory

Cause:

An operation to create or update a JSON parse tree would have caused the total number of elements in all JSON parse trees to equal or exceed 4G. An FJSON.GLOBAL_ALLOCATION exception was raised.

Action:

Modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response, or revise application logic so as to programmatically create fewer JSON elements.

FRM-41580

error in runtime process: invalid $ref string {0} in element at {1}: syntax error at offset {2} [characters]

Category:

Data

Cause:

The element passed to FJSON.RESOLVE$REF specified a $ref string which was not a syntactically valid URI.

Action:

Contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41581

error in runtime process: loop or overflow in recursive JSON references: {0}

Category:

Data

Cause:

The element passed to FJSON.RESOLVE$REF specified a $ref string which resolved to another $ref element, which in turn resolved to yet another $ref element, and so forth. The chain of recursive references, shown in the diagnostic message, contained a loop or more than 16 entries.

Action:

Contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41582

error in runtime process: $ref string {0} in element at {1} specifies a document which cannot be loaded: the $ref string itself resides in a document which was not loaded from a URL

Category:

Data

Cause:

Action:

Correct application logic. In general, $ref strings should not be placed in programmatically constructed documents.

FRM-41583

error in runtime process: $ref string {0} in element at {1} specifies a document which could not be loaded and parsed: an error occurred on the internal call to FHTTP.ISSUE_REQUEST

Category:

Data

Cause:

Self-explanatory

Action:

Examine the error messages that were produced for the internal call to FHTTP.ISSUE_REQUEST.

FRM-41584

error in runtime process: JSON pointer {0} could not be evaluated against document {1}: syntax error at offset {2} [characters]

Category:

Data

Cause:

Either (1) an invalid JSON pointer was passed to FJSON.EVALUATE_POINTER, or (2) the element passed to an invocation of FJSON.RESOLVE$REF specified a $ref string whose fragment [the portion after the '#'] was not a valid JSON pointer. The JSON pointer did not begin with '/' or contained an invalid escape sequence ['~' not followed by '0' or '1'].

Action:

In case (1), correct the application logic. In case (2), contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41585

error in runtime process: JSON pointer {0} could not be evaluated against document {1}: element specified by portion preceding '/' at offset {2} [characters] is not an object or array

Category:

Data

Cause:

Either (1) an invalid JSON pointer was passed to FJSON.EVALUATE_POINTER, or (2) the element passed to an invocation of FJSON.RESOLVE$REF specified a $ref string whose fragment [the portion after the '#'] was not a valid JSON pointer. The JSON pointer contained a '/' at the specified offset, but the portion of the specified JSON pointer preceding that '/' specified a scalar JSON element.

Action:

In case (1), correct the application logic. In case (2), contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41586

error in runtime process: JSON pointer {0} could not be evaluated against document {1}: key specified after ''/'' at offset {2} [characters] does not exist in the object specified by portion preceding the ''/''

Category:

Data

Cause:

Either (1) an invalid JSON pointer was passed to FJSON.EVALUATE_POINTER, or (2) the element passed to an invocation of FJSON.RESOLVE$REF specified a $ref string whose fragment [the portion after the '#'] was not a valid JSON pointer. The JSON pointer contained a '/' at the specified offset, and the portion of the specified JSON pointer preceding that '/' specified an object, but that object did not contain the key specified after the '/'.

Action:

In case (1), correct the application logic. In case (2), contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41587

error in runtime process: JSON pointer {0} could not be evaluated against document {1}: invalid array index specified after ''/'' at offset {2} [characters]

Category:

Data

Cause:

Either (1) an invalid JSON pointer was passed to FJSON.EVALUATE_POINTER, or (2) the element passed to an invocation of FJSON.RESOLVE$REF specified a $ref string whose fragment [the portion after the '#'] was not a valid JSON pointer. The JSON pointer contained a '/' at the specified offset, and the portion of the specified JSON pointer preceding that '/' specified an array, but the array index specified after the '/' was not a valid nonnegative decimal number.

Action:

In case (1), correct the application logic. In case (2), contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41588

error in runtime process: JSON pointer {0} could not be evaluated against document {1}: array index specified after ''/'' at offset {2} [characters] does not fall within the array specified by portion preceding the ''/''

Category:

Data

Cause:

Either (1) an invalid JSON pointer was passed to FJSON.EVALUATE_POINTER, or (2) the element passed to an invocation of FJSON.RESOLVE$REF specified a $ref string whose fragment [the portion after the '#'] was not a valid JSON pointer. The JSON pointer contained a '/' at the specified offset, and the portion of the specified JSON pointer preceding that '/' specified an array, but that array did not contain the element specified by the 0-relative index after the '/'.

Action:

In case (1), correct the application logic. In case (2), contact the provider of the service which produced the document containing the invalid JSON reference.

FRM-41592

The invalid base64 encoding was obtained from a STRING element whose JSON pointer was {0}

Category:

Data

Cause:

This message provides additional information about an invalid base64 encoding [reported in a preceding FRM-41492] in the JSON text response from a REST endpoint. It may be followed by a dump of the request and the response [FRM-41690 and FRM-41691], depending on the value of the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable.

Action:

No action is required.

FRM-41610

error in FHTTP.ISSUE_REQUEST: the {0} method sent to the URL generated from the URI template {1}{2} was rejected.

Category:

Requests/Responses

Cause:

The method specified by the 'method' parameter passed to FHTTP.ISSUE_REQUEST was rejected. This can happen if a security manager is set and the method is 'TRACE', but the 'allowHttpTrace' NetPermission is not granted.

Action:

Determine whether the conditions above apply. If not, and the problem persists, contact Oracle Support Services.

FRM-41620

error in FHTTP.ISSUE_REQUEST: server URL could not be obtained due to invalid ''server_url_or_id'' parameter {0}.

Category:

Data

Cause:

The 'server_url_or_id' parameter passed to FHTTP.ISSUE_REQUEST must begin with 'http:', 'https:', 'ws:', or 'wss:', or else must contain only alphanumeric characters and '_', '.', '-'.

Action:

Correct the 'server_url_or_id' parameter.

FRM-41621

error in FHTTP.ISSUE_REQUEST: server URL could not be obtained due to invalid config section name {0}

Category:

Data

Cause:

If a non-null 'server_url_or_id' parameter is passed to FHTTP.ISSUE_REQUEST, and it does not begin with 'http:', 'https:', 'ws:', or 'wss:', the config section name specified as the config parameter in the frmservlet URL used to launch the Forms application must contain only alphanumeric characters and '_', '.', '-'.

Action:

Specify a config section with a valid name in the frmservlet URL used to launch the Forms application.

FRM-41622

error in FHTTP.ISSUE_REQUEST: server URL could not be obtained due to missing credential for {0}

Category:

Configuration

Cause:

If a non-null 'server_url_or_id' parameter is passed to FHTTP.ISSUE_REQUEST, and it does not begin with 'http:', 'https:', 'ws:', or 'wss:', the Oracle Platform Security Services Credential Store must contain a generic credential for the server. The credential key must be of the form <config_section_name>=<credential_id>.

Action:

Use Fusion Middleware Control to add the generic credential. The value must be a well-formed URL which specifies a scheme of 'http', 'https', 'ws', or 'wss'.

FRM-41623

error in FHTTP.ISSUE_REQUEST: the server URL {1} specified by the credential for {0} was rejected.

Category:

Configuration

Cause:

If a non-null 'server_url_or_id' parameter is passed to FHTTP.ISSUE_REQUEST, and it does not begin with 'http:', 'https:', 'ws:', or 'wss:', the Oracle Platform Security Services Credential Store must contain a generic credential for the server. The credential key must be of the form <config_section_name>=<credential_id>. The value must be a string that's a well-formed URL which specifies a scheme of 'http', 'https', 'ws', or 'wss'.

Action:

Use Fusion Middleware Control to correct the generic credential.

FRM-41624

error in FHTTP.ISSUE_REQUEST: the server URL {1} was rejected.

Category:

Configuration

Cause:

The 'server_url_or_id' parameter passed to FHTTP.ISSUE_REQUEST began with 'http:', 'https:', 'ws:', or 'wss:', but it was not a well-formed URL.

Action:

FRM-41630

error in FHTTP.ISSUE_REQUEST: syntax error in URI template {0} at offset {1} [characters]

Category:

Data

Cause:

The URI template specified by the 'uri_template' parameter passed to FHTTP.ISSUE_REQUEST was not syntactically correct [RFC 6570, level 4].

Action:

Correct the URI template.

FRM-41633

error in FHTTP.ISSUE_REQUEST: the URL generated from the URI template {0}{1} for a {2} request was rejected.

Category:

Data

Cause:

The URL generated from the 'uri_template' and 'url_parameters' parameters passed to FHTTP.ISSUE_REQUEST was malformed or, if the 'server_url_or_id' parameter was null or not specified, did not specify a scheme of 'http', 'https', 'ws', or 'wss'.

Action:

Correct the 'uri_template' and/or 'url_parameters' parameters.

FRM-41640

error in FHTTP.ISSUE_REQUEST: ''url_parameters'' contains an unexpected {0} element; its JSON pointer is {1}

Category:

Data

Cause:

The values of the children of the JSON object specified by the 'url_parameters' parameter passed to FHTTP.ISSUE_REQUEST must be strings, arrays of strings, or objects whose child values are strings or arrays of strings. A violation of this constraint was detected.

Action:

Correct the offending element.

FRM-41642

error in FHTTP.ISSUE_REQUEST: ''url_parameters'' contains an element with an object key containing an invalid %-encoding; the element''s JSON pointer is {0}

Category:

Data

Cause:

A child element of the JSON object specified by the 'url_parameters' parameter passed to FHTTP.ISSUE_REQUEST corresponded to a variable in a '+' or '#' expression in the URI template specified by the 'uri_template' parameter, and the object key of the child element or an element within it contained an invalid sequence of 3-byte %-encodings. Each %-encoding must consist of '%' followed by 2 hex digits, and the sequence of bytes denoted by the %-encodings must be a valid AL32UTF8 representation of a Unicode character.

Action:

Correct the offending element.

FRM-41643

error in FHTTP.ISSUE_REQUEST: ''url_parameters'' contains a STRING element with a value containing an invalid %-encoding; the element''s JSON pointer is {0}

Category:

Data

Cause:

A child element of the JSON object specified by the 'url_parameters' parameter passed to FHTTP.ISSUE_REQUEST corresponded to a variable in a '+' or '#' expression in the URI template specified by the 'uri_template' parameter, and the value of the child element or an element within it contained an invalid sequence of 3-byte %-encodings. Each %-encoding must consist of '%' followed by 2 hex digits, and the sequence of bytes denoted by the %-encodings must be a valid AL32UTF8 representation of a Unicode character.

Action:

Correct the offending element.

FRM-41650

error in FHTTP.ISSUE_REQUEST: ''request_headers'' contains an unexpected {0} element; its JSON pointer is {1}

Category:

Data

Cause:

The values of the children of the JSON object specified by the 'request_headers' parameter passed to FHTTP.ISSUE_REQUEST must be strings. A violation of this constraint was detected.

Action:

Correct the offending element.

FRM-41652

error in FHTTP.ISSUE_REQUEST: ''request_headers'' contains an element whose object key is not a valid HTTP header name: invalid character found at offset {0} [characters]; the element''s JSON pointer is {1}

Category:

Data

Cause:

The object key of a child of the JSON object specified by the 'request_headers' parameter passed to FHTTP.ISSUE_REQUEST did not conform to the syntax for a header name specified by RFC 7230: an invalid character was found. Characters in header values must be visible USASCII characters [0x21-0x7f], and must not be any of: '"', '(', ')', ',', '/', ':', ';', '<', '=', '>', '?', '@', '[', '', ']', '{', '}'.

Action:

Correct the offending element.

FRM-41653

error in FHTTP.ISSUE_REQUEST: ''request_headers'' contains an element whose value is not a valid HTTP header value: invalid character found at offset {0} [characters]; the element''s JSON pointer is {1}

Category:

Data

Cause:

The value of a child of the JSON object specified by the 'request_headers' parameter passed to FHTTP.ISSUE_REQUEST did not conform to the syntax for a header value specified by RFC 7230: an invalid character was found. Characters in header values must be visible, or space, or horizontal tab. If the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 3 or 4, the invalid value is displayed in a subsequent FRM-41654 message.

Action:

Correct the offending element.

FRM-41654

The invalid header value is {0}

Category:

Data

Cause:

This message follows FRM-41653 if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 3 or 4.

Action:

No action is required.

FRM-41660

error in FHTTP.ISSUE_REQUEST: a {0} request to the URL generated from the URI template {1}{2} encountered an error communicating with the external service.

Category:

Network

Cause:

The request issued by FHTTP.ISSUE_REQUEST encountered an IOException while attempting to communicate with the external service. A subsequent FRM-41692 message indicates where the stack trace for the IOException was written.

Action:

Inspect the stack trace in the response identified by message FRM-41692 in ODL. If the stack trace does not indicate how to fix the problem, and the problem persists, contact the owner of the external service.

FRM-41661

error in FHTTP.ISSUE_REQUEST: a {0} request to the URL generated from the URI template {1}{2} received unexpected response status code {3}.

Category:

Requests/Responses

Cause:

The request issued by FHTTP.ISSUE_REQUEST received a response status code that was not specified in the 'accept' parameter and was not one of the status codes that are always accepted, namely 200, and [for all methods except TRACE] 204, and [for PUT and POST] 201 and 205. A subsequent FRM-41691 message indicates where the body of the response was written.

Action:

If the status code is a legitimate response from the accessed external service, include it in the 'accept' parameter, and add appropriate logic to handle it. Otherwise, inspect the diagnostic information in the response identified by message FRM-41691 in ODL.

FRM-41671

error in FHTTP.ISSUE_REQUEST: the runtime process encountered a memory allocation failure while attempting to process a {0} request to the URL generated from the URI template {1}{2}

Category:

Cause:

FHTTP.ISSUE_REQUEST was unable to allocate adequate memory in the runtime process.

Action:

Specify fewer or smaller request headers or a smaller request body, or modify the selection criteria specified in the request to the external service, so as to limit the size of the response.

FRM-41672

error in FHTTP.ISSUE_REQUEST: WebLogic was unable to create a thread to process a request to an external service.

Category:

Threads

Cause:

The number of active threads created by the WebLogic server exceeded the limit specified by the <max-concurrent-new-threads> element in weblogic-application.xml, weblogic.xml, or config.xml, as described in 'Configuring Concurrent Managed Objects' in 'Oracle Fusion Middleware Administering Server Environments for Oracle WebLogic Server'. The Forms application was terminated.

Action:

Increase the limit or run the Forms application when the system is less heavily loaded.

FRM-41673

error in FHTTP.ISSUE_REQUEST: the JVM encountered an OutOfMemoryError while attempting to process a {0} request to the URL generated from the URI template {1}{2}

Category:

Memory

Cause:

FHTTP.ISSUE_REQUEST was unable to allocate adequate memory in the JVM that's issuing the request.

Action:

Specify fewer or smaller request headers or a smaller request body, or modify the selection criteria specified in the request to the external service, so as to limit the size of the response.

FRM-41674

error in Dynamic Monitoring Service (DMS): WebLogic was unable to create a thread to remove unused DMS objects.

Category:

Threads

Cause:

The number of active threads created by the WebLogic server exceeded the limit specified by the <max-concurrent-new-threads> element in weblogic-application.xml, weblogic.xml, or config.xml, as described in 'Configuring Concurrent Managed Objects' in 'Oracle Fusion Middleware Administering Server Environments for Oracle WebLogic Server'.

Action:

No action is necessary if this happens very rarely. Increase the limit if this happens frequently.

FRM-41675

error in Forms prestart processing: WebLogic was unable to create a thread to fill the pool of prestarted Forms runtime processes.

Category:

Threads

Cause:

The number of active threads created by the Weblogic server exceeded the limit specified by the <max-concurrent-new-threads> element in weblogic-application.xml, weblogic.xml, or config.xml, as described in 'Configuring Concurrent Managed Objects' in 'Oracle Fusion Middleware Administering Server Environments for Oracle WebLogic Server'.

Action:

No action is necessary if this happens very rarely. Increase the limit if this happens frequently.

FRM-41690

The reconstructed request line, request headers, and request body (if any) have been written to {0}

Category:

Requests/Responses

Cause:

This message follows FRM-41539, FRM-41569, FRM-41592, and various error messages written by FHTTP.ISSUE_REQUEST, if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 3 or 4.

Action:

No action is required.

FRM-41691

The reconstructed response status line, response headers, and response body (if any) have been written to {0}

Category:

Requests/Responses

Cause:

This message follows FRM-41539 and FRM-41569, if the FORMS_HTTP_DIAGNOSTIC_LEVEL environment variable is set to 4, and various error messages written by FHTTP.ISSUE_REQUEST.

Action:

No action is required.

FRM-41692

The stack trace for the communication error has been written to {0}

Category:

Network

Cause:

This message follows FRM-41660 and FRM-41760.

Action:

No action is required.

FRM-41700

error encrypting credentials for an external service

Category:

Configuration

Cause:

An unexpected error occurred while encrypting credentials for an external service.

Action:

If the problem persists, contact Oracle Support Services.

FRM-41701

error decrypting credentials for an external service

Category:

Configuration

Cause:

An unexpected error occurred while decrypting credentials for an external service.

Action:

If the problem persists, contact Oracle Support Services.

FRM-41712

error in FHTTP.ISSUE_REQUEST: token {0} [{1}] missing from ''authorization_info''

Category:

Data

Cause:

The 'authorization_info' parameter passed to FHTTP.ISSUE_REQUEST (consisting of tokens separated by unit separator characters [u001f]) does not contain the token that was expected at the specified index [1-relative].

Action:

Correct the 'authorization_info' parameter.

FRM-41713

error in FHTTP.ISSUE_REQUEST: invalid value {0} for token {1} [{2}] in ''authorization_info''

Category:

Data

Cause:

The 'authorization_info' parameter passed to FHTTP.ISSUE_REQUEST (consisting of tokens separated by unit separator characters [u001f]) contains an invalid token at the specified index [1-relative]. In particular, token 1 [credential_id] must contain only alphanumeric characters and '_', '.', '-'.

Action:

Correct the 'authorization_info' parameter.

FRM-41714

error in FHTTP.ISSUE_REQUEST: logon dialog potentially required for an authorization that was not the last authorization in ''authorization_info''

Category:

Data

Cause:

The 'authorization_info' parameter passed to FHTTP.ISSUE_REQUEST (consisting of tokens separated by unit separator characters [u001f]) contained multiple authorizations. One of them was of type Basic Authentication or OAuth2 Password. Such an authorization must be the last of the multiple authorizations.

Action:

Correct the 'authorization_info' parameter.

FRM-41715

error in FHTTP.ISSUE_REQUEST: username {0} specified for basic authentication in ''authorization_info'' contains a colon

Category:

Data

Cause:

The 'authorization_info' parameter passed to FHTTP.ISSUE_REQUEST (consisting of tokens separated by unit separator characters [u001f]) specified basic authentication as the authorization (or one of the authorizations). The username specified in token 3 [1-relative] contained a colon, which is not allowed for basic authentication.

Action:

Correct the 'authorization_info' parameter.

FRM-41721

error in FHTTP.ISSUE_REQUEST: authorization failed due to invalid config section name {0}

Category:

Data

Cause:

Authorization for HTTP requests to external services requires that the config section name specified as the config parameter in the frmservlet URL used to launch the Forms application contain only alphanumeric characters and '_', '.', '-'.

Action:

Specify a config section with a valid name in the frmservlet URL used to launch the Forms application.

FRM-41722

error in FHTTP.ISSUE_REQUEST: authorization failed due to missing credential for {0}

Category:

Configuration

Cause:

API Key and OAuth2 authorizations for HTTP requests to external services require that the Oracle Platform Security Services Credential Store contain a generic credential for the external service. The credential key must be of the form <config_section_name>=<credential_id>.

Action:

Use Fusion Middleware Control to add the generic credential. The value must be the key for API Key authorizations, and <client_id><LF><client_password> or <client_id><LF><client_secret> for OAuth2 authorizations. For OAuth2 Password authorizations, <LF><username><LF><password> may optionally be appended to the value. <LF> is the line-feed character [0x0a]. It may optionally be preceded by a carriage-return character [0x0d].

FRM-41723

error in FHTTP.ISSUE_REQUEST: authorization failed due to invalid credential for {0}

Category:

Configuration

Cause:

API Key and OAuth2 authorizations for HTTP requests to external services require that the Oracle Platform Security Services Credential Store contain a valid generic credential for the external service. A generic credential is allowed (but not required) for Basic Authentication authorizations. The credential key must be of the form <config_section_name>=<credential_id>. The value must be a string of the form <username>:<password> for basic authentication, and <client_id><LF><client_password> or <client_id><LF><client_secret> for OAuth2 authorization. For OAuth2 Password authorizations, <LF><username><LF><password> may optionally be appended to the value. <LF> is the line-feed character [0x0a]. It may optionally be preceded by a carriage-return character [0x0d].

Action:

Use Fusion Middleware Control to correct the generic credential.

FRM-41724

error in FHTTP.ISSUE_REQUEST: authorization failed due to rejected credential for {0}

Category:

Configuration

Cause:

The Oracle Platform Security Services Credential Store contained a generic credential value of the form <username>:<password> for a Basic Authentication authorization, or a generic credential value of the form <client_id><LF><client_password_or_secret><LF><username><LF><password> for an OAuth2 Password authorization, but the username and password were rejected by the external service.

Action:

Determine the correct username and password, and use Fusion Middleware Control to correct the generic credential.

FRM-41725

error in FHTTP.ISSUE_REQUEST: authorization failed due to invalid SSO user credential for {0}

Category:

Data

Cause:

In SSO mode, OAuth2 authorization information may be stored in a password credential for the SSO user in the Oracle Platform Security Services Credential Store, and reused for that user in subsequent Forms application sessions. However, when the stored information was subsequently retrieved, it was found to be in an incorrect format.

Action:

If the problem persists, contact Oracle Support Services. As a temporary workaround, you could use Fusion Middleware Control to remove the password credential, or you could disable SSO mode.

FRM-41760

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the request to the token endpoint URL {1} encountered an error communicating with the token endpoint.

Category:

Network

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] encountered an IOException while attempting to communicate with the token endpoint. A subsequent FRM-41692 message indicates where the stack trace for the IOException was written.

Action:

Inspect the stack trace in the response identified by message FRM-41692 in ODL. If the stack trace does not indicate how to fix the problem, and the problem persists, contact the owner of the external service.

FRM-41761

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the request to the token endpoint URL {1} received unexpected response status code {2}. Details: {3}

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] received a response status code other than 200. If the request specified a scope, [scope=<requested_permissions>] will appear in the error message immediately following the token endpoint URL.

Action:

Refer to the details that appear at the end of the message.

FRM-41762

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the token endpoint URL {1} response {2} contained a syntax error or deviated from OAuth2 protocol at offset {3} [characters].

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] received a response containing a violation of the syntax prescribed by RFC 8259 [JSON] and RFC 6749 [OAuth2].

Action:

Try to determine why the erroneous response is being returned, e.g. by contacting the owner of the external service.

FRM-41763

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the token endpoint URL {1} response specified the unsupported token_type {2}.

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] received a response that specified an unsupported token_type. Currently, only "bearer" is supported.

Action:

Redesign the Forms application.

FRM-41764

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the request to the token endpoint URL {1} requested scope={2}, but the response granted only scope={3}.

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] received a response that did not grant all requested permissions.

Action:

If the requested operation does not actually require all the requested permissions, remove the unneeded ones. Otherwise, contact the owner of the external service and/or redesign the Forms application.

FRM-41765

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because an Access Token Location of ''Form Parameter'' was specified, but request content-type was not ''application/x-www-form-urlencoded''.

Category:

Data

Cause:

The Access Token Location specified for OAuth2 authorization [as token 4 of the 'authorization_info' parameter] was 'Form Parameter', but the request content-type header was missing or specified a media type other than 'application/x-www-form-urlencoded'.

Action:

Correct the Access Token Location or the request content-type.

FRM-41766

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the token endpoint URL {1} response did not specify an access token.

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] received a response which did not contain an access token.

Action:

Try to determine why the erroneous response is being returned, e.g. by contacting the owner of the external service.

FRM-41769

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the OAuth2 Token URL {1} was rejected.

Category:

Data

Cause:

The OAuth2 Token URL specified for OAuth2 authorization [as token 5 of the 'authorization_info' parameter] was malformed or did not specify a scheme of 'http', 'https', 'ws', or 'wss'.

Action:

Correct the OAuth2 Token URL.

FRM-41770

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the attempt to redirect to the authorization endpoint URL {1} encountered an error.

Category:

Network

Cause:

A browser was launched to communicate with the OAuth2 authorization server at the OAuth2 Authorization URL specified for OAuth2 authorization [as token 7 of the 'authorization_info' parameter], but the attempt to redirect the browser response to that URL encountered an IOException. A subsequent FRM-41692 message indicates where the stack trace for the IOException was written.

Action:

Inspect the stack trace in the response identified by message FRM-41692 in ODL. If the stack trace does not indicate how to fix the problem, and the problem persists, contact the owner of the external service.

FRM-41771

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the request to the authorization endpoint URL {1} produced an error. Details: {2}

Category:

Requests/Responses

Cause:

The request presented to the OAuth2 Authorization URL specified for OAuth2 authorization [as token 7 of the 'authorization_info' parameter] generated a response that indicated an error. If the request specified a scope, [scope=<requested_permissions>] will appear in the error message immediately following the authorization endpoint URL.

Action:

Refer to the details that appear at the end of the message.

FRM-41774

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the request to the authorization endpoint URL {1} requested scope={2}, but only scope={3} was granted.

Category:

Requests/Responses

Cause:

A scope was specified in the request presented to the OAuth2 Authorization URL specified for OAuth2 authorization [as token 7 of the 'authorization_info' parameter], but the subsequent response from the token endpoint did not grant all requested permissions.

Action:

If the requested operation does not actually require all the requested permissions, remove the unneeded ones. Otherwise, contact the owner of the external service and/or redesign the Forms application.

FRM-41779

error in FHTTP.ISSUE_REQUEST: OAuth2 authorization failed for client {0} because the OAuth2 Authorization URL {1} was rejected.

Category:

Data

Cause:

The OAuth2 Authorization URL specified for OAuth2 authorization [as token 7 of the 'authorization_info' parameter] was malformed or did not specify a scheme of 'http', 'https', 'ws', or 'wss'.

Action:

Correct the OAuth2 Authorization URL.

FRM-41838

runtime process: unable to open temporary record buffer file

Category:

Files

Cause:

The runtime process was unable to open the file used as the temporary record buffer. A preceding FRM-91180 or FRM-91181 error message provides more detail. (FRM-91181 will occur if the error was on the first write attempt).

Action:

Refer to error message FRM-91180 and FRM-91181.

FRM-41839

runtime process: disk I/O error on temporary record buffer file

Category:

Files

Cause:

An I/O error occurred while the runtime process was attempting to read or write a record to the temporary record buffer file. A preceding FRM-91181 or FRM-91182 error message provides more detail.

Action:

Refer to error message FRM-91181 and FRM-91182.

FRM-60000

fatal error configuring Forms component

Category:

Configuration

Cause:

Forms component provisioning failed.

Action:

Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60001

fatal error removing Forms component

Category:

Configuration

Cause:

Forms component deprovisioning failed.

Action:

Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60002

error reading Forms component registration document {0}

Category:

Configuration

Cause:

An error occurred while reading the Forms component registration document.

Action:

Do one of the following: \n1. Make sure that the registration document is valid. \n2. If the registration document is accidentally deleted or modified then reinstall ORACLE_HOME.

FRM-60003

error reading ORACLE_HOME registry file {0}

Category:

Configuration

Cause:

An error occurred while reading the ORACLE_HOME registry file.

Action:

Do one of the following: \n1. Make sure that the ORACLE_HOME registry file exists. \n2. If ORACLE_HOME registry file is accidentally deleted or modified then reinstall ORACLE_HOME.

FRM-60004

error obtaining text contents of the configuration file {0}

Category:

Configuration

Cause:

Failed to read the text contents of the configuration file.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it.

FRM-60005

Directory {0} exists; renaming it to {1}

Category:

Configuration

Cause:

The subdirectory under the Oracle Instance directory already exists and the provisioning process renamed the existing subdirectory.

Action:

No action is required.

FRM-60006

error obtaining the managed server URL

Category:

Configuration

Cause:

Failed to obtain the managed server URL during Windows application deployment.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60007

error creating Windows shortcuts

Category:

Configuration

Cause:

Failed to create Windows shortcuts during configuration.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60008

error creating Forms instance {0}

Category:

Configuration

Cause:

Failed to create Forms instance.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60009

error updating Forms instance {0}

Category:

Configuration

Cause:

Failed to update Forms instance.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60010

error deleting Forms instance {0}

Category:

Configuration

Cause:

Failed to update Forms instance.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60011

error creating non-managed instance configuration

Category:

Configuration

Cause:

Failed to create Forms instance non-managed configuration.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60012

error updating/deleting instance: invalid Forms instance contents {0}

Category:

Configuration

Cause:

Failed to update Forms instance.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60013

error adding missing non-managed instance configuration

Category:

Configuration

Cause:

Failed to add missing Forms instance non-managed configuration.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60101

error registering Forms J2EE application MBeans during the application startup

Category:

Configuration

Cause:

An error occurred while registering the Forms J2EE application runtime MBean or custom configuration files MBeans.

Action:

Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60102

error deregistering Forms J2EE application MBeans during the application shutdown

Category:

Configuration

Cause:

An error occurred while deregistering the Forms J2EE application runtime MBean or custom configuration files MBeans.

Action:

Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60104

error reading the Forms System component instance

Category:

Configuration

Cause:

An error occurred while reading the Forms system component instance information.

Action:

Do one of the following:\n1. If there are multiple Forms system component instance on the same Weblogic machine, make sure that you have followed the steps in the Forms deployment guide.\n2. Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-60114

error reading default configuration path

Category:

Configuration

Cause:

An error occurred while obtaining the default configuration location.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-60201

error initializing identity store

Category:

Configuration

Cause:

An error occurred while reading the identity store configuration file.

Action:

Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60202

Forms J2EE application {0} is already registered with Oracle Internet Directory host {1} under the container {2}. Deregistering it.

Category:

Configuration

Cause:

An attempt was made to re-create an existing Forms J2EE application footprint in Oracle Internet Directory. This may occur when the same Forms J2EE application is redeployed to the domain.

Action:

No action is required.

FRM-60203

error associating Forms application with Oracle Internet Directory host {0}

Category:

Configuration

Cause:

The Forms application footprint in Oracle Internet Directory failed to be created due to one of the following causes:\n 1. Oracle Internet Directory was not accessible.\n 2. The Forms J2EE application footprint password failed to be seeded in Oracle Platform Security Services on the mid-tier.\n 3. An I/O error occurred during storing of Oracle Internet Directory information from the Forms Oracle Internet Directory properties file.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60205

error disassociating Forms application with Oracle Internet Directory host {0}

Category:

Configuration

Cause:

Failed to remove the Forms J2EE application footprint from Oracle Internet Directory due to one of the following causes:\n 1. Oracle Internet Directory was not accessible.\n 2. An error status was returned while deregistering the Forms J2EE application footprint with Oracle Internet Directory.\n 3. Failed to fetch the Forms J2EE application footprint password from Oracle Platform Security Services on the mid-tier.\n 4. An I/O error occurred while cleaning Oracle Internet Directory information from the Forms Oracle Internet Directory properties file.

Action:

Do one of the following:\n 1. Examine the stack trace which accompanies this message, look for status of the IM tier and resolve the issue.\n 2. If using Fusion Middleware Control, make sure that information passed to deregister the Forms J2EE application with Oracle Internet Directory host is valid.\n 3. If the problem persists, contact Oracle Support Services.

FRM-60207

error storing credentials to Oracle Platform Security Services

Category:

Configuration

Cause:

An error occurred while storing the credentials to Oracle Platform Security Services.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60208

error deleting credentials from Oracle Platform Security Services

Category:

Configuration

Cause:

An error occurred while deleting the credentials from Oracle Platform Security Services.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60209

error obtaining credentials from Oracle Platform Security Services

Category:

Configuration

Cause:

An error occurred while reading the credentials from Oracle Platform Security Services.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60210

error obtaining MBean Server connection

Category:

Configuration

Cause:

An error occurred while connecting to the MBean Server.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60211

error migrating Resource Access Descriptor

Category:

Configuration

Cause:

An error occurred migrating Resource Access Descriptor to Oracle Platform Security Services.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60212

Resource Access Descriptor migration process interrupted

Category:

Configuration

Cause:

A running Resource Access Descriptor migration process was interrupted.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60213

error recording the Resource Access Descriptor migration result

Category:

Configuration

Cause:

An error occurred while recording the Resource Access Descriptor migration results.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60214

Forms Resource Access Descriptor migration thread awaken

Category:

Configuration

Cause:

Action:

FRM-60215

error reading the Resource Access Descriptor migration results

Category:

Configuration

Cause:

An error occurred while reading the Resource Access Descriptor migration results.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60216

error starting Forms Resource access migration to Oracle Platform Security Services

Category:

Configuration

Cause:

The Forms Resource Access Descriptor migration to Oracle Platform Security Services failed to start because the previous migration process is still running.

Action:

Wait for the exiting migration process to complete before running migration again.

FRM-60217

invalid Single Sign-on user

Category:

Configuration

Cause:

The user passed an invalid Single Sign-on user name to create a Resource Access Descriptor.

Action:

Provide a valid existing Single Sign-on user name and run the request again.

FRM-60218

error connecting to LDAP server

Category:

Configuration

Cause:

An error occurred while connecting the LDAP server due to one of the following causes: \n1. Invalid connection credentials were entered. \n2. Invalid hostname, port information was entered.\n3. LDAP server is down.

Action:

Examine the cause, and take the appropriate remedial action.

FRM-60220

error initializing the Forms Identity store

Category:

Configuration

Cause:

An error occurred while initializing the Forms Identity store.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60221

error obtaining the Forms identity store access

Category:

Configuration

Cause:

An error occurred while obtaining the Forms Identity store.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60222

error creating the FormsREST OPSS credential store map

Category:

Configuration

Cause:

An error occurred while creating FormsREST OPSS credential map.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60223

error accessing Forms local credential store

Category:

Configuration

Cause:

An error occurred while accessing Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60224

error writing to the Forms local credential store

Category:

Configuration

Cause:

An error occurred writing to the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60225

error reading user from the Forms local credential store

Category:

Configuration

Cause:

An error occurred reading user from the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60226

error decrypting credential in Forms local credential store

Category:

Configuration

Cause:

An error occurred decrypting credential in Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60227

error reading credential from the Forms local credential store

Category:

Configuration

Cause:

An error occurred reading credential from the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60228

error reading credential comments from the Forms local credential store

Category:

Configuration

Cause:

An error occurred reading credential comments from the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60229

error updating credential to the Forms local credential store

Category:

Configuration

Cause:

An error occurred updating credential to the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60230

error storing credential to the Forms local credential store

Category:

Configuration

Cause:

An error occurred storing credential to the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60231

error updating credential: invalid key {0} passed

Category:

Configuration

Cause:

An error occurred updating credential to the Forms local credential store because an invalid key passed.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60232

error updating credential: invalid map {0} passed

Category:

Configuration

Cause:

An error occurred updating credential to the Forms local credential store because an invalid map passed.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60233

error encrypting credential in Forms local credential store

Category:

Configuration

Cause:

An error occurred encrypting credential in Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60234

error initializing Forms local credential store

Category:

Configuration

Cause:

An error occurred initializing Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60235

error deleting credential from the Forms local credential store

Category:

Configuration

Cause:

An error occurred deleting credential from the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60236

error deleting credential: invalid map {0} passed

Category:

Configuration

Cause:

An error occurred deleting credential to the Forms local credential store because an invalid map passed.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60237

error accessing RADs in the Forms local credential store

Category:

Configuration

Cause:

An error occurred accessing RADs in the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60238

error deleting RADs in the Forms local credential store

Category:

Configuration

Cause:

An error occurred deleting RADs in the Forms local credential store.

Action

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60249

error creating Resource Access Descriptor for Forms application {0}: Resource Access Descriptor already exists

Category:

Configuration

Cause:

An error occurred while creating the Resource Access Descriptor because it already exists.

Action:

Edit the existing Resource Access Descriptor rather than adding it.

FRM-60250

error creating Resource Access Descriptor for Forms application {0}

Category:

Configuration

Cause:

An error occurred while creating the Resource Access Descriptor.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60251

error updating Resource Access Descriptor for Forms application {0}

Category:

Configuration

Cause:

An error occurred while updating the Resource Access Descriptor.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60252

error deleting Resource Access Descriptor for Forms application {0}

Category:

Configuration

Cause:

An error occurred while deleting the Resource Access Descriptor.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60253

error reading Resource Access Descriptor for Forms application {0}

Category:

Configuration

Cause:

An error occurred while reading the Resource Access Descriptor.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60254

error obtaining Resource Access Descriptor

Category:

Configuration

Cause:

An error occurred while obtaining the Resource Access Descriptor.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60255

error stashing Single Single-on user information in the Forms session

Category:

Configuration

Cause:

An error occurred while stashing Single Sign-on user information in the Forms session.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60256

permission error reading the Resource Access Descriptor from Oracle Internet Directory

Category:

Configuration

Cause:

Single Sign-on user does not have the right permission to read the Resource Access Descriptor.

Action:

No action is required.

FRM-60257

error reading Forms application {0}, Resource Access Descriptor for Single Sign-on User {1} from Oracle Internet Directory

Category:

Configuration

Cause:

An error occurred while obtaining the Forms application Resource Access Descritor from Oracle Internet Directory.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60258

error reading Forms application Resource Access Descriptor from Oracle Internet Directory

Category:

Configuration

Cause:

An error occurred while obtaining the Forms application Resource Access Descritor from Oracle Internet Directory.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60259

error processing line {0}: invalid syntax

Category:

Configuration

Cause:

An error occurred while processing the indicated line

Action:

Fix the entry and upload RADs again

FRM-60260

error processing line {0}: invalid set of parameters

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Fix the number of parameters at the indicated line

FRM-60261

error processing line {0}: invalid application name

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Add the missing application name and upload RADs again

FRM-60262

error processing line {0}: duplicate entry

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Delete the duplicate entry at the indicated line and upload RADs again

FRM-60263

error processing line {0}: missing Single Sign-on Username

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Add the Single Sign-on Username at the indicated line and upload RADs again

FRM-60264

error processing line {0}: invalid groupRad parameter value

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Fix the isGroupRad parameter value at the indicated line and upload RADs again

FRM-60265

error processing line {0}: missing dbUser parameter value

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Fix the dbUser parameter value at the indicated line and upload RADs again

FRM-60266

error processing line {0}: missing dbPassword parameter value

Category:

Configuration

Cause:

An error occurred while processing the indicated entry

Action:

Fix the dbPassword parameter value at the indicated line and upload RADs again

FRM-60301

invalid character in the file name argument {0}

Category:

Configuration

Cause:

An error occurred due to an invalid character in the file name.

Action:

Remove the invalid character from the file name and execute the operation again.

FRM-60302

error duplicating the configuration file {0} to {1}

Category:

Configuration

Cause:

An error occurred duplicating the configuration file due to one of the following causes: \n1. MBean registration failed. \n2. Failure to create a new file on the file system.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60303

error duplicating the configuration file {0}: invalid document type {1}

Category:

Configuration

Cause:

Invalid document type argument passed to operation.

Action:

Invoke the 'duplicate file' operation only on the supported valid document types (Type_default.env).

FRM-60304

error duplicating configuration file {0}: invalid argument {1} are passed to 'duplicate file' operation

Category:

Configuration

Cause:

The file the user tried to create already exists.

Action:

Pass a different file name for the new file that has to be created.

FRM-60305

error deleting the configuration file {0}

Category:

Configuration

Cause:

An error occurred deleting the configuration file due to one of the following causes: \n1. MBean deregistration failed. \n2. Failure to delete the file from the file system.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60306

error deleting the configuration file {0}: invalid document type {1}

Category:

Configuration

Cause:

An invalid document type argument was passed to the operation.

Action:

Invoke the 'duplicate file' operation only on the supported valid document types (Type_default.env).

FRM-60307

error converting the configuration object to the relevant CompositeType

Category:

Configuration

Cause:

Failed to convert the configuration object to the relevant CompositeType.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60308

error converting the configuration object to the relevant CompositeData

Category:

Configuration

Cause:

Failed to convert the configuration object to the relevant CompositeData.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.

FRM-60309

error registering child config MBean for the application section {0}

Category:

Configuration

Cause:

Failed to register the child config MBean for the given application section.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it.

FRM-60310

error deregistering child config MBean for the application section {0}

Category:

Configuration

Cause:

Failed to deregister the child config MBean for the given application section.

Action:

Examine the stack trace which accompanies this message for the possible cause of failures and correct it.

FRM-60311

error deleting application section {0}

Category:

Configuration

Cause:

An attempt was made to delete the default application section or a section that does not exist.

Action:

Choose the correct section name.

FRM-60312

error creating application section {0}

Category:

Configuration

Cause:

An attempt was made to create an application section that already exists or has an invalid section name.

Action:

Choose an alternative name for the section.

FRM-60313

error duplicating application section {0} to {1}

Category:

Configuration

Cause:

Failed to duplicate an application section because of one of the following reasons:\n 1. An attempt was made to duplicate an invalid application section.\n 2. An attempt was made to create an application section that already exists.

Action:

Do one of the following:\n 1. Choose a correct section name for the duplicated application section.\n 2. Choose an alternative name for the newly created application section.

FRM-60314

error encrypting userid for forms application {0}

Category:

Configuration

Cause:

An unexpected error occurred while encrypting the userid parameter value.

Action:

If the problem persists, contact Oracle Support Services.

FRM-60315

error decrypting userid for forms application {0}

Category:

Configuration

Cause:

An unexpected error occurred while decrupting the the userid parameter value.

Action:

If the problem persists, contact Oracle Support Services.

FRM-60316

error encrypting forms userid

Category:

Configuration

Cause:

An unexpected error occurred while encrypting the userid parameter value.

Action:

If the problem persists, contact Oracle Support Services.

FRM-60317

error creating formsapp keystore

Category:

Configuration

Cause:

An unexpected error occurred while creating the formsapp keystore

Action:

If the problem persists, contact Oracle Support Services.

FRM-60318

error processing configuration, invalid entry at line:{0}

Category:

Configuration

Cause:

An unexpected error occurred while persisting the configuration.

Action:

Fix the configuration and submit it again.

FRM-91108

internal error in runtime process: unable to initialize PL/SQL

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize PL/SQL.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91109

internal error in runtime process: application startup failure

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to start the Toolkit component.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91111

internal error in runtime process: window system startup failure

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to start the window system.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91112

internal error in runtime process: resource manager startup failure

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to start the Toolkit Resource Manager.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91116

internal error in runtime process: Oracle*Image startup failure

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to start Oracle*Image.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91119

internal error in runtime process: Oracle*VGS startup failure

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to start Oracle*VGS.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91124

fatal error in runtime process: {0} specified for FORMS_DECIMAL_PREFIX. Should be zero or the empty string

Category:

Configuration

Cause:

An invalid value was specified for the environment variable FORMS_DECIMAL_PREFIX.

Action:

Do one of the following: \n1. Specify FORMS_DECIMAL_PREFIX as '0' to force a zero before a leading decimal point in any number displayed without a format mask in the application. \n2. Specify FORMS_DECIMAL_PREFIX as '' (the empty string).

FRM-91126

fatal error in runtime process: invalid value {0} specified for environment variable {1}

Category:

Configuration

Cause:

An invalid environment variable value was specified. An example would be an invalid timezone for an environment variable that specifies a timezone.

Action:

Correct the environment variable value.

FRM-91127

runtime process: invalid directory name specified for environment variable {0}

Category:

Configuration

Cause:

An invalid value was specified for an environment variable that represents the name of a directory. Specifically, the value is too long: either it is itself longer than a system-imposed maximum, or a subdirectory name that Forms needs to construct would be longer than the system-imposed maximum. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, the functionality that required this environment variable was disabled.

Action:

If this error message appears for DOMAIN_HOME or FORMS_INSTANCE_NAME, and the problem persists, contact Oracle Support Services. Otherwise, correct the environment variable value.

FRM-91128

runtime process warning: invalid value {0} specified for environment variable {1}; using default {2}

Category:

Configuration

Cause:

An invalid environment variable value was specified. The indicated default value was used, and processing continued.

Action:

Correct the environment variable value.

FRM-91129

runtime process: no value specified for required environment variable {0}

Category:

Configuration

Cause:

A required environment variable was not set or was set to the empty string. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, the functionality that required this environment variable was disabled.

Action:

If this error message appears for DOMAIN_HOME or FORMS_INSTANCE_NAME, and the problem persists, contact Oracle Support Services. Otherwise, set the environment variable to a non-empty value.

FRM-91132

fatal error in runtime process: invalid data in timezone file {0}

Category:

Configuration

Cause:

The timezone file (specified by the environment variable FORMS_TZFILE) was found to contain invalid data.

Action:

Correct the FORMS_TZFILE environment variable value. It should specify $ORACLE_HOME/oracore/zoneinfo/timezone.dat or $ORACLE_HOME/oracore/zoneinfo/timezlrg.dat.

FRM-91134

fatal error in runtime process: NLS_LANG specifies unsupported character set

Category:

Configuration

Cause:

The NLS_LANG environment variable specified a character set which is not ASCII-based, e.g. fixed-width Unicode or an EBCDIC-based character set.

Action:

Correct the NLS_LANG environment variable value.

FRM-91135

fatal error in runtime process: message file {0} is missing

Category:

Configuration

Cause:

The specified message file was not found.

Action:

Verify that the file has not been moved or deleted. If necessary, reinstall it.

FRM-91137

runtime process: unable to open log file {0}

Category:

Configuration

Cause:

An invalid name was specified for a log file or a trace file. The name might be too long, or it might specify a non-existent or read-only directory. In the former case, the error message shows the name truncated at the maximum allowable length, followed by 3 dots. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, messages that subsequently would have been written to the file were silently discarded.

Action:

Correct the environment variable used to specify the directory (e.g. FORMS_TRACE_DIR), and/or the file name proper (which might have been specified e.g. by the value of the 'log' configuration parameter). If no environment variable or configuration parameter was set to specify the directory or the file name proper, and the problem persists, contact Oracle Support Services.

FRM-91138

runtime process: unable to create log file {0}

Category:

Configuration

Cause:

An attempt to open, write, or close a log file failed.

Action:

Verify that the directory specified for the log file has appropriate write privileges and adequate disk space.

FRM-91143

internal error in runtime process: unable to create runform global context

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to create the runform global context.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91144

internal error in runtime process: unable to parse user name

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to parse the user name.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91145

fatal error in runtime process: missing serverArgs parameter

Category:

Configuration

Cause:

If this error occurred when using the Forms Servlet, both the serverArgs configuration parameter and the serverArgs applet parameter (either of which can represent the command-line arguments that are passed to the frmweb executable) were either missing or had a blank value. If this error occurred for static HTML (HTML that's not generated by the Forms Servlet), the serverArgs applet parameter was either missing or had a blank value.

Action:

If this error occurred for static HTML, add a serverArgs parameter to the applet. Otherwise, ensure that the Forms Servlet configuration file or the base HTML files correctly define a serverArgs parameter. [Note that the base HTML files that are shipped with the produce omit the serverArgs parameter, but the shipped Forms Servlet configuration file specifies a non-blank value.]

FRM-91150

internal error in runtime process: unable to initialize Oracore program manager

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize the Oracore program manager.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91151

internal error in runtime process: unable to initialize Oracle NLS

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize Oracle NLS.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91152

internal error in runtime process: unable to set environment variable {0}

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to set an environment variable to a new value.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91153

internal error in runtime process: unable to initialize Common Area component

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize the Common Area component.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91154

internal error in runtime process: unable to initialize Oracore date component

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize the Oracore date component.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91157

internal error in runtime process: unable to redirect stderr to stdout

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to redirect stderr to stdout. This error should never occur at a customer site.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91160

BI Publisher integration error: {0}

Category:

Configuration

Cause:

The runtime process attempted to communicate with BI Publisher but an exception occurred. Some more information about the specific exception is included in this message, which may help to resolve the problem.

Action:

Attempt to use the information provided to resolve the problem. If the problem persists, contact Oracle Support Services.

FRM-91170

runtime process: JVM exiting with code {0}

Category:

Process

Cause:

The runtime process had started a JVM (in order to run Oracle Reports or the Forms debugger, or to update a password in Oracle Internet Directory). That JVM started exiting.

Action:

No action is required.

FRM-91171

runtime process: JVM aborting

Category:

Process

Cause:

The runtime process had started a JVM (in order to run Oracle Reports or the Forms debugger, or to update a password in Oracle Internet Directory). That JVM started aborting.

Action:

No action is required. However, if there appear to be problems running Oracle Reports or the Forms debugger, or updating a password in Oracle Internet Directory, this message may help to indicate the cause.

FRM-91180

fatal error in runtime process: error {0} ({1}) attempting to open temporary record buffer file

Category:

Files

Cause:

An attempt to open the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. The runtime process was terminated.

Action:

Examine the error string, and take appropriate remedial action. Verify that the file system or directory in which the file resides exists and that the runtime process has permissions to read and write to the file system or directory.

FRM-91181

runtime process: error {0} ({1}) attempting to write {2} bytes to offset {3} of temporary record buffer file {4}

Category:

Files

Cause:

The specified 'write' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action:

Examine the error string, and take appropriate remedial action. Verify that the file system or directory in which the file resides exists, and that the runtime process has permissions to read and write to the file system or directory, and that the file system contains sufficient space.

FRM-91182

runtime process: error {0} ({1}) attempting to read {2} bytes from offset {3} of temporary record buffer file {4}

Category:

Files

Cause:

The specified 'read' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued, for the moment at least; however, the error is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action:

Examine the error string, and take appropriate remedial action.

FRM-91183

runtime process: error {0} ({1}) attempting to allocate {2} bytes at offset {3} of temporary record buffer file {4}

Category:

Files

Cause:

The specified 'allocate' operation ('fallocate' on Linux and 'posix_fallocate' on other Unix platforms) to the temporary record buffer file encountered the indicated error. Both the error number (errno) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action:

Examine the error string, and take appropriate remedial action. Verify that the file system or directory in which the file resides exists, and that the runtime process has permissions to read and write to the file system or directory, and that the file system contains sufficient space.

FRM-91184

runtime process: error {0} ({1}) attempting to truncate or extend temporary record buffer file {2} to {3} bytes

Category:

Files

Cause:

The specified 'ftruncate' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action:

Examine the error string, and take appropriate remedial action. Verify that the file system or directory in which the file resides exists, and that the runtime process has permissions to read and write to the file system or directory, and that the file system contains sufficient space.

FRM-91185

runtime process: error {0} ({1}) attempting to close temporary record buffer file {2}

Category:

Files

Cause:

An attempt to close the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued; however, it's possible that the temporary record buffer file was not deleted properly.

Action:

Examine the error string, and take appropriate remedial action.

FRM-91190

fatal error in runtime process: unable to allocate {0} bytes of memory

Category:

Memory

Cause:

A critical memory allocation request failed. This may indicate insufficient swap space. Execution of the runtime process was terminated.

Action:

Increase the size of the swap space, or rerun the application when the system is less heavily loaded.

FRM-91191

runtime process: unable to allocate {0} bytes of memory; attempting to continue execution

Category:

Memory

Cause:

A memory allocation request failed. This may indicate insufficient swap space. Execution continued, but the current operation (e.g. the loading of a form) failed. And a subsequent critical memory allocation may have failed, thereby terminating the runtime process.

Action:

Increase the size of the swap space, or rerun the application when the system is less heavily loaded.

FRM-91192

fatal error in runtime process: unable to memory-map {0} bytes of memory

Category:

Memory

Cause:

A memory-map request failed. This probably indicates insufficient swap space. Execution of the runtime process was terminated.

Action:

Increase the size of the swap space, or rerun the application when the system is less heavily loaded.

FRM-91193

runtime process: unable to memory-map {0} bytes of memory; attempting to continue execution

Category:

Memory

Cause:

A memory-map request failed. This probably indicates insufficient swap space. Execution continued, but the current operation (e.g. the loading of a form) failed. And a subsequent critical memory allocation may have failed, thereby terminating the runtime process.

Action:

Increase the size of the swap space, or rerun the application when the system is less heavily loaded.

FRM-91194

fatal error in runtime process: unable to allocate memory for critical record manager operation

Category:

Memory

Cause:

A memory allocation failure (reported in a preceding FRM-91191 message) occurred while attempting a record manager operation, and the operation was subsequently deemed critical. Execution of the runtime process was terminated.

Action:

Increase the size of the swap space, or rerun the application when the system is less heavily loaded.

FRM-91195

fatal error in runtime process: cannot recover from disk I/O error on temporary record buffer file

Category:

Files

Cause:

A disk I/O error on the temporary record buffer file (reported in a preceding FRM-41839 message and in a FRM-91181 or FRM-91182 message preceding that) caused a critical operation to fail. Execution of the runtime process was terminated. Note that an "out of space" error on a write is *not* fatal.

Action:

Examine the preceding FRM-91181 or FRM-91182 message.

FRM-91196

fatal error in runtime process: unable to memory-map {0} bytes of memory backed by a file

Category:

Memory

Cause:

A memory-map request backed by a file failed. This probably indicates insufficient space in the file system (e.g. /tmp). Execution of the runtime process was terminated.

Action:

Increase the size of the file system, or rerun the application when the system is less heavily loaded.

FRM-91197

runtime process: unable to memory-map {0} bytes of memory backed by a file; attempting to continue execution

Category:

Memory

Cause:

A memory-map request backed by a file failed. This probably indicates insufficient space in the file system (e.g. /tmp). Execution continued, but the current operation (e.g. the loading of a form) failed. And a subsequent critical memory allocation may have failed, thereby terminating the runtime process.

Action:

Increase the size of the file system, or rerun the application when the system is less heavily loaded.

FRM-91199

internal error in runtime process: assertion failure: file {0}, line {1}

Category:

Process

Cause:

An assertion failed in code that the runtime process was executing.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91200

fatal error in runtime process: error reading HTTP header

Category:

Network

Cause:

A fatal error occurred while attempting to read an HTTP header.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.

FRM-91210

fatal error in runtime process: error reading HTTP data

Category:

Network

Cause:

A fatal error occurred while attempting to read HTTP data.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.

FRM-91220

fatal error in runtime process: error writing HTTP data

Category:

Network

Cause:

A fatal error occurred while attempting to write HTTP data.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.

FRM-91230

fatal error in runtime process: timeout on connection to Java client

Category:

Network

Cause:

The runtime process was waiting for a message from the Java client, but none appeared within the timeout interval. (This interval defaults to 15 minutes, but can be overridden by the FORMS_TIMEOUT environment variable.)

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process. Also check to see if the Forms applet on the Java client experienced a fatal error.

FRM-91260

internal error in runtime process: unable to initialize the Winsock DLL

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to initialize the Winsock DLL.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91270

runtime process unable to allocate socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to allocate a socket for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed.\n NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91272

runtime process unable to set close-on-exec on socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to set close-on-exec. The error message from the operating system is displayed. The runtime process attempted to continue execution.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91273

runtime process unable to enable local address reuse on socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to enable local address reuse. The error message from the operating system is displayed.\n NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91274

runtime process unable to translate hostname ({0}) to an address for protocol {1}: {2}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6) correctly, because the hostname could not be translated to an address. The error message from the operating system is displayed.\n NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91275

runtime process unable to bind socket address for port {0} to socket for protocol {1}: {2}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to bind the socket address for the indicated port to it. The error message from the operating system is displayed.\n NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91276

runtime process unable to obtain port number of socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to obtain the port number of the socket that it allocated for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed. This error should never occur at a customer site.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91277

internal error in runtime process: unable to write port and process ID information to stderr

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to write port and process ID information to standard error. This error should never occur at a customer site.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91278

runtime process unable to listen for connections on socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to listen for connections. The error message from the operating system is displayed.\n NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91279

runtime process unable to restrict IPv6 socket to IPv6 only: {0}

Category:

Process

Cause:

The runtime process was unable to configure the socket that it allocated for IPv6, to restrict its use to IPv6 only (as opposed both IPv6 and IPv4). The error message from the operating system is displayed. The runtime process attempted to continue execution, but a subsequent attempt to bind the socket might fail with the error "address already in use".

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91280

runtime process unable to set non-blocking I/O on socket for protocol {0}: {1}

Category:

Process

Cause:

The runtime process was unable to set non-blocking I/O on the socket that it allocated for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed. The runtime process attempted to continue execution.

Action:

If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91292

internal error in runtime process: invalid initial message from Java client

Category:

Process

Cause:

The initial message from the Java client to the runtime process was not in the expected format.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91293

internal error in runtime process: invalid initial message from servlet

Category:

Process

Cause:

The initial message from the servlet to the runtime process was not in the expected format.

Action:

If the problem persists, contact Oracle Support Services.

FRM-91299

fatal error in runtime process: unable to create a connection to the Java client

Category:

Process

Cause:

An unexpected error occurred while the runtime process was attempting to create a connection to the Java client. Usually, a previous message provides more detail.

Action:

If a previous error message indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-91930

message from Forms application: {0}

Category:

Other

Cause:

The Forms application called the MESSAGE built-in with an option of ODL_DEBUG.

Action:

Respond as directed by the application developer.

FRM-91934

message from Forms application: {0}

Category:

Other

Cause:

The Forms application called the MESSAGE built-in with an option of ODL_NOTIFICATION.

Action:

Respond as directed by the application developer.

FRM-91935

message from Forms application: {0}

Category:

Other

Cause:

The Forms application called the MESSAGE built-in with an option of ODL_WARNING.

Action:

Respond as directed by the application developer.

FRM-91936

message from Forms application: {0}

Category:

Other

Cause:

The Forms application called the MESSAGE built-in with an option of ODL_ERROR.

Action:

Respond as directed by the application developer.

FRM-91940

module {0} loaded by Forms runtime process

Category:

Other

Cause:

The Forms application caused the specified module to be opened.

Action:

No action is required.

FRM-91990

runtime process: A maximum of {0}K bytes were simultaneously allocated for archived record data.

Category:

Performance

Cause:

The runtime process allocated the indicated amount of memory without reserving swap space or /tmp file space. The memory will be included in many reports of memory usage (such as the output of the Linux pmap command), but it will not consume system resources (real memory or disk) until it is actually used for archived record data. (See FRM-91992).

Action:

No action is required.

FRM-91991

runtime process: A maximum of {0}K bytes were simultaneously allocated and reserved for archived record data.

Category:

Performance

Cause:

The runtime process allocated the indicated amount of memory, and reserved swap space or /tmp file space for it.

Action:

No action is required. However, if the number reported by this message is significantly larger than the number reported by FRM-91992 and you are using mapped-memory archiving (FORMS_RECMGR_ARCHIVE unset, or set to MAP_SWAP or MAP_TMPFILE), you may want to reduce the value of FORMS_RECMGR_BLOCK_SIZE (which defaults to 64K when memory is being reserved, but can be set as low as 32K). Better yet, don't reserve memory that's allocated for archived record data, if possible. (This can be accomplished in most Unix installations, by setting FORMS_RECMGR_RESERVE_SPACE to '0').

FRM-91992

runtime process: A maximum of {0}K bytes were simultaneously in use for archived record data.

Category:

Performance

Cause:

The runtime process used the indicated amount of memory for archived record data. Specifically, at time of maximum usage, it (the runtime process) had written data into the pages of memory, and the data was still needed at that point (because there was a possibility that the record might subsequently need to be activated). Note that when FORMS_RECMGR_ARCHIVE has been set to WRITE_TMPFILE, the runtime process has no way of notifying the file system when it no longer needs a page, and so the file system may retain an unneeded page in a real-memory buffer for a while. Thus, in this case the number reported by this message should be viewed as lower bound.

Action:

No action is required. However, the numbers reported by this message for various applications may help to determine an appropriate value for FORMS_RECMGR_ARCHIVE_THRESHOLD.

FRM-91994

runtime process: When total memory in use for archived record data was at its maximum, record groups required {0}K bytes for archived record data, plus approximately {1}K additional bytes for active record data and record anchors. If FORMS_RECMGR_USED_FOR_RECGRPS were set to FALSE, a total of approximately {2}K bytes would instead have been required.

Category:

Performance

Cause:

At the point in time when total memory in use for archived record data was at its maximum (as reported by FRM-91992), the runtime process used the sum of the first two amounts for all data and anchors for all records in record groups, but would instead have used the third amount if FORMS_RECMGR_USED_FOR_RECGRPS had been set to FALSE.

Action:

No action is required. However, the numbers reported by this message for various applications may help to determine the appropriate value for FORMS_RECMGR_USED_FOR_RECGRPS. [Bear in mind that TRUE (the default) requires more CPU than FALSE.]

FRM-91995

runtime process: The record manager is currently consuming the following for {0}: {1}

Category:

Performance

Cause:

The Forms application issued a call to the GET_RECMGR_STATS built-in, which then issued this message. The parameter {1} in this message is a formatted report of the amount of various types of memory currently being consumed for record data of the type indicated by the parameter {0} in this message (which corresponds to the argument passed to GET_RECMGR_STATS: all_record_data, archived_record_data, active_record_data, or record_anchors). The formatted report lists Kbytes of memory for the following 6 types of memory: MALLOCED, MAPPED, MAPPED_IN_USE, MAPPED_RESERVED, WRITTEN, WRITTEN_IN_USE.

Action:

No action is required.

FRM-93100

Initializing the Forms Servlet. Initialization parameters are:{0}

Category:

Configuration

Cause:

The Forms Servlet was being initialized.

Action:

No action is required.

FRM-93110

No Forms Servlet configuration file is specified.

Category:

Configuration

Cause:

The configFileName initialization parameter was not specified.

Action:

Specify the full name in the servlet parameter configFileName, the system property oracle.forms.configFileName, or the servlet context parameter configFileName.

FRM-93111

Cannot find Forms Servlet configuration file {0}.

Category:

Configuration

Cause:

The Forms Servlet configuration file (specified by the configFileName initialization parameter) was not found.

Action:

Verify that the configFileName initialization parameter specifies the correct value. (The value is taken from the servlet parameter configFileName, the system property oracle.forms.configFileName, or the servlet context parameter configFileName.) Create the file if necessary.

FRM-93112

error reading Forms Servlet configuration file {0}

Category:

Files

Cause:

An I/O error occurred while reading the specified file.

Action:

If the error persists, determine if the file has been damaged. Re-create the file if necessary.

FRM-93113

syntax error at line {0} in configuration file {1}: invalid section name "{2}"

Category:

Configuration

Cause:

The specified configuration file contained an invalid section name.

Action:

Provide a valid section name.

FRM-93114

Forms Servlet configuration file {0} contains invalid data.

Category:

Configuration

Cause:

A syntax error was detected while parsing the specified file.

Action:

A preceding FRM-93113 or FRM-93142 error message will provide more information. Take the action indicated for the FRM-93113 or FRM-93142 message.

FRM-93115

error reading ORACLE_HOME registry file

Category:

Configuration

Cause:

An error occurred while reading the ORACLE_HOME registry file.

Action:

Do one of the following:\n1. Make sure that the ORACLE_HOME registry file exists.\n2. If ORACLE_HOME registry file is accidentally deleted or modified then reinstall ORACLE_HOME.

FRM-93121

Cannot find environment variable configuration file {0}.

Category:

Configuration

Cause:

One of the following occurred. (The first is by far the most likely.) Note that an envFile parameter may specify a relative path; if it was not found in the current directory, Forms will search for it in the directory that contains the Forms Servlet configuration file. \n1. The envFile configuration parameter for this application specified a nonexistent file. A preceding FRM-93141 error message provides details. \n2. The envFile configuration parameter for this application specified a file that existed when the Forms Servlet extracted the parameter, but the file subsequently disappeared. \n3. No envFile configuration parameter that would apply to this application was specified, and the envFile servlet parameter specified a nonexistent file.

Action:

Take action depending on the cause. \n1. Take action indicated for the preceding FRM-93141 error message. \n2. Re-create the file, or correct the envFile configuration parameter. \n3. Verify that the envFile servlet parameter specifies the correct value. Create the file if necessary.

FRM-93122

error reading environment variable configuration file {0}

Category:

Files

Cause:

An I/O error occurred while reading the specified file.

Action:

If the error persists, determine if the file has been damaged. Re-create the file if necessary.

FRM-93124

Environment variable configuration file {0} contains invalid data.

Category:

Configuration

Cause:

The specified configuration file contained an invalid section name.

Action:

Provide a valid section name.

FRM-93128

invalid value {0} specified for environment variable FORMS_HTTP_PROXY_PORT or FORMS_HTTPS_PROXY_PORT; proxy host ignored.

Category:

Configuration

Cause:

This error is typically detected when attempting to access an external service (e.g. a REST service). An invalid environment variable value (non-numeric, < 0, or > 65535) was specified for FORMS_HTTP_PROXY_PORT or FORMS_HTTPS_PROXY_PORT. The value that was specified for FORMS_HTTP_PROXY_HOST or FORMS_HTTPS_PROXY_HOST was ignored, and processing continued. However, in the absence of a proxy, the attempt to access the external service may fail.

Action:

Correct the environment variable value.

FRM-93130

No base HTML file is specified.

Category:

Configuration

Cause:

Java Web Start was not enabled, but the basehtml configuration parameter was not specified, nor was the basehtmljpi configuration parameter, where relevant. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about which configuration parameter is appropriate.) The FRM-93140 error message provides details about which configuration sections were searched. (Note that the error message will always refer to the basehtml configuration parameter, not the basehtmljpi configuration parameter.)

Action:

Specify the appropriate configuration parameter.

FRM-93131

Cannot find base HTML file {0}.

Category:

Configuration

Cause:

Java Web Start was not enabled, but the specified base HTML file was not found. This file is typically specified by the basehtml configuration parameter, but in certain cases may be specified by the basehtmljpi configuration parameter. The FRM-93141 error message provides details. Note that the parameter may specify a relative path; if the file is not found in the current directory, Forms will search for the file in the directory that contains the Forms Servlet configuration file.

Action:

Verify that the parameter specifies the correct file. Create the file if necessary.

FRM-93132

error reading base HTML or JNLP file {0}

Category:

Files

Cause:

An I/O error occurred while reading the specified file.

Action:

If the error persists, determine if the file has been damaged. Re-create the file if necessary.

FRM-93134

No base JNLP file is specified.

Category:

Configuration

Cause:

Java Web Start was enabled or a JNLP file was embedded in the HTML file, but the basejnlp configuration parameter was not specified. The FRM-93140 error message provides details about which configuration sections were searched.

Action:

Specify the basejnlp configuration parameter.

FRM-93135

Cannot find base JNLP file {0}.

Category:

Configuration

Cause:

Java Web Start was enabled or a JNLP file was embedded in the HTML file, but the specified base JNLP file was not found. This file is specified by the basejnlp configuration parameter. The FRM-93141 error message provides details. Note that the parameter may specify a relative path; if the file is not found in the current directory, Forms will search for the file in the directory that contains the Forms Servlet configuration file.

Action:

Verify that the basejnlp parameter specifies the correct file. Create the file if necessary.

FRM-93136

no base TXT file specified for Oracle Forms Standalone Application

Category:

Configuration

Cause:

The baseSAAfile configuration parameter was not specified.

Action:

Specify the baseSAAfile configuration parameter.

FRM-93140

Section [{0}] of Forms Servlet configuration file {1} does not specify (or inherit) a value for the required parameter {2}.

Category:

Configuration

Cause:

A required configuration parameter was not specified in the indicated configuration section or in a parent section.

Action:

Specify the parameter value in the indicated section, or in a parent section. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about what values are expected.)

FRM-93141

Section [{0}] of Forms Servlet configuration file {1} specifies the nonexistent file {2} for parameter {3}.

Category:

Configuration

Cause:

A configuration parameter in the indicated configuration section specified the name of a nonexistent file.

Action:

Verify that the parameter specifies the correct file. Create the file if necessary.

FRM-93142

Section [{0}] of Forms Servlet configuration file {1} specifies the invalid value "{2}" for parameter {3}.

Category:

Configuration

Cause:

An invalid configuration parameter value was specified in the indicated configuration section. Note that invalid values for certain crucial parameters (such as HTMLdelimiter) will cause a subsequent error, FRM-93114.

Action:

Correct the parameter value. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about what values are expected.)

FRM-93143

Oracle Forms Standalone Launcher checksum failed.

Category:

Configuration

Cause:

The checksum received from the client did not match the Oracle Forms Standalone Launcher jar.

Action:

Contact your system administrator or get the latest Oracle Forms Standalone Launcher file.

FRM-93144

error while generating checksum of Oracle Forms Standalone Launcher file

Category:

Configuration

Cause:

An I/O error occurred while generating the checksum.

Action:

Check if Oracle Forms Standalone Launcher file exists.

FRM-93153

New connections to this Forms Servlet are not being allowed. Attempting to redirect connection attempt to {0}.

Category:

Configuration

Cause:

The allowNewConnections configuration parameter was false, and a value was specified for the connectionDisallowedURL configuration parameter. Redirection will be attempted to that URL.

Action:

No action is required.

FRM-93154

The Forms Servlet is not allowing new connections.

Category:

Configuration

Cause:

The allowNewConnections configuration parameter was false, and either no value was specified for the connectionDisallowedURL configuration parameter, or else redirection to the specified URL failed.

Action:

If a value is specified for the connectionDisallowedURL configuration parameter (as indicated in error message FRM-93153), check to see if the specified URL is malformed; if so, correct the URL. Otherwise, no action is required.

FRM-93156

The Forms Servlet is unable to contact the Forms Load Balancing Server at {0}:{1}.

Category:

Configuration

Cause:

The Forms Servlet was unable to contact the indicated Forms Load Balancing Server, and the MetricsServerErrorURL configuration parameter was not specified.

Action:

Do one or both of the following. \n1. Determine why the server is unavailable, and correct the condition. \n2. Specify a value for the MetricsServerErrorURL parameter in the Forms Servlet configuration file.

FRM-93160

unexpected error while obtaining the JVM pid

Category:

Process

Cause:

An Exception was encountered while obtaining the JVM process ID.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93162

unexpected error loading native library {0}

Category:

Process

Cause:

An Exception was encountered while loading native library.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93176

Command "{0}" is using default ORACLE_HOME setting: {1}.

Category:

Configuration

Cause:

A test command has retrieved the specified value for the ORACLE_HOME environment variable, from the environment variable configuration file specified by the envFile parameter in the default section of the Forms Servlet configuration file.

Action:

No action is required.

FRM-93180

Initializing ListenerServlet. Initialization parameters are: {0}

Category:

Configuration

Cause:

The Forms Listener Servlet was being initialized.

Action:

No action is required.

FRM-93196

Process list file {0} does not exist or is not writable; process list disabled.

Category:

Configuration

Cause:

When a runtime process was started or stopped, an attempt was made to write an updated list of runtime processes to the specified file, but it did not exist or was not writable. Note that the name of the process list file is obtained from the em_process_file parameter in the URL, the Forms Servlet configuration file, or the environment variable configuration file.

Action:

Verify that the em_process_file parameter specifies the correct file. If necessary, create the file or make it writable, or both.

FRM-93197

unexpected error while obtaining the application name from JRF

Category:

Configuration

Cause:

An Exception was encountered while obtaining the application name from JRF.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93198

unexpected error while obtaining the cluster name from JRF

Category:

Configuration

Cause:

An Exception was encountered while obtaining the cluster name from JRF.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93211

error decoding query string using {0} encoding. Spaces generated from "+" in the value of otherparams may be converted to "%20".

Category:

Configuration

Cause:

There was a mismatch between the way that the browser encoded multibyte characters and the way that the Forms Servlet decoded them. This could indicate an invalid value for the defaultcharset parameter in the configuration file, or possibly a problem in either the browser or Oracle software.

Action:

If the site uses the otherparams parameter in any URLs, verify that the defaultcharset parameter in the configuration file is correct; if the defaultcharset parameter is correct, contact Oracle Support Services. Otherwise, no action is required.

FRM-93214

internal buffer ({0} bytes) not big enough to read request content ({1} bytes)

Category:

Requests/Responses

Cause:

An internal buffer was not big enough to read the content of a request from the Java client. The FRM-93214 error message provides supplemental detail for the FRM-93218 error message.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93217

unable to read whole request from client: expected {0}, got {1}

Category:

Requests/Responses

Cause:

A fatal error occurred while reading the content of a request from the Java client. The FRM-93217 error message provides supplemental detail for the FRM-93218 error message.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.

FRM-93218

fatal error reading client request content

Category:

Requests/Responses

Cause:

A fatal error occurred while attempting to read the content of a request from the Java client. A preceding FRM-93214 or FRM-93217 error message might provide more detail.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.

FRM-93226

fatal error redirecting response to {0}

Category

Requests/Responses

Cause:

A fatal error occurred while redirecting a response. A subsequent FRM-93227 will display the stack trace

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.

FRM-93227

stack trace for preceding FRM-93226:

Category

Requests/Responses

Cause:

This message displays the stack trace associated with the preceding FRM-93226 message.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.

FRM-93228

fatal error writing response to client

Category:

Requests/Responses

Cause:

A fatal error occurred while writing a response to the Forms Java client.

Action:

Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.

FRM-93240

Multiple Forms applications cannot share an HTTP session.

Category:

Session

Cause:

A Forms application was launched in such a way that it attempted to share an HTTP session with an already running Forms application. This might result from one of the following:\n1. The user selected File, then New, then Browser Window (or Ctrl+N) in Internet Explorer while the servlet session was being tracked using cookies (that is, session cookies were enabled). In this case Forms does not support creating a new session for the second window.\n2. An application attempted to launch multiple Forms applications, and session cookies were enabled in the Forms application.\n3. An application attempted to launch multiple Forms applications using POST, cookies were disabled in the Forms application, and the launching application specified the same cookie name as did the Forms application.

Action:

Take action depending on the cause.\n1. No action is required.\n2. Disable session cookies in the Forms application.\n3. Change the cookie name in the launching application or the Forms application. This can be accomplished via <cookie-name> under <session-descriptor> in the weblogic.xml deployment descriptor.

FRM-93245

HTTP session not found on target server; possible load balancer configuration issue.

Category:

Session

Cause:

A GET request to the Forms Servlet or Forms Listener Servlet that was not for SSO Web Start specified a session ID (e.g. jsessionid) in a cookie or the URL, but no matching HTTP session was found on the server machine to which the request was directed. This might result from one of the following:\n1. A load balancer was not correctly configured to support sticky sessions.\n2. (1) cookies were disabled in weblogic.xml, (2) an intermediate agent timed out while an Oracle Forms Standalone application was waiting for an end user to do SSO login or to submit a Resource Access Descriptor (RAD) during SSO authentication, and (3) the preserveHttpSessionId configuration parameter was not set to true.

Action:

Take action depending on the cause.\n1. Verify that the load balancer is correctly configured to support session stickiness.\n2. Try reducing the value specified for the ssoSaaWaitInterval configuration parameter. [It defaults to 25 seconds.] Note that setting the preserveHttpSessionId configuration parameter to true will produce the more illuminating FRM-93248 in this case [i.e. when conditions (1) and (2) are true].

FRM-93248

connection to the server apparently closed after a request had executed for {0,number,#0.000} seconds, probably due to an intermediate agent timing out

Category:

Configuration

Cause:

This message may appear in the terminal window from which a Standalone application was launched. The Oracle Forms Standalone Launcher was waiting for SSO authentication to complete. When the wait exceeds the interval specified by the ssoSaaWaitInterval configuration parameter, the original request returns and the Standalone Launcher issues a new request, repeating until SSO authentication is complete. However, it appears that one of those requests failed, probably due to a timeout in an intermediate agent, which in turn caused the connection to the server to be closed.

Action:

Reduce the value specified for the ssoSaaWaitInterval configuration parameter. [It defaults to 25 seconds.]

FRM-93249

launch of browser window to be used for SSO authentication of an Oracle Forms Standalone application timed out after {0} seconds

Category:

Configuration

Cause:

This message will appear in the terminal window from which the Standalone application was launched. One of the following occurred:\n1. The browser was not launched at all, probably because java.awt.Desktop is not supported on the current platform. This message will be preceded by an FRM-92493 error message.\n2. The browser was launched, but the request generated by its initial URL did not specify a valid HTTP session, probably because a load balancer did not direct the request to the correct server. An FRM-93245 error message will appear on the launched browser window.\n3. A slow network or an overloaded client machine prevented the browser launch from completing within the indicated time interval (specified by the ssoSaaBrowserLaunchTimeout configuration parameter). The time interval is measured from the initial invocation of frmsal.jar that launched the application.

Action:

Take action depending on the cause.\n1. Launch the Standalone application on a platform which supports java.awt.Desktop.\n2. Verify that the load balancer is correctly configured to support session stickiness.\n3. Increase the value specified by ssoSaaBrowserLaunchTimeout configuration parameter.

FRM-93250

Forms session started.

Category:

Session

Cause:

This message was generated on the initial request from the browser to the Forms Servlet, before an HTTP session was created.

Action:

No action is required.

FRM-93251

Runtime session started for client {0} (IP address {1}).

Category:

Session

Cause:

This message was generated when the runtime process was created (typically just after the HTTP session was created). If performance monitoring was requested, it started at this point.

Action:

No action is required.

FRM-93252

Forms session ended.

Category:

Session

Cause:

This message was generated when the runtime process was terminated. If performance monitoring was requested, it stopped at this point.

Action:

No action is required.

FRM-93301

Fatal authentication error: Unable to connect to Oracle Internet Directory.

Category:

Security

Cause:

A NamingException occurred while attempting to connect to Oracle Internet Directory.

Action:

Verify that the Oracle Internet Directory is up.

FRM-93302

error running Forms in SSO mode.

Category:

Security

Cause:

The OHS instance front-ending Forms managed server is not configured to run with Webgate.

Action:

Configure OHS with the Webgate access client. Refer to the Forms documentation.

FRM-93304

No resource information found for key {0}.

Category:

Security

Cause:

No resource information was found for the specified key in Oracle Internet Directory. This message might be followed by error message FRM-93330 or FRM-93318.

Action:

If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.

FRM-93306

Encountered {0} while attempting to retrieve database credentials from Oracle Internet Directory.

Category:

Security

Cause:

A UtilException was encountered while attempting to retrieve database credentials from Oracle Internet Directory. This message might be followed by error message FRM-93330, FRM-93316, or FRM-93318.

Action:

If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.

FRM-93308

Unable to get the User Distinguished Name (DN) for the User or the Subscriber

Category:

Security

Cause:

An Exception occurred while attempting to get the User Distinguished Name for the Oracle Access Manager user from Oracle Internet Directory

Action:

Verify that the Oracle Internet Directory is Up.

FRM-93310

Encountered {0} while attempting to decode headers from mod_osso.

Category:

Security

Cause:

An Exception was encountered while attempting to decode headers from mod_osso.

Action:

If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.

FRM-93316

Encountered {0} while attempting to obtain user credentials. Redirecting to Delegated Administration Services.

Category:

Security

Cause:

A NoPermissionException occurred while attempting to obtain credentials. The user will be redirected to Delegated Administration Services.

Action:

If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.

FRM-93318

Encountered {0} while attempting to obtain user credentials. Redirecting to Delegated Administration Services or to the SSO error URL.

Category:

Security

Cause:

A NamingException that is not a NoPermissionException occurred while attempting to obtain user credentials.

Action:

If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.

FRM-93320

unable to obtain application entity credential from Oracle Platform Security Services

Category:

Security

Cause:

The Forms servlet could not retrieve application credential from Oracle Platform Security Services to connect to OID. One of the following was true: \n1. The Forms application did not have privileges to connect to Oracle Platform Security Services. \n2. Oracle Platform Security Services alias and key values were invalid.

Action:

Check whether credentials exist and are valid.

FRM-93322

unable to obtain user credentials; redirecting to Resource Access Descriptor servlet

Category:

Security

Cause:

User credentials were not obtained, and either the symptom was a NoPermissionException, or the ssoDynamicResourceCreate configuration parameter was true.

Action:

No action is required.

FRM-93324

Encountered {0} while attempting to obtain the Delegated Administration Services URL.

Category:

Security

Cause:

A UtilException was encountered while attempting to obtain the Delegated Administration Services URL.

Action:

Verify that Delegated Administration Services is up.

FRM-93326

Delegated Administration Services URL generated: {0}

Category:

Security

Cause:

The Forms application was running in SSO mode, the user did not have proper credentials configured in Oracle Internet Directory, and redirection to Delegated Administration Services was requested. This message provides the URL for Delegated Administration Services.

Action:

No action is required.

FRM-93328

User credentials not obtained; redirecting to the SSO error URL.

Category:

Security

Cause:

User credentials were not obtained. The error was not due to a NoPermissionException. The ssoDynamicResourceCreate configuration parameter was not true. If the ssoErrorURL configuration parameter was not defined, this message will be followed by error message FRM-93140, which will provide details.

Action:

No action is required.

FRM-93330

Fatal authentication error: User does not have proper credentials configured.

Category:

Security

Cause:

The user did not have proper credentials configured in the Identity Store (Oracle Internet Directory or Oracle Platform Security Services), and one of the following was true: \n1. The ssoDynamicResourceCreate configuration parameter was true, or the user did not have the necessary permissions to access Oracle Internet Directory.\n2. The ssoDynamicResourceCreate configuration parameter was not true and the ssoErrorURL configuration parameter was not defined.

Action:

Add the user credentials to the Identity Store (Oracle Internet Directory or Oracle Platform Security Services), if appropriate. Alternatively, define the ssoErrorURL configuration parameter.

FRM-93331

Fatal authentication error: Invalid Single Sign-On User.

Category:

Security

Cause:

There was a failure to obtain the Single Sign-On user information after authentication.

Action:

Re-login using SSO credentials. If the problem persists, contact Oracle Support Services.

FRM-93340

Session requires SSO user authentication.

Category:

Security

Cause:

The session was not SSO-authenticated or had expired.

Action:

No action is required.

FRM-93350

failure in SSO user validation

Category:

Security

Cause:

The Forms Listener Servlet decoded a request's SSO headers, but the values did not match the values from the Forms Servlet. The user was prompted to log in again.

Action:

No action is required.

FRM-93360

This session is in SSO mode.

Category:

Security

Cause:

The ssoMode parameter was specified as true in the base configuration file, and the servlet supported authentication.

Action:

No action is required.

FRM-93362

unable to update password in Oracle Internet Directory

Category:

Security

Cause:

The user did not have proper credentials configured in Oracle Internet Directory to update entries.

Action:

Check with the Oracle Internet Directory administrator to see if the user has permissions to update entries in Oracle Internet Directory.

FRM-93364

Cannot dynamically create resource in Oracle Internet Directory: URL specifies invalid value "{0}" for the config parameter.

Category:

Security

Cause:

The Forms application was running in SSO mode, the user did not have proper credentials configured in Oracle Internet Directory, and SSO dynamic resource creation was enabled. However, dynamic resource creation requires a valid configuration section in the base configuration file, but the user specified a nonexistent configuration section.

Action:

No action is required.

FRM-93365

error running Forms in SSO mode

Category:

Files

Cause:

Forms is not configured to run in SSO mode.

Action:

Configure Forms to run in SSO mode.

FRM-93366

error creating Forms application's Resource Access Descriptor in Oracle Internet Directory.

Category:

Security

Cause:

The Forms application failed to dynamically create a Resource Access Descriptor (RAD) in Oracle Internet Directory.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93367

invalid parameters {0} passed to the Forms Rad Servlet

Category:

Security

Cause:

Invalid parameters were passed to the Forms Rad Servlet.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93368

Forms Rad Servlet is in an invalid state.

Category:

Security

Cause:

Invalid Http session detected in the Forms Rad Servlet. This should never happen.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93369

Direct user access of Forms RadServlet is not allowed.

Category:

Security

Cause:

User tried to access the Forms RadServlet directly.

Action:

No action is required.

FRM-93370

error reading the Resouce Access Descriptor for update

Category:

Security

Cause:

Forms Rad Servlet failed to read the Resouce Access Descriptor to update it due to an internal error.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93371

error closing connection with Oracle Internet Directory

Category:

Security

Cause:

Forms encountered an error closing connection with Oracle Internet Directory.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93380

unexpected error while attempting to redirect to Oracle Access Manager or the Forms Rad servlet

Category:

Security

Cause:

An IOException or ServletException was encountered while attempting to do a sendRedirect or forward to Oracle Access Manager or the Forms Rad servlet.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93382

Oracle Access Manager login processing for an Oracle Forms Standalone application timed out after {0} seconds

Category:

Configuration

Cause:

This message will appear in the terminal window from which the Standalone application was launched. The user did not complete Oracle Access Manager login within the indicated time interval (specified by the ssoSaaBrowserPageTimeout configuration parameter). The time interval is measured from when the page was displayed.

Action:

Increase the time interval specified by ssoSaaBrowserPageTimeout configuration parameter if it is deemed inadequate.

FRM-93383

Resource Access Descriptor processing for an Oracle Forms Standalone application timed out after {0} seconds

Category:

Configuration

Cause:

This message will appear in the terminal window from which the Standalone application was launched. The user did not press Submit or Cancel in the Resource Access Descriptor page within the indicated time interval (specified by the ssoSaaBrowserPageTimeout configuration parameter). The time interval is measured from when the page was displayed.

Action:

Increase the time interval specified by ssoSaaBrowserPageTimeout configuration parameter if it is deemed inadequate.

FRM-93410

unexpected error while prestarting runtime processes

Category:

Process

Cause:

An unchecked Exception or Error was encountered while prestarting runtime processes. The prestarting of runtime processes might not have occurred at all, or it might have been partially completed.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93412

There are {0} prestarted runtime processes in the runtime process pool for configuration section [{1}].

Category:

Process

Cause:

During runtime process pool initialization, the indicated number of runtime processes were prestarted for the indicated configuration section, because the configuration section specified a value of true for the prestartRuntimes parameter. (The number of runtime processes is derived from the prestartInit parameter.)

Action:

No action is required.

FRM-93421

starting the timer for the runtime process pool for configuration section [{0}]

Category:

Process

Cause:

During runtime process pool initialization, a timer task was started for the indicated configuration section, because the configuration section specified a positive value for the prestartTimeOut parameter.

Action:

No action is required.

FRM-93423

adding {0} runtime processes to the runtime process pool for configuration section [{1}] because the pool has gone below the minimum

Category:

Process

Cause:

A prestarted runtime process was removed from the runtime process pool for the indicated configuration section, in order to start a new Forms application. This caused the number of prestarted runtime processes to fall below the value specified by the prestartMin parameter. As a result, the indicated number of prestarted runtime processes (derived from the prestartIncrement parameter) were added to the pool.

Action:

No action is required.

FRM-93424

removing the prestarted runtime processes for configuration section [{0}]

Category:

Process

Cause:

The servlet was being shut down, or the prestarting of runtime processes timed out (as indicated by message FRM-93425). As a result, prestarted processes were removed from the pool.

Action:

No action is required.

FRM-93425

The prestarting of runtime processes for configuration section [{0}] has timed out.

Category:

Process

Cause:

The thread that was filling the runtime process pool for the indicated configuration section timed out, after running for the number of minutes specified by the prestartTimeOut parameter for the indicated configuration section. Any prestarted processes in the pool were subsequently removed.

Action:

Determine why prestarting was taking an unexpectedly long time, or increase the value of the prestartTimeOut parameter.

FRM-93426

The prestarting of runtime processes for configuration section [{0}] is terminated.

Category:

Process

Cause:

A concurrent process removed the indicated configuration section's entry in the PoolManager while its runtime process pool was being filled. Any prestarted processes in the pool were subsequently removed.

Action:

No action is required.

FRM-93430

scheduling prestart event: {0}.

Category:

Process

Cause:

A scheduled prestart timer event was processed, resulting in the prestart of one or more Forms runtime processes.

Action:

No action is required.

FRM-93431

unexpected error while prestarting Forms runtime processes for the pre-start event: {0}

Category:

Process

Cause:

An Exception was encountered while prestarting Forms runtime processes for a scheduled prestart event.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93432

error adding notification listener to the Timer MBean

Category:

Process

Cause:

An Exception was encountered while adding notification listener to the Timer MBean.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93433

schedules restored from prestart archive file

Category:

Process

Cause:

Notifications were added to the prestart Timer MBean from the prestart archive file.

Action:

No action is required

FRM-93434

error restoring schedule {0} from the prestart archive file

Category:

Process

Cause:

An Exception was encountered while restoring a schedule from the prestart archive file.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93435

error restoring schedules from the prestart archive file

Category:

Process

Cause:

An Exception was encountered while restoring the schedules from the prestart archive file.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93436

schedules are written to the prestart archive file

Category:

Process

Cause:

Schedules from the prestart Timer MBean were dumped to the prestart archive file before the Forms application was shutdown.

Action:

No action is required

FRM-93437

error writing schedules to the prestart archive file

Category:

Process

Cause:

An Exception was encountered while writing schedules to the prestart archive file.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93438

error prestarting Forms runtime processes for the event: {0}

Category:

Process

Cause:

The scheduled Forms runtime processes could not be prestarted because of an invalid entry in the notification event from the prestart Timer MBean.

Action:

No action is required.

FRM-93439

scheduled prestart event not processed for configuration section [{0}]

Category:

Process

Cause:

The prestart scheduling event was not processed because the prestartRuntimes parameter is not set in formsweb.cfg.

Action:

Enable the prestartRuntimes parameter in formsweb.cfg.

FRM-93500

unexpected error while attempting to create the runtime process

Category:

Process

Cause:

An unchecked Exception or Error was encountered while attempting to create the runtime process. Typically, a runtime process creation error would cause a more specific message.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93520

Runtime process not created: Maximum permissible number of runtime processes is exceeded.

Category:

Configuration

Cause:

The maxRuntimeProcesses configuration parameter specified a positive decimal number, and there appeared to be that many runtime processes already executing.

Action:

No action is required.

FRM-93530

unable to switch to working directory {0}

Category:

Configuration

Cause:

The specified file did not exist or was not a directory. Note that the name of the working directory is obtained from one of the following: \n1. The workingDirectory parameter in the Forms Servlet configuration file. \n2. The workingDirectory servlet parameter. \n3. <oracle_home>/forms, where <oracle_home> is derived from the ORACLE_HOME parameter in the environment variable configuration file. \n4. <oracle_home>/forms, where <oracle_home> is derived from the ORACLE_HOME environment variable.

Action:

For cases 1 and 2, verify that the workingDirectory parameter specifies the correct directory. For cases 3 and 4, verify that the ORACLE_HOME parameter or environment variable specifies the correct directory. If necessary, create the directory.

FRM-93531

cannot create runtime process: unable to switch to working directory

Category:

Configuration

Cause:

Refer to error message FRM-93530 (which always precedes this message). The FRM-93530 message provides the name of the directory.

Action:

Refer to error message FRM-93530.

FRM-93534

unable to execute startup command {0}

Category:

Process

Cause:

The specified command (which was intended to start the runtime process) threw an Exception. The command was retried with <oracle_home>/bin prefixed, but that too threw an Exception. A stack trace accompanies the following FRM-93535 error message. This error should never occur at a customer site. Note that <oracle_home> is derived from one of the following:\n1. The ORACLE_HOME parameter in the environment variable configuration file.\n2. The ORACLE_HOME environment variable.

Action:

Contact Oracle Support Services.

FRM-93535

cannot create runtime process: unable to execute startup command

Category:

Process

Cause:

Refer to error message FRM-93534 (which always precedes this message). The FRM-93534 error message specifies the command. This error should never occur at a customer site.

Action:

Contact Oracle Support Services.

FRM-93536

cannot create runtime process: unable to create temporary logging file

Category:

Files

Cause:

An IOException occurred while trying to create a temporary logging file to capture the standard output and standard error streams of the newly created runtime process.

Action:

Verify that the Forms Listener Servlet has the necessary permissions and disk space to create a temporary file.

FRM-93543

cannot connect to runtime process: unable to get I/O streams from newly created runtime process

Category:

Process

Cause:

The Forms Listener Servlet encountered an Exception when attempting to obtain a BufferedInputStream for the standard output or standard error streams produced by the newly created runtime process. This error should never occur at a customer site.

Action:

Contact Oracle Support Services.

FRM-93546

external message from runtime process: {0}

Category:

Process

Cause:

The runtime process wrote the specified message to stderr or stdout, but the message does not appear to have been written by the frmweb exeutable. It typically will be an O/S message identifying an error that occurred while attempting to load the executable. In such a case, this message will be followed immediately by FRM-93552.

Action:

Examine the external message. If it identifies a fatal error, correct it, if possible. If the problem persists, contact Oracle Support Services.

FRM-93548

Runtime process ID is {0}.

Category:

Process

Cause:

The newly created runtime process sent its process ID back to the Forms Listener Servlet.

Action:

No action is required.

FRM-93550

cannot connect to runtime process: no response from newly created runtime process

Category:

Process

Cause:

The Forms Listener Servlet waited several times (for a total of roughly 4 minutes) for the initial response from the newly created runtime process, but no response arrived.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93552

cannot connect to runtime process: Newly created runtime process has terminated abnormally.

Category:

Process

Cause:

The Forms Listener Servlet created the runtime process, but the process terminated abnormally. The preceding error message provides more detail.

Action:

Take the action indicated for the preceding error message.

FRM-93553

cannot connect to runtime process: unable to establish a socket connection to newly created runtime process

Category:

Process

Cause:

The Forms Listener Servlet created the runtime process, but was unable to establish a socket connection to the process.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93558

cannot connect to runtime process: error reading data from newly created runtime process

Category:

Process

Cause:

The Forms Listener Servlet encountered an IOException while attempting to receive data from the newly created runtime process.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93566

unexpected error while attempting to stop runtime process

Category:

Process

Cause:

An unchecked Exception or Error was encountered while attempting to stop the runtime process. Processing continued. However, the runtime process might have been left in existence (thereby consuming resources), and messages from the runtime process might not have been written to the Oracle Diagnostic Log.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93572

error reading messages from runtime process

Category:

Files

Cause:

An I/O error occurred while reading the temporary file to which messages from the runtime process were written. Processing continued. However, messages from the runtime process were not written to the Oracle Diagnostic Log.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93574

Application server does not support Oracle character set {0}.

Category:

Configuration

Cause:

The runtime process used the specified Oracle character set when it wrote messages for the Oracle Diagnostic Log, but the application server did not support that character set. Processing continued, using the ISO-8859-1 Java character set. However, some multibyte characters (those in variable arguments) in messages from the runtime process might have been displayed incorrectly in the Oracle Diagnostic Log.

Action:

Verify that the environment variable configuration file specifies the correct value for NLS_LANG (specifically, the correct character set). If the problem persists, contact Oracle Support Services.

FRM-93600

unexpected error while attempting to communicate with the client or the runtime process

Category:

Process

Cause:

An unchecked Exception or Error was encountered while attempting to communicate with the client or the runtime process. Typically, a communication error would cause a more specific message.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93614

invalid or absent Content-Length from runtime process

Category:

Process

Cause:

This message provides more detail for the following FRM-93618 error message.

Action:

Refer to error message FRM-93618.

FRM-93618

fatal error reading data from runtime process

Category:

Process

Cause:

The runtime process was still running, but the Forms Listener Servlet encountered an IOException while attempting to receive data from the process. A preceding message might provide more detail. The accompanying stack trace represents the state of the process when the previous detail message was logged.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93624

internal buffer ({0} bytes) not big enough to hold header ({1} bytes) for message from servlet to runtime process

Category:

Requests/Responses

Cause:

An internal buffer was not big enough to hold the header for a message from the servlet to the runtime process. The FRM-93624 error message provides supplemental detail for the FRM-93628 error message.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93625

internal buffer ({0} bytes) not big enough to generate initial message from servlet to runtime process

Category:

Requests/Responses

Cause:

An internal buffer was not big enough to generate the initial message from the servlet to the runtime process. The FRM-93625 error message provides supplemental detail for the FRM-93628 error message.

Action:

If the problem persists, contact Oracle Support Services.

FRM-93628

fatal error writing data to runtime process

Category:

Process

Cause:

The runtime process was still running, but the Forms Listener Servlet encountered a fatal error while attempting to write data to the process. A preceding FRM-93624 or FRM-93625 error message might provide more detail.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93652

The runtime process has terminated abnormally.

Category:

Process

Cause:

The Forms Listener Servlet attempted to communicate with the runtime process, but the process had terminated prematurely. The preceding error message provides more detail.

Action:

Take the action indicated for the preceding error message.

FRM-93654

Runtime process {0} is terminating due to external action.

Category:

Process

Cause:

The runtime process was running on a UNIX platform, and received a signal 9 (SIGKILL) or 15 (SIGTERM), or the runtime process was running on a Windows platform, and exited with exit code 1. Presumably the runtime process was terminated explicitly, either via the Enterprise Manager, or via a 'kill' command (UNIX) or the task manager (Windows). As a result, the runtime process terminated abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message.

Action:

No action is required.

FRM-93656

Runtime process {0} is terminating due to signal {1}.

Category:

Process

Cause:

The runtime process was running on a UNIX platform, and received a signal other than 9 (SIGKILL) or 15 (SIGTERM). The signal caused the runtime process to terminate abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message. If the FORMS_CATCHTERM environment variable was not set to a value that is equivalent to FALSE, there will typically be a stack trace. If the FORMS_C_STACK_TRACE_TO_FILE environment variable was set to a value that is equivalent to FALSE, the stack trace will accompany this message; otherwise, the stack trace will appear in a file named frmweb_dump_<pid> in the Forms trace directory, where <pid> is the process ID. If the FORMS_CATCHTERM environment variable was set to a value that is equivalent to FALSE, there may be a core file that contains a stack trace.

Action:

Examine the stack trace for the runtime process. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93657

Runtime process {0} is terminating due to exception {1}.

Category:

Process

Cause:

The runtime process was running on a Windows platform, and encountered an exception (which is displayed as 8 hexadecimal digits in the error message, in some cases followed by a descriptive phrase). The exception caused the runtime process to terminate abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message. If the FORMS_CATCHTERM environment variable was not set to a value that is equivalent to FALSE, there will typically be a stack trace. If the FORMS_C_STACK_TRACE_TO_FILE environment variable was set to a value that is equivalent to FALSE, the stack trace will accompany this message; otherwise, the stack trace will appear in a file named frmweb_dump_<pid> in the Forms trace directory, where <pid> is the process ID.

Action:

Examine the stack trace for the runtime process. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93658

Stack trace for runtime process {0} is being written to file {1}.

Category:

Process

Cause:

The runtime process encountered a signal or an exception (identified by the preceding "FRM-93656" or "FRM-93657" message), and the FORMS_C_STACK_TRACE_TO_FILE environment variable was not set to a value that is equivalent to FALSE.

Action:

No action is required.

FRM-93659

Stack trace for runtime process {0} cannot be written to file {1}.

Category:

Process

Cause:

The runtime process encountered a signal or an exception (identified by the preceding "FRM-93656" or "FRM-93657" message), and the FORMS_C_STACK_TRACE_TO_FILE environment variable was not set to a value that is equivalent to FALSE. However, the stack trace file could not be created.

Action:

Ensure that the FORMS_TRACE_DIR environment variable (if set) and the ORACLE_INSTANCE environment variable each specify a valid directory with write permissions and adequate space.

FRM-93660

unable to get the hostname, using localhost instead of hostname in the Forms DMS table

Category:

Process

Cause:

The runtime process was unable to read the hostname from the server.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93661

error writing JVM Controller pid file

Category:

Process

Cause:

The runtime process was unable to write the JVM Controller pid file to the disk.

Action:

Ensure that ORACLE_INSTANCE/FRComponent/frcommon/tools/jvm/proc directory exists, the user running Weblogic server has write permissions to write to it and there is adequate disk space.

FRM-93662

error initializing OPMN metrics collection

Category:

Process

Cause:

The runtime process was unable to initialize OPMN metrics collection.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93700

Request duration is {0} seconds. Request size is {1} bytes; response size is {2} bytes.

Category:

Performance

Cause:

Performance monitoring at the request level was requested.

Action:

No action is required.

FRM-93710

Total duration of network exchanges is {0}. Total number of network exchanges is {1} ({2} long ones over {3} sec). Average time for one network exchange (excluding long ones) is {4}. Total number of bytes sent is {5}. Total number of bytes received is {6}.

Category:

Performance

Cause:

Performance monitoring at the session level was requested.

Action:

No action is required.

FRM-93840

Proctest: Warning: nProcs configuration parameter is nonnumeric - using 1.

Category:

Configuration

Cause:

A nonnumeric value was specifed for the nProcs parameter in the base configuration file. The value will default to 1.

Action:

Correct the nProcs configuration parameter.

FRM-93841

Proctest: Process test starting with {0} processes.

Category:

Process

Cause:

The Proctest command started.

Action:

No action is required.

FRM-93842

Proctest: Creating process {0}.

Category:

Process

Cause:

The Proctest command started creating a runtime process.

Action:

No action is required.

FRM-93843

Proctest: Failure to create process {0} - aborting test.

Category:

Process

Cause:

An Exception occurred while attempting to create a runtime process. The preceding error message identifies the problem, and includes a stack trace.

Action:

Refer to the preceding error message.

FRM-93844

Proctest: Connecting to process {0}.

Category:

Process

Cause:

The Proctest command started connecting to a newly created runtime process.

Action:

No action is required.

FRM-93845

Proctest: Failure to connect to process {0} - aborting test.

Category:

Process

Cause:

An Exception occurred while attempting to connect to a newly created runtime process. The preceding error message identifies the problem, and includes a stack trace.

Action:

Refer to the preceding error message.

FRM-93846

Proctest: unexpected error in process test

Category:

Process

Cause:

This message precedes error message FRM-93843 or FRM-93845 if the problem was an Error or an unchecked Exception that was not caught by Forms code. A stack trace is included.

Action:

Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.

FRM-93847

Proctest: Number of processes started and connected to is {0}.

Category:

Process

Cause:

The Proctest command created the requested number of runtime processes, and successfully connected to them.

Action:

No action is required.

FRM-93848

Proctest: Stopping the {0} runtime processes.

Category:

Process

Cause:

The Proctest command reached the point in its processing where it was about to stop the runtime processes that it had previously created.

Action:

No action is required.

FRM-93849

Proctest: Process test complete.

Category:

Process

Cause:

The Proctest command completed.

Action:

No action is required.

FRM-93893

Trace: Xlate encountered an IO error

Category:

Files

Cause:

The Xlate utility encountered an IOException.

Action:

Examine the stack trace.

FRM-94170

File {0} is missing from the current directory, looking in {1}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94171

File is missing from {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94172

Environment variable configuration file is {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94173

Value of serverArgs generated from configuration file and URL is "{0}".

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94178

Enterprise Manager configuration details: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94200

FormsServlet receiving {0} request. Details: {1}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94201

ListenerServlet receiving {0} request. Details: {1}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94202

HTTP request headers: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94212

Unable to get the Sequence Number from Pragma Header (Mac Client). Obtaining the seqNumber from the Accept header instead.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94213

forwarding 0 length request to runtime in response to request to close Forms session

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94231

starting new servlet session with ID {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94232

FormsServlet: encodeURL() has no effect.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94233

Server URL is rewritten. Details:{0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94241

ListenerServlet: encodeURL() has no effect.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94253

servlet session with ID {0} is invalidated.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94254

HTTP session ID changed to {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94282

Existing servlet session, ID = {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94283

No current servlet session.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94284

Requested session ID = {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94285

Requested session ID is from cookie.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94286

Requested session ID is not from cookie.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94287

Requested session ID is valid.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94288

Requested session ID is invalid.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94289

Session was not created by Oracle Forms.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94302

Encountering {0} while attempting to proxy the Oracle Internet Directory connection to the SSO user.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94332

Starting session in SSO mode. Details: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94334

User name from Oracle Internet Directory: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94398

SAA: Javascript sent to launched browser: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94430

Trying to get a prestarted process.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94431

Prestarted process is available and selected.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94432

Prestarted process is not available.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94433

prestart archive file does not exist

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94522

Creating new runtime process using default executable.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94523

Creating new runtime process using executable "{0}".

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94532

RunformProcess.startProcess(): executing {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94533

RunformProcess.startProcess(): execution failure, trying again using {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94538

successful creation of new runtime process

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94542

Getting stderr of child process.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94547

port number from message: {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94554

successful connection to runtime process after {0} attempts

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94556

successful connection to runtime process at port {0}

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94562

RunformSession.valueUnbound(): stopping runtime process.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-94610

Read timeout. Sending Response Pending with retry time = {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-96910

runtime process: OS page size is {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-96911

runtime process: preferred file system block size for temporary record buffer file is {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-96912

runtime process: page size for temporary record buffer file is {0}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-96913

runtime process: record manager record segment size for block {0}.{1} is {2}, adjusted to {3}.

Category:

Other

Cause:

This message is intended primarily for Oracle Support Services.

Action:

No action is required.

FRM-99999

Error {0}: See the release notes file (relnotes) for information about this error.

Category:

Configuration

Cause:

See the release notes.

Action:

Take action as documented in the release notes.