Error Messages

This chapter gives you general information and helpful tips about error messages.

FRM-10200: Illegal function in this context.

Cause: You pressed a key that is not valid in this context.

Action: Press [Show Keys] to view a list of valid function keys.

Level: 25

Trigger: None

FRM-10201: No parameters needed.

Cause: You pressed [Enter Application Parameters] or [Enter Menu Parameters], but none are required in this context.

Action: No action required.

Level: 25

Trigger: None

FRM-10202: Menus are nested too deeply.

Cause: You tried to select an item that would nest menus more than 10 deep.

Action: Press [Main Menu] to return to the main menu, then navigate to the menu of your choice.

Level: 25

Trigger: None

FRM-10203: Selected item is not in this menu.

Cause: In a full-screen menu, you entered a number that exceeds the maximum number of menu items.

Action: Choose an item that is on this menu.

Level: 25

Trigger: None

FRM-10204: No command defined for the selected background item.

Cause: You pressed [Background Menu n], where n was greater than the maximum number on the background menu.

Action: No action required. Press [Show Background Menu] to see the valid background menu items.

Level: 25

Trigger: None

FRM-10205: Menu %s not found.

Cause: In the choice field of a full-screen menu, you entered a menu name that does not exist in this application or is not found in the library.

Action: No action is required if the menu does not exist in the application. If it does, recompile the library.

Level: 25

Trigger: None

FRM-10206: memory allocation failure

Cause: A memory allocation failed when Forms Runtime attempted a menu operation.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 25

Trigger: None

FRM-10207: No background menu present.

Cause: You pressed [Show Background Menu], but no background menu exists.

Action: No action required.

Level: 25

Trigger: None

FRM-10208: Parameter %s not found.

Cause: A menu item referenced an undefined parameter.

Action: Contact your DBA.

Level: 25

Trigger: None

FRM-10209: No next menu from background in this context.

Cause: The application attempted to navigate to a named menu from the background menu.

Action: No action required.

Level: 25

Trigger: None

FRM-10210: Response required.

Cause: You did not enter a required parameter, or you left the choice field blank in a full-screen menu.

Action: Make an entry.

Level: 25

Trigger: None

FRM-10211: Field must be filled completely.

Cause: You partially entered a parameter that must be entered completely.

Action: Enter enough data to completely fill the field.

Level: 25

Trigger: None

FRM-10212: Login failed for this username and password.

Cause: You specified an illegal username and password.

Action: Check the username and password and try again.

Level: 25

Trigger: None

FRM-10213: Login procedure terminated.

Cause: You failed to logon to ORACLE three times in a row.

Action: No action required. If you are a valid user, check your user name and password.

Level: 25

Trigger: None

FRM-10214: No authorization to run any application.

Cause: You are not a valid user of any module in Oracle Forms.

Action: No action required. If you think that you should be a valid user, ask your DBA to grant you access to the module you wish to run.

Level: 25

Trigger: None

FRM-10215: No help available.

Cause: You pressed [Help], but none is available for this item.

Action: No action required.

Level: 25

Trigger: None

FRM-10216: Failed to spawn a command to the operating system.

Cause: The operating system could not spawn a sub-process.

Action: Refer to the error message that the operating system issued.

Level: 25

Trigger: None

FRM-10217: No authorization for any item in selected menu.

Cause: You tried to move to a menu that has no items you can access.

Action: Check the menu name you entered and try again.

Level: 25

Trigger: None

FRM-10218: Error for menu %s.

Cause: Oracle Forms could not read the library information for this menu, or an invalid menu name was specified.

Action: Recompile the library or correct the menu name.

Level: 25

Trigger: None

FRM-10219: Item number is invalid.

Cause: In a full-screen menu, you entered an invalid number in the choice field.

Action: Check the item number and re-enter it.

Level: 25

Trigger: None

FRM-10220: No detailed help available for this item.

Cause: You pressed [Help], but none is available for this menu item.

Action: No action required.

Level: 25

Trigger: None

FRM-10221: Cannot read file %s.

Cause: Either file privileges are set incorrectly, or the library you tried to open is invalid.

Action: Recompile the application library and try again.

Level: 25

Trigger: None

FRM-10222: Menu %s was created by an old version of the Form Compiler.

Cause: You are using a newer version of Oracle Forms than the one that created this menu module.

Action: Recompile the menu module and re-execute the command.

Level: 25

Trigger: None

FRM-10223: Application parameter module does not exist.

Cause: The parameter information could not be located in the library. This may be due to a library file that is invalid, or one that contains a different application.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10224: Application bind variable module does not exist.

Cause: The bind variable information could not be located in the library. This may be due to an invalid library file.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10225: Could not read parameter data.

Cause: The application library is invalid.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10226: Could not read bind variable data.

Cause: The application library is invalid.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10227: Too many menu parameters.

Cause: The application contains more menu parameters than can be used on your operating system.

Action: Revise and recompile the application, or contact your DBA.

Level: 25

Trigger: None

FRM-10228: Could not read help text.

Cause: The application library is invalid.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10229: Could not close file %s.

Cause: Operating system error or internal error.

Action: Contact your DBA.

Level: 25

Trigger: None

FRM-10230: Application procedure module does not exist.

Cause: The procedure information could not be located in the library. This may be due to an invalid library file.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10231: Could not read procedure data.

Cause: The application library is invalid.

Action: Recompile the application library and try again. If this is unsuccessful, contact your DBA.

Level: 25

Trigger: None

FRM-10233: Navigational procedures/macros not valid in current menu style.

Cause: You tried to use the full-screen, navigational packaged procedures, or macros in the pull-down or menu bar display style.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10234: Semicolon missing in macro statement.

Cause: The command line specified for this item has a syntax error.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10235: Macro %s not found.

Cause: The menu designer specified an undefined macro to be executed.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10236: No procedure/macro specified.

Cause: The menu designer has specified a blank command.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10237: Argument(s) not allowed for this procedure/macro.

Cause: The menu designer specified an argument to a command that does not take arguments.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10238: Error executing %s. Check argument(s).

Cause: The menu designer specified an argument to a command that does not take arguments.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10239: Cannot read form by that name.

Cause: Oracle Forms tried to read a form that does not exist in the current directory.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10240: Form name not specified.

Cause: Forms Runtime command did not give the name of a form to execute.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10241: Illegal operation when the Form Builder is active.

Cause: The menu designer specified a Built-in or macro that cannot be used when the Form Builder calls Forms Runtime.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10242: Cannot call linked-in Forms from Oracle Forms.

Cause: The menu designer specified a call to linked-in Forms from within Oracle Forms.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10243: Error occurred during invocation of Oracle Forms.

Cause: A call to Forms Runtime failed.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10244: Application %s does not exist.

Cause: The application name you specified does not exist in the database, or you do not have access privileges to it.

Action: Check the application name and try again, or contact your DBA.

Level: 25

Trigger: None

FRM-10245: Already on first item.

Cause: You pressed [Previous Item] from the first item in the parameter form.

Action: No action required. You cannot go to an item prior to the first item in a parameter form.

Level: 25

Trigger: None

FRM-10246: Error executing packaged procedure - inactive form.

Cause: The menu designer specified a built-in that cannot be executed in the current context.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10247: No active items in root menu of application.

Cause: You tried to open an application but its root menu has no items that you can access. The root menu is either the application's main menu or another menu specified when Oracle Forms called Forms Designer.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10248: No direct menu selection allowed when using a root menu.

Cause: The root menu is not the module's main menu, because Oracle Forms specified another root menu when calling Forms Designer.

Action: No action required. You can only use direct menu selection when the module's main menu is the root menu.

Level: 25

Trigger: None

FRM-10249: No authorization to run application %s.

Cause: You are not a valid user of the application you tried to run.

Action: No action required. If you think you should be a valid user, ask your DBA to grant you access privileges to the application.

Level: 25

Trigger: None

FRM-10250: Error initializing Forms Runtime application.

Cause: You did not name the module properly.

Action: Check the module name and enter it correctly.

Level: 25

Trigger: None

FRM-10251: Unsupported command type 4 switch used (-e,-i,-r,-w).

Cause: This menu option attempted to run a form, but specified a command line argument for Forms Runtime which is invalid when running a form from a menu.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10252: Unknown command type 4 switch used.

Cause: This menu option attempted to run a form, but specified an unknown command line argument for Forms Runtime.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10253: File name must be entered.

Cause: You have not entered a name (or you have deleted a name) for the file.

Action: You must enter a file name.

Level: 25

Trigger: None

FRM-10254: Cannot open file for screen shot.

Cause: The operating system could not open a file (e.g. permission problems, lack of disk space).

Action: Resolve the operating system condition that caused the error.

Level: 25

Trigger: None

FRM-10255: Error occurred during printing of screen shot.

Cause: The operating system had trouble with a file.

Action: Resolve the operating system condition that caused the error.

Level: 25

Trigger: None

FRM-10256: User is not authorized to run Oracle Forms Menu.

Cause: You are not enrolled in Oracle Forms. You do not have SELECT permission on the Oracle Forms base tables.

Action: Notify your DBA.

Level: 25

Trigger: None

FRM-10257: User is not authorized to select specified option.

Cause: You tried to select a menu item to which you do not have access.

Action: Choose another item or notify your DBA.

Level: 25

Trigger: None

FRM-10258: Specified menu is already active.

Cause: You tried to navigate to the current menu.

Action: No action required.

Level: 25

Trigger: None

FRM-10259: Invalid null argument to packaged procedure or function.

Cause: You did not specify an argument to a built-in, or the argument is invalid.

Action: Check the online Help for the proper built-in syntax.

Level: 25

Trigger: None

FRM-10260: No active items in selected menu.

Cause: You do not have access privileges for any items in this menu.

Action: Contact your DBA for access privileges if you think you should have access to the items on this menu.

Level: 25

Trigger: None

FRM-10261: Menu %s was created by a new version of the Form Compiler.

Cause: You are using an old version of Forms Runtime with a new version of the Form Compiler.

Action: Upgrade to new version of Forms Runtime.

Level: 25

Trigger: None

FRM-10262: Cannot put radio items, check boxes, or separators in menu bar.

Cause: You attempted to put radio items, check boxes, or separators in menu bar.

Action: Put these items in a submenu.

Level: 25

Trigger: None

FRM-10263: Cannot find icon file for iconic menu item.

Cause: No directory name for this icon.

Action: Contact the person who created the menu application.

Level: 25

Trigger: None

FRM-10264: Specified menu item does not exist.

Cause: You specified a menu item that does not exist in the form.

Action: Try retyping the name or choose another item name.

Level: 25

Trigger: None

FRM-10265: Library was created by an old version of the Form Compiler.

Cause: Oracle Forms cannot use library.

Action: Recompile the library with the current version of the Form Compiler.

Level: 25

Trigger: None

FRM-10266: Library was created by a new version of the Form Compiler.

Cause: Oracle Forms cannot use library.

Action: Recompile the library with current version of the Form Compiler.

Level: 25

Trigger: None

FRM-10267: Help type magic menu item must be placed on top-level menu.

Cause: You placed a help magic menu item on a submenu.

Action: Move the help magic menu item to the top-level menu (main menu).

Level: 25

Trigger: None

FRM-10268: Error: Program unit %s in library %s is uncompiled.

Cause: You called an uncompiled program unit from a library.

Action: Follow the PL/SQL program error.

Level: 25

Trigger: None

FRM-10269: Warning! Program unit %s in library %s is uncompiled.

Cause: In debug Forms Runtime, you called an uncompiled program unit in a library.

Action: This is just a warning. Forms Runtime will attempt to compile and run the program unit.

Level: 25

Trigger: None

FRM-10270: Cannot attach library %s while opening menu %s.

Cause: The specified library file is attached to the given menu, but cannot be located in the search path for PL/SQL libraries.

Action: Make sure the library file can be located before attempting to run with the specified menu again. For example, have it in the working directory.

Level: 25

Trigger: None

FRM-21011: PL/SQL unhandled exception %s.

Cause: An unhandled exception occurred while executing a menu trigger.

Action: Examine the text of the exception in this message. If this indicates a cause, correct it. If the problem persists, contact Oracle Support Services.

Level: 25

Trigger: None

FRM-40007: Invalid user identifier or password. Re-enter.

Cause: You entered an incorrect ORACLE username or password.

Action: Retype your username and password properly.

Level: 99

Trigger: ON-ERROR

FRM-40010: Cannot read form %s.

Cause: One of the following:

1. You entered a nonexistent form name.

2. You typed an incomplete path.

3. You do not have the proper privileges to run the form.

4. You do not have a compiled copy of the form.

Action: Retype the form name correctly, provide the proper path name, contact your system administrator, or compile the form.

Level: 5

Trigger: ON-ERROR

FRM-40011: Form was created by an old version of Oracle Forms.

Cause: The .FMB file was created with an old and incompatible version of the Form Compiler.

Action: Recompile the form or relink Generate.

Level: 99

Trigger: ON-ERROR

FRM-40012: Form was created by a new version of Oracle Forms.

Cause: The .FMB file was created by a new and incompatible version of the Form Compiler.

Action: Recompile the form.

Level: 99

Trigger: ON-ERROR

FRM-40013: Program Error: error occurred while reading form.

Cause: An internal error occurred while Oracle Forms was trying to read the .FMB file.

Action: Recompile the form.

Level: 99

Trigger: None

FRM-40014: Not enough memory to load the form.

Cause: Internal error. Your computer does not have enough memory to run the form.

Action: The designer might be able to modify the form so that it will run. If that is not feasible, your installation must make more memory available, either by modifying the operating system parameters or by adding more memory to the computer.

Level: 99

Trigger: ON-ERROR

FRM-40015: Unexpected end of file reading form.

Cause: The form was fragmented or incomplete.

Action: Recompile the form.

Level: 99

Trigger: None

FRM-40019: Unknown screen number to display.

Cause: An internal error occurred.

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

Level: 99

Trigger: None

FRM-40020: Page %d too small for this form.

Cause: Application design error. An item is positioned off the page.

Action: Ensure that all items that are associated with the given page fit completely on that page. You can reposition the items or resize the page.

Level: 99

Trigger: None

FRM-40021: Item in form file is too large.

Cause: An internal error occurred while Oracle Forms was reading the form.

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

Level: 99

Trigger: None

FRM-40023: Error creating record manager context.

Cause: Oracle Forms could not initialize its internal record manager.

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

Level: 99

Trigger: ON-ERROR

FRM-40024: Out of memory.

Cause: Internal error. Your computer does not have enough memory to run the form.

Level: 99

Trigger: ON-ERROR

FRM-40025: Cannot suppress screen output without file input.

Cause: You tried to run a form on the command line using incompatible preferences. The output_file preference works only in conjunction with the keyin preference.

Action: Retype the command to include both the output_file and keyin preferences.

Level: 99

Trigger: None

FRM-40026: Error opening key script file.

Cause: Oracle Forms cannot open the file you specified with the keyin preference.

Action: Make sure the file exists and the file protections are set properly. Or create a file with the keyin preference.

Level: 99

Trigger: None

FRM-40027: Error opening display spool file.

Cause: Operating system error. Oracle Forms cannot open a file specified with the output_file preference because there is insufficient disk space or because you have specified an incorrect filename.

Action: Contact your system administrator.

Level: 99

Trigger: None

FRM-40028: Error opening message file %s%s%s.MSB.

Cause: Oracle Forms cannot find the message file.

Action: Make sure the message file exists and the appropriate path is set.

Level: 99

Trigger: None

FRM-40029: Already logged on. Must logout before changing connections.

Cause: The Login() Built-in was issued while already logged on.

Action: Use the Logout() Built-in first.

Level: 25

Trigger: ON-ERROR

FRM-40030: File %s is not a Forms file.

Cause: The file specified on the command line was not a valid Oracle Forms file.

Action: Re-enter Forms Runtime startup command with the name of a valid file.

Level: 99

Trigger: ON-ERROR

FRM-40031: File %s is not a Forms Runtime file.

Cause: The file specified on the command line is not a Forms Runtime (.FMX) file.

Action: Re-enter a valid Forms Runtime (.FMX) file.

Level: 99

Trigger: ON-ERROR

FRM-40032: Internal Error: file %s contains an improper chunk size.

Cause: Internal error. File was compiled incorrectly or is corrupted.

Action: Recompile your file.

Level: 99

Trigger: ON-ERROR

FRM-40033: Internal Error: file %s contains a bad chunk table.

Cause: Internal error. File was compiled incorrectly or is corrupted.

Action: Recompile your file.

Level: 99

Trigger: ON-ERROR

FRM-40034: Cannot attach the library file.

Cause: Oracle Forms was unable to find the specified library file.

Action: Exit Forms Runtime and try again.

Level: 99

Trigger: ON-ERROR

FRM-40036: Library was created by a new version of Oracle Forms.

Cause: Oracle Forms unable to use library.

Action: Recompile the library with current version of Oracle Forms.

Level: 99

Trigger: ON-ERROR

FRM-40037: Library was created by an old version of Oracle Forms.

Cause: Oracle Forms unable to use library.

Action: Recompile the library with current version of Oracle Forms.

Level: 99

Trigger: ON-ERROR

FRM-40039: Cannot attach library %s while opening form %s.

Cause: The given library is attached to the form but cannot be located in the search path for PL/SQL libraries.

Action: Make sure that the given library can be found and that it has read permissions set.

Level: 99

Trigger: ON-ERROR

FRM-40040: Cannot perform proxy connection.

Cause: Database privileges for proxying user may not be configured on the database side or database account for SSO user not created.

Action: Make sure database is appropriately configured for making proxy connection.

Level: 99

Trigger: ON-ERROR

FRM-40041: Form %s requires a UTF8 character set.

Cause: An attempt was made to execute the specified form, but it contained one or more items whose datatype was NCHAR, and the NLS_LANG environment variable did not specify the UTF8 or AL32UTF8 character set.

Action: Set the NLS_LANG environment variable to a value which specifies the UTF8 or AL32UTF8 character set, and restart the application.

Level: 25

Trigger: ON-ERROR

FRM-40042: Unable to update the database password in the RAD repository.

Cause: An error occurred while trying to update the database password in the RAD repository.

Action: Contact your system administrator and get the password updated in the RAD repository. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40100: At first record.

Cause: You pressed [Previous Record] when the cursor was at the first record.

Action: No action is necessary.

Level: 5

Trigger: ON-ERROR

FRM-40101: Cannot position to a key item. None are navigable.

Cause: You pressed [Next Primary Key Item], but there are no enterable primary key items in this block.

Action: Use [Next Item] for navigation rather than [Next Primary Key Item].

Level: 10

Trigger: ON-ERROR

FRM-40102: Record must be entered or deleted first.

Cause: You pressed [Next Record] or [Down] in a context where it is meaningless. Either:

1. The last record in a block is the current record.

2. The block is empty.

3. You are in a new record in the middle of the block created by pressing [Insert Record].

Action: No action is necessary.

Level: 5

Trigger: ON-ERROR

FRM-40103: Cannot position to a key item. None are queryable.

Cause: You tried to use [Next Primary Key Item], but none of the primary key items in the block allow you to enter query criteria.

Action: No action is necessary.

Level: 10

Trigger: ON-ERROR

FRM-40104: No such block: %s.

Cause: Runtime error. A GO_BLOCK statement references a nonexistent block.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-40105: Unable to resolve reference to item %s.

Cause: Runtime error. A GO_ITEM statement references a nonexistent item.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-40106: No navigable items in destination block.

Cause: Runtime error. A GO_BLOCK statement references a block with no enterable items.

Action: Remove the statement or make at least one item in the block enterable.

Level: 99

Trigger: ON-ERROR

FRM-40107: Cannot navigate to non-displayed item %s.

Cause: Runtime error. A GO_ITEM statement references a non-displayed item.

Action: Remove the statement or turn on the Displayed Property for the indicated item.

Level: 20

Trigger: ON-ERROR

FRM-40108: No such form: %s.

Cause: You attempted to get/set properties of a nonexistent or unloaded form.

Action: Use a valid form name.

Level: 99

Trigger: ON-ERROR

FRM-40109: Cannot navigate out of current block in enter-query mode.

Cause: You attempted to navigate out of the current block during enter-query mode.

Action: No action is necessary. You cannot navigate out of the current block or record during enter-query mode.

Level: 99

Trigger: None

FRM-40110: At first block.

Cause: You attempted [Previous Block] when at the first block.

Action: None. Consider an alternative method of navigation.

Level: 5

Trigger: ON-ERROR

FRM-40111: At last block.

Cause: You attempted [Next Block] when at the last block.

Action: None. Consider an alternative method of navigation.

Level: 5

Trigger: ON-ERROR

FRM-40112: Attempted go_item to non enabled item %s:%s.

Cause: You attempted to issue a go_item to a non enabled item.

Action: None. Consider an alternative method of navigation.

Level: 99

Trigger: ON-ERROR

FRM-40200: Field is protected against update.

Cause: You tried to update a field that does not allow updates.

Action: No action is necessary. You cannot update this field in this form.

Level: 15

Trigger: ON-ERROR

FRM-40201: Field is full. Can't insert character.

Cause: Oracle Forms is in insert mode, and the current field is full.

Action: Delete a character to make room for the new character or press [Insert/Replace] to activate replace mode.

Level: 99

Trigger: None

FRM-40202: Field must be entered.

Cause: You have not entered a value (or you have deleted a value) in a field that requires data input.

Action: You must enter a value in this field.

Level: 15

Trigger: ON-ERROR

FRM-40203: Field must be entered completely.

Cause: You have not entered a complete value (or you have deleted part of a value) in a field that has a fixed length requirement.

Action: Enter a complete value (one that extends to the end of the field).

Level: 15

Trigger: ON-ERROR

FRM-40204: Cursor is at beginning of field value.

Cause: You tried to delete a character before the first character position of the field.

Action: Use [Delete Character] to delete the character that the cursor is on.

Level: 10

Trigger: ON-ERROR

FRM-40205: Cursor is beyond the current field value.

Cause: On a block mode terminal, you positioned the cursor out of a field.

Action: Move the cursor into the field and try the entry again.

Level: 99

Trigger: None

FRM-40206: Previous character is currently hidden.

Cause: You tried to delete a character that is off the screen.

Action: Scroll the character you want to delete into view using the arrow keys or [Scroll Left] and [Scroll Right].

Level: 10

Trigger: ON-ERROR

FRM-40207: Must be in range %.30s to %.30s.

Cause: You entered a value not in the valid item range.

Action: Enter a value in the range shown.

Level: 99

Trigger: None

FRM-40208: Form running in query-only mode. Cannot change database fields.

Cause: You entered a value on a query-only form.

Action: Do not enter values on this form. You can execute queries and view data, but you cannot alter existing data or enter new data.

Level: 15

Trigger: ON-ERROR

FRM-40209: Field must be of form %s.

Cause: The value that you entered did not match the format mask on the field.

Action: Retry with a field value that matches the format mask.

Level: 99

Trigger: ON-ERROR

FRM-40210: Search string not found.

Cause: Search string does not exist in the module.

Action: Check your search string to make sure it is accurate or try another search string.

Level: 99

Trigger: ON-MESSAGE

FRM-40211: Warning! Newlines may be stripped from this field.

Cause: You attempted to assign data with newlines to a single-line text field.

Action: Assign to a multi-line text field if you need the newlines.

Level: 5

Trigger: ON-MESSAGE

FRM-40212: Invalid value for field %s.

Cause: Caused by one of the following:

1. The value is not of the proper data type.

2. The value does not match any of the list of acceptable values.

3. For a text field, the value does not match the specified range.

Action: Retry with another value.

Level: 20

Trigger: ON-ERROR

FRM-40213: Cannot Copy_Region/Cut_Region; region not selected.

Cause: Region not selected.

Action: Select a region and try again.

Level: 5

Trigger: ON-ERROR

FRM-40214: Cannot open the clipboard for the copy/cut.

Cause: Clipboard unavailable.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40215: Cannot write to the clipboard.

Cause: Clipboard unavailable.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40216: Cannot open the clipboard for the paste.

Cause: Clipboard unavailable.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40217: Cannot get the data size from the clipboard.

Cause: Invalid data.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40218: Cannot read from the clipboard.

Cause: Invalid data.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40219: Cannot format the data read from the clipboard.

Cause: Invalid data.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40220: Cannot paste from the clipboard; value too long.

Cause: Invalid data.

Action: Platform specific.

Level: 99

Trigger: ON-ERROR

FRM-40221: Cannot Paste_Region; region not selected.

Cause: Paste_Region was invoked while no portion of the image item was selected.

Action: Select a region of the image item prior to calling Paste_Region.

Level: 99

Trigger: ON-ERROR

FRM-40222: Disabled item '%s.%s' failed validation.

Cause: Probable application design error. Forms determined that the item contains an invalid value, but it cannot give focus to the item because it is disabled. This could happen because either:

The application programmatically assigned an invalid valid to the item.

The application programmatically disabled the item after the end user entered an invalid valid in the item (and before the item was validated).

Action: Correct the application logic.

Level: 25

Trigger: ON-ERROR

FRM-40223: Field contains an invalid string for security purposes.

Cause: Field contains a string that could be a potential security violation.

Action: Remove the offending string.

Level: 15

Trigger: ON-ERROR

FRM-40301: Query caused no records to be retrieved. Re-enter.

Cause: No records matched the query criteria. Still in Enter Query mode.

Action: Either adjust the query criteria or press [Exit/Cancel] to leave Enter Query mode.

Level: 99

Trigger: ON-MESSAGE

FRM-40302: Cannot enter a query. No fields are queryable.

Cause: You pressed [Enter Query] while the cursor was in a block with no queryable fields.

Action: No action is necessary.

Level: 15

Trigger: ON-ERROR

FRM-40303: No base table fields in the block.

Cause: One of the blocks in the current module has no base table fields.

Action: No action is necessary.

Level: 99

Trigger: ON-ERROR

FRM-40350: Query caused no records to be retrieved.

Cause: The current query fetched no records from the table. The table is empty, or it contains no records that meet the query's search criteria.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40352: Last record of query retrieved.

Cause: You pressed [Down], [Next Record], [Next Set of Records], or [Scroll Down] after all records had been retrieved.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40353: Query cancelled.

Cause: You pressed [Exit/Cancel] in Enter Query mode, or you pressed CTRL-C (or its equivalent) while Oracle Forms was fetching rows from the database.

Action: No action is necessary.

Level: 5 when the query was canceled by CTRL-C; 10 otherwise

Trigger: ON-MESSAGE

FRM-40355: Query will retrieve 1 record.

Cause: You pressed [Count Query Hits]. If you now press [Execute Query], the number of records will be retrieved.

Action: No action is necessary.

Level: 25

Trigger: ON-MESSAGE

FRM-40356: Invalid number in example record. Query not issued.

Cause: In Enter Query mode, you entered an invalid number in the example record.

Action: Correct the entry and retry the query.

Level: 99

Trigger: ON-ERROR

FRM-40357: Invalid string in example record. Query not issued.

Cause: In query mode, you entered an invalid ALPHA or CHAR value in the example record.

Action: Correct the entry and retry the query.

Level: 99

Trigger: ON-ERROR

FRM-40358: Invalid date in example record. Query not issued.

Cause: In Enter Query mode, you entered an invalid DATE in the example record.

Action: Correct the entry and retry the query.

Level: 99

Trigger: ON-ERROR

FRM-40359: Invalid date or time in example record. Query not issued.

Cause: In Enter Query mode, you entered an invalid JDATE, EDATE, or TIME value in the example record.

Action: Correct the entry and retry the query.

Level: 99

Trigger: ON-ERROR

FRM-40360: Cannot query records here.

Cause: You attempted to query a block that does not allow queries.

Action: Do not attempt to query this block.

Level: 10

Trigger: ON-ERROR

FRM-40361: Query operation not support for TIME data type.

Cause: You made a query with a % "like" operator in a time field, which is not supported.

Action: Try to restate your query without a time data type.

Level: 10

Trigger: ON-ERROR

FRM-40364: The data type of item '%s' does not match the corresponding column in the stored procedure.

Cause: The data type of the item is different from the data type of the corresponding column in the stored procedure.

Action: Make the data type of the item in the block and the column in the stored procedure the same.

Level: 20

Trigger: ON-ERROR

FRM-40367: Invalid criteria in field %s in example record.

Cause: Only simple clauses are allowed in restricted enter query mode.

Action: Re-enter the criteria.

Level: 99

Trigger: ON-ERROR

FRM-40400: Transaction complete: %d records applied and saved.

Cause: Save complete.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40401: No changes to save.

Cause: No records were added or modified since the last apply or save. Caution: Unapplied database changes that were made through explicit sql (DML) are still applied, even when this message is displayed.

Action: No action is necessary.

Level: 5

Trigger: ON-ERROR

FRM-40402: Save cancelled.

Cause: You pressed CTRL-C (or the equivalent) while waiting for a lock.

Action: No action is necessary.

Level: 10

Trigger: ON-MESSAGE

FRM-40403: A calling form has unapplied changes. Save not allowed.

Cause: A calling form has unapplied changes.

Action: Apply the changes or return to the calling form and retry the save.

Level: 15

Trigger: ON-ERROR

FRM-40404: Database apply complete: %d records applied.

Cause: Apply complete.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40405: No changes to apply.

Cause: No records were added or modified since the last apply or save.

Action: No action is necessary.

Level: 5

Trigger: ON-ERROR

FRM-40406: Transaction complete: %d records applied; all records saved.

Cause: You finished an apply that recorded your changes and saved previously applied changes.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40407: Transaction complete: applied records saved.

Cause: You finished a save that saved previously applied changes.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-40408: database commit failure.

Cause: A database commit failed.

Action: Examine integrity constraints on the database tables that were updated. If any were violated, redo the updates without violating the constraints. If necessary, do the updates and the commit in sqlplus, and see if it issues an ORA-nnnnn message that will identify the constraint that was violated.

Level: 99

Trigger: ON-ERROR

FRM-40501: ORACLE error: unable to reserve record for update or delete.

Cause: A fatal error occurred while trying to select the record for update.

Action: Pressing [Display Error] provides more information, if it is available. You can also try to update or delete this record later. If necessary, contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40502: ORACLE error: unable to read list of values.

Cause: A fatal error occurred while trying to read a list of values.

Action: Contact your system administrator. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40504: ORACLE error: unable to execute a %s trigger.

Cause: A fatal error occurred while trying to execute a trigger.

Action: Contact your system administrator. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40505: ORACLE error: unable to perform query.

Cause: Processing error encountered. The table associated with the current block of the form might not exist, or your username might not have authority to perform the specified action on the table.

Action: Pressing [Display Error] provides more information, if it is available. You can also try to update or delete this record later. If necessary, contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40506: ORACLE error: unable to check for record uniqueness.

Cause: Processing error encountered while checking a record's primary key items for uniqueness. The table associated with the current block of the form does not exist, or you do not have authority to access the table.

Action: Contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40507: ORACLE error: unable to fetch next query record.

Cause: One of the following:

1. Oracle Forms was unable to allocate a record buffer (as reported in a previous FRM-40900).

2. If you are connected to an non-Oracle datasource through ODBC, the cursor loses its position in the result set after a commit.

3. A fatal error occurred while trying to fetch the next query record.

Action: For 1, refer to FRM-40900. For 2, requery. For 3, contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40508: ORACLE error: unable to INSERT record.

Cause: A fatal error occurred while trying to insert a record. The table associated with the current block of the form might not exist, your username might not have authority to perform the specified action on the table, or some other reason might have caused the fatal error.

Action: Contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40509: ORACLE error: unable to UPDATE record.

Cause: A fatal error occurred while trying to update a record. The table associated with the current block of the form might not exist, your username might not have authority to perform the specified action on the table, or some other reason might have caused the fatal error.

Action: Contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40510: ORACLE error: unable to DELETE record.

Cause: A fatal error occurred while trying to delete a record. The table associated with the current block of the form might not exist, your username might not have authority to perform the specified action on the table, or some other reason might have caused the fatal error.

Action: Contact your DBA.

Level: 99

Trigger: ON-ERROR

FRM-40511: ORACLE error occurred while executing a %s trigger.

Cause: A fatal error occurred while trying to execute a trigger. The table associated with the current block of the form might not exist, your username might not have authority to perform the specified action on the table, or some other reason might have caused the fatal error.

Action: Contact your DBA

Level: 99

Trigger: None

FRM-40512: ORACLE error: unable to issue SAVEPOINT command.

Cause: While attempting to call a new form or to commit, the issued SAVEPOINT command failed. This generally means that the module has run out of savepoints.

Action: Press [Display Error] to display the specific ORACLE error. You might be able to increase the maximum number of savepoints in the INIT.ORA file.

Level: 99

Trigger: ON-ERROR

FRM-40513: ORACLE error: unable to get date/time from database.

Cause: An error occurred while trying to resolve a database date/time initial value.

Action: Connect if you have not already done so. Verify database status.

Level: 10

Trigger: ON-ERROR

FRM-40514: Operation requires a database connection.

Cause: You tried to perform an database operation without connecting to the database.

Action: Connect to the database and retry.

Level: 20

Trigger: ON-ERROR

FRM-40515: ORACLE error: unable to open cursor.

Cause: You reached the limit in the number of cursors you can open.

Action: Check the number of cursors you have open.

Level: 99

Trigger: ON-ERROR

FRM-40600: Record has already been inserted.

Cause: You attempted to insert or update a record, but uniqueness is enforced on the block's primary key items. The record, as inserted or updated, is not unique.

Action: Change the values in one or more primary key fields of the current record, making them unique. If the requirement of unique primary key fields creates difficulties, consider eliminating the constraint.

Level: 25

Trigger: ON-ERROR

FRM-40602: Cannot insert into or update data in a view.

Cause: You tried to modify the contents of a view in a manner that is not permitted.

Action: No action is necessary; you cannot perform the operation you have attempted.

Level: 20

Trigger: ON-ERROR

FRM-40603: Records no longer reserved for update. Re-query to make changes.

Cause: You committed your modifications in a block where you had previously entered an ENTER_QUERY or EXECUTE_QUERY packaged procedure with the FOR_UPDATE parameter. This action released all locks on the records in this block.

Action: If you want to modify the block, you will need to re-query.

Level: 99

Trigger: ON-MESSAGE

FRM-40652: Cannot lock table in shared update mode.

Cause: Caused by one of the following:

1. You do not have access to this table.

2. Oracle Forms cannot lock the table in shared update mode.

Action: Contact your DBA.

Level: 15

Trigger: ON-ERROR

FRM-40653: Record not reserved for update or delete. Try again later.

Cause: You pressed CTRL-C (or the equivalent) to cancel. The operation that was attempting to update or delete the record was terminated.

Action: No action is necessary.

Level: 20

Trigger: ON-MESSAGE

FRM-40654: Record has been updated by another user. Re-query to see change.

Cause: Another user has updated this record since you performed a query and has changed at least one field in the record. Your actions have not changed the record in memory.

Action: You can update or delete this record now only if another user has restored the field values back to the way they were when you performed the query. Otherwise, you must re-query to fetch and display the new record into the form before you can update or delete it.

Level: 20

Trigger: ON-ERROR

FRM-40655: SQL error forced rollback: clear form and re-enter transaction.

Cause: A deadlock or some other error has caused the current transaction to fail. Your changes were rolled back.

Action: Clear the form (or exit and re-enter the form) and re-enter the transaction. You might have to modify the form's design to prevent the error from recurring.

Level: 25

Trigger: ON-ERROR

FRM-40657: Record changed or deleted by another user.

Cause: Another user has deleted the record since the query was executed, or database access control does not allow the operation.

Action: You can clear this record from your screen, but you cannot update or delete it since it no longer exists in the database, or database access control does not allow the operation. Check database access control policy.

Level: 20

Trigger: ON-MESSAGE

FRM-40659: Last row of query retrieved. Re-query to see remaining records.

Cause: A FOR_UPDATE query has been closed by executing a commit. Because the query was open prior to the commit, there may be more records to retrieve.

Action: Re-query to see remaining records.

Level: 5

Trigger: ON-MESSAGE

FRM-40700: No such trigger: %s.

Cause: Application design error. The form attempted to execute a trigger that doesn't exist, causing a fatal error.

Action: Correct the reference to the trigger.

Level: 20

Trigger: ON-ERROR

FRM-40702: Cannot call form with changes to save

Cause: You attempted to call another form with unsaved changes in the current form and savepoint mode off.

Action: Commit/post changes and then retry.

Level: 15

Trigger: ON-ERROR

FRM-40703: Fetched field cannot be changed in query mode.

Cause: You attempted to modify a fetched item in query mode.

Action: None required.

Level: 20

Trigger: ON-ERROR

FRM-40704: Illegal SQL statement in query-only mode

Cause: Application design error. The form tried to execute a function that is illegal in a query-only form.

Action: You might need to redesign the form.

Level: 20

Trigger: ON-ERROR

FRM-40705: Illegal SQL statement in non-commit-time trigger.

Cause: Application design error. The current trigger contains a SQL statement that is illegal for the trigger type.

Action: Rewrite the trigger text or use a different type of trigger.

Level: 20

Trigger: ON-ERROR

FRM-40714: Function illegal in this context.

Cause: Application design error. The current trigger contains an illegal function code.

Action: Rewrite the trigger text or use a different type of trigger.

Level: 20

Trigger: ON-ERROR

FRM-40724: Missing selector in CASE statement.

Cause: Application design error. The selector portion is missing in a CASE statement.

Action: Correct the statement.

Level: 99

Trigger: None

FRM-40730: Invalid message suppress level--unchanged from %d.

Cause: Application design error. A trigger attempted to set the system message level to an invalid number.

Action: Reset the SYSTEM.MESSAGE_LEVEL system variable to a valid number.

Level: 99

Trigger: ON-ERROR

FRM-40732: Target of GOTO does not exist in this macro.

Cause: Application design error. The label referenced in PL/SQL does not exist.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-40733: PL/SQL Built-in %s failed.

Cause: A fatal error occurred in Oracle Forms or in PL/SQL during trigger execution.

Action: Examine application logic to see if the Built-in is invoked incorrectly. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40734: Internal Error: PL/SQL error occurred.

Cause: An internal error occurred in PL/SQL during trigger execution.

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

Level: 99

Trigger: ON-ERROR

FRM-40735: %s trigger raised unhandled exception %s.

Cause: Application design error. The current trigger raised an exception (other than FORM_TRIGGER_FAILURE), but it did not handle the exception.

Action: Rewrite the trigger text to handle the exception.

Level: 99

Trigger: ON-ERROR

FRM-40736: Cannot initialize PL/SQL.

Cause: An internal error occurred while initializing PL/SQL.

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

Level: 99

Trigger: ON-ERROR

FRM-40737: Illegal restricted procedure %s in %s trigger.

Cause: Application design error. A trigger tried to execute a restricted packaged procedure.

Action: Remove the packaged procedure from the trigger text.

Level: 99

Trigger: ON-ERROR

FRM-40738: Argument %d to builtin %s cannot be null.

Cause: Application design error. No arguments were provided to the Built-in.

Action: Refer to the online Help for the correct usage of this Built-in.

Level: 99

Trigger: ON-ERROR

FRM-40739: Full rollback not allowed in post-only form.

Cause: Application design error. A trigger tried to issue a CLEAR_FORM packaged procedure with the FULL_ROLLBACK parameter in a post-only, called form.

Action: Remove the FULL_ROLLBACK parameter or ensure that the calling form does not have unposted changes when the call occurs.

Level: 99

Trigger: ON-ERROR

FRM-40740: Procedure %s only allowed in an on-%s trigger.

Cause: Application design error. A non-transactional trigger attempted to invoke a Built-in procedure that is restricted to a given trigger.

Action: Refer to the online Help for the correct usage of this procedure.

Level: 99

Trigger: ON-ERROR

FRM-40741: Unable to locate record %d on block %s.

Cause: You attempted to get or set record properties for an invalid record number for the given block.

Action: Verify your Get/Set record property parameters.

Level: 20

Trigger: ON-ERROR

FRM-40742: Illegal status conversion on record %d: %s to %s.

Cause: Application design error. A call to SET_RECORD_PROPERTY attempted an illegal conversion between record statuses.

Action: Refer to SET_RECORD_PROPERTY in online Help for correct transitions.

Level: 99

Trigger: ON-ERROR

FRM-40743: This operation with no base table requires the %s trigger.

Cause: Application design error. Attempted a database operation (query, insert, update, etc.) on a non-base table block without the appropriate transactional trigger.

Action: Refer to online Help for the appropriate transactional trigger and then create the correct trigger.

Level: 20

Trigger: ON-ERROR

FRM-40744: Truncation of input value will occur if editor accepted.

Cause: The editor's buffer is too small to accept the input.

Action: Change editors or enlarge the buffer.

Level: 99

Trigger: None

FRM-40745: Output value of Built-in %s was truncated.

Cause: Output variable is too small.

Action: Increase the size of the PL/SQL output variable.

Level: 15

Trigger: ON-ERROR

FRM-40746: Cannot call Built-in %s from startup debugger window.

Cause: Built-in is not accessible from the startup debugger window.

Action: Refer to the Oracle Forms Developer's Guide for a list of Built-ins that are not accessible from the startup debugger window.

Level: 99

Trigger: None

FRM-40747: Cannot call Built-in %s from a debug trigger.

Cause: Built-in is not accessible from the debug trigger.

Action: Refer to the Oracle Forms Developer's Guide for a list of Built-ins that are accessible from a debug trigger .

Level: 99

Trigger: None

FRM-40748: Trigger %s terminated by reset command.

Cause: You issued the reset command or you pressed the reset button in the debugger.

Action: If you want to navigate downward, go to the call stack.

Level: 99

Trigger: None

FRM-40749: Invalid record status specified for record %d.

Cause: Application design error. An attempt was made to set the Status Property of a record to an invalid value.

Action: The record's Status Property should be set to NEW_STATUS, QUERY_STATUS, INSERT_STATUS, or CHANGED_STATUS.

Level: 99

Trigger: ON-ERROR

FRM-40750: Record %d: Can't set status to QUERY or CHANGED in a control block.

Cause: Application design error. An attempt was made to set the Status Property of a record in a control block to QUERY_STATUS or CHANGED_STATUS.

Action: The record's Status Property should be set to NEW_STATUS or INSERT_STATUS.

Level: 99

Trigger: ON-ERROR

FRM-40800: User exit %s does not exist.

Cause: The form tried to invoke a user exit that does not exist. This could be caused by one of the following:

1. You are using the wrong version of Forms Runtime.

2. There could be an error in the form.

3. The FORMS_USEREXITS environment variable is not set correctly.

Action: Make sure that the dynamic library which defines the user exit symbol is listed in FORMS_USEREXITS list.

Level: 20

Trigger: ON-ERROR

FRM-40801: memory allocation failure

Cause: A memory allocation failed when Forms Runtime attempted to create an internal macro.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 25

Trigger: ON-ERROR

FRM-40808: Cannot execute HOST command. Error code = %s.

Cause: Cannot execute a HOST statement because of an operating system error.

Action: Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-40809: HOST command had error code = %s.

Cause: The operating system command resulted in the above error code.

Action: Verify that you entered the command properly.

Level: 99

Trigger: ON-ERROR

FRM-40811: Shell command had error.

Cause: The operating system command resulted in the above error code.

Action: Verify that you entered the command properly.

Level: 99

Trigger: ON-ERROR

FRM-40815: Variable GLOBAL.%s does not exist.

Cause: Application design error. A trigger references a global variable that does not exist.

Action: Create the global variable or remove the reference.

Level: 20

Trigger: ON-ERROR

FRM-40816: Could not allocate memory for new symbol.

Cause: A memory allocation failed when Forms Runtime attempted to access a new global variable.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: None

FRM-40817: Could not allocate memory for new value.

Cause: A memory allocation failed when Forms Runtime attempted to access a new global variable.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: None

FRM-40818: System variable name not defined.

Cause: You have tried to access a system variable that does not exist.

Action: Check the system variable name.

Level: 99

Trigger: ON-ERROR

FRM-40819: System variable is not modifiable.

Cause: You have tried to modify a system variable.

Action: You cannot modify system variables.

Level: 99

Trigger: ON-ERROR

FRM-40828: CALL or CALLQRY with invalid variable reference.

Cause: Application design error. A CALL or CALLQRY function code contains an invalid variable reference.

Action: Correct the statement.

Level: 99

Trigger: None

FRM-40831: Truncation occurred: value too long for field %s.

Cause: Application design error. A trigger, query, or user exit read a value into an item that is not long enough to hold the entire value. The item truncated the value.

Action: Increase the target item's item length to avoid truncation.

Level: 15

Trigger: ON-ERROR

FRM-40832: FORMS_USEREXITS environment variable not set. User exit %s did not execute.

Cause: FORMS_USEREXITS must be set for forms USER_EXIT Built-in to work.

Action: Set FORMS_USEREXITS to dynamic libraries, which define the user exit symbols. Searching is done in the order libraries are listed.

Level: 20

Trigger: ON-ERROR

FRM-40833: Could not completely load the dynamic user exit libraries. User exit %s did not execute.

Cause: User exit symbol was not found and there were failures in opening some of the dynamic user exit libraries.

Action: Make sure that all the user exit libraries listed in the FORMS_USEREXITS environment variable are correct and available.

Level: 20

Trigger: ON-ERROR

FRM-40834: Value from item %s.%s is too long for result set column (actual: %d bytes, maximum: %d bytes).

Cause: In a block based on a stored procedure, the application attempted to insert or update a value with too many bytes into a result set column with BYTE length semantics. The value was obtained from an instance of an item in the block. The insert or update attempt was suppressed.

Action: Ensure that the Maximum Length and Data Length Semantics in character-datatype items in the block match the definitions of the result-set columns in the stored procedure.

Level: 99

Trigger: ON-ERROR

FRM-40835: Value from item %s.%s is too long for result set column (actual: %d characters, maximum: %d characters).

Cause: In a block based on a stored procedure, the application attempted to insert or update a value with too many characters into a result set column with CHAR length semantics. The value was obtained from an instance of an item in the block. The insert or update attempt was suppressed.

Action: Ensure that the Maximum Length and Data Length Semantics in character-datatype items in the block match the definitions of the result-set columns in the stored procedure.

Level: 99

Trigger: ON-ERROR

FRM-40900: Unable to allocate record buffer for insert record, update record, or fetch. Operation aborted.

Cause: An insert record, update record, or fetch required main memory or space in the temporary record buffer file, but the main memory or disk space was unavailable. Further information is available from a preceding message: FRM-41839 (I/O error on the temporary record buffer file), FRM-41840 insufficient main memory), FRM-41847 (temporary record buffer file size limit exceeded), or FRM-41850 (archived record memory threshold exceeded).

Action: Refer to the preceding FRM-41839, FRM-41840, FRM-41847, or FRM-41850.

Level: 99

Trigger: ON-MESSAGE

FRM-40901: Note: not enough memory to remember all or part of this query.

Cause: A memory allocation failed when Forms Runtime attempted to save a query.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40902: SQL statement too large.

Cause: Application design error. The form's design includes a SQL command that is more than 2048 characters long.

Action: Shorten the SQL command.

Level: 99

Trigger: ON-ERROR

FRM-40903: Cannot create output file.

Cause: You pressed [Print Screen], but screen contents could not be written to a file because of one of the following:

1. You have entered an illegal file name.

2. The operating system does not give you authority to create files.

3. The necessary disk or directory space is not available.

Action: Check the file name you have entered and correct it if necessary. If you need additional help, contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-40904: Program error: unknown operation to be performed on record.

Cause: Internal error.

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

Level: 99

Trigger: ON-ERROR

FRM-40905: Unable to buffer more records on disk.

Cause: Internal error.

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

Level: 99

Trigger: None

FRM-40906: FATAL ERROR: cannot write a buffered record to disk.

Cause: Internal error while trying to write a buffered record to the disk.

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

Level: 99

Trigger: ON-ERROR

FRM-40907: FATAL ERROR: cannot read a buffered record from disk.

Cause: Internal error while trying to read a buffered record from the disk.

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

Level: 99

Trigger: ON-ERROR

FRM-40908: RAM Internal Error: %s

Cause: An internal error occurred within the form's internal record manager.

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

Level: 20

Trigger: ON-ERROR

FRM-40909: Internal Error: unknown error %d.

Cause: Internal error. Forms Runtime attempted to issue an unknown error message.

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

Level: 99

Trigger: None

FRM-40911: Record not created due to sequence number generation error.

Cause: Internal error. Either the sequence number object does not exist, or the designer does not have privileges for the sequence number object, or some other fatal database error occurred.

Action: Contact your DBA. If your DBA cannot correct the problem, and the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40912: WHEN-NEW-RECORD trigger failed. Record not created.

Cause: A runtime error occurred in a When-New-Record trigger that caused the trigger to fail. No new record was created.

Action: Contact your DBA. If your DBA cannot correct the problem, and the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40913: List of Values maximum exceeded. Some values are not displayed.

Cause: Application design error. Unable to return all the records in the current list of values; the number exceeds the maximum limit.

Action: Specify no more than 32,767 records to be returned in a list of values.

Level: 25

Trigger: ON-ERROR

FRM-40914: Memory allocation error: unable to complete transaction.

Cause: A memory allocation failed while Forms Runtime attempted to complete a transaction.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40915: Memory allocation error: unable to execute trigger %s.

Cause: A memory allocation failed while Forms Runtime attempted to execute a trigger.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40916: Memory allocation error: unable to execute query.

Cause: A memory allocation failed while Forms Runtime attempted to execute a query.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40917: Memory allocation error: unable to lock record.

Cause: A memory allocation failed while Forms Runtime attempted to lock a record.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40919: Internal SQL statement execution error: %d.

Cause: Error in the SQL statement Oracle Forms has tried to execute.

Action: Check the last SQL statement.

Level: 25

Trigger: ON-ERROR

FRM-40920: Unable to create view: low on system resources.

Cause: Something in your environment or application has prevented view creation.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40921: Could not create item: %s.

Cause: Something in your environment or application has prevented item creation.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-40922: An OLE error occurred: 0x%x.

Cause: A Built-in called an OLE or OLE-related function which failed.

Action: You need to lookup the error number in an OLE manual for further details.

Level: 99

Trigger: ON-ERROR

FRM-40923: OLE is not supported on this platform.

Cause: A Built-in that required OLE support was called, and your platform does not support OLE.

Action: Don't call OLE-related Built-ins on platforms that don't support OLE.

Level: 99

Trigger: ON-ERROR

FRM-40924: Invalid argument index specified.

Cause: An attempt was made to retrieve a value from the OLE-argument stack whose index was out of bounds for the size of the current OLE-argument stack

Action: Argument indices range from 1 to the number specified in the last call to FORMS_OLE.InitArgs()

Level: 99

Trigger: ON-ERROR

FRM-40925: No space initialized in OleArg for argument.

Cause: An attempt was made to store too many arguments into the initialized OLE-argument stack.

Action: Make sure you specify enough space in your call to FORMS_OLE.InitArgs().

Level: 99

Trigger: ON-ERROR

FRM-40926: OLE Object is NULL.

Cause: You cannot operate on a NULL OLE object.

Action: Do not attempt to call FORMS_OLE Built-ins with NULL OLE-objects.

Level: 99

Trigger: ON-ERROR

FRM-40927: Variant is not an array.

Cause: An attempt was made to access a variant as if it contained an array, and it did not.

Action: You can call FORMS_OLE.Get_Dims() to ensure that you have a variant with an array. For arrays, the return value for the function is greater than or equal to 1.

Level: 99

Trigger: ON-ERROR

FRM-40928: Too many array indices specified.

Cause: An attempt was made to access a variant that holds an array, but too many array indices were specified.

Action: You must use the correct number of array indices, the same number as returned by FORMS_OLE.GET_Dims().

Level: 99

Trigger: ON-ERROR

FRM-40929: Too few array indices specified.

Cause: An attempt was made to access a variant that holds an array, but too few array indices were specified.

Action: You must use the correct number of array indices, the same number as returned by FORMS_OLE.GET_Dims().

Level: 99

Trigger: ON-ERROR

FRM-40930: Array index was non-numeric.

Cause: An attempt was made to access a variant that holds an array, but the supplied array indices were non-numeric and not either ROW or COLUMN.

Action: The only valid array indices are numbers, which should be separated by columns. If you're fetching into a table from a variant, ROW and COLUMN can be used as placeholders for the row and column iterators during table construction.

Level: 99

Trigger: ON-ERROR

FRM-40931: Cannot populate table because datatype is unsupported.

Cause: An attempt to populate a table failed because one of its columns used an unsupported datatype.

Action: Restrict your column types to integers, numbers, strings, and dates.

Level: 99

Trigger: ON-ERROR

FRM-40932: Cannot populate variant because table's datatype is unsupported.

Cause: An attempt to populate a variant failed because one of the source table's columns used an unsupported datatype.

Action: Restrict your column types to integers, numbers, strings, and dates.

Level: 99

Trigger: ON-ERROR

FRM-40933: Cannot populate table because datatype is incorrect.

Cause: An attempt to populate a table failed because the block's datatype did not match the table's datatype.

Action: The table datatype must match the datatypes of the block's columns that are being retrieved.

Level: 99

Trigger: ON-ERROR

FRM-40934: Cannot populate table because records are out of bounds.

Cause: An attempt to populate a table failed because an illegal start or end record was specified.

Action: start_rec and end_rec parameters must fall between 1 and the number of retrievable records. end_rec may also be ALL_RECORDS.

Level: 99

Trigger: ON-ERROR

FRM-40935: Object does not exist locally.

Cause: An attempt to release an object failed because the 'kill_persistent' parameter was set to FALSE, and no local object existed to release.

Action: Never release objects you don't own.

Level: 10

Trigger: ON-ERROR

FRM-41000: This function is not currently available.

Cause: You pressed an undefined function key.

Action: Press [Show Keys] to determine which function key you should have pressed.

Level: 5

Trigger: ON-ERROR

FRM-41001: This function is not allowed on this device.

Cause: You tried to execute the Insert/Replace function.

Action: No action is necessary.

Level: 5

Trigger: ON-ERROR

FRM-41002: Please make a valid selection.

Cause: You entered an invalid selection number on the block menu; that block does not exist in this form.

Action: Select an existing block.

Level: 10

Trigger: ON-ERROR

FRM-41003: This function cannot be performed here.

Cause: You tried to perform a function that references a table, but current block does not correspond to any table.

Action: No action is necessary. You cannot perform the requested function on this block.

Level: 10

Trigger: ON-ERROR

FRM-41004: This function is not allowed in this mode.

Cause: You pressed a function key that does not work in this mode.

Action: No action is necessary.

Level: 10

Trigger: ON-ERROR

FRM-41005: Internal Error: function key not implemented.

Cause: You pressed a disabled function key.

Action: No action is necessary. You cannot use the function key in the current context unless the form's definition is modified.

Level: 25

Trigger: ON-ERROR

FRM-41007: Cursor not in a valid item. Function key was ignored.

Cause: You were not in a valid item when you pressed the function key.

Action: Position the cursor inside the item and press the function key again.

Level: 10

Trigger: ON-ERROR

FRM-41008: Undefined function key. Press %s for list of valid keys.

Cause: You pressed an undefined function key.

Action: Press [Show Keys] to determine which function key you should have pressed.

Level: 99

Trigger: ON-ERROR

FRM-41009: Function key not allowed. Press %s for list of valid keys.

Cause: You pressed a function key that is not allowed in this environment.

Action: Press [Show Keys] to determine which function key you should have pressed.

Level: 99

Trigger: ON-ERROR

FRM-41010: Cannot set attribute of the current item.

Cause: Application design error. A SET_ITEM statement tried to turn off the Input Allowed Property for the current item.

Action: Eliminate the statement or rewrite the trigger.

Level: 99

Trigger: ON-ERROR

FRM-41011: Undefined visual attribute.

Cause: Application design error. A Built-in tried to set an undefined visual attribute.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41012: Undefined item or variable reference.

Cause: Application design error. A NAME_IN statement tried to reference a nonexistent item or variable.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41013: Undefined property specified for item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in specified an undefined property.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41014: Cannot set property of null canvas item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in tried to change some property of a NULL canvas item.

Action: Specify a canvas for the item, or remove the statement.

Level: 99

Trigger: ON-ERROR

FRM-41015: Cannot set ENTERABLE Property of the current item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to change the Enterable Property of the current item.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41016: Cannot set DISPLAYED Property of the current item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to change the Displayed Property of the current item.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41017: Cannot set UPDATE ALLOWED Property of non-enabled item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in tried to turn on the Update Allowed Property of a non-enterable item.

Action: To turn on the Update Allowed Property of an item you must also turn on the Input Allowed Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41018: Cannot set UPDATE_NULL Property of non-enabled item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to turn on the Update If Null Property of a non-enterable item.

Action: To turn on the Update If Null Property of an item you must also turn on the Input Allowed Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41019: Cannot set REQUIRED Property of non-enabled item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in tried to turn on the Required Property of a non-enterable item.

Action: To turn on the Required Property of an item you must also turn on the Input Allowed Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41020: Cannot set ENTERABLE Property of non-displayed item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to turn on the Enterable Property of a non-displayed item.

Action: To turn on the Input Allowed Property of an item you must also turn on the Displayed Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41021: Cannot set QUERYABLE Property of non-displayed item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to turn on the Query Allowed Property of a non-displayed item.

Action: To turn on the Query Allowed Property of an item you must also turn on the Displayed Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41022: Cannot set REQUIRED Property of non-updateable item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in tried to turn on the Required Property of a non-updateable item.

Action: To turn on the Required Property of an item you must also turn on either the Update Allowed Property or the Update If Null Property of the item.

Level: 99

Trigger: ON-ERROR

FRM-41023: Cannot set UPDATE ALLOWED Property of secure item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in tried to change the Update Allowed Property of a database item which the user does not have permission to update.

Action: Either correct the SET_ITEM statement or grant update permission on the column to the user.

Level: 99

Trigger: ON-ERROR

FRM-41024: Cannot set UPDATE_NULL Property of secure item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in tried to change the Update If Null Property of a database item which the user does not have permission to update.

Action: Either correct the SET_ITEM statement or grant update permission on the column to the user.

Level: 99

Trigger: ON-ERROR

FRM-41025: Page number %d does not exist.

Cause: Application design error. Attempted an operation on a non-existent page.

Action: Check arguments to page related Built-ins.

Level: 99

Trigger: ON-ERROR

FRM-41026: Field does not understand operation.

Cause: You attempted to perform an operation that is invalid for the given item type.

Action: Do not attempt to perform the operation on an item to which the operation cannot be applied.

Level: 99

Trigger: ON-ERROR

FRM-41027: Primary key must be defined for this block.

Cause: There are no primary key items in the block and one of the following has happened:

1. You attempted to set Key_Mode of primary key option on for the block.

2. The Key_Mode is set to Automatic and the datasource to which your are connected does not support UNIQUE key mode.

Action: Specify one or more primary key items on the block.

Level: 99

Trigger: ON-ERROR

FRM-41028: Invalid property.

Cause: You passed an invalid property constant to a Get or Set property Built-in.

Action: Verify arguments.

Level: 99

Trigger: ON-ERROR

FRM-41029: Invalid parameter.

Cause: You attempted to set a form, block, item, or record property to an invalid value.

Action: Verify arguments to SET_FORM_PROPERTY, SET_BLOCK_PROPERTY, SET_ITEM_PROPERTY, or SET_RECORD_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41030: Cannot reset ITEM_LENGTH of item %s.%s.

Cause: Application design error. Attempted to change the length of a fixed length item.

Action: Statically declare the item to be of the maximum necessary length or change item type.

Level: 99

Trigger: ON-ERROR

FRM-41031: Cannot reset ITEM_LENGTH greater than the allocated buffer.

Cause: Application design error. Tried to reset ITEM_LENGTH greater than the allocated buffer.

Action: Increase item length in the form definition.

Level: 99

Trigger: ON-ERROR

FRM-41032: Cannot set ENABLED Property of current item %s.%s.

Cause: A call to SET_ITEM_PROPERTY attempted to set the Enabled Property of the current item.

Action: Either correct the call to SET_ITEM_PROPERTY or navigate to another item before setting the Enabled Property.

Level: 99

Trigger: ON-ERROR

FRM-41033: Cannot set ENABLED Property of non-displayed item %s.%s.

Cause: A call to SET_ITEM_PROPERTY attempted to set the Enabled Property of a non-displayed item.

Action: First navigate to the item, then set the Enabled Property with a call to SET_ITEM_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41034: Cannot set NAVIGABLE Property of non-displayed item %s.%s.

Cause: A call to SET_ITEM_PROPERTY attempted to set the Navigable Property of a non-displayed item.

Action: First navigate to the item, then set the Navigable Property with a call to SET_ITEM_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41035: Cannot set NAVIGABLE Property of non-enabled item %s.%s.

Cause: A call to SET_ITEM_PROPERTY attempted to set the Navigable Property of a non-enabled item.

Action: First set the Enabled Property of the item with a call to SET_ITEM_PROPERTY. Then set the Navigable Property of the item with another call to SET_ITEM_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41036: Cannot modify a checkbox that does not allow querying.

Cause: You attempted to modify a check box that does not allow querying.

Action: First set the Query Allowed Property to True, then the end user may shift and click the check box to enable or disable the item.

Level: 99

Trigger: ON-ERROR

FRM-41037: Cannot modify a radio group that does not allow querying.

Cause: You attempted to modify a radio group that does not allow querying.

Action: First set the Enabled Property to True with a call to SET_RADIO_BUTTON_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41038: Item %s is not a checkbox.

Cause: A call to CHECKBOX_CHECKED was made to an item which was not a check box.

Action: Correct the call to CHECKBOX_CHECKED.

Level: 20

Trigger: ON-ERROR

FRM-41039: Invalid Alert ID %d.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_ALERT will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41040: Cannot find radio button: %s.

Cause: An invalid ID or name was passed to a Built-in subprogram.

Action: Check the name or ID that you entered and try again.

Level: 99

Trigger: ON-ERROR

FRM-41041: Cannot find form module: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_FORM will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41042: No such property for Set_Item_Property.

Cause: You attempted to set an invalid item property.

Action: Check the documentation for setting item properties and try again.

Level: 99

Trigger: ON-ERROR

FRM-41043: Cannot find timer: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_TIMER will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41044: Error deleting timer %s

Cause: An error occurred while executing a DELETE_TIMER Built-in.

Action: Verify that your timer has been created correctly.

Level: 99

Trigger: ON-ERROR

FRM-41045: Cannot find item: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_ALERT will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41046: Invalid parameter used for Set_Item_Property.

Cause: An invalid parameter was passed to SET_ITEM_PROPERTY.

Action: Verify the valid parameters for SET_ITEM_PROPERTY and try again.

Level: 99

Trigger: ON-ERROR

FRM-41047: Cannot navigate out of current block in enter-query mode.

Cause: An illegal attempt to navigate out of the current block when in Enter Query mode.

Action: Perform operation before entering query mode.

Level: 99

Trigger: ON-ERROR

FRM-41048: Procedure %s is not valid in a %s trigger.

Cause: The indicated procedure is not valid when called from the indicated trigger. The procedure may be a restricted procedure, which cannot be called from any trigger that fires during navigation.

Action: Correct the invalid trigger.

Level: 20

Trigger: ON-ERROR

FRM-41049: You cannot delete this record.

Cause: You attempted to delete a record on a block that does not allow deletes.

Action: Do not attempt to delete records in this block until you have set the Delete Allowed Property to True.

Level: 10

Trigger: ON-ERROR

FRM-41050: You cannot update this record.

Cause: You attempted to update a record on a block that does not allow updates.

Action: Do not attempt to update records in this block until you have set the Update Allowed Property to True.

Level: 10

Trigger: ON-ERROR

FRM-41051: You cannot create records here.

Cause: You attempted to create records on a block that does not allow inserts.

Action: Do not attempt to create and insert new records into this block until you have set the Insert Allowed Property to True.

Level: 10

Trigger: ON-ERROR

FRM-41052: Cannot find Window: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_WINDOW will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41053: Cannot find Canvas: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_CANVAS will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41054: No such property for Get_Record_Property.

Cause: You attempted to get a non-existent record property.

Action: Verify call to GET_RECORD_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41055: No such property for Set_Record_Property.

Cause: You attempted to set a non-existent record property.

Action: Verify call to SET_RECORD_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41056: Cannot find Block: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_BLOCK will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41057: No such property for Set_View_Property.

Cause: You attempted to set a non-existent view property.

Action: Verify call to SET_VIEW_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41058: No such property for Get_Item_Property.

Cause: You attempted to get a non-existent item property.

Action: Verify call to GET_ITEM_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41059: No such property for Set_Canvas_Property.

Cause: You attempted to set a non-existent canvas property.

Action: Verify call to SET_CANVAS_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41060: Cannot disable Primary Key Property of only key item.

Cause: You attempted to turn off the Primary Key Property on the last primary key item on a block with one of the following:

1. The Primary Key Property.

2. Key mode of the primary key.

3. The database to which you are connected does not support UNIQUE key mode.

Action: Disable the block properties first.

Level: 20

Trigger: ON-ERROR

FRM-41061: No such property for Get_Window_Property.

Cause: You attempted to get a non-existent window property.

Action: Verify call to GET_WINDOW_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41062: Cannot find Editor: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_EDITOR will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41063: Cannot create Editor.

Cause: Not enough memory available for Forms Runtime.

Action: Try calling SHOW_EDITOR again after closing some of your windows.

Level: 20

Trigger: ON-ERROR

FRM-41064: Cannot create Timer %s: illegal identifier name.

Cause: Illegal identifier name.

Action: Check legal syntax for naming timers.

Level: 99

Trigger: ON-ERROR

FRM-41065: Cannot find Menu: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_MENU will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41066: No such property for Get_Form_Property.

Cause: You attempted to get a non-existent form property.

Action: Verify call to GET_FORM_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41067: Cannot find Menu Item: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_MENU_ITEM will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41068: Error in Set_Menu_Item_Property.

Cause: Invalid call to SET_MENU_ITEM_PROPERTY.

Action: Verify valid parameters and try again.

Level: 20

Trigger: ON-ERROR

FRM-41069: Error in Get_Menu_Item_Property.

Cause: Invalid call to GET_MENU_ITEM_PROPERTY.

Action: Verify valid parameters and try again.

Level: 20

Trigger: ON-ERROR

FRM-41070: Unknown property for Set_Menu_Item_Property.

Cause: You attempted to set a non-existent menu item property.

Action: Verify call to SET_MENU_ITEM_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41071: Unknown property for Get_Menu_Item_Property.

Cause: You attempted to get a non-existent menu item property.

Action: Verify call to GET_MENU_ITEM_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41072: Cannot create Group %s

Cause: Caused by one of the following

1. Duplicate column names in SQL statement.

2. Invalid record group name.

3. Query is invalid.

Action: Check the group name and/or correct the SQL statement.

Level: 20

Trigger: ON-ERROR

FRM-41073: Cannot find Group: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_GROUP will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41074: Cannot find Group or Column: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_GROUP or FIND_COLUMN will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41075: Error deleting Group.

Cause: The record group name or ID specified in the call to DELETE_GROUP is invalid, or the record group was not dynamically created.

Action: Check the record group name or ID, and make sure that the specified record group was dynamically created.

Level: 20

Trigger: ON-ERROR

FRM-41076: Error populating Group.

Cause: Caused by one of the following

1. An invalid group name or ID was specified.

2. An nonempty static record group was specified.

3. Query failed due to an invalid column or table name, or the query and group column structure do not match.

Action: Correct the application logic.

Level: 20

Trigger: ON-ERROR

FRM-41077: Error deleting Group Row(s).

Cause: DELETE_GROUP_ROW cannot be used to delete records from a static record group, or you specified an invalid row number.

Action: Correct the call to DELETE_GROUP_ROW.

Level: 20

Trigger: ON-ERROR

FRM-41078: Error resetting Group selection.

Cause: Record group name or ID specified is invalid.

Action: Check the record group name or ID and try again.

Level: 20

Trigger: ON-ERROR

FRM-41079: Error adding Group column.

Cause: Caused by one of the following:

1. You cannot add columns to a group that already has rows.

2. The width of CHAR columns cannot be less than the width of the corresponding database column.

3. You entered the name of a nonexistent or invalid record group.

4. You entered the name of a nonexistent or invalid column.

5. You entered a column type other than CHAR, NUMBER, or DATE.

6. Adding the column would cause the total memory required for non-LONG columns in a record to exceed 65535 bytes, and the record manager cannot be used for the record group because the FORMS_RECMGR_ARCHIVE environment variable has been set to WRITE_TMPFILE.

Action: Do one of the following:

1. If the group already has rows, delete the rows with DELETE_GROUP_ROW, then add the column.

2. Specify valid record group names, column names, and column types.

3. Set the FORMS_RECMGR_ARCHIVE environment variable to MAP_SWAP or MAP_TMPFILE, or leave it unset. (It will default to MAP_SWAP).

Level: 20

Trigger: ON-ERROR

FRM-41080: Error adding Group row.

Cause: Caused by one of the following:

1. You attempted to add rows to a group that is nonexistent or has no columns.

2. You entered the name of a nonexistent record group.

3. You provided a row number that is out of range or invalid.

Action: Create the group and add columns first. Check the call to ADD_GROUP_ROW to make sure that the record group name and row number are valid.

Level: 20

Trigger: ON-ERROR

FRM-41081: Cannot move Item: invalid position.

Cause: You attempted to move the item to an invalid position on the canvas.

Action: Make sure the coordinates you chose in your call to SET_ITEM_PROPERTY are valid.

Level: 99

Trigger: ON-ERROR

FRM-41082: Cannot resize item: position of item places it off of canvas.

Cause: The height and/or width you specified in your call to SET_ITEM_PROPERTY is invalid, or the height and/or width you specified causes the item to extend off of the canvas.

Action: Correct the call to SET_ITEM_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41083: No such property for Set_Form_Property

Cause: You attempted to set a nonexistent form property.

Action: Verify call to SET_FORM_PROPERTY for valid property.

Level: 20

Trigger: ON-ERROR

FRM-41084: Error getting Group Cell.

Cause: Invalid call to GET_GROUP_CHAR_CELL, GET_GROUP_DATE_CELL, OR GET_GROUP_NUMBER_CELL.

Action: Make sure the column type is of CHAR, DATE, or NUMBER, respectively. Check the validity of the row number and column name specified.

Level: 20

Trigger: ON-ERROR

FRM-41085: Error getting Group Row count.

Cause: Invalid call to GET_GROUP_ROW_COUNT.

Action: Check the record group name and try again.

Level: 20

Trigger: ON-ERROR

FRM-41086: Error getting Group selection count.

Cause: You specified an invalid record group name. Invalid call to GET_GROUP_SELECTION_COUNT.

Action: Correct the call to GET_GROUP_SELECTION.

Level: 20

Trigger: ON-ERROR

FRM-41087: Error getting Group selection.

Cause: You specified an invalid record group name or selection number. Invalid call to GET_GROUP_SELECTION.

Action: Correct the call to GET_GROUP_SELECTION.

Level: 20

Trigger: ON-ERROR

FRM-41088: Cannot set Group selection.

Cause: You specified an invalid record group name, ID, or row number.

Action: Correct the call to SET_GROUP_SELECTION.

Level: 20

Trigger: ON-ERROR

FRM-41089: Cannot move View: invalid position.

Cause: The x, y pair specified in the call to SET_VIEW_PROPERTY is invalid.

Action: Correct the call to SET_VIEW_PROPERTY by making sure that the position specified by your coordinates is on the canvas.

Level: 99

Trigger: ON-ERROR

FRM-41090: Invalid item type for go_item: %s.

Cause: You cannot navigate to the item.

Action: Check to make sure the item is a navigable item.

Level: 20

Trigger: ON-ERROR

FRM-41091: Cannot find LOV: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_LOV will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41092: No records in block %s.

Cause: You attempted to place a value into an item on a block that has no records.

Action: Put records in the block first.

Level: 20

Trigger: ON-ERROR

FRM-41093: Error setting item property: %s.

Cause: You specified Lock Record and the item was not a text item, or you specify Case Insensitive Query and the data type was not ALPHA or CHAR.

Action: In the case of Lock Record, make sure that the item is a text item. When specifying Case Insensitive Query, make sure that the data type is ALPHA or CHAR.

Level: 20

Trigger: ON-ERROR

FRM-41094: No such property for Get_View_Property.

Cause: You attempted to get a non-existent view property.

Action: Verify call to GET_VIEW_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41095: No such property for Get_Canvas_Property.

Cause: You attempted to get a non-existent canvas property.

Action: Verify call to GET_CANVAS_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41096: Cannot resize View: invalid size.

Cause: The x, y coordinates place the view off the canvas.

Action: Choose another x, y pair.

Level: 99

Trigger: ON-ERROR

FRM-41097: Cannot resize Canvas: invalid size.

Cause: The x, y coordinates place the view off the window.

Action: Choose another x, y pair.

Level: 99

Trigger: ON-ERROR

FRM-41098: Cannot modify Display Position of a content view.

Cause: The Display Position Property applies to a stacked canvas-view only.

Action: Correct the call to SET_VIEW_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41099: Cannot modify Size of a content view.

Cause: The size of a content view is dependent on window size. Only stacked view sizes may be modified using SET_VIEW_PROPERTY.

Action: Correct the call to SET_VIEW_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41100: Cannot find relation %s.

Cause: You attempted to get, set, or find using an invalid relation.

Action: Check call to Built-in for correct arguments.

Level: 99

Trigger: ON-ERROR

FRM-41101: No such property for Get_Relation_Property.

Cause: You attempted to get a non-existent relation property.

Action: Verify call to GET_RELATION_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41102: No such property for Set_Relation_Property.

Cause: You attempted to set a non-existent relation property.

Action: Verify call to SET_RELATION_PROPERTY for valid property.

Level: 99

Trigger: ON-ERROR

FRM-41103: No such property value for Set_Relation_Property.

Cause: Application design error. Improper relation property value passed to SET_RELATION_PROPERTY Built-in.

Action: Correct call to SET_RELATION_PROPERTY Built-in and retry.

Level: 99

Trigger: ON-ERROR

FRM-41104: Cannot find Relation: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_RELATION will be performed.

Level: 20

Trigger: ON-ERROR

FRM-41105: You cannot query records without a saved parent record.

Cause: You attempted to query detail records without first creating a master record.

Action: Create a master record, and then query the detail records.

Level: 10

Trigger: ON-ERROR

FRM-41106: You cannot create records without a parent record.

Cause: You attempted to create new detail records without first creating a master record.

Action: Create a master record, and then add the detail records.

Level: 10

Trigger: ON-ERROR

FRM-41107: Master delete option for the relation is invalid.

Cause: An invalid query data source type or an invalid DML data target type is specified for the detail block.

Action: Verify that the detail block's query data source and the DML data targets are of type table.

Level: 99

Trigger: ON-ERROR

FRM-41200: Integration error: invalid product.

Cause: Invalid product name specified during integration.

Action: Check the integration parameters.

Level: 99

Trigger: ON-ERROR

FRM-41201: Integration error: communication mode must be SYNCHRONOUS or ASYNCHRONOUS.

Cause: Invalid communication mode specified in RUN_REPORT_OBJECT.

Action: Check the RUN_REPORT_OBJECT parameters and try again.

Level: 20

Trigger: ON-ERROR

FRM-41202: Integration error: parameter list %s has no parameters.

Cause: Parameter list has no arguments.

Action: Check the specified parameter list for parameters.

Level: 20

Trigger: ON-ERROR

FRM-41203: Integration error: invalid parameter list ID.

Cause: An invalid parameter list ID was passed.

Action: Check the parameter list ID name and try again.

Level: 20

Trigger: ON-ERROR

FRM-41204: Integration error: memory allocation error.

Cause: An internal error occurred.

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

Level: 20

Trigger: ON-ERROR

FRM-41208: Integration error: execution mode must be BATCH or RUNTIME.

Cause: Invalid execution mode specified in RUN_REPORT_OBJECT.

Action: Specify either BATCH or RUNTIME for the execmode parameter.

Level: 20

Trigger: ON-ERROR

FRM-41209: Integration error: document location must be FILESYSTEM or DB.

Cause: Invalid document location specified while integrating with another product.

Action: Specify either FILESYSTEM or DB for the location parameter.

Level: 20

Trigger: ON-ERROR

FRM-41211: Integration error: SSL failure running another product.

Cause: There is a problem detected when launching another product.

Action: Check the RUN_REPORT_OBJECT Built-in.

Level: 99

Trigger: ON-ERROR

FRM-41212: Integration error: invalid communication mode for data exchange

Cause: User specified an asynchronous RUN_REPORT_OBJECT.

Action: Change to a synchronous RUN_REPORT_OBJECT communication mode.

Level: 20

Trigger: ON-ERROR

FRM-41213: Unable to connect to the Report server %s.

Cause: There is a problem connecting to the specified Report server.

Action: Check the Report server and make sure it is up and running.

Level: 99

Trigger: ON-ERROR

FRM-41214: Unable to run report.

Cause: The report server was unable to run the specified report.

Action: Check the Report server and make sure it is up and running.

Level: 99

Trigger: ON-ERROR

FRM-41215: Invalid server name or jobid.

Cause: There is a problem decoding the return value from the Built-in run_report.

Action: The return value from the Built-in run_report should not be modified before being passed to another report Built-in.

Level: 99

Trigger: ON-ERROR

FRM-41216: Unable to cancel job.

Cause: There is a problem cancelling a report job.

Action: Check the Report server and make sure that the specified job exists.

Level: 99

Trigger: ON-ERROR

FRM-41217: Unable to get report job status.

Cause: There is a problem getting report status for a given report job.

Action: Check the Report server and make sure that the specified job exists.

Level: 99

Trigger: ON-ERROR

FRM-41218: Unable to copy report output.

Cause: There is a problem copying report output for a given report job.

Action: Check the Report server and make sure that the specified output file exists.

Level: 99

Trigger: ON-ERROR

FRM-41219: Cannot find report: invalid ID.

Cause: The user has specified an invalid report object name.

Action: Check the form and make sure that the report object exists.

Level: 99

Trigger: ON-ERROR

FRM-41220: Failed to authenticate user.

Cause: There was a failure in displaying the web report.

Action: Check if the user credentials are valid against identity store in use.

Level: 99

Trigger: ON-ERROR

FRM-41221: Failed to connect to identity store.

Cause: There was a failure in connecting to authentication service of identity store.

Action: Check if the authentication service is running.

Level: 99

Trigger: ON-ERROR

FRM-41222: Invalid property for this report object type.

Cause: There was a reports property mismatch.

Action: Make sure properties being handled belong to correct report object type. It is a property mismatch if a property belonging to reports object type 'ORAREPORTS' is being operated for reports object of type 'ORABIP' and vice versa.

Level: 99

Trigger: ON-ERROR

FRM-41223: BI Publisher integration error.

Cause: There was an error while invoking BI Publisher.

Action: Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41224: Invalid BI Publisher service location.

Cause: You specified an invalid value for service location.

Action: Make sure value of service location property is complete.

Level: 99

Trigger: ON-ERROR

FRM-41225: SSL mandatory but service location non-SSL.

Cause: A non-SSL service location was specified when SSL Connection property set to mandatory.

Action: Make sure an SSL service location is specified when SSL Connection configured. Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41226: Access denied on BI Publisher server.

Cause: You do not have authority to access BI Publisher server.

Action: Make sure correct BI Publisher user name and password specified. Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41227: Invalid parameter reported by BI Publisher.

Cause: BI Publisher call caused InvalidParametersException.

Action: Make sure all of the report properties are valid.

Level: 99

Trigger: ON-ERROR

FRM-41228: Operation failed at BI Publisher server.

Cause: There was an error on BI Publisher server when executing the operation.

Action: Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41229: Output file name missing.

Cause: No file name was specified when calling operation to copy report output.

Action: Make sure a valid file name is specified for the operatin to copy report output.

Level: 99

Trigger: ON-ERROR

FRM-41230: File Not Found Exception.

Cause: FileNotFoundException thrown when trying to copy report output.

Action: Make sure you have file creation priviledge for the file name provided. Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41231: Failed to write report output.

Cause: IOException thrown when trying to write report output.

Action: Check your write priviledge and space on the disk. Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41232: Failed to initialize JVM.

Cause: Unable to initialize JVM required to invoke BI Publisher call.

Action: Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41300: Invalid parameter used for Set_Radio_Button_Property.

Cause: You specified a parameter that does not exist.

Action: Check the list of legal parameters.

Level: 99

Trigger: ON-ERROR

FRM-41301: Invalid parameter used for Set_View_Property.

Cause: You specified a parameter that does not exist.

Action: Check the list of legal parameters.

Level: 99

Trigger: ON-ERROR

FRM-41302: Invalid parameter used for Set_Canvas_Property.

Cause: You specified a parameter that does not exist.

Action: Check the list of legal parameters.

Level: 99

Trigger: ON-ERROR

FRM-41303: No such property for Set_Window_Property.

Cause: You specified a property that does not exist.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41304: No such property for Set_Block_Property.

Cause: You specified a property that does not exist.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41305: No such property for Get_Block_Property.

Cause: You specified a property that does not exist.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41306: Invalid parameter used for Set_Window_Property.

Cause: You specified a parameter that is not valid.

Action: Check the list of valid parameters.

Level: 99

Trigger: ON-ERROR

FRM-41307: Invalid parameter used for Set_Block_Property.

Cause: You specified a parameter that is not valid.

Action: Check the list of valid parameters.

Level: 99

Trigger: ON-ERROR

FRM-41308: Error unsetting Group selection.

Cause: You tried to deselect a record or a subset of records that was not selected or is not in the record group.

Action: Check the records that are expected in the group.

Level: 20

Trigger: ON-ERROR

FRM-41309: No such property for Get_Radio_Button_Property.

Cause: You specified a property that is invalid.

Action: Check the list of valid properties.

Level: 99

Trigger: ON-ERROR

FRM-41310: No such property for Set_Radio_Button_Property.

Cause: You specified a property that is invalid.

Action: Check the list of valid properties.

Level: 99

Trigger: ON-ERROR

FRM-41311: Invalid argument or argument ordering for %s.

Cause: You supplied an incorrect argument list.

Action: Check the list of valid arguments.

Level: 99

Trigger: ON-ERROR

FRM-41312: Must have at least one writable item in block.

Cause: A block with the Insert Allowed Property or Update Allowed Property set to True must have at least one writable item. You attempted to make the only remaining base table item in the block not writable by setting either the Derived Column Property or Query Only Property to True.

Action: Set Insert Allowed or Update Allowed to False for the block, rather than setting Derived Column or Query Allowed to False for each item.

Level: 10

Trigger: ON-ERROR

FRM-41313: No such property for Set_Alert_Property.

Cause: An invalid property has been specified for SET_ALERT_PROPERTY.

Action: Enter a valid alert property.

Level: 99

Trigger: ON-ERROR

FRM-41314: Cannot set Insert Allowed Property of current item %s.%s

Cause: You attempted to set the Insert Allowed Property for a current item.

Action: The Insert Allowed Property is only valid on non-current items. Make sure the item is not current.

Level: 99

Trigger: ON-ERROR

FRM-41315: Cannot set Insert Allowed Property of non-displayed item %s.%s

Cause: You tried to set Insert Allowed Property for a non-displayed item.

Action: The Insert Allowed Property is only valid on displayed items. Make sure the item is displayed.

Level: 99

Trigger: ON-ERROR

FRM-41316: Cannot set Insert Allowed Property of disabled item %s.%s

Cause: You tried to set Insert Allowed Property for a disabled item.

Action: The Insert Allowed Property is only valid on enabled items. Make sure the item is enabled.

Level: 99

Trigger: ON-ERROR

FRM-41317: Item is not a radio button %s

Cause: You tried to use a radio button Built-in with an item that is not a radio button.

Action: Make sure the item is a radio button.

Level: 99

Trigger: ON-ERROR

FRM-41318: Item %s is not a VBX item.

Cause: You tried to use a VBX Built-in with an item that is not a VBX item.

Action: Make sure the item is a VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41319: Invalid property %s specified for VBX item %s.

Cause: You tried to get or set an invalid property for the specified VBX item.

Action: Make sure the property is valid for the specified VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41320: Unable to get property %s for VBX item %s.

Cause: Could not get the valid property for the VBX item.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41321: Unable to set property %s for VBX item %s.

Cause: Could not set the valid property for the VBX item.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41322: Invalid event %s for VBX item %s.

Cause: You tried to get or set an invalid event for the specified VBX item.

Action: Make sure the event is valid for the specified VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41323: Too many parameters for event %s for VBX item %s.

Cause: You specified too many parameters for the event name for the VBX item.

Action: Make sure there is a valid number of parameters for the event.

Level: 99

Trigger: ON-ERROR

FRM-41324: Too few parameters for event %s for VBX item %s.

Cause: You specified too few parameters for the event name for the VBX item.

Action: Make sure there is a valid number of parameters for the event.

Level: 99

Trigger: ON-ERROR

FRM-41325: VBX event parameter must be a string.

Cause: The VBX event parameter is not a string.

Action: Make sure the VBX event parameter is a string.

Level: 99

Trigger: ON-ERROR

FRM-41326: Failed to deliver event %s to VBX item %s.

Cause: The VBX event failed.

Action: Make sure the event is valid for the specified VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41327: Failed to get default property for VBX item %s.

Cause: The VBX.GET_VALUE_PROPERTY Built-in failed.

Action: Make sure an initial value is assigned to the VB Control Value property.

Level: 99

Trigger: ON-ERROR

FRM-41328: Failed to set default property for VBX item %s.

Cause: The VBX.SET_VALUE_PROPERTY Built-in failed.

Action: Make sure you are setting a valid value property.

Level: 99

Trigger: ON-ERROR

FRM-41329: Item %s is not a List item.

Cause: You tried to add a list element to an item that is not a list.

Action: Make sure the item is a List item.

Level: 99

Trigger: ON-ERROR

FRM-41330: Could not insert list element into %s.

Cause: You tried to insert an other values element when the block contained either queried or changed records.

Action: For more information, refer to help for restrictions on <a href="../builta_c/addliste.html">ADD_LIST_ELEMENT Built-in</a>.

Level: 99

Trigger: ON-ERROR

FRM-41331: Could not delete element from %s.

Cause: Caused by one of the following:

You tried to delete the other values element when the block contained either queried or changed records.

You tried to delete an element from a list that does not contain an other values element when the block contained either queried or changed records.

Action: For more information, refer to help for restrictions on <a href="../builta_c/clearlis.html">CLEAR_LIST</a> and <a href="../builtd_f/dellsele.html">DELETE_LIST_ELEMENT</a>.

Level: 99

Trigger: ON-ERROR

FRM-41332: List element index out of range.

Cause: An invalid index (e.g. a negative number) was specified to the Add_List_Element Built-in.

Action: Correct the index in the call to Add_List_Element.

Level: 99

Trigger: ON-ERROR

FRM-41333: Cannot convert list element value.

Cause: Could not resolve list element value to a string.

Action: Make sure list element is a string.

Level: 99

Trigger: ON-ERROR

FRM-41334: Invalid record group for list population.

Cause: You tried to populate a list from a record group that does not exist.

Action: Make sure the record group exists.

Level: 99

Trigger: ON-ERROR

FRM-41335: Populate_List: invalid column type for column 1.

Cause: The record group does not have a column of the same type.

Action: Make sure record group has a column of the same type.

Level: 99

Trigger: ON-ERROR

FRM-41336: Populate_List: invalid column type for column 2.

Cause: The record group does not have a column of the same type.

Action: Make sure record group has a column of the same type.

Level: 99

Trigger: ON-ERROR

FRM-41337: Cannot populate the list from record group.

Cause: The record group is invalid or the list item does not satisfy the requirements for deleting and adding elements.

Action: Make sure the record group is valid. For more information about deleting and adding list elements, refer to help for restrictions on <a href="../builtd_f/dellsele.html">DELETE_LIST_ELEMENT</a> and <a href="../builta_c/addliste.html">ADD_LIST_ELEMENT</a>.

Level: 99

Trigger: ON-ERROR

FRM-41338: Cannot retrieve the list into record group.

Cause: The record group is invalid.

Action: Make sure the record group is valid.

Level: 99

Trigger: ON-ERROR

FRM-41339: Cannot clear the list.

Cause: A memory allocation failed when Forms Runtime attempted to clear a list.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-41340: No such property or value for Set_Application_Property.

Cause: You specified an invalid property and/or an invalid value for a property.

Action: Specify a valid property and/or a valid value.

Level: 99

Trigger: ON-ERROR

FRM-41341: Invalid cursor shape %s specified.

Cause: There is a predefined set of cursor types, and an invalid cursor type was specified.

Action: Specify a valid cursor type.

Level: 99

Trigger: ON-ERROR

FRM-41342: Invalid parameter %s specified for VBX event %s.

Cause: You specified an invalid parameter for a VBX event.

Action: Check the parameter type.

Level: 99

Trigger: ON-ERROR

FRM-41343: Item %s is not an OLE object.

Cause: Invalid item passed to OLE Built-in.

Action: Specify a valid OLE item.

Level: 99

Trigger: ON-ERROR

FRM-41344: OLE object not defined for %s in the current record.

Cause: An empty OLE container is defined.

Action: Define an OLE object to reside in the OLE container.

Level: 20

Trigger: ON-ERROR

FRM-41345: Cannot find the verb %s for this server.

Cause: You specified an invalid OLE verb.

Action: Specify a valid OLE verb.

Level: 99

Trigger: ON-ERROR

FRM-41346: Cannot determine the verb count for OLE object %s.

Cause: Could not communicate with OLE server.

Action: Re-install the OLE server.

Level: 99

Trigger: ON-ERROR

FRM-41347: Invalid verb index for OLE object %s.

Cause: You provided an index that is greater than the verb count.

Action: Check the index value.

Level: 99

Trigger: ON-ERROR

FRM-41348: OLE server error: %s.

Cause: OLE server detects an error.

Action: Try to resolve the error based on the message from the OLE server.

Level: 99

Trigger: ON-ERROR

FRM-41349: OLE object %s cannot execute verb; verb id %d

Cause: OLE object does not recognize the verb.

Action: Try to execute another verb.

Level: 99

Trigger: ON-ERROR

FRM-41350: OLE object is currently not displayed.

Cause: You tried to close a server that is not running.

Action: Ask if the server is active in a record that is not currently active.

Level: 99

Trigger: ON-ERROR

FRM-41351: Cannot navigate out of current form.

Cause: You cannot navigate to an inactive form.

Action: Check to make sure the form you are navigating to is active.

Level: 99

Trigger: ON-ERROR

FRM-41352: Failed to create a new session.

Cause: You attempted to open a new form with a new session.

Action: Check the database server.

Level: 99

Trigger: ON-ERROR

FRM-41353: Cannot start another call form.

Cause: You went to a peer form and performed a call form.

Action: Make sure you are not at a peer form when calling the form.

Level: 99

Trigger: ON-ERROR

FRM-41354: Cannot close form %s.

Cause: Unsuccessful attempt to close a form.

Action: Make sure the form is open.

Level: 99

Trigger: ON-ERROR

FRM-41355: Cannot navigate to form %s.

Cause: You cannot navigate to an inactive form.

Action: Check to make sure you are navigating to an active form.

Level: 99

Trigger: ON-ERROR

FRM-41356: Invalid method %s for VBX item %s.

Cause: You specified an invalid method name for the VBX item.

Action: Specify a valid method name for the VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41357: Incorrect number of arguments to method %s for VBX item %s.

Cause: You specified an incorrect number of arguments to the method for the VBX item.

Action: Make sure the number of arguments is what the VBX item expects.

Level: 99

Trigger: ON-ERROR

FRM-41358: Method %s failed for VBX item %s.

Cause: You specified an invalid method name for the VBX item.

Action: Specify a valid method name for the VBX item.

Level: 99

Trigger: ON-ERROR

FRM-41359: The Open_Form session feature is not enabled. Cannot create new session.

Cause: You do not have the multiple sessioning feature enabled on the database.

Action: The Open_Form session feature is only available for use against a database with multiple sessioning enabled.

Level: 99

Trigger: ON-ERROR

FRM-41360: Invalid value used in Set_Window_Property for window %s.

Cause: You are using an invalid value when attempting to set a window property.

Action: Specify a valid window property value.

Level: 99

Trigger: ON-ERROR

FRM-41361: Cannot navigate out of current form in Enter-Query mode.

Cause: You are in Enter-Query mode and trying to navigate to another form when using Open Form.

Action: Exit Enter-Query mode and try again.

Level: 10

Trigger: ON-ERROR

FRM-41362: No such property for Set_Alert_Button_Property.

Cause: You specified an invalid property for Set_Alert_Button_Property.

Action: Specify a valid property for Set_Alert_Button_Property.

Level: 99

Trigger: ON-ERROR

FRM-41363: No such property for Set_LOV_Column_Property.

Cause: You specified an invalid property for Set_LOV_Column_Property.

Action: Specify a valid property for Set_LOV_Column_Property.

Level: 99

Trigger: ON-ERROR

FRM-41364: Invalid column number specified for LOV %s.

Cause: You specified an invalid column number for the LOV.

Action: Specify a valid column number for the LOV.

Level: 99

Trigger: ON-ERROR

FRM-41365: No such property for Set_TabPage_Property.

Cause: You specified an invalid property for Set_TabPage_Property.

Action: Specify a valid property for Set_TabPage_Property.

Level: 99

Trigger: ON-ERROR

FRM-41366: No such property for Get_TabPage_Property.

Cause: You specified an invalid property parameter.

Action: Check the list of valid properties.

Level: 99

Trigger: ON-ERROR

FRM-41367: Cannot find TabPage: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to FIND_TABPAGE will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41368: Invalid parameter used for Set_TabPage_Property.

Cause: You specified a parameter that is not valid.

Action: Check the list of valid parameters.

Level: 99

Trigger: ON-ERROR

FRM-41369: Cannot insert a second record into a single-record block.

Cause: You (or the application) have attempted to insert a second record into a block whose Single Record Property is TRUE.

Action: Don't attempt to insert a record into such a block.

Level: 99

Trigger: ON-ERROR

FRM-41370: Cannot modify calculated item %s.%s.

Cause: Application design error. The application attempted to assign a value to a calculated item.

Action: If the calculated item is a formula item, then its formula determines its value at all times. It may be appropriate to modify the formula. Or it may be appropriate to change the calculated item to a non-calculated control item whose value is set in various triggers.

Level: 99

Trigger: ON-ERROR

FRM-41371: Cannot set INSERT_ALLOWED Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in attempted to set a calculated item's INSERT_ALLOWED Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41372: Cannot set ITEM_IS_VALID Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in attempted to set a calculated item's ITEM_IS_VALID Property to FALSE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41373: Cannot set LOCK_RECORD Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in attempted to set a calculated item's LOCK_RECORD Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41374: Cannot set PRIMARY_KEY Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in attempted to set a calculated item's PRIMARY_KEY Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41375: Cannot set QUERYABLE Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in attempted to set a calculated item's QUERYABLE Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41376: Cannot set REQUIRED Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in attempted to set a calculated item's REQUIRED Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41377: Cannot set UPDATEABLE Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in attempted to set a calculated item's UPDATEABLE Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41378: Cannot set UPDATE_NULL Property of calculated item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY Built-in attempted to set a calculated item's UPDATE_NULL Property to TRUE.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41379: Cannot recalculate non-formula item %s.%s.

Cause: Application design error. A RECALCULATE Built-in specified an item which is not a formula item.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41380: Cannot set the blocks query data source.

Cause: The user attempt to change the block's data source dynamically has failed.

Action: Check the form and make sure that the specified block is not a control block and the block status is new.

Level: 99

Trigger: ON-ERROR

FRM-41381: Cannot set the blocks DML data target source.

Cause: The user attempt to change the block's DML data target dynamically has failed.

Action: Check the form and make sure that the specified block is not a control block and the block status is new.

Level: 99

Trigger: ON-ERROR

FRM-41382: No such property for Get_Item_Instance_Property.

Cause: Application design error. A GET_ITEM_INSTANCE_PROPERTY Built-in specified an invalid property.

Action: Change the property to one that is documented as supported by the built-in, or else remove the call to the built-in.

Level: 99

Trigger: ON-ERROR

FRM-41383: No such property for Set_Item_Instance_Property.

Cause: Application design error. A SET_ITEM_INSTANCE_PROPERTY Built-in specified an invalid property.

Action: Change the property to one that is documented as supported by the built-in, or else remove the call to the built-in.

Level: 99

Trigger: ON-ERROR

FRM-41384: Invalid parameter used for Set_Item_Instance_Property.

Cause: Application design error. A SET_ITEM_INSTANCE_PROPERTY Built-in specified an invalid value for a property.

Action: Modify or remove the call to the built-in.

Level: 99

Trigger: ON-ERROR

FRM-41385: Maximum number of queried records exceeded.

Cause: The user specified maximum number of records for a given block is reached.

Action: Check the forms block and form level properties.

Level: 99

Trigger: ON-ERROR

FRM-41386: Cannot set VISIBLE Property of tab page containing current item.

Cause: You tried to set the Visible Property for the tab page which contains the current item.

Action: The Visible Property is only valid for tab pages which don't contain the current item.

Navigate to an item on a different tab page or different canvas first.

Level: 99

Trigger: ON-ERROR

FRM-41387: Cannot set VISIBLE Property of last enterable tab page.

Cause: You tried to set the Visible Property for the only enterable tab page on the canvas.

Action: Make sure there is at least one other enterable tab page on the canvas before trying to set the Visible Property.

Level: 99

Trigger: ON-ERROR

FRM-41388: Cannot set ENABLED Property of tab page containing current item.

Cause: You tried to set the Enabled Property for the tab page which contains the current item.

Action: The property is only valid for tab pages which don't contain the current item.

Navigate to an item on a different tab page or different canvas first.

Level: 99

Trigger: ON-ERROR

FRM-41389: Cannot set ENABLED Property of last enterable tab page.

Cause: You tried to set the Enabled Property for the only enterable tab page on the canvas.

Action: Make sure there is at least one other enterable tab page on the canvas before trying to set the Enabled Property.

Level: 99

Trigger: ON-ERROR

FRM-41390: Cannot set REQUIRED Property of subordinate mirror item %s.%s.

Cause: Application design error. A SET_ITEM_PROPERTY or SET_ITEM_INSTANCE_PROPERTY Built-in attempted to set the Required Property of a subordinate mirror item. The Required Property will be obtained from the master mirror item (the item specified by the Synchronize With Item Property).

Action: Set the Required Property of the master mirror item.

Level: 25

Trigger: ON-ERROR

FRM-41391: Cannot find visual attribute: invalid ID.

Cause: An invalid ID was passed to a Built-in subprogram.

Action: Verify that a proper call to Find_VA will be performed.

Level: 99

Trigger: ON-ERROR

FRM-41392: No such property for Get_VA_Property.

Cause: You attempted to get a non-existent visual attribute property.

Action: Verify call to Get_VA_Property for a valid property.

Level: 99

Trigger: ON-ERROR

FRM-41393: No such property for Set_VA_Property.

Cause: You attempted to set an invalid visual attribute property.

Action: Check the documentation for setting visual attribute properties and try again.

Level: 99

Trigger: ON-ERROR

FRM-41394: Invalid parameter value used for Set_VA_Property.

Cause: You attempted to set an invalid value for a visual attribute property.

Action: Check the documentation for setting visual attribute properties and try again.

Level: 99

Trigger: ON-ERROR

FRM-41395: Invalid parameter used for Set_Report_Object_Property.

Cause: You specified a parameter that does not exist.

Action: Check the list of legal parameters.

Level: 99

Trigger: ON-ERROR

FRM-41396: No such property for Get/Set_Report_Object_Property.

Cause: You specified a property that does not exist.

Action: Check the list of legal properties.

Level: 99

Trigger: ON-ERROR

FRM-41397: Invalid parameter used for MESSAGE.

Cause: Application design error. A MESSAGE Built-in specified an invalid option. The option must be one of ACKNOWLEDGE, NO_ACKNOWLEDGE, RUEI_BEGIN, RUEI_END, ODL_DEBUG, ODL_NOTIFICATION, ODL_WARNING, or ODL_ERROR.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-41402: Invalid type of visual attribute passed to Set_<object>_Property.

Cause: You attempted to set an object's visual attribute to a VA of the wrong type.

Action: Verify VA types in the Builder and specify a valid VA for this object.

Level: 99

Trigger: ON-ERROR

FRM-41403: Cannot set DEFAULT_WHERE: invalid value.

Cause: The user attempted to set the DEFAULT_WHERE to an invalid value.

Action: Check the value you chose in your call to SET_BLOCK_PROPERTY is valid.

Level: 99

Trigger: ON-ERROR

FRM-41411: SELECTED_RADIO_BUTTON property allowed only on a radio group.

Cause: The user attempted to obtain the SELECTED_RADIO_BUTTON property for an item which is not a radio group.

Action: Check the value that was specified for the item.

Level: 99

Trigger: ON-ERROR

FRM-41412: Cannot set scrollbar position for specified block.

Cause: The user attempted to set a scrollbar position property for a block which has no scrollbar.

Action: Check the value that was specified for the block.

Level: 99

Trigger: ON-ERROR

FRM-41413: Cannot get scrollbar position for specified block.

Cause: The user attempted to get a scrollbar position property for a block which has no scrollbar.

Action: Check the value that was specified for the block.

Level: 99

Trigger: ON-ERROR

FRM-41414: Combo box item element %s is longer than Maximum Length.

Cause: The label for combo box item element %s is longer than Maximum Length.

Action: Reduce the number of characters in the element's label.

Level: 99

Trigger: ON-ERROR

FRM-41415: Cannot set record distance: position of item places it off of canvas.

Cause: The record distance you specified in your call to SET_ITEM_PROPERTY is invalid, or the record distance you specified causes the item to extend off of the canvas.

Action: Correct the call to SET_ITEM_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-41416: No credentials provided. Application running in suppress logon mode.

Cause: Forms is exiting as no credentials are provided and the application is running in suppress logon mode.

Action: Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-41417: Block QRCN support not available - QRCN turned off.

Cause: The underlying block query failed the QRCN subscription registration.

Action: Check the underlying query table for the cause. Too many columns in the query, unsupported column type, or GUARANTEED mode could not be supported for the QRCN Subscription Mode (try Best Effort if possible).

Level: 99

Trigger: ON-ERROR

FRM-41418: invalid record group column type

Cause: A record group column of an invalid type was passed to a record group builtin, or was encountered in a record group passed to a record group builtin. In the case where the builtin is POPULATE_GROUP_FROM_JSON, no column in the passed-in record group may be of type REF, and if the passed-in JSON collection is a JSON object, the first column in the record group must be of type CHAR, LONG, or NUM.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41419: attempted update to nonempty static record group

Cause: An attempt was made to programmatically update a nonempty static record group at run time.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41420: CURRENT_RECORD not valid when setting ROW_VISUAL_ATTRIBUTE.

Cause: The CURRENT_RECORD constant is not valid to be used in Set_Item_Instance_Property when setting the ROW_VISUAL_ATTIBUTE.

Action: Correct the application logic by explicitly specifying the desired row number or by using :SYSTEM.CURSOR_ROW.

Level: 99

Trigger: ON-ERROR

FRM-41421: Invalid row %d for item %s.%s.

Cause: You attempted to set the row visual attribute for an invalid row number for the given item.

Action: Verify your Set_Item_Instance_Property parameters.

Level: 20

Trigger: ON-ERROR

FRM-41422: Unsupported sort column datatype for item %s.%s.

Cause: An attempt was made to sort a block item with a datatype which is not supported.

Action: Sort column can only be of type char, number, or date.

Level: 99

Trigger: ON-ERROR

FRM-41423: Inadequate memory to sort column.

Cause: An attempt to sort column data failed because of inadequate system memory.

Action: Check system memory and insure it's adequate for running the application.

Level: 99

Trigger: ON-ERROR

FRM-41424: Unsupported Filter Summary column datatype for item %s.%s.

Cause: Attempt to perform a Filter Summary on a block item with a datatype which is not supported.

Action: Filter Summary column can only be of type CHAR, NUMBER,or DATE.

Level: 99

Trigger: None

FRM-41425: Inadequate memory for Filter Summary column.

Cause: Attempt to Filter Summary column data failed because of inadequate system memory.

Action: Check system memory and insure it's adequate for running the application.

Level: 99

Trigger: None

FRM-41426: Unable to add column for Filter Summary creation to design-time record group %s.

Cause: Filter Summary failed due to a design-time record group being specified.

Action: Make sure record group for the Filter Summary is updateable at runtime.

Level: 99

Trigger: None

FRM-41427: Record group %s column mismatch for Filter Summary item.

Cause: The Filter Summary record group columns do not match the required types.

Action: Make sure the record group has the correct types matching the Filter Summary item and a number count column.

Level: 99

Trigger: None

FRM-41428: Inadequate number of columns in record group %s for the Filter Summary item.

Cause: The Filter Summary record group contains less than two columns.

Action: Make sure the record group has the correct number of coumns.

Level: 99

Trigger: None

FRM-41429: Warning - Possible truncation when adding Filter Summary results to record group %s.

Cause: Attempt to add a row from Filter Summary result to the record group may result in truncation.

Action: Make sure the record group columns are large enough to house the Filter Summary result values.

Level: 99

Trigger: None

FRM-41430: Filter Summary record group %s Count column is of wrong type.

Cause: Invalid column type for the Filter Summary's record group Count column.

Action: Record group Count column can only be of type NUMBER.

Level: 99

Trigger: None

FRM-41431: Filter Summary results failed to be added to record group %s.

Cause: Attempt to add a row from the Filter Summary result to the record group failed.

Action: Check that the record group can hold all the column values.

Level: 99

Trigger: None

FRM-41472: scratchpad memory allocation failed

Cause: An FSCRATCHPAD operation was unable to allocate adequate memory. An FSCRATCHPAD.ALLOCATION exception was raised.

Action: Modify application logic so as to limit the amount of data written to the scratchpad.

Level: 99

Trigger: ON-ERROR

FRM-41480: invalid 'uri_template' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE

Cause: The 'uri_template' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE must specify a syntactically correct URI template [RFC 6570, level 4]. A more specific FRM-41480 message is written to ODL.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41484: invalid 'parameters' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE

Cause: (a) The 'parameters' parameter passed to FSCRATCHPAD.EXPAND_TEMPLATE must specify null or a JSON object element; (b) the object's child values must be strings, arrays of strings, or objects whose child values are strings or arrays of strings; (c) where the URI template allows strings to contain %-encodings, such encodings must be valid. For violations of (b) and (c), a more specific FRM-41484, FRM-41486, or FRM-41487 message is written to ODL.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41490: invalid charset specified for scratchpad file operation

Cause: The 'charset' parameter passed to FSCRATCHPAD.APPEND_FILE or FSCRATCHPAD.TO_FILE was invalid. It must be a valid Oracle Database character set name or else 'NLS_LANG', which indicates the Oracle Database character set name that was specified in the NLS_LANG environment variable.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41491: conflicting parameters: charset and base64 both specified for scratchpad file operation

Cause: FSCRATCHPAD.APPEND_FILE or FSCRATCHPAD.TO_FILE was passed both a non-null 'charset' parameter and a 'base64_encode' or 'base64_decode' parameter with a value of true. Charset conversion is appropriate only for character files and base64 encoding or decoding is appropriate only for binary files.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41492: scratchpad contents not a valid base64 encoding

Cause: 'base64_decode := true' was specified for FSCRATCHPAD.TO_FILE, but the scratchpad contents (up to the string specified by the 'stop_at' parameter, if specified) did not constitute a valid base64 encoding. A valid base64 encoding must contain only white space [blank, tab, carriage return, or line feed] or base64 alphabet characters ['A'-'Z', 'a'-'z', '0'-'9', '+', '/', or '=']. '=' characters are not required, but if present, they must occur only at the end, and they must ensure that the total number of base64 alphabet characters is a multiple of 4. Information that may help diagnose the issue was written to ODL.

Action: Correct application logic that populates the scratchpad.

Level: 99

Trigger: ON-ERROR

FRM-41493: Scratchpad contents could not be written.

Cause: FSCRATCHPAD.TO_FILE was unable to successfully write the scratchpad contents to the location specified by the 'file_name' parameter. The FRM-41493 message written to ODL specifies the full name of the file.

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

Level: 99

Trigger: ON-ERROR

FRM-41494: File could not be read into scratchpad.

Cause: The 'file_name' parameter passed to FSCRATCHPAD.APPEND_FILE specified a file that could not be found or could not be read. The FRM-41494 or FRM-41495 message written to ODL specifies the full name of the file.

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

Level: 99

Trigger: ON-ERROR

FRM-41500: invalid FJSON.ELEMENT_T value

Cause: Application design error. A value that was passed to a function or procedure in the FJSON, FHTTP, or FSCRATCHPAD package, that was expecting an FJSON.ELEMENT_T value, either was not in fact an FJSON.ELEMENT_T value or else specified an element that did not currently exist in a JSON parse tree. An FJSON.BAD_ARGUMENT exception was raised.

Action: Ensure that the value is of type FJSON.ELEMENT_T and that FJSON.FREE_ALL was not called after the element was created.

Level: 99

Trigger: ON-ERROR

FRM-41501: Target element of specified JSON operation cannot be null.

Cause: Application design error. A null FJSON.ELEMENT_T value was passed as the first parameter to a function or procedure in the FJSON or FHTTP package which requires a target element. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41502: Element value for a JSON array cannot be null.

Cause: Application design error. A null FJSON.ELEMENT_T value was passed as the last parameter to the FJSON.ADD or FJSON.SET procedure. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41503: BOOLEAN value used to construct a JSON boolean element cannot be null.

Cause: Application design error. A null BOOLEAN value was passed as the last (or only) parameter to the FJSON.NEW_BOOLEAN function, or to the FJSON.ADD_BOOLEAN, FJSON.SET_BOOLEAN, or FJSON.PUT_BOOLEAN procedure. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41504: NUMBER value used to construct a JSON number element cannot be null.

Cause: Application design error. A null NUMBER value was passed as the last (or only) parameter to the FJSON.NEW_NUMBER function, or to the FJSON.ADD_NUMBER, FJSON.SET_NUMBER, or FJSON.PUT_NUMBER procedure. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41505: NUMBER value used to construct a JSON number element cannot be infinity.

Cause: Application design error. A NUMBER value of infinity was passed as the last (or only) parameter to the FJSON.NEW_NUMBER function, or to the FJSON.ADD_NUMBER, FJSON.SET_NUMBER, or FJSON.PUT_NUMBER procedure. RFC 8259 does not allow a JSON number that represents infinity. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41506: 'expected_num_elements' parameter to FJSON.NEW_OBJECT function cannot be null.

Cause: Application design error. A null expected_num_elements parameter was passed to the FJSON.NEW_OBJECT function. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41507: 'expected_num_elements' parameter to FJSON.NEW_OBJECT function cannot be negative.

Cause: Application design error. A negative expected_num_elements parameter was passed to the FJSON.NEW_OBJECT function. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41508: invalid sort option(s) passed to FJSON.SORT_NUMBERS or FJSON.SORT_STRINGS

Cause: Application design error. The sort option(s) passed to the FJSON.SORT_NUMBERS and FJSON.SORT_STRINGS functions must be ASCENDING, DESCENDING, NULLS_LAST, NULLS_FIRST, CASE_SENSITIVE, CASE_INSENSITIVE, BINARY_ORDER, or LINGUISTIC_ORDER. Duplicate or contradictory options are not allowed. The last 4 are not allowed for FJSON.SORT_NUMBERS. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41510: JSON array position cannot be null.

Cause: Application design error. A null array position was passed as the second parameter to the FJSON.FIND function, or to the FJSON.ADD, FJSON.SET, or FJSON.REMOVE procedure. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41511: invalid JSON array position

Cause: Application design error. The array position passed as the second parameter to the FJSON.FIND function, or to the FJSON.ADD, FJSON.SET, or FJSON.REMOVE procedure, was negative, zero, or too large. An FJSON.BAD_ARGUMENT exception was raised. For FJSON.SET and FJSON.REMOVE, the array position must be no greater than the number of elements in the array. For FJSON.ADD, the array position may be equal to one more than the number of elements in the array, but no greater. For FJSON.FIND, any positive value is acceptable. If the specified element does not exist, FJSON.FIND will quietly return null.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41512: Element value for a JSON array resides in the same array.

Cause: Application design error. An FJSON.ELEMENT_T value that was passed as the third parameter to the FJSON.ADD or FJSON.SET procedure was already an element of the JSON array that was passed as the first parameter. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic. If you want to move an element of an array from one position to another (thereby reordering the elements of the array), it is recommended that you:

1. Use FJSON.FIND to obtain the element to be moved.

2. Use FJSON.REMOVE_FROM_PARENT to remove it from the array. For best performance, this should if possible be done immediately after step 1 [or at any rate before doing any subsequent FJSON.FIND on the same array].

3. Use FJSON.ADD to insert it at the desired new position.

Level: 99

Trigger: ON-ERROR

FRM-41513: too many elements in JSON array or object

Cause: Application design error. An invocation of the FJSON.ADD or FJSON.PUT procedure would have caused the number of elements in a JSON array or object to equal 2G. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41514: invalid JSON object key

Cause: Application design or configuration error. The object key passed as the second parameter to the FJSON.PUT or FJSON.REMOVE_PROPERTY procedure was too large. An FJSON.BAD_ARGUMENT exception was raised. By default, the AL32UTF8 representation of an object key must not exceed 32767 bytes. Note that an object key whose NLS_LANG charset representation does not exceed 32767 bytes could exceed 32767 bytes when converted to AL32UTF8.

Action: If there is a requirement to create REST endpoint request bodies that contain object keys larger than 32767 bytes, the FORMS_JSON_KEY_LENGTH_BITS environment variable [which defaults to 15] can be set to a value N in the range 16..30. This will allow keys of any size less than 2 raised to the power of N. The tradeoff is that the total number of bytes required for all strings, numbers, and hash arrays for all elements in all JSON parse trees must not exceed 2 raised to the power of 64-N. Also bear in mind that keys larger than 32767 bytes [in the NLS_LANG charset] cannot be used in PL/SQL VARCHAR2 variables.

Level: 99

Trigger: ON-ERROR

FRM-41515: syntax error in application-created JSON text

Cause: A parse of the JSON text that was passed to the errpos-omitted flavor of FJSON.PARSE encountered a violation of RFC 7159. The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41516: loop in JSON parse tree

Cause: Application design error. An FJSON.CLONE, FJSON.GENERATE, or FHTTP.ISSUE_REQUEST detected a loop in a JSON parse tree [so it wasn't really a tree at all]: the target element passed to FJSON.CLONE or FJSON.GENERATE, or the request_body element passed to FHTTP.ISSUE_REQUEST, was encountered while traversing its descendent elements. The FJSON.CLONE, FJSON.GENERATE, or FHTTP.ISSUE_REQUEST was aborted and the memory it consumed was released. An FJSON.BAD_ARGUMENT or FHTTP.BAD_ARGUMENT exception was raised. This condition was caused by an earlier call to FJSON.ADD, FJSON.SET, or FJSON.PUT that added a child element C to an array or object A, where C was equal to A or was an ancestor of A.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41520: application-created element of incorrect type specified as target of JSON operation

Cause: Application design error. An FJSON.ELEMENT_T value passed as the first parameter to a function or procedure in the FJSON package, or as the second parameter to the POPULATE_GROUP_FROM_JSON procedure, specified an element whose element type is not supported by the specified function or procedure, and the element was programmatically created by the application. An FJSON.BAD_ARGUMENT exception was raised (except for POPULATE_GROUP_FROM_JSON).

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41521: application-created element of unexpected type or value found in JSON array or object

Cause: Application design error. One of the following occurred:

1. An FJSON.FIND_x or FJSON.GET_x function produced an element of an unexpected type that was programmatically created by the application.

2. The JSON array passed as the first parameter to the FJSON.JOIN function contained an element that was not a JSON string, and the element was programmatically created by the application.

3. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained an initial element that was a JSON object, but also contained an element that was not a JSON object, and that element was programmatically created by the application.

4. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained an initial element that was a JSON array or scalar element, but also contained an element that was a JSON object, and that element was programmatically created by the application.

5. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a scalar element, or a JSON array or JSON object that in turn contained a scalar element, and the type of the scalar element did not match the corresponding record group column. [DATE columns are a special case: if a null epoch_unit was passed to POPULATE_GROUP_FROM_JSON, the corresponding scalar element must be a JSON string (representing an ISO 8601 date/time string); otherwise, it must be a JSON number (representing "epoch": seconds since 1970-01-01).] The scalar element was programmatically created by the application.

6. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a scalar element, or a JSON array or JSON object that in turn contained a scalar element, and the corresponding record group column was of type DATE. Either a null epoch_unit was passed to POPULATE_GROUP_FROM_JSON and the scalar element was a JSON string which was not in valid ISO 8601 format, or a non-null epoch_unit was specified and the scalar element was a JSON number which was not a valid epoch. The scalar element was programmatically created by the application.

7. The JSON array or JSON object passed as the second parameter to the POPULATE_GROUP_FROM_JSON function contained a JSON string element, or a JSON array or JSON object that in turn contained a JSON string element, and the value of the string element exceeded 32767 bytes. The string element was programmatically created by the application.

8. A JSON object was passed as the second parameter to the POPULATE_GROUP_FROM_JSON function. It contained an element whose object key exceeded 32767 bytes or, in the case where the first record group column was of type NUMBER, could not be converted to a number. The element was programmatically created by the application.

In cases 1 and 2, an FJSON.BAD_ARGUMENT exception was raised.

In cases 2-8, additional information that may help diagnose the issue was written to ODL (starting with an FRM-41533, FRM-41534, FRM-41535, or FRM-41536 message for cases 2-5, 6, 7, and 8, respectively).

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41522: expected element not found in application-created JSON array or object

Cause: Application design error. An FJSON.FIND_ARRAY, FJSON.FIND_OBJECT, FJSON.GET_ARRAY, or FJSON.GET_OBJECT function produced no element, and the FJSON.ELEMENT_T value passed as the first parameter to the function was programmatically created by the application. An FJSON.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41530: retrieved element of incorrect type specified as target of JSON operation

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

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41531: retrieved element of unexpected type or value found in JSON array or object

Cause: Application design error. One of the following occurred:

1. An FJSON.FIND_x or FJSON.GET_x function produced an element of an unexpected type that was retrieved from a REST endpoint.

2. The JSON array passed as the first parameter to the FJSON.JOIN function contained an element that was not a JSON string, and the element was retrieved from a REST endpoint.

In cases 1 and 2, an FJSON.CONTENT exception was raised.

In all cases, additional information that may help diagnose the issue was written to ODL (starting with a more detailed FRM-41531 message for case 1, and an FRM-41533, FRM-41534, FRM-41535, or FRM-41536 message for cases 2-5, 6, 7, and 8, respectively).

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41532: expected element not found in retrieved JSON array or object

Cause: Application design error. An FJSON.FIND_ARRAY, FJSON.FIND_OBJECT, FJSON.GET_ARRAY, or FJSON.GET_OBJECT function produced no element, and the FJSON.ELEMENT_T value passed as the first parameter to the function was retrieved from a REST endpoint. An FJSON.CONTENT exception was raised. Additional information that may help diagnose the issue was written to ODL (starting with a more detailed FRM-41532 message).

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41540: unexpected content detected in JSON document

Cause: The application called the FJSON.UNEXPECTED_CONTENT procedure, presumably because its logic detected unexpected content of some sort. The message passed to that procedure was incorporated into an FRM-41540 or FRM-41541 message written to ODL. An FJSON.CONTENT exception was raised.

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

Level: 99

Trigger: ON-ERROR

FRM-41549: unexpected scalar conversion exception encountered while processing JSON document

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

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

Level: 99

Trigger: ON-ERROR

FRM-41560: syntax error in retrieved JSON text

Cause: A parse of the JSON text response from a REST endpoint encountered a violation of RFC 7159. The parse was aborted, and the memory that had already been allocated for the parse tree was made available for subsequent JSON parse tree operations. An FJSON.PARSE_FAILURE exception was raised. Additional information that may help diagnose the issue was written to ODL (starting with a more detailed FRM-41560 message).

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

Level: 99

Trigger: ON-ERROR

FRM-41561: oversize object key in retrieved JSON text

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

Action:

Level: 99

Trigger: ON-ERROR

FRM-41562: oversize array or object in retrieved JSON text

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

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

Level: 99

Trigger: ON-ERROR

FRM-41570: JSON parse memory limit exceeded

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

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

Level: 99

Trigger: ON-ERROR

FRM-41571: JSON new memory limit exceeded

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

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

Level: 99

Trigger: ON-ERROR

FRM-41572: JSON memory allocation failed

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

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

Level: 99

Trigger: ON-ERROR

FRM-41573: JSON parse trees require excessive memory for element values.

Cause: This error arises only if both the following occur:

1. The FORMS_JSON_KEY_LENGTH_BITS environment variable [which defaults to 15, limiting object keys to 32767 bytes] was set to a value N in the range 16..30 [the maximum allowed].

2. The total number of bytes required for all strings, numbers, and hash arrays for all elements in all JSON parse trees exceeded 2 raised to the power of 64-N.

If this error occurred, then an FJSON.GLOBAL_ALLOCATION exception was raised.

Level: 99

Trigger: ON-ERROR

FRM-41574: too many elements in JSON parse trees

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

Level: 99

Trigger: ON-ERROR

FRM-41580: invalid $ref string

Cause: The element passed to FJSON.RESOLVE$REF specified a $ref string which was not a syntactically valid URI. ODL will contain a more detailed message.

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

Level: 99

Trigger: ON-ERROR

FRM-41581: $ref recursion excessive or produced loop

Cause: The element passed to FJSON.RESOLVE$REF specified a $ref string which resolved to another $ref element, which in turn resolved to yet another $ref element, and so forth. ODL will contain a more detailed message.

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

Level: 99

Trigger: ON-ERROR

FRM-41584: invalid JSON pointer

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

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

Level: 99

Trigger: ON-ERROR

FRM-41590: invalid charset specified for JSON file operation

Cause: The 'charset' parameter passed to FJSON.NEW_STRING_FROM_FILE or FJSON.STRING_VALUE_TO_FILE was invalid. It must be a valid Oracle Database character set name or else 'NLS_LANG', which indicates the Oracle Database character set name that was specified in the NLS_LANG environment variable.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41591: conflicting parameters: charset and base64 both specified for JSON file operation

Cause: FJSON.NEW_STRING_FROM_FILE or FJSON.STRING_VALUE_TO_FILE was passed both a non-null 'charset' parameter and a 'base64_encode' or 'base64_decode' parameter with a value of true. Charset conversion is appropriate only for character files and base64 encoding or decoding is appropriate only for binary files.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41592: JSON string not a valid base64 encoding

Cause: 'base64_decode := true' was specified for FJSON.STRING_VALUE_TO_FILE, but the value of the JSON string specified by the 'target' parameter was not a valid base64 encoding. A valid base64 encoding must contain only white space [blank, tab, carriage return, or line feed] or base64 alphabet characters ['A'-'Z', 'a'-'z', '0'-'9', '+', '/', or '=']. '=' characters are not required, but if present, they must occur only at the end, and they must ensure that the total number of base64 alphabet characters is a multiple of 4. Information that may help diagnose the issue was written to ODL.

Action: If the string was retrieved from a REST endpoint, contact the owner of the REST service. If the string was created by the application, correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41593: JSON string could not be written.

Cause: FJSON.STRING_VALUE_TO_FILE was unable to successfully write the string value to the location specified by the 'file_name' parameter. The FRM-41493 message written to ODL specifies the full name of the file.

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

Level: 99

Trigger: ON-ERROR

FRM-41594: File could not be read into JSON string.

Cause: The 'file_name' parameter passed to FJSON.NEW_STRING_FROM_FILE specified a file that could not be found or could not be read. The FRM-41494 or FRM-41495 message written to ODL specifies the full name of the file.

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

Level: 99

Trigger: ON-ERROR

FRM-41600: invalid '%s' parameter passed to FHTTP.ISSUE_REQUEST

Cause: Application design error. The specified parameter specified a value that violated one of the following constraints:

1. The 'method' parameter value must (a) be GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, or PATCH and (b) be acceptable for configured security settings and the specific URL that was generated. For violations of (b), a more specific FRM-41610 message is written to ODL.

2. The 'server_url_or_id' parameter value must, if specified, either be a well-formed http, https, ws, or wss URL or else contain only alphanumeric characters and '_', '.', '-'. In the second case, the '='-separated concatentaion of the 'config' parameter specified in the frmservlet URL and this 'server_url_or_id' parameter are used as a key to a generic credential. The generic credential must specify a well-formed http, https, ws, or wss URL (which will be prepended to the URL generated from the 'uri_template' and 'url_parameters' parameters). A more specific FRM-41620, FRM-41621, FRM-41622, or FRM-41623 message is written to ODL.

3. The 'uri_template' parameter value must specify a syntactically correct URI template [RFC 6570, level 4], and it must, in conjunction with the URL derived from the 'server_url_or_id' parameter and the 'url_parameters' parameter, generate a well-formed http, https, ws, or wss URL. A more specific FRM-41630 or FRM-41633 message is written to ODL.

4. (a) The 'url_parameters' parameter value must specify null or a JSON object element; (b) the object's child values must be strings, arrays of strings, or objects whose child values are strings or arrays of strings; (c) where the URI template allows strings to contain %-encodings, such encodings must be valid. For violations of (b) and (c), a more specific FRM-41640, FRM-41642, or FRM-41643 message is written to ODL.

5. (a) The 'request_headers' parameter value must specify null or a JSON object element; (b) the object's child values must be strings; (c) the child keys and values must be valid HTTP header names and values [RFC 7230]. For violations of (b) and (c), a more specific FRM-41650, FRM-41652, or FRM-41653 message is written to ODL.

6. The 'accept' and 'parse' parameter value must be null or a comma-separated list of (a) 3-digit HTTP response status codes in the range 100-599 and/or (b) ranges of such status codes, specified as hyphen-separated low and high values.

7. The 'request_body' parameter must not be specified if the 'method' parameter is GET, HEAD, DELETE, OPTIONS, or TRACE.

8. The 'authorization_info' parameter value must consist of tokens separated by unit separator characters [u001f]. The tokens must be syntactically valid and must specify a supported authorization mode. An authorization that requires a logon dialog must be last. A more specific FRM-41712, FRM-41713, FRM-41714, or FRM-41715 message is written to ODL.

In all cases, an FHTTP.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41660: HTTP request encountered error communicating with an external service

Cause: The request issued by FHTTP.ISSUE_REQUEST encountered an I/O error while communicating with the external service. An FHTTP.BAD_RESPONSE exception was raised. ODL will contain a more detailed message.

Action: If the problem persists, contact the owner of the external service.

Level: 99

Trigger: ON-ERROR

FRM-41661: HTTP request received unexpected response status code %d.

Cause: The request issued by FHTTP.ISSUE_REQUEST received a response status code that was not specified in the 'accept' parameter and was not one of the status codes that are always accepted, namely 200, and [for all methods except TRACE] 204, and [for PUT and POST] 201 and 205. An FHTTP.BAD_RESPONSE exception was raised. ODL will contain a more detailed message.

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

Level: 99

Trigger: ON-ERROR

FRM-41670: HTTP URL and request headers require excessive memory.

Cause: The URL generated from the 'uri_template' and 'url_parameters' parameters passed to FHTTP.ISSUE_REQUEST, together with the headers generated from the 'request_headers' parameter, required nearly 2Gb of memory. An FHTTP.BAD_ARGUMENT exception was raised.

Action: Verify that the 'uri_template', 'url_parameters', and 'request_headers' parameters are reasonable.

Level: 99

Trigger: ON-ERROR

FRM-41671: memory allocation failure encountered while processing an HTTP request

Cause: FHTTP.ISSUE_REQUEST was unable to allocate adequate memory in the runtime process. An FHTTP.ALLOCATION exception was raised. ODL will contain a more detailed message.

Action: Specify fewer or smaller request headers or a smaller request body, or modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response.

Level: 99

Trigger: ON-ERROR

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-41673: OutOfMemoryError encountered while processing an HTTP request

Cause: FHTTP.ISSUE_REQUEST was unable to allocate adequate memory in the JVM that's issuing the request. An FHTTP.ALLOCATION exception was raised. ODL will contain a more detailed message.

Action: Specify fewer or smaller request headers or a smaller request body, or modify the selection criteria specified in the request to the REST endpoint, so as to limit the size of the response.

Level: 99

Trigger: ON-ERROR

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-41698: invalid '%s' parameter passed to FHTTP.SET_SERVER_OPTION

Cause: Application design error. The specified parameter specified a value that violated one of the following constraints:

1. The 'server' parameter value must be a well-formed URL wthout a query or fragment whose protocol is http, https, ws, or wss, or an initial portion of such a URL. It will typically specify a protocol and a domain.

2. The 'server_option' parameter value must be one that is supported by FHTTP.SET_SERVER_OPTION.

In all cases, an FHTTP.BAD_ARGUMENT exception was raised.

Action: Correct the application logic.

Level: 99

Trigger: ON-ERROR

FRM-41699: FHTTP PL/SQL package supported only in Forms Servlet mode

Cause: A function or procedure in the FHTTP PL/SQL package was invoked in Forms Listener mode, which is no longer supported. A Form_Fatal_Error exception was raised.

Action: Use Forms Servlet mode.

Level: 99

Trigger: ON-ERROR

FRM-41700: HTTP request authorization failed

Cause: A request issued by FHTTP.ISSUE_REQUEST required authorization and the 'authorization_info' parameter value was syntactically valid, but authorization was unsuccessful. ODL will contain more detailed message(s).

Action: Examine the message(s) in ODL.

Level: 99

Trigger: ON-ERROR

FRM-41701: OAuth2 authorization timed out

Cause: A request issued by FHTTP.ISSUE_REQUEST required an OAuth2 authorization code grant. This in turn required the OAuth2 authorization server to interact with the end user. The end user did not either approve or deny the requsted privilege within the interval specified by the ssoSaaBrowserPageTimeout configuration parameter, or the OAuth2 authorization server encountered an error.

Action: Increase the value of the ssoSaaBrowserPageTimeout configuration parameter, if desired.

Level: 99

Trigger: ON-ERROR

FRM-41702: username and password for REST service not both specified

Cause: A request issued by FHTTP.ISSUE_REQUEST required basic authentication or an OAuth2 password credentials grant. A logon dialog was presented, but an empty username and/or an empty password were entered.

Action: Enter a non-empty username and a non-empty password.

Level: 99

Trigger: ON-ERROR

FRM-41703: colon specified in username for basic authentication

Cause: A request issued by FHTTP.ISSUE_REQUEST required basic authentication. A logon dialog was presented, but a username containing a colon was entered. This is not allowed for basic authentication.

Action: Enter a corrected username.

Level: 99

Trigger: ON-ERROR

FRM-41704: specified username and password specified rejected by REST service

Cause: A request issued by FHTTP.ISSUE_REQUEST required basic authentication or an OAuth2 password credentials grant. A logon dialog was presented, and a username and a password were entered, but the REST service rejected the HTTP request as unauthorized.

Action: Determine the correct username/password and enter them.

Level: 99

Trigger: ON-ERROR

FRM-41705: REST logon dialog terminated after 3 unsuccessful attempts

Cause:

Action: Determine the correct username/password and restart the Forms application.

Level: 99

Trigger: ON-ERROR

FRM-41800: List of Values not available for this field.

Cause: You pressed [List], but the form does not provide a list of values for this field.

Action: No action is necessary.

Level: 10

Trigger: ON-MESSAGE

FRM-41801: Last value retrieved.

Cause: You pressed [List] and then pressed [Next Item] after the last value in the list was displayed.

Action: Enter an item value or press [List] again to display the list of possible values.

Level: 10

Trigger: ON-MESSAGE

FRM-41802: Duplicate record function allowed on new records only.

Cause: You pressed [Duplicate Record], but the current record is the one that has been fetched from the database.

Action: No action is necessary. You can use [Duplicate Record] only when creating a new record.

Level: 10

Trigger: ON-ERROR

FRM-41803: No previous record to copy value from.

Cause: You pressed [Duplicate Item] or [Duplicate Record], but the current record is the first record in the block.

Action: No action is necessary. [Duplicate Item] and [Duplicate Record] are meaningless in this context.

Level: 10

Trigger: ON-ERROR

FRM-41804: Variable was not entered: %.30s.

Cause: Your response to the Query Where alert contained a placeholder not used in any of the query items.

Action: Correct the placeholder in your response, or define it in one of the query items. Then re-execute the query.

Level: 99

Trigger: ON-ERROR

FRM-41805: Ambiguous item name: %s.

Cause: Application design error. A call to a Built-in specified an ambiguous item name. (No block was specified, and more than one block contains an item of the specified name).

Action: Specify a block name (block.item).

Level: 99

Trigger: ON-ERROR

FRM-41806: Too many variables used.

Cause: You used more than 25 substitution variables in your query.

Action: Reduce the number of substitution variables and re-query.

Level: 99

Trigger: ON-ERROR

FRM-41809: Error initializing Menu.

Cause: You tried to use the menu component from within Oracle Forms, and an internal error occurred.

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

Level: 99

Trigger: ON-ERROR

FRM-41810: Error creating menu.

Cause: You tried to use the menu component from within Oracle Forms, and an internal error occurred.

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

Level: 99

Trigger: ON-ERROR

FRM-41811: Error removing menu.

Cause: You tried to use Menus from within Oracle Forms, and an internal Menu error occurred.

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

Level: 99

Trigger: ON-ERROR

FRM-41812: Error resetting Menu.

Cause: You tried to use the menu component from within Oracle Forms, and an internal error occurred.

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

Level: 99

Trigger: ON-ERROR

FRM-41813: Form exited by debug mode.

Cause: You selected the Exit Oracle Forms Runtime option on the Break Processing menu.

Action: No action is necessary.

Level: 99

Trigger: None

FRM-41814: Invalid page position.

Cause: Application design error. A trigger tried to move or resize a view to a page that would cause all or part of the view to display off of the screen.

Action: Correct the statement.

Level: 99

Trigger: ON-ERROR

FRM-41815: No such property for Get_LOV_Property.

Cause: You attempted to get a nonexistent LOV property.

Action: Verify the valid LOV properties and try again.

Level: 20

Trigger: ON-ERROR

FRM-41816: Attempt to create existing timer: %s.

Cause: Attempted to create a timer that already exists.

Action: Delete or alter the existing timer before re-creating a new one.

Level: 99

Trigger: ON-ERROR

FRM-41817: No such timer: %s.

Cause: You attempted to alter or delete a non-existent timer.

Action: Check the Built-in for proper arguments.

Level: 99

Trigger: ON-ERROR

FRM-41818: Toolkit failed to create timer %s :may be out of memory.

Cause: An internal error occurred while attempting to create a timer, possibly as a result of memory constraints.

Action: Check and adjust memory quotas as necessary.

Level: 99

Trigger: ON-ERROR

FRM-41819: Timers are not supported on this platform.

Cause: Illegal attempt to create a timer on a platform where timers are not supported.

Action: None. A timer option is unavailable on your platform.

Level: 99

Trigger: ON-ERROR

FRM-41820: Toolkit failed to delete timer: %s.

Cause: Internal error caused by timer failure.

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

Level: 99

Trigger: ON-ERROR

FRM-41821: Timer name too long: %s...

Cause: You attempted to create a timer with a name longer than 30 bytes.

Action: Retry with a shorter name.

Level: 99

Trigger: ON-ERROR

FRM-41822: Timer name may not be null string.

Cause: You attempted to create a timer with a null name.

Action: Retry with a non-null name.

Level: 99

Trigger: ON-ERROR

FRM-41823: Illegal timer interval for timer %s.

Cause: You attempted to create a timer with an interval less than 1 millisecond.

Action: Recreate your timer with an interval of at least 1 millisecond.

Level: 99

Trigger: ON-ERROR

FRM-41824: Date/time operation failed for %s.

Cause: An internal error occurred while attempting to resolve a date/time initial value for an item.

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

Level: 10

Trigger: ON-ERROR

FRM-41825: No such property for Set_LOV_Property.

Cause: You attempted to set a nonexistent LOV property.

Action: Verify the valid LOV properties and try again.

Level: 20

Trigger: ON-ERROR

FRM-41826: Cannot replace group; columns don't match LOV.

Cause: Cannot replace the list of values' current record group with a record group that is incompatible with the LOV column structure.

Action: Do not attempt to assign this record group to this LOV.

Level: 20

Trigger: ON-ERROR

FRM-41827: Group does not exist.

Cause: The group name or ID specified is invalid.

Action: Check the name or ID entered and try again.

Level: 20

Trigger: ON-ERROR

FRM-41828: LOV does not exist.

Cause: LOV name or ID specified is invalid.

Action: Check the name or ID entered and try again.

Level: 20

Trigger: ON-ERROR

FRM-41829: Record not created.

Cause: Application design error. The record failed to get its initial value.

Action: Contact the application designer.

Level: 20

Trigger: ON-ERROR

FRM-41830: List of Values contains no entries.

Cause: The record group underlying the LOV contains no records.

Action: Check to be sure that any criteria used to reduce a long list LOV did not eliminate all matches.

Level: 5

Trigger: ON-ERROR

FRM-41832: Error: program unit %s in library %s is uncompiled.

Cause: You called an uncompiled program unit from a library.

Action: Follow the PL/SQL program error.

Level: 99

Trigger: ON-ERROR

FRM-41833: Warning! Program unit %s in library %s is uncompiled.

Cause: You called an uncompiled program unit in a library when debug mode was specified.

Action: This is just a warning. Forms Runtime will attempt to compile and run the program unit.

Level: 99

Trigger: None

FRM-41835: Canvas %s is not a tab canvas.

Cause: You tried to perform a tab canvas specific operation on a canvas which is not a tab canvas.

Action: Make sure the canvas specified is a tab canvas.

Level: 99

Trigger: ON-ERROR

FRM-41836: No tab page %s in canvas %s.

Cause: You tried to perform an operation on a tab page which does not exist in the specified canvas.

Action: Make sure you specify a tab page which exists in the specified tab canvas.

Level: 99

Trigger: ON-ERROR

FRM-41837: Error raising tab page %s.

Cause: The specified tab page could not be brought to the top (made the current page of the tab canvas).

Action: Make sure the specified page is enabled, and not hidden.

Level: 99

Trigger: ON-ERROR

FRM-41838: Unable to open temporary record buffer file

Cause: Unable to open file used as temporary record buffer.

Action: Verify that the file system or directory in which the file resides exists and that you have permissions to read and write to it.

Level: 99

Trigger: ON-ERROR

FRM-41839: Disk I/O error on temporary record buffer file

Cause: An I/O error occurred on attempting to read or write a record to the temporary record buffer file.

Action: Verify that the file system or directory in which the file resides exists, and that you have permissions to read and write to it, and that it contains sufficient space. If the file system is full, and you are executing a large query, retry it with additional query criteria (in order to reduce the size of the result set). Alternatively, commit changes and, if necessary, clear one or more blocks to free up disk space.

Level: 99

Trigger: ON-ERROR

FRM-41840: Insufficient main memory for record buffers

Cause: Unable to allocate memory for a record being created in a block or record group.

Action: If you are executing a large query, retry it with additional query criteria (in order to reduce the size of the result set). Alternatively, commit changes and, if necessary, clear one or more blocks to free up memory, or try restarting the application when fewer programs are running concurrently, or on a machine with more memory.

Level: 99

Trigger: ON-ERROR

FRM-41841: Use the debugger-enabled executable if specifying DEBUG=YES.

Cause: You tried to use the debugger from an executable which doesn't include it.

Action: Run the other executable (name will vary with operating system), which includes the debugger.

Level: 99

Trigger: None

FRM-41843: Invalid time zone region %s for ADJUST_TZ.

Cause: A call to the ADJUST_TZ procedure specified an invalid 'from' or 'to' time zone region name.

Action: Specify a valid name. If the name is valid, you may need to ask your system administrator to install a larger time zone file.

Level: 25

Trigger: ON-ERROR

FRM-41844: ADJUST_TZ could not convert date.

Cause: A call to the ADJUST_TZ procedure specified valid 'from' and 'to' time zone region names, but nevertheless failed. This probably indicates that the date was too close to the boundary dates of Jan 1, 4712 BC or Dec 31, 9999 AD.

Action: Specify a valid date.

Level: 25

Trigger: ON-ERROR

FRM-41845: Javascript events have been disabled.

Cause: Either the environment variable FORMS_ALLOW_JAVASCRIPT_EVENTS or the applet parameter enableJavaScriptEvent has been set to FALSE.

Action: Set client applet's parameter enableJavaScriptEvent and the server's environment variable FORMS_ALLOW_JAVASCRIPT_EVENTS to true. The default value of both these variables is true.

Level: 15

Trigger: ON-ERROR

FRM-41847: Temporary record buffer file size limit exceeded

Cause: An insert record, update record, or fetch required space in the temporary record buffer file, but it had reached its size limit (4GB or the value specified by the FORMS_RECMGR_MAX_TMPFILE_SIZE environment variable).

Level: 99

Trigger: ON-ERROR

FRM-41848: JavaScript execution is disabled during webstart session.

Cause: JavaScript integration is not supported when running webstart.

Action: Use a browser if you want to run JavaScript integration with Oracle Forms.

Level: 15

Trigger: ON-ERROR

FRM-41849: JavaScript execution is disabled for Stand-alone App.

Cause: JavaScript integration is not supported with Stand-alone App.

Action: Use a browser if you want to run JavaScript integration with Oracle Forms.

Level: 15

Trigger: ON-ERROR

FRM-41850: Archived record memory threshold exceeded

Cause: An insert record, update record, or fetch required virtual memory, but the virtual memory consumed by all archived records had exceeded the archive threshold (4GB or the value specified by the FORMS_RECMGR_ARCHIVE_THRESHOLD environment variable).

Level: 99

Trigger: ON-ERROR

FRM-41851: RECORDS_DISPLAYED property must be between 1 and MAX_RECORDS_DISPLAYED property

Cause: An attempt was made to set the number of records displayed to an invalid value.

Action: Make sure that the requested number of records displayed is a positive integer less than or equal to the maximum number of records displayed for the block.

Level: 20

Trigger: ON-ERROR

FRM-41852: RECORDS_DISPLAYED property can't be updated for autosize blocks

Cause: An attempt was made to set the number of records displayed in a block which is set to autosize.

Action: Either remove the call to set the number of records displayed, or change the block to not be autosize.

Level: 20

Trigger: ON-ERROR

FRM-41853: Popup menu %s not found

Cause: The specified popup menu does not exist in the module.

Action: Either remove the call to set the popup menu, or change the menu name to specify one that exists.

Level: 99

Trigger: ON-ERROR

FRM-41854 Cannot assign new menu when initial menu not set

Cause: A canvas or item that does not have a popup menu specified at design-time cannot have one added at runtime.

Action: Either remove the call to set the popup menu, or ensure that a popup menu is associated with the object at design-time.

Level: 99

Trigger: ON-ERROR

FRM-41855 Canvas %s does not have a splitter associated with it

Cause: The splitter position cannot be set because the specified canvas does not have a spitter associated with it.

Action: Either remove the call to set the splitter position, or ensure that the canvas has a splitter associated with it.

Level: 99

Trigger: ON-ERROR

FRM-41856 Invalid position specified for splitter

Cause: The splitter position is inappropriate for the specified canvas.

Action: Ensure that the splitter position is non-negative, and is less than or equal to the height of the view (for canvases with a vertical splitter orientation) or the width of the view (for canvases with a horizontal splitter orientation).

Level: 99

Trigger: ON-ERROR

FRM-41857 Minimum UI Value must be less than Maximum UI Value

Cause: The minimum and maximum UI values conflict.

Action: Ensure that the minimum UI value property is smaller than the maximium UI value property.

Level: 99

Trigger: ON-ERROR

FRM-41858 Minimum UI Value must be divisible by UI Increment Value

Cause: The minimum UI value must be evenly divisible by the UI Increment Value.

Action: Ensure that the minimum UI value property is divisible by the UI Increment value property.

Level: 99

Trigger: ON-ERROR

FRM-41859 Maximum UI Value must be divisible by UI Increment Value

Cause: The maximum UI value must be evenly divisible by the UI Increment Value.

Action: Ensure that the maximum UI value property is divisible by the UI Increment value property.

Level: 99

Trigger: ON-ERROR

FRM-41900: Run aborted by fatal error.

Cause: Internal error.

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

Level: 99

Trigger: None

FRM-41901: Error: %d cursors were not closed.

Cause: Internal error.

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

Level: 99

Trigger: None

FRM-41902: Total cursors used %d.

Cause: This message appears when you run a form with the Statistics preference set to True.

Action: No action is necessary.

Level: 20

Trigger: ON-MESSAGE

FRM-41903: Run aborted by end of input file.

Cause: Internal error.

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

Level: 99

Trigger: None

FRM-42017: Module name must be specified.

Cause: You did not specify a module name.

Action: Specify a module name.

Level: 99

Trigger: None

FRM-42100: No errors encountered recently.

Cause: You pressed [Display Error], but no error has occurred recently.

Action: No action is necessary.

Level: 5

Trigger: ON-MESSAGE

FRM-42400: Performing event trigger %s.

Cause: This message is displayed during a trigger when debug mode is specified.

Action: No action is necessary.

Level: 99

Trigger: ON-MESSAGE

FRM-42401: Performing program trigger %s.

Cause: This message is displayed during a trigger when debug mode is specified.

Action: No action is necessary.

Level: 99

Trigger: ON-MESSAGE

FRM-42423: Cannot execute trigger %s: no compiled state

Cause: This message is displayed when running a form in debug mode, if the compiled state of a trigger has been destroyed. This can happen if you apply a change to the trigger text and that change results in compilation errors.

Action: You can recompile the trigger in the debugger or exit the form and start it up again.

Level: 99

Trigger: ON-ERROR

FRM-42431: Unable to initialize debugger.

Cause: An error occured while attempting to initialize debugger. This could be caused by one of the following:

1. The JVM failed to startup.

2. The Classpath does not include the debugger dependencies.

Action: Restart the JVM or modify the Classpath.

Level: 99

Trigger: ON-ERROR

FRM-42435: Remote Debugger: Specified port(s) are not available.

Cause: Other processes are using the specified port(s).

Action: Try some other port.

Level: 99

Trigger: None

FRM-47000: Cannot create Parameter List %s : internal error.

Cause: Internal error.

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

Level: 99

Trigger: ON-ERROR

FRM-47001: Cannot create Parameter List %s : list with this name exists.

Cause: The name you specified for the parameter list is already in use.

Action: Specify another name for the parameter list.

Level: 99

Trigger: ON-ERROR

FRM-47002: Cannot create Parameter List : name must not be null.

Cause: The parameter list name cannot be null.

Action: Specify a name for the parameter list.

Level: 99

Trigger: ON-ERROR

FRM-47003: Cannot delete Parameter List : internal error.

Cause: Internal error.

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

Level: 99

Trigger: ON-ERROR

FRM-47004: Cannot delete Parameter List : invalid ID.

Cause: Attempted to pass an invalid parameter list ID.

Action: Check the list ID name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47005: Cannot validate parameter %s : internal error.

Cause: Internal error.

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

Level: 99

Trigger: ON-ERROR

FRM-47006: Cannot create Parameter List '%s' : illegal identifier name.

Cause: Illegal identifier name.

Action: Check valid syntax for the identifier.

Level: 99

Trigger: ON-ERROR

FRM-47007: Cannot get parameter %s attributes from Parameter List : invalid list ID.

Cause: Specified an invalid parameter list ID.

Action: Check the parameter list ID name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47008: Cannot add parameter %s to Parameter List %s : internal error.

Cause: An internal error occurred.

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

Level: 99

Trigger: ON-ERROR

FRM-47009: Cannot add parameter %s to Parameter List : invalid list ID.

Cause: You specified an invalid parameter list ID.

Action: Check the parameter list ID name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47010: Cannot add parameter to Parameter List %s : null key specified.

Cause: No name specified for the parameter.

Action: Specify a parameter name key in your call to ADD_PARAMETER.

Level: 99

Trigger: ON-ERROR

FRM-47011: Cannot add parameter %s to Parameter List %s : incorrect type specified.

Cause: You specified an invalid parameter type.

Action: Specify either TEXT_PARAMETER or DATA_PARAMETER.

Level: 99

Trigger: ON-ERROR

FRM-47012: Cannot add parameter %s to Parameter List %s : group %s does not exist.

Cause: Record group name does not exist.

Action: Check the record group name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47013: Cannot add parameter %s to Parameter List %s : parameter with this name exists.

Cause: Parameter with this name already exists.

Action: Specify another name for the parameter.

Level: 99

Trigger: ON-ERROR

FRM-47014: Cannot delete parameter %s from Parameter List %s : internal error.

Cause: Internal error.

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

Level: 99

Trigger: ON-ERROR

FRM-47015: Cannot delete parameter %s from Parameter List : invalid list ID.

Cause: Specified an invalid parameter list ID.

Action: Check the list ID name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47016: Cannot delete parameter from Parameter List %s : null key specified.

Cause: You did not specify a name for the parameter.

Action: Correct the call to DELETE_PARAMETER by supplying a parameter name.

Level: 99

Trigger: ON-ERROR

FRM-47017: Cannot delete parameter %s from Parameter List %s : no such named parameter exists.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name that does not exist.

Action: Check the parameter name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47018: Cannot set parameter %s attributes in Parameter List %s : internal error.

Cause: Internal error: you specified an invalid parameter list ID.

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

Level: 99

Trigger: ON-ERROR

FRM-47019: Cannot set parameter %s attributes in Parameter List : invalid list ID.

Cause: You specified an invalid parameter list ID.

Action: Check the parameter list ID name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47020: Cannot set parameter %s attributes in Parameter List %s : no such named parameter exists.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name that does not exist.

Action: Check the parameter name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47021: No such parameter named %s exists in Parameter List %s.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name that does not exist.

Action: Check the name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47022: Cannot create Parameter List %s : name is a reserved word.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a name that is a reserved word.

Action: Specify another name for the parameter list.

Level: 99

Trigger: ON-ERROR

FRM-47023: No such parameter named %s exists in form %s.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name does not exist.

Action: Check the name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47024: Parameter %s type does not match definition in form %s.

Cause: You specified a parameter type that does not match the definition in the form.

Action: Specify a parameter type that matches the definition in the form.

Level: 99

Trigger: ON-ERROR

FRM-47025: Cannot get parameter %s attributes from Parameter List %s : internal error.

Cause: Internal error: you specified an invalid parameter list ID.

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

Level: 99

Trigger: ON-ERROR

FRM-47026: Cannot get parameter %s attributes from Parameter List %s : no such named parameter exists.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name does not exist.

Action: Check the name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47027: Cannot add parameter %s to Parameter List %s : invalid key specified .

Cause: You specified an invalid parameter list ID.

Action: Check the name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47028: Cannot set parameter %s attribute in Parameter List %s : group %s does not exist.

Cause: You specified an invalid parameter list ID.

Action: Check the name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47029: Invalid parameter list ID in form %s.

Cause: Caused by one of the following:

1. You specified an invalid parameter list ID.

2. You specified a parameter name does not exist.

Action: Check the ID and try again.

Level: 99

Trigger: ON-ERROR

FRM-47030: Value of parameter %s is too long for definition in form %s.

Cause: You specified a parameter that is too long.

Action: Specify a parameter that is valid.

Level: 99

Trigger: ON-ERROR

FRM-47031: Cannot set value of parameter %s in DEFAULT parameter list: invalid value specified.

Cause: Application design error. A Built-in (such as SET_PARAMETER_ATTR) is attempting to set the value of a parameter which was defined when the form was designed, but the value specified is not legal for the parameter's datatype.

Action: The call to the Built-in must be modified or removed.

Level: 99

Trigger: ON-ERROR

FRM-47032: Cannot set value of parameter %s in DEFAULT parameter list: internal error.

Cause: An internal error while attempting to set the value of a parameter.

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

Level: 99

Trigger: ON-ERROR

FRM-47033: Cannot set value of read-only bind variable %s.

Cause: Application design error. The application attempted to assign a value to a bind variable which cannot be programmtically modified.

Action: The assignment must be removed.

Level: 25

Trigger: ON-ERROR

FRM-47100: Cannot read image file %s.

Cause: Caused by one of the following:

1. Oracle Forms was unable to find or open the file.

2. The data in the file is not in the specified format.

Action: Check the file name and file format and try again.

Level: 99

Trigger: ON-ERROR

FRM-47101: Cannot write image file %s.

Cause: Caused by one of the following:

1. Oracle Forms was unable to find or open the file.

2. The data in the file is not in the specified format.

Action: Check the file name, and make sure you have write privileges.

Level: 99

Trigger: ON-ERROR

FRM-47102: Cannot perform %s operation on images %s and %s.

Cause: This operation cannot be performed on color images.

Action: Check to see that both images are black and white.

Level: 99

Trigger: ON-ERROR

FRM-47103: Cannot zoom image %s.

Cause: Internal multimedia error caused by trying to scale a null image or invalid image data.

Action: Check the image name that you want to zoom and try again.

Level: 99

Trigger: ON-ERROR

FRM-47104: Invalid image type %s.

Cause: Data in the file name specified does not match the data type specified.

Action: Check the file name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47105: No image name specified.

Cause: You did not supply a name to the Built-in call.

Action: Refer to the documentation for the proper syntax for the Built-in in question.

Level: 99

Trigger: ON-ERROR

FRM-47106: No image type specified.

Cause: You did not specify an image type when calling READ_IMAGE_FILE or WRITE_IMAGE_FILE.

Action: Supply an image type as an argument in your call to READ_IMAGE_FILE or WRITE_IMAGE_FILE.

Level: 99

Trigger: ON-ERROR

FRM-47107: Invalid zoom factor %.10g for Image_Zoom.

Cause: You specified a zoom factor outside the range 100.0/4096.0 - 409600.0 for a zoom type of ZOOM_IN_FACTOR or ZOOM_OUT_FACTOR.

Action: Correct the call to IMAGE_ZOOM.

Level: 20

Trigger: ON-ERROR

FRM-47108: Item %s is not an image item.

Cause: You attempted to perform an image operation on an item that is not an image item.

Action: Check the item name and try again.

Level: 99

Trigger: ON-ERROR

FRM-47109: Cannot locate image file %s.

Cause: You specified a file that cannot be found or does not exist.

Action: Verify that the file exists and the pathname is correct.

Level: 20

Trigger: ON-ERROR

FRM-47110: No region was selected for Image_Zoom: %s

Cause: You tried to zoom an image without selecting an image region.

Action: Select an image region.

Level: 20

Trigger: ON-ERROR

FRM-47111: Cannot copy value to item: %s

Cause: You tried to use the COPY Built-in on an image item.

Action: You cannot use the COPY Built-in on an image item.

Level: 99

Trigger: ON-ERROR

FRM-47112: Invalid zoom type %d for Image_Zoom.

Cause: You specified a zoom type for Image_Zoom that was not one of ADJUST_TO_FIT, SELECTION_RECTANGLE, ZOOM_IN_FACTOR, ZOOM_OUT_FACTOR, or ZOOM_PERCENT.

Action: Correct the call to IMAGE_ZOOM.

Level: 20

Trigger: ON-ERROR

FRM-47113: Invalid zoom percent %.10g for Image_Zoom.

Cause: Caused by one of the following:

1. You specified an invalid zoom percent (outside the range 100.0/4096.0 - 409600.0) for a zoom type of ZOOM_PERCENT.

Action: Correct the call to IMAGE_ZOOM.

Level: 20

Trigger: ON-ERROR

FRM-47114: Cannot zoom or scroll an image item whose Sizing Style is Fill.

Cause: You attempted to call IMAGE_ZOOM or IMAGE_SCROLL on an image item whose Sizing Style is Fill.

Action: Correct or remove the call to IMAGE_ZOOM or IMAGE_SCROLL.

Level: 20

Trigger: ON-ERROR

FRM-47115: Internal error occured while reading unsupported image.

Cause: Image may be corrupt or may be non-standard format or compression.

Action: Verify image data, format, compression etc.

Level: 99

Trigger: ON-ERROR

FRM-47300: Item is not a hierarchical tree. (%s)

Cause: A hierarchical tree Built-in was invoked on a non-tree item.

Action: Check item type and name.

Level: 99

Trigger: ON-ERROR

FRM-47301: Cannot add data as sibling to the tree root.

Cause: ADD_TREE_DATA or ADD_TREE_NODE attempted to add data as a sibling of the root.

Action: Add data at a lower level in the tree.

Level: 99

Trigger: ON-ERROR

FRM-47302: Can only add data to tree as child or sibling.

Cause: ADD_TREE_DATA or ADD_TREE_NODE attempted to use an unknown offset_type value.

Action: Only PARENT_OFFSET and SIBLING_OFFSET are allowed for the offset_type parameter.

Level: 99

Trigger: ON-ERROR

FRM-47303: ADD_TREE_DATA only accepts data from a group or query.

Cause: ADD_TREE_DATA attempted to use an unknown datasource value.

Action: Only RECORD_GROUP and QUERY_TEXT are allowed for the datasource parameter.

Level: 99

Trigger: ON-ERROR

FRM-47304: Cannot delete the root node of a tree.

Cause: DELETE_TREE_NODE attempted to delete the root node.

Action: Check if a node is the root (use ID_NULL) before trying to delete it.

Level: 99

Trigger: ON-ERROR

FRM-47305: Can only search a tree looking for label or value.

Cause: FIND_TREE_NODE attempted to use an unknown search_by parameter value.

Action: Set the search_by parameter to NODE_LABEL or NODE_VALUE.

Level: 99

Trigger: ON-ERROR

FRM-47306: Search_type must be FIND_NEXT or FIND_NEXT_CHILD.

Cause: FIND_TREE_NODE attempted to use an invalid search_type parameter value.

Action: Set the search_type parameter to FIND_NEXT or FIND_NEXT_CHILD.

Level: 99

Trigger: ON-ERROR

FRM-47307: Cannot get the properties of the tree root node.

Cause: GET_TREE_NODE_PARENT or GET_TREE_NODE_PROPERTY attempted to obtain information from the root node.

Action: Only invoke the Built-ins against valid nodes.

Level: 99

Trigger: ON-ERROR

FRM-47308: Invalid property for GET or SET_TREE_NODE_PROPERTY.

Cause: You passed an invalid property constant to GET or SET_TREE_NODE_PROPERTY.

Action: Verify arguments.

Level: 99

Trigger: ON-ERROR

FRM-47309: Invalid property for GET or SET_TREE_PROPERTY.

Cause: You passed an invalid property constant to GET or SET_TREE_PROPERTY.

Action: Verify arguments.

Level: 99

Trigger: ON-ERROR

FRM-47310: Bad selection index for GET_TREE_SELECTION.

Cause: Selection index must be in the range 1 .. number of selected nodes.

Action: Ensure that the selection is within the required range.

Level: 99

Trigger: ON-ERROR

FRM-47311: Error populating record group.

Cause: Invalid record group specified for POPULATE_GROUP_FROM_TREE.

Action: Check existence of the record group, and that it isn't statically defined.

Level: 99

Trigger: ON-ERROR

FRM-47312: Internal error populating record group.

Cause: Internal error during POPULATE_GROUP_FROM_TREE. Note that some rows may already have been added.

Action: Unable to add row to the record group.

Level: 99

Trigger: ON-ERROR

FRM-47313: Invalid query for the hierarchical tree.

Cause: Unable to create valid tree data from the specified query text.

Action: Check the query text for a valid number of columns and valid data types.

Level: 99

Trigger: ON-ERROR

FRM-47314: Cannot set the properties of the tree root node.

Cause: SET_TREE_NODE_PROPERTY attempted to set a property of the root node.

Action: Only invoke the Built-in against valid nodes.

Level: 99

Trigger: ON-ERROR

FRM-47315: Invalid parameter value for SET_TREE_NODE_PROPERTY.

Cause: Check the parameter values for the tree node property being set.

Action: Correct the parameter value passed to SET_TREE_NODE_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-47316: Branch nodes with no children are not allowed.

Cause: Attempt to change the state of a node from a leaf node to a branch. This tree does not allow empty branch nodes.

Action: Either change the tree to allow empty branch nodes, or add children to the node.

Level: 99

Trigger: ON-ERROR

FRM-47317: Leaf nodes cannot have children.

Cause: Attempt to change the state of a node with children from a branch node to a leaf.

Action: Delete the children from the node before changing the node's state.

Level: 99

Trigger: ON-ERROR

FRM-47318: Invalid parameter value for SET_TREE_PROPERTY.

Cause: Check the parameter values for the tree property being set.

Action: Correct the parameter value passed to SET_TREE_PROPERTY.

Level: 99

Trigger: ON-ERROR

FRM-47319: Cannot select the tree root node.

Cause: SET_TREE_SELECTION attempted to select the root node.

Action: Only invoke the Built-in against valid nodes.

Level: 99

Trigger: ON-ERROR

FRM-47320: Bad selection type for SET_TREE_SELECTION.

Cause: SET_TREE_SELECTION attempted to use an invalid selection_type parameter value.

Action: Set the selection_type parameter to SELECT_ON, SELECT_OFF, or SELECT_TOGGLE.

Level: 99

Trigger: ON-ERROR

FRM-47321: Data used to populate tree is invalid.

Cause: ADD_TREE_DATA attempted to use data of wrong format.

Action: Check number and type of columns in group or query.

Level: 99

Trigger: ON-ERROR

FRM-47322: The specified tree data source is not a record group.

Cause: The data source for the tree was declared a record group, but isn't.

Action: Check that the id or name specified is of an existing record group.

Level: 99

Trigger: ON-ERROR

FRM-47323: No nodes are selected in the tree.

Cause: Attempt was made to obtain a selected node when none are currently selected.

Action: Check for number of selected nodes before trying to retrieve one of them.

Level: 99

Trigger: ON-ERROR

FRM-47324: Could not allocate memory for tree structures.

Cause: Unable to allocate memory for internal tree structures. Tree destroyed.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47325: Could not allocate memory for tree node.

Cause: Unable to allocate memory for a tree node.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47333: Could not set required state for tree node.

Cause: Unable to change state for a tree node.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47334: Could not allocate memory for tree node icon string.

Cause: Unable to allocate memory for the name of a tree node icon.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47335: Could not locate a tree node icon. (%s)

Cause: Unable to find the desired icon in standard locations.

Action: Check that your tree node icons are located in the proper directories.

Level: 99

Trigger: ON-ERROR

FRM-47336: Could not set tree node to the requested icon.

Cause: Unable to set the requested tree node icon.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47337: Tree node label cannot be null.

Cause: Attempt was made to set a tree node's label to a null value.

Action: Set the label to a non-null value.

Level: 99

Trigger: ON-ERROR

FRM-47338: Could not allocate memory for tree node label.

Cause: Unable to allocate memory for a tree node label.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47339: Could not set tree node to the requested label.

Cause: Unable to set the requested tree node label.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47340: Could not allocate memory for tree node value.

Cause: Unable to allocate memory for a tree node value.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47341: There are too many nodes for the tree.

Cause: Only MAX-SIGNED-4-BYTE nodes, both current and deleted, are permitted in a tree.

Action: Decrease the number of nodes placed in the tree. If constantly adding and removing nodes, you might need to clear and re-populate the tree.

Level: 99

Trigger: ON-ERROR

FRM-47342: Could not allocate memory for tree query text.

Cause: Unable to allocate memory for the tree query text.

Action: Try executing the application when the system is less heavily loaded. If the problem persists, contact Oracle Support Services.

Level: 99

Trigger: ON-ERROR

FRM-47343: Invalid node ID specified for hierarchical tree item %s

Cause: A hierarchical tree built-in was invoked on a hierarchical tree item, but the node ID passed to the built-in was not valid for the tree item.

Action: Specify a valid node ID.

Level: 99

Trigger: ON-ERROR

FRM-47344: RECORDS_DISPLAYED property can't be set for a tree item

Cause: An attempt was made to change the number of records displayed for a block that contains a hierarchical tree or the hierarchical tree itself but hierarchical trees must always be in single-record blocks.

Action: Specify a different block or item.

Level: 20

Trigger: ON-ERROR

FRM-47500: Failed to register database event %s

Cause: Attempt to register a database event failed

Action: Check the event attributes on the database side

Level: 5

Trigger: ON-ERROR

FRM-47501: Cannot find event: invalid ID.

Cause: The user has specified an invalid event object name.

Action: Check the form and make sure that the event object exists.

Level: 99

Trigger: ON-ERROR

FRM-47502: Invalid event property

Cause: Invalid event property

Action: Check the event event property

Level: 5

Trigger: ON-ERROR

FRM-47700: Failed to start the JVM.

Cause: An error occured while attempting to start the inprocess JVM.

Action: Make sure that jvm libraries can be located by the runtime process

Level: 99

Trigger: ON-ERROR

FRM-47800: Unable to communicate with the JVM Controller: %s.

Cause: Unable to communicate with the JVM Controller

Action: JVM Controller, to which runform is connected, might be down. Contact your system administrator.

Level: 99

Trigger: ON-ERROR

FRM-50000: Value is too long.

Cause: You entered a value which contains too many bytes or characters for the item.

Action: Enter a shorter value.

Level: 15

Trigger: ON-ERROR

FRM-50001: Acceptable characters are a-z, A-Z, and space.

Cause: You entered an unacceptable character into the item.

Action: Enter a character from a-z, A-Z, or a space.

Level: 15

Trigger: ON-ERROR

FRM-50002: Month must be between 1 and 12.

Cause: You entered an invalid month value in a date field.

Action: Enter a month value from 1 (for January) to 12 (for December).

Level: 15

Trigger: ON-ERROR

FRM-50003: Year must be in proper range.

Cause: You entered a year that is not valid for the applicable format mask year element.

Action: Enter a valid year. For most format mask year elements, a number between 0 and 9999 is acceptable. For signed format mask year elements, a number between -4712 and -1 may also be specified.

Level: 15

Trigger: ON-ERROR

FRM-50004: Day must be between 1 and last of month.

Cause: You entered an invalid day.

Action: Enter a valid day. For April, for example, enter a number between 1 and 30.

Level: 15

Trigger: ON-ERROR

FRM-50006: Legal characters are 0-9 + and -.

Cause: You entered an unacceptable character in a number item.

Action: Enter a valid number. A valid number has digits 0 through 9. A number may be preceded by a plus (+) or minus (-) sign. If the message allows it, a number may contain one decimal point at any location, except before the sign.

Level: 15

Trigger: ON-ERROR

FRM-50007: Too many digits after decimal point.

Cause: You entered a number with 3 or more decimal digits after the decimal point in an item with the MONEY or RMONEY data type.

Action: Re-enter a valid number.

Level: 15

Trigger: ON-ERROR

FRM-50009: Too many decimal points.

Cause: You entered a number that contains two or more decimal points, or you have entered a number that contains a decimal point in an item that requires a whole (non-decimal) number.

Action: Enter a number with no more than one decimal point. If you have used only one decimal, remove the decimal and the decimal part of the number.

Level: 15

Trigger: ON-ERROR

FRM-50010: Money format is [+-]9999999.99

Cause: You entered an invalid value in a MONEY or RMONEY item.

Action: Enter a valid value. This value should have zero or dollar digits, followed by a decimal and two cents digits. The entire number can be preceded by a plus (+) or a minus (-) sign.

Level: 15

Trigger: ON-ERROR

FRM-50011: Not a valid month name.

Cause: You entered an invalid month name in a date field.

Action: Enter a valid month name. Oracle Forms recognizes the first three characters of a month name. For example, JAN stands for January, JUN for June.

Level: 15

Trigger: ON-ERROR

FRM-50012: Date must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted date.

Action: Re-enter the date in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50013: Plus or minus must be in first position.

Cause: You entered the plus or minus sign in the wrong position.

Action: Retype with the plus or minus sign in the first position.

Level: 15

Trigger: ON-ERROR

FRM-50014: Bad exponent.

Cause: You entered an exponent in an item that does not accept exponents.

Action: Enter a value without an exponent.

Level: 15

Trigger: ON-ERROR

FRM-50016: Legal characters are 0-9 - + E .

Cause: You entered an unacceptable character in a number item.

Level: 15

Trigger: ON-ERROR

FRM-50017: Hour must be between 0 and 23.

Cause: You entered an invalid hour.

Action: Enter a valid hour. Oracle Forms records time on a 24-hour basis.

Level: 15

Trigger: ON-ERROR

FRM-50018: Minutes must be between 00 and 59.

Cause: You entered an invalid minute value.

Action: Enter a valid minute value.

Level: 15

Trigger: ON-ERROR

FRM-50019: Seconds must be between 00 and 59.

Cause: You entered an invalid value.

Action: Enter a value between 00 and 59.

Level: 15

Trigger: ON-ERROR

FRM-50020: Missing exponent.

Cause: You failed to enter an exponent.

Action: Enter an exponent.

Level: 15

Trigger: ON-ERROR

FRM-50021: Date must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted date.

Action: Re-enter the date in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50022: Time must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted time.

Action: Re-enter the time in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50023: Date must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted date.

Action: Re-enter the date in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50024: Space are allowed in leading positions only.

Cause: You entered spaces intermixed with data.

Action: Re-enter data with no spaces intermixed.

Level: 15

Trigger: ON-ERROR

FRM-50025: Date/time must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted date and time.

Action: Re-enter the date and time in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50026: Date must be entered in a format like %s.

Cause: You entered an invalid or incorrectly formatted date.

Action: Re-enter the date in the requested format.

Level: 15

Trigger: ON-ERROR

FRM-50027: Invalid format mask for given datatype.

Cause: The format mask you assigned to a text item is incompatible with the data type of the text item.

Action: Assign a new format mask to the text item. For more information, refer to help on <a href="../../designing_forms/items/f500842.html">About Formatting Text Item Values with Format Masks</a>.

Level: 15

Trigger: ON-ERROR

FRM-50028: Format mask not allowed for this datatype.

Cause: The data types LONG and IMAGE do not support a format mask.

Action: Do not try to create a format mask for data types LONG or IMAGE.

Level: 15

Trigger: ON-ERROR

FRM-50029: Too many digits preceding decimal point for scientific notation.

Cause: You specified a number using scientific notation, but used more than one digit preceding the decimal point.

Action: Re-enter the number using scientific notation.

Level: 15

Trigger: ON-ERROR

FRM-50045: Seconds past midnight confilicts with hour.

Cause: You entered a time where the seconds past midnight component does not agree with the hour component.

Action: Make sure the hour and seconds past midnight agree, or use a format mask without seconds past midnight.

Level: 15

Trigger: ON-ERROR

FRM-50048: New passwords do not match. Please make them identical.

Cause: You entered different strings in 'New Password' and 'Retype New' fields.

Action: Re-enter the values in (New and Retype) fields such that they identical.

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91126: fatal error in runtime process: invalid value %s specified for environment variable %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91127: runtime process: invalid directory name specified for environment variable %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91129: runtime process: no value specified for required environment variable %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91132: fatal error in runtime process: invalid data in timezone file %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91135: fatal error in runtime process: message file %s is missing

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-91137: runtime process: unable to open log file %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92000: internal error: cannot access Java class

Cause: The Forms server requested a Java class by specifying a numeric "handlerClassId", and the Forms Java client found an entry for the specified handlerClassId in the registry. However, the Java class that was specified by the registry entry could not be accessed.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause (e.g. a configuration problem), correct it. If the problem persists, contact Oracle Support Services.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92020: invalid URL %s sent to browser with target %s. full details: %s

Cause: The Forms application executed the web.showDocument built-in, and the applet did not define the clientBrowser parameter, which caused Forms to attempt to resolve the specified URL relative to the applet's document base. However, this attempt encountered a MalformedURLException. This is not a fatal error.

Action: Correct the URL that is passed to the web.showDocument built-in.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92022: cannot launch URL %s with target %s. full details: %s

Cause: The Forms application executed the web.showDocument built-in, and encountered an Exception. This is not a fatal error.

Action: If the "full details" messages indicates the problem, correct it. Otherwise, if the problem persists, contact Oracle Support Services.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92030: internal error: no registry entry for handleClassId=%s

Cause: The Forms server requested a Java class by specifying a numeric "handlerClassId", but the Forms Java client could not find an entry for the specified handlerClassId in the registry.

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

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92040: internal error: cannot find Java class

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92050: fatal error: cannot connect to the server: %s:%s

Cause: An attempt was made to connect to the Forms server. The serverURL applet parameter was not specified, so Forms attempted to connect to the specified host machine, on the specified port. (These are derived from the serverHost and serverPort applet parameters, if specified). However, an unexpected Exception was encountered. This message appears when there is no message that gives a more specific reason for the connection failure.

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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92052: fatal error: cannot connect to the server at URL %s

Cause: An attempt was made to connect to the Forms server, at the specified URL. (This is derived from the serverURL applet parameter). However, an unexpected Exception was encountered. This message appears when there is no message that gives a more specific reason for the connection failure.

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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92054: error while terminating single sign-on session with URL %s

Cause: An attempt was made to connect to the single sign-on server using OHS redirect, at the specified URL. However, an unexpected Exception was encountered. This message appears when there is no message that gives a more specific reason for the connection failure.

Action: The system administrator should ensure that OHS redirects are working properly.

Appears: Java console

Level: 99

Trigger: None

FRM-92055: error reading cookies while terminating single sign-on session

Cause: An attempt was made to read the cookies while terminating single sign-on session. However, an unexpected Exception was encountered. This message appears when there is no message that gives a more specific reason for the failure.

Action: Make sure that Javascript is enabled for the browser.

Appears: Java console

Level: 99

Trigger: None

FRM-92056: error reading cookies while checking life of single sign-on session

Cause: An attempt was made to read the cookies while checking life of single sign-on session. However, an unexpected Exception was encountered. This message appears when there is no message that gives a more specific reason for the failure.

Action: Make sure that Javascript is enabled for the browser.

Appears: Java console

Level: 99

Trigger: None

FRM-92060: fatal error: cannot connect to the server: bad machine specification: %s:%s

Cause: An attempt was made to connect to the Forms server. The serverURL applet parameter was not specified, so Forms attempted to connect to the specified host machine, on the specified port. (These are derived from the serverHost and serverPort applet parameters, if specified). However, the format of the host/port combination was invalid.

Action: Correct the syntax of the serverHost and/or the serverPort applet parameter, or specify a valid value for the serverURL applet parameter.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92062: fatal error: cannot connect to the server: bad URL specification: %s

Cause: An attempt was made to connect to the Forms server, at the specified URL. (This is derived from the serverURL applet parameter). However, the URL was malformed.

Action: Correct the syntax of the serverURL applet parameter.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92070: internal error: cannot instantiate Java class

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92080: fatal error: cannot execute command: %s %s. full details: %s

Cause: The Forms application executed the web.showDocument built-in, and the applet defined the clientBrowser parameter, which caused Forms to attempt to start the specified external client browser. However, this attempt encountered an Exception.

Action: If the "full details" messages indicates the problem, correct it. Otherwise, if the problem persists, contact Oracle Support Services.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92089: unexpected fatal error while initializing the applet's user interface

Cause: An unexpected Exception was encountered while attempting to initialize the applet's user interface.

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.

Appears: Java console, applet status window

Level: 99

Trigger: None

FRM-92090: unexpected fatal error in client-side Java code during startup

Cause: An unexpected Exception was encountered in client-side Java code during startup.

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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92091: unexpected fatal error in client-side Java code

Cause: An unexpected Exception was encountered in client-side Java code (after startup).

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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92095: Cannot obtain server certificate chain

Cause: SSL certificate(s) were not found on the server.

Action: Contact the server admin for SSL certificate(s).

Appears: Java console

Level: 99

Trigger: None

FRM-92102: A network error or server failure has occurred. The Forms client has attempted to reestablish its connection to the Server %s time(s) without success. You will need to restart your application.

Cause: The Forms Java client attempted to communicate with the Forms server. The indicated number of attempts (specified by the networkRetries applet parameter) were made, but each attempt encountered an unexpected Exception. This probably indicates a problem with the network, or with the application server that was hosting the Forms server, or with the server machine that was hosting the application server.

Action: Correct the network problem (if any), or restart the application server or reboot the server host machine (if necessary).

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92103: A network error or server failure has occurred. You will need to restart your application.

Cause: The Forms Java client attempted to communicate with the Forms server. The networkRetries applet parameter did not specify a positive value, so only a single attempt was made. This attempt encountered an unexpected Exception. This probably indicates a problem with the network, or with the application server that was hosting the Forms server, or with the server machine that was hosting the application server.

Action: Correct the network problem (if any), or restart the application server or reboot the server host machine (if necessary).

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92104: A network error or server failure has occurred. The request was sent to the wrong application server (not the one which created the session). The Forms client has attempted to migrate the session %s time(s) without success. You will need to restart your application.

Cause: The Forms Java client attempted to communicate with the Forms server. The indicated number of attempts were made, but on each attempt, the request was sent to the wrong application server (not the one which created the session). This probably indicates a problem with the network, or with the application server that was hosting the Forms server that initially created the session, or with the server machine that was hosting the application server.

Action: Correct the network problem (if any), or restart the application server or reboot the server host machine (if necessary).

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92110: New passwords do not match. They must be identical. Password change failed.

Cause: In the Change Password dialog, the new password and the retyped new password do not match.

Action: Retry the Change Password dialog, and correctly type and retype the new password.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92120: Fatal error: registry file %s is missing.

Cause: The Forms Java client was unable to read the registry file at the specified URL (on the Forms server machine).

Action: The system administrator should ensure that the registry file exists and is readable.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92130: JavaScript execution is disabled in an Oracle Forms Standalone Application.

Cause: JavaScript integration is not supported in an Oracle Forms Standalone Application.

Action: Use a browser if you want to run JavaScript integration with Oracle Forms.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92134: JavaFX not found, audio support disabled.

Cause: The JavaFX classes needed for audio support were not found.

Action: Install and configure JavaFX to run with your client-side Java installation.

Appears: Java console

Level: 99

Trigger: None

FRM-92135: No source file specified for Play_Audio.

Cause: URI String is null or does not exist.

Action: Check the value specified as media file name, it should not be null and file should exist at specified location.

Appears: Java console

Level: 99

Trigger: None

FRM-92136: Illegal URL format used in media file name %s.

Cause: Either URI has null scheme or its not a proper URI.

Action: Check the value specified as media file name.

Appears: Java console

Level: 99

Trigger: None

FRM-92137: Unsupported protocol specified for Play_Audio %s.

Cause: Unsupported protocol specified for the media source.

Action: Ensure that a supported protocol is being used for Play_Audio.

Appears: Java console

Level: 99

Trigger: None

FRM-92138: Malformed URL used in Play_Audio %s.

Cause: Incorrect/unsupported URL supplied as media source.

Action: Check the media URL and make the required correction in the URL format.

Appears: Java console

Level: 99

Trigger: None

FRM-92140: Media Error - %s MEDIA_CORRUPTED

Cause: The media appears to be invalid or corrupted.

Action: Validate the media file if its a valid media file. Also check, if its supported by javafx.scene.media.MediaPlayer.

Appears: Java console

Level: 99

Trigger: None

FRM-92141: Media Error - %s MEDIA_INACCESSIBLE

Cause: Although the media may exist, it is not accessible.

Action: Check the access rights are given to the user which is trying to access media file.

Appears: Java console

Level: 99

Trigger: None

FRM-92142: Media Error - %s MEDIA_UNAVAILABLE

Cause: Media does not exist or is otherwise unavailable.

Action: Check if media file is physically available at the specified location.

Appears: Java console

Level: 99

Trigger: None

FRM-92143: Media Error - MEDIA_UNSPECIFIED

Cause: Media has not been specified.

Action: Supply a valid media file name.

Appears: Java console

Level: 99

Trigger: None

FRM-92144: Media Error - %s MEDIA_UNSUPPORTED

Cause: Media type is not supported by this platform.

Action: Use one of the supported formats for the source media.

Appears: Java console

Level: 99

Trigger: None

FRM-92145: Media Error - OPERATION_UNSUPPORTED

Cause: An operation performed on the media is not supported by this platform.

Action: Operation user is trying to perform on media is not supported on this platform.

Appears: Java console

Level: 99

Trigger: None

FRM-92146: Media Error - PLAYBACK_ERROR

Cause: A playback error which does not fall into any of the other pre-defined categories.

Action: Contact your system administrator.

Appears: Java console

Level: 99

Trigger: None

FRM-92147: Media Error - PLAYBACK_HALTED

Cause: An unrecoverable error which has resulted in halting playback.

Action: Media player is in a halted state. Restart the application if media support is needed.

Appears: Java console

Level: 99

Trigger: None

FRM-92148: Media Error - %s UNKNOWN

Cause: An error has occurred for an unknown reason.

Action: Contact your system administrator.

Appears: Java console

Level: 99

Trigger: None

FRM-92150: Fatal error: web client version is too new.

Cause: The version of the client is newer than the version of the Server.

Action: The system administrator should ensure that the Forms product is correctly installed on the Forms server machine.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92160: Fatal error: web client version is too old.

Cause: The version of the client is older than the version of the Server.

Action: The system administrator should ensure that the Forms product is correctly installed on the Forms server machine.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92170: JavaScript execution is disabled during Java Web Start session.

Cause: JavaScript integration is not supported when running Java Web Start.

Action: Use a browser if you want to run JavaScript integration with Oracle Forms.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92180: Fatal error: JavaScript is unable to obtain the server URL. This can occur if legacy_lifecycle=true and JavaScript has been disabled. If so, you will need to reenable JavaScript, restart the browser, and restart your application.

Cause: The serverURL applet parameter specified a value of "?", which indicates that the serverURL should be obtained from an element outside of the applet. (In a page that's generated from a standard base HTML file, this occurs when legacy_lifecycle=true in formsweb.cfg). Forms attempted to obtain the serverURL using JavaScript, but the attempt failed, probably because JavaScript has been disabled.

Action: Reenable JavaScript and restart the browser. If that does not solve the problem, 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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92190: JavaScript is unable to evaluate expression.

Cause: The Forms application executed the web.JavaScript_Eval_Expr built-in, but an invalid Javascript expression was specified as the first argument.

Action: Correct the Javascript expression that is passed to the web.JavaScript_Eval_Expr built-in.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92192: Target %s for JavaScript evaluation does not exist.

Cause: The Forms application executed the web.JavaScript_Eval_Expr built-in, but an invalid target was specified as the second argument.

Action: Correct the target that is passed to the web.JavaScript_Eval_Expr built-in.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92193: error executing JavaScript while terminating single sign-on session

Cause: An attempt was made to terminate the single sign-on session using Javascript. However, an unexpected Exception was encountered.

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

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92210: invalid value %s for lookAndFeel applet parameter. Defaulting to %s.

Cause: An invalid value was specified for the lookAndFeel applet parameter.

Action: The system administrator should ensure that a valid value was specified for the lookAndFeel applet parameter.

Appears: Java console, applet status window

Level: 99

Trigger: None

FRM-92211: invalid value %s for colorScheme applet parameter. Forms will use the default colorScheme for the specified lookAndFeel.

Cause: An invalid value was specified for the colorScheme applet parameter.

Action: The system administrator should ensure that a valid value was specified for the colorScheme applet parameter.

Appears: Java console, applet status window

Level: 99

Trigger: None

FRM-92212: unable to process %s required for custom color scheme. Forms will not use custom color scheme.

Cause: Unable to locate registry file or it had some format issue.

Action: The system administrator should ensure that registry file is available and valid.

Appears: Java console

Level: 99

Trigger: None

FRM-92213: color parameter %s not defined in %s. Forms will not use custom color scheme.

Cause: A color parameter required for custom color scheme was undefined in registry file.

Action: The system administrator should ensure that registry file has all the required color parameters when custom color scheme configured.

Appears: Java console

Level: 99

Trigger: None

FRM-92214: invalid value for color parameter %s. Forms will not use custom color scheme.

Cause: An invalid value was defined for color property in registry file.

Action: The system administrator should ensure that color parameters has valid values defined.

Appears: Java console

Level: 99

Trigger: None

FRM-92215: invalid value for color parameter %s. Parameter will be ignored.

Cause: An invalid value was defined for color property in registry file.

Action: The system administrator should ensure that color parameters has valid values defined.

Appears: Java console

Level: 99

Trigger: None

FRM-92220: access to system clipboard denied

Cause: The system clipboard is locked by some other application. This generally indicates a problem with the other application. Note: If the allowAlertClipboard applet parameter is set to 'false', this message appears only on the Java console.

Action: Determine which application is locking the system clipboard, and terminate it (or terminate the action that's locking the clipboard). Then, if possible, correct the application so that it does not erroneously lock the system clipboard.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92290: HTTP response code %s received when attempting to download archive file

Cause: An error occurred on the attempt to download the file specified in the preceding 'Downloading archive file' message. The Oracle Forms Standalone Launcher was terminated.

Action: Check network connectivity. For a response code of 404, also verify that the file exists. If the problem persists, contact Oracle Support Services.

Appears: Java console

Level: 99

Trigger: None

FRM-92291: Unsupported Java version detected. Contact system administrator or download a supported Java version from: %s

Cause: The java version on client machine is not allowed.

Action: Install a supported java release or have the system administrator change the value of the fsalJavaVersion applet parameter

Appears: Java console

Level: 99

Trigger: None

FRM-92292: Required parameter fsalJavaVersion not set or is invalid.

Cause: The fsalJavaVersion parameter is not set or the format is incorrect.

Action: Check for the parameter and the format of it.

Appears: Java console

Level: 99

Trigger: None

FRM-92293: Unsupported Java version detected. Contact system administrator.

Cause: The java version on client machine is not allowed.

Action: Install a supported java release or have the system administrator change the value of the fsalJavaVersion applet parameter

Appears: Java console

Level: 99

Trigger: None

FRM-92310: Wrong password, try again

Cause: Password entered for TrustStore was wrong.

Action: Try again with new password.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92311: Wrong password, retry limit exceeded

Cause: Retry limit for entering TrustStore password was exceeded.

Action: Try again by restarting the Oracle Forms Standalone Application.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-92312: Password can not be blank

Cause: An empty password was entered.

Action: Try again with proper password.

Level: 99

Trigger: None

FRM-92313: Password changes only permitted when running in a terminal window

Cause: System console for accepting password was not available.

Action: Try running the application from a command prompt/terminal where console is available.

Level: 99

Trigger: None

FRM-92314: Unable to load certificate details

Cause: Certificate details failed to load.

Action: Try running the FSAL application with switch -showDetails 2, to check the details of SSL/TLS certificate. Meanwhile contact Oracle Support Services.

Level: 99

Trigger: None

FRM-92410: EndUserMonitoring initialization has failed. Verify that %s (specified by the applet parameter %s) is a valid URL.

Cause: EndUserMonitoring initialization failed, probably due to an invalid URL specified by the specified applet parameter (typically the EndUserMonitoringURL parameter). The applet parameter was ignored; EndUserMonitoring was then disabled and execution continued.

Action: The system administrator should ensure that a valid URL was specified for the specified applet parameter. If that does not solve the problem, 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.

Appears: Java console

Level: 99

Trigger: None

FRM-92411: EndUserMonitoring has failed, and will be disabled.

Cause: EndUserMonitoring was enabled, but a subsequent attempt to send a message to the EndUserMonitoring monitor encountered an unexpected Exception. EndUserMonitoring was then disabled, and execution continued.

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.

Appears: Java console

Level: 99

Trigger: None

FRM-92412: failure to send EndUserMonitoring data

Cause: EndUserMonitoring was enabled, but a subsequent attempt to send data to the EndUserMonitoring monitor was unsuccessful. Execution continued.

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

Appears: Java console

Level: 99

Trigger: None

FRM-92413: Update is needed, but automatic updating has been disabled by the administrator.

Cause: The checksum matching failed and autoupdate of Oracle Forms Standalone Launcher is disabled by the admin.

Action: Contact your system administrator to allow autoupdate of Oracle Forms Standalone Launcher.

Appears: Java console

Level: 99

Trigger: None

FRM-92420: could not find listener class %s

Cause: The class specified by the formsMessageListener applet parameter could not be found. The applet parameter was ignored, and execution continued.

Action: The system administrator should ensure that a valid class name was specified for the formsMessageListener applet parameter.

Appears: Java console

Level: 99

Trigger: None

FRM-92421: could not instantiate listener class %s

Cause: The class specified by the formsMessageListener applet parameter could not be instantiated. The applet parameter was ignored, and execution continued.

Action: The system administrator should ensure that a valid class name was specified for the formsMessageListener applet parameter.

Appears: Java console

Level: 99

Trigger: None

FRM-92422: could not initialize listener class %s

Cause: An unexpected Error was encountered while attempting to find and instantiate the class specified by the formsMessageListener applet parameter. The applet parameter was ignored, and execution continued.

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.

Appears: Java console

Level: 99

Trigger: None

FRM-92430: warning: invalid value %s ignored for parameter %s - defaulting to %s

Cause: The specified applet parameter (typically the asyncEventDelay parameter) did not specify a valid decimal number. A default value (5 seconds) was substituted, and execution continued.

Action: The system administrator should ensure that a valid decimal number was specified for the specified applet parameter.

Appears: Java console

Level: 99

Trigger: None

FRM-92431: warning: heartbeat or maxeventwait parameter value is less than 250ms

Cause: The value specified for the heartbeat or maxeventwait parameter specified a duration of under 250 milliseconds, which might cause problems.

Action: The system administrator should consider increasing the value to a more appropriate duration.

Appears: Java console

Level: 99

Trigger: None

FRM-92440: Thread %s has been interrupted while waiting for a message from the server.

Cause: The specified thread (in the Forms Java client) was interrupted while waiting for a message from the Forms server. This message identifies the thread, for diagnostic purposes. A fatal error subsequently occurs.

Action: No action is required for this message. (But action may be required for the subsequent fatal error).

Appears: Java console

Level: 99

Trigger: None

FRM-92450: Thread %s has been interrupted while waiting for a dialog to appear.

Cause: The specified thread was starting a dialog, and was interrupted while waiting for a dialog to appear. The wait was restarted.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92460: Thread %s has been interrupted while waiting for the LOV data fetching thread to die.

Cause: The specified thread had been fetching data for an LOV, but the end user accepted or canceled the LOV, so the thread requested a graceful death. But it was interrupted while the request was underway.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92470: unable to load image %s for image item

Cause: A requested image could not be loaded. A default image (indicating that the load failed) was substituted, and execution continued."

Action: If the error message specifies the name of the image file, verify that it exists, and is readable, and is in a valid image format.

Appears: Java console

Level: 99

Trigger: None

FRM-92471: unable to load image %s for iconic button item

Cause: A requested image could not be loaded. A default image (indicating that the load failed) was substituted, and execution continued."

Action: If the error message specifies the name of the image file, verify that it exists, and is readable, and is in a valid image format.

Appears: Java console

Level: 99

Trigger: None

FRM-92472: unable to load image %s for checkbox item

Cause: A requested image could not be loaded. A default image (indicating that the load failed) was substituted, and execution continued."

Action: If the error message specifies the name of the image file, verify that it exists, and is readable, and is in a valid image format.

Appears: Java console

Level: 99

Trigger: None

FRM-92473: unable to load image %s for radiobutton item

Cause: A requested image could not be loaded. A default image (indicating that the load failed) was substituted, and execution continued."

Action: If the error message specifies the name of the image file, verify that it exists, and is readable, and is in a valid image format.

Appears: Java console

Level: 99

Trigger: None

FRM-92474: unable to load image %s for alert

Cause: A requested image could not be loaded. A default image (indicating that the load failed) was substituted, and execution continued."

Action: If the error message specifies the name of the image file, verify that it exists, and is readable, and is in a valid image format.

Appears: Java console

Level: 99

Trigger: None

FRM-92480: Property %s: specified value has caused %s.

Cause: An attempt to set the value of an item property failed because the value was not of the proper type. The property was left unchanged, and execution continued. This error most commonly occurs when the application executes the SET_CUSTOM_PROPERTY built-in.

Action: Correct the value that is being passed to the SET_CUSTOM_PROPERTY built-in.

Appears: Java console

Level: 99

Trigger: None

FRM-92491: Unable to fetch archive file from server.

Cause: An Oracle Forms Standalone Application was attempting to fetch an archive file from the server but an error occurred.

It may fail due to following reasons:

1. Archive file does not exist.

2. Communication error.

Action: Ensure the following:

1. formsweb.cfg must have the parameter ARCHIVE defined.

2. Check network connectivity.

3. Change timeout value.

Appears: Java console

Level: 99

Trigger: None

FRM-92492: An erroneous applet definition containing <html> or <jnlp>, or with no configuration parameters, was received from the server. Its contents are shown below for diagnostic purposes:

Cause: The basesaafile configuration parameter apparently specified the wrong base text file, or raw HTML containing an error message from OHS or OAM was generated.

Action: Contact your system administrator.

Appears: Java console

Level: 99

Trigger: None

FRM-92493: Cannot open URL, java.awt.Desktop is not supported on this platform.

Cause: The java.awt.Desktop class is not supported on the platform.

Action: Run the Oracle Forms Standalone Application on a platform where the java.awt.Desktop class is supported.

Appears: Java console

Level: 99

Trigger: None

FRM-92494: Warning: Invalid timeout value. Continuing with default timeout value of %s milliseconds.

Cause: An invalid timeout value was encountered in the command line arguments for the Oracle Forms Standalone Launcher.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92495: Warning: Ignoring invalid archive URL %s.

Cause: The archive configuration or URL parameter specifies a single or a comma-separated list of values. The single value or one of the values was invalid, e.g. an absolute URL beginning with 'http:' or 'https:', but containing no '/'.

Action: Correct or remove the invalid archive URL.

Appears: Java console

Level: 99

Trigger: None

FRM-92496: 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.

Appears: Java console

Level: 99

Trigger: None

FRM-92497: Server returned HTTP response code %s

Cause: The Oracle Forms Standalone Launcher received an HTTP error response code when attempting to connect to the server, for example, 'Server returned HTTP response code 403--Forbidden'.

Action: Submit a valid request.

Appears: Java console

Level: 99

Trigger: None

FRM-92498: Warning: Invalid showDetails value. Continuing with default value of 0.

Cause: An invalid showDetails value was encountered in the command line arguments for the Oracle Forms Standalone Launcher.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92501: There is no active WebSocket session

Cause: An error occurred while trying to access the Session object.

Action: Initiate a WebSocket session.

Appears: Java console

Level: 99

Trigger: None

FRM-92502: An instance of WebSocket server is already running

Cause: An error occurred while starting a WebSocket server.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92503: Port number %s is in use. Please try a different port number.

Cause: An error occurred while trying to start WebSocket server on given port number.

Action: Provide a different port number.

Appears: Java console

Level: 99

Trigger: None

FRM-92504: A WebSocket session already exists

Cause: An error occurred while trying to initiate another WebSocket client session.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92505: Unable to initiate a WebSocket client session

Cause: An error occurred while trying to connect to the WebSocket server.

Action: Start WebSocket server if it has not yet started or check port number.

Appears: Java console

Level: 99

Trigger: None

FRM-92506: Given port number %s is invalid. Using default port number %s

Cause: An error occurred while trying to validate the given port number.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92507: WebSocket server is not running.

Cause: An error occurred while trying to access the WebSocket server object.

Action: Start WebSocket server.

Appears: Java console

Level: 99

Trigger: None

FRM-92508: Unable to download new Oracle Forms Standalone Launcher file.

Cause: A checksum mismatch error occurred while attempting to download new jar.

Action: A network interruption may have occurred. Try again or contact your administrator.

Appears: Java console

Level: 99

Trigger: None

FRM-92509: Unable to start the Oracle Forms Standalone Launcher process.

Cause: An error occurred while trying to start the Oracle Forms Standalone Launcher process.

Action: Try again and check file permissions.

Appears: Java console

Level: 99

Trigger: None

FRM-92510: Couldn't insert initial text.

Cause: An exception was thrown while attempting to render the UI dialog.

Action: Try again by relaunching the Oracle Forms Standalone Application and if problem persists, contact Oracle Support Services.

Appears: Java console

Level: 99

Trigger: None

FRM-92511: Unexpected error: %s

Cause: An unexpected exception was thrown while dealing with SSL/TLS.

Action: Try again by relaunching the Oracle Forms Standalone Application and if problem persists, contact Oracle Support Services.

Appears: Java console

Level: 99

Trigger: None

FRM-92512: Unable to load TrustStore

Cause: An exception was thrown while attempting to load or create a TrustStore file.

Action: Try again by relaunching the Oracle Forms Standalone Application and if problem persists, contact Oracle Support Services.

Appears: Java console

Level: 99

Trigger: None

FRM-92513: Access denied

Cause: The file did not have write permission.

Action: User should change the file permissions.

Appears: Java console

Level: 99

Trigger: None

FRM-92514: Cache directory %s not found or access to it failed

Cause: The directory was not present or did not have write permission.

Action: User should change the folder permissions.

Appears: Java console

Level: 99

Trigger: None

FRM-92522: forcing use of the native HTTP implementation

Cause: The useURLConnection applet parameter was specified as 'true' or 'yes'.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92523: forcing use of the Forms HTTP(S) implementation

Cause: The useURLConnection applet parameter was specified as 'false' or 'no'.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92530: error closing socket: %s

Cause: An unexpected Exception was encountered while attempting to close a socket. Execution continued.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92540: reallocating output buffer for native HTTP implementation

Cause: The native HTTP 'write' method was requested to write a block of data larger than its current output buffer. The buffer was reallocated, and execution continued.

Action: No action is required.

Appears: Java console

Level: 99

Trigger: None

FRM-92550: negative content-length on a response to a GET to URL %s

Cause: The Forms Java client issued a GET request to the Forms servlet. The result was a response with negative content-length. The fatal error FRM-92052 will subsequently appear.

Action: No action is required for this message. (But action may be required for the subsequent fatal error).

Appears: Java console

Level: 99

Trigger: None

FRM-92551: negative response (%s) to a read on behalf of a GET to URL %s

Cause: The Forms Java client issued a GET request to the Forms servlet. The result was a negative response. The fatal error FRM-92052 will subsequently appear.

Action: No action is required for this message. (But action may be required for the subsequent fatal error).

Appears: Java console

Level: 99

Trigger: None

FRM-92572: Forms HTTP connect has failed - giving up after %s attempts.

Cause: A Forms HTTP connect failed. The fatal error FRM-92050 (or possibly FRM-92060) will subsequently appear.

Action: No action is required for this message. (But action may be required for the subsequent fatal error).

Appears: Java console

Level: 99

Trigger: None

FRM-92574: Forms HTTP read has failed: %s

Cause: An unexpected Exception was encountered while attempting a native HTTP 'read'.

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.

Appears: Java console

Level: 99

Trigger: None

FRM-92575: SSL/TLS hostname verification of %s failed. Continuing at user''s request.

Cause: The user has requested to continue running (insecurely) even though SSL/TLS hostname verification failed.

Action: No action is required for this message but correcting the invalid SSL/TLS certificate is strongly encouraged.

Appears: Java console

Level: 99

Trigger: None

FRM-92576: SSL/TLS hostname verification has been disabled at user''s request.

Cause: The user specified the option "-bypassHostnameVerification true" when invoking the Forms Standalone Launcher.

Action: No action is required for this message, but specifying this option in a production system is strongly discouraged.

Appears: Java console

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93111: Cannot find Forms Servlet configuration file %s.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93112: error reading Forms Servlet configuration file %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93114: Forms Servlet configuration file %s contains invalid data.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93121: Cannot find environment variable configuration file %s.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93122: error reading environment variable configuration file %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93124: Environment variable configuration file %s contains invalid data.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93130: No base HTML file is specified.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93131: Cannot find base HTML file %s.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93132: error reading base HTML or JNLP file %s

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93134: No base JNLP file is specified.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93135: Cannot find base JNLP file %s.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93146: Oracle Forms Standalone Launcher version does not match server version %s.

Cause: Oracle Forms Standalone Launcher jar is outdated.

Action: Get the latest Oracle Forms Standalone Launcher file.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93150: The following restricted parameters cannot be specified in the URL: %s

Cause: The indicated parameters were specified by the end user (in a Forms Servlet URL).

Action: Remove the indicated parameters from the URL and resubmit.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93151: Restricted characters cannot be specified in the URL

Cause: Invalid characters were specified by the end user (in a Forms Servlet URL).

Action: Remove the invalid characters from the URL and resubmit.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: The system administrator has disabled new connections to the Forms Servlet.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93156: The Forms Servlet is unable to contact the Forms Load Balancing Server at %s:%s.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93218: fatal error reading client request content

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93240: Multiple Forms applications cannot share an HTTP session.

Cause: Either (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, or else (2) the Forms application was configured incorrectly.

Action: In case (1), select File, then New, then Browser Window (or Ctrl+N) in an Internet Explorer window that is not running a Forms application, or start a second instance of Internet Explorer. Otherwise, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93242: HTTP session not found on target server, probably because it has already been used.

Cause: You probably re-submitted a downloaded JNLP file that was created for Java Web Start with SSO enabled, or with the jnlpMatchIP configuration parameter set to true, or with the jnlpTimeout configuration parameter set to a non-zero value. Such JNLP files can be used only once.

Action: If you re-submitted a downloaded "one-shot" JNLP file, resubmit the original URL (that generated the JNLP file) from the browser. If the error occurred when submitting a URL from the browser, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93243: Static HTML is not allowed.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93245: HTTP session not found on target server; possible load balancer configuration issue.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93248: connection to the server apparently closed after a request had executed for %s seconds, probably due to an intermediate agent timing out

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93249: launch of browser window to be used for SSO authentication of an Oracle Forms Standalone application timed out after %s seconds

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93260: JNLP file has expired.

Cause: There was excessive delay launching a JNP file after the Web Start request that created it.

Action: Retry the Web Start request.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93261: JNLP file launched from unexpected IP address

Cause: The JNLP file was not launched from the IP address from which it was created (by a Web Start request).

Action: Launch the JNLP file from the IP address from which it was created.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93302: error running Forms in SSO mode.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93340: Session requires SSO user authentication.

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

Action: Re-login using SSO credentials.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: An attempt to dynamically create an SSO resource failed because the user specified a nonexistent configuration section.

Action: Specify the name of a valid configuration section in the base configuration file as the value of the config parameter.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93365: error running Forms in SSO mode

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93367: invalid parameters %s passed to the Forms Rad Servlet

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93380: unexpected error while attempting to redirect to Oracle Access Manager or the Forms Rad servlet

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93382: Oracle Access Manager login processing for an Oracle Forms Standalone application timed out after %s seconds

Cause: Oracle Access Manager login was not completed within the indicated time interval.

Action: If you aborted the application by closing the page, or intended to abort the application by closing the page, no action is required. If you completed the login after receiving this error message, the application was subsequently aborted, but you can retry launching it. [The login page won't be presented because you are already logged in]. If you intended to complete the login, retry launching the application and redoing the login within the indicated time interval. If that interval is insufficient, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93383: Resource Access Descriptor processing for an Oracle Forms Standalone application timed out after %s seconds

Cause: Submit or Cancel was not pressed in the Resource Access Descriptor page within the indicated time interval.

Action: If you aborted the application by closing the page, or intended to abort the application by closing the page or pressing Cancel, no action is required. If you intended to enter data (pressing Submit to complete the action), retry launching the application and reentering the data within the indicated time interval. If that interval is insufficient, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93384: SSO login for an Oracle Forms Standalone application completed, but the application was terminated.

Cause: This message may appear in a browser window which is performing SSO authentication for a Standalone application if you completed the SSO login after the SSO login page timed out or an error occurred in the startup process. A more specific message should appear in the terminal window from which the Standalone application was launched.

Action: Refer to the message in the terminal window from which the Standalone application was launched. If no such message appears or the Forms session is not being run as a Standalone application, and the problem persists, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93385: Resource Access Descriptor processing for an Oracle Forms Standalone application timed out, or was not performed due to an error in the startup process.

Cause: This message may appear in a browser window which is performing SSO authentication for a Standalone application if you pressed pressed Submit or Cancel after RAD processing timed out or an error occurred in the startup process. A more specific message should appear in the terminal window from which the Standalone application was launched.

Action: Refer to the message in the terminal window from which the Standalone application was launched. If the Forms session is not being run as a Standalone application, and the problem persists, contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93500: unexpected error while attempting to create the runtime process

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: The number of currently executing runtime processes has reached the limit that was set by the system administrator.

Action: Retry the application when the system is less heavily loaded.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93550: cannot connect to runtime process: no response from newly created runtime process

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93600: unexpected error while attempting to communicate with the client or the runtime process or an external service

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93618: fatal error reading data from runtime process

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93628: fatal error writing data to runtime process

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93652: The runtime process has terminated abnormally.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93830: Test cookie set. Details:%s

Cause: This is the normal output of the setcookie and setcookiesess commands.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93832: Found test cookie: %s=%s

Cause: The test cookie was found.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93834: Test cookie not found.

Cause: The test cookie was not found.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

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

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93841: Proctest: Process test starting with %s processes.

Cause: The Proctest command started.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93842: Proctest: Creating process %s.

Cause: The Proctest command started creating a runtime process.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93843: Proctest: Failure to create process %s - aborting test.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93844: Proctest: Connecting to process %s.

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

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93845: Proctest: Failure to connect to process %s - aborting test.

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93846: Proctest: unexpected error in process test

Cause: A fatal error occurred in the Forms server, which will require the attention of your system administrator.

Action: Contact your system administrator.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93847: Proctest: Number of processes started and connected to is %s.

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

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93848: Proctest: Stopping the %s 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.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93849: Proctest: Process test complete.

Cause: The Proctest command completed.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93860: em_result=%s|000

Cause: This is the normal output of the status command.

Action: No action is required.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93890: Trace: invalid Xlate parameter %s

Cause: The URL that contains the trace command also specifies a parameter that is not recognized by the Xlate utlity.

Action: Correct the URL.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93891: Trace: outputClass parameter value "%s" for Xlate cannot contain a ".".

Cause: The URL that contains the trace command specifies an invalid value for the outputClass parameter.

Action: Correct the URL that specifies the invalid parameter value.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93892: Trace: PID parameter value "%s" for Xlate cannot contain a "%s".

Cause: The URL that contains the trace command specifies an invalid value for the PID parameter.

Action: Correct the URL that specifies the invalid parameter value.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-93893: Trace: Xlate encountered an IO error

Cause: The Xlate utility encountered an IOException.

Action: Ensure that a valid PID parameter is specified.

Appears: Java console, alert

Level: 99

Trigger: None

FRM-99999: Error %s occurred. See the release notes file (relnotes) for information about this error.

Cause: An error occurred; the error is documented in the release notes file.

Action: See the release notes file.

Level: 25

Trigger: None