Started redo application at
Thread 1: logseq 71199, block 907842
Thu Jun 23 23:11:13 CST 2011
Recovery of Online Redo Log: Thread 1 Group 15 Seq 71199 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo15.log
Thu Jun 23 23:11:14 CST 2011
Recovery of Online Redo Log: Thread 1 Group 16 Seq 71200 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo16.log
Thu Jun 23 23:11:15 CST 2011
Completed redo application
[root@cmhoneypotmx01 bdump]# tail alert_antispam.log -f
Started redo application at
Thread 1: logseq 71199, block 907842
Thu Jun 23 23:11:13 CST 2011
Recovery of Online Redo Log: Thread 1 Group 15 Seq 71199 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo15.log
Thu Jun 23 23:11:14 CST 2011
Recovery of Online Redo Log: Thread 1 Group 16 Seq 71200 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo16.log
Thu Jun 23 23:11:15 CST 2011
Completed redo application
Thu Jun 23 23:18:24 CST 2011
Completed crash recovery at
Thread 1: logseq 71200, block 294542, scn 9653068842
75768 data blocks read, 75758 data blocks written, 383866 redo blocks read
Thu Jun 23 23:18:25 CST 2011
Thread 1 advanced to log sequence 71201 (thread open)
Thread 1 opened at log sequence 71201
Current log# 17 seq# 71201 mem# 0: /home/oracle/redotbs_space/redo17.log
Successful open of redo thread 1
Thu Jun 23 23:18:25 CST 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jun 23 23:18:25 CST 2011
SMON: enabling cache recovery
Thu Jun 23 23:18:28 CST 2011
Successfully onlined Undo Tablespace 67.
Thu Jun 23 23:18:28 CST 2011
SMON: enabling tx recovery
Thu Jun 23 23:18:28 CST 2011
Database Characterset is ZHS16GBK
Opening with internal Resource Manager plan
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=32, OS id=1881
Thu Jun 23 23:18:34 CST 2011
SMON: Parallel transaction recovery tried
Thu Jun 23 23:18:37 CST 2011
db_recovery_file_dest_size of 20480 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.
Thu Jun 23 23:18:37 CST 2011
Completed: ALTER DATABASE OPEN
[root@cmhoneypotmx01 bdump]#
[root@cmhoneypotmx01 bdump]# tail alert_antispam.log -f -n 222
__large_pool_size = 16777216
large_pool_size = 16777216
__java_pool_size = 16777216
java_pool_size = 16777216
__streams_pool_size = 0
streams_pool_size = 0
nls_language = SIMPLIFIED CHINESE
nls_territory = CHINA
sga_target = 0
control_files = /home/oracle/oradata/antispam/control01.ctl, /home/oracle/oradata/antispam/control02.ctl, /home/oracle/oradata/antispam/control03.ctl
db_block_size = 8192
__db_cache_size = 7516192768
db_cache_size = 7516192768
compatible = 10.2.0.1.0
log_buffer = 46756864
db_file_multiblock_read_count= 16
db_recovery_file_dest = /home/oracle/flash_recovery_area
db_recovery_file_dest_size= 21474836480
undo_management = AUTO
undo_tablespace = UNDOTBSNEW
undo_retention = 200
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=antispamXDB)
job_queue_processes = 10
background_dump_dest = /home/oracle/admin/antispam/bdump
user_dump_dest = /home/oracle/admin/antispam/udump
core_dump_dest = /home/oracle/admin/antispam/cdump
audit_file_dest = /home/oracle/admin/antispam/adump
db_name = antispam
open_cursors = 300
pga_aggregate_target = 4294967296
PMON started with pid=2, OS id=1645
PSP0 started with pid=3, OS id=1647
MMAN started with pid=4, OS id=1649
DBW0 started with pid=5, OS id=1651
LGWR started with pid=6, OS id=1653
CKPT started with pid=7, OS id=1655
SMON started with pid=8, OS id=1657
RECO started with pid=9, OS id=1659
CJQ0 started with pid=10, OS id=1661
MMON started with pid=11, OS id=1663
Thu Jun 23 23:04:21 CST 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=1665
Thu Jun 23 23:04:21 CST 2011
starting up 1 shared server(s) ...
Thu Jun 23 23:04:21 CST 2011
ALTER DATABASE MOUNT
Thu Jun 23 23:04:25 CST 2011
Setting recovery target incarnation to 1
Thu Jun 23 23:04:25 CST 2011
Successful mount of redo thread 1, with mount id 2697586741
Thu Jun 23 23:04:25 CST 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jun 23 23:04:25 CST 2011
ALTER DATABASE OPEN
Thu Jun 23 23:04:27 CST 2011
Errors in file /home/oracle/admin/antispam/bdump/antispam_dbw0_1651.trc:
ORA-01157: ????/?????? 113 - ??? DBWR ????
ORA-01110: ???? 113: '/home/oracle/oracle_data_index_space/mx_mta_space_07.dbf'
ORA-27086: ?????? - ??????
Linux-x86_64 Error: 11: Resource temporarily unavailable
Additional information: 8
ORA-1157 signalled during: ALTER DATABASE OPEN...
Thu Jun 23 23:06:07 CST 2011
Shutting down instance (immediate)
Thu Jun 23 23:06:07 CST 2011
Shutting down instance: further logons disabled
Thu Jun 23 23:06:07 CST 2011
Stopping background process CJQ0
Thu Jun 23 23:06:07 CST 2011
Stopping background process MMNL
Thu Jun 23 23:06:08 CST 2011
Stopping background process MMON
License high water mark = 1
Thu Jun 23 23:06:09 CST 2011
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Thu Jun 23 23:06:11 CST 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Jun 23 23:06:11 CST 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Jun 23 23:07:31 CST 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
IMODE=BR
ILAT =30
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.5.0.
System parameters with non-default values:
processes = 250
sessions = 280
sga_max_size = 9663676416
__shared_pool_size = 603979776
shared_pool_size = 603979776
__large_pool_size = 16777216
large_pool_size = 16777216
__java_pool_size = 16777216
java_pool_size = 16777216
__streams_pool_size = 0
streams_pool_size = 0
nls_language = SIMPLIFIED CHINESE
nls_territory = CHINA
sga_target = 0
control_files = /home/oracle/oradata/antispam/control01.ctl, /home/oracle/oradata/antispam/control02.ctl, /home/oracle/oradata/antispam/control03.ctl
db_block_size = 8192
__db_cache_size = 7516192768
db_cache_size = 7516192768
compatible = 10.2.0.1.0
log_buffer = 46756864
db_file_multiblock_read_count= 16
db_recovery_file_dest = /home/oracle/flash_recovery_area
db_recovery_file_dest_size= 21474836480
undo_management = AUTO
undo_tablespace = UNDOTBSNEW
undo_retention = 200
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=antispamXDB)
job_queue_processes = 10
background_dump_dest = /home/oracle/admin/antispam/bdump
user_dump_dest = /home/oracle/admin/antispam/udump
core_dump_dest = /home/oracle/admin/antispam/cdump
audit_file_dest = /home/oracle/admin/antispam/adump
db_name = antispam
open_cursors = 300
pga_aggregate_target = 4294967296
PMON started with pid=2, OS id=1714
PSP0 started with pid=3, OS id=1716
MMAN started with pid=4, OS id=1718
DBW0 started with pid=5, OS id=1720
LGWR started with pid=6, OS id=1722
CKPT started with pid=7, OS id=1724
SMON started with pid=8, OS id=1726
RECO started with pid=9, OS id=1728
CJQ0 started with pid=10, OS id=1730
MMON started with pid=11, OS id=1732
Thu Jun 23 23:07:32 CST 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=1734
Thu Jun 23 23:07:32 CST 2011
starting up 1 shared server(s) ...
Thu Jun 23 23:07:32 CST 2011
ALTER DATABASE MOUNT
Thu Jun 23 23:07:36 CST 2011
Setting recovery target incarnation to 1
Thu Jun 23 23:07:36 CST 2011
Successful mount of redo thread 1, with mount id 2697601780
Thu Jun 23 23:07:36 CST 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Jun 23 23:07:36 CST 2011
ALTER DATABASE OPEN
Thu Jun 23 23:07:40 CST 2011
Beginning crash recovery of 1 threads
parallel recovery started with 7 processes
Thu Jun 23 23:07:41 CST 2011
Started redo scan
Thu Jun 23 23:07:45 CST 2011
Completed redo scan
383866 redo blocks read, 75768 data blocks need recovery
Thu Jun 23 23:11:13 CST 2011
Started redo application at
Thread 1: logseq 71199, block 907842
Thu Jun 23 23:11:13 CST 2011
Recovery of Online Redo Log: Thread 1 Group 15 Seq 71199 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo15.log
Thu Jun 23 23:11:14 CST 2011
Recovery of Online Redo Log: Thread 1 Group 16 Seq 71200 Reading mem 0
Mem# 0: /home/oracle/redotbs_space/redo16.log
Thu Jun 23 23:11:15 CST 2011
Completed redo application
Thu Jun 23 23:18:24 CST 2011
Completed crash recovery at
Thread 1: logseq 71200, block 294542, scn 9653068842
75768 data blocks read, 75758 data blocks written, 383866 redo blocks read
Thu Jun 23 23:18:25 CST 2011
Thread 1 advanced to log sequence 71201 (thread open)
Thread 1 opened at log sequence 71201
Current log# 17 seq# 71201 mem# 0: /home/oracle/redotbs_space/redo17.log
Successful open of redo thread 1
Thu Jun 23 23:18:25 CST 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jun 23 23:18:25 CST 2011
SMON: enabling cache recovery
Thu Jun 23 23:18:28 CST 2011
Successfully onlined Undo Tablespace 67.
Thu Jun 23 23:18:28 CST 2011
SMON: enabling tx recovery
Thu Jun 23 23:18:28 CST 2011
Database Characterset is ZHS16GBK
Opening with internal Resource Manager plan
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=32, OS id=1881
Thu Jun 23 23:18:34 CST 2011
SMON: Parallel transaction recovery tried
Thu Jun 23 23:18:37 CST 2011
db_recovery_file_dest_size of 20480 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.
Thu Jun 23 23:18:37 CST 2011
Completed: ALTER DATABASE OPEN
阅读(1210) | 评论(0) | 转发(0) |
