What does nQSError 27002 mean in OBIEE?

nQSError 27002 is a syntax error that means 'Near : Syntax error [at line X]'. It indicates the BI Server encountered an unexpected token while parsing your logical SQL. The 'token' shown is the word or character that triggered the error — usually where your syntax went wrong.

Why does my physical SQL query work but fail in OBIEE?

OBIEE uses logical SQL, not physical SQL. Logical SQL is a simplified dialect that doesn't support all standard SQL features like subqueries without aliases, comma-separated FROM clauses, or certain SQL functions. Your physical SQL (Oracle database SQL) won't translate directly.

How do I convert physical SQL to logical SQL for OBIEE?

Key differences: 1) Use explicit JOINS instead of comma-separated tables, 2) Wrap subqueries in parentheses with aliases, 3) Reference columns through presentation folders (Subject_Area.Folder.Column), 4) Use only OBIEE-supported functions, 5) Quote all identifiers with double quotes.

What's the difference between ANSI joins and comma joins in OBIEE?

ANSI joins use the JOIN keyword (INNER JOIN, LEFT JOIN, etc.) and are supported by OBIEE. Comma joins (old-style: FROM table1, table2) are NOT supported in OBIEE logical SQL. Always use explicit ANSI join syntax.

OBIEE / SQL

OBIEE nQSError 27002 — Syntax Error: The Logical SQL vs Physical SQL Trap

March 25, 2026 · 1,200 words

You've written SQL that works perfectly in SQL*Plus. You paste it into your OTBI report and immediately hit this:

nQSError: 27002
"Near : Syntax error [at line X]"

The frustrating part? Your SQL looks correct. It's valid Oracle syntax. So what's the problem?

The issue is that OBIEE uses logical SQL, not physical SQL. They look similar, but they're fundamentally different languages. Understanding this distinction will eliminate 90% of your nQSError 27002 errors.

Logical SQL vs Physical SQL: The Core Difference

Physical SQL is what you write in SQL*Plus or SQL Developer — it queries the actual database tables directly.

Logical SQL is what OBIEE uses — it queries through the presentation layer (subject areas and folders), not the physical tables.

Feature	Physical SQL (Oracle DB)	Logical SQL (OBIEE)
Join syntax	ANSI or comma joins	ANSI joins only
Subqueries	Supported everywhere	Must be aliased and parenthesized
Column references	table.column or alias.column	"Subject Area"."Folder"."Column"
Functions	All Oracle functions	OBIEE-supported functions only
Quoting	Optional, case-insensitive	Always double-quotes, case-sensitive

When OBIEE encounters physical SQL syntax, it tries to parse it as logical SQL, and that's where the syntax error occurs.

The Most Common Cause: Comma Joins

The #1 source of nQSError 27002 is trying to use comma-separated tables (old-style joins). This works in Oracle SQL but NOT in OBIEE:

❌ This will fail with nQSError 27002:

SELECT p.PERSON_ID, a.ASSIGNMENT_ID
FROM "Employees".p, "Assignments".a
WHERE p.PERSON_ID = a.PERSON_ID
      

✅ This is the correct OBIEE syntax:

SELECT p.PERSON_ID, a.ASSIGNMENT_ID
FROM "Employees" p
INNER JOIN "Assignments" a ON p.PERSON_ID = a.PERSON_ID
      

Always use explicit ANSI JOIN syntax in OBIEE. Never use comma-separated table lists.

Second Most Common: Unsupported SQL Functions

Some Oracle functions don't exist in OBIEE logical SQL. For example:

❌ Won't work in OBIEE:

SELECT ROWNUM as row_number
FROM "Employees"
WHERE ROWNUM <= 10
      

OBIEE doesn't support ROWNUM. Common unsupported functions include:

ROWNUM
ROW_NUMBER() OVER (PARTITION BY ...)
CONNECT_BY
DBMS_ functions (DBMS_METADATA, DBMS_RANDOM, etc.)
Package functions
Recursive CTEs (WITH ... AS ...)

Workaround: Use OBIEE's built-in aggregation functions (SUM, COUNT, AVG, MIN, MAX) or create a database view and expose it through the OBIEE subject area.

Third Most Common: Subquery Syntax Issues

Subqueries in OBIEE must be properly aliased and parenthesized:

❌ This fails:

SELECT * FROM (
  SELECT PERSON_ID, NAME FROM "Employees"
)
      

✅ This works:

SELECT * FROM (
  SELECT PERSON_ID, NAME FROM "Employees"
) AS emp
      

Always alias your subqueries with "AS alias_name". OBIEE requires this.

How to Fix nQSError 27002: Step-by-Step

Step 1: Identify the Token in the Error Message

The error shows which token caused the problem. Example:

nQSError: 27002
Near "," (comma): Syntax error [at line 2]
      

The comma tells you it's a join syntax issue. Look for comma-separated tables.

Step 2: Convert to ANSI JOIN Syntax

Find any comma-separated tables and convert them to explicit JOINS:

-- Before (physical SQL):
SELECT * FROM table1 t1, table2 t2
WHERE t1.id = t2.id

-- After (logical SQL):
SELECT * FROM table1 t1
INNER JOIN table2 t2 ON t1.id = t2.id
      

Step 3: Check Column References

Ensure all columns use the correct subject area and folder paths:

-- Correct format:
SELECT "Subject_Area"."Column_Name"
FROM "Subject_Area"

-- Or with folder nesting:
SELECT "Subject_Area"."Folder"."Column_Name"
FROM "Subject_Area"
      

Step 4: Replace Unsupported Functions

If the error mentions a function, check if it's supported by OBIEE. Use OBIEE alternatives:

Unsupported	OBIEE Alternative
ROWNUM	ROW_NUMBER() or LIMIT clause (if supported)
CAST	Use OBIEE column casting in presentation layer
TO_CHAR with date formats	Use OBIEE date formatting functions
Package functions	Create a database view and expose it

Real-World Example: Converting Physical to Logical SQL

Scenario: Pull all active employees hired in the last 90 days with their current salary.

❌ Physical SQL (Oracle — won't work in OBIEE):

SELECT p.PERSON_ID, p.FULL_NAME, s.SALARY_AMOUNT,
       ROWNUM as row_num
FROM per_all_people_f p, per_all_assignments_f a,
     compensation_salary s
WHERE p.PERSON_ID = a.PERSON_ID
  AND a.ASSIGNMENT_ID = s.ASSIGNMENT_ID
  AND p.CREATION_DATE >= TRUNC(SYSDATE) - 90
  AND a.EFFECTIVE_LATEST_CHANGE = 'Y'
  AND ROWNUM <= 100
      

✅ Logical SQL (OBIEE — correct syntax):

SELECT
  "Employees"."PERSON_ID",
  "Employees"."FULL_NAME",
  "Compensation"."SALARY_AMOUNT"
FROM "Employees"
INNER JOIN "Assignments"
  ON "Employees"."PERSON_ID" = "Assignments"."PERSON_ID"
INNER JOIN "Compensation"
  ON "Assignments"."ASSIGNMENT_ID" = "Compensation"."ASSIGNMENT_ID"
WHERE "Employees"."CREATION_DATE" >= CURRENT_DATE - 90
  AND "Assignments"."EFFECTIVE_LATEST_CHANGE" = 'Y'
      

Key changes:

Removed comma joins, added explicit INNER JOINs
Removed ROWNUM (not supported)
Used double quotes and proper column paths
Replaced TRUNC(SYSDATE) with CURRENT_DATE

Prevention: Write OBIEE-First SQL from the Start

Always use ANSI JOIN syntax — Never comma-separated tables
Always quote identifiers — Use "Subject_Area"."Column"
Always alias subqueries — (SELECT ...) AS alias
Test in the OBIEE Answer Editor first — Before using in reports
Check function support — Verify any non-standard function works in OBIEE

Need to Reference Oracle HCM Tables in Your Query?

Search our database of 35,000+ Oracle Fusion Cloud tables. Find exact table names, column structures, and subject area mappings for your OTBI reports.

Search Oracle HCM Tables →

Summary

nQSError 27002 happens when you write physical SQL (Oracle syntax) instead of logical SQL (OBIEE syntax). The three main culprits are:

Comma joins — Use ANSI JOIN syntax
Unsupported functions — Check OBIEE function support
Unaliased subqueries — Always add "AS alias_name"

Remember: OBIEE doesn't query the database directly; it queries the metadata layer. Write for the metadata layer, not the physical tables.