从alert日志中看数据库启动数据启动的三个过程

﹏ヽ暗。殇╰゛Y 2022-06-11 02:54 84阅读 0赞

1. 启动数据库到nomount 此时oracle会读取初始化参数文件分配内存（SGA）启动一系列的后台进程

Oracle读取初始化参数文件windows中到$ORACLE\_HOME/database、linux中到$ORACLE\_HOME/dbs中依次去读取spfile<SID>.ora ——>spfile.ora ——>init<SID>.ora如果都没有oracle启动失败

SQL> startup nomount

ORACLE  例程已经启动。

Total System Global Area  326414336 bytes

Fixed Size                  1374388 bytes

Variable Size             243271500 bytes

Database Buffers           75497472 bytes

Redo Buffers                6270976 bytes

SQL>

对应alert日志：

Starting ORACLE instance (normal)

LICENSE\_MAX\_SESSION = 0

LICENSE\_SESSIONS\_WARNING = 0

Picked latch-free SCN scheme 2

Using LOG\_ARCHIVE\_DEST\_1 parameter default value as USE\_DB\_RECOVERY\_FILE\_DEST

Autotune of undo retention is turned on.

IMODE=BR

ILAT =27

LICENSE\_MAX\_USERS = 0

SYS auditing is disabled

Starting up:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options.

Using parameter settings in server-side spfile D:\\APP\\WWANG\\PRODUCT\\11.2.0\\DBHOME\_1\\DATABASE\\SPFILEMDSP.ORA

System parameters with non-default values:

processes                = 150

shared\_pool\_size         = 0

nls\_language             = "SIMPLIFIED CHINESE"

nls\_territory            = "CHINA"

memory\_target            = 312M

control\_files            = "D:\\APP\\WWANG\\ORADATA\\MDSP\\CONTROL01.CTL"

control\_files            = "D:\\APP\\WWANG\\FLASH\_RECOVERY\_AREA\\MDSP\\CONTROL02.CTL"

db\_block\_size            = 8192

compatible               = "11.2.0.0.0"

db\_recovery\_file\_dest    = "D:\\app\\wwang\\flash\_recovery\_area"

db\_recovery\_file\_dest\_size= 1G

undo\_tablespace          = "UNDOTBS1"

remote\_login\_passwordfile= "EXCLUSIVE"

db\_domain                = ""

dispatchers              = "(PROTOCOL=TCP) (SERVICE=mdspXDB)"

audit\_file\_dest          = "D:\\APP\\WWANG\\ADMIN\\MDSP\\ADUMP"

audit\_trail              = "DB"

db\_name                  = "mdsp"

open\_cursors             = 300

diagnostic\_dest          = "D:\\APP\\WWANG"

Thu Jun 02 22:43:04 2011

PMON started with pid=2, OS id=2992

Thu Jun 02 22:43:04 2011

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

VKTM running at (10)millisec precision with DBRM quantum (100)ms

Thu Jun 02 22:43:04 2011

GEN0 started with pid=4, OS id=2388

Thu Jun 02 22:43:04 2011

DIAG started with pid=5, OS id=3724

Thu Jun 02 22:43:04 2011

DBRM started with pid=6, OS id=3736

Thu Jun 02 22:43:04 2011

PSP0 started with pid=7, OS id=3040

Thu Jun 02 22:43:04 2011

DIA0 started with pid=8, OS id=3044

Thu Jun 02 22:43:04 2011

MMAN started with pid=9, OS id=2692

Thu Jun 02 22:43:04 2011

DBW0 started with pid=10, OS id=3032

Thu Jun 02 22:43:04 2011

LGWR started with pid=11, OS id=3960

Thu Jun 02 22:43:04 2011

CKPT started with pid=12, OS id=3056

Thu Jun 02 22:43:04 2011

SMON started with pid=13, OS id=3144

Thu Jun 02 22:43:04 2011

RECO started with pid=14, OS id=2608

Thu Jun 02 22:43:04 2011

MMON started with pid=15, OS id=2452

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

starting up 1 shared server(s) ...

ORACLE\_BASE from environment = D:\\app\\wwang

Thu Jun 02 22:43:04 2011

MMNL started with pid=16, OS id=3064

2.启动数据库到mount状态

Alter database mount

SQL> alter database mount;

数据库已更改。

SQL>

这个阶段oracle根据参数文件中control\_files找到控制文件然后打开控制文件中控制文件中得到数据文件和重做日志文件的名字以及位置，mount状态数据库普通用户不能访问，mount状态主要用于数据库的恢复

对应的alert日志：

Thu Jun 02 22:57:25 2011

alter database mount

Thu Jun 02 22:57:30 2011

Successful mount of redo thread 1, with mount id 634474837

Database mounted in Exclusive Mode

Lost write protection disabled

Completed: alter database mount

Thu Jun 02 22:58:08 2011

db\_recovery\_file\_dest\_size of 1024 MB is 0.00% used. This is a

user-specified limit on the amount of space that will be used by this

database for recovery-related files, and does not reflect the amount of

space available in the underlying filesystem or ASM diskgroup.

3．打开数据库

Alter database open

SQL> alter database open;

数据库已更改。

SQL>

这个阶段oracle打开数据文件和重做日志文件，这时普通用户可以访问数据库进行相关的操作

对应alert日志：

Thu Jun 02 23:03:08 2011

alter database open

Thu Jun 02 23:03:08 2011

Thread 1 opened at log sequence 39

Current log\# 3 seq\# 39 mem\# 0: D:\\APP\\WWANG\\ORADATA\\MDSP\\REDO03.LOG

Successful open of redo thread 1

MTTR advisory is disabled because FAST\_START\_MTTR\_TARGET is not set

Thu Jun 02 23:03:08 2011

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

No Resource Manager plan active

Starting background process QMNC

Thu Jun 02 23:03:13 2011

QMNC started with pid=20, OS id=3944

Completed: alter database open

从alert日志中看数据库启动数据启动的三个过程

发表评论取消回复

还没有评论，来说两句吧...

相关阅读

相关 Android应用启动流程：从启动到可交互的过程解析

相关路由器的启动过程

相关分布式数据库启动日志服务配置方法

相关 ViewPager 从入门到带你撸个启动页之实战启动页（三）

相关通过哪个日志查看CRS启动过程

相关 App的启动过程（8）surfaceflinger的启动

相关 Oracle的启动过程

相关从alert日志中看数据库启动数据启动的三个过程

相关 Linux的启动过程

相关 Angular的启动过程