Intermediate SQL Color Coded SQL, UNIX and Database Essays


How AIX Paging Space works. Part 1: Why your program memory footprint gets bloated sometimes

If you recall AIX memory saga from my previous “AIX memory” posts (Process memory, SGA Memory), one of the points was that during the lifetime of the process (or shared memory segment) at any given moment each allocated memory page could reside in one of the two places:

  • Either the page is located in a physical RAM
  • OR the page is located in paging space

In memory location is, obviously, preferred. If I was a memory page I would WANT to be there đŸ™‚ In paging space ? – not so much, but, of course I could be forced there if I’m not popular enough and AIX needs memory for other things.


ORACLE 11g XML alert logs. Surprise: They are actually more convenient to work with

I have to admit, I was initially very skeptical about ORACLE 11g Automated Diagnostic Repository or ADR.

Why do I need to use “special” tool to access database alert log ? (and not vi) Who decided to move trace directories to some weird location ?? (why not keep them where they’ve always been?) Why store alert records as XML ??!! (it is meant for humans, you know …)

These things have “inconvenience” and “pain in the a%%.” written all over them … And, of course, the usual ORACLE attitude: “we decided to change it, so suck it up and learn how it works” did not help much …

Old habits die hard, but lately, I’ve started to come around using ADR. It turns out that with a bit of adrci knowledge and a few tweaks in the environment, working with alert logs from a regular UNIX shell becomes not only manageable but actually (gulp!) much more convenient …