- 论坛徽章:
- 0
|
oracle log:
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 300
sessions = 335
__shared_pool_size = 83886080
__large_pool_size = 4194304
__java_pool_size = 8388608
nls_language = SIMPLIFIED CHINESE
nls_territory = CHINA
sga_target = 289406976
control_files = D:\ORACLE\PRODUCT\10.1.0\ORADATA\MY\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.1.0\ORADATA\MY\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.1.0\ORADATA\MY\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 188743680
compatible = 10.1.0.2.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.1.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=myXDB)
job_queue_processes = 10
background_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MY\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MY\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MY\CDUMP
sort_area_size = 65536
db_name = my
open_cursors = 300
pga_aggregate_target = 95420416
Mon Jun 21 01:02:16 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
PMON started with pid=2, OS id=1096
DBW0 started with pid=4, OS id=1904
LGWR started with pid=5, OS id=284
CKPT started with pid=6, OS id=784
SMON started with pid=7, OS id=600
CJQ0 started with pid=9, OS id=776
MMAN started with pid=3, OS id=744
Mon Jun 21 01:02:21 2010
alter database mount exclusive
RECO started with pid=8, OS id=804
Mon Jun 21 01:02:21 2010
Controlfile identified with block size 16384
Mon Jun 21 01:02:25 2010
Setting recovery target incarnation to 2
Mon Jun 21 01:02:25 2010
Successful mount of redo thread 1, with mount id 1037880157
Mon Jun 21 01:02:25 2010
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Jun 21 01:02:26 2010
alter database open
Mon Jun 21 01:02:26 2010
Beginning crash recovery of 1 threads
attempting to start a parallel recovery with 2 processes
parallel recovery started with 2 processes
Mon Jun 21 01:02:26 2010
Started first pass scan
Mon Jun 21 01:02:27 2010
Completed first pass scan
4867 redo blocks read, 600 data blocks need recovery
Mon Jun 21 01:02:28 2010
Started redo application at
Thread 1: logseq 5, block 10017, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 1 Seq 5 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MY\REDO01.LOG
Mon Jun 21 01:02:29 2010
Completed redo application
Mon Jun 21 01:02:30 2010
Completed crash recovery at
Thread 1: logseq 5, block 14884, scn 0.348205
600 data blocks read, 600 data blocks written, 4867 redo blocks read
Mon Jun 21 01:02:31 2010
Thread 1 advanced to log sequence 6
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch
Thread 1 opened at log sequence 6
Current log# 2 seq# 6 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MY\REDO02.LOG
Successful open of redo thread 1
Mon Jun 21 01:02:32 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jun 21 01:02:32 2010
SMON: enabling cache recovery
Mon Jun 21 01:02:34 2010
Successfully onlined Undo Tablespace 1.
Mon Jun 21 01:02:34 2010
SMON: enabling tx recovery
Mon Jun 21 01:02:34 2010
Database Characterset is ZHS16GBK
Mon Jun 21 01:02:35 2010
Published database character set on system events channel
Mon Jun 21 01:02:35 2010
All processes have switched to database character set
Mon Jun 21 01:02:38 2010
Starting background process QMNC
QMNC started with pid=15, OS id=1552
Mon Jun 21 10:47:40 2010
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Jun 21 10:47:41 2010
Starting background process MMON
Starting background process MMNL
MMON started with pid=16, OS id=604
MMNL started with pid=17, OS id=616
Mon Jun 21 10:47:43 2010
Completed: alter database open
Mon Jun 21 10:47:55 2010
db_recovery_file_dest_size of 2048 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. |
|