"Starting" on Windows2000 Server
Muhammad Mustafa, February 25, 2003 - 12:43 am UTC
Dear Sir
When i start my 2000 server computer with Oracle 8.1.6 oracleserviceSID stuck on "Starting" all other services properly started. In registery Ora_SID_autostart = TRUE and in control panel it is also set to Automatically.
I have to manually start the service after connecting to an idle instance.
TNSListener service is started in the 2000 server but when i try to connect to oracle from 2000 professional it does not connect to database.
Thanks & Regards
Muhammad Mustafa
February 25, 2003 - 9:29 am UTC
check your alert log and the windows event log.
To schedule& automate startup
Tarry, February 25, 2003 - 11:09 am UTC
A simple *.cmd script can be written like.......
E:\oracle\ora817\bin\svrmgrl @E:\oracle\startup\startup.sql
and scheduled for on system startup
calling script startup.sql can be as simple as......
spool E:\oracle\checkbox\check--to check if it went ok..
set echo on
connect appdev/pwd@service_name as sysdba
startup
This will startup the script on server startup.
What you (probably) didn't mention was that you had more than one home on your machine.......
Startup and/or Shutdown Oracle database on windows NT/2k Machines.
Mirza Shoeb Baig, February 25, 2003 - 4:29 pm UTC
Create two files (one bat file and other sql file in a folder) startupdb.bat
content of bat file:
REM This bat file will call the sql file.
specify the location of svrmgrl command=@startup.sql
exit
file name: startup.sql
Content of sql file:
#This sqlfile will start the database.
connect internal
startup pfile=specify the location of your init.ora
#eg.,
#connect internal
#startup pfile=O:\oracle\admin\ATNYIDW\pfile\init.ora
#exit
/
exit
The above solution is working on NT 4.0 in production
and similar configuration will be good on w2k too.
If there are multiple database and/or multiple homes on the machine, then specify the appropriate init.ora in the startup.sql file.
Thanks
Mirza Shoeb Baig
Internal -
Senthil Kumar, February 26, 2003 - 9:23 am UTC
As far startuping the Oracle database it is okay to use services but Stopping the Oracle service in WIndows - in fact doesnot close the database properly it only wait for some time and
kills the process. This may lead to Oracle crash. Tom
hope you will comment on this.
Internal is going to be depreciated very soon. Oracle recommends not to use Internal
February 27, 2003 - 7:02 am UTC
it will NOT lead to "oracle crash". Oracle is built to be a tad resiliant. This will not crash it anymore then a power failure would.
internal is depricated already and in 9i is not even supported.
Watch Out! stopping service may kill db
Dan, February 26, 2003 - 11:59 pm UTC
I concur with Senthil, under some NT/2000 variations with Oracle 8.1.x a NET STOP OracleServiceXXX will kill the service without shutting down the db (even with a very long timeout). ick ick ick.
There is metalink traffic on this. I know it was a problem in 8.1.7.0, We've recently moved to 8.1.7.4 and I have not retested this problem at the 8.1.7.4 patch level.
BUG:724051 claims this is fixed up in 8.1.6, but I seem to recall (actually I'm SURE I observed it in 8.1.7.0) it cropped up again after 8.1.6 in some configurations.
If you want to use the NET START/NET STOP in 8i Try this out in a test environment as close a possible to your production environment and check you alert log for "Crash Recovery" on restart. And then keep an eye on your production Alert logs as well for a while... Guess you should do that anyway...
This could really suck if you are doing cold backups... your shutdowns might not be clean - could hoop your backups.
I'm nervous enough about this that I use start/stop scripts that connect as SYSOPER and startup/shutdown. I'll try again NET START/NET STOP with 9i.
P.S. NET START OracleServiceXXX works just peachy - I just like to keep the startup/shutdown as similar as possible for our sysadmins... and for me when i'm tired.
February 27, 2003 - 7:35 am UTC
if you are doing cold backups and backup your online redo logs -- it is perfectly ok.
Try ORADIM instead of Net {Start|Stop}
Archer, February 27, 2003 - 2:58 pm UTC
ORADIM, the Oracle utility for creating and deleting Oracle DB Services on NT, also has -STARTUP and -SHUTDOWN options. The two nice things about this are 1) the -STARTUP allows you to specify a different PFILE, and 2) the -SHUTDOWN option supports a -SHUTMODE of a, i, or n for SHUTDOWN ABORT, IMMEDIATE, or NORMAL, respectively. This allows you to shutdown the DB from a .BAT file or the command line and specify the shutdown type, which can be handy. I am not sure, but I think the default behavior (and the one used by NET STOP) is a SHUTDOWN ABORT. If you are nervous about this and would rather SHUTDOWN IMMEDIATE, try:
oradim -shutdown -sid MY_SID -shutmode i
To start up the DB the same way, simply use:
oradim -startup -sid MY_SID
Tom - two questions about ORADIM that I've never quite figured out:
1) Where does the name ORADIM come from? I can't think of any registry or service-related acronym anything like DIM.
2) What is the purpose of the different -STARTTYPE and -SHUTTYPE options of {SRVC|INST|SRVC,INST}. I would have thought from the name that you could start the DB w/out starting the NT service, or vice versa, but on my system all three options appear to start or stop both.
February 27, 2003 - 8:10 pm UTC
1) don't know, I'll guess (hey, here comes the rumor mill)
Database
Instance
Manager
dim ;)
2) again, don't know -- don't run windows for anything. /etc/init.d/ is so simple by comparision -- sorry. maybe a windows dba can help us out here.
ORADIM in Windows
Ogun, February 28, 2003 - 3:49 am UTC
I have Oracle8i running on a Windows2000 machine. I don't have any startup or shutdown scripts but when i have to, i always follow these ways.
For startup
1 - first start the service. If your Oracle service is not running on Win2K, then you are unable to connect an idle instance with connect internal or something from svrmgrl.
oradim -startup -sid {SID} -starttype srvc
2 - then start the instance and the listener via svrmgrl and lsnrctl
For shutdown
1 - fisrt close, dismount the database and shutdown your running instance
2 - Now you are ready to stop the service
On win2k, it doesn't mean that your db is up and running when the service is running. If your startype identified in oradim is srvc,inst or inst (which requires the service to be already running) then your db. can be opened. Also when you set oracle service to run automatically at boot, it starts the service due to the last starttype. Which means it can only start the service, not the instance. That's why your db can not be guaranteed to start this way.
About Internal
Ogun, February 28, 2003 - 3:54 am UTC
Hi Tom,
You said that internal is no longer supported in Oracle9i. Why does Oracle need to do this - since it's a security problem or what? Does this mean we can no longer use OS authentication? Than how can we connect to a db?
Thanks.
February 28, 2003 - 9:53 am UTC
connect internal
is more or less the same as
connect / as sysdba
there were two ways to do things
a) as internal and internal was implemented differently on different OS's
b) as sysdba -- and sysdba is consistently implemented
so, in order to make things consistent, more secure (the fewer paths to protect, the fewer holes to be found), internal was depricated and then removed
Problem
Muhammad Mustafa, March 06, 2003 - 2:43 am UTC
Hello
when i open the bat file svrmgrl closes at once.
i have written in batch file...
E:\oracle\ora816\bin\svrmgrl @E:\oracle\startup\startup.sql
Regards
Mustafa
Drop the Service OracleServiceSID
Reviewer, March 07, 2003 - 4:25 am UTC
Hi
Try drop the service and recreate it using
oradim -new -sid <sid_name> -intpwd -startmode auto -pfile ../init.ora
Idle Instance ?
kumar, May 29, 2003 - 11:23 am UTC
Tom,
Can you explain what 'Connected to an Idle Instance' means ?
May 29, 2003 - 1:35 pm UTC
it means Oracle was not started.
Startup Db from client ..
A reader, June 09, 2003 - 6:16 am UTC
hi Tom ..
how can we startup db from client side. ?
Thanx ..
Back to UNIX/LINUX process model...
fan, June 09, 2003 - 5:28 pm UTC
Tom,
On Windoz server, "net start oracleservie<SID>"
will load the exe and start the database......
On 9.2 on LINUX, I looked at dbstart script,
I see it launches Sqlplus and issue "startup"
My question : so is this the single command that actually load/started the Oracle process(es) first and mount, open the database ? Is this the sequence of events ?....
and dbshut does the reverse.
Thanks
June 09, 2003 - 7:00 pm UTC
yes, on linux, you need no "services", you just type startup
Re: Startup Db from client .. June 09, 2003
Sorry, June 14, 2003 - 4:23 am UTC
i m answering
/*
Startup Db from client .. June 09, 2003
Reviewer: A reader from Pal
hi Tom ..
how can we startup db from client side. ?
Thanx ..
*/
configure a nodefault listener .. on database and start the listener ..
connect sys/<<Password>>@host_string as sysdba
and then issue
Startup
June 14, 2003 - 8:49 am UTC
it is a lot more complex then that...
*windows*, it is all about services, if the service isn't running on the server, it isn't going to start, there is "nothing" to connect to.
8i, where is your pfile? how are you going to get that?
I use different soft to connect to server...
Sikandar Hayat, June 14, 2003 - 12:56 pm UTC
I have 5 different servers so I use NetOP and Radmin softwares which give me the desktop of each server and very easy to do any actitiy.
In Win2000 there is remote assistance feature so you may use it to get the desktop of your db server on your machine.
I don't like to play with NT/2K services becuase these are not trustable. Sometime you stop service and unable to restart it.
June 14, 2003 - 1:59 pm UTC
if you don't start a server on nt, you ain't going to start the database. you need the database service running, else "startup" isn't going to be happening.
A reader, November 02, 2003 - 8:22 pm UTC
My oracle services stops by themselves after restarting them
Godwin, December 24, 2003 - 9:25 am UTC
Hi Tom,
We are running two instances on Oracle 8.0.5.0.0 Enterprise Edition. One of the instances has to be restarted each morning because it stops by itself after it has been started.My operating system is windows 2000 server and each day i have to go the control panel-services to restart these oracle services for the database to work. the services that i normally restart are: OracleStartIDD and OracleServiceIDD. what do you think is the cause? At the eventviewer i see this error message:"The service did'nt respond to the start or control request in a timely fashion"
thanks
December 24, 2003 - 10:16 am UTC
the database just doesn't "stop by itself"
do you reboot these boxes every night? if so -- why?
think about it -- the database won't just shutdown every night all by itself, you are doing something
A reader, December 24, 2003 - 10:53 am UTC
Hi,
If you are not restarting the servers, something really strange is happening check your alert.log, investigate what happens when the database goes down.
"The service did'nt respond to the start or control request in a timely fashion",
means that the time the database took to start, is more than the average, probably a recovery is happening, this doesn't means necesarily a problem.
If your database started anyway, you can ignore this problem, or start to analyze why is taking as much to start the service.
Problem still occuring-Here is my alert log file named iddALRT.log
Godwin, January 06, 2004 - 12:21 pm UTC
Hi,
Am still facing the same problem. You asked me to check my alert.log file and here is the details. I can't make any sense of what is in it since am not a DBA. Can you help analyze the problem? I will be grateful. I need your help as soon as possible.
---iddALRT.log file----
Dump file d:\idd\pdump\trace\iddALRT.LOG
Tue Jun 17 12:58:51 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Tue Jun 17 12:58:52 2003
CREATE DATABASE IDD
LOGFILE 'c:\orant\database\logIDD1.ora' SIZE 1024K,
'd:\idd\logfiles\logIDD2.ora' SIZE 1024K
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXLOGHISTORY 1
DATAFILE 'c:\orant\database\Sys1IDD.ora' SIZE 50M
MAXDATAFILES 254
MAXINSTANCES 1
CHARACTER SET WE8ISO8859P1
NATIONAL CHARACTER SET WE8ISO8859P1
Tue Jun 17 12:58:54 2003
Database mounted in Exclusive Mode.
Tue Jun 17 12:58:57 2003
Successful mount of redo thread 1, with mount id 1607943948.
Tue Jun 17 12:58:57 2003
Picked broadcast on commit scheme to generate SCNs
Tue Jun 17 12:58:58 2003
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Successful open of redo thread 1.
Tue Jun 17 12:58:58 2003
SMON: enabling cache recovery
Tue Jun 17 12:58:58 2003
create tablespace SYSTEM datafile 'c:\orant\database\Sys1IDD.ora' SIZE 50M
default storage (initial 10K next 10K) online
Tue Jun 17 12:59:10 2003
Completed: create tablespace SYSTEM datafile 'c:\orant\datab
Tue Jun 17 12:59:10 2003
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
Tue Jun 17 12:59:12 2003
Thread 1 advanced to log sequence 2
Current log# 2 seq# 2 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 cannot allocate new log, sequence 3
Checkpoint not complete
Current log# 2 seq# 2 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 3
Current log# 1 seq# 3 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 4
Current log# 2 seq# 4 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 cannot allocate new log, sequence 5
Checkpoint not complete
Current log# 2 seq# 4 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 5
Current log# 1 seq# 5 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 6
Current log# 2 seq# 6 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Tue Jun 17 12:59:26 2003
SMON: enabling tx recovery
Tue Jun 17 12:59:29 2003
Completed: CREATE DATABASE IDD
LOGFILE 'c:\orant\database\log
Tue Jun 17 12:59:31 2003
ALTER DATABASE DATAFILE 'c:\orant\database\Sys1IDD.ora' AUTOEXTEND ON
Completed: ALTER DATABASE DATAFILE 'c:\orant\database\Sys1IDD
Tue Jun 17 12:59:31 2003
CREATE ROLLBACK SEGMENT SYSROL TABLESPACE "SYSTEM" STORAGE (INITIAL 100K NEXT 100K)
Completed: CREATE ROLLBACK SEGMENT SYSROL TABLESPACE "SYSTEM"
Tue Jun 17 12:59:31 2003
ALTER ROLLBACK SEGMENT "SYSROL" ONLINE
Completed: ALTER ROLLBACK SEGMENT "SYSROL" ONLINE
Tue Jun 17 12:59:33 2003
Thread 1 advanced to log sequence 7
Current log# 1 seq# 7 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
Current log# 1 seq# 7 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 8
Current log# 2 seq# 8 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 9
Current log# 1 seq# 9 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 10
Checkpoint not complete
Current log# 1 seq# 9 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 10
Current log# 2 seq# 10 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 11
Current log# 1 seq# 11 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 12
Checkpoint not complete
Current log# 1 seq# 11 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 12
Current log# 2 seq# 12 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 13
Current log# 1 seq# 13 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 14
Checkpoint not complete
Current log# 1 seq# 13 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 14
Current log# 2 seq# 14 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 15
Current log# 1 seq# 15 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 16
Current log# 2 seq# 16 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 17
Current log# 1 seq# 17 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 18
Current log# 2 seq# 18 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 19
Current log# 1 seq# 19 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 20
Current log# 2 seq# 20 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 21
Current log# 1 seq# 21 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 22
Checkpoint not complete
Current log# 1 seq# 21 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 22
Current log# 2 seq# 22 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 23
Current log# 1 seq# 23 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 24
Checkpoint not complete
Current log# 1 seq# 23 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 24
Current log# 2 seq# 24 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 25
Current log# 1 seq# 25 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 26
Current log# 2 seq# 26 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 27
Current log# 1 seq# 27 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 28
Current log# 2 seq# 28 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 29
Current log# 1 seq# 29 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 30
Current log# 2 seq# 30 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 cannot allocate new log, sequence 31
Checkpoint not complete
Current log# 2 seq# 30 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 31
Current log# 1 seq# 31 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 32
Current log# 2 seq# 32 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 33
Current log# 1 seq# 33 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 34
Current log# 2 seq# 34 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 cannot allocate new log, sequence 35
Checkpoint not complete
Current log# 2 seq# 34 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 35
Current log# 1 seq# 35 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 36
Current log# 2 seq# 36 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 37
Current log# 1 seq# 37 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 38
Current log# 2 seq# 38 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 39
Current log# 1 seq# 39 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 40
Current log# 2 seq# 40 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 41
Current log# 1 seq# 41 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 42
Current log# 2 seq# 42 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 43
Current log# 1 seq# 43 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 44
Current log# 2 seq# 44 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 45
Current log# 1 seq# 45 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 46
Current log# 2 seq# 46 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 47
Current log# 1 seq# 47 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 48
Current log# 2 seq# 48 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 49
Current log# 1 seq# 49 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 cannot allocate new log, sequence 50
Checkpoint not complete
Current log# 1 seq# 49 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 50
Current log# 2 seq# 50 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 51
Current log# 1 seq# 51 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 52
Current log# 2 seq# 52 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 53
Current log# 1 seq# 53 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 54
Current log# 2 seq# 54 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 55
Current log# 1 seq# 55 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Thread 1 advanced to log sequence 56
Current log# 2 seq# 56 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Thread 1 advanced to log sequence 57
Current log# 1 seq# 57 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Tue Jun 17 13:03:22 2003
CREATE TABLESPACE RBS_IDD DATAFILE 'd:\idd\rollback\Rbs1IDD.ora' SIZE 1000M
DEFAULT STORAGE ( INITIAL 1024K NEXT 1024K MINEXTENTS 2 MAXEXTENTS 121 PCTINCREASE 0)
Tue Jun 17 13:07:07 2003
Completed: CREATE TABLESPACE RBS_IDD DATAFILE 'd:\idd\rollbac
Tue Jun 17 13:07:07 2003
ALTER DATABASE DATAFILE 'd:\idd\rollback\Rbs1IDD.ora' AUTOEXTEND ON
Completed: ALTER DATABASE DATAFILE 'd:\idd\rollback\Rbs1IDD.o
Tue Jun 17 13:07:07 2003
ALTER TABLESPACE SYSTEM
DEFAULT STORAGE ( INITIAL 100K NEXT 100K MINEXTENTS 1 MAXEXTENTS 300 PCTINCREASE 1)
Completed: ALTER TABLESPACE SYSTEM
DEFAULT STORAGE ( INITIAL
Tue Jun 17 13:07:08 2003
CREATE TABLESPACE User_idd DATAFILE 'd:\idd\datafiles\Usr1IDD.ora' SIZE 2000M
DEFAULT STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 1 MAXEXTENTS 121 PCTINCREASE 1)
Tue Jun 17 13:16:16 2003
Completed: CREATE TABLESPACE User_idd DATAFILE 'd:\idd\datafi
Tue Jun 17 13:16:16 2003
ALTER DATABASE DATAFILE 'd:\idd\datafiles\Usr1IDD.ora' AUTOEXTEND ON
Completed: ALTER DATABASE DATAFILE 'd:\idd\datafiles\Usr1IDD.
Tue Jun 17 13:16:17 2003
CREATE TABLESPACE Temp_IDD DATAFILE 'd:\idd\temp\Tmp1IDD.ora' SIZE 500M
DEFAULT STORAGE ( INITIAL 100K NEXT 100K MINEXTENTS 1 MAXEXTENTS 121 PCTINCREASE 0) TEMPORARY
Tue Jun 17 13:17:50 2003
Completed: CREATE TABLESPACE Temp_IDD DATAFILE 'd:\idd\temp\T
Tue Jun 17 13:17:50 2003
ALTER DATABASE DATAFILE 'd:\idd\temp\Tmp1IDD.ora' AUTOEXTEND ON
Completed: ALTER DATABASE DATAFILE 'd:\idd\temp\Tmp1IDD.ora'
Tue Jun 17 13:17:51 2003
CREATE TABLESPACE Index_idd DATAFILE 'd:\idd\index\Indx1IDD.ora' SIZE 2000M
DEFAULT STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 1 MAXEXTENTS 121 PCTINCREASE 1)
Tue Jun 17 13:23:56 2003
Completed: CREATE TABLESPACE Index_idd DATAFILE 'd:\idd\index
Tue Jun 17 13:23:56 2003
ALTER DATABASE DATAFILE 'd:\idd\index\Indx1IDD.ora' AUTOEXTEND ON
Completed: ALTER DATABASE DATAFILE 'd:\idd\index\Indx1IDD.ora
Tue Jun 17 13:23:56 2003
CREATE PUBLIC ROLLBACK SEGMENT RB0 TABLESPACE "RBS_IDD"
STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 2 MAXEXTENTS 121 )
Completed: CREATE PUBLIC ROLLBACK SEGMENT RB0 TABLESPACE "RBS
Tue Jun 17 13:23:57 2003
CREATE PUBLIC ROLLBACK SEGMENT RB1 TABLESPACE "RBS_IDD"
STORAGE ( INITIAL 50K NEXT 50K MINEXTENTS 2 MAXEXTENTS 121 )
Completed: CREATE PUBLIC ROLLBACK SEGMENT RB1 TABLESPACE "RBS
Tue Jun 17 13:23:57 2003
ALTER ROLLBACK SEGMENT "RB0" ONLINE
Completed: ALTER ROLLBACK SEGMENT "RB0" ONLINE
Tue Jun 17 13:23:57 2003
ALTER ROLLBACK SEGMENT "RB1" ONLINE
Completed: ALTER ROLLBACK SEGMENT "RB1" ONLINE
Tue Jun 17 13:23:57 2003
alter rollback segment "SYSROL" offline
Completed: alter rollback segment "SYSROL" offline
Dump file d:\idd\pdump\trace\iddALRT.LOG
Wed Jun 18 05:45:26 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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 Jun 18 05:45:26 2003
alter database "idd" mount exclusive
Wed Jun 18 05:45:31 2003
Successful mount of redo thread 1, with mount id 1607975675.
Wed Jun 18 05:45:31 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Wed Jun 18 05:45:31 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 1 Seq 57 Reading mem 0
Mem# 0 errs 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Wed Jun 18 05:46:00 2003
kccrsz: expanded controlfile section 9 from 56 to 112 records
requested to grow by 56 record(s); added 1 block(s) of records
Thread 1 advanced to log sequence 58
Thread 1 opened at log sequence 58
Current log# 2 seq# 58 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Successful open of redo thread 1.
Wed Jun 18 05:46:01 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Wed Jun 18 05:46:04 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Mon Jun 23 07:09:39 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Mon Jun 23 07:09:43 2003
alter database "idd" mount exclusive
Mon Jun 23 07:09:49 2003
Successful mount of redo thread 1, with mount id 1608464699.
Mon Jun 23 07:09:49 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Mon Jun 23 07:09:49 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 2 Seq 58 Reading mem 0
Mem# 0 errs 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Mon Jun 23 07:09:53 2003
Thread 1 advanced to log sequence 59
Thread 1 opened at log sequence 59
Current log# 1 seq# 59 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Successful open of redo thread 1.
Mon Jun 23 07:09:54 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Mon Jun 23 07:10:00 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Wed Jun 25 20:41:54 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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 Jun 25 20:41:54 2003
alter database "idd" mount exclusive
Wed Jun 25 20:41:59 2003
Successful mount of redo thread 1, with mount id 1608658327.
Wed Jun 25 20:41:59 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Wed Jun 25 20:41:59 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 1 Seq 59 Reading mem 0
Mem# 0 errs 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Wed Jun 25 20:42:03 2003
Thread 1 advanced to log sequence 60
Thread 1 opened at log sequence 60
Current log# 2 seq# 60 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Successful open of redo thread 1.
Wed Jun 25 20:42:04 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Wed Jun 25 20:42:08 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Sun Jun 29 18:14:17 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Sun Jun 29 18:14:17 2003
alter database "idd" mount exclusive
Sun Jun 29 18:14:22 2003
Successful mount of redo thread 1, with mount id 1609011454.
Sun Jun 29 18:14:22 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Sun Jun 29 18:14:22 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 2 Seq 60 Reading mem 0
Mem# 0 errs 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Sun Jun 29 18:14:26 2003
Thread 1 advanced to log sequence 61
Thread 1 opened at log sequence 61
Current log# 1 seq# 61 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Successful open of redo thread 1.
Sun Jun 29 18:14:27 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Sun Jun 29 18:14:32 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Thu Jul 03 07:51:58 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Thu Jul 03 07:51:58 2003
alter database "idd" mount exclusive
Thu Jul 03 07:52:03 2003
Successful mount of redo thread 1, with mount id 1609378466.
Thu Jul 03 07:52:03 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Thu Jul 03 07:52:03 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 1 Seq 61 Reading mem 0
Mem# 0 errs 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Thu Jul 03 07:52:07 2003
Thread 1 advanced to log sequence 62
Thread 1 opened at log sequence 62
Current log# 2 seq# 62 mem# 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Successful open of redo thread 1.
Thu Jul 03 07:52:08 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Thu Jul 03 07:52:11 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Mon Jul 07 07:43:05 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Mon Jul 07 07:43:05 2003
alter database "idd" mount exclusive
Mon Jul 07 07:43:10 2003
Successful mount of redo thread 1, with mount id 1609705101.
Mon Jul 07 07:43:10 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Mon Jul 07 07:43:10 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 2 Seq 62 Reading mem 0
Mem# 0 errs 0: D:\IDD\LOGFILES\LOGIDD2.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Mon Jul 07 07:43:13 2003
Thread 1 advanced to log sequence 63
Thread 1 opened at log sequence 63
Current log# 1 seq# 63 mem# 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Successful open of redo thread 1.
Mon Jul 07 07:43:14 2003
SMON: enabling cache recovery
SMON: enabling tx recovery
Mon Jul 07 07:43:16 2003
Completed: alter database "idd" open
Dump file d:\idd\pdump\trace\iddALRT.LOG
Mon Jul 07 23:55:26 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
processes = 100
shared_pool_size = 10000000
control_files = c:\orant\database\ctl1IDD.ora, d:\idd\controls\ctl2IDD.ora
db_block_buffers = 550
db_block_size = 2048
compatible = 8.0.5.0.0
log_buffer = 32768
log_checkpoint_interval = 8000
log_checkpoint_timeout = 0
db_files = 1020
db_file_multiblock_read_count= 16
dml_locks = 200
sequence_cache_entries = 30
sequence_cache_hash_buckets= 23
remote_login_passwordfile= SHARED
sort_area_size = 65536
db_name = IDD
background_dump_dest = d:\idd\pdump\trace
user_dump_dest = d:\idd\udump\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
Mon Jul 07 23:55:26 2003
alter database "idd" mount exclusive
Mon Jul 07 23:55:31 2003
Successful mount of redo thread 1, with mount id 1609749363.
Mon Jul 07 23:55:31 2003
Database mounted in Exclusive Mode.
Completed: alter database "idd" mount exclusive
Mon Jul 07 23:55:31 2003
alter database "idd" open
Beginning crash recovery of 1 threads
Recovery of Online Redo Log: Thread 1 Group 1 Seq 63 Reading mem 0
Mem# 0 errs 0: C:\ORANT\DATABASE\LOGIDD1.ORA
Crash recovery completed successfully
Picked broadcast on commit scheme to generate SCNs
Mon Jul 07 23:55:35 2003
Thread 1 advanced t
January 06, 2004 - 2:12 pm UTC
umm, it is january.
this says the last time the db was started was july
if you have a really big alert file that got truncated (thank goodness!!!!!) please don't post it here, i don't want it.
do you REBOOT you windoze server each night (as asked)
juancarlosreyesp@yahoo.com, January 06, 2004 - 5:52 pm UTC
Hi,
Tom is right it is not a good idea to post all your alert.log
you should only post the last two startup process maximum.
What you have to check in your alert log is
-->Mon Jul 07 07:43:05 2003
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V5.0, OS V8.147, CPU type 586
-->Starting up ORACLE RDBMS Version: 8.0.5.0.0.
System parameters with non-default values:
This means your database had started up
-->Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 1
Tue Jan 06 18:38:26 2004
alter database close normal
Tue Jan 06 18:38:26 2004
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Jan 06 18:38:26 2004
-->Shutting down archive processes
Archiving is disabled
Tue Jan 06 18:38:26 2004
ARCH shutting down
-->alter database dismount
This means your database had been shutdown manually, not crashed.
If after your start up you find things like this, as your have.
Beginning crash recovery of 1 threads
Started recovery at
Thread 1: logseq 855, block 3049, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 855 Reading mem 0
Mem# 0 errs 0: D:\ORAEDVB\LOGFILES\LOG_2EDVB.ORA
Mem# 1 errs 0: E:\ORAEDVB\LOGFILES\LOG_2EDVB.ORA
means its doing a crash recovery, it seems your server is shutdown, or someone is playing with it.
Based on my experience what I see is your alert log says you are not shutting down your database, else crashing.
If you are not doing that, go to your office with your bed and see what happens one night, how the database gets shuts down, some one is restarting your database or other strange thing is happening.
You can do a normal startup and shutdown to see the difference, I suggest you to rename the current alert log.
:)
A reader, January 23, 2004 - 10:41 am UTC
Crash Recovery and User_DUMP_DEST
Deepak Haldiya, February 21, 2005 - 9:17 pm UTC
Hi Tom,
Everytime a crash recovery takes place, oracle writes a trace file in User_Dump_Dest, apart from writing to the alert log. Why is that so? I was of the understanding that the trace files are written to the User_Dump_Dest only on the requests of Server Process.
Please find the trace file generated below.
Dump file d:\ora92\admin\ora92\udump\ora92_ora_1492.trc
Thu Dec 16 21:54:08 2004
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Instance name: ora92
Redo thread mounted by this instance: 0 <none>
Oracle process number: 12
Windows thread id: 1492, image: ORACLE.EXE
*** SESSION ID:(9.1) 2004-12-16 21:54:08.000
(blkno = 0x7a, size = 276, max = 1, in-use = 1, last-recid= 0)
(blkno = 0x7b, size = 56, max = 145, in-use = 1, last-recid= 1)
Thread checkpoint rba:0x000013.00000002.0010 scn:0x0000.0009ee9f
On-disk rba:0x000013.00000856.0000 scn:0x0000.0009f923
Use incremental checkpoint cache-low RBA
Thread 1 recovery from rba:0x000013.00000003.0000 scn:0x0000.00000000
----- Redo read statistics for thread 1 -----
Read rate (ASYNC) = 1065Kb/sec => 2131 blocks in 1s
Read buffer = 8192Kb (16384 blocks)
Longest record = 0Kb
Record moves = 0/4543 (0%)
----------------------------------------------
*** 2004-12-16 21:54:10.000
KCRA: start recovery claims for 110 data blocks
*** 2004-12-16 21:54:10.000
KCRA: buffers claimed = 110/110, eliminated = 0
Dump file d:\ora92\admin\ora92\udump\ora92_ora_1492.trc
Mon Feb 21 19:40:15 2005
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Instance name: ora92
Redo thread mounted by this instance: 0 <none>
Oracle process number: 12
Windows thread id: 1492, image: ORACLE.EXE
*** SESSION ID:(9.1) 2005-02-21 19:40:15.000
(blkno = 0x7a, size = 276, max = 1, in-use = 1, last-recid= 0)
(blkno = 0x7b, size = 56, max = 145, in-use = 1, last-recid= 1)
Thread checkpoint rba:0x000040.00000353.0010 scn:0x0000.00239a5b
On-disk rba:0x000040.00001d65.0000 scn:0x0000.0023bebe
Use incremental checkpoint cache-low RBA
Thread 1 recovery from rba:0x000040.00000f9e.0000 scn:0x0000.00000000
----- Redo read statistics for thread 1 -----
Read rate (ASYNC) = 881Kb/sec => 3527 blocks in 2s
Read buffer = 8192Kb (16384 blocks)
Longest record = 0Kb
Record moves = 0/7753 (0%)
----------------------------------------------
*** 2005-02-21 19:40:29.000
KCRA: start recovery claims for 65 data blocks
*** 2005-02-21 19:40:29.000
KCRA: buffers claimed = 65/65, eliminated = 0
Thanks
February 22, 2005 - 8:31 am UTC
<quote>I was of
the understanding that the trace files are written to the User_Dump_Dest only on
the requests of Server Process.
</quote>
and that is absolutely true and the server process doing recovery did request this. it started in 9.2 and still happens in 10g, it is diagnostic information useful for monitoring what crash recovery (which should be an "exceptional" condition, not the norm) did and how much it had to do.
how do i start the database 10g under RHAL 3.0
Drumil Narayan, March 08, 2005 - 9:48 am UTC
hello Tom,
just i installed the database, shutdown it with oem only.
after that i reboot the machine, then i am trying to start up the databas its not getting up.
i want to start it with comand line arguments.
though the lsnrctl and sqlplus files are there in
my $ORACLE_HOME/bin, they are not getting executed..
now from where should i start from
thanx in advance..drumil
March 08, 2005 - 11:32 am UTC
insufficient data here...
I'd log in, type
$ sqlplus "/ as sysdba"
startup
OK
Siva, April 09, 2005 - 9:26 am UTC
Hi Tom,
Could you please provide documentation link for
STARTUP and SHUTDOWN commands?
April 09, 2005 - 12:02 pm UTC
know the ip addresses on network
Salah beck, April 10, 2005 - 7:01 am UTC
Hi Tom
i want to get all ip addresses and computer names for clients on my network.
how i can do it ?
Thank You ..
April 10, 2005 - 10:39 am UTC
ask the networking guys?
problem with database open
shams, May 26, 2005 - 4:21 pm UTC
hi tom,
i'm unable to open the database.can u help me to figure it out.
os=win2000
oracle=9i
here i attach the corresponding "alert file" and "trace file"
:::alert file :::
Dump file d:\oracle9\ora91\admin\new\bdump\alert_newins.log
Thu May 26 20:06:41 2005
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 3, CPU type 586
Thu May 26 20:06:41 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 33554432
large_pool_size = 8388608
java_pool_size = 16777216
control_files = d:\oracle9\ora91\oradata\new\log_dest_1\O1_MF_19791T00_.CTL, d:\oracle9\ora91\oradata\new\log_dest_2\O1_MF_19791V00_.CTL
db_block_size = 8192
db_cache_size = 16777216
compatible = 9.2.0.0.0
log_buffer = 1048576
db_file_multiblock_read_count= 16
db_create_file_dest = D:\oracle9\ora91\oradata\new\file_dest
db_create_online_log_dest_1= D:\oracle9\ora91\oradata\new\log_dest_1
db_create_online_log_dest_2= D:\oracle9\ora91\oradata\new\log_dest_2
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS
undo_retention = 10800
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = newins
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = d:\oracle9\ora91\admin\new\bdump
user_dump_dest = d:\oracle9\ora91\admin\new\udump
core_dump_dest = d:\oracle9\ora91\admin\new\cdump
audit_trail = TRUE
sort_area_size = 2097152
db_name = new
open_cursors = 300
ifile = D:\oracle9\ora91\admin\new\pfile\init.ora
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 16777216
workarea_size_policy = AUTO
aq_tm_processes = 1
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
CJQ0 started with pid=8
QMN0 started with pid=9
Thu May 26 20:06:46 2005
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu May 26 20:08:38 2005
alter database mount
Thu May 26 20:08:43 2005
Successful mount of redo thread 1, with mount id 2040713862.
Thu May 26 20:08:43 2005
Database mounted in Exclusive Mode.
Completed: alter database mount
Thu May 26 20:12:26 2005
alter database open
Thu May 26 20:12:26 2005
Beginning crash recovery of 1 threads
Thu May 26 20:12:27 2005
Started first pass scan
Thu May 26 20:12:30 2005
Completed first pass scan
64 redo blocks read, 12 data blocks need recovery
Thu May 26 20:12:30 2005
Started recovery at
Thread 1: logseq 6, block 2, scn 0.68666
Recovery of Online Redo Log: Thread 1 Group 2 Seq 6 Reading mem 0
Mem# 0 errs 0: D:\ORACLE9\ORA91\ORADATA\NEW\LOG_DEST_1\O1_MF_2_19791W00_.LOG
Mem# 1 errs 0: D:\ORACLE9\ORA91\ORADATA\NEW\LOG_DEST_2\O1_MF_2_19791X00_.LOG
Thu May 26 20:12:31 2005
Ended recovery at
Thread 1: logseq 6, block 66, scn 0.88757
12 data blocks read, 12 data blocks written, 64 redo blocks read
Crash recovery completed successfully
Thu May 26 20:12:33 2005
Thread 1 advanced to log sequence 7
Thread 1 opened at log sequence 7
Current log# 1 seq# 7 mem# 0: D:\ORACLE9\ORA91\ORADATA\NEW\LOG_DEST_1\O1_MF_1_19791V00_.LOG
Current log# 1 seq# 7 mem# 1: D:\ORACLE9\ORA91\ORADATA\NEW\LOG_DEST_2\O1_MF_1_19791W00_.LOG
Successful open of redo thread 1.
Thu May 26 20:12:34 2005
SMON: enabling cache recovery
Thu May 26 20:12:37 2005
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Thu May 26 20:12:38 2005
SMON: enabling tx recovery
Thu May 26 20:12:38 2005
Database Characterset is WE8MSWIN1252
Updating 7.0.0.0.0 NLS parameters in sys.props$
-- adding 9.2.0.1.0 NLS parameters.
Thu May 26 20:12:39 2005
Errors in file d:\oracle9\ora91\admin\new\udump\newins_ora_796.trc:
ORA-01403: no data found
Error 1403 happened during db open, shutting down database
USER: terminating instance due to error 1403
Instance terminated by USER, pid = 796
ORA-1092 signalled during: alter database open...
:::trace file::::
Dump file d:\oracle9\ora91\admin\new\udump\newins_ora_1340.trc
Thu May 26 20:26:31 2005
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 3, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Windows 2000 Version 5.0 Service Pack 3, CPU type 586
Instance name: newins
Redo thread mounted by this instance: 1
Oracle process number: 12
Windows thread id: 1340, image: ORACLE.EXE
*** SESSION ID:(9.3) 2005-05-26 20:26:31.000
Thread checkpoint rba:0x000007.00000002.0010 scn:0x0000.00015ab7
On-disk rba:0x000007.00000044.0000 scn:0x0000.00015b03
Use incremental checkpoint cache-low RBA
Thread 1 recovery from rba:0x000007.00000003.0000 scn:0x0000.00000000
----- Redo read statistics for thread 1 -----
Read rate (ASYNC) = 16Kb/sec => 65 blocks in 2s
Read buffer = 8192Kb (16384 blocks)
Longest record = 0Kb
Record moves = 0/101 (0%)
----------------------------------------------
*** 2005-05-26 20:26:33.000
KCRA: start recovery claims for 12 data blocks
*** 2005-05-26 20:26:33.000
KCRA: buffers claimed = 12/12, eliminated = 0
ORA-01403: no data found
May 26, 2005 - 7:35 pm UTC
"U" isn't here, and I've yet to meet this "U" character.
you do have a tar open with support right?
but tell us, what was the last thing you did after that last successful open? That is "what changed"
shams, May 31, 2005 - 3:53 am UTC
U'r right. the last time when i opend the database was'nt closed successfully bcz of power failure. after that i mount the database and rename the log member of both the log group(i think may be all the members are cleared). and then issue alter database open. at this time the database is need to media recover bcz of last uncleaned shutdown. but it did'nt get any redo info from log file(my database is in noarchivelog mode) to synchronize the datafile and failed to startup. can i able to start it anyway
Thanks
May 31, 2005 - 7:58 am UTC
massive keyboard failure is in your future. Many very important keys are not being transmitted already. You better look into that.
You cannot "rename" log members.
I recommend you contact support so they can find out what really took place (the exact commands entered) and see if there is anything that can be done.
Check init.ora file
A reader, August 24, 2005 - 8:59 am UTC
Tom,
I manage a very important productive system. The only option I have to restart the system is to schedule a reboot on night Sat/Sun. Is there any possibility to check after altering init.ora file, that the file is not corrupt and the Oracle instance will not have any problem to start using this init.ora file (without restarting the instance)
Something like startup /verify (only verify init.ora file, not really restart...). I did not use spfile currently because the system was migrated from Oracle 8 and they used startup pfile=.....in their backup scripts.
August 24, 2005 - 2:12 pm UTC
not really, for example:
processes=5000
that is "valid", but you'll only find out after you try to start the database with it if you have configured your system to SUPPORT 5000 processes.
In 9i, with spfiles, it is harder to get "totally invalid" values into the spfile (parameter file), but you can still put values that are valid, but won't work and aren't know not to work until you restart.
You cannot have an important production system that has to be up AND do unattended shutdown/startups, that is an oxymoron.
why would you schedule a reboot of a production server? Unless you were there to do some maintenance -- why would you reboot the thing?
Steve, October 05, 2005 - 9:57 am UTC
I'm under a good deal of pressure to allow a weekly scheduled re-boot of our production servers which run on Wintel. Trouble is, we have a so-called database expert centre that recommends weekly re-boots of Wintel boxes, but I'm saying that it's not a good thing and should only take place because it HAS to - for maintenance - not just someone thinks it's a good idea. Can you help flesh out the arguments - I've told them that I won't be around at 3am on a Sunday morning if the db fails to re-start following such a reboot!
October 05, 2005 - 11:29 am UTC
I don't run windows in real life, so I cannot comment as to whether it really needs it or not.
but unattended reboots are dangerous - OS might not start, database might not start, service X might not restart.
what is my missing step
Jen, February 20, 2006 - 9:22 pm UTC
hi Tom, may i know what are the missing configuration i need to do to overcome the problem below?
SQL> CONN sys as sysdba
Enter password:
Connected.
SQL> SHUTDOWN immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP mount
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
thanks
February 21, 2006 - 7:38 am UTC
did you really connect directly as you say you are.
Or did you connect over the network.
what is my missing step
Jen, February 22, 2006 - 12:42 am UTC
Yes, i did it through my local machine, not through the network.
Is there anything to do with the listener.ora? or do i need to configure extra thing in my listener.ora? this is how my current listener.ora setting...
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = jennifer711-1)(PORT = 1521))
)
February 22, 2006 - 8:38 am UTC
what is TWO_TASK set to (unix right?) - environment variable
what is my missing step
Jen, February 22, 2006 - 10:51 am UTC
not unix but window xp
February 22, 2006 - 12:32 pm UTC
do you have local set?
(local is the same as unix TWO_TASK but for windows)
You should be able to
connect / as sysdba
no password, no nothing if you are truly local.
what is my missing step
Jen, February 23, 2006 - 5:23 am UTC
i got it ;)
thanks Tom
Start the db over a network
Rihaz, September 18, 2008 - 4:40 pm UTC
How to start the database from the remote machine ( over the network) ....
C:\>sqlplus xxx/xxx@xxxx as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Thu Sep 18 15:51:32 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
SQL> startup;
ORA-24324: service handle not initialized