Alter a column and every package, view, and trigger that references it goes INVALID across the schema. A hard reference to what you changed won't recompile at all — the app finds out at the next call with ORA-04068, not at deploy.

Oracle changes aren't just DDL — they're packages, procedures, types, and anonymous BEGIN…END blocks, and an EXECUTE IMMEDIATE can hide DDL inside what reads as one statement. An ungoverned block runs whatever it contains.

Oracle runs the same schema across many users, and 12c multitenant fans every change across pluggable databases. By hand that's the same change re-run per schema or PDB; miss one and they quietly diverge.

Dev, staging, and prod diverge the moment one change lands outside the pipeline — and a dependent that exists in one environment can be missing or INVALID in the next, and you find out at deploy.

SQL review runs on the change before it applies — 200+ rules catch a DROP that orphans dependents, an anonymous PL/SQL block hiding DDL, a missing index, and naming violations. The ruleset is strict on production, relaxed on dev.

The migration applies in dev, then staging, then production — and across every schema or PDB in one rollout, not re-run by hand. The same change meets progressively more realistic data, so a cascade of invalid objects surfaces in staging, not first in production. A failure stops the chain.

Approval gates sit between stages. Routine changes auto-promote into dev; production-bound DDL waits for a human who sees the SQL, the review results, and the rollout plan in one record.

Every applied migration is logged with version, environment, executor, and timestamp. Each entry keeps a schema snapshot, and schema sync compares any two databases and realigns them through the same pipeline.

Redaction needs the Advanced Security option, an extra-cost license on Enterprise Edition. Standard and Express get nothing.

A SELECT-only user probes: WHERE salary BETWEEN 99999 AND 100001 returns a redacted 0, but the matching rows give the value away.

SYS, SYSDBA, and any holder of EXEMPT REDACTION POLICY bypass every policy. Redaction never applies to the most powerful sessions.

Data Pump (expdp) and RMAN read the table directly — redaction is a query-time transform. A full export is cleartext.

Workspace rules, first match wins. Conditions on environment, project, database, and classification pick the algorithm — full, partial, MD5, range, custom. One rule covers Enterprise, Standard, and Autonomous alike.

Project-level override for a single column.

Time-bound Query or Export exemptions for named users — service accounts excluded. Every grant logged. Every access logged.

Nobody mints a least-privilege schema per agent before a five-minute setup. They paste the connection they have — often carrying DBA, sometimes AS SYSDBA — and that grant reads every table, drops any object, and can schedule a DBMS_SCHEDULER external job.

There's no connection-string read-only switch to hide behind. A keyword filter that allows SELECT is bypassed by an anonymous block — BEGIN EXECUTE IMMEDIATE 'DROP TABLE orders'; END; is one statement to the parser — and Oracle DDL implicitly commits, so there's nothing to roll back.

Unified Auditing is real and capable — but it records the database user, and every agent shares the one MCP schema. Which agent ran that DELETE, for which person, after which prompt? The audit trail names the same user every time.

The agent reads data, ingests untrusted content, and sends it back out — the lethal trifecta in one shot. A scoped credential can't stop an injection that asks for data it's allowed to read.

The agent authenticates as itself, not as a connection string. Scope follows the identity — only the projects, databases, and tables its role allows, whatever the privileges on the login behind Bytebase.

Sensitive values are masked before they reach the model — and unlike Data Redaction, the mask needs no Advanced Security option, isn't lifted by SYS or SYSDBA, and isn't inferred through a WHERE predicate. A restricted SSN comes back as ******.

A change doesn't run on send. It opens a Bytebase issue, where SQL review and approval apply just as for a human-authored migration.

Database governance for Oracle.

Schema Migration

Data Masking

MCP Server

Connect Oracle

Explore the standard for database governance

Solutions & Platform

Resources

Change Management

Access & Security

AI & Agents

Comparisons

Company

Legal