Windows平台下Oracle实例启动过程中日志输出

Sat Aug 06 20:39:55 2016
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 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 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes                = 150
memory_target            = 13120M
control_files            = "D:\APP\ADMINISTRATOR\ORADATA\ORCL\CONTROL01.CTL"
control_files            = "D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size            = 8192
compatible               = "11.2.0.0.0"
db_recovery_file_dest    = "D:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace          = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain                = ""
dispatchers              = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
audit_file_dest          = "D:\APP\ADMINISTRATOR\ADMIN\ORCL\ADUMP"
audit_trail              = "DB"
db_name                  = "orcl"
open_cursors             = 300
diagnostic_dest          = "D:\APP\ADMINISTRATOR"
Sat Aug 06 20:40:04 2016
PMON started with pid=2, OS id=584
Sat Aug 06 20:40:04 2016
VKTM started with pid=3, OS id=564 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Sat Aug 06 20:40:04 2016
GEN0 started with pid=4, OS id=1676
Sat Aug 06 20:40:04 2016
DBRM started with pid=6, OS id=3328
Sat Aug 06 20:40:04 2016
PSP0 started with pid=7, OS id=1920
Sat Aug 06 20:40:04 2016
DIAG started with pid=5, OS id=3868
Sat Aug 06 20:40:04 2016
MMAN started with pid=9, OS id=4028
Sat Aug 06 20:40:10 2016
DBW0 started with pid=10, OS id=1972
Sat Aug 06 20:40:04 2016
DIA0 started with pid=8, OS id=1128
Sat Aug 06 20:40:10 2016
LGWR started with pid=11, OS id=3280
Sat Aug 06 20:40:10 2016
CKPT started with pid=12, OS id=3700
Sat Aug 06 20:40:10 2016
RECO started with pid=14, OS id=3776
Sat Aug 06 20:40:10 2016
SMON started with pid=13, OS id=1296
Sat Aug 06 20:40:10 2016
MMNL started with pid=16, OS id=3356
Sat Aug 06 20:40:10 2016
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\Administrator
Sat Aug 06 20:40:17 2016
alter database mount exclusive
Sat Aug 06 20:40:10 2016
MMON started with pid=15, OS id=2060
Sat Aug 06 20:40:21 2016
Successful mount of redo thread 1, with mount id 1446963249
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Thread 1 opened at log sequence 4055
Current log# 2 seq# 4055 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Aug 06 20:40:25 2016
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
Sat Aug 06 20:40:28 2016
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Sat Aug 06 20:40:30 2016
QMNC started with pid=20, OS id=2668
Completed: alter database open
Sat Aug 06 20:40:31 2016
Starting background process CJQ0
Sat Aug 06 20:40:32 2016
CJQ0 started with pid=24, OS id=1740
Sat Aug 06 20:40:32 2016
db_recovery_file_dest_size of 3912 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.
Setting Resource Manager plan SCHEDULER[0x3008]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sat Aug 06 20:40:36 2016
Starting background process VKRM
Sat Aug 06 20:40:36 2016
VKRM started with pid=19, OS id=3712
Sat Aug 06 20:45:30 2016
Starting background process SMCO
Sat Aug 06 20:45:30 2016
SMCO started with pid=21, OS id=3876