Skip to Main Content
  • Questions

  • Database hang and we cannot switch logfile or shutting down the DB

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Hariharan.

Asked: February 28, 2018 - 1:04 pm UTC

Last updated: March 09, 2018 - 2:25 am UTC

Version: 11.2.0.4

Viewed 1000+ times

You Asked

Hi Experts,

During the issue time database hang and we cannot switch logfile or shutting down using IMMEDIATE. All the Redo logfiles are showing status ACTIVE and still its showing ACTIVE after 1 Week. \

Why the Redo logfile is still ACTIVE status for most of the logfiles ? Please help to resolve the issue


Tue Feb 20 18:33:53 2018
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
Tue Feb 20 18:44:15 2018
License high water mark = 6455
USER (ospid: 47710656): terminating the instance
Termination issued to instance processes. Waiting for the processes to exit
Tue Feb 20 18:44:25 2018
Instance termination failed to kill one or more processes ---->>>
Instance terminated by USER, pid = 47710656


Trace file
------------
Line 52: [a] Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'
Line 179: Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'
Line 110941: [a] Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'
Line 111068: Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'
Line 221113: [a] Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'
Line 221240: Chain 1 Signature: 'control file sequential read'<='log file switch (checkpoint incomplete)'<='buffer busy waits'

GROUP# MB STATUS ARC
9 3072 ACTIVE YES
9 3072 ACTIVE YES
10 3072 ACTIVE YES
10 3072 ACTIVE YES
11 3072 ACTIVE YES
13 3072 ACTIVE YES
14 3072 CURRENT NO
14 3072 CURRENT NO


Thanks,

and Connor said...

I would log a call with Support providing your alert log and any associated trace files.

But in the interim, I would not use 'shutdown immediate' - I would use shutdown abort. My shutdown method for databases for 20 years has been:

alter system checkpoint;
shutdown abort;

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Hariharan Senthil pandiyan, March 01, 2018 - 1:22 pm UTC

Thanks you, we will check and update.

A reader, March 08, 2018 - 9:14 am UTC

There was Logminer running in the Database which cause the Active state for most of the Redologs. Not sure but after disabling the Logminer status changed to Normal for all the Redologs.

Thanks,
Connor McDonald
March 09, 2018 - 2:25 am UTC

Thanks for the update. That will be useful information for others if they encounter it.
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's latest video and Chris's latest video from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database