XXXX1012-Oracle數(shù)據(jù)庫(kù)診斷事件詳解(如何獲取所有內(nèi)部事件號(hào))

1、.：.；Oracle數(shù)據(jù)庫(kù)診斷事件詳解什么是Oracle數(shù)據(jù)庫(kù)的診斷事件呢？簡(jiǎn)而言之的來(lái)說(shuō)Oracle的診斷事件就是Oracle數(shù)據(jù)庫(kù)中用于實(shí)現(xiàn)一些特殊功用的類(lèi)別，普通主要用于實(shí)現(xiàn)以下幾個(gè)方面的功用：改動(dòng)Oracle數(shù)據(jù)庫(kù)的行為啟用搜集Oracle數(shù)據(jù)庫(kù)的跟蹤或者調(diào)試信息啟用對(duì)Oracle數(shù)據(jù)庫(kù)的額外的錯(cuò)誤檢測(cè)4 5r/Rd0一、 Oracle數(shù)據(jù)庫(kù)診斷事件簡(jiǎn)介ITPUB個(gè)人空間K$g,r aNVkeCG什么是Oracle數(shù)據(jù)庫(kù)的診斷事件呢？簡(jiǎn)而言之的來(lái)說(shuō)Oracle的診斷事件就是Oracle數(shù)據(jù)庫(kù)中用于實(shí)現(xiàn)一些特殊功用的類(lèi)別，普通主要用于實(shí)現(xiàn)以下幾個(gè)方面的功用：p L8z%I6?&djZ$Z

2、3F0 改動(dòng)Oracle數(shù)據(jù)庫(kù)的行為u R.|5d;+_V4f*OUD0 啟用搜集Oracle數(shù)據(jù)庫(kù)的跟蹤或者調(diào)試信息ITPUB個(gè)人空間,.A%ct8mh4b 啟用對(duì)Oracle數(shù)據(jù)庫(kù)的額外的錯(cuò)誤檢測(cè)如何去設(shè)置Oracle數(shù)據(jù)庫(kù)的各種診斷事件呢？我們首先來(lái)給設(shè)置診斷事件下一個(gè)簡(jiǎn)單的定義，就是讓Oracle數(shù)據(jù)庫(kù)產(chǎn)生跟蹤信息日志文件。設(shè)置診斷事件有如下的四種方法：ITPUB個(gè)人空間t)R$l 在INIT或者SPFILE初始化文件中設(shè)置ITPUB個(gè)人空間sv8ONy1S6K這種設(shè)置的診斷事件都是針對(duì)于整個(gè)實(shí)例的：ITPUB個(gè)人空間X:O/A4a| s&yevent=event trace name

3、 context forever, level level;ITPUB個(gè)人空間ZJy+xF!A假設(shè)需求設(shè)置多個(gè)診斷事件，可以經(jīng)過(guò)以下兩種方法：ITPUB個(gè)人空間g X|)O,Q*H方法一：運(yùn)用冒號(hào)分隔開(kāi)兩個(gè)診斷事件Anj8F0event = 10248 trace name context forever, level 10:10249 trace name context forever, level 104+NQc7l0mO-p0方法二：運(yùn)用延續(xù)的行設(shè)置診斷事件ITPUB個(gè)人空間vA,dW ;A5E!ZWevent = 10248 trace name context forever, l

4、evel 10ITPUB個(gè)人空間!BQvmGmevent = 10249 trace name context forever, level 10ITPUB個(gè)人空間 p#|W(I/nQC0F,afY z 在當(dāng)前SQL會(huì)話(huà)中設(shè)置N8l#q*SBT&F0針對(duì)整個(gè)實(shí)例的診斷事件的設(shè)置：%?kEX.?zHn0ALTER SYSTEM SET EVENTS event trace name context forever, level level;ITPUB個(gè)人空間W2Ez*y3A5U禁用設(shè)置的診斷事件：ITPUB個(gè)人空間4dwbnFSrALTER SYSTEM SET EVENTS event tra

5、ce name context off;f M-s6TI6nY0針對(duì)當(dāng)前會(huì)話(huà)的診斷事件的設(shè)置：_51K t!vr0ALTER SESSION SET EVENTS event trace name context forever, level level;ITPUB個(gè)人空間z:y)s&TJ禁用設(shè)置的診斷事件：$QZ Zq0ALTER SESSION SET EVENTS event trace name context off;ITPUB個(gè)人空間T4y;l;BU8b| 在另外一個(gè)SQL會(huì)話(huà)中運(yùn)用DBMS_SYSTEM.SETEV存儲(chǔ)過(guò)程設(shè)置ITPUB個(gè)人空間c9k:h%ox.H.KFEXECU

6、TE sys.dbms_system.set_ev(sid, serial#, , , )ITPUB個(gè)人空間k&G#mIQ其中的SID,SERIAL#都是從視圖V$SESSION中獲得的。G4tMunkQ)S0 在另外一個(gè)會(huì)話(huà)中運(yùn)用debug工具設(shè)置cR D5T7J&JW0對(duì)一個(gè)進(jìn)程設(shè)置診斷事件：8%Tv &qCQ/R+3g4B#xR0ORADEBUG EVENT event TRACE NAME CONTEXT FOREVER, LEVEL levelITPUB個(gè)人空間%nN-j;h!cbL$?禁用設(shè)置的診斷事件：ITPUB個(gè)人空間iTIM3hfORADEBUG EVENT event TR

7、ACE NAME CONTEXT OFFITPUB個(gè)人空間&h s/ow$B9wYM對(duì)一個(gè)會(huì)話(huà)設(shè)置診斷事件：ITPUB個(gè)人空間xz*WRORADEBUG SESSION_EVENT event TRACE NAME CONTEXT FOREVER, LEVEL level0Xs;qyb0禁用設(shè)置的診斷事件：)nnf4ct r0ORADEBUG SESSION_EVENT event TRACE NAME CONTEXT OFF注： 在Oracle8i以上的版本中，是運(yùn)用sysdba權(quán)限的用戶(hù)登陸sqlplus后執(zhí)行ORADEBUG命令；在Oracle7.3/8.0的版本中， 是運(yùn)用intern

8、al用戶(hù)登陸svrmgrl后執(zhí)行ORADEBUG命令；在更早的Oracle版本中運(yùn)用ORADBX (ORAMBX在VMS系統(tǒng)上)。由于oradebug允許在另外的會(huì)話(huà)中設(shè)置診斷事件，這樣就可以跟蹤一些平常不太trace的會(huì)話(huà)，例如對(duì) export工具的診斷。診斷事件可以分成會(huì)話(huà)級(jí)的診斷事件和進(jìn)程級(jí)的診斷事件，進(jìn)程級(jí)的診斷事件是可以在INIT初始化參數(shù)文件中設(shè)定，會(huì)話(huà)級(jí)的診斷事 件那么可以運(yùn)用alter session.或者alter system .命令來(lái)設(shè)定。Oracle數(shù)據(jù)庫(kù)在檢測(cè)診斷事件的時(shí)候都是先檢測(cè)會(huì)話(huà)級(jí)的診斷事件，然后再檢測(cè)進(jìn)程級(jí)的診斷事件。對(duì)于設(shè)置Oracle數(shù)據(jù)庫(kù)的診斷事件都必

9、需遵照一定的語(yǔ)法，例如在會(huì)話(huà)級(jí)別上設(shè)置診斷事件可以按照以下的語(yǔ)法來(lái)設(shè)置：;)JKk4Yt0alter session set events 10181 trace name context forever, level 1000;ITPUB個(gè)人空間7uD4q*s;y6q而同樣的診斷事件在INIT初始化參數(shù)文件中就應(yīng)該按照以下語(yǔ)法設(shè)置：4NS, zCr9k0event=10181 trace name context forever, level 1000ITPUB個(gè)人空間y$rz6Jz*Z|e在INIT初始化參數(shù)文件中設(shè)置診斷事件的時(shí)候，普通來(lái)說(shuō)最好在診斷事件后加上相關(guān)的注釋?zhuān)⑨尩膬?nèi)容普通來(lái)

10、說(shuō)應(yīng)該包括診斷事件的作用、為什么要運(yùn)用這個(gè)診斷事件以及設(shè)置診斷事件的時(shí)間。ITPUB個(gè)人空間&Ls.n2eT9Rr?Nx-X2#k下面這個(gè)圖是關(guān)于設(shè)置診斷事件的語(yǔ)法表：ITPUB個(gè)人空間#D8V8M-v,TbbxJO E*M!i*pj0診斷事件規(guī)定的語(yǔ)法為：ITPUB個(gè)人空間fD_)FwB:*qoh0VX%0Event Name:它代表關(guān)聯(lián)事件的符號(hào)名或者是一個(gè)事件號(hào)。假設(shè)是immediate，代表是一個(gè)立刻無(wú)條件的診斷事件，不用去等待任何人發(fā)布它；也可以是指定的Oracle錯(cuò)誤號(hào)碼，還可以是詳細(xì)的事件名。RvI_#ie4?4U P0Action：分為和。Action Key Word的值可以

11、是trace、debugger、crash，而qualifiers的語(yǔ)法那么是依賴(lài)于詳細(xì)的Action。ITPUB個(gè)人空間qe2f t:T,P 當(dāng)為crash的時(shí)候，語(yǔ)法為：ITPUB個(gè)人空間y2|nY)_?S;f_ (默以為空)|off (在等待事件中禁用crash)| aftertimes (發(fā)生此事件N次后crash)mw&K)L %zN/uhi;As0 當(dāng)為debugger的時(shí)候，語(yǔ)法為：rO6O)Nx!G0 (默以為空)| off (在等待事件中禁用debugger)| aftertimes (發(fā)生此事件N次后debugger)| forever (一旦開(kāi)場(chǎng)debugger,以后每次

12、發(fā)惹事件時(shí)都要debugger)| lifetime (一旦開(kāi)場(chǎng)debugger,以后N次發(fā)惹事件時(shí)都要debugger，然后在此診斷事件中禁用debugger)b#DXHrH0 當(dāng)為trace的時(shí)候，語(yǔ)法為：L7mWA4T&q5sH0name ,*ITPUB個(gè)人空間K6A8Vk T9pTrace Name:是關(guān)聯(lián)內(nèi)部trace號(hào)的符號(hào)名。其中，context是一種特殊的trace name，它不會(huì)去調(diào)用調(diào)試dump操作，但是卻會(huì)前往給發(fā)起診斷事件者能否context跟蹤被激活，跟蹤是什么級(jí)別的。跟蹤的級(jí)別是指dump程序內(nèi) 部運(yùn)用來(lái)控制dump出來(lái)詳細(xì)信息的級(jí)別，通常來(lái)說(shuō)，級(jí)別越高，dump

13、出來(lái)的信息就會(huì)越詳細(xì)，最低級(jí)別是1。All是另外一種特殊的trace name，它意味著經(jīng)過(guò)ksdtradv宏在編譯的時(shí)候聲明一切的trace names。假設(shè)在診斷事件中關(guān)聯(lián)多余一個(gè)以上的trace，至少有一個(gè)應(yīng)該是context，相應(yīng)的，診斷事件中最后一個(gè)關(guān)聯(lián)的動(dòng)作將前往跟蹤的級(jí)別， 而且在不同的調(diào)用中診斷事件號(hào)最好獨(dú)一。ITPUB個(gè)人空間!4Vp L2kWtrace qualifier的語(yǔ)法為：ITPUB個(gè)人空間,tz;K-L R*B4DWq(默以為空)|off(在等待事件中禁用這個(gè)trace)| after times (發(fā)生此事件N次后開(kāi)場(chǎng)trace)|forever (一旦激活tr

14、ace,以后每次發(fā)惹事件時(shí)都要trace)| lifetime (一旦開(kāi)場(chǎng)trace,以后N次勝利發(fā)惹事件時(shí)都要trace，然后在此診斷事件中禁用trace)| level (當(dāng)trace第一次被激活，設(shè)置初始化級(jí)別為N，之后激活的trace的級(jí)別那么由trace type來(lái)決議)|type (如何修正以后激活的trace的級(jí)別)l6HRv2e7wR0trace type：ITPUB個(gè)人空間F2E2mHq*i;increment 升高級(jí)別直至最高xvCqg9_2Q0decrement 降低級(jí)別到0并且禁用VfQIh?+C0constant 堅(jiān)持級(jí)別不變ITPUB個(gè)人空間xK(bLmJ$bh:i

15、此外，對(duì)于trace的指定，假設(shè)設(shè)置診斷事件是immediate，那么意味著trace將不會(huì)等待診斷事件，在trace qualifier中只需求設(shè)置trace的級(jí)別，lifetime默以為1。對(duì)于設(shè)置診斷事件，Oracle數(shù)據(jù)庫(kù)提供了四個(gè)跟蹤信息的類(lèi)別可以供我們來(lái)運(yùn)用：ITPUB個(gè)人空間1ij5Cl eUhW)hm1G 類(lèi)別一：Dump SomethingITPUB個(gè)人空間t7Mudw9l!Z-h這個(gè)類(lèi)別的Trace文件是無(wú)條件立刻生成的，普通都是dump出Oracle數(shù)據(jù)庫(kù)的數(shù)據(jù)，例如查看重做日志文件的頭或者是查看控制文件中的內(nèi)容等。這類(lèi)的診斷事件是不可以在INIT或者SPFILE的初始化

16、參數(shù)文件中指定的。ITPUB個(gè)人空間 Kc&kh&PfWXB 類(lèi)別二：Trap on Error3C/dLN w-sqO0這個(gè)類(lèi)別的診斷事件是讓Oracle每次生成一個(gè)errorstack的錯(cuò)誤信息的trace文件。!r1dM8r;V ed0 類(lèi)別三：Change execution pathITPUB個(gè)人空間IFdA(T這個(gè)類(lèi)別的診斷事件主要是用于修正某些代碼段的可執(zhí)行途徑。例如，設(shè)置診斷事件10269就可以讓Oracle數(shù)據(jù)庫(kù)的后臺(tái)SMON進(jìn)程不再進(jìn)展自在空間的重組的操作。:P2Q5cb9I .r0 類(lèi)別四：Trace somethingITPUB個(gè)人空間l9CFZJ&vv這個(gè)類(lèi)別的診斷事

17、件主要是用于某種特殊的目的而需求獲取相應(yīng)的trace信息，例如對(duì)sql調(diào)優(yōu)。最常見(jiàn)的診斷事件10046就是讓Oracle數(shù)據(jù)庫(kù)去跟蹤每條執(zhí)行的sql語(yǔ)句的訪(fǎng)問(wèn)途徑。ITPUB個(gè)人空間H:gx/T*|每種類(lèi)別的診斷事件都有一種或者多種級(jí)別，級(jí)別有以下四種表現(xiàn)方式：ITPUB個(gè)人空間P#W_dF*uJ Range，例如從1到10ITPUB個(gè)人空間%;p!kPu5K:W)_:Q&bY bitmask 例如0 x01 0 x02 0 x04 0 x08 0 x10+okd_Tk0 flag 例如0代表off，1代表onITPUB個(gè)人空間7rXpn_#$u&Fk identifier 例如object

18、id, memory address等等在設(shè)置運(yùn)用各種診斷事件的時(shí)候，有一些事項(xiàng)是需求留意的：Z;L/8T mz!GC|0 確定運(yùn)用的診斷事件對(duì)于當(dāng)前的Oracle數(shù)據(jù)庫(kù)版本是合法的：由于對(duì)于不同版本的Oracle數(shù)據(jù)庫(kù)來(lái)說(shuō)，診斷事件的含義和用法都有所不同。ITPUB個(gè)人空間8e*_R0J 確定運(yùn)用的診斷事件允許設(shè)定的級(jí)別，在很多時(shí)候設(shè)定的級(jí)別不同是會(huì)影響到診斷事件所代表的行為的。.M wSJ q$u e&z8u?0 在INITSID.ORA文件中設(shè)置的任何診斷事件，假設(shè)Oracle數(shù)據(jù)庫(kù)需求晉級(jí)，一定要提早注釋或者取消。ITPUB個(gè)人空間C+W&jpr9WITPUB個(gè)人空間 #HC7p1C大

19、部分的診斷事件的數(shù)值都是在10000至10999范圍內(nèi)，運(yùn)用如下的腳本可以查看到一切的診斷事件：ITPUB個(gè)人空間Q;mqguMsw1DSET SERVEROUTPUT ON9N&lk0ZIo0DECLARE ITPUB個(gè)人空間U,P&RO:Merr_msg VARCHAR2(120);T-s!I&_h0S0iq#VH0BEGINITPUB個(gè)人空間)I*s!Ef4j3in_u-|dbms_output.enable (1000000);ITPUB個(gè)人空間1O%BL*u2Ck1FOR err_num IN 10000.10999ITPUB個(gè)人空間*mW Y HvLmSLOOP#hn8t.QZO-

20、O0err_msg := SQLERRM (-err_num);pCJf.N&y0IF err_msg NOT LIKE %Message |err_num| not found% THEN.Gd ?*V2_,K)R)l/0dbms_output.put_line (err_msg);ITPUB個(gè)人空間b|L1F6u.iEND IF;Fm8q#w7UX3X+_0END LOOP;HC%f*N)oAX0END;OO8w7yMOq%h0/ITPUB個(gè)人空間Y6?4|%C6SX+#U在UNIX系統(tǒng)中，可以在$ORACLE_HOME/rdbms/mesg/oraus.msg這個(gè)文件中找到一切的診斷事件

21、的稱(chēng)號(hào)和定義。運(yùn)用如下腳本可以輸出一切的詳細(xì)的診斷事件的信息：ITPUB個(gè)人空間%_5Acu/r Pevent=10000*W A%q%ayP$m!U0while $event -ne 10999 pc;Z rEkbr0doITPUB個(gè)人空間gov4Z4Cevent=expr $event + 12v/*K5Km0O8N0oerr ora $eventITPUB個(gè)人空間,#V a4Z0Av%$Vdone運(yùn)用如下腳本可以檢查當(dāng)前會(huì)話(huà)中設(shè)置了哪些診斷事件：W%Y/BM G:i0SET SERVEROUTPUT ONi-?HF_rP0DECLAREITPUB個(gè)人空間 &gmC)L)g#kl_leve

22、l NUMBER;ITPUB個(gè)人空間FZ72A&zL wBEGINITPUB個(gè)人空間$SkoEBIFOR l_event IN 10000.10999ITPUB個(gè)人空間9a6sVsT,r7uFLOOP!h0Bnl)B(0dbms_system.read_ev (l_event,l_level);9g1T,pA*d3C0IF l_level 0 THENca,O+%x E0dbms_output.put_line (Event |TO_CHAR (l_event)|*d%Gp0r0,DP0 is set at level |TO_CHAR (l_level);r-WQ$aqk6YC0END IF

23、;ITPUB個(gè)人空間y)b!MU,QEND LOOP;ITPUB個(gè)人空間 1EkU-d,X Yh2R9mEND;ITPUB個(gè)人空間k#v0fZ#s2J;RB/大部分的診斷事件的數(shù)值都是在10000至10999范圍內(nèi)，運(yùn)用如下的腳本可以查看到一切的診斷事件：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 %M

24、essage |err_num| not found% THEN dbms_output.put_line (err_msg); END IF; END LOOP; END; /ORA-10000: control file debug event, name control_file ORA-10001: control file crash event1 ORA-10002: control file crash event2 ORA-10003: control file crash event3 ORA-10004: block recovery testing - internal

25、error ORA-10005: trace latch operations for debugging ORA-10006: block recovery testing - external error ORA-10007: log switch debug crash after new log select, thread ORA-10008: log switch debug crash after new log header write, thread ORA-10009: log switch debug crash after old log header write, t

26、hread ORA-10010: Begin Transaction ORA-10011: End Transaction ORA-10012: Abort Transaction ORA-10013: Instance Recovery ORA-10014: Roll Back to Save Point ORA-10015: Undo Segment Recovery ORA-10016: Undo Segment extend ORA-10017: Undo Segment Wrap ORA-10018: Data Segment Create ORA-10020: partial li

27、nk restored to linked list (KSG) ORA-10021: KST event to trace control file header writes and reads ORA-10022: trace ktsgsp ORA-10023: Create Save Undo Segment ORA-10024: Write to Save Undo ORA-10026: Apply Save Undo ORA-10027: Specify Deadlock Trace Information to be Dumped ORA-10028: Dump trace in

28、formation during lock / resource latch cleanup ORA-10029: session logon (KSU) ORA-10030: session logoff (KSU) ORA-10031: sort debug event (S*) ORA-10032: sort statistics (SOR*) ORA-10033: sort run information (SRD*/SRS*) ORA-10035: Write parse failures to alert log file ORA-10036: create remote row

29、source (QKANET) ORA-10037: allocate remote row source (QKARWS) ORA-10038: dump row source tree (QBADRV) ORA-10039: type checking (OPITCA) ORA-10041: dump undo records skipped ORA-10043: check consistency of owner/waiter/converter lists in KSQ ORA-10044: free list undo operations ORA-10045: free list

30、 update operations - ktsrsp, ktsunl ORA-10046: enable SQL statement timing ORA-10047: trace switching of sessions ORA-10048: Undo segment shrink ORA-10049: protect library cache memory heaps ORA-10050: sniper trace ORA-10051: trace OPI calls ORA-10052: dont clean up obj$ ORA-10053: CBO Enable optimi

31、zer trace ORA-10056: dump analyze stats (kdg) ORA-10057: suppress file names in error messages ORA-10058: use table scan cost in tab$.spare1 ORA-10059: simulate error in logfile create/clear ORA-10060: CBO Enable predicate dump ORA-10061: disable SMON from cleaning temp segment ORA-10062: disable us

32、age of OS Roles in osds ORA-10063: disable usage of DBA and OPER privileges in osds ORA-10064: thread enable debug crash level , thread ORA-10065: limit library cache dump information for state object dump ORA-10066: simulate failure to verify file ORA-10067: force redo log checksum errors - block n

33、umber ORA-10068: force redo log checksum errors - file number ORA-10070: force datafile checksum errors - block number ORA-10071: force datafile checksum errors - file number ORA-10072: protect latch recovery memory ORA-10073: latch cleanup tracing ORA-10074: default trace function mask for kst ORA-

34、10075: CBO Disable outer-join to regular join conversion ORA-10076: CBO Enable cartesian product join costing ORA-10077: CBO Disable view-merging optimization for outer-joins ORA-10078: CBO Disable constant predicate elimination optimization ORA-10079: trace data sent/received via SQL*Net ORA-10080:

35、 dump a block on a segment list which cannot be exchanged ORA-10081: segment High Water Mark has been advanced ORA-10082: free list head block is the same as the last block ORA-10084: free list becomes empty ORA-10085: free lists have been merged ORA-10086: CBO Enable error if kko and qka disagree o

36、n oby sort ORA-10087: disable repair of media corrupt data blocks ORA-10088: CBO Disable new NOT IN optimization ORA-10089: CBO Disable index sorting ORA-10090: invoke other events before crash recovery ORA-10091: CBO Disable constant predicate merging ORA-10092: CBO Disable hash join ORA-10093: CBO

37、 Enable force hash joins ORA-10094: before resizing a data file ORA-10095: dump debugger commands to trace file ORA-10096: after the cross instance call when resizing a data file ORA-10097: after generating redo when resizing a data file ORA-10098: after the OS has increased the size of a data file

38、ORA-10099: after updating the file header with the new file size ORA-10100: after the OS has decreased the size of a data file ORA-10102: switch off anti-joins ORA-10103: CBO Disable hash join swapping ORA-10104: dump hash join statistics to trace file ORA-10105: CBO Enable constant pred trans and M

39、Ps w WHERE-clause ORA-10106: CBO Disable evaluating correlation pred last for NOT IN ORA-10107: CBO Always use bitmap index ORA-10108: CBO Dont use bitmap index ORA-10109: CBO Disable move of negated predicates ORA-10110: CBO Try index rowid range scans ORA-10111: Bitmap index creation switch ORA-10

40、112: Bitmap index creation switch ORA-10113: Bitmap index creation switch ORA-10114: Bitmap index creation switch ORA-10115: CBO Bitmap optimization use maximal expression ORA-10116: CBO Bitmap optimization switch ORA-10117: CBO Disable new parallel cost model ORA-10118: CBO Enable hash join costing

41、 ORA-10119: QKA Disable GBY sort elimination ORA-10120: generate relative file # different from absolute ORA-10121: CBO Dont sort bitmap chains ORA-10122: Disable transformation of count(col) to count(*) ORA-10124: Force creation of segmented arrays by kscsAllocate ORA-10125: Disable remote sort eli

42、mination ORA-10126: Debug oracle java xa ORA-10127: Disable remote query block operation ORA-10128: Dump Partition Pruning Information ORA-10129: Alter histogram lookup for remote queries ORA-10130: sort disable readaheads ORA-10132: dump plan after compilation ORA-10133: testing for SQL Memory Mana

43、gement ORA-10134: tracing for SQL Memory Management for session ORA-10: CBO do not count 0 rows partitions ORA-10: CBO turn off fix for bug 1089848 ORA-10: CBO turn off fix for bug 1344111 ORA-10: CBO turn off fix for bug 1577003 ORA-10: CBO turn off fix for bug 6119 ORA-10140: CBO turn off fix for

44、bug 1332980 ORA-10141: CBO disable additional keys for inlist in bitmap optimization ORA-10142: CBO turn off advanced OR-expansion checks ORA-10143: CBO turn off hints ORA-10144: CBO turn off cost based selection of bji over bsj subquery ORA-10145: test auditing network errors ORA-10146: enable Orac

45、le TRACE collection ORA-10147: enable join push through UNION view ORA-10149: allow the creation of constraints with illegal date constants ORA-10150: import exceptions ORA-10152: CBO dont consider function costs in plans ORA-10153: Switch to use public synonym if private one does not translate ORA-

46、10154: Switch to disallow synonyms in DDL statements ORA-10155: CBO disable generation of transitive OR-chains ORA-10156: CBO disable index fast full scan ORA-10157: CBO disable index access path for in-list ORA-10158: CBO preserve predicate order in post-filters ORA-10159: CBO disable order-by sort

47、 pushdown into domain indexes ORA-10160: CBO disable use of join index ORA-10161: CBO recursive semi-join on/off-switch ORA-10162: CBO join-back elimination on/off-switch ORA-10163: CBO join-back elimination on/off-switch ORA-10164: CBO disable subquery-adjusted cardinality fix ORA-10165: mark sessi

48、on to be aborted during shutdown normal ORA-10166: trace long operation statistics updates ORA-10167: CBO use old index MIN/MAX optimization ORA-10168: CBO disable single-table predicate predicate generation ORA-10169: CBO disable histograms for multi partitions ORA-10170: CBO use old bitmap costing

49、 ORA-10171: CBO disable transitive join predicates ORA-10172: CBO force hash join back ORA-10173: Dynamic Sampling time-out error ORA-10174: view join-back elimination switch ORA-10175: CBO star transformation switch ORA-10176: CBO colocated join switch ORA-10177: CBO colocated join switch ORA-10178

50、: CBO turn off hash cluster filtering through memcmp ORA-10179: CBO turn off transitive predicate replacement ORA-10180: temp table transformation print error messages ORA-10181: CBO disable multi-column in-list processing ORA-10182: CBO disable generation of implied predicates ORA-10183: CBO disabl

51、e cost rounding ORA-10184: CBO disable OR-exp if long inlist on bitmap column ORA-10185: CBO force index joins ORA-10186: CBO disable index join ORA-10187: CBO additional index join switch ORA-10188: CBO additional index join switch ORA-10189: CBO turn off FFS null fix ORA-10190: Analyze use old fre

52、quency histogram collection and density ORA-10191: Avoid conversion of in-lists back to OR-expanded form ORA-10192: nopushdown when number of groups exceed number of rows ORA-10193: Force repeatable sampling with specified seed ORA-10194: CBO disable new LIKE selectivity heuristic ORA-10195: CBO don

53、t use check constraints for transitive predicates ORA-10196: CBO disable index skip scan ORA-10197: CBO force index skip scan ORA-10199: set parameter in session ORA-10200: consistent read buffer status ORA-10201: consistent read undo application ORA-10202: consistent read block header ORA-10203: bl

54、ock cleanout ORA-10204: signal recursive extend ORA-10205: row cache debugging ORA-10206: transaction table consistent read ORA-10207: consistent read transactions status report ORA-10208: consistent read loop check ORA-10209: enable simulated error on control file ORA-10210: check data block integr

55、ity ORA-10212: check cluster integrity ORA-10213: crash after control file write ORA-10214: simulate write errors on control file ORA-10215: simulate read errors on control file ORA-10216: dump control file header ORA-10217: debug sequence numbers ORA-10218: dump uba of applied undo ORA-10219: monit

56、or multi-pass row locking ORA-10220: show updates to the transaction table ORA-10221: show changes done with undo ORA-10222: row cache ORA-10223: transaction layer - turn on verification codes ORA-10224: index block split/delete trace ORA-10225: free/used extent row cache ORA-10226: trace CR applica

57、tions of undo for data operations ORA-10227: verify (multi-piece) row structure ORA-10228: trace application of redo by kcocbk ORA-10229: simulate I/O error against datafiles ORA-10231: skip corrupted blocks on _table_scans_ ORA-10232: dump corrupted blocks symbolically when kcbgotten ORA-10233: ski

58、p corrupted blocks on index operations ORA-10234: trigger event after calling kcrapc to do redo N times ORA-10235: check memory manager internal structures ORA-10236: dump redo on object no. or block type mismatch errors 1410/8103 ORA-10237: simulate C (for testing purposes) ORA-10238: instantiation

59、 manager ORA-10239: multi-instance library cache manager ORA-10240: dump dbas of blocks that we wait for ORA-10241: remote SQL execution tracing/validation ORA-10242: suppress OER 2063 (for testing distrib w/o different error log) ORA-10243: simulated error for test of K2GTAB latch cleanup ORA-10244

60、: make tranids in error msgs print as 0.0.0 (for testing) ORA-10246: print trace of PMON actions to trace file ORA-10247: Turn on scgcmn tracing. (VMS ONLY) ORA-10248: turn on tracing for dispatchers ORA-10249: turn on tracing for multi-stated servers ORA-10250: Trace all allocate and free calls to