Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-01154: database busy. Open, close, mount, and dismount not allowed now

650105Dec 31 2008 — edited Jul 10 2010
hey to all i've posted the same problem yesterday but by restarting the service and kill oracle.exe suddenly the problem resolve now today same problem occur again i put my alert log and trac file copy here could plz tell what is the problem i think redolog 2 casued error at mountted stage when i issue
alter database open
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
Alert Log
Wed Dec 31 09:09:05 2008
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=3588
Wed Dec 31 09:09:07 2008
alter database mount exclusive
PSP0 started with pid=3, OS id=3592
Setting recovery target incarnation to 2
Wed Dec 31 09:09:19 2008
Successful mount of redo thread 1, with mount id 1202699443
Wed Dec 31 09:09:19 2008
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Dec 31 09:09:19 2008
alter database open
Wed Dec 31 09:18:49 2008
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Wed Dec 31 09:37:54 2008
Started redo scan
Wed Dec 31 09:37:54 2008
Completed redo scan
434 redo blocks read, 63 data blocks need recovery
Wed Dec 31 09:37:55 2008
Started redo application at
Thread 1: logseq 11984, block 30825
Wed Dec 31 09:37:55 2008
Recovery of Online Redo Log: Thread 1 Group 1 Seq 11984 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
Wed Dec 31 09:37:56 2008
Completed redo application
Wed Dec 31 09:38:00 2008
Completed crash recovery at
Thread 1: logseq 11984, block 31259, scn 395809161
63 data blocks read, 63 data blocks written, 434 redo blocks read
Wed Dec 31 09:51:47 2008
alter database open
Wed Dec 31 09:51:48 2008
ORA-1154 signalled during: alter database open...
Wed Dec 31 10:03:36 2008
alter database open
Wed Dec 31 10:03:36 2008
ORA-1154 signalled during: alter database open...

trace file

Dump file d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3656.trc
Tue May 13 19:07:24 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:853M/2047M, Ph+PgF:2135M/3947M, VA:1055M/2047M
Instance name: orcl

Redo thread mounted by this instance: 1

Oracle process number: 16

Windows thread id: 3656, image: ORACLE.EXE (SHAD)


*** 2008-05-13 19:07:24.892
*** SERVICE NAME:(orcl) 2008-05-13 19:07:24.767
*** SESSION ID:(136.867) 2008-05-13 19:07:24.767
opitsk: network error occurred while two-task server trying to send break; error code = 12152
Dump file d:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3656.trc
Wed Dec 31 09:09:07 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1392M/2047M, Ph+PgF:2597M/3947M, VA:1015M/2047M
Instance name: orcl

Redo thread mounted by this instance: 0 <none>

Oracle process number: 149

Windows thread id: 3656, image: ORACLE.EXE (SHAD)


*** SERVICE NAME:() 2008-12-31 09:09:07.218
*** SESSION ID:(159.1) 2008-12-31 09:09:07.218
kccsga_update_ckpt: num_1 = 8, num_2 = 0, num_3 = 0, lbn_2 = 0, lbn_3 = 0
*** 2008-12-31 09:14:19.781
Waited for detached process: DBW0 for 300 seconds:
*** 2008-12-31 09:14:19.828
Dumping diagnostic information for DBW0:
OS tid = 3600
Memory (Avail/Total): Ph:1011M/2047M, Ph+PgF:2205M/3947M, VA:1014M/2047M
CPU Load: 19%
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
------------------------------------------- ------------------------------------------- -------- -------- -------- --------
7C82ED54 00000000 00000000 00000000 00000000 00000000
77E41A5E 77E6C24B 00000000 00000000 00000000 00000000
_skgfifi+673 00000000 00000000 00000000 00000000 00000000
ksfdopn+486 skgfifi+0 05fbea28 0602ab44 3f76d3bc 05fbedd2
kcfbid+529 ksfdopn+0 05fbedd2 0000001b 00002000 00000002
kcfida+443 kcfbid+0 00001cb6 05fbf204 05fbf050 00000000
_ksbabs+627 00000000 00000000 00000000 00000000 00000000
_ksbrdp+747 00000000 03c437a0 00000000 00000000 00000000
opirip+674 ksbrdp+0 00000000 00000000 00000000 00000000
opidrv+857 opirip+0 00000032 00000004 05fbfec0 00000000
sou2o+45 opidrv+0 00000032 00000004 05fbfec0 00000000
opimaireal+227 _sou2o+0 05fbfeb4 00000032 00000004 05fbfec0
opimai+92 opimai_real+0 00000003 05fbfeec 00000000 00000000
BackgroundThreadStart@4+422 opimai+0 00000000 00000000 00000000 00000000
77E66088 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 15 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 719 ms
total time: 734 ms
*** 2008-12-31 09:14:20.968
*** 2008-12-31 09:14:30.984
Waited for detached process: DBW0 for 310 seconds:
*** 2008-12-31 09:14:31.000
Dumping diagnostic information for DBW0:
OS tid = 3600
Memory (Avail/Total): Ph:1011M/2047M, Ph+PgF:2203M/3947M, VA:1002M/2047M
CPU Load: 7%
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
------------------------------------------- ------------------------------------------- -------- -------- -------- --------
7C82ED54 00000000 00000000 00000000 00000000 00000000
_skgfdisp+704 00000000 00000000 00000000 00000000 00000000
skgfqio+91 skgfdisp+0 0602ab44 05fbe988 00000004 00000000
ksfdread1+599 skgfqio+0 0602ab44 05fbe9b4 00000004 00000000
ksfdread+25 ksfdread1+0 41c36208 000001b6 04b7be00 00004000
kccrbp+222 ksfdread+0 41c36208 000001b6 04b7be00 00004000
kccrecrbl+228 _kccrbp+0 ffffffff 000001b6 04b7be00 00004000
__VInfreq__kccext_info+97 kccrecrbl+0 062f76a0 000000da 00000000 00000000
kccrecread_write+120 kccextinfo+0 00000000 00000000 00000000 00000000
kccugg+198 kccrec_read_write+0 062f76a0 04b8bfe4 00001db1 05fbf050
kccget_record+27 _kccugg+0 00000000 00000000 00000000 00000000
kccgfi+26 kcc_get_record+0 05fbf204 00001db1 05fbf050 00000004
kcfida+398 kccgfi+0 05fbf204 00001db1 05fbf050 00000000
_ksbabs+627 00000000 00000000 00000000 00000000 00000000
_ksbrdp+747 00000000 03c437a0 00000000 00000000 00000000
opirip+674 ksbrdp+0 00000000 00000000 00000000 00000000
opidrv+857 opirip+0 00000032 00000004 05fbfec0 00000000
sou2o+45 opidrv+0 00000032 00000004 05fbfec0 00000000
opimaireal+227 _sou2o+0 05fbfeb4 00000032 00000004 05fbfec0
opimai+92 opimai_real+0 00000003 05fbfeec 00000000 00000000
BackgroundThreadStart@4+422 opimai+0 00000000 00000000 00000000 00000000
77E66088 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 31 ms
total time: 31 ms
*** 2008-12-31 09:14:31.421
*** 2008-12-31 09:14:41.421
Waited for detached process: DBW0 for 320 seconds:
*** 2008-12-31 09:14:41.421
Dumping diagnostic information for DBW0:
OS tid = 3600
Memory (Avail/Total): Ph:1010M/2047M, Ph+PgF:2202M/3947M, VA:1002M/2047M
CPU Load: 7%
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
------------------------------------------- ------------------------------------------- -------- -------- -------- --------
7C82ED54 00000000 00000000 00000000 00000000 00000000
77E41A5E 77E6C24B 00000000 00000000 00000000 00000000
_skgfifi+673 00000000 00000000 00000000 00000000 00000000
ksfdopn+486 skgfifi+0 05fbea28 0602ab44 3f7d313c 05fbedd2
kcfbid+529 ksfdopn+0 05fbedd2 0000001f 00002000 00000002
kcfida+443 kcfbid+0 00001ea9 05fbf204 05fbf050 00000000
_ksbabs+627 00000000 00000000 00000000 00000000 00000000
_ksbrdp+747 00000000 03c437a0 00000000 00000000 00000000
opirip+674 ksbrdp+0 00000000 00000000 00000000 00000000
opidrv+857 opirip+0 00000032 00000004 05fbfec0 00000000
sou2o+45 opidrv+0 00000032 00000004 05fbfec0 00000000
opimaireal+227 _sou2o+0 05fbfeb4 00000032 00000004 05fbfec0
opimai+92 opimai_real+0 00000003 05fbfeec 00000000 00000000
BackgroundThreadStart@4+422 opimai+0 00000000 00000000 00000000 00000000
77E66088 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
*** 2008-12-31 09:14:41.531
*** 2008-12-31 09:18:49.453
Successfully allocated 3 recovery slaves
Using 364 overflow buffers per recovery slave
*** 2008-12-31 09:37:54.320
Thread 1 checkpoint: logseq 11984, block 2, scn 395787552
cache-low rba: logseq 11984, block 30825
on-disk rba: logseq 11984, block 31259, scn 395789161
start recovery at logseq 11984, block 30825, scn 0
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 217Kb in 0.48s => 0.44 Mb/sec
Total physical reads: 4096Kb
Longest record: 18Kb, moves: 0/725 (0%)
Change moves: 44/430 (10%), moved: 0Mb
Longest LWN: 20Kb, moves: 0/87 (0%), moved: 0Mb
Last redo scn: 0x0000.17974368 (395789160)
----------------------------------------------
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 2
Average hash chain = 63/62 = 1.0
Max compares per lookup = 2
Avg compares per lookup = 932/1961 = 0.5
----------------------------------------------
*** 2008-12-31 09:37:54.993
KCRA: start recovery claims for 63 data blocks
*** 2008-12-31 09:37:55.009
KCRA: blocks processed = 63/63, claimed = 63, eliminated = 0
*** 2008-12-31 09:37:55.747
Recovery of Online Redo Log: Thread 1 Group 1 Seq 11984 Reading mem 0
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 2
Average hash chain = 63/62 = 1.0
Max compares per lookup = 2
Avg compares per lookup = 495/983 = 0.5
----------------------------------------------

Edited by: Oracle Studnet on Dec 30, 2008 9:45 PM
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 7 2010
Added on Dec 31 2008
9 comments
22,557 views