oracle数据库00603,ora-00603如何处理？

最新推荐文章于 2021-04-12 10:19:07 发布
最新推荐文章于 2021-04-12 10:19:07 发布
阅读量733 收藏
点赞数
文章标签： oracle数据库00603

Instance terminated by SMON, pid = 2048

Mon Apr 12 12:09:32 2010

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 2

Autotune of undo retention is turned on.

IMODE=BR

ILAT =18

LICENSE_MAX_USERS = 0

SYS auditing is disabled

ksdpec: called for event 13740 prior to event group initialization

Starting up ORACLE RDBMS Version: 10.2.0.1.0.

System parameters with non-default values:

processes                = 150

__shared_pool_size       = 138412032

__large_pool_size        = 4194304

__java_pool_size         = 4194304

__streams_pool_size      = 0

sga_target               = 1015021568

control_files            = C:\ORACLE\PRODUCT\ROCKET\CONTROL_C.CTL, D:\ORACLE\ORADATA\CONTROL_D.CTL, E:\ORACLE\ORADATA\CONTROL_E.CTL

db_block_size            = 8192

__db_cache_size          = 859832320

compatible               = 10.2.0.1.0

log_archive_dest_1       = LOCATION=G:\oracle\oradata

log_archive_format       = ARC%S_%R.%T

db_file_multiblock_read_count= 16

db_recovery_file_dest    = F:\oracle\oradata

db_recovery_file_dest_size= 2147483648

undo_management          = AUTO

undo_tablespace          = UNDO

remote_login_passwordfile= EXCLUSIVE

db_domain                =

dispatchers              = (protocol=TCP)

shared_servers           = 10

job_queue_processes      = 10

audit_file_dest          = C:\ORACLE\PRODUCT\ADMIN\ROCKET\ADUMP

background_dump_dest     = C:\ORACLE\PRODUCT\ADMIN\ROCKET\BDUMP

user_dump_dest           = C:\ORACLE\PRODUCT\ADMIN\ROCKET\UDUMP

core_dump_dest           = C:\ORACLE\PRODUCT\ADMIN\ROCKET\CDUMP

db_name                  = rocket

open_cursors             = 300

pga_aggregate_target     = 337641472

PMON started with pid=2, OS id=2468

PSP0 started with pid=3, OS id=2732

MMAN started with pid=4, OS id=2736

DBW0 started with pid=5, OS id=2740

LGWR started with pid=6, OS id=2744

CKPT started with pid=7, OS id=2748

SMON started with pid=8, OS id=2752

RECO started with pid=9, OS id=2756

CJQ0 started with pid=10, OS id=2760

MMON started with pid=11, OS id=2764

Mon Apr 12 12:09:32 2010

starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

MMNL started with pid=12, OS id=2768

Mon Apr 12 12:09:32 2010

starting up 10 shared server(s) ...

Mon Apr 12 12:09:33 2010

ALTER DATABASE   MOUNT

Mon Apr 12 12:09:37 2010

Setting recovery target incarnation to 1

Mon Apr 12 12:09:37 2010

Successful mount of redo thread 1, with mount id 2257082749

Mon Apr 12 12:09:37 2010

Database mounted in Exclusive Mode

Completed: ALTER DATABASE   MOUNT

Mon Apr 12 12:09:37 2010

ALTER DATABASE OPEN

Mon Apr 12 12:09:37 2010

Beginning crash recovery of 1 threads

parallel recovery started with 3 processes

Mon Apr 12 12:09:38 2010

Started redo scan

Mon Apr 12 12:09:38 2010

Completed redo scan

349 redo blocks read, 40 data blocks need recovery

Mon Apr 12 12:09:38 2010

Started redo application at

Thread 1: logseq 418, block 78

Mon Apr 12 12:09:38 2010

Recovery of Online Redo Log: Thread 1 Group 1 Seq 418 Reading mem 0

Mem# 0 errs 0: C:\ORACLE\PRODUCT\ROCKET\REDO_C.LOG

Mon Apr 12 12:09:38 2010

Completed redo application

Mon Apr 12 12:09:38 2010

Completed crash recovery at

Thread 1: logseq 418, block 427, scn 20793331

40 data blocks read, 40 data blocks written, 349 redo blocks read

Mon Apr 12 12:09:38 2010

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=28, OS id=2824

Mon Apr 12 12:09:38 2010

ARC0: Archival started

ARC1 started with pid=29, OS id=2832

Mon Apr 12 12:09:38 2010

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

Thread 1 advanced to log sequence 419

Thread 1 opened at log sequence 419

Current log# 2 seq# 419 mem# 0: D:\ORACLE\ORADATA\REDO_D.LOG

Successful open of redo thread 1

Mon Apr 12 12:09:39 2010

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Mon Apr 12 12:09:39 2010

ARC1: STARTING ARCH PROCESSES

Mon Apr 12 12:09:39 2010

ARC0: Becoming the 'no FAL' ARCH

ARC0: Becoming the 'no SRL' ARCH

Mon Apr 12 12:09:39 2010

SMON: enabling cache recovery

Mon Apr 12 12:09:39 2010

ARC2: Archival started

Mon Apr 12 12:09:39 2010

ARC1: STARTING ARCH PROCESSES COMPLETE

ARC1: Becoming the heartbeat ARCH

Mon Apr 12 12:09:39 2010

Successfully onlined Undo Tablespace 1.

Mon Apr 12 12:09:39 2010

SMON: enabling tx recovery

Mon Apr 12 12:09:39 2010

Database Characterset is ZHS16GBK

ARC2 started with pid=30, OS id=2836

Mon Apr 12 12:09:40 2010

Errors in file c:\oracle\product\admin\rocket\udump\rocket_ora_2828.trc:

ORA-00600: 内部错误代码, 参数: [4194], [77], [82], [], [], [], [], []

DEBUG: Replaying xcb 0x4b38be8c, pmd 0x4a9388dc for failed op 8

Doing block recovery for file 2 block 55

No block recovery was needed

Mon Apr 12 12:13:14 2010

Errors in file c:\oracle\product\admin\rocket\udump\rocket_ora_2828.trc:

ORA-00600: 内部错误代码, 参数: [4194], [77], [82], [], [], [], [], []

ORA-00600: 内部错误代码, 参数: [4194], [77], [82], [], [], [], [], []

Mon Apr 12 12:13:18 2010

DEBUG: Replaying xcb 0x4b38be8c, pmd 0x4a9388dc for failed op 8

Mon Apr 12 12:13:18 2010

Errors in file c:\oracle\product\admin\rocket\udump\rocket_ora_2828.trc:

ORA-00600: 内部错误代码, 参数: [4194], [77], [82], [], [], [], [], []

ORA-00600: 内部错误代码, 参数: [4194], [77], [82], [], [], [], [], []

Doing block recovery for file 2 block 55

No block recovery was needed

Mon Apr 12 12:13:21 2010

Errors in file c:\oracle\product\admin\rocket\udump\rocket_ora_2828.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-00600: internal error code, arguments: [4194], [77], [82], [], [], [], [], []

ORA-00600: internal error code, arguments: [4194], [77], [82], [], [], [], [], []

Mon Apr 12 12:16:52 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_smon_2752.trc:

ORA-00600: internal error code, arguments: [4194], [77], [82], [], [], [], [], []

Mon Apr 12 12:16:55 2010

DEBUG: Replaying xcb 0x4b38be8c, pmd 0x4a9388dc for failed op 8

Mon Apr 12 12:16:56 2010

Non-fatal internal error happenned while SMON was doing shrinking of rollback segments.

SMON encountered 1 out of maximum 100 non-fatal internal errors.

Mon Apr 12 12:16:56 2010

Doing block recovery for file 2 block 55

No block recovery was needed

Mon Apr 12 12:20:27 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_pmon_2468.trc:

ORA-00600: internal error code, arguments: [4194], [77], [82], [], [], [], [], []

Mon Apr 12 12:20:30 2010

DEBUG: Replaying xcb 0x4b38be8c, pmd 0x4a9388dc for failed op 8

Doing block recovery for file 2 block 55

No block recovery was needed

Mon Apr 12 12:20:30 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_pmon_2468.trc:

ORA-00600: internal error code, arguments: [4194], [77], [82], [], [], [], [], []

Mon Apr 12 12:20:30 2010

PMON: terminating instance due to error 472

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_mman_2736.trc:

ORA-00472: PMON  process terminated with error

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_psp0_2732.trc:

ORA-00472: PMON  process terminated with error

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_reco_2756.trc:

ORA-00472: PMON  process terminated with error

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_lgwr_2744.trc:

ORA-00472: PMON  process terminated with error

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_dbw0_2740.trc:

ORA-00472: PMON  process terminated with error

Mon Apr 12 12:20:32 2010

Errors in file c:\oracle\product\admin\rocket\bdump\rocket_ckpt_2748.trc:

ORA-00472: PMON  process terminated with error

李茂宗
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Oracle报错ORA-00603 ORA-00600[4193]错误 解决方案
ZSY老司机的博客
10-02 3639
5、删除原有的undo tablespace创建新的undo tablespace。根据MOS介绍，此故障一般和undo segment有关。1、在做了redo log当前日志组被破坏恢复的测试后。2、启动数据库后出现ORA-600 【4193】的错误。查看告警日志，数据库启动正常，问题解决！3、通过pfile启动Instance。6、关闭数据库，重新通过spfle启动。1、通过spfile生成pfile。2、编辑pfile文件。3、数据库被强制关闭。
ORA-00603 解决方法
热门推荐
Cavenaghi 的专栏
05-18 2万+
     今天发现在使用OracleConnection连接ORACLE数据库的过程中突然出现连接不上的情况，dotNetFramework返回ORA-00603错误。     ORA-00603: ORACLE 服务器会话因致命错误而终止。     然后跟踪到trace日志。发现如下异常。         ksedmp: internal or fatal error ORA
ORA-00603: ORACLE server session terminated by fatal error
sap basis的blog
05-14 1万+
ORA-00603: ORACLE server session terminated by fatal error 后台错误中发现是UNDO的问题 ORA-00600: internal error code, arguments: [4194], [98], [75], [], [], [], [], [] 解决办法 1、通过错误信息可以确定当前回滚段是1-10，所以修改PFILE文件
数据库报ora-00603 ora-ora27504 (转)
cqwf95925的博客
07-02 341
环境是: OS:AIX 5304 HA:5.2 ORACLE 9206 RAC 2 NODES ALERT日志报错: ORA-00603: ORACLE server session terminated by ...
ORA-00600 internal error code, arguments [1265]和ORA-00603 ORACLE server session terminated by fatal
娜然的专栏
06-25 2773
晚上收到数据报警： Errors in file /app/oracle/admin/xxxxx/udump/xxxxx_ora_22467.trc: ORA-00600: internal error code, arguments: [1265], [0xADE975850], [], [], [], [], [], [] Tue Jun 24 22:00:45 CST 2014 Er
连接Oracle数据库时报ORA-12541:TNS:无监听程序的图文解决教程
09-10
主要介绍了连接Oracle数据库时报ORA-12541:TNS:无监听程序的图文解决教程,非常不错，具有参考借鉴价值，需要的朋友可以参考下
Oracle数据库发生ORA-04031错误原因浅析及处理.pdf
10-09
Oracle数据库发生ORA-04031错误原因浅析及处理 Oracle数据库是甲骨文公司提供的一种分布式数据库管理系统，以分布式数据库为核心的软件产品。它具有完整的数据管理功能，作为一个关系数据库，它是一个非常实用的...
解决 navicat连接oracle报错：ORA-12737InstantClientLight
07-06
然而，有时在使用Navicat连接Oracle数据库时可能会遇到各种问题，如"ORA-12737 InstantClientLight"错误。本文将深入探讨这个错误及其解决方案，同时也会涉及Navicat与Oracle的集成以及InstantClient的相关知识。 ...
Oracle数据库中ora-12899错误的解决方法
09-09
在Oracle数据库操作中，我们可能会遇到各种错误代码，其中之一便是ORA-12899错误。这个错误通常出现在数据导入过程中，特别是在不同字符集之间进行数据迁移时。当尝试将一个字符集（如ZHS16GBK）中的数据导入到另一...
断电后，oracle数据库启动不了
08-13
NULL 博文链接：https://huangshanghua.iteye.com/blog/2307671
oracle故障分析报告,Oracle 数据库异常宕机错误分析：ORA-01092
weixin_29533307的博客
04-03 2378
在数据库运维中，也许每一个DBA都很怕ORA-600，导致600错误的原因常常难觅踪迹，大部分情况下可能是由bug导致的，因此成为广大DBA的噩梦。但是遇到ORA-600的机会并不会很高。根据Bethune智能诊断平台对于中国Oracle数据库用户使用现状分析报告，我们发现，实例异常宕机的相关错误总结如下：(图为2016年非完全统计结果，仅供参考)从以上结果看出，I/O类报错和异常宕机相关性最⾼，...
oracle19c启动报错00603,19c redo异常 – 提供7*24专业数据库(Oracle,SQL Server,MySQL等)恢复和Oracle技术服务@Tel:+86 134296487...
weixin_30802367的博客
04-12 516
对于19c在pdb情况下三种常见故障进行了模拟测试:模拟19c数据库redo异常恢复模拟19c数据库pdb undo异常恢复模拟19c数据库root pdb undo异常恢复模拟oracle 19c数据库redo丢失的恢复操作,模拟数据库有事务,在没有提交的情况下redo丢失故障[oracle@localhost oradata]$ ssSQL*Plus: Release 19.0.0.0.0 -...
oracle的后台进程杀掉会有什么影响
anshejd70787的博客
05-14 623
以下练习出自于DBA思想的天空： 数据库版本为： 10.2.0.1.0在启动数据库之后，出现的进程为 oracle 20037 1 0 06:46 ? 00:00:00 ora_pmon_orcl oracle 20039 1 0 06:46 ? 00:00:00 ora_psp0_orcl orac...
因为存储离线造成的ORA-600(2662)错误的解决
一名DBA的学习和成长记录
08-18 4495
前两天同事在测试DATA GUARD的时候将主库的ONLINE日志意外覆盖，造成数据库无法打开，采用隐含参数的方法打开又碰到ORA-600错误，最后采用设置EVENTS的方式解决。 由于是在别人的机器上操作，而且很多操作都是摸索进行，因此没有将操作记录下来。现在打算重现一下问题并简单记录解决过程。 上篇已经描述了问题的产生步骤，下面描述解决这个问题的方法。 ORA-600(2662)错误的重
Oracle安全警示录:加错裸设备导致redo异常
weixin_34337265的博客
05-30 62
2019独角兽企业重金招聘Python工程师标准>>> ...
undo异常总结和恢复思路
u012388497的专栏
04-03 2028
UNDO异常报错千奇百怪,针对本人遇到的比较常见的undo异常报错进行汇总，仅供参考，数据库恢复过程是千奇百怪的，不能照搬硬套.    ORA-00704/ORA-00376    ORA-00704: bootstrap process failure    ORA-00604: error occurred at recursive SQL level 2    ORA
python 连接oracle数据库报错ORA-12154
最新发布
10-28
Python连接Oracle数据库报错ORA-12154通常是由于连接字符串配置不正确导致的。可以尝试以下几个解决方法： 1. 确认连接字符串是否正确，包括主机名、端口号、服务名等信息是否填写正确。 2. 确认Oracle客户端是否...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值