Describes actions to identify problems when generating a report created using Oracle Business Intelligence Suite Extended Edition:
Example 5-3 Troubleshooting an Oracle Communications Data Model Report
Assume the log file contains the following error:
Query Status: Query Failed: [nQSError: 15018] Incorrectly defined logical table source (for fact table Customer Mining) does not contain mapping for [Customer.Cell Phone Number, Customer.Customer Segment Name, Customer.Party Name].
This error occurs when there is a problem in the Business layer in your Oracle Business Intelligence Suite Extended Edition repository.
In this case, you need to check the mapping for Customer.Cell Phone Number
, Customer.Customer Segment Name
, and Customer.Party Name
.
Example 5-4 Troubleshooting a Report: A Table Does Not Exist
Assume the log file contains the following error:
Query Status: Query Failed: [encloser: 17001] Oracle Error code: 942, message: ORA-00942: table or view does not exist.
This error occurs when the physical layer in your Oracle Business Intelligence Suite Extended Edition repository has the table which actually does not exist in the Database.
To find out which table has problem:
Copy the SQL query to database environment.
Execute the query.
The table which does not exist is marked out by the database client.
Example 5-5 Troubleshooting a Report: When the Database is Not Connected
Assume the log file contains the following error:
Error: Query Status: Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: connect failed because target host or object does not exist.
Meaning: This error occurs when the Database is not connected.
Action: Check connecting information in physical layer and ODBC connection to ensure that the repository is connecting to the correct database.