ORACLE EVENT && ORADEBUG

zhouwf0726發表於2019-01-27
Oracle

本文介紹一下ORACLE資料庫的除錯工具ORACLE EVENT && ORADEBUG


--首先介紹下獲得當前SESSION的SID、SERIAL#的幾種方法：

1、select sid from v$mystat where rownum = 1;

2、select sid from v$session where audsid = userenv('sessionid');

3、select sid from v$session where audsid = sys_context('userenv','sessionid');

4、select sid from v$session where sid = dbms_support.mysid;--需要單獨安裝包

D:Oracleora92rdbmsadmin>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on 星期二 6月 5 11:20:03 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> conn /as sysdba
已連線。
SQL> @dbmssupp.sql
程式包已建立。
程式包主體已建立。
SQL> GRANT EXECUTE ON dbms_support TO PUBLIC;
授權成功。
SQL> CREATE PUBLIC SYNONYM dbms_support FOR dbms_support;
同義詞已建立。
SQL> conn test/test
已連線。
SQL> select sid from v$session where sid = dbms_support.mysid;

一、ORACLE EVENT

1、“SQL TRACE”

是Oracle提供的用於進行SQL跟蹤的手段，是強有力的輔助診斷工具。在日常的資料庫問題診斷和解決中，“SQL TRACE”是
非常常用的方法。

在全域性啟用


在引數檔案(pfile/spfile)中指定: SQL_TRACE = true
在全域性啟用SQL_TRACE會導致所有程式的活動被跟蹤，包括後臺程式及所有使用者程式，這通常會導致比較嚴重的效能問題，
所以在生產環境中要謹慎使用。

在當前session級設定

SQL> alter session set SQL_TRACE=true;

會話已更改。

SQL> select * from test;

COL1 COL2 COL3
-------------------- -------------------- --------------------
00001 00002 00003
00004 00005 00006

SQL> alter session set SQL_TRACE=false;

會話已更改。

跟蹤其它使用者程式


SQL> exec dbms_system.set_SQL_TRACE_in_session(sid,seial#,true);
SQL> exec dbms_system.set_SQL_TRACE_in_session(sid,seial#,false);



2. 10046事件

10046事件是Oracle提供的內部事件，是對SQL_TRACE的增強.
10046事件可以設定以下四個級別:
1 - 啟用標準的SQL_TRACE功能,等價於SQL_TRACE。
4 - Level 1 加上繫結值(bind values)
8 - Level 1 + 等待事件跟蹤
12 - Level 1 + Level 4 + Level 8

a． 在全域性設定

在引數檔案中增加:
EVENT="10046 trace name context forever,level 12"
此設定對所有使用者的所有程式生效、包括後臺程式.

b． 對當前session設定

SQL> alter session set events '10046 trace name context forever';

SQL> alter session set events '10046 trace name context forever, level 8';

SQL> alter session set events '10046 trace name context off';

c． 對其他使用者session設定

SQL> exec dbms_system.set_ev(sid,seial#,10046,12,'');

3、利用DBMS_SUPPORT包

更多內容參看：http://zhouwf0726.itpub.net/post/9689/291636

SQL>EXECUTE dbms_support.start_trace;
SQL>EXECUTE dbms_support.start_trace (BINDS=>true);
SQL>EXECUTE dbms_support.start_trace (WAITS=>true);
SQL>EXECUTE dbms_support.start_trace_in_session(25,4328,waits->true,binds=>true);
SQL>EXECUTE dbms_support.stop_trace;
SQL>EXECUTE dbms_support.stop_trace_in_session (25, 4328);


給出幾個跟蹤指定的SESSION的例子：

SESSION 1:

SQL> SHOW USER
USER 為"TEST"

SQL> SELECT SID,SERIAL# FROM V$SESSION WHERE SID=(select sid from v$mystat where
rownum = 1);

SID SERIAL#
---------- ----------
12 6


SESSION 2:

SQL> SHOW USER
USER 為"SYS"

SQL> EXEC DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(12,6,TRUE);

PL/SQL 過程已成功完成。


SESSION 1:

SQL> set serveroutput on
SQL> declare
2 event_level number;
3 begin
4 for event_number in 10000..10999 loop
5 sys.dbms_system.read_ev(event_number, event_level);
6 if (event_level > 0) then
7 sys.dbms_output.put_line('Event '||to_char(event_number)||' is set at level '||to_char(event_level));
8 end if;
9 end loop;
10 end;
11 /
Event 10046 is set at level 1

PL/SQL 過程已成功完成。

SQL> SELECT * FROM TEST;

COL1 COL2 COL3
-------------------- -------------------- --------------------
00001 00002 00003
00004 00005 00006

SQL> SELECT P1.VALUE||''||P2.VALUE||'_ORA_'||P.SPID FILENAME
2 FROM
3 V$PROCESS P,
4 V$SESSION S,
5 V$PARAMETER P1,
6 V$PARAMETER P2
7 WHERE P1.NAME = 'user_dump_dest'
8 AND P2.NAME = 'db_name'
9 AND P.ADDR = S.PADDR
10 AND S.AUDSID = USERENV ('SESSIONID');

FILENAME
--------------------------------------------------------------------------------
D:oracleadminorcludumporcl_ORA_3204


3204:(可以用tkprof格式化後分析)

PARSING IN CURSOR #1 len=18 dep=0 uid=61 oct=3 lid=61 tim=5017207740 hv=3157870488 ad='650e4cf0'
SELECT * FROM TEST
END OF STMT
PARSE #1:c=93750,e=602584,p=1,cr=19,cu=0,mis=1,r=0,dep=0,og=4,tim=5017207733
EXEC #1:c=0,e=47,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=5017238223
FETCH #1:c=0,e=442,p=1,cr=3,cu=0,mis=0,r=1,dep=0,og=4,tim=5017244533
FETCH #1:c=0,e=34,p=0,cr=1,cu=0,mis=0,r=1,dep=0,og=4,tim=5017250817
*** 2007-06-05 09:40:41.000


SESSION 2:

SQL> SHOW USER
USER 為"SYS"

SQL> EXEC DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(12,6,FALSE);

SESSION 1:

SQL> declare
2 event_level number;
3 begin
4 for event_number in 10000..10999 loop
5 sys.dbms_system.read_ev(event_number, event_level);
6 if (event_level > 0) then
7 sys.dbms_output.put_line('Event '||to_char(event_number)||' is set at level '||to_char(event_level));
8 end if;
9 end loop;
10 end;
11 /

PL/SQL 過程已成功完成。


SESSION 2:

SQL> exec dbms_system.set_ev(12,6,10046,12,'');

PL/SQL procedure successfully completed

SESSION 1:

SQL> declare
2 event_level number;
3 begin
4 for event_number in 10000..10999 loop
5 sys.dbms_system.read_ev(event_number, event_level);
6 if (event_level > 0) then
7 sys.dbms_output.put_line('Event '||to_char(event_number)||' is set at level '||to_char(event_level));
8 end if;
9 end loop;
10 end;
11 /
Event 10046 is set at level 12

PL/SQL 過程已成功完成。

SQL> SELECT P1.VALUE||''||P2.VALUE||'_ORA_'||P.SPID FILENAME
2 FROM
3 V$PROCESS P,
4 V$SESSION S,
5 V$PARAMETER P1,
6 V$PARAMETER P2
7 WHERE P1.NAME = 'user_dump_dest'
8 AND P2.NAME = 'db_name'
9 AND P.ADDR = S.PADDR
10 AND S.AUDSID = USERENV ('SESSIONID');

FILENAME
--------------------------------------------------------------------------------

D:oracleadminorcludumporcl_ORA_3204


3204:

PARSING IN CURSOR #1 len=25 dep=0 uid=61 oct=3 lid=61 tim=6781738649 hv=1275046628 ad='64ef8a4c'
select count(*) from test
END OF STMT
PARSE #1:c=0,e=652,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=6781738640
BINDS #1:
EXEC #1:c=0,e=117,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=6781738874
WAIT #1: nam='SQL*Net message to client' ela= 5 p1=1111838976 p2=1 p3=0
FETCH #1:c=0,e=91,p=0,cr=3,cu=0,mis=0,r=1,dep=0,og=4,tim=6781739037
WAIT #1: nam='SQL*Net message from client' ela= 233 p1=1111838976 p2=1 p3=0
FETCH #1:c=0,e=3,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=0,tim=6781739404
WAIT #1: nam='SQL*Net message to client' ela= 3 p1=1111838976 p2=1 p3=0


SESSION 2:

SQL> exec dbms_system.set_ev(12,6,10046,0,'');

ALTER SESSION SET SQL_TRACE=TRUE;
ALTER SESSION SET TRACEFILE_IDENTIFIER=...;

select d.value||'/'||lower(rtrim(i.instance,chr(0)))||'_ora_'||p.spid||'.trc' trace_file_name
from (select p.spid
from v$mystat m, v$session s,v$process p
where m.statistic# = 1 and
s.sid = m.sid and
p.addr = s.paddr ) p,
( select t.instance
from v$thread t,v$parameter v
where v.name = 'thread' and
(v.value = 0 or t.thread# = to_number(v.value))) i,
( select value from v$parameter where name = 'user_dump_dest') d
/

獲得診斷事件列表：

大部分的診斷事件的數值都是在10000至10999範圍內，使用如下的指令碼可以檢視到所有的診斷事件：
SET SERVEROUTPUT ON
DECLARE
err_msg VARCHAR2(120);
BEGIN
dbms_output.enable (1000000);
FOR err_num IN 10000..10999
LOOP
err_msg := SQLERRM (-err_num);
IF err_msg NOT LIKE '%Message '||err_num||' not found%' THEN
dbms_output.put_line (err_msg);
END IF;
END LOOP;
END;
/

在UNIX系統中，可以在$ORACLE_HOME/rdbms/mesg/oraus.msg這個檔案中找到所有的診斷事件的名稱和定義。使用如下指令碼可以輸出所有
的詳細的診斷事件的資訊：

event=10000
while [ $event -ne 10999 ]
do
event=`expr $event + 1`
oerr ora $event
done

樣本輸出檔案如下：

10001, 00000, "control file crash event1"
// *Document: NO
// *Cause:
// *Action:
10002, 00000, "control file crash event2"
// *Document: NO
// *Cause:
// *Action:
10003, 00000, "control file crash event3"
// *Document: NO
// *Cause:
// *Action:
10004, 00000, "block recovery testing - internal error"
// *Document: NO
// *Cause:
// *Action:

二、ORADEBUG

ORADEBUG

ORADEBUG is an undocumented debugging utility supplied with Oracle

For more general information see ORADEBUG introduction

In Oracle 9.2 commands include

HELP
SETMYPID
SETORAPID
SETOSPID
TRACEFILE_NAME
UNLIMIT
FLUSH
CLOSE_TRACE
SUSPEND
RESUME
WAKEUP
DUMPLIST
DUMP
EVENT
SESSION_EVENT
DUMPSGA
DUMPVAR
PEEK
POKE
IPC
Dumping the SGA

HELP command

The ORADEBUG HELP command lists the commands available within ORADEBUG

These vary by release and platform. Commands appearing in this help do not necessarily work for the release/platform on which the database is running

For example in Oracle 9.2.0.1 (Windows 2000) the command 

  ORADEBUG HELP

returns the following 

CommandArgumentsDescription
HELP[command]Describe one or all commands
SETMYPIDDebug current process
SETOSPID&ltospid>Set OS pid of process to debug
SETORAPID&ltorapid> ['force']Set Oracle pid of process to debug
DUMP&ltdump_name> &ltlvl> [addr]Invoke named dump
DUMPSGA[bytes]Dump fixed SGA
DUMPLISTPrint a list of available dumps
EVENT&lttext>Set trace event in process
SESSION_EVENT&lttext>Set trace event in session
DUMPVAR&ltp|s|uga> &ltname> [level]Print/dump a fixed PGA/SGA/UGA variable
SETVAR&ltp|s|uga> &ltname> &ltvalue>Modify a fixed PGA/SGA/UGA variable
PEEK&ltaddr> &ltlen> [level]Print/Dump memory
POKE&ltaddr> &ltlen> &ltvalue>Modify memory
WAKEUP&ltorapid>Wake up Oracle process
SUSPENDSuspend execution
RESUMEResume execution
FLUSHFlush pending writes to trace file
CLOSE_TRACEClose trace file
TRACEFILE_NAMEGet name of trace file
LKDEBUGInvoke global enqueue service debugger
NSDBXInvoke CGS name-service debugger
-G&ltInst-List | def | all>Parallel oradebug command prefix
-R&ltInst-List | def | all>Parallel oradebug prefix (return output)
SETINST&ltinstance# .. | all>Set instance list in double quotes
SGATOFILE&ltSGA dump dir>Dump SGA to file; dirname in double quotes 
DMPCOWSGA&ltSGA dump dir>Dump & map SGA as COW; dirname in double quotes
MAPCOWSGA&ltSGA dump dir>Map SGA as COW; dirname in double quotes
HANGANALYZE[level]Analyze system hang
FFBEGINFlash Freeze the Instance
FFDEREGISTERFF deregister instance from cluster
FFTERMINSTCall exit and terminate instance
FFRESUMEINSTResume the flash frozen instance
FFSTATUSFlash freeze status of instance
SKDSTTPCS&ltifname> &ltofname>Helps translate PCs to names
WATCH&ltaddress> &ltlen> &ltself|exist|all|target>Watch a region of memory
DELETE&ltlocal|global|target> watchpoint &ltid>Delete a watchpoint
SHOW&ltlocal|global|target> watchpointsShow watchpoints
COREDump core without crashing process
UNLIMITUnlimit the size of the trace file
PROCSTATDump process statistics
CALL&ltfunc> [arg1] ... [argn]Invoke function with arguments
SETMYPID command
Before using ORADEBUG commands, a process must be selected. Depending on the commands to be issued, this can either be the current process or another process 
Once a process has been selected, this will be used as the ORADEBUG process until another process is selected 
The SETMYPID command selects the current process as the ORADEBUG process 
For example 
  ORADEBUG SETMYPID
ORADEBUG SETMYPID can be used to select the current process to run systemwide commands such as dumps 
Do not use ORADEBUG SETMYPID if you intend to use the ORADEBUG SUSPEND command 
SETORAPID command
Before using ORADEBUG commands, a process must be selected. Depending on the commands to be issued, this can either be the current process or another process 
Once a process has been selected, this will be used as the ORADEBUG process until another process is selected 
The SETORAPID command selects another process using the Oracle PID as the ORADEBUG process 
The syntax is 
  ORADEBUG SETORAPID pid

where pid is the Oracle process ID of the target process For example 
  ORADEBUG SETORAPID 9
The Oracle process id for a process can be found in V$PROCESS.PID 
To obtain the Oracle process ID for a foreground process use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$session
    WHERE sid = DBMS_SUPPORT.MYSID
  );
Alternatively, if the DBMS_SUPPORT package is not available use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$session
    WHERE sid = 
    (
      SELECT sid FROM v$mystat WHERE ROWNUM = 1
    )
  );
To obtain the process ID for a background process e.g. SMON use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$bgprocess
    WHERE name = 'SMON'
  );
To obtain the process ID for a dispatcher process e.g. D000 use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$dispatcher
    WHERE name = 'D000'
  );
To obtain the process ID for a shared server process e.g. S000 use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$shared_server
    WHERE name = 'S000'
  );
To obtain the process ID for a job queue process e.g. job 21 use 
  SELECT pid FROM v$process 
  WHERE addr =
  (
    SELECT paddr FROM v$session
    WHERE sid = 
    (
      SELECT sid FROM dba_jobs_running WHERE job = 21
    )
  );
To obtain the process ID for a parallel execution slave e.g. P000 use 
  SELECT pid FROM v$px_process 
  WHERE server_name = 'P000';
SETOSPID command
Before using ORADEBUG commands, a process must be selected. Depending on the commands to be issued, this can either be the current process or another process 
Once a process has been selected, this will be used as the ORADEBUG process until another process is selected 
The SETOSPID command selects the another process using the operating system PID as the ORADEBUG process 
The syntax is 
  ORADEBUG SETOSPID pid

where pid is the operating system process ID of the target process For example 
  ORADEBUG SETOSPID 34345
The operating system process ID is the PID on Unix systems and the thread number on Windows NT/2000 systems 
On Unix the PID of interest may have been identified using a top or ps command 
TRACEFILE_NAME command
This command prints the name of the current trace file e.g. 
    ORADEBUG TRACEFILE_NAME
For example 
    /export/home/admin/SS92003/udump/ss92003_ora_14917.trc
This command does not work on Windows 2000 (Oracle 9.2) 
UNLIMIT command
In Oracle 8.1.5 and below the maximum size of the trace file is restricted by default. This means that large dumps (LIBRARY_CACHE, BUFFERS) may fail. 
To remove the limitation on the size of the trace file use 
    ORADEBUG UNLIMIT
In Oracle 8.1.6 and above the maximum size of the trace file defaults to UNLIMITED 
FLUSH command
To flush the current contents of the trace buffer to the trace file use 
    ORADEBUG FLUSH
CLOSE_TRACE command
To close the current trace file use 
    ORADEBUG CLOSE_TRACE
SUSPEND command
This command suspends the current process 
First select a process using SETORAPID or SETOSPID 
Do not use SETMYPID as the current ORADEBUG process will hang and cannot be resumed even from another ORADEBUG process 
For example the command 
  ORADEBUG SUSPEND
suspends the current process 
The command 
  ORADEBUG RESUME
resumes the current process 
While the process is suspended ORADEBUG can be used to take dumps of the current process state e.g. global area, heap, subheaps etc. 
This example demonstrates how to take a heap dump during a large (sorting) query 
This example requires two sessions, session 1 logged on SYS AS SYSDBA and session 2 which executes the query. In session 2 identify the PID using 
    SELECT pid FROM v$process
    WHERE addr IN
    (
        SELECT paddr FROM v$session
        WHERE sid = dbms_support.mysid
    );
In this example the PID was 12 
In session 1 set the Oracle PID using 
    ORADEBUG SETORAPID 12
In session 2 start the query 
    SELECT ... FROM t1 ORDER BY ....
In session 1 suspend session 2 
    ORADEBUG SUSPEND
The query in session 2 will be suspended 
In session 1 run the heap dump 
    ORADEBUG DUMP HEAPDUMP 1
The heapdump will show the memory structures allocated for the sort. At this point further dumps e.g. subheap dumps can be taken. 
In session 1 resume session 2 
    ORADEBUG RESUME
The query in session 2 will resume execution 
RESUME command
This command resumes the current process 
First select a process using SETORAPID or SETOSPID 
Do not use SETMYPID as the current ORADEBUG process will hang and cannot be resumed even from another ORADEBUG process 
For example the command 
  ORADEBUG SUSPEND
suspends the current process 
The command 
  ORADEBUG RESUME
resumes the current process 
While the process is suspended ORADEBUG can be used to take dumps of the current process state e.g. global area, heap, subheaps etc. 
See SUSPEND for an example of use of the SUSPEND and RESUME commands 
WAKEUP command
To wake up a process use 
    ORADEBUG WAKEUP pid

For example to wake up SMON, first obtain the PID using 
    SELECT pid FROM v$process
    WHERE addr = 
    (
        SELECT paddr FROM v$bgprocess
        WHERE name = 'SMON'
    );
If the PID is 6 then send a wakeup call using 
    ORADEBUG WAKEUP 6
DUMPLIST command
To list the dumps available in ORADEBUG use 
    ORADEBUG DUMPLIST pid

For example in Oracle 9.2 (Windows 2000) this command returns the following 
Dump Name
EVENTS
TRACE_BUFFER_ON
TRACE_BUFFER_OFF
HANGANALYZE
LATCHES
PROCESSSTATE
SYSTEMSTATE
INSTANTIATIONSTATE
REFRESH_OS_STATS
CROSSIC
CONTEXTAREA
HEAPDUMP
HEAPDUMP_ADDR
POKE_ADDRESS
POKE_LENGTH
POKE_VALUE
POKE_VALUE0
GLOBAL_AREA
MEMORY_LOG
REALFREEDUMP
ERRORSTACK
HANGANALYZE_PROC
TEST_STACK_DUMP
BG_MESSAGES
ENQUEUES
SIMULATE_EOV
KSFQP_LIMIT
KSKDUMPTRACE
DBSCHEDULER
GRANULELIST
GRANULELISTCHK
SCOREBOARD
GES_STATE
ADJUST_SCN
NEXT_SCN_WRAP
CONTROLF
FULL_DUMPS
BUFFERS
RECOVERY
SET_TSN_P1
BUFFER
PIN_BUFFER
BC_SANITY_CHECK
FLUSH_CACHE
LOGHIST
ARCHIVE_ERROR
REDOHDR
LOGERROR
OPEN_FILES
DATA_ERR_ON
DATA_ERR_OFF
BLK0_FMTCHG
TR_SET_BLOCK
TR_SET_ALL_BLOCKS
TR_SET_SIDE
TR_CRASH_AFTER_WRITE
TR_READ_ONE_SIDE
TR_CORRUPT_ONE_SIDE
TR_RESET_NORMAL
TEST_DB_ROBUSTNESS
LOCKS
GC_ELEMENTS
FILE_HDRS
KRB_CORRUPT_INTERVAL
KRB_CORRUPT_SIZE
KRB_PIECE_FAIL
KRB_OPTIONS
KRB_SIMULATE_NODE_AFFINITY
KRB_TRACE
KRB_BSET_DAYS
DROP_SEGMENTS
TREEDUMP
LONGF_CREATE
ROW_CACHE
LIBRARY_CACHE
SHARED_SERVER_STATE
KXFPCLEARSTATS
KXFPDUMPTRACE
KXFPBLATCHTEST
KXFXSLAVESTATE
KXFXCURSORSTATE
WORKAREATAB_DUMP
OBJECT_CACHE
SAVEPOINTS
OLAP_DUMP
DUMP command
To perform a dump use 
    ORADEBUG DUMP dumpname level

For example for a level 4 dump of the library cache use 
    ORADEBUG SETMYPID
    ORADEBUG DUMP LIBRARY_CACHE 4
EVENT command
To set an event in a process use 
    ORADEBUG EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level

For example to set event 10046, level 12 in Oracle process 8 use 
    ORADEBUG SETORAPID 8
    ORADEBUG EVENT 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12
SESSION_EVENT command
To set an event in a session use 
    ORADEBUG SESSION_EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level

For example 
    ORADEBUG SESSION_EVENT 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12
DUMPSGA
To dump the fixed SGA use 
    ORADEBUG DUMPSGA
DUMPVAR
To dump an SGA variable use 
    ORADEBUG DUMPVAR SGA variable_name

e.g. 
    ORADEBUG DUMPVAR SGA kcbnhb
which returns the number of hash buckets in the buffer cache 
The names of SGA variables can be found in X$KSMFSV.KSMFSNAM. Variables in this view are suffixed with an underscore e.g. 
    kcbnhb_
PEEK
To peek memory locations use 
    ORADEBUG PEEK address length

where address can be decimal or hexadecimal and length is in bytes 
For example 
    ORADEBUG PEEK 0x20005F0C 12
returns 12 bytes starting at location 0x20005f0c 
POKE
To poke memory locations use 
    ORADEBUG POKE address length value

where address and value can be decimal or hexadecimal and length is in bytes 
For Example 
    ORADEBUG POKE 0x20005F0C 4 0x46495845
    ORADEBUG POKE 0x20005F10 4 0x44205349
    ORADEBUG POKE 0x20005F14 2 0x5A45
WARNING Do not use the POKE command on a production system 
IPC
To dump information about operating system shared memory and semaphores configuration use the command 
    ORADEBUG IPC
This command does not work on Windows NT or Windows 2000 (Oracle 9.2) 
On Solaris, similar information can be obtained using the operating system command 
    ipcs -b
Dumping the SGA
In some versions it is possible to dump the entire SGA to a file 
Freeze the instance using 
    ORADEBUG FFBEGIN
Dump the SGA to a file using 
    ORADEBUG SGATOFILE directory

Unfreeze the instance using 
    ORADEBUG FFRESUMEINST
This works in Oracle 9.0.1 and 9.2.0 on Solaris, but fails in both versions in Windows 2000 





來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/756652/viewspace-242439/，如需轉載，請註明出處，否則將追究法律責任。







相關文章