Skip to main content

UNIX Command Reference for DBAs

A 68,000-line command reference for Solaris, AIX, HP-UX and Linux, converted from a plain text file into navigable Markdown. Download link at the bottom.

What it is

Albert van der Sel compiled UNIX command examples over years of DBA work — commands for Oracle, DB2 and SQL Server administrators who have to keep the box underneath the database alive. Version 115 is dated 2009. I have been carrying the text file around since, adding to it.

The problem with the original is not the content. It is that 2.8 MB of plain text with no structure is only usable through Ctrl+F, and only if you already know the exact string you are looking for.

So I converted it. Headings are real headings now, command listings are fenced code blocks, and there is a table of contents with 207 entries at the top. You can scroll it, link into it, and read it on a phone.

What is in it

Memory, swap and CPU inspection on five platforms, side by side. Mount and NFS. Permissions, sticky bit, SETUID. find, crontab, job control. Backup with tar, cpio, dd, compress, gzip. Filesystems and volume management. Network troubleshooting. Error code references for IBM LPARs and partition firmware. Solaris error messages. Shell scripting patterns.

It is the kind of document that answers "how do I check physical memory on HP-UX again" in four seconds instead of four minutes.

What it is not

It is not maintained and it is not modern. The core of it predates systemd, predates most of what you run in a container, and some of the AIX and Tru64 material describes machines you will never touch.

That does not make it useless. Legacy UNIX is exactly the place where you cannot guess the syntax and cannot find a decent answer online, because nobody has blogged about lsattr -E -l sys0 in fifteen years. The value of an old reference is highest precisely where the systems are old.

Treat every command as something to verify on your own box before you run it in production. Especially the ones that write.

Download

unix-command-reference.md — 2.7 MB, Markdown, UTF-8.

Your browser will probably open it as plain text rather than download it. Right-click the link and save it instead, or grab it from the terminal:

curl -O https://raw.githubusercontent.com/Patriarcha/notes/main/unix-command-reference.md

Content is unchanged from the original — I fixed the character encoding and added structure, nothing else. It is too large for GitHub to render in the browser, so read it in your own editor.

Credit where it belongs: this is Albert van der Sel's work. I converted the format.

Comments

Popular posts from this blog

Diskless server iSCSI boot disk XCP-NG installation

 For Cisco UCS chassis, eg. 5108 for installation it's required to set FC or iSCSI disk for boot ( boot disk ). They are called diskless servers. Unfrtunatelly XCP-NG - 8.2.1 Jan 2025 - in my case cannot boot as it is from iSCSI. Here is a guide, how to do it.

AI's Democratic Era Ended in April 2026

For about three years, every big AI lab behaved like a teenager with a new car. Look what mine can do. Look at my benchmark. Look at my context window. Every few weeks somebody published a chart where their bar was taller than everybody else's bar, and we all went along with it, because the bars kept getting taller and the models kept getting better and it was fun to watch. Meanwhile China said almost nothing. Then once in a while DeepSeek dropped something that knocked everyone off their feet, everyone spent a week arguing about training costs, and the noise started again. That era is over. It ended in April 2026, and I don't think we noticed how completely. The race we thought we were in The mental model everybody used was Formula 1. Whoever builds the fastest car wins the season. Speed was the whole point, and speed was something you showed off, because showing off is how you raise the next round. Some people preferred the Manhattan Project comparison. I used to think that o...

Replacing a failing disk in AIX rootvg

A disk in a mirrored rootvg is the one disk you cannot just pull. It holds the boot image, it probably holds the primary dump device, and half of every logical volume on the system lives on it. Pull it without preparation and reducevg refuses, or worse, the machine comes up on nothing after the next reboot. This is the full sequence for a two-disk mirrored rootvg on AIX, replacing hdisk0 . Non-root volume groups are much simpler and I have noted the difference at the end. Decide whether you actually have a problem Disks rarely die cleanly. They complain first, and the complaints show up in the error log: errpt | more 1581762B 0727203502 T H hdisk0 DISK OPERATION ERROR 1581762B 0727203502 P H hdisk0 DISK OPERATION ERROR The third column is the one that matters. T is temporary, P is permanent. A single temporary error on a busy system is noise. A cluster of them over a few hours is a drive on its way out. A permanent error is not a warning, it is a report of ...