2,598
社区成员
发帖
与我相关
我的任务
分享今天突然发现数据库无法启动，用SQLPLUS手工启动，数据库可以mount,但无法OPEN，显示错误ora-00600,请教各位高手如何解决？
操作系统是digital unix 4,
数据库是oracle 8.1.5,
今天由于没有先关数据库就重启了系统，结果
数据库可以mount起来，就是无法open,
在
svrmgr>shutdown immediate
svrmgr>startup
后,错误码是
ORA-00600: internal error code, arguments: [3051], [82], [73], [], [], [],
[], []
ORA-00600: internal error code, arguments: [733], [8388688], [pga heap], [],[], [],[], []
请问各位大虾谁也碰到过同样的问题，是怎么解决的？
谢谢！
数据库是oracle 8.1.5,
今天由于没有先关数据库就重启了系统，结果
数据库可以mount起来，就是无法open,
在
svrmgr>shutdown immediate
svrmgr>startup
后,错误码是
ORA-00600: internal error code, arguments: [3051], [82], [73], [], [], [],
[], []
ORA-00600: internal error code, arguments: [733], [8388688], [pga heap], [],[], [],[], []
请问各位大虾谁也碰到过同样的问题，是怎么解决的？
谢谢！
...全文
请发表友善的回复…
发表回复
oym_123 2002-06-22
- 打赏
- 举报
我把数据库重装了，
谢谢各位
谢谢各位
45060203 2002-06-21
- 打赏
- 举报
关注
sun9989 2002-06-21
- 打赏
- 举报
可能是磁介质出了点毛病，
用以前备份过的数据文件覆盖一下，
恢复数据库，行不行。
用以前备份过的数据文件覆盖一下，
恢复数据库，行不行。
ATCG 2002-06-21
- 打赏
- 举报
检查是否有服进程不正常死机，可从alert.log得知
oym_123 2002-06-21
- 打赏
- 举报
错误信息只有这两条
谢谢
谢谢
oym_123 2002-06-21
- 打赏
- 举报
startup force我试过了，不行
sdjnlf 2002-06-19
- 打赏
- 举报
用startup force试一试
jljlwsy 2002-06-19
- 打赏
- 举报
你很倒霉，不过ora-00600不足以使你的数据库不能OPEN,应该还有别的错误信息。
xinpingf 2002-06-19
- 打赏
- 举报
If you receive an ORA-00600 message, report it as a software bug to customer support.
呵呵，我喜欢这个
呵呵，我喜欢这个
penitent 2002-06-19
- 打赏
- 举报
ORA-00600: internal error code, arguments: [num], [], [],[],[],[]
An actual message might appear as follows:
ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[]
Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.
In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.
If you receive an ORA-00600 message, report it as a software bug to customer support.
An actual message might appear as follows:
ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[]
Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.
In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.
If you receive an ORA-00600 message, report it as a software bug to customer support.
penitent 2002-06-19
- 打赏
- 举报
ORA-00600: internal error code, arguments: [num], [], [],[],[],[]
An actual message might appear as follows:
ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[]
Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.
In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.
If you receive an ORA-00600 message, report it as a software bug to customer support.
An actual message might appear as follows:
ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[]
Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.
In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.
If you receive an ORA-00600 message, report it as a software bug to customer support.
