I thought that this would work ok, but it doesn't seem to shutdown the
database cleanly.
from Alert Log: (I shut the DB down with ORADIM at 22:00... notice how
nothing was written to the alert log)
Wed Jan 26 10:38:30 2000
Thread 1 advanced to log sequence 1537
Current log# 1 seq# 1537 mem# 0: E:\ORACLE\GPRO\LOGGPRO1.ORA
Dump file E:\Oracle\GPRO\trace\gproALRT.LOG
Wed Jan 26 22:44:57 2000
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V4.0, OS V5.101, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 200
shared_pool_size = 50128878
control_files = E:\Oracle\GPRO\ctl1GPRO.ora,
E:\Oracle\GPRO\ctl2GPRO.ora
db_block_buffers = 3200
db_block_size = 4096
compatible = 8.0.5.0.0
log_buffer = 409600
log_checkpoint_interval = 21
log_checkpoint_timeout = 0
db_files = 1000
db_file_multiblock_read_count= 32
dml_locks = 500
rollback_segments = RB0, RB1
sequence_cache_entries = 100
sequence_cache_hash_buckets= 89
remote_login_passwordfile= SHARED
sort_area_size = 1000000
db_name = GPRO
open_cursors = 106
optimizer_mode = rule
background_dump_dest = E:\Oracle\GPRO\trace
user_dump_dest = E:\Oracle\GPRO\trace
max_dump_file_size = 10240
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Wed Jan 26 22:44:57 2000
alter database "gpro" mount exclusive
Wed Jan 26 22:45:02 2000
Successful mount of redo thread 1, with mount id 2361566637.
Wed Jan 26 22:45:02 2000
Database mounted in Exclusive Mode.
Completed: alter database "gpro" mount exclusive
Wed Jan 26 22:45:02 2000
alter database "gpro" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1537 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\GPRO\LOGGPRO1.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Wed Jan 26 22:45:03 2000
Thread 1 advanced to log sequence 1538
Thread 1 opened at log sequence 1538
Current log# 2 seq# 1538 mem# 0: E:\ORACLE\GPRO\LOGGPRO2.ORA
Successful open of redo thread 1.
Wed Jan 26 22:45:03 2000
SMON: enabling cache recovery
SMON: enabling tx recovery
Wed Jan 26 22:45:04 2000
Completed: alter database "gpro" open
this is the alert log when it is shut down properly:
Thu Jan 27 22:00:07 2000
Shutting down instance (immediate)
License high water mark = 18
Thu Jan 27 22:01:19 2000
Thread 1 advanced to log sequence 1552
Current log# 2 seq# 1552 mem# 0: E:\ORACLE\GPRO\LOGGPRO2.ORA
Thu Jan 27 22:01:21 2000
ALTER DATABASE CLOSE NORMAL
Thu Jan 27 22:01:21 2000
SMON: disabling tx recovery
SMON: disabling cache recovery
Thu Jan 27 22:01:21 2000
Thread 1 closed at log sequence 1552
Thu Jan 27 22:01:21 2000
Completed: ALTER DATABASE CLOSE NORMAL
Thu Jan 27 22:01:21 2000
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
Dump file E:\Oracle\GPRO\trace\gproALRT.LOG
Why does oradim give the option of shutting down the database properly, when
all it seems to be doing is stopping the oracle service?
Scott
- Original Message -----
From: "Sybrand Bakker" <postbus_at_sybrandb.demon.nl>
Newsgroups: comp.databases.oracle.server
To: "W. Scott Moore" <sirws_at_hotmail.com>
Sent: Thursday, January 20, 2000 3:22 PM
Subject: Re: Clean Shutdown?
> On Thu, 20 Jan 2000 13:01:50 -0700, "W. Scott Moore"
> <sirws_at_hotmail.com> wrote:
>
> >oradim80 -SHUTDOWN -SID GISP -USRPWD manager -SHUTTYPE inst,
srvc -SHUTMODE
> >i
> >
> >Does this provide a clean shutdown...
> >
> >I know a shutdown immediate is clean, from svrmgr, but would this also
> >suffice?
> >
> >Scott
> >
> >
> Actually this is better as servermanager won't shut the service.
>
>
> Hth,
>
>
> Sybrand Bakker, Oracle DBA
>
Received on Tue Feb 01 2000 - 11:55:07 CST
