cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Oracle Shadow process

former_member759680
Contributor
0 Kudos

Hello,

While shutting down the database for offline backup, we get the following message in Alert log:

Active call for process 5632 user 'SYSTEM' program 'ORACLE.EXE (SHAD)'

SHUTDOWN: waiting for active calls to complete.

And after that the Database doesn't shutdown.

Upon research, I found this is caused by an Oracle Bug 5907779.

Meatlink NOte - 5907779.8

But this is corrected in 10.2.0.4.

We are already on 10.2.0.4 and still we are facing this error.

Could someone please help me with resolving this?

Alert Log:

Sun Mar 21 21:03:03 2010
Shutting down instance (immediate)
License high water mark = 28
Sun Mar 21 21:03:03 2010
Stopping Job queue slave processes, flags = 7
Sun Mar 21 21:03:03 2010
Job queue slave processes stopped
Sun Mar 21 21:08:15 2010
Active call for process 5632 user 'SYSTEM' program 'ORACLE.EXE (SHAD)'
SHUTDOWN: waiting for active calls to complete.
Sun Mar 21 21:09:59 2010
Incremental checkpoint up to RBA [0x956.d68a.0], current log tail at RBA [0x956.d738.0]
Sun Mar 21 21:23:04 2010
MMNL absent for 1252 secs; Foregrounds taking over
Sun Mar 21 21:40:00 2010
Incremental checkpoint up to RBA [0x956.d766.0], current log tail at RBA [0x956.d777.0]
Sun Mar 21 22:03:18 2010
SHUTDOWN: Active sessions prevent database close operation
Sun Mar 21 22:06:49 2010

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

Do you run the latest minipatch for Oracle on Windows?

Markus

former_member759680
Contributor
0 Kudos

No, we did not run minipatch.

Would it solve this error?

I ask this because all our other servers are working fine 10.2.0.4.

markus_doehr2
Active Contributor
0 Kudos

> No, we did not run minipatch.

It's HIGHLY ADVISED to install the latest minipatch, lots of problems have been solved with patch 30.

> Would it solve this error?

I don't know - too less information, you'd need to check the oracle trace files for the specific threads.

> I ask this because all our other servers are working fine 10.2.0.4.

Those other systems may not execute that exact statement producing that crash on your database.

Markus