- 最后登录
- 2017-5-4
- 在线时间
- 81 小时
- 威望
- 999
- 金钱
- 2391
- 注册时间
- 2013-9-11
- 阅读权限
- 150
- 帖子
- 1124
- 精华
- 5
- 积分
- 999
- UID
- 1220
|
1#
发表于 2017-4-15 23:57:12
|
查看: 1802 |
回复: 0
错误信息:~Errors in file d:\oracle\product\10.2.0\admin\jn\bdump\jn_dbw0_3236.trc:~ORA-01157: cannot identify/lock data file 5 - see DBWR trace file~ORA-01110: data file 5: 'D:\TOOLS\ORADATA\jn\bj.DBF'~ORA-27086: unable to lock file - already in use~OSD-00002: 附加错误信息~O/S-Error: (OS 32) 另一个程序正在使用此文件,进程无法访问。~~ORA-1157 signalled during: alter database open...
DBV查看的信息。但是并没有提示有坏块。
这是发生错误时间段的日志:
Dump file d:\oracle\product\10.2.0/admin/jn/bdump\alert_jn.log
Sat Mar 17 06:57:43 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 4 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3689M/4082M, Ph+PgF:5690M/5961M, VA:1938M/2047M
Sat Mar 17 06:57:43 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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.1.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 113246208
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 8388608
spfile = D:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEJN.ORA
sga_target = 612368384
control_files = D:\TOOLS\ORADATA\JN\CONTROL01.CTL, D:\TOOLS\ORADATA\JN\CONTROL02.CTL, D:\TOOLS\ORADATA\JN\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 473956352
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = d:\oracle\product\10.2.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=jnXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\JN\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\JN\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\JN\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\JN\CDUMP
db_name = jn
open_cursors = 300
pga_aggregate_target = 203423744
PSP0 started with pid=4, OS id=3140
MMAN started with pid=6, OS id=3144
PMON started with pid=2, OS id=3112
DBW0 started with pid=8, OS id=3236
DBW1 started with pid=10, OS id=3280
LGWR started with pid=12, OS id=3296
CKPT started with pid=14, OS id=3320
SMON started with pid=16, OS id=3356
RECO started with pid=18, OS id=3380
CJQ0 started with pid=20, OS id=3388
MMON started with pid=22, OS id=3404
MMNL started with pid=24, OS id=3416
Sat Mar 17 06:57:45 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Sat Mar 17 06:57:47 2012
alter database mount exclusive
Sat Mar 17 06:57:53 2012
Setting recovery target incarnation to 2
Sat Mar 17 06:57:53 2012
Successful mount of redo thread 1, with mount id 2869742955
Sat Mar 17 06:57:53 2012
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Sat Mar 17 06:57:53 2012
alter database open
Sat Mar 17 06:57:54 2012
Errors in file d:\oracle\product\10.2.0\admin\jn\bdump\jn_dbw0_3236.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'D:\TOOLS\ORADATA\JN\BJ.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: 附加错误信息
O/S-Error: (OS 32) 另一个程序正在使用此文件,进程无法访问。
ORA-1157 signalled during: alter database open...
Sat Mar 17 07:11:41 2012
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.
Sat Mar 17 08:37:03 2012
ALTER DATABASE open
Sat Mar 17 08:37:03 2012
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Sat Mar 17 08:37:03 2012
Started redo scan
Sat Mar 17 08:37:03 2012
Completed redo scan
152 redo blocks read, 42 data blocks need recovery
Sat Mar 17 08:37:03 2012
Started redo application at
Thread 1: logseq 764, block 31418
Sat Mar 17 08:37:03 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 764 Reading mem 0
Mem# 0 errs 0: D:\TOOLS\ORADATA\JN\REDO01.LOG
Sat Mar 17 08:37:03 2012
Completed redo application
Sat Mar 17 08:37:03 2012
Completed crash recovery at
Thread 1: logseq 764, block 31570, scn 61206560
42 data blocks read, 42 data blocks written, 152 redo blocks read
Sat Mar 17 08:37:04 2012
Thread 1 advanced to log sequence 765
Thread 1 opened at log sequence 765
Current log# 2 seq# 765 mem# 0: D:\TOOLS\ORADATA\JN\REDO02.LOG
Successful open of redo thread 1
Sat Mar 17 08:37:04 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Mar 17 08:37:04 2012
SMON: enabling cache recovery
Sat Mar 17 08:37:04 2012
Successfully onlined Undo Tablespace 1.
Sat Mar 17 08:37:04 2012
SMON: enabling tx recovery
Sat Mar 17 08:37:04 2012
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=38, OS id=3884
Sat Mar 17 08:37:07 2012
Completed: ALTER DATABASE open
Sat Mar 17 08:42:49 2012
ORA-00060: Deadlock detected. More info in file d:\oracle\product\10.2.0\admin\jn\udump\jn_ora_960.trc.
Sat Mar 17 11:07:38 2012
Memory Notification: Library Cache Object loaded into SGA
Heap size 2188K exceeds notification threshold (2048K)
KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
Sat Mar 17 11:07:38 2012
Memory Notification: Library Cache Object loaded into SGA
Heap size 2318K exceeds notification threshold (2048K)
Details in trace file d:\oracle\product\10.2.0\admin\jn\udump\jn_ora_1820.trc
KGL object name :XDB.XDZynXpO5DTv2jNMI2jLTZZA==
数据, 信息, Errors, file, cannot |
|