Category Archives: Berry van den Heuvel
Bad xml instance! Attribute ‘biFormat’ is not declared for element ‘dataFormat’
When reports are created in a 12 environment, it is not possible to simply compress the reports in 12 and unarchive them in 11. When we want to run the 12-report on an 11 environment, just copy and paste the XML and apply the XML. Sometimes this error message appears;
When we scroll to the end of the message, we can see what the problem is;
Attribute 'biFormat' is not declared for element 'dataFormat'
- edit the XML
- search for the tag ‘biFormat’
- remove the tag biFormat=”dateShort”
- apply XML
- save report
Het bericht Bad xml instance! Attribute ‘biFormat’ is not declared for element ‘dataFormat’ verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).
Add a message to the Sign In page
Sometimes, it can be convenient for the user, when there is an extra message on the sign in page. For example when the datamarts are not refreshed already.
To add this message (for example WELCOME!), follow these steps;
- go to the directory of the signin.html (Locations of important files)
- create a copy
cp signin.html signin.html_orig
- edit the file
edit signin.html
- add your html code between
-
<td class="boxcontent" width="100">
and
<form id="logonForm" method="post" action="@{logonURL}" onsubmit="return onLogonFormSubmit()">
Now it looks like
<td class="boxcontent" width="100">
<text>WELCOME!</text>
<form id="logonForm" method="post" action="@{logonURL}" onsubmit="return onLogonFormSubmit()">
- save the file
- restart the presentationserver (Restart processes with Enterprise Manager)
Now, your message appears on the sign in page.
Het bericht Add a message to the Sign In page verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).
The primary key of the logical level is not unique
Problem: Model Check Error No. 38152
Screenshot;
[38152] The primary key of the [BUSINESS_MODEL].[DIMENSION].[LEVEL] logical level is not unique. This will cause failures during aggregate persistence and data discrepancies in created aggregates. The following logical SQL can be used to diagnose the issue: /* Query to check uniqueness of [QUERY]
Possible solution:
- open logical level
- click Keys
- remove the key that is not correct
- click OK
- check model
The Model Check Error is gone.
Het bericht The primary key of the logical level is not unique verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).
Invalid identifier at OCI call OCIStmtExecute (2)
Problem: Error when editing report
Screenshot:
Screenshot text:
[NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 904, message: ORA-00904: "[TABLE_NAME]"."[COLUMN_NAME]": invalid identifier at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.
Possible solution:
The physical column “[TABLE_NAME]”.”[COLUMN_NAME]” doesn’t exist anymore.
- remove this column from the physical layer or create it in the database
- check in
- refresh screen
The error message is not displayed anymore.
Het bericht Invalid identifier at OCI call OCIStmtExecute (2) verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).
Cannot read property ‘getAttribute’ of null
Problem: you edit a column selector and get the message “Cannot read property ‘getAttribute’ of null”
Possible cause:
When you edit a column selector and save the report, the current selection of the column selector in your view is also saved. Here, the part “choice” is added to the XML by OBIEE.
Possible solution:
When you remove the part choice=”xxxxxxxxxxxxxxxxx” from the XML and save the report again, the error message will not be displayed, when you edit the column selector again.
Het bericht Cannot read property ‘getAttribute’ of null verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).
