标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,740)
- DB2 (22)
- MySQL (75)
- Oracle (1,590)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (161)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (582)
- Oracle安装升级 (95)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (84)
- PostgreSQL (27)
- pdu工具 (5)
- PostgreSQL恢复 (9)
- SQL Server (29)
- SQL Server恢复 (10)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- ORA-600 krhpfh_03-1208
- VMware勒索加密恢复(vmdk勒索恢复)
- ORA-39773: parse of metadata stream failed故障处理
- sql数据库备份失败—失败: 23(数据错误(循环冗余检查)
- vmdk文件被加密恢复(虚拟机文件加密)
- 差点被误操作的ORA-600 kcratr_nab_less_than_odr故障
- win平台19c 打patch遭遇2个小问题汇总
- pg单个数据库目录恢复-pdu恢复单个数据库目录数据
- pg删除数据恢复—pdu恢复pg delete数据
- .[OnlyBuy@cyberfear.com].REVRAC勒索mysql恢复
- 表dml操作权限授权给public,导致只读用户失效
- 21c数据库恢复遭遇ora-600 ktugct: corruption detected
- pg_control丢失/损坏处理
- 当前主流数据库版本服务支持周期-202503
- pg启动报invalid checkpoint record处理
- 删除redo导致ORA-00313 ORA-00312故障处理
- Navicat连接postgresql时出现column “datlastsysoid” does not exist错误解决
- aix磁盘损坏oracle数据库恢复
- pg误删除数据恢复(PostgreSQL delete数据恢复)
- PostgreSQL表文件损坏恢复—pdu恢复损坏的表文件
标签归档:ora-600 15419
PL/SQL Developer编译过程引起ora-600[15419]
数据库版本
SQL> select * from v$version; BANNER ---------------------------------------------------------------- Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production PL/SQL Release 9.2.0.8.0 - Production CORE 9.2.0.8.0 Production TNS for IBM/AIX RISC System/6000: Version 9.2.0.8.0 - Production NLSRTL Version 9.2.0.8.0 - Production
alert中发现错误
Sun Feb 5 16:32:33 2012 Errors in file /oracle9/app/admin/crm/udump/crm2_ora_2434040.trc: ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], [] ORA-06544: PL/SQL: internal error, arguments: [2603], [], [], [], [], [], [], [] ORA-06553: PLS-707: unsupported construct or internal error [2603] Sun Feb 5 16:32:33 2012 Trace dumping is performing id=[cdmp_20120205163233] Sun Feb 5 16:32:45 2012 Errors in file /oracle9/app/admin/crm/udump/crm2_ora_2732864.trc: ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], [] ORA-06544: PL/SQL: internal error, arguments: [2603], [], [], [], [], [], [], [] ORA-06553: PLS-707: unsupported construct or internal error [2603]
trace文件内容
----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- ksedmp+0148 bl ksedst 1029746FC ? ksfdmp+0018 bl 01FD4014 kgeriv+0118 bl _ptrgl kgesiv+0080 bl kgeriv FFFFFFFFFFF3AF0 ? 700000D072A1238 ? FFFFFFFFFFF3A80 ? 3592393502A3F478 ? 100112038 ? ksesic1+005c bl kgesiv 000000000 ? 700000000003BC8 ? 2FFFFFEFFFF40C8 ? 7000002E147A6E0 ? 110002A20 ? kkxexe+0308 bl ksesic1 3C3B00003C3B ? 000000001 ? 000000024 ? 102A1143C ? 000000009 ? 110362830 ? 000000002 ? 000007FFF ? opiexe+274c bl kkxexe 1103B5B50 ? opiodr+08cc bl _ptrgl rpidrus+008c bl opiodr 4103A2A20 ? 300000000 ? FFFFFFFFFFF6A70 ? 50000F618 ? skgmstack+00d0 bl _ptrgl rpidru+0090 bl skgmstack 0FFFF5F30 ? 1101FAF78 ? 110006448 ? FFFFFFFFFFF6AD8 ? 700000C7CF68900 ? rpiswu2+0358 bl _ptrgl rpidrv+07fc bl rpiswu2 700000C386E8718 ? 500000000 ? 1103B7908 ? FFFFFFFFFFF6E40 ? 000000000 ? 2E00000000 ? 1101E9CA8 ? 000000000 ? rpiexe+0034 bl rpidrv 5FFFF6A68 ? 400000A20 ? FFFFFFFFFFF6A70 ? 00000002E ? psdevnCallback+00d4 bl rpiexe FFFFFFFFFFF71D0 ? rpiswu2+0358 bl _ptrgl psdevn+0068 bl rpiswu2 700000C386E8718 ? 10803D00008 ? 000000000 ? 102A1BA98 ? 1103B7210 ? 2E00000008 ? 108000003D0 ? 000000000 ? pbedeevn+0350 bl _ptrgl pbeevnd+0198 bcl pevm_CHSNULL+01c0 FFFFFFFFFFF7370 ? 000000000 ? 100AE4A10 ? 000000000 ? 11035F738 ? 11035FB76 ? pfrrun+0ce4 bl pbeevnd 1103B7210 ? 1103B7278 ? 700000CE62919A6 ? peicnt+01b8 bl pfrrun 1103B7210 ? kkxexe+01f8 bl peicnt FFFFFFFFFFF8F80 ? 1103B7210 ? opiexe+274c bl kkxexe 1103B7908 ? opiall0+102c bl opiexe 4FFFFFFB0 ? FFFFFFFFFFFBBB0 ? FFFFFFFFFFFA0A0 ? kpoal8+0a78 bl opiall0 5EFFFFBED4 ? 22FFFFBC18 ? FFFFFFFFFFFA5B8 ? 000000000 ? FFFFFFFFFFFA508 ? 1102A6498 ? 5B00000070 ? 24000000007FFF ? opiodr+08cc bl _ptrgl ttcpip+0cc4 bl _ptrgl opitsk+0d60 bl ttcpip 11000CF90 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? opiino+0758 bl opitsk 000000000 ? 000000000 ? opiodr+08cc bl _ptrgl opidrv+032c bl opiodr 3C00000018 ? 4101FAF78 ? FFFFFFFFFFFF7B0 ? 0A000F350 ? sou2o+0028 bl opidrv 3C0C000000 ? 4A00E8B50 ? FFFFFFFFFFFF7B0 ? main+0138 bl 01FD3A28 __start+0098 bl main 000000000 ? 000000000 ? --------------------- Binary Stack Dump --------------------- ……………… SO: 700000c386e8718, type: 4, owner: 700000c3c7779a0, flag: INIT/-/-/0x00 (session) trans: 0, creator: 700000c3c7779a0, flag: (41) USR/- BSY/-/-/-/-/- DID: 0002-02FA-00A04E87, short-term DID: 0000-0000-00000000 txn branch: 0 oct: 47, prv: 0, sql: 700000d85e7a0d8, psql: 7000002615ef140, user: 46/DBMARK O/S info: user: yuyangah, term: LENOVO-C18854BA, ospid: 5624:5632, machine: WORKGROUP\LENOVO-C18854BA program: plsqldev.exe application name: PL/SQL Developer, hash value=1190136663 action name: 测试窗口 - procedure PRC_MARK_UP, hash value=3097949562 last wait for 'pipe get' blocking sess=0x0 seq=42 wait_time=122 handle address=700000cd07bddb8, buffer length=1000, timeout=e10 temporary object counter: 0
通过这里可以看出,WORKGROUP\LENOVO-C18854BA机上的yuyangah用户在使用PL/SQL Developer操作PRC_MARK_UP过程的时候,产生了该错误。查询mos[ID 436359.1]发现有相关记录
解决方法:
1.在编译包/过程/函数时,不要选中在pl/sql dev中的Tools > Preferences > Debugger >Add debug information when compiling
2.检查的版本pl/sql dev是否和数据库兼容,建议使用新版本