Oracle Forms Error Messages 列表03

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

--刘轶鹤转

D Forms Error Messages

Oracle Forms Error Messages 列表03相关推荐

  1. 资料整理——Oracle数据库错误消息列表(Database Error Messages)

    问题: Oracle数据库中大概有多少条error message? 解答: 根据对Oracle官网资料(https://docs.oracle.com/cd/E11882_01/server.112 ...

  2. oracle 浏览器插件,ThinForms - for Oracle Forms, EBS, Discoverer

    应用介绍 TheThinFormsChromeextensionallowsyoutorunOracleFormsandOracleEBS(OracleFormsbased)applications, ...

  3. 在MingW上更新的G ++获取大量错误消息(G++ updated on MingW gets massive error messages)

    问 题 I'm on Windows 10 with MinGW, and recently updated my g++, using mingw-get update and mingw-get ...

  4. Docker安装指定版本异常:Error: Package: docker-ce-17.03.1.ce-1.el7.centos.x86_64 (docker-ce-stable)

    产生问题的安装步骤 sudo yum-config-manager -y --add-repo https://download.docker.com/linux/centos/docker-ce.r ...

  5. oracle form 6i菜单模块,利用DDE技术实现ORACLE FORMS 6i 中打开文件(如:EXCEL、WORD、图片、网页)的功能...

    一.产生前因: 在ITPUB论坛中有人提出:如何在FORMS 中实现超链接,如何在FORMS中直接打开文本文档及图片等类似问题. 二.参考资料: 1.从FORM中导出数据到EXCEL例子(Export ...

  6. Download Oracle Forms 6i

    To download Oracle Forms Developer 6i from Oracle click this link http://download.oracle.com/otn/nt/ ...

  7. PHP getimagesize(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL rou

    今天碰到客户应用服务器(CentOS)一个问题,使用getimagesize()时总是报错: PHP getimagesize(): SSL operation failed with code 1. ...

  8. Centos9 PHP Warning: copy(): SSL operation failed with code 1. OpenSSL Error messages:

    问题 执行php -r "copy('http://install.phpcomposer.com/installer', 'composer-setup.php');"后报错: ...

  9. Oracle分析函数一——函数列表

    Oracle 分析函数 Oracle 分析函数--函数列表 SUM         : 该函数计算组中表达式的累积和 MIN         : 在一个组中的数据窗口中查找表达式的最小值 MAX    ...

最新文章

  1. pandas使用rename函数重命名dataframe中数据列的名称、从而创建一个包含重复列名称的dataframe数据集
  2. springboot2稳定版本_Spring Boot 2.4 正式发布,重大调整
  3. 拷贝Python对象、浅拷贝、深拷贝
  4. MongoDB在Windows系统下的安装和启动
  5. 最优化学习笔记(十二)——基本共轭方向算法(续)
  6. 如何学习前端开发,有哪些前端教程,前端学习路线图?
  7. 拓端tecdat|R语言ARIMA集成模型预测时间序列分析
  8. 算法:258. Add Digits 各位相加
  9. 推荐-最新1000多个单机游戏下载,不用注册直接下载!(3)
  10. 图像渲染测试软件,3D渲染参数(测试图及光子图)
  11. 堡垒之夜显示连接不上服务器,堡垒之夜匹配提示未能连接到服务器 | 手游网游页游攻略大全...
  12. WinZip 18.0下载地址及注册码
  13. 人性观察,人类关系的基石
  14. JDBC与MYSQL数据库
  15. 磁共振神经根水成像_磁共振神经根水成像鉴别类肿瘤样椎间盘突出症与神经鞘瘤2例...
  16. 一秒批量修改文件扩展名(后缀名)
  17. 用glRotatef函数转动对象
  18. GitHub网站的主题设置
  19. 11.集合之List
  20. Orcle 12c DG 新特性---Far Sync

热门文章

  1. java event sourcing_使用Spring Cloud和Reactor在微服务中实现EventSourcing -解道Jdon
  2. DevOps Master课程总结:招聘DevOps工程师必问的12个问题
  3. FPGA零基础学习:半导体存储器和可编程逻辑器件简介
  4. php $this-%3euid,码 | 保利威帮助中心 - Part 3
  5. 重庆2020计算机考研科目,2020年计算机考研大纲原文
  6. 【UnityShader】凹凸映射之高度贴图和法线贴图
  7. Python-(生成由0到9组成的n位数字)
  8. 百度导航hd android,百度导航HD版
  9. 21天学通Java学习笔记-Day06
  10. crypto buuctf 还原大师