Can a "shutdown abort" cause a fractured block?

Hey there, simple question: Can a "shutdown abort" cause a fractured block?
I'm currently doing some postmortem work on an old DB (EBS R12 OBA) installation and what might lead to a fractured block. It appears that once a fractured block is detected, Oracle Support automatically shuffles the issue off as a "serious issue within the OS/HW layer". I suppose as a DBA this means they can wash their hands of the issue and pass it on to someone else.
So far it appears that an OS level app could compromise the write of logical blocks to OS blocks. It also appears that logical volume configuration (pertaining to an older AIX install) could lead to fractured blocks. Yet another article indicates that an HBA I/O error could lead to this issue. And of course file-system corruption.
But...going back to the original question, can a shutdown abort on a database introduce a fractured block?

It cannot. A shutdown abort or any abnormal termination means that active transactions are terminated without COMMIT or ROLLBACK. When you start the database after a SHUTDOWN ABORT or any other abnormal termination, Oracle says the active transactions failed and rolls them back. You will be left with the database in a consistent state as if those active transactions never occurred. I suppose you could say that until recovery is complete the block could be in a fractured state meaning that the contents could be inconsistent. But once the database is opened, the block is consistent and not fractured.
HTH,
Brian

Similar Messages

Hi. My phone screen broke and I had it replaced from a phone shop. The guy said that while changing the screen and phone was blocked. It is now disabled for like 23,000,000 minutes and I can't restore it cause I dont have all the data sync to my computer.

Hi. My phone screen broke and I had it replaced from a phone shop. The guy said that while changing the screen and phone was blocked. It is now disabled for like 23,000,000 minutes and I can't restore it cause I dont have all the data sync to my computer. Is there anything I can do or can Apple do something if I give them the correct password?

As you had the iPhone opened by an unauthorised repairer ( Apple do not replace screens on iPhone 4)
Apple will not provide any service or support
Take it back to the "phoneShop" and tell them to fix it
You have no other alternatives
or try this
http://support.apple.com/kb/HT1212

What is a Fractured Block ?

Hi ,
May anyone let me know what is a Fractured Block, how it comes and what is its impact in the database ?
Thanks in advance.
Deep

Fractured Blocks a.k.a split blocks comes while taking non-RMAN online backups.
Read the following excerpt to know more about the factured block and its disadantages. Fractured block generally leads excessive redo.
==
Extract from metalink note : 76736.1:
Q: Why do tablespaces not require hot backup mode or extra logging
when using RMan for backups?
A: To understand why RMAN does not require extra logging or backup mode,
you must first understand why those features are required for non-RMAN
online backups.
A non-RMAN online backup consists of a non-Oracle tool, such as cp or
dd, backing up a datafile at the same time that DBWR is updating the
file. We can't prevent the tool from reading a particular block at the
exact same time that DBWR is updating that block. When that happens,
the non-Oracle tool might read a block in a half-updated state, so that
the block which is copied to the backup media might only have been
updated in its first half, while the second half contains older data.
This is called a "fractured block". If this backup needs to be restored
later, and that block needs to be recovered, recovery will fail because
that block is not usable.
The 'alter tablespace begin backup' command is our solution for the
fractured block problem. When a tablespace is in backup mode, and a
change is made to a data block, instead of logging just the changed
bytes to the redo log, we also log a copy of the entire block image
before the change, so that we can reconstruct this block if media
recovery finds that this block was fractured. That block image logging
is what causes extra redo to be generated while files are in backup
mode.
The reason that RMAN does not require extra logging is that it
guarantees that it will never back up a fractured block. We can make
that guarantee because we know the format of Oracle data blocks, and we
verify that each block that we read is complete before we copy it to the
backup. If we read a fractured block, we read the block again to obtain
a complete block before backing it up. non-Oracle tools are not able to
do the same thing because they do not know how to verify the contents of
an Oracle data block.
Backup mode has another effect, which is to 'freeze' the checkpoint in
the header of the file until the file is removed from backup mode.
We do this because we cannot guarantee that the third-party backup
tool will copy the file header prior to copying the data blocks.
RMAN does not need to freeze the file header checkpoint because we
know the order in which we will read the blocks, which enables us to
capture a known good checkpoint for the file.

My oracle as well as the linux can not shutdown

my linux 7.3 and oracle 817, can not been 'shutdown abort', and for linux, "shutdown -fr now", after the case logged that the ram has been run out.
I think it could caused by the io process between oracle instance and filesystem was interrupte before it complete, and locked can not open.
there is some way to resume the system ,except for hot reboot I did now?
site: http://dep.daifumd.com

You can upgrade the iMac for no extra charge - sign into the App Store there, download and install 10.8.
I recommend that you make a backup (Time Machine is probably the easiest method) before you install, and make sure that you are not using any applications that are incomptible with 10.8 (eg Office 2004) - other than that, it should go smoothly.
Matt

Loss of all controlfile,database is automatic shutdown abort?

Your database is configured in NOARCHIVELOG mode. All the control files have been lost due to a hard disk failure but the data files are not lost. You have the closed whole database backup available to you. Which two statements are true in this scenario? (Choose two.)
A) The instance aborts.
B) The database cannot be recovered.
C) The database can be recovered by restoring the control files from the backup.
D) The database remains opened and you have to shut it down with the ABORT option.
E) The database can be restored till the point of the last closed whole database backup.
noarchivelog mode , before open database i had rman backup full database;
idle> conn / as sysdba
Connected.
idle> alter database open;
Database altered.
idle> conn anbob/anbob
Connected.
anbob@ANBOB> create table testdelctl(id int);
Table created.
anbob@ANBOB> insert into testdelctl values(999);
1 row created.
anbob@ANBOB> commit;
Commit complete.
anbob@ANBOB> conn system/oracle
Connected.
system@ANBOB> select * from v$controlfile;
STATUS
NAME
IS_ BLOCK_SIZE FILE_SIZE_BLKS
/oracle/oradata/anbob/control01.ctl
NO 16384 430
/oracle/oradata/anbob/control02.ctl
NO 16384 430
/oracle/oradata/anbob/control03.ctl
NO 16384 430
system@ANBOB> !rm /oracle/oradata/anbob/control*.ctl
system@ANBOB> !ls /oracle/oradata/anbob/
redo01.log redo03.log system01.dbf undotbs01.dbf users01.dbf
redo02.log sysaux01.dbf temp01.dbf undotbs2.dbf
system@ANBOB> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/oradata/anbob/control01.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
system@ANBOB> select status from v$instance;
STATUS
OPEN
sys@ANBOB> conn anbob/anbob
Connected.
anbob@ANBOB> select * from testdelctl;
ID
999
anbob@ANBOB> insert into testdelctl values(0);
1 row created.
anbob@ANBOB> commit;
Commit complete.
anbob@ANBOB> conn / as sysdba
Connected.
sys@ANBOB> alter systme checkpoint;
alter systme checkpoint
ERROR at line 1:
ORA-00940: invalid ALTER command
sys@ANBOB> alter system checkpoint;
System altered.
sys@ANBOB> select status from v$instance;
STATUS
OPEN
sys@ANBOB> select * from v$version where rownum=1
2 ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
sys@ANBOB> shutdown immediate
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/oracle/oradata/anbob/control01.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
sys@ANBOB> shutdown abort
ORACLE instance shut down.
sys@ANBOB> startup
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 96471284 bytes
Database Buffers 67108864 bytes
Redo Buffers 2973696 bytes
ORA-00205: error in identifying control file, check alert log for more info
sys@ANBOB> select status from v$instance;
STATUS
STARTED
[oracle@aix ~]$ rman target/
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Jul 14 22:32:12 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: anbob (not mounted)
RMAN> restore controlfile;
Starting restore at 14-JUL-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/14/2011 22:32:27
RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP
RMAN> restore controlfile from autobackup;
Starting restore at 14-JUL-11
using channel ORA_DISK_1
recovery area destination: /oracle/flash_recovery_area
database name (or database unique name) used for search: ANBOB
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /oracle/flash_recovery_area/ANBOB/autobackup/2011_07_14/o1_mf_s_756511643_71xy4xjm_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/oracle/oradata/anbob/control01.ctl
output filename=/oracle/oradata/anbob/control02.ctl
output filename=/oracle/oradata/anbob/control03.ctl
Finished restore at 14-JUL-11
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:32:52
ORA-01507: database not mounted
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:33:12
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/14/2011 22:33:19
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/oradata/anbob/system01.dbf'
RMAN> recover database;
Starting recover at 14-JUL-11
Starting implicit crosscheck backup at 14-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 14-JUL-11
Starting implicit crosscheck copy at 14-JUL-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 14-JUL-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /oracle/flash_recovery_area/ANBOB/autobackup/2011_07_14/o1_mf_s_756511643_71xy4xjm_.bkp
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 19 is already on disk as file /oracle/oradata/anbob/redo03.log
archive log thread 1 sequence 20 is already on disk as file /oracle/oradata/anbob/redo01.log
archive log filename=/oracle/oradata/anbob/redo03.log thread=1 sequence=19
archive log filename=/oracle/oradata/anbob/redo01.log thread=1 sequence=20
media recovery complete, elapsed time: 00:00:03
Finished recover at 14-JUL-11
RMAN> alter database open resetlogs;
database opened
RMAN> exit
Recovery Manager complete.
o[oracle@aix ~]$ ora
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jul 14 22:34:23 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
sys@ANBOB> !ls /oracle/oradata/anbob/
control01.ctl control03.ctl redo02.log sysaux01.dbf temp01.dbf undotbs2.dbf
control02.ctl redo01.log redo03.log system01.dbf undotbs01.dbf users01.dbfconn anbob
sys@ANBOB> conn anbob
Enter password:
Connected.
anbob@ANBOB> select * from tab;
TNAME TABTYPE CLUSTERID
TESTCHAR TABLE
TT TABLE
TESTTRUN TABLE
TESTADDM TABLE
TEST TABLE
TESTFUNIDX TABLE
TEAM TABLE
MEMB TABLE
TESTENC TABLE
TESTREC TABLE
BIN$p/SuvHy7sn7gQKjA9QF/dQ==$0 TABLE
DETP TABLE
TESTDELCTL TABLE
DEPT TABLE
TESTFLS TABLE
15 rows selected.
anbob@ANBOB> select * from testdelctl;
ID
999
0
why,loss of all controlfile,the database not abort?

Satish Kandi wrote:
The files, which are in use by a process, are not actually deleted when one issues rm command.
Its only when the process terminates that the locks are released and file is actually deleted at operating system level.I concur!
This behavior is *NIX only.
Windows explicitly prevents open files from being deleted.
Edited by: sb92075 on Jul 14, 2011 9:18 PM

SHUTDOWN ABORT in ORACLE 10g

Hi,
I wrote a procedure to be run before reinstalling a database. As I am not interested in rolling back, or waiting for transactions to finish, I am using SHUTDOWN ABORT to drop users. Everything works well in ORACLE 9i but it cannot restart in 10g - error:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor.
The procedure looks like:
SHUTDOWN ABORT
STARTUP RESTRICT
declare
cursor cnt_usr is
Select username from dba_users where username in (....some user names);
str_cmd varchar2(400):='';
begin
FOR usr IN cnt_usr LOOP
BEGIN
str_cmd := 'DROP USER '|| usr.username || ' CASCADE ' ;
dbms_output.put_line ('Executing: '|| str_cmd);
EXECUTE IMMEDIATE str_cmd;
EXCEPTION
WHEN OTHERS THEN str_cmd := ' ';
END;
END LOOP;
end;
ALTER SYSTEM DISABLE RESTRICTED SESSION;
exit;
Any idea what may cause the error?
Thank you
Dan

> You do know that Abort means to kill the database.
Incorrect. It simply means that the database is shutdown in an inconsistent state - i.e. with "open" transactions and thus "dirty" data.
However, Oracle is designed as a very robust database and this is not a problem. It simply gets the database into a consistent state again on the next startup.
The risk is that something or someone interferes (mucks up) Oracle data files before the next db start - without the redo logs for example, the instance will have a hard time trying to recover the database and get it into a consistent state.
The danger is thus not Oracle, but the Idiot Factor one tends to get with cowboy-type administrators.
What is questionable though is the OP's script that requires the database to be shutdown and started up for a series of drop schemas. That is using a Very Large Hammer to drive in a Very Small Nail. It is a total overkill - not too mention impacting database availability.. And I do not think that our environment is so special/unique that it the exception to measure Oracle instance uptime in 1000's of hours.

How to startup database after shutdown abort

Hi.
I had a havy load transaction, coudn't kill, so I run shutdown abort,
now I can't open database, that is massage I get:
"ORA-16038: log 3 sequence# 52 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1:
'/u01/app/oracle/oradata/ORCL/onlinelog/o1_mf_3_48fpv6q1_.log'
ORA-00312: online log 3 thread 1:
'/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/o1_mf_3_48fpv95v_.log'
What to do?

Upss sorry:
Check your flashrecovery area directory, it's full and your redo logs cannot be archived
release the space..
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
Edited by: Kamran Agayev A. on Mar 5, 2009 8:27 PM

Shutdown abort during switch over?

Hello,
I seem to notice a different behaviour between 11.2.0.1 and 11.2.0.2 during switchover on Linux 64 bit.
On primary I'm connected in sqlplus
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY;
Database altered.
exit
In alert.log:
Fri Dec 03 11:52:50 2010
Process (ospid 15296) is suspended due to switchover to physical standby operation.
Enter again in sqlplus
SQL> SHUTDOWN IMMEDIATE;
ORA-01092: ORACLE instance terminated. Disconnection forced
in alert.log
Fri Dec 03 11:53:23 2010
Performing implicit shutdown abort due to switchover to physical standby
Shutting down instance (abort)
License high water mark = 811
USER (ospid: 16022): terminating the instance
Instance terminated by USER, pid = 16022
Fri Dec 03 11:53:25 2010
Instance shutdown complete
ORA-1092 : opitsk aborting process
remaining inside sql session:
SQL> STARTUP MOUNT;
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
exit and restart sqlplus
SQL> STARTUP MOUNT;
ORACLE instance started.
Total System Global Area 2739171328 bytes
Fixed Size          2229640 bytes
Variable Size          1207962232 bytes
Database Buffers     1509949440 bytes
Redo Buffers          19030016 bytes
in alert.log
Fri Dec 03 11:55:02 2010
Starting ORACLE instance (normal)
****************** Huge Pages Information *****************
Huge Pages memory pool detected (total: 1500 free: 1500)
DFLT Huge Pages allocation successful (allocated: 1313)
And then normal election to primary for the dr RDBMS.
But I didn't notice this "shutdown abort" when using 11.2.0.1.
The same happens if at the beginning I remain in sqlplus sesison and try to run "startup mount"
Is this expected?
Thanks in advance,
Gianluca

If you use IMMEDIATE, an ABORT will be performed anyway as of 11.2.0.2 and you would see the following in the alert
Performing implicit shutdown abort due to switchover to physical standby
Shutting down instance (abort)
So the answer is Yes.
You can confirm this yourself by reviewing :
11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus [ID 1304939.1]
Best Regards
mseberg
Wow, this question is way old! Please open your own question user user11311455, you caught me before I had coffee.
Edited by: mseberg on Aug 17, 2011 8:09 AM

Database is hang during shutdown abort (Urgent Production Issue)

Hi Gurus
In my production system while shutdown immediate , database was hang.
When we logged in system and gave shutdown abort its again hang.
Pls suggest me what could be the reason and how it can be solved
Thanks

Tue Oct 21 05:01:09 2008
Shutting down instance: further logons disabled
Tue Oct 21 05:45:19 2008
ksvcreate: Process(q005) creation failed
Tue Oct 21 05:45:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:45:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:45:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:46:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:47:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:30 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:42 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:48:54 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:06 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:18 2008
ksvcreate: Process(q000) creation failed
Tue Oct 21 05:49:24 2008
Shutting down instance (abort)
License high water mark = 26
Termination issued to instance processes. Waiting for the processes to exit
Tue Oct 21 05:49:35 2008
Instance termination failed to kill one or more processes
Tue Oct 21 06:06:43 2008
Instance terminated by USER, pid = 20613

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 abort

whats the worst thing that can happen when you kill oracle procee kill -9 or do shutdown abort ?
will oracle always get away with instance recovery ?
or it could corrupt redo log?
will there be need for recovery or restore?

whats the worst thing that can happen when you kill oracle procee kill -9 or do shutdown abort ?Database will shut down in inconsistent state and in next startup it need the instance recovery which is done automatically by SMON process.
will oracle always get away with instance recovery ?
or it could corrupt redo log? What you do mean by this line? Not clear to me what you want to ask
will there be need for recovery or restore?No need to restore and recovery is required in case of instance crash.
--neeraj

Can not shutdown the server 206

Hello,
On adf & non-adf servers I am getting following error with opmn command
/apps/std/1022/opmn/bin/opmnctl stopall
opmnctl: stopping opmn and all managed processes...
opmnctl: graceful stop of processes failed, trying forceful shutdown...
Can not shutdown the server 206
This happens more often than I like, and wondering what may be the cause?
This especially happens after I undeploy or deploy application.
Thanks
s

s,
For OC4J we use the admin.jar:
http://download.oracle.com/docs/cd/B31017_01/web.1013/b28950/startstop.htm-Michael

Opmn 'Can not shutdown the server 206'

Hello,
On adf & non-adf servers I am getting following error with opmn command
/apps/std/1022/opmn/bin/opmnctl stopall
opmnctl: stopping opmn and all managed processes...
opmnctl: graceful stop of processes failed, trying forceful shutdown...
Can not shutdown the server 206
This happens more often than I like, and wondering what may be the cause?
This especially happens after I undeploy or deploy application.
Thanks
s

Thanks shail,
I didn't see any useful error in opmn.log or ipm.log
didn't see any error in log/states/* either
Currently my script ignores the shutdown errors and call startall
However I see following errors (shutdown appears to be ok) in opmn/logs/OC4J~spfstd~default_island~1 log file
09/04/20 12:01:24 Stop process
09/04/20 12:01:27 Shutting down...
09/04/20 12:01:27 JAM Agent: jaminit.destroy()
09/04/20 12:01:27 JAM Agent: jamagent.destroyJam() called
JAM Agent: Shutdown signal received, shutting down
09/04/20 12:01:27 JAM Agent: Shutdown complete
09/04/20 12:03:37 Start process
09/04/20 12:03:58 log4j:ERROR setFile(null,true) call failed.
09/04/20 12:03:58 java.io.FileNotFoundException: /logs/idp/idp.log (No such file or directory)
09/04/20 12:03:58 at java.io.FileOutputStream.openAppend(Native Method)
09/04/20 12:03:58 at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
09/04/20 12:03:58 at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
09/04/20 12:03:58 at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
09/04/20 12:03:58 at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:156)
09/04/20 12:03:58 at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
09/04/20 12:03:58 at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247)
09/04/20 12:03:58 at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123)
09/04/20 12:03:58 at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87)
09/04/20 12:03:58 at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645)
09/04/20 12:03:58 at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603)
09/04/20 12:03:58 at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:524)
09/04/20 12:03:58 at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:408)
09/04/20 12:03:58 at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:432)
09/04/20 12:03:58 at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460)
09/04/20 12:03:58 at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)

Running shutdown abort

When calling shutdown immediate and it lasts long
because of rolling back some transaction, I call
shutdown abort and start the instance, the crash recovery
succeeds, is there any reason for shutting down normal
again to last long too (there are no transactions to roll back)?

Hi,
any reason for shutting down normal do you mean shutdown normalWhen shutting down normal, Oracle waits for connected users to willingly disconnect (you can kill the sessions too though). Check if you've gor jobs running (DBA_JOBS_RUNNING) because they 'connect' to the database in order to run. This could be the reason why it takes a long time.
For example if I bounce one of my main DBs, once it's open, at least 5 jobs will start running. If I issue shutdown normal it'll wait for these job to finish their tasks.
Regards,
Yoann.

Can't Shutdown Problem

i can't shutdown my hp pavilion touchsmart. even when i change "closing the lid" and "power button" into shutdown. Help me please. I can't shutdown my unit.

Hello diding_hp,
Welcome to the HP Forums!
I understand you are unable to shut down the notebook. To assist you, please provide the following information:
1. The computer's model number. If you require assistance locating this information, please reference this website: Guide to finding your product number
2. The computer's operating system. If you require assistance locating this information, please reference this website to determine your Windows operating system.
3. Have you installed any new hardware on this computer, before the issue appeared?
4. Have you installed any new software or drivers on this computer, before the issue appeared?
Additionally, if the issue just began occurring, I would perform a system restore. I want you to bring the computer back to the earliest restore point possible, in an attempt to dodge whatever caused the issue. Here is a document on how to perform a System Restore: System Restore
Thanks for posting on the HP Forums. Have a great day!
Mario
I worked on behalf of HP.

Can a "shutdown abort" cause a fractured block?

Similar Messages

Maybe you are looking for