[nQSError: 43023] Number of sessions exceeded the limit.

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 resolve this problem you just follow the below instructions.

Open the NQSConfig.INI file and locate the [ SERVER ] section, check the number
for MAX_SESSION_LIMIT = 1000 ; parameter. (by default this parameter value will be 1000)
If the value for this parameter is less than the number of concurrent users of your application,
then increase the number as it should be equal or greater than the number concurrent users of
your
application.
If I am wrong, feel free to suggest me please.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g, Presentation Services

[nQSError: 22040] To use AGO function, the storage level of the

query ('[time1.time_key]') must be a static level. (HY000)
This error may occurs most probably due to improper Time dimension hierarchy.

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

[38087] None of the levels in time Dimension '' defines a

chronological key.
For a Time Dimension, it is mandatory that at least one logical level must have set Chronological
key. If a chronological key is not set for a Time dimension, then we will get the following error
when you check the consistency.

Solution : Expand the Time dimension, go to properties of any logical level, then go to keys tab
and check the Chronological Key tab.

Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Labels: BI Server, Dimensional Hierarchy, Errors, OBIEE 10g

Error : [nQSError: 13015] You do not have the permission to set

the value of the variable
View Display Error
Error getting drill information: SET VARIABLE LOB='APD' SELECT item.item saw_0,
valueof(nq_session.LOB) saw_1 FROM OLEM
Error Details
Error Codes: YQCO4T56:OPR4ONWY:U9IM8TAC:OI2DL65P
Odbc driver returned an error (SQLExecDirectW).
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general
error has occurred. [nQSError: 13015] You do not have the permission to set the value of the
variable 'LOB'. (HY000)
SQL Issued: {call NQSGetLevelDrillability('SET VARIABLE LOB=''APD'' SELECT item.item
saw_0, valueof(nq_session.LOB) saw_1 FROM OLEM')}

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

[nQSError:15001] Could not load navigation space for subject

area ...

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

[nQSError: 14026] Unable to navigate requested expression

When the joins are not properly defined in Physical layer for a physical table then the following
error will results by Presentation services when we request the same table.

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

Error Codes: OPR4ONWY:U9IM8TAC

The Presentation Services User gets the mentioned error when he issue any request to the OBI
server.
Error Codes: OPR4ONWY:U9IM8TAC
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A
general error has occurred. [nQSError: 43082] Illegal operation attempted on a closed
request. (HY000).

The most possible reason is :

BI Server Administrator might have killed the active query (active query means the query which
is being processing by BI Server). So once the admin killed an active query, BI server will stop
processing that query and the user will get above mentioned error in Presentation services.
Solution : Resend the same request by clicking on Results tab in Answers.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g

Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P

User gets the below shown error in Presentation Services when he try to issue any requests to
OBI Server.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A
general error has occurred. [nQSError: 43081] Illegal operation attempted on a closed
session. (HY000)

The most possible reason for this error is :

The BI Server Administrator might have disconnected the current user's session and that user
might be still sending request to the BI Server.
Solution :
When the BI Server Administrator disconnects USER from the current session, then such user
can not send request to the BI Server. Because that user in no more in the session to request.
Solution : Log out from the Presentation Services (just click on the Log Out button) and again
Log in and check the same request.
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: BI Server, Errors, OBIEE 10g

ERROR 1064 on OBIEE.

Today I came across this error when I tried to restart the Oracle BI Server on my local system.
The actual error I got isCould not start Oracle BI server service on Local system.
Error 1064 : An exception occurred in the service when handling the control request.

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

[nQSError: 43023] Number of sessions exceeded the limit.

(08004)
[nQSError: 22040] To use AGO function, the storage level of
the query ('[time1.time_key]') must be a static level. (HY000)
[38087] None of the levels in time Dimension '' defines a
chronological key.
Error : [nQSError: 13015] You do not have the permission to
set the value of the variable
[nQSError:15001] Could not load navigation space for
subject area ...
[nQSError: 14026] Unable to navigate requested expression
Error Codes: OPR4ONWY:U9IM8TAC
Error Codes:
OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P
ERROR 1064 on OBIEE.
No Log Found
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest