ORASOLU TOOLBOX · AUTOMATION & DEVOPS
Make database delivery repeatable
Database DevOps workflows benefit from the same principles as application delivery: controlled changes, repeatable validation and clear evidence. These examples provide practical checks that can be used in delivery pipelines.
Capture a compact baseline before applying a database change.
SELECT
SYS_CONTEXT('USERENV', 'DB_NAME') AS database_name,
SYS_CONTEXT('USERENV', 'INSTANCE_NAME') AS instance_name,
SYSTIMESTAMP AS captured_at
FROM dual;
Run a post-change check for invalid database objects.
SELECT
owner,
object_type,
COUNT(*) AS invalid_count
FROM dba_objects
WHERE status = 'INVALID'
GROUP BY owner, object_type
ORDER BY owner, object_type;
Check that a table or view exists in the expected owner and state.
SELECT
owner,
object_name,
object_type,
status
FROM dba_objects
WHERE owner = UPPER('&owner')
AND object_name = UPPER('&object_name')
ORDER BY object_type;
Review dependencies that may be affected by a database change.
SELECT
owner,
name,
type,
referenced_owner,
referenced_name,
referenced_type
FROM dba_dependencies
WHERE owner = UPPER('&owner')
ORDER BY name, type;
Check scheduler jobs after a deployment or configuration change.
SELECT
owner,
job_name,
enabled,
state
FROM dba_scheduler_jobs
WHERE owner = UPPER('&owner')
ORDER BY job_name;
Return a simple completion record for a pipeline or deployment log.
SELECT
'COMPLETED' AS result,
SYS_CONTEXT('USERENV', 'DB_NAME') AS database_name,
SYSTIMESTAMP AS completed_at
FROM dual;
ORASOLU TOOLBOX · AUTOMATION & DEVOPS
A database deployment is not complete until it is validated.
Use repeatable pre-checks and post-checks around database changes so deployments can be evaluated consistently instead of relying on manual inspection.