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

Sat Aug 06 20:39:55 2016Starting ORACLE instance (normal)

LICENSE_MAX_SESSION= 0LICENSE_SESSIONS_WARNING= 0Picked latch-free SCN scheme 3Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST

Autotune of undo retention is turned on.

IMODE=BR

ILAT=27LICENSE_MAX_USERS= 0SYS auditing is disabled

Starting up:

Oracle Database 11g Enterprise Edition Release11.2.0.1.0 -64bit Production

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

Using parameter settingsin server-side spfile D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA

System parameters with non-default values:

processes= 150memory_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= 8192compatible= "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= 300diagnostic_dest= "D:\APP\ADMINISTRATOR"Sat Aug06 20:40:04 2016PMON started with pid=2, OS id=584Sat Aug06 20:40:04 2016VKTM started with pid=3, OS id=564at elevated priority

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

Sat Aug06 20:40:04 2016GEN0 started with pid=4, OS id=1676Sat Aug06 20:40:04 2016DBRM started with pid=6, OS id=3328Sat Aug06 20:40:04 2016PSP0 started with pid=7, OS id=1920Sat Aug06 20:40:04 2016DIAG started with pid=5, OS id=3868Sat Aug06 20:40:04 2016MMAN started with pid=9, OS id=4028Sat Aug06 20:40:10 2016DBW0 started with pid=10, OS id=1972Sat Aug06 20:40:04 2016DIA0 started with pid=8, OS id=1128Sat Aug06 20:40:10 2016LGWR started with pid=11, OS id=3280Sat Aug06 20:40:10 2016CKPT started with pid=12, OS id=3700Sat Aug06 20:40:10 2016RECO started with pid=14, OS id=3776Sat Aug06 20:40:10 2016SMON started with pid=13, OS id=1296Sat Aug06 20:40:10 2016MMNL started with pid=16, OS id=3356Sat Aug06 20:40:10 2016starting up1 dispatcher(s) for network address ‘(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))‘...

starting up1shared server(s) ...

ORACLE_BASE from environment=D:\app\Administrator

Sat Aug06 20:40:17 2016alter databasemountexclusive

Sat Aug06 20:40:10 2016MMON started with pid=15, OS id=2060Sat Aug06 20:40:21 2016Successfulmount of redo thread 1, with mount id 1446963249Database mountedinExclusive Mode

Lostwriteprotection disabled

Completed: alter databasemountexclusive

alter database open

Thread1 opened at log sequence 4055Current log#2 seq# 4055 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG

Successful open of redo thread1MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Sat Aug06 20:40:25 2016SMON: enabling cache recovery

Successfully onlined Undo Tablespace2.

Verifyingfile header compatibility for11g tablespace encryption..

Verifying 11gfile header compatibility fortablespace encryption completed

SMON: enabling tx recovery

Database Characterset is AL32UTF8

Sat Aug06 20:40:28 2016No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

Sat Aug06 20:40:30 2016QMNC started with pid=20, OS id=2668Completed: alter database open

Sat Aug06 20:40:31 2016Starting background process CJQ0

Sat Aug06 20:40:32 2016CJQ0 started with pid=24, OS id=1740Sat Aug06 20:40:32 2016db_recovery_file_dest_size of3912 MB is 0.00%used. This is a

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

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

space availableinthe 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 Aug06 20:40:36 2016Starting background process VKRM

Sat Aug06 20:40:36 2016VKRM started with pid=19, OS id=3712Sat Aug06 20:45:30 2016Starting background process SMCO

Sat Aug06 20:45:30 2016SMCO started with pid=21, OS id=3876