Many people (at least myself) are ignorant, once development complete and shipped to production, then developers will be least bothered about how dashboards are working.
Even though DEV/QA people thoroughly verified for data and functionality, some times end user can perceive error on dash board, because of QA slippage, resources unavailability or wrong combination of objects(listed at end).
To avoid these kind-of-errors in future, schedule an iBot with Error Track report every day or every hour (as you needed) and fix them in advance before end user asks or notifies about the error.
Here is a sample error track report
Error Track -iBot scheduled every day.
Here is a list of common errors, that end users can perceive at any time.
[nQSError: 14026] Unable to navigate requested expression: ToDate("xyz").
[nQSError: 14026] Unable to navigate requested expression: XYZ.Column. Please fix the metadata consistency warnings.
[nQSError: 15018] Incorrectly defined logical table source (for fact table XYZ) does not contain mapping for [XY Column].
[nQSError: 16001] ODBC error state: IM002 code: 0 message: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.
[nQSError: 17001] Oracle Error code: 12541, message: ORA-12541: TNS:no listener
[nQSError: 17001] Oracle Error code: 28000, message: ORA-28000: the account is locked
[nQSError: 17001] Oracle Error code: 904, message: ORA-00904: "XYZ.Column": invalid identifier
[nQSError: 17010] SQL statement preparation failed."
[nQSError: 17014] Could not connect to Oracle database."
[nQSError: 22024] A comparison is being carried out between non-compatible types.
[nQSError: 22036] Level in TODATE function (Quarter) must be a rollup of (or equivalent to) the measure level (Year).
[nQSError: 22047] The Dimension used in TODATE function must be referenced in the query.
[nQSError: 23006] The session variable, NQ_SESSION.XYZ, has no value definition.
[nQSError: 27002] Near < 'OR' > or <> 'or' <>: Syntax error [nQSError: 26012] .
[nQSError: 27005] Unresolved column: "XYZ"
[nQSError: 27007] Ambiguous column: "XYZ"
[nQSError: 27015] XYZ: column in GROUPBY clause not in the projection list.
[nQSError: 27020] The repository variable "XYZ" does not exist.
[nQSError: 42020] GROUP BY clause, blah blah, is inconsistent with the projected columns in
[nQSError: 46066] Operation cancelled.
[nQSError: 52061] Cache entry, C:\OracleBIData\cache\NQS_xyz, is removed unexpectedly, could not finish ConstructHeader() operation. Restart server to resolve the issue.
[nQSError: 59001] Binary Logical operation is not permitted on DOUBLE PRECISION, VARBINARY operand(s).
[nQSError: 59001] Subtract operation is not permitted on TIMESTAMP, INTEGER operands.
--Hope it helped you
Locate analytics virtual folder (C:\OracleBI\web\app\) in this folder replace default.asp page with following.
I am assuming you have anonymous user exists and particular user role has assigned some dashboards.
##%@ LANGUAGE="JScript" %##
##%@ LANGUAGE="JScript" %##
Replace default.jsp contents with following
Please replace ## with < 'or' > respectively as shown in following figure
When ever users access obiee launch url , it bypasses logon screen and redirect to dashboard.
--Coming soon with new stuff
Today i would like to give some information on Report XML.
Every request internally stored as xml. i.e Request XML, you can view request xml in two ways, goto request’s advanced tab, under Request XML segment you can view this xml or Using Catalog Manager – locate report— on report right click – choose properties –click on Edit XML button—pops window with xml.
Here is through catalog manager.
In general creating a new request throughUI consists of criteria, results, prompts same thing with xml file, it compromise of three main divisions criteria, views, prompts under root node report.
Every request consists of common xml namespace (identified with uniquely named elements and attributes) attributes i.e xmlns
Then next part is criteria (report — criteria)
Criteria element again divided into two major elements Columns, Filters same as UI web construction.
Here is an example with namespaces and all available columns in report.
If you expand column, it internally composed from column related elements and attributes, here is a sample.
Then second large part in criteria is Filters, as show like below
Then next part in report is Views (report –views), in this section consists of all available views for corresponding report.
Last section in report is prompts, here all propmpt related things will be defined in xml, like caption, on which column, control etc
Following chart consist of some of basic elements or attributes and why they are used.