Offline backup shuting database

[Former Member]

Hi,

offline backup in bi server.

all the oracle process are stopped. nothing is running in oracle sid.

ps -ef|grep ora_ showing no process. but it is nit shutting down.

but

alert log showing below message

SMON: disabling cache recovery

Fri Mar 26 12:15:18 2010

Shutting down archive processes

Archiving is disabled

Fri Mar 26 12:15:23 2010

ARCH shutting down

ARC1: Archival stopped

Fri Mar 26 12:15:28 2010

ARCH shutting down

ARC0: Archival stopped

Fri Mar 26 12:16:51 2010

Thread 1 closed at log sequence 11347

Successful close of redo thread 1

Fri Mar 26 12:17:37 2010

Completed: ALTER DATABASE CLOSE NORMAL

Fri Mar 26 12:17:38 2010

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

Fri Mar 26 12:22:39 2010

SHUTDOWN: waiting for detached processes to terminate.

kindly help me

kvl

[former_member524429]

Hi,

Oracle Release ?

OS release ?

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
Fri Mar 26 12:22:39 2010
SHUTDOWN: waiting for detached processes to terminate.

Such problems have been found with Oracle 8.0.6.* versions. Please apply the latest patches.

Also if possible upgrade the Oracle Release, If running with Oracle 8.

Please refer Topic 4.b and 4.g of SAP Note 521264 - Hang situations along with the suggested SAP Notes within that SAP Note to get more information.

Regards,

Bhavik G. Shroff

[Former Member]

Thanx

Oracle Release - 10.2.0.2

OS release - Aix 5.3

it took one hour to shutdown.

kvl

[former_member204746]

there was probably one big rollback that had to be done before being able tu shutdown Oracle cleanly.

check alert_SID.log for more clues.