oracle数据库切换问题,数据库双机自动切换问题

最新推荐文章于 2024-05-16 07:25:33 发布

乖乖女的老公

最新推荐文章于 2024-05-16 07:25:33 发布

阅读量486

点赞数

文章标签： oracle数据库切换问题

两台数据库做双机环境：VCS4.1[url=]ORACLE RDBMS Version: 11.1.0.6.0.，数据文件放在裸设备上OS:SUSE Linux Enterprise Server 10 (i586) 64位

现在遇到的问题是：业务量很小，但隔一段时间数据库就会自动切换，分析了alert日志，发现每天晚上22:00以后，数据库就会自动重启它的一些后台进

程，日志如下，想请教高手们，为什么oracle会隔一段时间自动关闭了呢？是11gR164位 suse版本有问题吗？

--正常情况下

Wed Nov 23 21:31:27 2011

Starting background process CJQ0

Wed Nov 23 21:31:27 2011

CJQ0 started with pid=30, OS id=1213

--异常情况下

Wed Nov 30 22:34:46 2011

Stopping background process SMCO

Stopping background process FBDA

Shutting down instance: further logons disabled

Wed Nov 30 22:34:48 2011

Stopping background process CJQ0

Stopping background process QMNC

Stopping background process MMNL

Stopping background process MMON

Shutting down instance (immediate)

License high water mark = 19

ALTER DATABASE CLOSE NORMAL

Wed Nov 30 22:34:51 2011

SMON: disabling tx recovery

SMON: disabling cache recovery

Wed Nov 30 22:34:52 2011

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

Thread 1 closed at log sequence 27

Successful close of redo thread 1

Completed: ALTER DATABASE CLOSE NORMAL

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

Wed Nov 30 22:34:53 2011

Stopping background process VKTM:

Wed Nov 30 22:35:00 2011

Instance shutdown complete--此时实例完全关闭

Wed Nov 30 22:40:16 2011

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Using LOG_ARCHIVE_DEST_1 parameter default value as /opt/oracle/product/11gR1/db/dbs/arch

Autotune of undo retention is turned on.

IMODE=BR

ILAT =36

LICENSE_MAX_USERS = 0

SYS auditing is disabled

Starting up ORACLE RDBMS Version: 11.1.0.6.0.

Using parameter settings in server-side pfile /opt/oracle/product/11gR1/db/dbs/initsuseora.ora

System parameters with non-default values:

processes = 300

spfile = "/dev/datavg/spfile"

sga_target = 512M

control_files = "/dev/datavg/control01"

control_files = "/dev/datavg/control02"

control_files = "/dev/datavg/control03"

db_block_size = 8192

compatible = "11.1.0.0.0"

undo_tablespace = "UNDOTBS1"

remote_login_passwordfile= "EXCLUSIVE"

db_domain = ""

audit_file_dest = "/opt/oracle/admin/suseora/adump"

audit_trail = "DB"

db_name = "suseora"

open_cursors = 300

pga_aggregate_target = 2680M

diagnostic_dest = "/opt/oracle"

Wed Nov 30 22:40:16 2011

PMON started with pid=2, OS id=9015

Wed Nov 30 22:40:16 2011

VKTM started with pid=3, OS id=9017 at elevated priority

VKTM running at (20)ms precision

Wed Nov 30 22:40:16 2011

DIAG started with pid=4, OS id=9021

Wed Nov 30 22:40:16 2011

DBRM started with pid=5, OS id=9023

Wed Nov 30 22:40:16 2011

PSP0 started with pid=6, OS id=9025

Wed Nov 30 22:40:16 2011

DSKM started with pid=7, OS id=9027

Wed Nov 30 22:40:16 2011

DIA0 started with pid=8, OS id=9029

Wed Nov 30 22:40:16 2011

MMAN started with pid=7, OS id=9031

Wed Nov 30 22:40:17 2011

DBW0 started with pid=9, OS id=9033

Wed Nov 30 22:40:17 2011

LGWR started with pid=10, OS id=9035

Wed Nov 30 22:40:17 2011

CKPT started with pid=11, OS id=9038

Wed Nov 30 22:40:17 2011

SMON started with pid=12, OS id=9040

Wed Nov 30 22:40:17 2011

RECO started with pid=13, OS id=9042

Wed Nov 30 22:40:17 2011

MMON started with pid=14, OS id=9044

Wed Nov 30 22:40:17 2011

MMNL started with pid=15, OS id=9046

ORACLE_BASE not set in environment. It is recommended

that ORACLE_BASE be set in the environment

Reusing ORACLE_BASE from an earlier startup = /opt/oracle

Wed Nov 30 22:40:17 2011

ALTER DATABASE MOUNT

Setting recovery target incarnation to 1

Successful mount of redo thread 1, with mount id 357503505

Database mounted in Exclusive Mode

Lost write protection disabled

Completed: ALTER DATABASE MOUNT

Wed Nov 30 22:40:21 2011

ALTER DATABASE OPEN

Thread 1 opened at log sequence 27

Current log# 3 seq# 27 mem# 0: /dev/datavg/redolog03

Successful open of redo thread 1

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

SMON: enabling cache recovery

Successfully onlined Undo Tablespace 2.

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Database Characterset is AL32UTF8

Opening with internal Resource Manager plan

Starting background process FBDA

Starting background process SMCO

Wed Nov 30 22:40:21 2011

FBDA started with pid=17, OS id=9070

Wed Nov 30 22:40:21 2011

SMCO started with pid=18, OS id=9072

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

Wed Nov 30 22:40:22 2011

QMNC started with pid=19, OS id=9077

Completed: ALTER DATABASE OPEN

Wed Nov 30 22:45:20 2011

Starting background process CJQ0

Wed Nov 30 22:45:20 2011

CJQ0 started with pid=26, OS id=10268

Setting Resource Manager plan SCHEDULER[0x2C0B]

EFAULT_MAINTENANCE_PLAN via scheduler window

Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter

另外，该系统还经常出现4030错误，见下面的日志，报空间不够，但通过对系统内存的监控，没发现有耗内存的进程，奇怪。

Error message: Linux-x86_64 Error: 28: No space left on device

Additional information: 1

Writing to the above trace file is disTue Aug 14 22:00:01 2012