Value Suppression not working

Sometimes it seems that the value suppression option is not working…

First of all, check if the solution is in Value Suppression

If this was not the solution to your problem, than maybe it has something to do with the columns you are sorting on…

  • open at the Criteria tab

  • add a sort to the column on which you want to apply the value suppression on, with Sort Ascending or Sort Descending

  • (optional) add other sorts with Add Ascending Sort or Add Descending Sort

  • in our example, the criteria look like this

  • open the Result tab

  • now the value suppression is working!

Rows with only null values are displayed OR option to disable or enable is not working

There is an option in the Pivot Table Properties, to include or exclude rows with only null values that are displayed in reports.

But sometimes, this option is not working in OBIEE 12c! What you can do is edit the XML of the report.

  • search for the tag nullSuppress=”false”

For example;

<saw:views currentView="0" textDelivery="compoundView!1" valueHierarchyIndent="false" parentsBefore="true" includeNewColumns="true" nullSuppress="false">
  • remove the nullSuppress tag
  • the rows with only null values are gone… and now this option is working again!

 

Error While Downloading To Excel – There was an error processing your download

Problem: error while trying to download to Excel

Solution:

  • edit the config.xml
  • check the tag <XMLP> and edit as follows:
    <XMLP>
    <InputStreamLimitInKB>2048000</InputStreamLimitInKB>
    <ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing>
    </XMLP>
  • stop and restart OBIEE services
  • retry to export to Excel

Maximum number of allowed input records

Problem: error message in report

Screenshot:

Screenshot text:

Maximum number of allowed input records.

Solution:

  • log in to the server
  • go to the directory of instanceconfig.xml
cd /[ENV]/domains/bi/config/fmwconfig/biconfig/OBIPS
  • make a copy of instanceconfig.xml
cp instanceconfig.xml instanceconfig.xml[_orig]
  • edit instanceconfig.xml
vi instanceconfig.xml
  • directly above the </Table> tag, insert this <Cube> section
<Cube>
    <CubeMaxRecords>9999999</CubeMaxRecords>
    <CubeMaxPopulatedCells>999999999</CubeMaxPopulatedCells>
</Cube>
  • save the file and quit
:wq

The error message will not be displayed anymore.

Bad xml instance! Attribute ‘skipLabels’ is not declared for element ‘labels’

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 'skipLabels' is not declared for element 'labels'
  • edit the XML
  • search for the tag ‘skipLabels’
  • remove the tag skipLabels=”true”
  • apply XML
  • save report

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

The primary key of the logical level is not unique

Problem: Model Check Error No. 38152

Screenshot;

The primary key of the logical level is not unique

Screenshot text:

[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

The primary key of the logical level is not unique 2

  • remove the key that is not correct
  • click OK
  • check model

The Model Check Error is gone.

Invalid identifier at OCI call OCIStmtExecute (2)

Problem: Error when editing report

Screenshot:

invalid identifier at OCI call OCIStmtExecute (2)

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.

Cannot read property ‘getAttribute’ of null

Problem: you edit a column selector and get the message “Cannot read property ‘getAttribute’ of null”

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.

column selector choice

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.