Professional Documents
Culture Documents
Errors
Errors
Errors
Oracle Business Intelligence - When a user tries to login, he will get an error called- [nQSError:
43023] Number of sessions exceeded the limit, because the maximum number of users are
already logged in. to know more about this error please visit this link - http://obieeblogjagga.blogspot.in/2012/08/nqserror-43023-number-of-sessions.html.
NQSConfig.ini is a configuration file, where we can configure the OBI Server however we
want. MAX_SESSION_LIMIT is a parameter in NQSConfig.ini file to configure the maximum
number of session that can be opened at a time. For example, if you set a value 10 to this
parameter(MAX_SESSION_LIMIT = 10), then only 10 users can be login. Assume that, 10
users are already logged in, now if any user tries to login then he will get the following error,
because the session limit is reached already. The users has to wait until any one of the user(who
have
logged
in)
logged
out
from
the
session.
To use AGO or TODATE time series functions, it is recommended that, we should define the
detailed level also in the Time dimension hierarchy.
Eg : Suppose you have a time dimension table, that includes columns Time_key, Date_value,
Month, Quarter, and Year. And If you have created the Time dimension hierarchy with the levels
such as YEAR, QUARTER and Month only (there is no level defined for the column
Date_value, which describes the granularity (level of detail)of the row.).
This works fine, for drill down, level based measures and to define aggregate tables.
But when you try to use AGO or TODATE function with this Time dimension hierarchy,
you will get the above mentioned error.
Solution : Just include one more logical level for the Time dimension hierarchy and add the
date_value(or a column which holds granularity for the row.) as a logical key.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Dimensional Hierarchy, Errors, OBIEE 10g
Solution : Expand the Time dimension, go to properties of any logical level, then go to keys tab
and check the Chronological Key tab.
This is the common error, the developers get, when he try to change the value of session
variable using request variable in request prefix field. ( refer how to change the value of session
variable using Request Variable ).
Solution :
Go to properties of session variable all check the option "Enable everyone to set value"
Follow the below steps :
1. Open Administration Tool. Go to Manager > Variables.
2. Select System or Non-System variable (depends on type of your variable) under the Session
from left pane. Then the corresponding variables will be listed on right pane.
3. Right click on the variable(for which your getting error in presentation service when you tried
to change its value) and select properties.
4. check the option "Enable everyone to set value" (by default this option is unchecked) and click
OK.
Now, check the request in presentation service. Log out from that session and again login to
presentation services and the same report. If you get the same error again, please let me know by
your comments.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g, Variables
In BMM layer of Administration tool, if you do not define logical join for a logical table, the
following error will occur.
Solution : Identify the Logical table in the Error message, and make the proper joins in BMM
layer.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g
Solution :
Open Administrator Tool, find the physical table which you used in the request, define the joins
with the fact/dimensional table properly. Then save the repository and restart the services
(presentation services and BI services) or reload the metadata. Now check the same request in
presentation services.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g
After searching some blogs I got the solution for this issue.
Solution :
Open NQSConfig.INI file, and check each section and make necessary changes.
In my case, I had given the wrong repository name (instead of text.rpd I had given tex.rpd), so I
changed the name of the RPD, after that restart was successfull.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g
Errors