بسم الله الرحمن الرحيم

السلام عليكم ورحمة الله وبركاته

لدي سيرفير linux3 + oracle 10g

عندما قمت بعمل
shutdown immediate

استغرق زمن طويل

قمت بعمل
shutdown abort

ثم

startup

تمت فتح الdatabase

ثم

shutdown immediate

أيضاً لم يستجيب

راجعت ال alert_$ORACLE_SID.log


وجدته به error ويشير لملف ال trace المرفق بالموضوع

فما هو حل هد`ه المشكلة ؟؟

أخوكم


الملف ال trace

branch06_ora_2834.txt

SHUTDOWN IMMEDIATE hangs or very slow

Loss of functionality
----------------------
basic functionality as shutdown immediate doesnot work



Sequence of events
-------------------
after shutdown immediate

sqlplus> shutdown immediate


Where did it happen
-------------------
after shutdown immediate

Significance of loss
---------------------
basic functionality as shutdown immediate doesnot work

Specific error
----------------
Alert messages 'SHUTDOWN: waiting for active calls to complete.'


What is working
-----------------
Database works

Expected result
---------------
find reasonable explanation why basic functionality
doesnot work or is this a bug




Cause
Is db control's repository running on the database target, against which
shutdown immediate was attempted? If YES, then it's the wrong way of doing
it. You should stop db control first to get rid of all connections between db
control and repository database and then shutdown the database with 'shutdown
immediate'.

current database session:
SQL> select SID, USERNAME, PROGRAM from v$session;
SID USERNAME PROGRAM
---------- ------------------------------ --------------------------------------
243 SYSTEM SQL Developer
246 SYSMAN OMS
247 oracle@lgiora09 (q001)
248 oracle@lgiora09 (q000)
251 DBSNMP emagent@lgiora09 (TNS V1-V3)
252 SYSMAN OMS
253 SYSMAN OMS
254 DBSNMP emagent@lgiora09 (TNS V1-V3)
255 SYSTEM java.exe
256 SYSMAN OMS
.
clearly OMS and OEM are connected ( GRID CONTROL or DBCONSOLE or ORACLE
ENTERPRISE MANAGER) - (SYSMAN and DBSNMP)
These sessions should be de-activated ( that is to log off any OEM OMS,
SYSMAN and DBSNMP ) before shutdown immediate is attempted




Solution
To implement the solution,
1. clearly OMS and OEM are connected ( GRID CONTROL or DBCONSOLE or ORACLE
ENTERPRISE MANAGER) - (SYSMAN and DBSNMP)
These sessions should be de-activated ( that is to log off any OEM OMS,
SYSMAN and DBSNMP ) before shutdown immediate is attempted

It is not a bug.

Dbconsole, Oracle Enterprise Manager and Grid Control and agents keep doing internal processing

- also a few PLSQL notification procedures running on the database by database control like

BEGIN EMD_NOTIFICATION.QUEUE_READY(:1, :2, :3); END;

For shutdown immediate, if there are active call then wait for the all the active calls to finish

so dbconsole or Oracle Enterprise Manager or Grid Control should be disconnected before

sqlplus> shutdown immediate
is done

also few PLSQL notification procedures running on the
database by database control like BEGIN EMD_NOTIFICATION.QUEUE_READY(:1, :2, :
3); END;

As per internal documentation of the shutdown immediate, if there are active
call
then it would wait for the all the active calls to finish.

Ref:OracleMetalink

أخي الفاضل
k_ocp

جزاك الله خيراً
و لكن أنا عملت

shutdown abort

ثم

startup

ثم

shutdown immediate

مما يعني أنه لا يوجد connection علي ال database

أخوي ابن الجوزي

السلام عليكم

ممكن تسوي الخطوات التاليه:

shutdown abort

ثم

بعدين سوي إعادة تشغيل للسيرفر

ثم

startup database

ثم

shutdown immediate

وقلي اش النتيجه

أخي الفاضل
k_ocp

لقد جربت هذه الطريقة عندما واجهتني المشكلة
و لكن لم تستجيب .

Shutdown_immediate_hangs.zipأخوي ابن الجوزي

السلام عليكم


شوف الملفات اللي رفعتها



وقلي اش النتيجه

patch 5057695 for linux 86x


Patch.zip