Appendix A – Troubleshooting

This appendix provides you with information to troubleshoot common errors, and steps to resolve them when generating NoetixViews metadata into Oracle Analytics. Contact insightsoftwareSupport if any problems persist.

Generating Large Amounts of NoetixViews Content into Oracle Analytics Leads to Performance Issues

The administrative and user experience in Oracle Analytics may degrade as the size of the repository increases. Oracle Analytics cannot handle repositories that are approximately 40 MB and above in size, and the OAC service may fail to start. You may not be able to use the entire NOETIX_SYS schema of a NoetixViews instance in a single Oracle Analytics repository. insightsoftware recommends the following approaches to minimize the effect of a large repository:

Perform a staged rollout of NoetixViews content by generating only those NoetixViews roles that are immediately needed. Generate additional roles when needed.
Use the Generator Filter options in the Angles for Oracle Generator to eliminate view essays and column descriptions from the generated objects. The Noetix Search can be used to access this information if you choose not to generate it into the repository.
Use NoetixViews Workbench or custom hook scripts to avoid generating columns or views from NoetixViews roles that are not needed.
Use NoetixViews Workbench or custom hook scripts to avoid generating List of Value (LoV) mappings that are not needed.
Use multiple instances of Oracle Analytics and generate multiple smaller repositories based on different sets of NoetixViews modules. The Repository Size Estimator in the Choose Roles dialog of the Angles for Oracle Generator interface can be used to estimate the size of the NoetixViews content that will be generated into the repository based on the roles selected. Repositories can be organized by organizational unit, Oracle EBS module or by some other functional grouping.

Queries Fail with a “Null Password Given” Error

The query users get an error message as follows:

[nQSError: 17001] Oracle Error code: 1005, message: ORA-01005: null password given; logon denied at OCI call OCISessionBegin. [nQSError: 17014] Could not connect to Oracle database. (HY000)

The administrator may have forgotten to set the password in the connection pool before bringing the repository online. To resolve, do the following:

Open the repository and modify the password associated with the connection pool, and select Save. For information about modifying the password, see the "Setting the Connection Pool Password" section in Generating Oracle Analytics Repository.
Open Presentation Services, select Answers, and in the left pane, select Reload Server Metadata before you start executing a query.

Report and Dashboard Templates May Return QBVC92JY Error When Viewed

Report and dashboard templates that typically return a large amount of data in a pivot table view in Oracle Analytics Answers and Oracle Analytics Dashboards may fail with a QBVC92JY error. This problem occurs because settings in Oracle Analytics keep it from processing and displaying large data sets.

This behavior can be mitigated by modifying the <CubeMaxPopulatedCells> and <CubeMaxRecords> settings in the instanceconfig.xml file that is part of Oracle Analytics.

For more information about this problem and its resolution, refer to Oracle Metalink document 494163.1.

Report and Dashboard Templates May Return View Display Error When Prompt Value is not Provided

Report and dashboard templates may return the following error when the default prompt value is used. This error occurs with prompts that expect non-textual input – for example, a prompt for a numeric value. This happens because the default value, --Select actual values--, is used directly in the SQL command, causing the syntax error.

[nQSError: 10058] A general error has occurred. [nQSError: 27002] Near <->; Syntax error [nQSError: 26012].

To successfully run the report or dashboard template, change all prompts to valid values.

Regeneration Increases Repository File Size

During regenerations, on account of the import of existing UDML files into the repository, the size of the repository may increase despite no metadata changes. Thereafter, the repository cannot be uploaded to the Oracle Analytics if its size exceeds 40 MB.

For a workaround, make sure of the following points during regeneration:

Do not delete existing UDML files to import them anew.
Do not select the Import Unchanged UDML Files check box.
Perform the following steps periodically:
1. Use nQUDMLGen.exe to generate a new UDML file from the existing repository.
2. Use nQUDMLExec.exe to create a repository using the UDML file generated in the preceding step.
If you need assistance to perform the steps, contact insightsoftwareSupport.

How to Customize Null Flag for Physical Columns in Repository

Previously, reports based on metadata generated with the use of the Angles for Oracle Generator displayed the null value for selection in the parameter prompt during run time. Now, you can use the hk_popgvw.sql hook script to modify the behavior by updating the value in the NULLABLE_FLAG column of the N_GEN_VIEW_COLUMNS table.