Solution : https://service.sap.com/sap/support/notes/613872 (SAP Service marketplace login required)
Summary :
This SAP Note discusses the use of the ORADEBUG tool in SQLPLUS from Oracle 8.1 for tracing Oracle processes. Users with SYSDBA authorization can initiate various trace activities such as session traces, system state dumps, and process state analysis. The traces are saved in $SAPDATA_HOME/saptrace/usertrace, requiring checks for sufficient disk space. Trace levels and actions include SQL tracing, adding bind variables, and capturing wait events. Tracing must be carefully planned to ensure performance and data management, including remembering to deactivate traces and manage trace file sizes effectively.
Key words :
subareas 0-0 total size 000000000006ead0 minimum subarea size 00000000 area subarea shmid stable addr actual addr 0 0 11665408 0x00000050000000 0x00000050000000 subarea size segment size 000000000006f000 0000000064400000 area #1 `variable size', subareas 2-2 total size 000000002d000000 minimum subarea size 01000000 area subarea shmid stable addr actual addr 1 2 11665408 0x00000086912000 0x00000086912000 subarea size segment size 000000002d6ee000 0000000064400000, nam='db file sequential read' ela= 179 p1=265 p2=58380 p3=1, nam='<wait_event>' ela=0 p1=0 p2=0 p3=0 nam, area #0 `fixed size', oradebug setmypidoradebug unlimitoradebug dump systemstate 10oradebug tracefile_name, oradebug setmypidoradebug ipcoradebug tracefile_name shared memory, oradebug dump errorstack 1oradebug tracefile_name alternatively, control files / data files / redo logs 9, sskgxpt 0xad96338 flags sskgxpt_readpending info
Related Notes :
| 805934 | FAQ: Database time |
| 766349 | FAQ: Oracle SQL optimization |
| 712624 | High CPU consumption by Oracle |
| 654176 | Analyzing Oracle trace files with TKPROF |
| 633914 | Error when executing DBMS_STATS |
| 619188 | FAQ: Oracle wait events |
| 521264 | Hang situations |
| 502782 | Composite SAP Note ora-4030 |