SQL dialect
Oracle SQL Parser for Java and .NET
General SQL Parser (GSP) parses Oracle with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage , including complete procedural SQL support. One commercial SDK, 38 dialects, Java and .NET.
Example
Oracle SQL that GSP parses
CREATE OR REPLACE PACKAGE BODY hr.emp_mgmt AS
PROCEDURE raise_salary(p_id NUMBER, p_pct NUMBER) IS
BEGIN
UPDATE employees SET salary = salary * (1 + p_pct / 100)
WHERE employee_id = p_id;
END;
END emp_mgmt; Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvoracle);
parser.sqltext = sql; // the Oracle SQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
} The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
What GSP handles in Oracle
- PL/SQL packages and types
- CONNECT BY hierarchical queries
- Synonyms and database links
- MERGE statements
- Compound triggers
- Procedural SQL: PL/SQL procedures, functions, packages, triggers, and object types, including compound triggers and pipelined functions
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Oracle.
Actively maintained
Recent Oracle parser updates
- 2026-06-23 [Oracle] Improve synonym and dblink data lineage analysis
- 2026-06-18 [Oracle] Fix CTE alias resolution for repeated references
- 2026-06-13 [Oracle] Add regression tests for ${} in string literals
Full history in the release notes.
Go deeper
Oracle resources
- Oracle syntax reference — dialect documentation
- Oracle keyword compatibility — every keyword, and whether it can be an identifier
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — NuGet setup for .NET
Common questions
Does GSP parse Oracle stored procedures and procedural SQL?
Yes. GSP parses PL/SQL procedures, functions, packages, triggers, and object types, including compound triggers and pipelined functions into a full AST — procedure bodies become real statement trees you can traverse, not opaque text blocks. This is what makes lineage and impact analysis work inside procedural code.
Do I need a Oracle database connection to validate SQL?
No. GSP validates Oracle syntax completely offline. You get error line and column positions, the offending token, and a hint — with no server, driver, or credentials involved.
How complete is the Oracle grammar?
GSP uses a dedicated hand-tuned grammar for Oracle — not a generic SQL grammar with flags. The parser recognizes 690 Oracle keywords and knows which 678 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Oracle parser from C# / .NET?
Yes. The .NET edition (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every Oracle parsing feature on this page works in C# and VB.NET.
Can GSP extract column-level lineage from Oracle SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Oracle scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.