Job and shutdown immediate

Hi,
On our database there is too many job which running every 10 sec, and other each minute (but this job run for 10 minutes !).
I would like to stop database, but how will work the command shutdown immediate ? It will wait the end of each job ? And for job which execute with 10 minutes of delay ?
Nicolas.

IMMEDIATE
Does not wait for current calls to complete or users to disconnect from the database.
Further connects are prohibited. The database is closed and dismounted. The instance is shutdown and no instance recovery is required on the next database startup.
Joel PÃ©rez
http://www.oracle.com/technology/experts

Similar Messages

Scheduled shutdown immediate and full database export

Hi all,
The database is Oracle 10g.
How to make a scheduled shutdown immediate and full database export ? I want to use a batch file for it so I can make a sheduled task from the windows control panel everyday at 2 am. So what to write in the batch file because I am a bit new to 10g ?
Thank you very much

>
How to make a scheduled shutdown immediate and full database export ? I want to use a batch file for it so I can make a sheduled task from the windows control panel everyday at 2 am. So what to write in the batch file because I am a bit new to 10g ?No, you can't take logical backup after shutdown database.
If you want to schedule the logical backup of your database, just you can refer from here
Schema level
http://mohamedazar.wordpress.com/2010/04/18/datapump-scheduler-for-schema-level/
Full export
http://mohamedazar.wordpress.com/2010/02/16/dbms-scheduler-for-data-pump/

Shutdown immediate hangs and HVM of a database

Hi,
I have following questions,
1. What are the possible causes of SHUTDOWN IMMEDIATE command hangs
and doesnt responds.
2. What do u mean by High Water Mark(HVM) of a database. Because when we
give SHUTDOWN IMMEDIATE command there is message in alert log file
mentioning the HVM of a database.
3.Also is there any relationship between shutdown process taking long time to
shutdown a database and HVM of a database.
4. If the database instance is up for a long time then does it take long time to
shutdown a instance.
Thanks,
Girish A

Hello,
for 1.) view Metalink Note:375935.1. Maybe you even get an error: "SHUTDOWN: Waiting for active calls to complete". This has nothing to do with HWM but with already logged on sessions. Immediate means new connections are not able to log in, existing connetions are not disconnected at once.
for 2.) the HWM is the highest point to which datafiles have been filled up. This is the value to which you are able to shrink (if you desire to). View Metalink Note:1034330.6 for message "License high water mark" in alert.log at shutdown ("highest number of concurrent users sessions").
Greets,
Hannibal

Shutdown immediate hangs

SunOS 5.8
Database version: 9.2.0.4.0
Customer shutdown database every night for backup the datafiles to disk.
For your information, 2 weeks ago customer moved datafiles to a new disk.
The stoppscript has worked for a week.
And after a week the database will not shutdown.
We did a shutdown abort, and it works for a couple of days.
Now it happend again. The database will not go down.
Can't find any error messages!
Any suggestions?
# stoppscript
. $HOME/.profile
INSTANSER="BALA"
echo
echo "###########################################"
echo "# Startar nedtagning av O R A C L E #"
echo "###########################################"
echo
echo
echo "####### Stoppar LISTENER #######"
echo
$ORACLE_HOME/bin/lsnrctl << EOF
stop LISTENER
exit
EOF
for i in $INSTANSER
do
ORACLE_SID=$i
export ORACLE_SID
echo
echo "##### Stoppar instans - $ORACLE_SID #####"
echo
$ORACLE_HOME/bin/sqlplus /nolog << EOF
connect / as sysdba
shutdown immediate
startup exclusive restrict
shutdown
exit
EOF
done
echo
echo "########################################"
echo "# Slut nedtagning av O R A C L E #"
echo "########################################"
echo
# Alert_log
Tue Sep 5 01:16:48 2006
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 41
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Tue Sep 5 01:16:55 2006
ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Sep 5 01:16:56 2006
Shutting down archive processes
Archiving is disabled
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC0: Archival stopped
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC1: Archival stopped
Tue Sep 5 01:16:56 2006
Thread 1 closed at log sequence 11287
Successful close of redo thread 1.
Tue Sep 5 01:16:56 2006
Completed: ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:56 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Sep 5 08:15:15 2006
Shutting down instance (abort)

I am having similar problem. My server has been up for around 100 days now. And I extensively use XML DB in my code. So, now the DOM memory failed for me, so, I am doing shutdown immediate in the hope that it might fix it ( or atleast start where it is hanging).
Here is a snippet of my alert log file. Can you see where I am stuck at?
Thu Sep 21 14:01:15 2006
Process m001 died, see its trace file
Thu Sep 21 14:01:15 2006
ksvcreate: Process(m001) creation failed
Thu Sep 21 14:28:38 2006
Starting background process EMN0
EMN0 started with pid=19, OS id=2396
Thu Sep 21 14:28:38 2006
Shutting down instance: further logons disabled
Thu Sep 21 14:28:40 2006
Stopping background process CJQ0
Thu Sep 21 14:28:40 2006
Stopping background process QMNC
Thu Sep 21 14:28:42 2006
Stopping background process MMNL
Thu Sep 21 14:28:43 2006
Stopping background process MMON
Thu Sep 21 14:28:45 2006
Shutting down instance (immediate)
License high water mark = 23
Thu Sep 21 14:28:45 2006
Stopping Job queue slave processes
Thu Sep 21 14:28:45 2006
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Thu Sep 21 14:28:55 2006
ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:28:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Thu Sep 21 14:28:56 2006
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 411
Successful close of redo thread 1
Thu Sep 21 14:29:01 2006
Completed: ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:29:01 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
btw, This is my screen right now.
U:\Rahul\sql>sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Sep 21 14:28:16 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - Production
SQL> sho sga
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
SQL> shutdown immediate;
Database closed.
Database dismounted.
Ok, when I am writing this post, I came back with this message.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
Database mounted.
Database opened.
SQL>
Still, any comments would be really appreciated.
Thank you,
Rahul.
P.S - This is a 32 bit windows 2003 server. 10gR2.
Message was edited by:
rputtagunta

Using launchd to send an email on startup and shutdown

Hello All !
I'd like to get an email whenever my Mac starts up and shuts down, since I have to leave it unattended for quite some long periods of time (and even with the help of a UPS, power goes out anyway...). My Mac runs under Mac OS X Lion.
I found some help on the Internet, mainly from this page : http://www.syntaxtechnology.com/2009/06/email-on-shutdown-and-restart/ , which applies to Linux, and hoped it could work on Mac OS X (I thought at first I could just drop a script in something like /etc/init.d/ or /etc/rc.d/rc5.d but well... we have launchd instead...).
The first method listed in the page above worked well, but sends an email only on startup (for a reminder: you add a line that starts with @reboot in your crontab, and a command that sends directly an email).
I then tried to adapt the second method to Mac OS X, and succeeded partially: I wrote a small script based on what was shown on that page (a start and stop function, start gets called when the script is started, and stop gets called based on a trap on various kill signals, with an infinite wait loop: see below). I also wrote the plist file, loaded it in launchd and rebooted my Mac several times to test everything.
I get an email on each startup (yeah!), but the shutdown mail gets sent only at the next startup. So I guess that postfix gets killed by the shutdown process *before* being able to send my shutdown email :-(
So here are my main questions, if someone can help me:
1. is there a way to precisely call a script during the shutdown process, meaning giving it a priority so it gets called before postfix dies ? (like the rc directories and the naming conventions (KnnScriptName and SnnScriptName) found on some Linux/Unix).
2. is it possible to do that with launchd ? if not, what would be the Mac OS X sanctionned way of doing this ?
Other things:
3. my shell script writing ability is kind of rusty, so maybe I made some "very bad shell writingTM": l'm not sure putting an infinite while loop with a 15 second pause in it is the best way of telling a script to do nothing. There might other things in there that would make an Unix guru jump out of his chair: please tell me :-)
This is my plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC “-//Apple Computer//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
<plist version=“1.0”>
<dict>
<key>Disabled</key>
<false/>
<key>Label</key><string>org.amarante.startshutemail</string>
<key>ProgramArguments</key>
<array>
<string>/Library/Scripts/startshutemail-launchd.sh</string>
<string>start</string>
</array>
<key>RunAtLoad</key><true/>
</dict>
</plist>
And this is the script that does the job:
#!/bin/bash
# PHL 20120604 startshutemail-launchd.sh
# Send an email on startup and shutdown (version for launchd)
# Based on script and explanations found here:
# http://www.syntaxtechnology.com/2009/06/email-on-shutdown-and-restart/
# Modification history
# PHL 20120604 v01 First version
# Environment variables #################################################
DEST_EMAIL="[email protected]"
SRV_NAME=Amarante
EVENT_TIME=$(date +%Y/%m/%d-%H:%M:%S)
RESTART_SUBJECT="[$SRV_NAME] $EVENT_TIME : System Startup"
RESTART_BODY="This is an automated message to notify you that $SRV_NAME started successfully at $EVENT_TIME."
SHUTDOWN_SUBJECT="[$SRV_NAME] $EVENT_TIME : System Shutdown"
SHUTDOWN_BODY="This is an automated message to notify you that $SRV_NAME is shutting down now ($EVENT_TIME)."
# Functions ##########
stop()
echo "$SHUTDOWN_BODY" | mail -s "$SHUTDOWN_SUBJECT" $DEST_EMAIL
return 0
start()
echo "$RESTART_BODY" | mail -s "$RESTART_SUBJECT" $DEST_EMAIL
return 0
# Main part #########
case $1 in
stop)
stop
start)
start
esac
# trap kill signals to send an email
trap stop HUP INT QUIT ABRT KILL ALRM TERM TSTP
# sleep until killed
while :
do
sleep 15
done
Thanks for your help, and any comment :-)
Paul-Henri

Thanks a lot for your answer, Camelot, even if it sorts of confirm what I suspected. Pinging a machine from an external observer is a solution, but it will also report broken links problems and not only a computer shutting down, and it raises the next tier of problems, general network reliability after individual system reliability. It's something I'll have to look at for sure.
It's weird there isn't any way to access the way the shutdown process works.
One of the commenters (#14) on the page from Syntaxtechnology had a similar problem: he added a "sendmail -q" in his script to force sendmail to go to work and service the queue before shutting down, which I can try, but he also added a delay to the stop process of sendmail, which is something I'm not sure I can do on Mac OS X (and that might disappear one day with one of the OS updates).
Unless there is a way to change the launchd.plist file for postfix and add an ExitTimeOut option in it (I found this idea here : https://discussions.apple.com/message/17229690#17229690 )
Cheers,
Paul-Henri

Shell Script for Startup and Shutdown the database

Hi,
i want Shell Script for Startup and Shutdown the database in Solaries.
could any one can hep me where i can get this script. or send to me to [email protected]
Thanks & Regards,
Gangi reddy

SHUTDOWN
SHUTDOWN ABORT]
Shuts down a currently running Oracle instance, optionally closing and dismounting a database.
Terms
Refer to the following list for a description of each term or clause:
ABORT
Proceeds with the fastest possible shutdown of the database without waiting for calls to complete or users to disconnect.
Uncommitted transactions are not rolled back. Client SQL statements currently being processed are terminated. All users currently connected to the database are implicitly disconnected and the next database startup will require instance recovery.
You must use this option if a background process terminates abnormally.
IMMEDIATE
Does not wait for current calls to complete or users to disconnect from the database.
Further connects are prohibited. The database is closed and dismounted. The instance is shutdown and no instance recovery is required on the next database startup.
NORMAL
NORMAL is the default option which waits for users to disconnect from the database.
Further connects are prohibited. The database is closed and dismounted. The instance is shutdown and no instance recovery is required on the next database startup.
TRANSACTIONAL [LOCAL]
Performs a planned shutdown of an instance while allowing active transactions to complete first. It prevents clients from losing work without requiring all users to log off.
No client can start a new transaction on this instance. Attempting to start a new transaction results in disconnection. After completion of all transactions, any client still connected to the instance is disconnected. Now the instance shuts down just as it would if a SHUTDOWN IMMEDIATE statement was submitted. The next startup of the database will not require any instance recovery procedures.
The LOCAL mode specifies a transactional shutdown on the local instance only, so that it only waits on local transactions to complete, not all transactions. This is useful, for example, for scheduled outage maintenance.
Usage
SHUTDOWN with no arguments is equivalent to SHUTDOWN NORMAL.
You must be connected to a database as SYSOPER, or SYSDBA. You cannot connect via a multi-threaded server. For more information about connecting to a database, see the CONNECT command earlier in this chapter.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a90842/ch13.htm#1013607
Joel Pérez

How to automate the Oracle database start and shutdown process

How we can automate and oracle database start and stop procees with Linux start/shutdown process.
I want to automatically start the oracle database at the time linux server and shutdown the database on shutdown linux server.

Hi,
I can share my scripts:
1) /home/oracle/start_oracle.sh
#Script should be ran as Oracle user
cd /tmp
export ORACLE_SID=orcl
export ORACLE_HOME=/oracle/ora9i
lsnrctl start
sqlplus -S /nolog <<ENDSQL
connect / as sysdba
startup
exit
ENDSQL
emctl start dbconsole
isqlplusctl start
NOTE: emctl and isqlplus are optional
2) /home/oracle/stop_oracle.sh
#Script should be ran as Oracle user
cd /tmp
export ORACLE_SID=orcl
export ORACLE_HOME=/oracle/ora9i
isqlplusctl stop
emctl stop dbconsole
sqlplus -S /nolog <<ENDSQL
connect / as sysdba
shutdown immediate
exit
ENDSQL
lsnrctl stop
NOTE: emctl and isqlplus are optional
Then what you need:
1) K91oracle_stop (put it in the desired run level)
#!/bin/bash
# description: Stop Oracle before reboots
su - oracle -c "/home/oracle/stop_oracle.sh" >> /home/oracle/stoporacle.log
2) S91oracle_start (put it in the desired run level)
#!/bin/bash
# description: Start Oracle after reboots
su - oracle -c "/home/oracle/start_oracle.sh" >> /home/oracle/startoracle.log
Bye.

Shutdown immediate problem

I'm trying to shutdown an Oracle9i database on Unix using SHUTDOWN IMMEDIATE but it just hangs.
I checked the sessions in V$SESSION and noticed there were a few INACTIVE sessions. So I built a script that goes thru all the INACTIVE sessions and kills them.
With all these sessions having status KILLED...when I try to run a SHUTDOWN IMMEDIATE, the database still hangs. I don't want to use SHUTDOWN ABORT.
Does anyone have any information on what makes SHUTDOWN IMMEDIATE hang? Could there be some unix processes....or oracle processes?
Thanks

Dear All,
I am also having some shutdown problem with the Oracle 10g on my Windows Server 2003 machine. My machine could not shutdown (means OS cannot completely shutdown the machine) even after i issued the "shutdown immediate" command.
As what Jaafar said, we should kill the process from OS level. Can any of you explain more on this as I have no idea on how to do this? Which process should I kill after I issued the "Shutdown immediate" command?
Thank you.
best regards,
Wnson

Shutdown immediate hanging

I need to develop a scripts that shuts down all databases on a server. One of my databases sometimes hangs after issuing "shutdown immediate" command, and I want to handle this situation in my script. What I am thinking is to add "shutdown abort" in the script if "shutdown immediate" does not work. However, I do not know how to determine the database is hanging during shutdown immediate. Can you advise me on how to handle the shutdown immediate hanging problem in my shell script? Or is there better way to handle this in the script?
Thank you very much for your help!

As noted, if your shutdown immediate really hang because of rollback, then my method won't work either. The only different will be Oracle is going to do the rollback at next startup when doing instance recovery. In that case, the startup will appear to be hang.
Check this metalink doc,
What To Do and Not To Do When 'shutdown immediate' Hangs
Doc ID: Note:375935.1
There are cases where shutdown immediate hang because of bug.
Shutdown Immediate Hangs
Doc ID: Note:268884.1

Is it safe to control c out of a shutdown immediate?

development database
10.1.0.3
solaris
I did a shutdown immediate and it is taking time to shut down. something is probably running. I should have checked first and could n ot. I tried sqlplus / as sysdba to create another session and 10.1.0.3 is too old to do that while shutting down.,
is it safe to control c out of this shutdown
shutdown abort
startup
shutdowm immediate
startup
or might I corrupt the database?
I need to bounce this irregardless of what is running.

Hi Anantha,
slight correction: uncommitted transactions are not rolled back during the shutdown abort. But they are rolled back during the next startup of the instance during the crash recovery phase. So at the end, the database looks exactly the same as after a shutdown immediate-startup sequence. That is, if you have all the online logfiles in place needed for the crash recovery.
Kind regards
Uwe

Collecting database time up and shutdown

created a trigger as I want to collect db startup and shutdown time but it doesnt seem to work. there is what i did.
first created the table needed
create table log_tab(action char(1), tm varchar2(10)) ;
then
create or replace trigger log_db_avai
after startup on database
begin
insert into log_tab
values('DB START',to_char(sysdate,'DD-MM-RRRR H24:MI:SSSSS');
end;
and
create or replace trigger log_db_avai
before shutdown on database
begin
insert into log_tab
values('DB START',to_char(sysdate,'DD-MM-RRRR H24:MI:SSSSS');
end;
and when executed ai have
Warning: Trigger created with compilation errors.
SQL> show err
Errors for TRIGGER LOG_DB_AVAI:
LINE/COL ERROR
2/1 PL/SQL: SQL Statement ignored
2/74 PL/SQL: ORA-00917: missing comma
Any help? does any one have a better way of collecting this info? thanks in advance.
Mirdassou

And if you still want to use triggers and table, you can use a correct syntax like:
[oracle@xxx ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.2.0 - Production on Mar. Mai 16 11:28:19 2006
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connecté à :
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> create table start_log
2 (
3 oper char(8),
4 stamp timestamp
5 )
6 tablespace users;
Table créée.
SQL> create or replace trigger db_startup
2    after startup on database
3 begin
4    insert into start_log values ('DB START',systimestamp);
5    commit;
6 end;
7 /
Déclencheur créé.
SQL> create or replace trigger db_shutdown
2    before shutdown on database
3 begin
4    insert into start_log values ('DB STOP ',systimestamp);
5    commit;
6* end;
Déclencheur créé.
SQL> shutdown immediate;
Base de données fermée.
Base de données démontée.
Instance ORACLE arrêtée.
SQL> startup
Instance ORACLE lancée.
Total System Global Area 197132288 bytes
Fixed Size                  1259912 bytes
Variable Size              96470648 bytes
Database Buffers           96468992 bytes
Redo Buffers                2932736 bytes
Base de données montée.
Base de données ouverte.
SQL> select * from start_log order by 2 asc;
OPER                     STAMP
DB STOP                  16/05/06 11:33:52,472859
DB START                 16/05/06 11:34:35,105274Regards,
Yoann.
PS: Of course auditing does the trick :-)

Startup and shutdown

I am in need of some assistnace.
I am gettign an ORA-00205 error when I start to startup my database.
I think it has something to do with my control file
My database will not even mount. I llooked at my alert log and is iabout 75 percent full. Can somebody walk me through how to resolve this problem. Here is what I tried
I did a shutdown immediate in SQLPLUS
I did a ps -ef | grep oracle to kame sure the database is shutdown
I killed all process assocaited with thr process
I did a start up command and it still failed
My alert log has somethinn about Thread sequence not able to advance.
Please advise

user1381515 wrote:
Here is a sample of my alert file.
Thread 1 advances to log sequence 1185
Current log #1 seq 1189 mem# .opt/app/oracle/data3/ordata/arcdev (name of database) /redo 01.1
This goed in sequnece to 1186 to 1226 then I get
Thrread 1 cannot allocate new log seg 1127
Current log #1 seq 1227 mem# .opt/app/oracle/data3/ordata/arcdev (name of database) /redo 01.1
and hen I get thsi error and then from time it switche back and forth to the original error and error shown above.
It a linux OPS
Totally conused.
What commands do I user to connect.What is the actual problem right now.
I believe your database is not up. So there is no question of log file switching.
Did you resolve your problem of database startup. If yes then we would try to look why it is not able to allocate new log sequence.
Regards
Anurag

How to write triggers on startup and shutdown of the server?

Plz advice.
How to write triggers on startup and shutdown of the server?
I could write it but nothing happened!!!

Small code example for you:
[email protected]> @ connect mob/mob
[email protected]> create or replace trigger shutdown_trigger
2 before shutdown on database
3 begin
4 insert into shut_table values(sysdate);
5 end;
6 /
Trigger created.
[email protected]> create or replace trigger start_trigger
2 after startup on database
3 begin
4 insert into start_table values(sysdate);
5 end;
6 /
Trigger created.
[email protected]> @ connect "/ as sysdba"
[email protected]> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
[email protected]> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 64036368 bytes
Fixed Size 454160 bytes
Variable Size 50331648 bytes
Database Buffers 12582912 bytes
Redo Buffers 667648 bytes
Database mounted.
Database opened.
[email protected]> select * from mob.start_table;
START_DAT
14-SEP-06
[email protected]> select * from mob.shut_table;
SHUT_DATE
14-SEP-06
Best Regards
Krystian Zieja / mob

Shutdown immediate won't work, Must abort to switch to SunCluster standby

Customer has a Solaris Clusterware, The customer sees the semtimedop() system call returning EAGAIN when running "shutdown immediate" on their database on one cluster node. This is expected when the shared resource that the semaphore is protecting is unavailable. The shared resource is only being used by Oracle processes, so we need to know what the resource is and what the other processes are doing with it. MOS doc 760968.1 isn't helpful. A Solaris crash dump taken when the database shutdown problem was occurring showed no signs of an OS issue so database assistance is needed.
We have tried to capture the following trace, but the trace is empty , and we 're stuck since then.
SQL> alter session set events '10046 trace name context forever,level 12';
SQL> alter session set events '10400 trace name context forever, level 1';
SQL> shutdown immediate;

don't you think it is about time you upgraded to something that hasn't been out of support since 2007 (almost 6 years ago...???). Hopefully you don't have any CC information stored in that db as there has not been any security updates since before it went to de-support.
What I would like to know is how did you even get 9i to install on Solaris 10? IIRC, that is not even a supported OS/Oracle version configuration. As for your current problem,
http://www.lmgtfy.com/?q=oracle+9i+suncluster+failover
http://docs.oracle.com/cd/E19787-01/820-2574/gctbk/index.html

Database shutdown immediate - time calculation ?

Hi,
Good Day.
did any one tried to calculate time the database would took to complete "shutdown immediate" command?
hope to have a healthy discussion..
Regards,
Muhammad Ahmad

Mohamed ELAzab wrote:
Hello Jonathan Lewis,
1-Please note that looking into the alert_sid.log is a good start as it will show if the smon process was dead according to the note:
Shutdown Normal or Shutdown Immediate Hangs. SMON disabling TX Recovery [ID 1076161.6]
I can see that that note is labelled: "Checked for relevance June 2009", but have you seen the garbage it suggests for temporary segments:
<ul>
Verify that temporary segments are decreasing
To verify that the temporary segments are decreasing have an active session
available in Server Manager or SQLPLUS during the SHUTDOWN IMMEDIATE. Issue the following
query to ensure the database is not hanging, but is actually perform extent
cleanup:
SVRMGR/SQL> select count(block#) from fet$;
COUNT(BLOC
+7+
SVRMGR/SQL> select count(block#) from uet$;
COUNT(BLOC
+402+
</ul>
For this to be true the temporary tablespace would have to be declared as dictionary managed, possibly even with contents = "PERMANENT" but it's so long since I've created a dictionary-managed TEMP that I can't be sure of the second point. I would be very cautious about trusting any document that started with such antiquated material - you can have no idea how much of its content might be (at best) deficient and (at worst) dangerously wrong.
3-to know the transactions that will be rolled back please read the note:
How to Check Why Shutdown Immediate Hangs? [ID 164504.1]
Same type of problem - "Checked for relevance: Mar 2010", starts with:
<ul>
Start Server Manager (or SQL*Plus for 8i or higher)
SVRMGRL> connect internal (or SYSDBA for 8i or higher)
SVRMGRL> select * from x$ktuxe where ktuxecfl = 'DEAD';
</ul>
Although x$ktuxe will show you transaction states from the undo segment headers, and this might show you recursive (or other special case) transactions that do not appear in v$transaction, I wouldn't trust a note that is based on 7.3 technology to be an appropriate reference document.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Job and shutdown immediate

Similar Messages

Maybe you are looking for