In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-21 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Oracle internal event numbers are often used to track the state of the system. How to use these internal event numbers requires events and experience. Only these commonly used internal event numbers are recorded here to prepare for work.
1. 10013: used to monitor transaction recovery
2. 10015: dump the UNDO SEGMENT header
Event = "10015 trace name context forever"
3. 10029: used to give login information during the session
4. 10030: used to give logout information during the session
5. 10032: statistics of dump sort
6. 10033: statistics on the growth of dump sorting
7. 10045: track Freelist management operations
8. 10046: trace SQL statements
Alter session set events' 10046 trace name context forever, level 4 variables;-- tracks SQL statements and displays binding variables
Alter session set events' 10046 trace name context forever, level 8 minutes;-- tracks SQL statements and displays wait events
9. 10053: dump optimization strategy
10, 10059: simulate creation and cleanup errors in redo logs
11, 10061: prevent the SMON process from clearing temporary segments at startup
12, 10079: dump SQL*NET statistics
13, 10081: dump high water mark change
14, 10104: dump Hash connection statistics
15. 10128: dump partition rest and recuperation information
16, 10200: dump consistent read information
17. 10201: Undo application in dump consistency reading
18, 10209: allow errors to be simulated in control files
19, 10210: triggers a block check event
Event = "10210 trace name context forever, level 10"
20, 10211: trigger index check event
21, 10213: the simulation crashes after writing the control file
22, 10214: simulate write errors in the control file
Levelnumber from 1 to 9 indicates the block number that caused the error. If it is greater than or equal to 10, each control file will make an error.
23, 10215: simulation of read errors in control files
24, 10220: dump Undo header changes
25,10221; dump Undo changes
26, 10224: separation and deletion of dump indexes
27, 10225: dump changes in intervals based on dictionary management
28, 10229: imitate the Icano error on the data file
29, 10231: set to ignore corrupted blocks during a full table scan
Alter session set events' 10231 trace name context off';-turns off block checking during a session
Event = "10231 trace name context forever, level 10"-- checks the blocks of data that any process reads into SGA
30, 10232: dump blocks that are set to soft corruption (when DBMS_REPAIR package setting or DB_BLOCK_CHECKING is TRUE) to the trace file
31, 10235: for memory heap check
Alter session set events' 10235 trace name context forever, level 1'
32, 10241: dump remote SQL execution
33, 10246: track the PMON process
34, 10248: track the dispatch process
35, 10249: track the MTS process
36, 10252: analog write data file header error
37, 10253: error simulating writing redo log file
38, 10262: memory leaks when connections are allowed
Alter session set events' 10262 trace name context forever, level 300 bytes;-- allows for memory leaks of 300 bytes
39, 10270: dump shared cursors
40, 10285: simulation control file header damage
41, 10286: simulation control file open error
42, 10287: simulation archiving error
43, 10357: debug the direct path mechanism
44, 10500: track the SMON process
45, 10608: track the creation of bitmap indexes
46, 10704: tracking enqueues
47, 10706: track global enqueues
48, 10708: buffer cache tracking RAC
49, 10710: track access to bitmap indexes
50, 10711: track bitmap index merge operations
51, 10712: track bitmap index OR operations
52, 10713: track bitmap index AND operations
53, 10714: track bitmap index MINUS operations
54, 10715: track the conversion of bitmap indexes to ROWID
55, 10716: track the compression and decompression of bitmap indexes
56, 10719: track changes to bitmap indexes
57, 10731: trace cursor declaration
58, 10928: track PL/SQL execution
59, 10938: dump PL/SQL execution statistics
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.