Solved

Oradim not shutting the db when server reboots.oradim -EDIT -SID PERISTAT -STARTMODE a -SHUTMODE i -PFILE

Posted on 2006-10-27
5
577 Views
Last Modified: 2012-06-21
I need that the database shutsdown in immediate manner before rebotting sever.the Oradim is not functioning in this way.
How should I approach this issue?
0
Comment
Question by:LindaC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 13

Expert Comment

by:anand_2000v
ID: 17820655
what is you OS ??
0
 
LVL 8

Author Comment

by:LindaC
ID: 17820677
If i include the "oradim" command, you should know is some kind of indows server.
Specifically is a Windows 2003 server R2
0
 
LVL 13

Expert Comment

by:anand_2000v
ID: 17820762
what is you oracle version ?? If it is 8 on windows 2000 and above ,its a known bug which makes auto shutdown impossible (which  is de supported ).
0
 
LVL 8

Author Comment

by:LindaC
ID: 17820786
Version 9.2.0.8
0
 
LVL 35

Accepted Solution

by:
Mark Geerlings earned 125 total points
ID: 17821339
Oracle9 on WindowsServer2003 occasionally hangs when the shutdown command is given.  This may be a bug.  We used that combination for a couple years and I filed a TAR with Oracle on it, but they never found a solution.

I did not use the "oradim" executable for this.  I used a *.SQL script that had the line: "shutdown immediate", and called that from a batch file that called SQL*Plus to run the *.sql file.  But this hung occasionally for us.  When that happened, I did a "net stop OracleService[SID]" from a command prompt, or just rebooted the Windows server.

I automated this process with two different batch files that were scheduled via the Windows Task Scheduler.  The first one first renamed a special text file that I kept just for that purpose (named: "keep_me.txt") to: "weekend.txt" then attempted to do an Oracle shutdown and cold backup.  If that succeeded (and that took about 30-40 minutes on our server, then at the end of the process, it restarted Oracle, then renamed: "weekend.txt" back to "keep_me.txt".

The second batch file was scheduled to run one hour later than the first one, early Sunday mornings.  It checked for the existance of the file named "weekend.txt".  If it found it (which indicated that the shutdown-backup-restart process failed, probably in the shutdown) it simply did: "shutdown.exe /R /F".  This forced a server reboot, which restarted Oracle.  I didn't get a cold backup that way, but we also did hot backups each night, and this way at least the server and database were restarted for the next week.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever had to make fundamental changes to a table in Oracle, but haven't been able to get any downtime?  I'm talking things like: * Dropping columns * Shrinking allocated space * Removing chained blocks and restoring the PCTFREE * Re-or…
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
This video explains what a user managed backup is and shows how to take one, providing a couple of simple example scripts.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question