ORA-600 [16606] Error From Database Level Triggers Using :OLD or :NEW Syntax [ID 1089801.1]
2013-06-17 15:52
816 查看
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Server - Enterprise Edition - Version: 8.1.5.0 to 11.2.0.2 - Release: 8.1.5 to 11.2Information in this document applies to any platform.
Symptoms
An ORA-600 [16606] error occurs on execution of a database level trigger, such as a logon trigger.The call stack for the ORA-600 [16606] will resemble:
kglsget kqlsget psdghi ph1pbv ph1gnt ph1ylx ph1lex plsql ph1run ph1drv phpsyn phpcmp pcicms2 pcicmp2 kkxcmp0 rpiswu2 kkxcmp kktcrt opiexe opiosq0 kpooprx kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o opimai_real main __start
Changes
The trigger has been updated to reference correlation variables :NEW or :OLD.Cause
This is due to incorrect use of PLSQL correlation names (:OLD & :NEW) in a trigger as identified inBug:8319488, as correlation names are only supported for row level DML triggers.
Solution
Correct the application code to remove use of the correlation names :OLD and/or :NEW in anything but row level (i.e. FOR EACH ROW) DML triggers.References
BUG:8319488 - ORA-600 [16606] WITH LOGON TRIGGERNOTE:138525.1 - ORA-600 [16606]
相关文章推荐
- ORA-16796: one or more properties could not be imported from the database [ID 358040.1]
- RMAN-04004: error from recovery catalog database: ORA-00942: table or view doesnot exist 解决方式
- ORA-16796: one or more properties could not be imported from the database [ID 358040.1]
- ORA-600 [504], ..., [Transaction Branch Allocation] Error When Using XA [ID 868527.1]
- [小e笔记]之翻译的翻&译文的译——Ora-600 [4193] WhenOpening Or Shutting Down A Database [ID 452662.1]
- ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver (文档 ID 752297.1)
- ORA-07445 or ORA-600 Errors With a Big Stack or a Corrupted Stack (文档 ID 1318825.1)
- [error] isNewPageLoaded found an old pageLoadError: Error: Current window or frame is closed!
- 【Oracle】切换数据库报错:SQLSyntaxErrorException: ORA-00904: "SYSRESOURC0_"."SENDORNOT": 标识符无效
- ORA-600 [kzsviver:1] Error On Setting Users’ Passwords [ID 554605.1]
- How to Find the Offending SQL from a ORA-600 or ORA-7445 Trace File (文档 ID 154170.1) 转到底部 In this
- Diagnosing and Resolving Error ORA-04031 on the Shared Pool or Other Memory Pools (文档 ID 146599.1)
- Move or migrate user accounts from old Linux server to a new Linux server
- Using Timer to get history values from EDNA database, an error is prompted in the page : "Sys.WebForms.PageRequestManagerTimeout
- Unable to connect to read only database, Getting error ORA-00604 ORA-16000 (Doc ID 461653.1)
- Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: [ID 301830.1]
- ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver (文档 ID 752297.1)
- RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
- java.sql.SQLSyntaxErrorException: ORA-00911: 无效字符 ``` *### SQL: SELECT COUNT(ID) AS VALU
- UNNAMED FILE ERROR IN STANDBY AFTER ADDING NEW FILE TO PRIMARY DATABASE – ORA-01111, ORA-01110, ORA-