Step into my daily life as a DBA from routine tasks to the awkward gotchas to all of the really cool things that make the oracle database “AMAZING”.
Introduction DML WAIT[NOWAIT], introduced in 23.26.2.0.0, helps to specify how long a DML statement should wait to acquire a lock before rolling back the DML statement and returning session control to the user. The general syntax is: You can specify whether to wait forever, not at all or for n seconds, milliseconds or microseconds. The […]
Introduction In a relational database, defining constraints can help ensure data integrity, improve data consistency, enhance SQL query performance, and, in the case of foreign keys, ensure referential integrity. I talk a lot more about constraints in a previous post about database constraints. In a separate post, I also talk about locks and transaction concurrency
Imagine that at your local superstore(Walmart, Target, etc.), when you got to the parking lot, you had to get a number and wait till you got called to proceed into the store to do your shopping(however long that takes) and then leave, consequently freeing up space for the next person to come in. This sounds
INTRODUCTION I was recently confronted with an error ORA-01502 error. This occurred as I was attempting to perform a DML operation on a table. Initially, I was surprised but after some digging I managed to get to the bottom of the issue. Here’s what happened. SETUP Firstly, we create a sample table, create a unique
A bit of Background I have been reading a lot about autoupgrade. I see lots of oracle technologists talking about it on their blogs and videos and they recommend it. Having got tired of watching from the sidelines, wondering what all the fuzz is about and also due to my own enormous FOMO, I decided
Most data problems don’t come from bad SQL — they come from bad assumptions. And the worst one is believing that constraints can be “handled in the application.” They can’t. They never could. The moment data is touched by an ETL job, a script, an integration, a migration, or a future rewrite, every application‑level rule evaporates. The database is the only place where integrity actually persists. Datatypes, keys, foreign keys, checks, and assertions aren’t optional features — they’re the backbone of reliable systems. If the data matters, the constraints belong in the database. Full stop.
Everyone has a pattern or writing style when it come to SQL I’ve noticed. Some people use uppercase for keywords other people don’t, some start a column on a new line others don’t, people format differently, leaving commas at the end of the line vs at the beginning and many more niche ways people write.
Services or Service names in Oracle specify one or more names that clients can use to connect to an Oracle Database. It is a logical representation of a database. When an instance starts, it registers itself with the listener using one or more service names. They are a good way of separating various application connections
Introduction As an IT professional, especially one working closely with data, surely, almost definitely, you have been asked a question from the users along the lines of “Can we know what the value was of col1 in the table t1 at 25:00 on Thursday, the 30th of February 8000 years ago?” (Silly, but that’s really
Flashback Data Archive: Recreating History, After The Fact Read More »
Background Story time When I just started working as a DBA, the Senior Database Administrator was taking me through the environment and how everything was set up, including all the servers, databases, applications, and more. He was talking about one of the purchased applications that runs in production, and then explained that the vendor had
