Skip to main content

Static analysis for PL/SQL and Oracle SQL

ZPA parses database code into structured syntax, then applies checks that understand PL/SQL and Oracle SQL semantics.

Browse the rule catalog Install for SonarQube

Analyze the code that runs in Oracle

PL/SQL

Anonymous blocks, packages, procedures, functions and declarations are parsed as structured code.

Oracle SQL

SELECT and DML grammar inside database programs is available to rules as named syntax.

Oracle Forms

Object references can be checked when a project supplies Forms metadata. See the metadata format

utPLSQL reports

The SonarQube plugin imports test execution and coverage reports alongside analysis results. Read the integration guide

ZPA understands code, not just text

Rules work from parsed structures and semantic context, then attach the explanation and metadata needed to act on a finding.

Structured parsing

PL/SQL + Oracle SQL

Blocks, declarations and SQL statements are available to checks as structured syntax.

Symbol and type awareness

names · scopes · types

Rules can use declarations, usages, scopes and PL/SQL types while analyzing code.

Documented findings

rule · priority · remediation

Each issue includes rule metadata and links to guidance with rationale and examples.

Choose where to run ZPA

Both use the same analyzer and built-in rules. Choose the integration that fits your workflow.

SonarQube

For project-level findings and team review.

  • Runs through SonarScanner.
  • Publishes issues and metrics in SonarQube.
  • Can import Forms metadata and utPLSQL reports.
Install the SonarQube plugin

Standalone CLI

For local analysis and CI jobs.

  • Scans a source directory.
  • Writes console or Sonar Generic Issue Data.
  • Supports JSON configuration and custom rule plugins.
Read the CLI guide

Write rules for your conventions

When the built-in catalog is not enough, use ZPA’s custom rule API to inspect the same parsed structures and enforce standards specific to your codebase.

Read the custom rules guide

Get started with ZPA

Start with the documentation path that matches the next thing you need to do.