从alert日志中看数据库启动数据启动的三个过程
来源:互联网 发布:淘宝卖二手东西流程 编辑:程序博客网 时间:2024/06/06 12:56
从alert日志中看数据库启动数据启动的三个过程
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日志中看数据库启动数据启动的三个过程
- 数据库启动的三个台阶
- kernel启动过程的三个特殊进程
- oracle startip启动数据库的三个步骤
- Oracle笔记:数据库启动的三个阶段
- oracle数据库启动的三个阶段
- oracle10G 数据库的启动过程
- 数据库启动分为三个步骤
- 2812从内部flash启动的过程
- PowerPC从NorFlash启动的过程
- 数据库启动过程
- 数据库启动过程
- Oracle数据库启动过程
- oracle数据库启动过程
- Oracle 数据库启动过程
- Oracle启动数据库的三个台阶nomount,mount,open
- 实验46:启动数据库的三个台阶nomount,mount,open
- 数据库启动的三个台阶nomount,mount,open
- S2SH开发中的乱码解决
- 黑马程序员-枚举
- 保险ECIF
- 构造函数不能为虚函数的理由
- acm 学校海选题目
- 从alert日志中看数据库启动数据启动的三个过程
- Oracle 10g RAC 维护常用命令
- 【STL】标准库中vector的操作
- Lucene 之 Hello world
- 【搜索】poj3411 paid road
- book的复制
- 捕捉好热点让你流量大增的网络营销法
- glance-0.1.7 分析(一)—— 开始
- Linux 抓取网页方式(curl+wget)