Shutdown normal

Hi,
While stopping an Oracle database I have used "SHUTDOWN" command, to stop the Oracle database normally. But there are already some existing connections to the database. After shutdown normal Oracle waits for these connections to be disconnected themself.
Suppose these connections do not gets disconnected themself. Then Oracle won't allow you to connect to database again to kill those database sessions, and we are stuck. Though this can be managed by rebooting the database machine. But inspite of rebooting the machine, is there any other way as well to handle this scenario?
Thanks in advance.

The suggestion had been "+You can grep database connections from OS and kill them individually+". This works on Unix/Linux where separate server processes service each user. On Windows it is a single multi-threaded process.
The suggestion had been to kill individual processes -- which you can't do on Windows.
What you did was to kill the Oracle database instance process.
+If you have compared Oracle on Unix/Linux with Windows you'd know that the reference is to Unix/Linux not Windows. (and that is not because "Oracle is different on Windows" but because the architecture on Windows has to be multi-threaded rather than multi-processing if different database sessions are to access a shared SGA.+ But I digress).
So, on Unix/Linux, it is easier to identify and kill individual processes.
(+If you know how to map database sessions to oracle PIDs to individual threads in the single Oracle.exe process and then how to use orakill, you'd be able to do something similar on Windows.+ But, again, I digress).
If you want a method to handle some (the DBA ??) inadvertently issuing SHUTDOWN instead of SHUTDOWN IMMEDIATE, think of
a. Configuring your Service Shutdown to use SHUTDOWN IMMEDIATE and making it mandatory for all DBAs/SysAdmins to use Service Shutdown instead of SQLPlus SHUTDOWN
b. Making it mandatory for all DBAs to use SQLPlus SHUTDOWN IMMEDIATE or suffer a reprimand for using SHUTDOWN
c. Write an ON SHUTDOWN database trigger that
i loops through all database sessions
ii excludes the background sessions and the session that issues the shutdown
iii issues an ALTER SYSTEM KILL SESSION for the remaining sesssions
Hemant K Chitale
http://hemantoracledba.blogspot.com

Similar Messages

I can't stop shutdown normal

hi expert,
i'm running the command shutdown, but it don't finish.
sqlplus SYS/password#@TMPDB1 as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Aug 10 14:08:51 2010
Copyright (c) 1982, 2005, 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 normal;
^Ci'm waiting until 10 minute, but without any success.
In alert log i'm finding this problem:
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 14568 (4)
Tue Aug 10 14:23:40 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 14568 (4)
Tue Aug 10 14:23:40 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 14568 (4)How i can stop the database? or stop the shutdown?
If I open another shel I have this error.
$ export ORACLE_SID=TMPDB1
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Aug 10 14:27:03 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> select name from v$database;
select name from v$database
ERROR at line 1:
ORA-01034: ORACLE not availablemany thanks as usual,
Lain
Edited by: Lain on 10-ago-2010 14.28

Chinar, ar u sure?
in this moment I've 36 active pid on my unix system (sun os)
thanks too you,
Cheers
$ ps -ef | grep TMPDB1
oracle 3091     1   0   Aug 05 ?           0:01 ora_d000_TMPDB1
oracle 3080     1   0   Aug 05 ?           0:41 ora_smon_TMPDB1
oracle 3085     1   0   Aug 05 ?           5:06 ora_cjq0_TMPDB1
oracle 3053     1   0   Aug 05 ?          14:34 ora_pmon_TMPDB1
oracle 26085     1   0   Aug 06 ?           0:12 ora_j008_TMPDB1
oracle 3074     1   0   Aug 05 ?           0:41 ora_dbw7_TMPDB1
oracle 3082     1   0   Aug 05 ?           0:00 ora_reco_TMPDB1
oracle 3065     1   0   Aug 05 ?           0:37 ora_dbw3_TMPDB1
oracle 3067     1   0   Aug 05 ?           0:56 ora_dbw4_TMPDB1
oracle 3061     1   0   Aug 05 ?           1:12 ora_dbw1_TMPDB1
oracle 3072     1   0   Aug 05 ?           0:37 ora_dbw6_TMPDB1
oracle 3132     1   0   Aug 05 ?           0:44 /opt/oracle/product/10.2.0/ORA/bin/tnslsnr LISTENER_TMPDB1 -inherit
oracle 3055     1   0   Aug 05 ?           0:19 ora_psp0_TMPDB1
oracle 23780     1   0   Aug 06 ?           0:11 ora_j004_TMPDB1
oracle 16381 14888   0 14:40:59 pts/3       0:00 grep -i dwh
oracle 3057     1   0   Aug 05 ?           0:22 ora_mman_TMPDB1
oracle 3063     1   0   Aug 05 ?           1:41 ora_dbw2_TMPDB1
oracle 3078     1   0   Aug 05 ?           5:59 ora_ckpt_TMPDB1
oracle 3113     1   0   Aug 05 ?         893:35 ora_arc1_TMPDB1
oracle 20780     1   0   Aug 06 ?           4:56 oracleTMPDB1 (LOCAL=NO)
oracle 3076     1   0   Aug 05 ?          24:23 ora_lgwr_TMPDB1
oracle 23450     1   0   Aug 06 ?           0:28 ora_j003_TMPDB1
oracle 3059     1   0   Aug 05 ?           0:52 ora_dbw0_TMPDB1
oracle 3111     1   0   Aug 05 ?        1203:53 ora_arc0_TMPDB1
oracle 3093     1   0   Aug 05 ?           0:01 ora_s000_TMPDB1
oracle 3069     1   0   Aug 05 ?           0:40 ora_dbw5_TMPDB1
oracle 24945     1   0   Aug 06 ?           0:11 ora_j007_TMPDB1
oracle 26087     1   0   Aug 06 ?           0:11 ora_j009_TMPDB1
oracle 14899     1   0 14:09:21 ?           0:01 ora_emn0_TMPDB1
oracle 23782     1   0   Aug 06 ?           0:11 ora_j005_TMPDB1
oracle 22527     1   0   Aug 06 ?           0:11 ora_j002_TMPDB1
oracle 24943     1   0   Aug 06 ?           0:11 ora_j006_TMPDB1
oracle 14859 14772   0 14:08:52 pts/2       0:00 sqlplus SYS/password@TMPDB1 as sysdba
oracle 21724     1   0   Aug 06 ?           0:30 ora_j001_TMPDB1
oracle 21136     1   0   Aug 06 ?           0:30 ora_j000_TMPDB1
oracle 14861     1   0 14:08:52 ?           0:01 oracleTMPDB1 (LOCAL=NO)Edited by: Lain on 10-ago-2010 14.43

Oracle instance shutdown normal vs immediate (users connected) how-to?

Hello Oracle crowd, recently, i tried to shutdown my instance Oracle 9.2.0.1.0 using sqlplus shutdown. i assume the default is shutdown normal but the instance would not shutdown. after reading the admin docs i realized it must be waiting for connected users to logoff. my question is how do i get a list of the current users connected so i don't have to resort to: shutdown immediate. pls advise, david.

Hi,
the v$session view answers this question, try 'select distinct username from v$session;' . If there are any other users besides your own, you must use 'shutdown immediate'.

SQL Server Status SHUTDOWN | Normal

Hi
I have one sql 2008 database .TDP backup is running for this server.now I am not able to take log backup on this server.It is failing.When I checked the database properties I found that status - Shutdown | Normal.
I am able to access this database and application is working fine and I am able to take SQL Native backup also.
Why this status showing Shutdown | Normal ?,Anybody can help me on this.

Now I found one more thing.
Actually this db is in mirroring .When I checked sys.databases I found that is_cleanly_shutdown column showing value 1
How I can make it to 0 ?Restart of SQL Server will resolve ?
If the Mirroring session is active, backup is not allowed on the database. More details
here.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @PradeepAdiga

Grid & shutdown normal

Funny situation. We have a development database that goes down every night for a cold backup (it is a BCV split, so downtime is minimal). Anyway, one of the DBA's here left GRID on a database Performance screen with 10 sec. refresh interval. Shutdown process is:
a) stop oem_agent
b) shutdown abort
c) startup restrict
d) shutdown normal
e) start oem_agent
Guess what:
sqlplus /nolog
SQL*Plus: Release 10.2.0.2.0 - Production on Fri Dec 8 17:24:33 2006
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
SQL> connect / as sysdba
Connected.
SQL> select sid,serial#,status,username from v$session
2 where program = 'OMS';
SID SERIAL# STATUS USERNAME
232 3 INACTIVE SYS
SQL> alter system kill session '232,3';
System altered.
SQL> select sid,serial#,status from v$session
2 where program = 'OMS';
no rows selected
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup restrict
ORACLE instance started.
Total System Global Area 1761607680 bytes
Fixed Size 2057480 bytes
Variable Size 788531960 bytes
Database Buffers 956301312 bytes
Redo Buffers 14716928 bytes
Database mounted.
Database opened.
SQL> select sid,serial#,status,username from v$session
2 where program = 'OMS';
SID SERIAL# STATUS USERNAME
234 7 INACTIVE SYS
SQL> Obviously, SHUTDOWN NORMAL waits forever and backup process hangs.
Now, AFAIK remote connections AS SYSDBA to a database in restricted mode are not allowed:
SQL> connect xxx@xxx as sysdba
Enter password: *********
ERROR:
ORA-12526: TNS:listener: all appropriate instances are in restricted mode So question I have is how OMS server which is, obviously, on a separate box can make a remote connection AS SYSDBA to a database in restricted mode? And how to prevent it so database could be shut down in normal mode?
SY.

2 mnazim : Oracle Enterprise Manager 10g Grid Control Release 10.2.0.2.0
2 bazzza : Grid credentials are set to connect AS SYSDBA. However, as I stated, database is in restrict mode, therefore listener service is in restricted mode:
oracle> lsnrctl status
LSNRCTL for HPUX: Version 10.2.0.2.0 - Production on 11-DEC-2006 11:29:07
Services Summary...
Service "yyy" has 1 instance(s).
Instance "yyy", status RESTRICTED, has 1 handler(s) for this service...
The command completed successfullyand should not allow any connections except local connections AS SYSDBA/SYSOPER, while grid "magically" makes a remote one:
SQL> connect / as sysdba
Connected.
SQL> connect / as sysoper
Connected.
SQL> connect xxx as sysdba
Enter password:
Connected.
SQL> connect /@yyy as sysdba
ERROR:
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
Warning: You are no longer connected to ORACLE.
SQL> connect xxx@yyy as sysdba
Enter password:
ERROR:
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
Warning: You are no longer connected to ORACLE.
SQL> 2 Ugonic: Your statement "It connects direstly using it own settings" is not true. OMS makes a regular SQL*Net connection (with some twist, obviously):
SQL> connect / as sysdba
Connected.
SQL> select sid,serial#,username,osuser from v$session where program = 'OMS';
       SID    SERIAL# USERNAME
OSUSER
       235         17 SYS
SQL> host
oracle> lsnrctl stop
LSNRCTL for HPUX: Version 10.2.0.2.0 - Production on 11-DEC-2006 11:13:47
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=local10i)))
The command completed successfully
oracle> exit
SQL> alter system kill session '235,17';
System altered.
SQL> exec dbms_lock.sleep(30)
PL/SQL procedure successfully completed.
SQL> select sid,serial#,username,osuser from v$session where program = 'OMS';
no rows selected
SQL> host
oracle> lsnrctl start
The command completed successfully
oracle> exit
SQL> select sid,serial#,username,osuser from v$session where program = 'OMS';
no rows selected
SQL> exec dbms_lock.sleep(30)
PL/SQL procedure successfully completed.
SQL> select sid,serial#,username,osuser from v$session where program = 'OMS';
       SID    SERIAL# USERNAME
OSUSER
       235         23 SYS
SQL>As you can see, stoping listener prevents the connection. So my question still stands. I will trace SQL*Net on level 16 on both sides (grid & db) when I'll have some time to see if there is some "magic" parameter in handshake/connect request.
SY.
P.S. All that time agent was down:
oracle> status_oemagent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Agent is Not Running

10.1.0.4 SUN solaris 8 Database does not shutdown normally

After SAN crash the 10.1.04 database does not shutdown immediate (hanging or..)
I shutdown abort and startup is smooth.
I checked the leftover OS processes looks like none left...
Any sugestion?
TIA

in the alert :12:27:06 2007
Waiting for Job queue slaves to complete
Wed Feb 14 12:28:15 2007
Job queue slave processes stopped
Wed Feb 14 12:33:18 2007
Active call for process 9247 user 'oracle' program 'oracle@solars23 (J000)'
SHUTDOWN: waiting for active calls to complete.
Wed Feb 14 12:47:00 2007
KTSMG_UPDATE_MQL(): MMNL absent for 1201 secs; Foregrounds taking over
oracle 9295 9274 0 12:25:03 ? 0:00 oracle102 (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

Shutdown normal|immediate slow on new install of 11R2.0.3.{2|3|4} on Solaris

Just installed a new pair of SPARC T4-4 (each w/2x CPUs, 128GB mem) with Solaris 11.1 sru 3.4.1 to run a Data Guard solution for 3x instances using 3x diff. Oracle 11R2 versions (11.2.0.3.2-4)
But all three instances on both pro & sec server randomly indicates Time Drift warnings in their alert logs and vktm traces, but both solaris boxes are running ntp sync fine.
Also various operations like instance startup/shutdown takes a long time, as well as a simple launch of sqlplus can take minutes. Also spawning a simple CLI like 'ps -ef' can sometimes take up to 20-30 sec. Neither swap nor cpu is loaded.
Could it be a known bug seen before or a faulty init ora parameter and/or combination?
Also posted this under Solaris 11 Forum:
simple processes are very slow at intervals
TIA for any hints!
snip of a VKTM trace:
Trace file /global/oraadmin/diag/rdbms/<redacted>/trace/<redacted>_vktm_27415.trc Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Product ion ORACLE_HOME = /global/orabase/product/11.2.0.3.4/db_1 System name:    SunOS Node name:      <redacted> Release:        5.11 Version:        11.1 Machine:        sun4v Instance name: <redacted> Redo thread mounted by this instance: 0 <none> Oracle process number: 3 Unix process pid: 27415, image: oracle@<redacted> (VKTM) *** 2013-06-03 12:51:02.036 *** SESSION ID:(1609.1) 2013-06-03 12:51:02.036 *** CLIENT ID:() 2013-06-03 12:51:02.036 *** SERVICE NAME:() 2013-06-03 12:51:02.036 *** MODULE NAME:() 2013-06-03 12:51:02.036 *** ACTION NAME:() 2013-06-03 12:51:02.036 kstmmainvktm: succeeded in setting elevated priority highres_enabled *** 2013-06-03 12:51:02.036 VKTM running at (1)millisec precision with DBRM quantum (100)ms [Start] HighResTick = 4585953873256 kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1370256662 *** 2013-06-03 12:55:54.137 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (2984405)usec at (4586245994477) whereas (1000000) is allowed *** 2013-06-03 12:56:13.269 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (19133925)usec at (4586265128403) whereas (1000000) is allowed kstmchkdrift (kstmhighrestimecntkeeper:lowres): Time stalled at 1370256973 kstmchkdrift (kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1370256974 drift: 1 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (7023737)usec at (4586963505968) whereas (1000000) is allowed
Mod. action: please, to keep tab formatting on forum side, use the tag
before and after your code output, thanks. lease, Edited by: N Gasparotto on Jun 3, 2013 4:16 PM

Thanks for your suggestion but as I have read the doc then the patch for Bug 9843304 is included in the 11.2.0.2 patchset and then also for PSUs 11.2.0.3.*
I think that the reason we see VKTM trace/drift is not high load as this is not the case, but more lock contention emulating high load. Question is just what lock and why and how to work around it...
Hoped that other SPARC T4 + 11R2 users might have seen similar issue and know what to tweak of either init ora/solaris setting or if bug is known.
Just to show a snap in time. miles varies off course and issue (as mentioned in Solaris 11 forum) is not seen constantly and not during below sampling...
#root:~# top -n 2
last pid: 6594; load avg: 8.07, 6.17, 7.32; up 6+21:28:53        18:04:14
249 processes: 239 sleeping, 5 zombie, 5 on cpu
CPU states: 95.5% idle, 1.0% user, 3.5% kernel, 0.0% iowait, 0.0% swap
Kernel: 67325 ctxsw, 624 trap, 53970 intr, 55554 syscall, 15 flt
Memory: 128G phys mem, 14G free mem, 64G total swap, 64G free swap
   PID USERNAME NLWP PRI NICE SIZE   RES STATE    TIME    CPU COMMAND
20916 oracle     18 20    0   50G   50G cpu/86 146:50 0.77% oracle
6202 oracle      7 51    0   25G   25G cpu/90   0:25 0.18% oracle
prstat -m -U oracle -n 10
   PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/NLWP
21426 oracle    28 0.0 0.0 0.0 0.0 0.0 72 0.0   2 11 39   0 oracle/1
20916 oracle   5.5 0.0 0.0 0.0 0.0 89 5.6 0.0   3 24 8K   0 oracle/18
6180 oracle   2.2 2.3 0.0 0.0 0.0 62 33 0.2 8K 287 20K   0 oracle/7
6212 oracle   1.9 1.9 0.0 0.0 0.0 67 29 0.2 8K 269 19K   0 oracle/8
6196 oracle   1.9 1.8 0.0 0.0 0.0 67 29 0.2 8K 279 20K   0 oracle/8
6209 oracle   1.8 1.8 0.0 0.0 0.0 67 30 0.2 8K 311 19K   0 oracle/8
6178 oracle   1.5 1.0 0.0 0.0 0.0 65 32 0.2 1K 18 1K   0 oracle/7
6202 oracle   1.4 1.0 0.0 0.0 0.0 67 30 0.1 974 18 1K   0 oracle/8
6156 oracle   1.9 0.4 0.0 0.0 0.0 87 11 0.1 7K 193 16K   0 oracle/17
6158 oracle   1.9 0.4 0.0 0.0 0.0 83 15 0.1 5K 217 11K   0 oracle/13
Total: 171 processes, 3808 lwps, load averages: 9.36, 7.14, 7.48
#root:~# plockstat -CH -n 10 -e 5 -p 20916
        0
Mutex hold
Count     nsec Lock                         Caller
    2    22935 libc.so.1`_time_lock         oracle`slgtd+0x70
    1    27510 libc.so.1`_time_lock         oracle`slgtd+0x70
    2    13120 libc.so.1`libc_malloc_lock   oracle`lwemfaa+0x60
    2     8720 libc.so.1`libc_malloc_lock   oracle`sltstidinit+0x4
    2     7975 libc.so.1`__aio_mutex        libc.so.1`_aio_close+0x44
    2     5150 libc.so.1`libc_malloc_lock   oracle`sltsmxd+0x30
    2     4935 libc.so.1`libc_malloc_lock   oracle`sltsmxi+0x4
    2     3990 libc.so.1`libc_malloc_lock   oracle`sltstiddestroy+0x4
    2     3945 libc.so.1`libc_malloc_lock   oracle`slwmmputmem+0x10
    1     5910 libc.so.1`_time_lock         oracle`sLdiGetDate+0x6c

Approximate time needed for normal shutdown of the instance

how to figure out how much time needed to stop the oracle instance?
do the oracle "shutdown immediate" in case when OS is shutting down or "shutdown normal"?
What will be the result if there are still long-running transactions when OS shutdown initiated?

Anton Kharus wrote:
how to figure out how much time needed to stop the oracle instance?
By measuring the shutdown timings from time to time.
do the oracle "shutdown immediate" in case when OS is shutting down or "shutdown normal"?
What will be the result if there are still long-running transactions when OS shutdown initiated?
Oracle is only shutdown at a system shutdown if you configure shutdown scripts to do so.
Depending on the OS you have these scripts must be placed somewhere in /etc/rc?.d or /sbin/rc?.d
It is ofcourse depending on the shutdown type, and the amount of running session.
Shutdown normal will wait until all users have disconnected
Shutdown immediate will wait until all users have ended their running statement
Shutdown transactional will wit for users to and an active transaction
Shutdown abort will not wait, but leave the database in a to-be recovered state.
Shutdown abort should only be used in case all other shutdown commands do not work, or there has been some kind of error leaving some database processes running.
HTH,
FJFranken
My Blog: http://managingoracle.blogspot.com

Shutdown with normal option

I have issued a command 'Shutdown normal' as Internal. It is not able to shutdown the oracle server. How do I stop as I don't know who are connected. It is waiting from long time.

I have issued a command 'Shutdown normal' as Internal. It is not able to shutdown the oracle server. How do I stop as I don't know who are connected. It is waiting from long time.

Windows 2003 R2 Gray Screen Hang on HP DL380 G5 when restarting or shutdown after Nov/Dec 2011 Windows Update

I’ve 4 identical HP DL 380 G5 Servers with Windows 2003 R2 Std. The 4 machines have the same Windows driver version and motherboard BIOS version. 2 have no problem. 2 have problems after Nov/Dec 2011 Windows Update!
After running for a few days from power-up, the 2 problem servers will hang at gray screen during restart. After clicking for restart,
- The Event Log service will stop normally so there is no more error log can be seen!
- The IP ping to the server can still work. The mouse pointer in Windows can still be moved.
- The Windows shutdown gray screen can be shown.
- [Ctrl-Alt-Del] has stopped to function.
Then the system just freezes at that status. I can only cold-boot the system!
After power-up again, I can do the Windows restart / shutdown normally! But after a few day of running, the above symptom repeats! The symptom happened since I installed the Windows Update in Dec 2011. It didn’t happen before that!
Anyone can give a hint on how to diagnose it?

Hi,
In order to troubleshoot the server hang issue, you can first preform a clean boot on the problematic system.
Steps:
====================
1. Click Start->Run…->type
msconfig and press Enter
2. Click Services tab and select Hide All Microsoft Services
and Disable All third party Services
3. Click Startup tab and Disable All startup items
4. Click OK and choose Restart
5. After reboot, check whether the problem still occurs
If the server hang on issue still continues in clean boot mode, for the further troubleshooting, you may check in the Task Manager to see which process takes the memory resources.
Meanwhile, you can also use reliability and performance Monitor to track down what cause the performance issue.
Windows Reliability and Performance Monitor
http://technet.microsoft.com/en-us/library/cc755081(WS.10).aspx
Windows Performance Monitor
http://technet.microsoft.com/en-us/library/cc749249.aspx
Best Regards,
Aiden
Aiden Cao
TechNet Community Support

T400 with Windows XP, freezes on shutdown

Hi, I recently purchased a Lenovo T400 laptop (originally with vista) and installed Windows XP on it. I installed all the drivers one by one from the lenovo website, and verything works nicely- except for one hitch. When I go to shutdown or restart, it starts shutting down and then at the screen "windows is shutting down" everything freezes in place. I cant move the mouse and it won't shutdown no matter how much time I give it. So I have to manually shut it down using the power button. I was wondering if anyone has encountered this problem before and know of a fix? Thanks very much,
Thio

I'm reviving this post since I'm having the same issue. Windows XP and hangs on during shutdown. Yesterday I installed around 30 updates using the ThinkVantage program. Maybe is the Power Management Driver, BIOS update, who knows. Any help will be really appreciated. Thanks.
jongsun209 wrote:
Hi,
I also have same exect problem for my T400 (after installing new audio driver).
No fixes found yet, but system restore (prior to new audio driver installation) at safemode worked for me.
(since windows can't shutdown normally on regular mode).
Hopefully this helps.

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

IPhone Keypad popping up during Shutdown

Hello Apple Technicains and Users, i don't know if this was posted before but there is a firmware problem that i've been noticing (and a couple of my friends) during the normal shutdown of the iPhone 4.
What would happen during the shutdown normally occurs 1/3, but when it's shutting down the circular progress bar will show indicating it shutting down, then after about 3 - 10 seconds the keypad will pop up. After about 2 minutes of it being up it fully shuts down.
iPhone Information -
iPhone Type - 4G
iPhone Firmware - 4.3.3
iPhone Condition - 3 Months old ( Never dropped )
Jailbroken - God no.
Carrier - ROGERS
Is anybody also having this problem? Or is it just me and my freinds?
Thanks for reading
WirsoftOnline Admin.

Hey aabirkett,
Thanks for the question. Based on the information you have provided, you may have a hardware issue with the Proximity Sensor on your iPhone 5s. To completely isolate, you can attempt the troubleshooting steps recommended for these symptoms:
iPhone: Hardware troubleshooting
http://support.apple.com/kb/TS2802
Screen won't lock or go black when answering calls
Verify mute or speaker have not been activated, just prior to placing your ear over the receiver.
While on a call hold your hand over the top third of the display, and verify that the screen is locked or goes to sleep.
Try turning iPhone off and then on again.
[…] My issue is still not resolved. What do I do next?
Contact Apple Support.
Thanks,
Matt M.

Read last shutdown information

Hello.
Where can I read information about last shutdown (a type of shutdown - normal, transactional, immediate, abort ...)?
Thanks.

Hi,
In that case you can write a startup and shutdown trigger on the database.
In the shutdown trigger,
-You would add a record in your table (say log table), all the details which you need to analyze by your client application.
The below is optional if you want to check for abort condition.
In the startup trigger.
-You would add a record about the timing of the startup of the database.
- Moreover you would also check the last inserted record. If the last inserted record was that of startup. This would mean that the last shutdown was not a clear shutdown could be a result of crash/abort (As it does not fire the shutdown trigger). If this is the case you would make a entry of shutdown here (time of shutdown would not be known but you can do approximation from v$log / v$archived_log).
Regards
Anurag Tibrewal.

Unix Command to Shutdown

What is the most basic way to shutdown via the command line? Thanks.
Steve M.

What will happen to open Mac applications?
The question of using Terminal to shutdown arose because of a very strange situation I encountered last evening. I was in the middle of saving a document as a PDF when all of a sudden the system started acting crazy. I would get a rapid staccato of warning beeps assiciated with the curson dancing around on the desktop from icon to icon highlighting each in rapid succession. Selecting something from the menu bar resulted in the focus rapidly shifting all along the row of choices, for example with Safari, the focus would shift from Apple to Safari to File to View to History, you get the picture. I was unable to quit open apps. I was unable to pull down the Apple menu to get to shutdown or restart or logout. I succeded in opening terminal somehow and got a few lines of gibberish followed by the prompt. I tried sudo shutdown but was not aware of using -h or -r. But somehow, just opening Terminal had cause my system to settle down and stabilize and I was able to shutdown normally from the Apple menu. System is fine now. I've never seen anything quite that bizarre (at least since OS 9!).
Thanks,
Steve M.

Shutdown normal

Similar Messages

Maybe you are looking for