oracle自动关闭原因,大家好，帮忙看一下数据库是什么原因引起自动关闭的？

左志坚

936人浏览 · 2021-04-11 01:14:01

左志坚 · 2021-04-11 01:14:01 发布

Sun Aug 17 04:29:05 2008

Memory Notification: Library Cache Object loaded into SGA

Heap size 2289K exceeds notification threshold (2048K)

Details in trace file /oracle/oms/admin/LHOMS/udump/lhoms_ora_401644.trc

KGL object name :select * from ( select decode(ta.showStatus,1,'是','2','否') as showStatus,ta.previewId ,ta.wellId, ta.wellName, tb5.well_Series as wellSeries, tb5.note as noteYB,tb5.str2 as str2, ta.infoSource,ta.expectWorkingDate ,ta.actualWellDepth, ta.inclnation, ta.bitOutsize, ta.workContent, ta.oilThickness ,ta.wellEyeDia, ta.createOrgName, ta.gunTypeId, ta.gunType,ta.bulletTypeId, ta.bulletType,ta.holeDensity , ta.conveyanceType,ta.opsContent ,ta.preview_type ,ta.designWellDepth ,ta.synergicOrg,ta.constructionOrg, t

Sun Aug 17 04:29:05 2008

Memory Notification: Library Cache Object loaded into SGA

Heap size 2288K exceeds notification threshold (2048K)

Details in trace file /oracle/oms/admin/LHOMS/udump/lhoms_ora_401644.trc

Sun Aug 17 04:29:10 2008

Memory Notification: Library Cache Object loaded into SGA

Heap size 2325K exceeds notification threshold (2048K)

Details in trace file /oracle/oms/admin/LHOMS/udump/lhoms_ora_401644.trc

KGL object name :select * from ( select * from ( select decode(ta.showStatus,1,'是','2','否') as showStatus,ta.previewId ,ta.wellId, ta.wellName, tb5.well_Series as wellSeries, tb5.note as noteYB,tb5.str2 as str2, ta.infoSource,ta.expectWorkingDate ,ta.actualWellDepth, ta.inclnation, ta.bitOutsize, ta.workContent, ta.oilThickness ,ta.wellEyeDia, ta.createOrgName, ta.gunTypeId, ta.gunType,ta.bulletTypeId, ta.bulletType,ta.holeDensity , ta.conveyanceType,ta.opsContent ,ta.preview_type ,ta.designWellDepth ,ta.synergicOrg,ta.co

Sun Aug 17 06:02:09 2008

Starting background process EMN0

Sun Aug 17 06:02:10 2008

Shutting down instance: further logons disabled

EMN0 started with pid=23, OS id=1335532

Sun Aug 17 06:02:11 2008

Stopping background process CJQ0

Sun Aug 17 06:02:11 2008

Stopping background process QMNC

Sun Aug 17 06:02:14 2008

Stopping background process MMNL

Sun Aug 17 06:02:15 2008

Stopping background process MMON

Sun Aug 17 06:02:18 2008

Shutting down instance (immediate)

License high water mark = 206

Sun Aug 17 06:02:18 2008

Stopping Job queue slave processes

Sun Aug 17 06:02:18 2008

Job queue slave processes stopped

All dispatchers and shared servers shutdown

Sun Aug 17 06:02:30 2008

PMON failed to acquire latch, see PMON dump

Sun Aug 17 06:02:41 2008

PMON failed to acquire latch, see PMON dump

Sun Aug 17 06:05:08 2008

ALTER DATABASE CLOSE NORMAL

Sun Aug 17 06:05:09 2008

SMON: disabling tx recovery

SMON: disabling cache recovery

Sun Aug 17 06:05:13 2008

Shutting down archive processes

Archiving is disabled

Sun Aug 17 06:05:18 2008

ARCH shutting down

ARC1: Archival stopped

Sun Aug 17 06:05:23 2008

ARCH shutting down

ARC0: Archival stopped

Sun Aug 17 06:05:25 2008

Thread 1 closed at log sequence 2459

Successful close of redo thread 1

Sun Aug 17 06:05:56 2008

Completed: ALTER DATABASE CLOSE NORMAL

Sun Aug 17 06:05:56 2008

ALTER DATABASE DISMOUNT

Completed: ALTER DATABASE DISMOUNT

ARCH: Archival disabled due to shutdown: 1089

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

ARCH: Archival disabled due to shutdown: 1089

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

Sun Aug 17 06:11:46 2008

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Autotune of undo retention is turned on.

IMODE=BR

ILAT =61

LICENSE_MAX_USERS = 0

SYS auditing is enabled

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

= 500

sessions

= 555

__shared_pool_size

= 436207616

__large_pool_size

= 16777216

__java_pool_size

= 33554432

__streams_pool_size

= 0

sga_target

= 3221225472

control_files

= /oracle/oms/102_64/dbs/cntrl/control01.ctl, /oracle/oms/oradata/sysdata/cntrl/control02.ctl, /oracle/oms/oradata/undo/cntrl/control03.ctl

db_block_size

= 8192

__db_cache_size

= 1644167168

db_16k_cache_size

= 1073741824

compatible

= 10.2.0.1.0

log_archive_dest_1

= LOCATION=/oracle/oms/oraarch

log_archive_format

= %t_%s_%r.dbf

db_file_multiblock_read_count= 16

undo_management

= AUTO

undo_tablespace

= UNDOTBS1

remote_login_passwordfile= EXCLUSIVE

audit_sys_operations

= TRUE

db_domain

dispatchers

= (PROTOCOL=TCP) (SERVICE=LHOMSXDB)

utl_file_dir

= /oracle/oms

job_queue_processes

= 10

background_dump_dest

= /oracle/oms/admin/LHOMS/bdump

user_dump_dest

= /oracle/oms/admin/LHOMS/udump

core_dump_dest

= /oracle/oms/admin/LHOMS/cdump

audit_file_dest

= /oracle/oms/admin/LHOMS/adump

audit_trail

= DB

db_name

= LHOMS

open_cursors

= 300

pga_aggregate_target

= 1073741824

PMON started with pid=2, OS id=467000

PSP0 started with pid=3, OS id=561230

MMAN started with pid=4, OS id=552982

DBW0 started with pid=5, OS id=499760

LGWR started with pid=6, OS id=348246

CKPT started with pid=7, OS id=1261698

SMON started with pid=8, OS id=1695782

RECO started with pid=9, OS id=114856

CJQ0 started with pid=10, OS id=1065080

MMON started with pid=11, OS id=1617976

Sun Aug 17 06:11:47 2008

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

MMNL started with pid=12, OS id=1360058

Sun Aug 17 06:11:47 2008

starting up 1 shared server(s) ...

Sun Aug 17 06:11:48 2008

ALTER DATABASE

MOUNT

Sun Aug 17 06:11:54 2008

Setting recovery target incarnation to 1

Sun Aug 17 06:11:54 2008

Successful mount of redo thread 1, with mount id 2832495462

Sun Aug 17 06:11:54 2008

Database mounted in Exclusive Mode

Completed: ALTER DATABASE

MOUNT

Sun Aug 17 06:11:55 2008

ALTER DATABASE OPEN

Sun Aug 17 06:11:55 2008

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=16, OS id=1179776

Sun Aug 17 06:11:55 2008

ARC0: Archival started

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC1 started with pid=17, OS id=966826

Sun Aug 17 06:11:55 2008

Thread 1 opened at log sequence 2459

Current log# 3 seq# 2459 mem# 0: /oracle/oms/redolog/redo03.log

Current log# 3 seq# 2459 mem# 1: /oracle/oms/mirrlog/redo03m.log

Successful open of redo thread 1

Sun Aug 17 06:11:55 2008

ARC0: STARTING ARCH PROCESSES

Sun Aug 17 06:11:55 2008

ARC1: Becoming the 'no FAL' ARCH

ARC1: Becoming the 'no SRL' ARCH

Sun Aug 17 06:11:55 2008

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Sun Aug 17 06:11:55 2008

SMON: enabling cache recovery

Sun Aug 17 06:11:55 2008

ARC2: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

ARC0: Becoming the heartbeat ARCH

ARC2 started with pid=18, OS id=1675382

Sun Aug 17 06:11:56 2008

Successfully onlined Undo Tablespace 1.

Sun Aug 17 06:11:56 2008

SMON: enabling tx recovery

Sun Aug 17 06:11:56 2008

Database Characterset is ZHS16GBK

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

QMNC started with pid=20, OS id=1515730

Sun Aug 17 06:11:58 2008

Completed: ALTER DATABASE OPEN

Sun Aug 17 06:17:55 2008

Shutting down archive processes

Sun Aug 17 06:18:00 2008

ARCH shutting down

ARC2: Archival stopped

Sun Aug 17 06:41:34 2008

Memory Notification: Library Cache Object loaded into SGA

Heap size 2289K exceeds notification threshold (2048K)

腾讯云开发者社区

腾讯云面向开发者汇聚海量精品云计算使用和开发经验，营造开放的云计算技术生态圈。

更多推荐

Elasticsearch复杂数据类型终极指南：从入门到精通

Elasticsearch作为功能强大的搜索引擎，支持多种复杂数据类型，让开发者能够灵活处理各种结构化和非结构化数据。本文将带你全面了解Elasticsearch中的复杂数据类型，从基础概念到实际应用，助你轻松掌握数据建模的核心技巧。## 内部对象：构建层级化数据结构在Elasticsearch中，对象类型（Object）是最基础的复杂数据类型之一，用于表示具有嵌套关系的数据。例如，我们可

腾讯云开发者社区

终极指南：Flink SQL连接器版本管理从混乱到有序的升级之路

Apache Flink作为流处理领域的佼佼者，其SQL连接器的版本管理一直是开发者面临的核心挑战。本文将系统讲解Flink SQL连接器版本管理的最佳实践，帮助你轻松应对版本兼容性问题，实现从混乱到有序的升级之旅。## 连接器版本管理的常见痛点 😫在Flink应用开发中，连接器版本管理常常让开发者头疼不已。不同版本的连接器可能导致各种兼容性问题，例如API变更、功能差异甚至运行时错误。

腾讯云开发者社区

如何快速搭建Neon无服务器PostgreSQL：面向初学者的完整指南

Neon是一款革命性的无服务器PostgreSQL解决方案，它通过分离存储和计算层，实现了自动扩缩容、类代码式数据库分支以及零级扩展能力。本指南将帮助你从零开始搭建Neon开发环境，体验这款创新数据库的强大功能。## 准备工作：环境要求与依赖项在开始搭建Neon环境前，请确保你的系统满足以下要求：- Linux操作系统（推荐Ubuntu 20.04+或Debian 11+）- Git