19 FRM-41838 to FRM-99999

FRM-41838: runtime process: unable to open temporary record buffer file

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Files

FRM-60000: fatal error configuring Forms component

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60001: fatal error removing Forms component

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60002: error reading Forms component registration document {0}

Cause: An error occurred while reading the Forms component registration document.

Action: Do one of the following: 1. Make sure that the registration document is valid. 2. If the registration document is accidentally deleted or modified then reinstall ORACLE_HOME.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60003: error reading ORACLE_HOME registry file {0}

Cause: An error occurred while reading the ORACLE_HOME registry file.

Action: Do one of the following: 1. Make sure that the ORACLE_HOME registry file exists. 2. If ORACLE_HOME registry file is accidentally deleted or modified then reinstall ORACLE_HOME.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60004: error obtaining text contents of the configuration file {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60005: Directory {0} exists; renaming it to {1}

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

Action: No action is required.

Level: 1

Type: WARNING

Impact: Configuration

FRM-60006: error obtaining the managed server URL

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60007: error creating Windows shortcuts

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60008: error creating Forms instance {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60009: error updating Forms instance {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60010: error deleting Forms instance {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60011: error creating non-managed instance 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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60101: error registering Forms J2EE application MBeans during the application startup

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60102: error deregistering Forms J2EE application MBeans during the application shutdown

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60104: error reading the Forms System component instance

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

Action: Do one of the following:1. 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.2. 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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60114: error reading default configuration path

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60201: error initializing identity store

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: WARNING

Impact: Configuration

FRM-60203: error associating Forms application with Oracle Internet Directory host {0}

Cause: The Forms application footprint in Oracle Internet Directory failed to be created due to one of the following causes: 1. Oracle Internet Directory was not accessible. 2. The Forms J2EE application footprint password failed to be seeded in Oracle Platform Security Services on the mid-tier. 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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60205: error disassociating Forms application with Oracle Internet Directory host {0}

Cause: Failed to remove the Forms J2EE application footprint from Oracle Internet Directory due to one of the following causes: 1. Oracle Internet Directory was not accessible. 2. An error status was returned while deregistering the Forms J2EE application footprint with Oracle Internet Directory. 3. Failed to fetch the Forms J2EE application footprint password from Oracle Platform Security Services on the mid-tier. 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: 1. Examine the stack trace which accompanies this message, look for status of the IM tier and resolve the issue. 2. If using Fusion Middleware Control, make sure that information passed to deregister the Forms J2EE application with Oracle Internet Directory host is valid. 3. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60207: error storing credentials to Oracle Platform Security Services

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60208: error deleting credentials from Oracle Platform Security Services

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60209: error obtaining credentials from Oracle Platform Security Services

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60210: error obtaining MBean Server connection

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60211: error migrating Resource Access Descriptor

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60212: Resource Access Descriptor migration process interrupted

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60213: error recording the Resource Access Descriptor migration result

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60214: Forms Resource Access Descriptor migration thread awaken

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60215: error reading the Resource Access Descriptor migration results

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60216: error starting Forms Resource access migration to Oracle Platform Security Services

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60217: invalid Single Sign-on user

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60218: error connecting to LDAP server

Cause: An error occurred while connecting the LDAP server due to one of the following causes: 1. Invalid connection credentials were entered. 2. Invalid hostname, port information was entered.3. LDAP server is down.

Action: Examine the cause, and take the appropriate remedial action.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60220: error initializing the Forms Identity store

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60221: error obtaining the Forms identity store access

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60250: error creating Resource Access Descriptor for Forms application {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60251: error updating Resource Access Descriptor for Forms application {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60252: error deleting Resource Access Descriptor for Forms application {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60253: error reading Resource Access Descriptor for Forms application {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60254: error obtaining Resource Access Descriptor

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60255: error stashing Single Single-on user information in the Forms session

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60256: permission error reading the Resource Access Descriptor from Oracle Internet Directory

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

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

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

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60258: error reading Forms application Resource Access Descriptor from Oracle Internet Directory

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60301: invalid character in the file name argument {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60302: error duplicating the configuration file {0} to {1}

Cause: An error occurred duplicating the configuration file due to one of the following causes: 1. MBean registration failed. 2. 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.

Level: 1

Type: ERROR

Impact: Configuration

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

Cause: Invalid document type argument passed to operation.

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

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60305: error deleting the configuration file {0}

Cause: An error occurred deleting the configuration file due to one of the following causes: 1. MBean deregistration failed. 2. 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.

Level: 1

Type: ERROR

Impact: Configuration

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

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).

Level: 1

Type: ERROR

Impact: Configuration

FRM-60307: error converting the configuration object to the relevant CompositeType

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60308: error converting the configuration object to the relevant CompositeData

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60309: error registering child config MBean for the application section {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60310: error deregistering child config MBean for the application section {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60311: error deleting application section {0}

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

Action: Choose the correct section name.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60312: error creating application section {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-60313: error duplicating application section {0} to {1}

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

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

Level: 1

Type: ERROR

Impact: Configuration

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

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91109: internal error in runtime process: application startup failure

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91111: internal error in runtime process: window system startup failure

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91112: internal error in runtime process: resource manager startup failure

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91116: internal error in runtime process: Oracle*Image startup failure

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91119: internal error in runtime process: Oracle*VGS startup failure

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

Cause: An invalid value was specified for the environment variable FORMS_DECIMAL_PREFIX.

Action: Do one of the following: 1. 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. 2. Specify FORMS_DECIMAL_PREFIX as '' (the empty string).

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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

Action: Correct the environment variable value.

Level: 1

Type: WARNING

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-91134: fatal error in runtime process: NLS_LANG specifies unsupported character set

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.

Level: 1

Type: ERROR

Impact: Configuration

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

Cause: The specified message file was not found.

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

Level: 1

Type: ERROR

Impact: Configuration

FRM-91137: runtime process: unable to open log file {0}

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91144: internal error in runtime process: unable to parse user name

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91145: fatal error in runtime process: missing serverArgs parameter

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.]

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91151: internal error in runtime process: unable to initialize Oracle NLS

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91157: internal error in runtime process: unable to redirect stderr to stdout

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91170: runtime process: JVM exiting with code {0}

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-91171: runtime process: JVM aborting

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.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: WARNING

Impact: Files

FRM-91190: fatal error in runtime process: unable to allocate {0} bytes of 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.

Level: 1

Type: ERROR

Impact: Memory

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

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.

Level: 1

Type: ERROR

Impact: Memory

FRM-91192: fatal error in runtime process: unable to memory-map {0} bytes of 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.

Level: 1

Type: ERROR

Impact: Memory

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

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.

Level: 1

Type: ERROR

Impact: Memory

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

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.

Level: 1

Type: ERROR

Impact: Memory

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

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.

Level: 1

Type: ERROR

Impact: Files

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

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.

Level: 1

Type: ERROR

Impact: Memory

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

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.

Level: 1

Type: ERROR

Impact: Memory

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

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91200: fatal error in runtime process: error reading HTTP header

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.

Level: 1

Type: ERROR

Impact: Network

FRM-91210: fatal error in runtime process: error reading HTTP data

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.

Level: 1

Type: ERROR

Impact: Network

FRM-91220: fatal error in runtime process: error writing HTTP data

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.

Level: 1

Type: ERROR

Impact: Network

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

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.

Level: 1

Type: ERROR

Impact: Network

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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. 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: WARNING

Impact: Process

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

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. 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.

Level: 1

Type: ERROR

Impact: Process

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

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. 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.

Level: 1

Type: ERROR

Impact: Process

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

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. 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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. 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: WARNING

Impact: Process

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

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.

Level: 1

Type: WARNING

Impact: Process

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

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91293: internal error in runtime process: invalid initial message from servlet

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.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-91930: message from Forms application: {0}

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

Action: Respond as directed by the application developer.

Level: 32

Type: TRACE

Impact: Other

FRM-91934: message from Forms application: {0}

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

Action: Respond as directed by the application developer.

Level: 1

Type: NOTIFICATION

Impact: Other

FRM-91935: message from Forms application: {0}

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

Action: Respond as directed by the application developer.

Level: 1

Type: WARNING

Impact: Other

FRM-91936: message from Forms application: {0}

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

Action: Respond as directed by the application developer.

Level: 1

Type: ERROR

Impact: Other

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

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.

Level: 1

Type: TRACE

Impact: Performance

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

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').

Level: 1

Type: TRACE

Impact: Performance

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

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.

Level: 1

Type: TRACE

Impact: Performance

FRM-91994: runtime process: 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.

Cause: At the point in time when total memory 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.]

Level: 1

Type: TRACE

Impact: Performance

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

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.

Level: 1

Type: TRACE

Impact: Performance

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

Cause: The Forms Servlet was being initialized.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93110: No Forms Servlet configuration file is specified.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93111: Cannot find Forms Servlet configuration file {0}.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93112: error reading Forms Servlet configuration file {0}

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.

Level: 1

Type: ERROR

Impact: Files

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

Cause: The specified configuration file contained an invalid section name.

Action: Provide a valid section name.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93114: Forms Servlet configuration file {0} contains invalid data.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93121: Cannot find environment variable configuration file {0}.

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. 1. The envFile configuration parameter for this application specified a nonexistent file. A preceding FRM-93141 error message provides details. 2. The envFile configuration parameter for this application specified a file that existed when the Forms Servlet extracted the parameter, but the file subsequently disappeared. 3. 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. 1. Take action indicated for the preceding FRM-93141 error message. 2. Re-create the file, or correct the envFile configuration parameter. 3. Verify that the envFile servlet parameter specifies the correct value. Create the file if necessary.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93122: error reading environment variable configuration file {0}

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.

Level: 1

Type: ERROR

Impact: Files

FRM-93124: Environment variable configuration file {0} contains invalid data.

Cause: The specified configuration file contained an invalid section name.

Action: Provide a valid section name.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93130: No base HTML file is specified.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93131: Cannot find base HTML file {0}.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93132: error reading base HTML or JNLP file {0}

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.

Level: 1

Type: ERROR

Impact: Files

FRM-93134: No base JNLP file is specified.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93135: Cannot find base JNLP file {0}.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93136: no base TXT file specified for Oracle Forms Standalone Application

Cause: The baseSAAfile configuration parameter was not specified.

Action: Specify the baseSAAfile configuration parameter.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93137: Oracle Forms Standalone Application session not allowed when ssoMode enabled

Cause: The configuration parameter ssoMode was enabled for an Oracle Forms Standalone Application request.

Action: Disable ssoMode, or use a browser to launch Oracle Forms.

Level: 1

Type: ERROR

Impact: Configuration

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

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.)

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.)

Level: 1

Type: ERROR

Impact: Configuration

FRM-93143: Oracle Forms Standalone Launcher checksum failed.

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93144: error while generating checksum of Oracle Forms Standalone Launcher file

Cause: An I/O error occurred while generating the checksum.

Action: Check if Oracle Forms Standalone Launcher file exists.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93145: Oracle Forms Standalone Launcher version parameter is missing.

Cause: The request received from Oracle Forms Standalone Launcher does not contain Oracle Forms Standalone Launcher version information.

Action: Get the latest Oracle Forms Standalone Launcher file.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93146: Oracle Forms Standalone Launcher version {0} does not match server version {1}.

Cause: Oracle Forms Standalone Launcher jar is outdated.

Action: Get the latest Oracle Forms Standalone Launcher file.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93154: The Forms Servlet is not allowing new connections.

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

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

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. 1. Determine why the server is unavailable, and correct the condition. 2. Specify a value for the MetricsServerErrorURL parameter in the Forms Servlet configuration file.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93160: unexpected error while obtaining the JVM pid

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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93180: Initializing ListenerServlet. Initialization parameters are: {0}

Cause: The Forms Listener Servlet was being initialized.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

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

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.

Level: 1

Type: WARNING

Impact: Configuration

FRM-93197: unexpected error while obtaining the application name from JRF

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93198: unexpected error while obtaining the cluster name from JRF

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.

Level: 1

Type: ERROR

Impact: Configuration

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

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.

Level: 1

Type: WARNING

Impact: Configuration

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

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93218: fatal error reading client request content

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93228: fatal error writing response to client

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93240: Multiple Forms applications cannot share an HTTP 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:1. 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.2. An application attempted to launch multiple Forms applications, and cookies were enabled in the Forms application.3. 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.1. No action is required.2. Disable cookies in the Forms application.3. 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.

Level: 1

Type: NOTIFICATION

Impact: Session

FRM-93242: serverURL applet parameter refers to an HTTP session that no longer exists.

Cause: The serverURL applet parameter specified an encoding (e.g. jsessionid) for a non-existant HTTP session. This probably resulted from the user double-clicking on a downloaded JNLP file that was created for Java Web Start with SSO enabled.

Action: No action is required.

Level: 1

Type: ERROR

Impact: Session

FRM-93243: Static HTML is not allowed.

Cause: The serverURL applet parameter did not specify an ifcfs parameter and did not specify an encoding (e.g. jsessionid) for an HTTP session. The request for this URL was sent directly to the Forms Listener Servlet, but no HTTP session was associated with the request. This indicates that the HTML that defines the applet is "static", i.e. that it was not generated by the Forms Servlet. Static HTML is not allowed unless the envFile servlet initialization parameter for lservlet is set to a non-blank value.

Action: If you wish to allow static HTML, set the envFile servlet initialization parameter for lservlet to a non-blank value. This parameter specifies the full path of a file that defines values for environment variables (e.g. default.env). If you don't need such a file for static HTML (e.g. because all necessary environment variables are set in the Windows registry or in the script that launches webLogic), then set the envFile servlet initialization parameter for lservlet to ".".

Level: 1

Type: ERROR

Impact: Session

FRM-93244: URL could not be rewritten for a Java Web Start application or an Oracle Forms Standalone application.

Cause: Oracle Forms was attempting to run a Java Web Start application or an Oracle Forms Standalone application. Either URL rewriting was disabled (url-rewriting-enabled set to false in weblogic.xml), or else SSO was enabled (for Java Web Start: SSO is not allowed for Oracle Forms Standalone applications) and cookies were enabled (cookies-enabled not set or set to true in weblogic.xml). The application was terminated.

Action: If you wish to support Java Web Start or Oracle Forms Standalone applications when SSO is not enabled, ensure that url-rewriting-enabled is not set or is set to true in weblogic.xml. If, in addition, you wish to support Java Web Start applications when SSO is enabled, then also ensure that cookies-enabled is set to false weblogic.xml.

Level: 1

Type: ERROR

Impact: Session

FRM-93250: Forms session started.

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.

Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93251: Runtime session started for client {0} (IP address {1}).

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.

Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93252: Forms session ended.

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.

Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93301: Fatal authentication error: Unable to connect to Oracle Internet Directory.

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

Action: Verify that the Oracle Internet Directory is up.

Level: 1

Type: ERROR

Impact: Security

FRM-93302: error running Forms in SSO mode.

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.

Level: 1

Type: ERROR

Impact: Security

FRM-93304: No resource information found for key {0}.

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.

Level: 1

Type: WARNING

Impact: Security

FRM-93306: Encountered {0} while attempting to retrieve database credentials from Oracle Internet Directory.

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.

Level: 1

Type: WARNING

Impact: Security

FRM-93308: Unable to get the User Distinguished Name (DN) for the User or the Subscriber

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.

Level: 1

Type: ERROR

Impact: Security

FRM-93310: Encountered {0} while attempting to decode headers from mod_osso.

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.

Level: 1

Type: WARNING

Impact: Security

FRM-93316: Encountered {0} while attempting to obtain user credentials. Redirecting to Delegated Administration Services.

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.

Level: 1

Type: WARNING

Impact: Security

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

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.

Level: 1

Type: WARNING

Impact: Security

FRM-93320: unable to obtain application entity credential from Oracle Platform Security Services

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

Action: Check whether credentials exist and are valid.

Level: 1

Type: ERROR

Impact: Security

FRM-93322: unable to obtain user credentials; redirecting to Delegated Administration Services

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.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93324: Encountered {0} while attempting to obtain the Delegated Administration Services URL.

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

Action: Verify that Delegated Administration Services is up.

Level: 1

Type: ERROR

Impact: Security

FRM-93326: Delegated Administration Services URL generated: {0}

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.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93328: User credentials not obtained; redirecting to the SSO error URL.

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.

Level: 1

Type: NOTIFICATION

Impact: Security

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

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: 1. The ssoDynamicResourceCreate configuration parameter was true, or the user did not have the necessary permissions to access Oracle Internet Directory. The Delegated Administration Services URL could not be generated. The preceding FRM-93324 error message provides more detail. 2. The ssoDynamicResourceCreate configuration parameter was not true and the ssoErrorURL configuration parameter was not defined. The preceding FRM-93140 error message provides more detail.

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. Alternatively, ensure that the Delegated Administration Services URL can be generated.

Level: 1

Type: ERROR

Impact: Security

FRM-93331: Fatal authentication error: Invalid Single Sign-On User.

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.

Level: 1

Type: ERROR

Impact: Security

FRM-93340: Session requires SSO user authentication.

Cause: The session was not SSO-authenticated or had expired.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93350: failure in SSO user validation

Cause: The 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.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93360: This session is in SSO mode.

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

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93362: unable to update password in Oracle Internet Directory

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.

Level: 1

Type: ERROR

Impact: Security

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

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.

Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93365: error running Forms in SSO mode

Cause: Forms is not configured to run in SSO mode.

Action: Configure Forms to run in SSO mode.

Level: 1

Type: ERROR

Impact: Files

FRM-93366: error creating Forms application's Resource Access Descriptor in Oracle Internet Directory.

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.

Level: 1

Type: ERROR

Impact: Security

FRM-93367: invalid parameters {0} passed to the Forms Rad Servlet

Cause: Invalid parameters were passed to the Forms Rad Servlet.

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

FRM-93368: Forms Rad Servlet is in an invalid state.

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

Action: If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Security

FRM-93369: Direct user access of Forms RadServlet is not allowed.

Cause: User tried to access the Forms RadServlet directly.

Action: No action is required.

Level: 1

Type: ERROR

Impact: Security

FRM-93370: error reading the Resouce Access Descriptor for update

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.

Level: 1

Type: ERROR

Impact: Security

FRM-93371: error closing connection with Oracle Internet Directory

Cause: Forms encountered an eorror 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.

Level: 1

Type: ERROR

Impact: Security

FRM-93410: unexpected error while prestarting runtime processes

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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93421: starting the timer for the runtime process pool for configuration section [{0}]

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.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93424: removing the prestarted runtime processes for configuration section [{0}]

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.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93430: scheduling prestart event: {0}.

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

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93432: error adding notification listener to the Timer MBean

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93433: schedules restored from prestart archive file

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

Action: No action is required

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93434: error restoring schedule {0} from the prestart archive file

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93435: error restoring schedules from the prestart archive file

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93436: schedules are written to the prestart archive file

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

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93437: error writing schedules to the prestart archive file

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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93439: scheduled prestart event not processed for configuration section [{0}]

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93500: unexpected error while attempting to create the runtime 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93530: unable to switch to working directory {0}

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: 1. The workingDirectory parameter in the Forms Servlet configuration file. 2. The workingDirectory servlet parameter. 3. <oracle_home>/forms, where <oracle_home> is derived from the ORACLE_HOME parameter in the environment variable configuration file. 4. <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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93531: cannot create runtime process: unable to switch to working directory

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.

Level: 1

Type: ERROR

Impact: Configuration

FRM-93534: unable to execute startup command {0}

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:1. The ORACLE_HOME parameter in the environment variable configuration file.2. The ORACLE_HOME environment variable.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Process

FRM-93535: cannot create runtime process: unable to execute startup command

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93536: cannot create runtime process: unable to create temporary logging file

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.

Level: 1

Type: ERROR

Impact: Files

FRM-93543: cannot connect to runtime process: unable to get I/O streams from newly created runtime 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.

Level: 1

Type: ERROR

Impact: Process

FRM-93546: external message from runtime process: {0}

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93548: Runtime process ID is {0}.

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

Action: No action is required.

Level: 16

Type: NOTIFICATION

Impact: Process

FRM-93550: cannot connect to runtime process: no response from newly created runtime 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93553: cannot connect to runtime process: unable to establish a socket connection to newly created runtime 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.

Level: 1

Type: ERROR

Impact: Process

FRM-93558: cannot connect to runtime process: error reading data from newly created runtime 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.

Level: 1

Type: ERROR

Impact: Process

FRM-93566: unexpected error while attempting to stop runtime 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.

Level: 1

Type: WARNING

Impact: Process

FRM-93572: error reading messages from runtime process

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.

Level: 1

Type: WARNING

Impact: Files

FRM-93574: Application server does not support Oracle character set {0}.

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.

Level: 1

Type: WARNING

Impact: Configuration

FRM-93600: unexpected error while attempting to communicate with the client or the runtime 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.

Level: 1

Type: ERROR

Impact: Process

FRM-93614: invalid or absent Content-Length from runtime process

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

Action: Refer to error message FRM-93618.

Level: 1

Type: ERROR

Impact: Process

FRM-93618: fatal error reading data from runtime 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.

Level: 1

Type: ERROR

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

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.

Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93628: fatal error writing data to runtime 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.

Level: 1

Type: ERROR

Impact: Process

FRM-93652: The runtime process has terminated abnormally.

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93654: Runtime process {0} is terminating due to external action.

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93656: Runtime process {0} is terminating due to signal {1}.

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93657: Runtime process {0} is terminating due to exception {1}.

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93658: Stack trace for runtime process {0} is being written to file {1}.

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93659: Stack trace for runtime process {0} cannot be written to file {1}.

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.

Level: 1

Type: WARNING

Impact: Process

FRM-93660: unable to get the hostname, using localhost instead of hostname in the Forms DMS table

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93661: error writing JVM Controller pid file

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93700: Request duration is {0} seconds. Request size is {1} bytes; response size is {2} bytes.

Cause: Performance monitoring at the request level was requested.

Action: No action is required.

Level: 16

Type: TRACE

Impact: Performance

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}.

Cause: Performance monitoring at the session level was requested.

Action: No action is required.

Level: 1

Type: TRACE

Impact: Performance

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

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.

Level: 1

Type: WARNING

Impact: Configuration

FRM-93841: Proctest: Process test starting with {0} processes.

Cause: The Proctest command started.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93842: Proctest: Creating process {0}.

Cause: The Proctest command started creating a runtime process.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93844: Proctest: Connecting to process {0}.

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

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

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

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.

Level: 1

Type: ERROR

Impact: Process

FRM-93846: Proctest: unexpected error in process test

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.

Level: 1

Type: ERROR

Impact: Process

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

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

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93848: Proctest: Stopping the {0} runtime processes.

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.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93849: Proctest: Process test complete.

Cause: The Proctest command completed.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

FRM-94170: File {0} is missing from the current directory, looking in {1}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94171: File is missing from {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94172: Environment variable configuration file is {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94173: Value of serverArgs generated from configuration file and URL is "{0}".

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94178: Enterprise Manager configuration details: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94200: FormsServlet receiving {0} request. Details: {1}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94201: ListenerServlet receiving {0} request. Details: {1}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94202: HTTP request headers: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94213: forwarding 0 length request to runtime in response to request to close Forms session

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94231: starting new servlet session

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94232: FormsServlet: encodeUrl() has no effect.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94233: Server URL is rewritten. Details:{0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94241: ListenerServlet: encodeUrl() has no effect.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94253: Servlet session is invalidated.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94281: No current servlet session ID.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94282: Existing servlet session, ID = {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94283: No current servlet session.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94284: requesting a servlet session with invalid session ID = {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94285: Session ID is from cookie.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94286: Session ID is not from cookie.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94332: Starting session in SSO mode. Details: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94334: User name from Oracle Internet Directory: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94430: Trying to get a prestarted process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94431: Prestarted process is available and selected.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94432: Prestarted process is not available.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94433: prestart archive file does not exist

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94522: Creating new runtime process using default executable.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94523: Creating new runtime process using executable "{0}".

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94532: RunformProcess.startProcess(): executing {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94538: successful creation of new runtime process

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94542: Getting stderr of child process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94547: port number from message: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94554: successful connection to runtime process after {0} attempts

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94556: successful connection to runtime process at port {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94562: RunformSession.valueUnbound(): stopping runtime process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-94610: Read timeout. Sending Response Pending with retry time = {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

FRM-96910: runtime process: OS page size is {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Other

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

Cause: See the release notes.

Action: Take action as documented in the release notes.

Level: 1

Type: ERROR

Impact: Configuration