How to Debug Oracle Errors in BI Connector Log Files

Modified on Tue, 2 Sep at 1:46 AM

When working with BI Connector and Oracle Fusion, errors may occur during query execution or data fetch. Debugging these issues becomes easier by checking the BI Connector log files, identifying the error message, and applying the right fix. Below is a quick guide on how to access logs and troubleshoot common Oracle errors.


How to Access BI Connector Log Files?

       1 . Using BI Connector UI:

  • Open BI Connector
  • Go to the Help Center tab
  • Click Download Logs to save the latest logs as a ZIP file

      2. Using File Explorer: 

  • Open File Explorer on the BI Connector machine.
  • Navigate to: C:\ProgramData\Guidanz\BI Connector\logs
  • You will find the log files in this folder.

Identify the Right Log File to Search

  • For Data Model issues: Check bip.log
  • For Subject Area/Analysis issues: Check biconnector.log.
  • Search for the keyword ERROR.
  • Check the log entries around the time the failure happened.


Possible Error Scenarios

  1. Invalid Identifier

  Error Message:
  "ColumnName": Invalid identifier
  Reason:
  The column name in the SQL query does not exist in the table or it is misspelled.
  Suggestions:

  1. Please check the SQL query you used to create the data model , and confirm the column name exist in table.
  2. If you using data pipeline , ensure that the watermark column, primary key columns are correctly spelled and exist in the source table.
  3. Double-check for typos in column names.

2. Table Not Found
Error Message in log:
Table or View does not exist
Reason :
Invalid Table name or table does not exist
Suggestions:
Fusion table names are case-sensitive , Please make sure that you have entered the correct table name.



3. Authentication Error
Error Message in log:
Authentication Failure / Invalid Username and Password.
Reason :
Username and Password is invalid or expired
Suggestions:
Provide the correct username and password in the Data source in BI Connector.



4. Report Does Not Exist
Error Message in log:
The Report path does not exist / Report path is invalid / Path not found
Reason:
The Report you are trying to load in BI Tools does not exist.
Suggestions:
1. Verify in Oracle Fusion / OAC environment , the report exist or not.

2. Check if the report path entered in BI Connector is correct and matches the exact folder structure in Oracle Fusion / OAC.



5. Data Model Does Not Exist
Error Message in log:
Not able to get data set columns.
Reason:
The Data Model you are trying to load in BI Tools does not exist.
Suggestions:
Verify in Oracle Fusion / OAC environment , the data model exist or not and you have access to that data model. 



6. Report Is Not Accessible
Error Message in log:
access denied for user to path

Reason:
The Report you are trying to load in BI Tools is not accessible with the current user's permissions.

Suggestions:

1. Verify that the user account has the necessary role and privileges to access the report.

2. Check if the report is shared with the user or role in Fusion / OAC and that folder-level permissions are correctly set.



7. Oracle Memory Issue
Error Message in log: 
XDODataSizeLimitException / Payload too large / OutOfMemoryError / any error message with size limit , memory issue keywords
Reason : 
For this particular table, the amount of data being fetched exceeds Oracle’s size limit and results in a memory-related failure during query execution.
Suggestions:

To resolve this, please follow the steps below:

      1. Open BI Connector and edit that particular table.

      2. Click on Settings.

      3. Change the "No of Rows per fetch" value from 50,000 to 25,000.
      4. Click on Apply and Save the table.



8. Query Timeout
Error Message in log:
504 Gateway Timeout / Read timed out / Bad Gateway
Reason:
The oracle is taking too long to process the query, and the connection is timing out.
Suggestions:
        
1Check network connectivity between the BI Connector and Oracle Fusion.
        2. Reduce the “No of Rows per fetch” in BI Connector for that particular table.



9. Invalid Oracle Fusion URL / Network Issue
Error Message in log:
ERR_NAME_NOT_RESOLVED / getaddrinfo ENOTFOUND 
Reason:
The URL you provided in the data source in BIC is expired or invalid.
If you are able to access the URL in the browser, then it might be due to network issues.
Suggestions:

             1. Provide the valid Oracle Fusion account URL.

             2. If you are able to access the URL in the browser, ensure a stable network connection.


10. Invalid SQL Query
Error Message in log:
Please verify the data model SQL query and associated parameters

Reason:
The SQL query sent to Oracle Fusion is invalid. 
Suggestions:

             1. Verify the SQL Query used in BIC for table creation is correct or not , you can click Run in BIC to verify data is coming or not.

             2. If you are using data pipelines , Verify that the watermark column, primary key columns is correctly spelled and exists in the source Fusion table.

             3. The water mark column format should be correct. 



11. SSL / Network Issues
Error Message in log:
SSL handshake failed / Unable to establish connection / Connection refused.
Reason:
There may be a network firewall or SSL/TLS mismatch between the BI Connector machine and the Oracle Fusion.
Suggestions:

             1. Ensure SSL certificates are up to date and valid.

             2. Check if outbound ports to Oracle are allowed.

             3. Try accessing the report URL in a browser to verify connectivity.



12. Access Denied / Missing "SOAP" Privilege
Error Message in log:
Access denied / SOAP privileges
Reason:
The Fusion user account configured in BI Connector does not have sufficient privileges to access BI Publisher services over SOAP API.
Suggestions:
To connect BI Connector with Oracle Fusion, the user must have appropriate roles and privileges. Refer to this guide for detailed requirements:
https://support.biconnector.com/support/solutions/articles/8000043776-what-obiee-oac-permissions-roles-access-is-needed-for-bi-connector-to-connect-to-obiee-