[38083] The Attribute ..... defines a measure using an obsolete method.

[38083] The Attribute '<Column Name>' defines a measure using an obsolete method.

This error occurs whenever there is an obsolete method used in BMM layer esp aggregate function like SUM, COUNT, MIN, MAX etc.

Since version 10.1.3.2, Aggregate functions in logical column definitions which use other logical columns are not supported anymore.

Solution 1:

    You can change this behaviour by setting the parameter SUPPORT_OBSOLETE_MEASURES to YES
    This parameter is not found in NQSConfig.ini file. We need to add this in the 'General' section.

Solution 2: 

  We can use Evaluate, Evaluate_aggr, Evaluate_Predicate, Evaluate_Analytic functions to achieve the respective obsolete functionality.

OBI 11g Column Permission Setting: PROJECT_INACCESSIBLE_COLUMN_AS_NULL

In Oracle BI 10g, If a column is hidden from a user and when the User logs in there would be an error.

To fix this error, we have to change the parameter  PROJECT_INACCESSIBLE_COLUMN_AS_NULL in NQSConfig.ini

In Oracle BI 11g,  the parameter value is set to ‘YES’ :

[SECURITY]

DEFAULT_PRIVILEGES = READ;  

PROJECT_INACCESSIBLE_COLUMN_AS_NULL = YES;  # default is no

# Note that the paths below should be relative to the instance

# config directories if specified.  e.g.,

# $(ORACLE_INSTANCE)/config/OracleBIServerComponent/<instance_name>

#IGNORE_LDAP_PWD_EXPIRY_WARNING = NO;     // default is no.

Isolation level in Connection Pool

What are Isolation level in Connection Pool Setting ??


They are applicable for ODBC and DB2 gateways only. 

The Level options:

Committed Read:    Locks are held while the data is read to avoid dirty reads. Data can be changed before the transaction ends with that connection.

Dirty Read:   0 Locking. Can read uncommitted or dirty data, change values in data during read process in a transaction. Least restrictive of all types.

Repeatable Read:  Places locks on all data used in a query so that nobody can update the data. However new rows can be inserted by other users but will be available in later reads in the current transaction.

Serialization:   Places a range lock on data set preventing other users to insert or update the rows in data set until the transaction is complete. Most restrictive of all.

Maximum Connections in Connection Pool

Setting up Maximum Connection in Connection Pool is one of the main parameter which affect performance.

The default value of 10 is usually too low (it will cause queuing) but setting it too high will eat up memory and the BI Server process may not even start (1024 kb of server memory is consumed per connection ) .

So a general rule is to follow the below formula to set up Maximum Connections.

Maximum number of connections =   Total  number of reports per dashboard *  20% of concurrent users 

Point to note: It 20% of concurrent users .NOT 20% of total users.  Generally, In any given time at-least 25% of user will be accessing dashboard.
 

Oracle BI tutorial

Oracle has given self-learn tutorial for OBI 10g & 11g.

Follow the below link to access the tutorial.

OBI 11g    OBI10g


These tutorial not only help any keen OBI starters to gain knowledge in OBI but also helps oracle to showcase their new features in their everlasting releases and patches.