- 最后登录
- 2017-5-4
- 在线时间
- 81 小时
- 威望
- 999
- 金钱
- 2391
- 注册时间
- 2013-9-11
- 阅读权限
- 150
- 帖子
- 1124
- 精华
- 5
- 积分
- 999
- UID
- 1220
|
1#
发表于 2017-4-12 18:49:25
|
查看: 1593 |
回复: 0
以下为alert.prod文件
/***/***/为目录名
Tue Sep 3 15:55:03 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_15424.trc:
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
Tue Sep 3 15:55:03 2002
Errors in file /***/***/proddb/8.1.6/admin/bdump/prod_qmn0_15099.trc:
ORA-00600: internal error code, arguments: [kcfrbd_2], [3], [3933375], [1], [96000], [96000], [], []
Tue Sep 3 15:55:05 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_15515.trc:
ORA-07445: exception encountered: core dump [ktsdsh()+468] [SIGBUS] [Invalid address alignment] [2808135451] [] []
ORA-07445: exception encountered: core dump [ktsdsh()+468] [SIGBUS] [Invalid address alignment] [2808135451] [] []
ORA-07445: exception encountered: core dump [ktsdsh()+468] [SIGBUS] [Invalid address alignment] [2808135451] [] []
ORA-00600: internal error code, arguments: [6002], [0], [0], [4], [2], [], [], []
Tue Sep 3 15:55:07 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_15565.trc:
ORA-07445: exception encountered: core dump [ktudhd()+176] [SIGBUS] [Invalid address alignment] [2838294593] [] []
ORA-07445: exception encountered: core dump [ktudhd()+176] [SIGBUS] [Invalid address alignment] [2838294593] [] []
ORA-07445: exception encountered: core dump [ktugusc()+460] [SIGBUS] [Invalid address alignment] [2838294607] [] []
Tue Sep 3 15:55:07 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_8053.trc:
ORA-07445: exception encountered: core dump [ssdgetcall()+52] [SIGBUS] [Invalid address alignment] [3029065726] [] []
ORA-07445: exception encountered: core dump [ssdgetcall()+52] [SIGBUS] [Invalid address alignment] [3029065726] [] []
ORA-07445: exception encountered: core dump [kdbcpss()+248] [SIGSEGV] [Address not mapped to object] [3029065728] [] []
Tue Sep 3 15:55:09 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_15424.trc:
ORA-00600: internal error code, arguments: [4042], [0], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
Tue Sep 3 15:55:10 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_8571.trc:
ORA-07445: exception encountered: core dump [ktsdsh()+468] [SIGBUS] [Invalid address alignment] [2881110049] [] []
Tue Sep 3 15:55:11 2002
Errors in file /***/***/proddb/8.1.6/admin/bdump/prod_pmon_15083.trc:
ORA-07445: exception encountered: core dump [kturxf()+184] [SIGBUS] [Invalid address alignment] [2894207255] [] []
Tue Sep 3 15:55:12 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_15424.trc:
ORA-00600: internal error code, arguments: [4042], [0], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
Tue Sep 3 15:55:13 2002
Errors in file /***/***/proddb/8.1.6/admin/udump/prod_ora_8556.trc:
ORA-07445: exception encountered: core dump [ktsdsh()+468] [SIGBUS] [Invalid address alignment] [2772115487] [] []
Tue Sep 3 15:55:24 2002
问题的最好解决方法是请求Oracle的技术支持。谁叫我等学艺不精呢
下面是Oraclemetalink的文章,这可能是Oracle BUG引起的问题。
Doc ID: Note:1032451.6
Subject: ORA-600 [4097]: WHEN RUNNING EXPORT, SQL*PLUS, OR TRYING TO ACCESS DATABASE
Type: PROBLEM
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 11-JUN-1997
Last Revision Date: 22-JAN-2002
Problem Description
===================
When running export, SQL*PLUS, or trying to access the database you receive the
following error:
ORA-600 [4097]
The database crashed and system rollback segment has problems with transaction
table.
Problem Explanation
===================
When accessing a rollback segment header to see if a transaction has been
committed you observe the XID given is in the future of the transaction table.
Ie: the WRAP of the XID is higher than the current WRAP number on the
RBS header.
Related Terms
=============
ORA 600 [4097], rollback segment, export, sqlplus
Solution Description
====================
This is [BUG:427389]
Workaround:
----------
- Drop all rollback segments, except for SYSTEM.
- Create default dummy 2nd system rollback segment.
- Create the same number of rollback segments, small ones, with different
names.
- Recreate the original rollback segments (they now should all have higher
segment numbers).
- Drop the small dummy rollback segments & the dummy system
rollback segment.
- Export & rebuild the database (this is mandatory).
Solution Explanation
====================
Every time you need to add a rollback segment, first create all of the dummy
segments again, to make sure they use up the old segment numbers. Then create
the new segment and drop all dummy segments.
References
==========
[BUG:427389] |
|