OBIEE nQSError 10058 — Column Not Found: Complete Fix Guide

Common causes:

• Typo in column name — "PERSON_I" instead of "PERSON_ID"
• Wrong subject area — Referencing a column from HCM General Ledger when you're querying Payroll
• Column was removed — In a recent RPD (metadata repository) refresh
• Case sensitivity — Using "person_id" instead of "PERSON_ID"
• Using physical table names — Querying "PER_ALL_PEOPLE_F" instead of the presentation layer
• Incorrect folder path — Missing the presentation folder hierarchy

Here's the key difference: If the column exists in the database but not in the OBIEE subject area, OBIEE will never find it. You're not querying the database directly — you're querying the metadata layer.

How to Fix nQSError 10058 (Step-by-Step)

Step 1: Identify the Exact Column Name from the Error

The error message typically shows the column name. For example:

In this case, the column referenced is "PERSON_I" (which is a typo). The correct name is "PERSON_ID".

Step 2: Open the OBIEE Answer Editor and Browse the Subject Area

In OTBI or OBIEE:

1. Click New > Answer
2. Select your subject area from the dropdown
3. Look at the available columns in the left panel
4. Search for the column you referenced — does it exist?
5. If it exists, note the exact spelling and case

Step 3: Verify the Subject Area Name

Subject area names are case-sensitive in OBIEE. Make sure you're using the exact name:

Step 4: Check for Path Issues

Some subject areas have nested folder structures. Your column reference should include the full path:

Step 5: Verify the Subject Area Still Exists

If your BI environment was recently updated, the subject area might have been renamed or consolidated. Check:

• The subject area name in your report
• The list of available subject areas in Answer Editor
• The RPD (repository metadata) version in your environment

Common Examples & Fixes

Advanced Debugging: When the Simple Fixes Don't Work

If you've checked spelling, case, and subject area names but still get the error:

1. Clear your cache: In OBIEE, go to Administration > Manage Sessions > Clear Cache
2. Check the RPD version: Ensure your BI environment is using the latest metadata
3. Verify column permissions: Your user role might not have access to the column
4. Check subject area filters: Some columns are hidden behind row-level security filters
5. Restart OBIEE: As a last resort, restart the BI Server

Why This Matters for HCM Developers

In Oracle HCM, you often need to pull data from multiple subject areas (Payroll, Compensation, Absence Management, etc.). Each subject area has its own column definitions, and they're not always consistent across modules.

For example:

• Payroll subject area: Uses "PAYROLL_RUN_ID"
• Compensation subject area: Uses "COMP_RUN_ID"

If you try to join these directly, you'll get column not found errors. The key is understanding which columns live in which subject area.

Prevention: Best Practices

• Always use the Answer Editor column browser — Copy column names directly; don't type them
• Test in Dev first — Validate your logical SQL before pushing to Production
• Document subject area structure — Keep a reference of which columns belong to which subject areas
• Monitor RPD updates — When your BI environment is patched, test existing reports
• Use aliases for clarity — Makes debugging easier when columns have similar names

Summary

nQSError 10058 "column not found" is usually fixed by:

1. Checking spelling and case sensitivity
2. Using the Answer Editor to browse available columns
3. Verifying the correct subject area name
4. Ensuring the full column path is correct

The most common cause is a simple typo or case mismatch. Always copy column names directly from the Answer Editor to avoid these errors.