

Twice a year I fill in as DBA when our lady graybeard Oracle DBA takes vacation. This month is one of those times. Yay me.
For my org, it’s just the massive in-house developed line-of-business application that’s tightly coupled to Oracle that keeps us chained to it. It’s technical debt from top to bottom, and has been accumulating steadily since the early 2010s, but no one seems willing to start replacing it.
The new projects typically go with Postgres, MariaDB, or if all else fails, MSSQL. But the Oracle monster in the closet isn’t likely to leave any time soon.




















Literally this.