oracle数据库启动可分三个步骤:
nomount -> mount -> open
1、Nomount:启动实例
Startup nomount:首先查找参数文件(pfile/spfile),根据文件创建实例。Nomount的过程是启动数据库实例的过程
启动成功:
查看参数文件位置:
Show parameter spfile;
若是没有参数文件,oracle会启动不了。
V$process视图:
Spid:列代表的是操作系统上的进程号
指定参数文件启动nomount:
Start nomount pfile=’参数文件路径’;
Background_dump_dest目录,告警日志文件alert_.log
Show parameter background_dump
Show parameter dump_dest
Show parameter control_files
2、Mount:打开控制文件
Alter database mount;
从参数文件中获得控制文件的位置信息,然后找到控制文件,并且根据控制文件中记录的数据文件位置进行数据文件的存在判断
数据文件:
Select name from v$datafile;
3、Open:打开所有控制文件中描述的文件
Alter database open;
Nomount日志:Thu May 29 15:05:14 2014
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter defaultvalue as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =35
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise EditionRelease 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Miningand Real Application Testing options.
Using parameter settings in server-sidespfile D:\APP\HUANG\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEHXW168.ORA
System parameters with non-default values:
processes = 200
memory_target = 2032M
control_files ="D:\APP\HUANG\ORADATA\HXW168\CONTROL01.CTL"
control_files ="D:\APP\HUANG\FLASH_RECOVERY_AREA\HXW168\CONTROL02.CTL"
db_block_size = 8192
compatible ="11.2.0.0.0"
db_recovery_file_dest ="D:\app\huang\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace ="UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain =""
dispatchers ="(PROTOCOL=TCP) (SERVICE=hxw168XDB)"
audit_file_dest ="D:\APP\HUANG\ADMIN\HXW168\ADUMP"
audit_trail ="DB"
db_name ="hxw168"
open_cursors = 300
diagnostic_dest ="D:\APP\HUANG"
Thu May 29 15:05:14 2014
PMON started with pid=2, OS id=7068
Thu May 29 15:05:14 2014
VKTM started with pid=3, OS id=7520 atelevated priority
VKTM running at (10)millisec precision withDBRM quantum (100)ms
Thu May 29 15:05:14 2014
GEN0 started with pid=4, OS id=4332
Thu May 29 15:05:14 2014DIAG started with pid=5, OS id=3008
Thu May 29 15:05:14 2014
DBRM started with pid=6, OS id=7900
Thu May 29 15:05:14 2014
PSP0 started with pid=7, OS id=6864
Thu May 29 15:05:14 2014
DIA0 started with pid=8, OS id=5836
Thu May 29 15:05:14 2014
MMAN started with pid=9, OS id=7552
Thu May 29 15:05:14 2014
DBW0 started with pid=10, OS id=5584
Thu May 29 15:05:14 2014
LGWR started with pid=11, OS id=7412
Thu May 29 15:05:14 2014
CKPT started with pid=12, OS id=4152
Thu May 29 15:05:14 2014
SMON started with pid=13, OS id=5176
Thu May 29 15:05:15 2014
RECO started with pid=14, OS id=5452
Thu May 29 15:05:15 2014MMON started with pid=15, OS id=3532
starting up 1 dispatcher(s) for networkaddress '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu May 29 15:05:15 2014
MMNL started with pid=16, OS id=4184
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\app\huang
Nomount到mount日志:
Thu May 29 15:57:51 2014
alter database mount
Thu May 29 15:57:55 2014
Successful mount of redo thread 1, withmount id 581607551
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount
Mount到open日志:
Thu May 29 15:58:44 2014
alter database open
Thu May 29 15:58:44 2014
Thread 1 opened at log sequence 8
Current log# 2 seq# 8 mem# 0: D:\APP\HUANG\ORADATA\HXW168\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled becauseFAST_START_MTTR_TARGET is not set
Thu May 29 15:58:44 2014
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11gtablespace encryption..
Verifying 11g file header compatibility fortablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active