startupalter.logspfile.ora(二)
:52:59 2015
DIAG started with pid=5, OS id=24383
Fri Jun 12 00:52:59 2015
DBRM started with pid=6, OS id=24385
Fri Jun 12 00:52:59 2015
PSP0 started with pid=7, OS id=24387
Fri Jun 12 00:52:59 2015
DIA0 started with pid=8, OS id=24389
Fri Jun 12 00:52:59 2015
MMAN started with pid=9, OS id=24391
Fri Jun 12 00:52:59 2015
DBW0 started with pid=10, OS id=24393
Fri Jun 12 00:52:59 2015
LGWR started with pid=11, OS id=24395
Fri Jun 12 00:52:59 2015
CKPT started with pid=12, OS id=24397
Fri Jun 12 00:52:59 2015
SMON started with pid=13, OS id=24399
Fri Jun 12 00:52:59 2015
RECO started with pid=14, OS id=24401
Fri Jun 12 00:52:59 2015
MMON started with pid=15, OS id=24403
Fri Jun 12 00:52:59 2015
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Fri Jun 12 00:52:59 2015
MMNL started with pid=16, OS id=24405
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/app/oracle
Fri Jun 12 00:52:59 2015
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 3870724267
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Fri Jun 12 00:53:05 2015
ALTER DATABASE OPEN
Thread 1 opened at log sequence 557
Current log# 2 seq# 557 mem# 0: /u01/app/oracle/oradata/orcl3939/redo02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
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
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Jun 12 00:53:10 2015
QMNC started with pid=20, OS id=24454
Completed: ALTER DATABASE OPEN
Fri Jun 12 00:53:14 2015
Starting background process CJQ0
Fri Jun 12 00:53:14 2015
CJQ0 started with pid=22, OS id=24475
Fri Jun 12 00:53:15 2015
db_recovery_file_dest_size of 3852 MB is 18.77% 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[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Fri Jun 12 00:53:17 2015
Starting background process VKRM
Fri Jun 12 00:53:17 2015
VKRM started with pid=21, OS id=24482