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

Similar Messages

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

If shutdown immediate hangs database waits one hour for shutdown abort

we have schedules cold backup for our 11g database on redhat 5.3.
there is a shell script written with shutdown immediate command.
If database hangs during shutdown immediate database waits one hour for auto shutdown abort.
but this happens once or twice in a month
can we do this auto shutdown abort earlier than one hour ??

user13376823 wrote:
we have schedules cold backup for our 11g database on redhat 5.3.
Since you're shutting down the database for cold backup so ensure it should be shutdown properly by shutdown or shutdown immediate cmd not by abort cmd.
Consistent backup:-
A backup taken when the database is mounted (but not open) after a normal shutdown. The checkpoint SCNs in the datafile headers match the header information in the control file. None of the datafiles has changes beyond its checkpoint. Consistent backups can be restored without recovery.
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1007616

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

Shutdown immediate hangs ORA-12012, ORA-12008, ORA-06512

We have a problem while immediate shutting down the database:
alert.log:
Errors in file /data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc:
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Mon Jun 11 16:20:29 2007
Job queue slave processes stopped
Mon Jun 11 16:26:36 2007
Active call for process 7695 user 'oracle' program 'oracle@lxegbp2qs (J000)'
SHUTDOWN: waiting for active calls to complete.
Trace:
/data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /data_archiv/oracle/product/10g
System name:     Linux
Node name:     lxegbp2qs
Release:     2.6.5-7.244-smp
Version:     #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine:     i686
Instance name: EGB
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 7708, image: oracle@lxegbp2qs (J001)
*** SERVICE NAME:(SYS$USERS) 2007-06-11 16:20:28.759
*** SESSION ID:(273.1) 2007-06-11 16:20:28.759
*** 2007-06-11 16:20:28.759
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
The job with id 3 should not run during shut down (needs only seconds):
select substr(what, 1, 70), TO_CHAR(last_date, 'DD.MM.YYYY HH24:MI:SS') as last_date, TO_CHAR(next_date, 'DD.MM.YYYY SQL> HH24:MI:SS') as next_date from dba_jobs where job=3;
SUBSTR(WHAT,1,70)
LAST_DATE NEXT_DATE
dbms_refresh.refresh('"TEST"."MV_TEST"');
11.06.2007 06:00:06 12.06.2007 06:00:00
Any ideas where to look for?

Active call for process 7695 user 'oracle' programKill active call process mentioned in alert.log.

Shutdown immediate hangs for 30 mins

Hi,
my database is running on RAC .. it has two instances.. one instance closed immediately... another instance take 30 mins to down.
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
SHUTDOWN: waiting for detached processes to terminate.
Thanks,

First Thing First........
I generally never take any such step until it become essential. I always use the above command to kill LOCAL sessions and DB comes down in sometime.Oracle is ORACLE. There are some magical things happen. Something work somewhere and somewhere not.
1. The only thing you can check is ALTER_ORACLE_SID.log.. There you come to know what is happening. Along with this you can see whether the number of orcle processes are coming down. If Not then something needs to be done.
2. Don't use such thing which is not adviseable. This is wried. You can never know when a problem will be in front of you.
KILL THE LOCAL SESSION AND ORACLE WILL DOWN IN 99.9% CASES.
Let me know if someone disagree with me.
Lochan

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

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

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/

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

I have two wireless networks that I switch back and forth. Everytime I switch the network zone my macbook pro hangs and I have to do a hard shutdown and restart. What is the fix?

I have two wireless networks that I switch back and forth. Everytime I switch the network zone my macbook pro hangs and I have to do a hard shutdown and restart. What is the fix?

Create two locations in Network, one for one and one for the other.
WiFi, Internet problems, possible solutions
WiFi security issues, at home and WiFi hotspots

Shutdown immediate - will be a problem?

I need to shutdown Oracle database. I wonder if I can do it cleanly? The problem depends on that there is a session 497 which can't be killed neither on database level nor os level. (On database level it simultanously expires and starts with new serial, on os level there is no process related to this session, or it can be zombie process we have, which can't be killed too) Session 497 is probably related to badly canceled operation of bringing a datafile online. Sometime ago we had to bring a datafile online so media recovery of this datafile was required. As we had no archivelog (21 days window) the media recovery couldn't be acomplished. This operation hung. Session 497 may still want to recover that datafile. How do you think? May any problems occur during a shutdown process? May shutdown immediate process wait (and hang too) untill the 497 session end?
Edited by: Przemek Piechota on 2011-02-10 07:40

content of alert_log:
Wed Feb 9 00:29:58 2011
ORA-1157 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 00:33:20 2011
ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE
Wed Feb 9 00:33:20 2011
Errors in file /u01/app/oracle/admin/easy/bdump/easy1_dbw0_1028264.trc:
ORA-01157: Message 1157 not found; No message file for product=RDBMS, facility=ORA; arguments: [74]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [74] [u01/app/oracle/oradata/easy/integracja03]
ORA-27037: Message 27037 not found; No message file for product=RDBMS, facility=ORA
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Wed Feb 9 00:33:20 2011
ORA-1157 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 00:47:46 2011
Thread 1 advanced to log sequence 51550 (LGWR switch)
Current log# 1 seq# 51550 mem# 0: /u01/app/oracle/oradata/easy/log1a
Current log# 1 seq# 51550 mem# 1: /u01/app/oracle/oradata/easy/log1b
Wed Feb 9 01:01:41 2011
ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE
Wed Feb 9 01:01:41 2011
ORA-1113 signalled during: ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/easy/integracja03' ONLINE...
Wed Feb 9 01:03:58 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:03:58 2011
Media Recovery Start
parallel recovery started with 3 processes
ORA-279 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...
Wed Feb 9 01:05:28 2011
ALTER DATABASE RECOVER CANCEL
Wed Feb 9 01:05:29 2011
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Wed Feb 9 01:05:29 2011
ALTER DATABASE RECOVER CANCEL
Wed Feb 9 01:05:29 2011
Errors in file /u01/app/oracle/admin/easy/udump/easy1_ora_1843296.trc:
*ORA-07445: exception encountered: core dump [kcrpnq+006c] [SIGSEGV] [Invalid permissions for mapped object] [0x000000000] [] []*
Wed Feb 9 01:05:30 2011
*Trace dumping is performing id=[cdmp_20110209010530]*
Wed Feb 9 01:10:20 2011
PMON failed to delete process, see PMON trace file
Wed Feb 9 01:16:31 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:16:31 2011
Media Recovery Start
Wed Feb 9 01:16:31 2011
Media Recovery failed with error 1124
ORA-283 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...
Wed Feb 9 01:17:29 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:17:29 2011
Media Recovery Start
Wed Feb 9 01:17:29 2011
Media Recovery failed with error 1124
Wed Feb 9 01:42:04 2011
Completed: alter database datafile '/u01/app/oracle/oradata/easy/integracja03' offline drop
Wed Feb 9 01:43:53 2011
ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03'
Wed Feb 9 01:43:53 2011
Media Recovery Start
Wed Feb 9 01:43:53 2011
Media Recovery failed with error 1124
ORA-283 signalled during: ALTER DATABASE RECOVER datafile '/u01/app/oracle/oradata/easy/integracja03' ...

Shutdown immediate taking time

HI
I m using oracle 10g release 2. on hpux itanium
some of my database is taking longer time to shutdown more than 30 minutes. so usually i m doing
startup force and than shutdown immediate... wat is the problem behind this and how can i resolve it plz suggest.

A SHUTDOWN NORMAL will wait for sessions to disconnect. So, if you have application processes or users that do not disconnect, it will "hang". It is likely that this is causing your shutdown to delay. You could check the alert log file for messages about Oracle waiting for users to disconnect.
A SHUTDOWN IMMEDIATE will kill active sessions, complete a rollback of transactions that are killed and then shutdown the database. If you are using a SHUTDOWN IMMEDIATE, this can take a long time if there are large active transactions (or many active transactions) that Oracle needs to rollback -- the rollback can take time. (Also, if there are very many connected sessions, Oracle will take time to disconnect all of them).
A SHUTDOWN ABORT does a quick kill by shutting down the instance, without validating connected sessions. Rollback is automatically initiated by Oracle with the Instance Recovery at the STARTUP. The STARTUP can take slightly longer (in terms of seconds or a few minutes, generally) depending on the volume of Redo to be re-applied. Rollback is deferred to be executed after the OPEN.
You could try a SHUTDOWN TRANSACTIONAL. However, this can still take a long time or "hang" if a user or application process (or multiple of them) has/have active transaction(s) and does/do not issue COMMITs.
See the documentation on the SHUTDOWN command :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14357/ch12042.htm#i2699551
Hemant K Chitale
http://hemantoracledba.blogspot.com

Export and import Oracle 10G database

Hello all
Can anyone tell me once for all how can i backup oracle 10G database and restore it in other computer (export and import)
thanks alot
Ron

Do you can access to metalink?
If not, I copy an paste this doc's....
Doc ID: Note:10767.1
Subject: How to perform FULL System Export/Imports
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 18-APR-1994
Last Revision Date: 30-AUG-2002
Purpose
This article highlights some important points to consider when performing
a Full System Export and Import.
Scope and Application
It is intended to assist users performing FULL System Exports and Imports.
A Full System Export and Import is a useful way to replicate or clean up
a database. Please note the following guidelines when performing a Full
System Export and Import:
1. When performing the import, ensure you are pointing at the correct
instance. Always check values for the SID and two task driver before
proceeding.
*Note: On Unix systems, just entering a sub-shell, such as using
C-shell, can change the database that the import would work
against.
2. When possible, it is advisable to take a physical copy of the
exported database and the database you intend to import into before
starting the import. This ensures any mistakes are reversible.
3. NEVER run a FULL SYSTEM IMPORT on a machine that has more than one
database UNLESS you are 100% sure all tablespaces have been
pre-created. A full import will create any undefined tablespaces
using the same datafile names as the exported database. There are
situations where this is very dangerous:
-> If the datafiles belong to ANY other database, they will be
CORRUPTED. This is especially true if the exported database is
on the same machine, because its datafiles will be re-used by
the database you are importing into.
-> If the datafiles have names that clash with existing operating
system files.
4. When exporting, it is advisable to also produce a report showing
information you may need before / after the import:
-> List the tablespaces and datafiles
-> List the rollback segments
-> List a count, by user, of each object type such as tables,
indexes, etc.
This enables you to ensure that tablespaces have been pre-created
and to check the success of the import after it is complete.
5. If you are creating a completely new database from an export, remember
to create an extra rollback segment in SYSTEM, and make this available
in the init.ora file before proceeding with the import.
6. There are some versions of export that do not retain sequence numbers
correctly. It is advisable to select next_value for each sequence
after the export so that these can be checked after import.
Following these guidelines will help you to avoid major problems.
Doc ID: Note:174226.1
Subject: How To Copy an Oracle Database To Another Machine
Type: HOWTO
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 12-OCT-2001
Last Revision Date: 01-OCT-2003
goal: How to copy an Oracle database to another machine
fact: Oracle Server - Enterprise Edition
fix:
Pre-requisites: The copy is between 2 machines, both have to be on the same OS
and have to have exactly the same database version installed.
1. Make sure the database you want to copy was closed with a SHUTDOWN IMMEDIATE,
SHUTDOWN NORMAL or SHUTDOWN TRANSACTIONAL.
2. Copy init.ora and control files to create instance and be able to go in
mount mode. Check the init.ora for the locations where the controlfiles have
to be, if those locations are not valid on the machine put the control files on
different places and adjust the init.ora accordingly.
3.a. Copy the datafiles (all of them).
b. Copy the redo-logfiles (all of them).
4.a. (Unix only) Set the environment variables:
ORACLE_SID - set to the database name you wish to create
ORACLE_HOME - set to full pathname of the Oracle system home directory
PATH - needs to include $ORACLE_HOME/bin
b. (NT/2000 only) Do 'set ORACLE_SID=<SID>'
Use oradim to create the service for the instance. For more information
on oradim please refer to (the part that refers to creating a new instance):
Note:68720.1 Creating a new 7.3, 8.0, 8.1 Instance/Database
5. Use servermanager (check the name to use for your version of oracle) or
sqlplus (version 9i and above) to startup the database in mount mode.
Do
CONNECT INTERNAL/<PASSWORD>
then
STARTUP MOUNT
Then do a rename of the copied datafiles if they are not in the same path as on
the other machine. For all the files that are in the result of the query:
SELECT NAME FROM V$DATAFILE;
do
ALTER DATABASE RENAME FILE '<oldfullpath>\<filename>' to <
newfullpath>\<filename>';
6. Query the datadictionary for the old location of the redolog files using:
SELECT MEMBER FROM V$LOGFILE;
If the new place is not the same as the old do:
ALTER DATABASE RENAME FILE '<oldfullpath>\<redologfilename>' to &
lt;newfullpath>\<redologfilename>';
7. Now open the database:
ALTER DATBASE OPEN;
******************************************************************

RAC Node hang and unexpected reboot

Hello friends
We are facing the intermittent issue of node hang and unexpected shutdown of node. This is 2 node rac 10.2.03 running on windows 2003. Here's crsd.log
2009-07-16 17:24:03.058: [ OCRMSG][5252]prom_rpc: CLSC recv failure..ret code 7
2009-07-16 17:24:03.058: [ OCRMSG][5252]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.058: [ COMMCRS][5616]clscsendx: (0000000002AF5C60) Physical connection (0000000003892080) not active
2009-07-16 17:24:03.058: [ OCRMSG][5616]prom_rpc: CLSC send failure..ret code 11
2009-07-16 17:24:03.058: [ OCRMSG][5616]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.105: [ COMMCRS][5252]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.105: [ OCRMSG][5252]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.105: [ OCRMSG][5252]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.105: [ COMMCRS][5616]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.105: [ OCRMSG][5616]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.105: [ OCRMSG][5616]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.152: [ COMMCRS][5252]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.152: [ OCRMSG][5252]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.152: [ OCRMSG][5252]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.168: [ COMMCRS][5616]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.168: [ OCRMSG][5616]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.168: [ OCRMSG][5616]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.215: [ COMMCRS][5252]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.215: [ OCRMSG][5252]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.215: [ OCRMSG][5252]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.215: [ COMMCRS][5616]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.215: [ OCRMSG][5616]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.215: [ OCRMSG][5616]prom_rpc: possible OCR retry scenario
2009-07-16 17:24:03.261: [ COMMCRS][5616]clscsendx: (0000000002AF5C60) Connection not active
2009-07-16 17:24:03.261: [ OCRMSG][5616]prom_rpc: CLSC send failure..ret code 6
2009-07-16 17:24:03.261: [ OCRMSG][5616]prom_rpc: possible OCR retry scenario
Please throw me the light, what may be issue.

I suggest you install [ IPD/OS|http://www.oracle.com/technology/products/database/clustering/ipd_download_homepage.html] on you cluster. This will give you all the relevant OS statistics so when a node reboot happens, you can figure out what the state of the nodes was at that time and then fix the problem. The hang is often caused by something other than Oracle RAC.

Shutdown immediate hangs and HVM of a database

Similar Messages

Maybe you are looking for