| Database shutdown [message #51965] |
Mon, 24 June 2002 06:09  |
Virginia
Messages: 3
Registered: October 1998
|
Junior Member |
|
|
Platform:NT 4.0
Version: running Oracle 8.0.6
Our Database shut down last night during the nightly Seagate backup. This is a copy of our Alert Log - We have 3 control files, all on different drives. I had no problem restarting the database. Any ideas on what caused this - Disk space is adequate and there is no one on the system. thanks virginia
Fri Jun 21 00:04:05 2002
alter database backup controlfile to 'G:BackupCTRLFilescntlappy.dbf'
Completed: alter database backup controlfile to 'G:BackupCT
Fri Jun 21 02:47:21 2002
Errors in file G:oradataappYadMInBDUMPappyCKPT.TRC:
ORA-00206: error in writing (block 3, # blocks 1) of controlfile
ORA-00202: controlfile: 'G:ORADATAAPPYCTLFILESCTL1APPY.ORA'
ORA-27072: skgfdisp: I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because
another process has locked a portion of the file.
Fri Jun 21 02:47:21 2002
CKPT: terminating instance due to error 221
Instance terminated by CKPT, pid = 428
Starting up ORACLE RDBMS Version: 8.0.6.0.0.
System parameters with non-default values:
processes = 250
shared_pool_size = 10000000
pre_page_sga = TRUE
control_files = G:oradataappYCTLFILESctl1appY.ora, H:oradataappYCTLFILESctl2appY.ora, E:oradataappYCTLFILESctl3appY.ora
db_block_buffers = 15000
db_block_size = 4096
compatible = 8.0.5.0.0
log_archive_start = TRUE
log_archive_dest = F:ORADATAAPPYARCHIVE
log_buffer = 131072
_log_io_size = 1000
log_checkpoint_interval = 10000
db_files = 60
db_file_multiblock_read_count= 8
dml_locks = 250
rollback_segments = rb1, rb2, rb3, rb4, rb5, rb6, rb7, rb8, rb9, rb10, rb11, rb12, rb13, rb14, rb15
sequence_cache_entries = 10
sequence_cache_hash_buckets= 10
remote_login_passwordfile= SHARED
db_name = APPI
open_cursors = 300
text_enable = TRUE
snapshot_refresh_processes= 1
background_dump_dest = G:oradataappYadMInBDUMP
user_dump_dest = G:oradataappYadMInUDUMP
max_dump_file_size = 10240
PMON started with pid=2
DBW0 started with pid=3
ARCH started with pid=4
LGWR started with pid=5
CKPT started with pid=6
SMON started with pid=7
RECO started with pid=8
SNP0 started with pid=9
Fri Jun 21 07:22:59 2002
alter database mount exclusive
Fri Jun 21 07:23:03 2002
Successful mount of redo thread 1, with mount id 327077143.
Fri Jun 21 07:23:03 2002
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Fri Jun 21 07:23:04 2002
alter database open
Beginning crash recovery of 1 threads
Fri Jun 21 07:23:04 2002
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 3 Seq 5593 Reading mem 0
Mem# 0 errs 0: E:ORADATAAPPYLOGFILESLOG3A.ORA
Fri Jun 21 07:23:04 2002
Thread recovery: finish rolling forward thread 1
Thread recovery: 0 data blocks read, 0 data blocks written, 0 redo blocks read
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Fri Jun 21 07:23:04 2002
Thread 1 advanced to log sequence 5594
Thread 1 opened at log sequence 5594
Current log# 4 seq# 5594 mem# 0: E:ORADATAAPPYLOGFILESLOG4A.ORA
Successful open of redo thread 1.
Fri Jun 21 07:23:04 2002
SMON: enabling cache recovery
SMON: enabling tx recovery
Fri Jun 21 07:23:05 2002
|
|
|
|
| Re: Database shutdown [message #51969 is a reply to message #51965] |
Mon, 24 June 2002 08:21  |
ecpdba
Messages: 4
Registered: June 2002
|
Junior Member |
|
|
Your database could not access a file that was currently being held by another process. Probably the Seagate backup, I don't know. Try to schedule the backups during a low period of activity.
Also, double check your virus software. It is possible that this may have caused it.
Hth
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
