There may be several reasons that can cause this error when attempting to run custom reports.
The following is a checklist of items to check in order to resolve this type of error.
- Can this report be run accessing the database directly using Crystal Reports? Verify that you can successfully obtain the report using Crystal Reports.
A report that can not be run without Audit will not be successful under Audit.
- Make sure all the tables and queries for this custom report are accessible from the eTAudit DSN.
- Verify if the database is set to case sensitive. Note: Oracle is SQL92 compliant. Therefore table and column names are translated to upper case in the oracle database when they are not quoted. MS SQL Server allows you to have an option in the database properties to set quoted identifier to No (the default then single and double quotes are treated the same way. This option is not available in Oracle.
Double Quotes are used because it allows the support of language characters.
The following is a summary of how double-quotes are used.
- Internal Audit created tables such as SEOSDATA, KB_VERSION, AUDITEXTENDSTRING, where users cannot modify their names are not double-quoted.
- Security Command Center Table Collector tables names are double-quoted because they are user-defined that users can create/modify from GUI.
- The Audit column names are not double-quoted because they are fixed and cannot be changed.
- The Security Command Center column may or may not be double-quoted.
- If the column is predefined for internal use which users cannot modify, they are not double-quoted, e.g., the escc_pending, escc_pendingid, etc.
- If a column is not predefined for Security Command Center Table Collector internal usage, and they can be viewed/created/modified via the Security Command Center GUI, then it will be double-quoted in its database object name.
Note: Once you use double quotes, the syntax of the SELECT statement becomes case-sensitive.