|
| Finding pipe name | 12 April 1999 |
| If a session is waiting on a pipe get event, how can you identify the name of the pipe being waited upon? | ||
 | The parameter P1 in V$SESSION_WAIT is the library cache object handle address for the pipe. You can join this to X$KGLOB.KGLHDADR and then take the name from KGLNAOBJ. |
|
| X$ tables | 20 January 2000 |
I was looking at the X$ tables listed in V$FIXED_TABLE
and noticed that while most have a unique TABLE_NUM in the range 0..246 the following group all share the number 65537.
NAME TABLE_NUM ------------------------------ ---------- X$KCVFHONL 65537 X$KCVFHMRR 65537 X$KCVFHALL 65537 X$KGLTABLE 65537 X$KGLBODY 65537 X$KGLTRIGGER 65537 X$KGLINDEX 65537 X$KGLCLUSTER 65537 X$KGLCURSOR 65537Can you please explain what this TABLE_NUM is, and what does this mean exactly? | ||
| That TABLE_NUM indicates that despite the X$ in their name, these are in fact fixed views, like the V$ views, rather than fixed tables. |
|
| X$KSMLRU | 1 March 2000 |
| Where can I find information about the X$ tables? The one I need a description of is X$KSMLRU. | ||
| There is a note on MetaLink called "Library Cache and Shared Pool Tuning" that contains a description. However, it is not exactly as that note describes, because only the largest chunk allocation is guaranteed to be captured, as my book explains. The other 9 rows should be taken with a pinch of salt. I actually tried to log a bug about it, and got an email back from the responsible developer. He outlined his algorithm in pseudo-code, and explained that it works exactly as he intended. That is, he felt that the note was in error in describing his X$. |
| Copyright © Ixora Pty Ltd |
|