FRM-40400 TO FRM-40750
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. A fatal error occurred while
trying to fetch the next query record.
2. If you are connected to an
non-Oracle datasource through ODBC, the cursor loses its position in the result
set after a commit.
Action: Requery if
you are connected with a non-Oracle datasource. If not, 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-40656: Update cannot be made due to prior rollback. Clear
the record.
Cause: This record
was already updated, but when you attempted to commit your changes, a serious
error prevented this update or any further update or delete from being
performed. The error might have occurred due to one of the following reasons:
1. A deadlock forced the loss of row
locks.
2. The record had a database cluster
key, and the previous attempt to update the record in the database was rolled
back due to an error somewhere else in the form.
Action: You must
clear this record before you can commit any other transactions in the form.
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
No comments:
Post a Comment