问题描述: 一个客户的数据库从9201升级到9208之后,数据库alert日志中出现以下错误: Fri May 10 12:23:57 2013 Errors in file d:\oracle\admin\lssgsj\udump\lssgsj_ora_2960.trc: ORA-00600: interna

PL/SQL: Return types of Result Set variables or query do not match 如果游标结构不适合PL/SQL游标变量或者是实际的游标参数不同于游标形参的时候发生该异常 (针对PL/SQL DEVELOPER 环境下的ETL配置)检查

PL/SQL: numeric or value error: Bulk Bind: Truncated bind 在bulk collect 批处理插入的时候数值错误,检查仓库表源表对应列的数据类型是否对应

streams apply aborted by ORA-12801: error signaled in parallel query server P000                                                          

数据库启动失败,报告错误:ora-00600 kcratr1_lastbwr Sat Jun 12 11:22:54 2010 ALTER DATABASE OPEN Block change tracking file is current. Sat Jun 12 11:22:54 2010 Beginning crash recovery of 1 thread

ORA-600 [17147] [ID 138580.1] Modified 03-JUN-2010     Type REFERENCE     Status PUBLISHED Note: For additional ORA-600 related information please read Note:146580.1 PUR

Thu Jun  3 07:37:01 2010 Errors in file /opt/oracle/admin/crmdb/udump/crmdb1_ora_2941248.trc: ORA-00600: internal error code, arguments: [kole_t2u], [34], [], [], [], [], [], [] Thu Jun  3 07:37:

Tue Jan  5 12:00:29 2010 Errors in file /u01/oracle/admin/GAMIS/bdump/gamis2_j009_570624.trc: ORA-00600: internal error code, arguments: [15470], [0x7000007E6E76A60], [], [], [], [], [], [] Bug

lmon crash with ora-600[kclexpand_5] Oracle bug: Bug# 6658484 See Note:6658484.8 Instance crash / OERI[kclexpand_5] from DRM in RAC Fixed: 10.2.0.4.1, 10.2.0.5, 11.1.0.7 Bug 66584

在10.2.0.1中,我们使用dbms_transaction.local_transaction_id来获得XID,这个在某些时候,因为bug,会造成600错误。 下面是OracleSupport上面的解释: Bug 7330258  OERI[15470] during call to DBMS_TRANSAC

example: CREATE TABLE TEST_TAB (ID NUMBER,NAME VARCHAR2(10),MSG VARCHAR2(20)); SQL> INSERT INTO TEST_TAB VALUES(1,’A',’B'); 1 row inserted SQL> INSERT INTO TEST_TAB VALUES(2,̵

/oracle/app/product/9.2.0/admin/wzshhda/bdump/wzshhda_pmon_356550.trc Oracle9i Enterprise Edition Release 9.2.0.6.0 – 64bit Production With the Partitioning, OLAP and Oracle Data Mining optio

metalink: 756746.1 SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for