Oracle Forms Error Messages 列表05
FRM-40900: Unable to allocate record buffer. Clear form to continue.
Cause: Failed attempt to allocate memory for a fetched or new record. The remaining records that are queried are temporarily buffered on disk. This is an indication that no more temporary files can be written to the disk.
Action: Clear form and then attempt to continue. You may have to exit the form and then re-open. Also, make sure there is enough disk space and that you have write privileges to the disk drive and directory.
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
Cause: You passed an invalid property constant to a Get or Set property Built-in.
Action: Verify arguments.
Level: 99
Trigger: ON-ERROR
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
--刘轶鹤转
652
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
