How to set biserver session timeout in obiee12c

sandy45252

Hi All,

we are seeing regular nqserver messages are below

[2017-05-17T07:19:11.405+00:00] [OBIS] [NOTIFICATION:1] [] [] [ecid: ca6ed286-330d-4fab-b19a-cb15039b1eae-00004362,0:2:1:6:11] [sik: biservice] [tid: 50b53700] Connection Pool entry for DSN HR_BI, DB name is HRBI, connection pool name is Init Block Connection Pool [[

Properties: description=SessionVar Exchange; producerID=0xe26d5b90; requestID=0xfffe0c51; sessionID=0xfffe0000; userName=nQS;

]]

[2017-05-17T07:19:11.407+00:00] [OBIS] [NOTIFICATION:1] [] [] [ecid: ca6ed286-330d-4fab-b19a-cb15039b1eae-00004362,0:2:1:6:11] [sik: biservice] [tid: 50b53700] Connection Pool exit for DSN HR_BI, DB name is HRBI, connection pool name is Init Block Connection Pool [[

Properties: description=SessionVar Exchange; producerID=0xe26d5b90; requestID=0xfffe0c51; sessionID=0xfffe0000; userName=nQS;

]]

[2017-05-17T07:19:11.407+00:00] [OBIS] [NOTIFICATION:1] [] [] [ecid: ca6ed286-330d-4fab-b19a-cb15039b1eae-00004362,0:2:1:6:11] [sik: biservice] [tid: 50b53700] Connection destroyed due to timeout. dsn is VALUEOF(HR_DSN), DB name is HRBI [[

Properties: description=SessionVar Exchange; producerID=0xe26d5b90; requestID=0xfffe0c51; sessionID=0xfffe0000; userName=nQS;

can see lot more message with similar entry and exit within seconds,

Willing to know is it natural behaviour of obiee or  do we have to change any settings to avoid this .

And also saw below message in nq server log

DBGateway Max Data Size::0

DBGateway Max Rows::0

DBGateway Max Threads::300

Listen Port::9502

MAXIMUM_FILE_HANDLES::4096

Machine::sv2lxbi05.corp.equinix.com

Max Session Limit::2000

Monitor Port::9501

Number of Processors::6

ORACLE_BI_HOME::/u01/app/obiee12c/bi

ORACLE_BI_LANG::en

ORACLE_COMPONENT::/u01/app/obiee12c/user_projects/domains/bi_domain/servers/obis1

Repositories::{Star=liverpd.rpd}

SQLBypass  Max Threads::200

Server Max Threads::200

Server Thread Stack Size::1048576

Session TimeOut(Secs)::60

Unique Identifier::obis1

Thanks,

Sandy

[Deleted User]

Are you using connection pooling with timeouts in your RPD connection pool objects?

sandy45252

Thanks Christian ,

We are not using Enable connection pooling in rpd connection pool settings

[Deleted User]

Edit: Sorry. Posted the reply into the wrong thread.

[Deleted User]

Next thing to check: Query limits based on Application Roles:

sandy45252

checked query limit of application roles they all set to 10 min, but the log show session timeout to 60 sec

[Deleted User]

Sandy,

Can you post the [SERVER] section of your nqsconfig?

sandy45252

Hi Christian,

Please find below the server section details of NQSconfig.INI config file

###############################################################################

#

#  Server Section

#

###############################################################################

[SERVER]

READ_ONLY_MODE = NO;  # This is for both online & offline - This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control

MAX_SESSION_LIMIT = 2000; 

MAX_REQUEST_PER_SESSION_LIMIT = 5000; 

SERVER_THREAD_RANGE = 100-200; 

SERVER_THREAD_STACK_SIZE = 0;  # default is 256 KB (32 BIT mode), 1 MB (64 BIT mode), 0 for default

DB_GATEWAY_THREAD_RANGE = 100-300; 

DB_GATEWAY_THREAD_STACK_SIZE = 0;  # default is 256 KB (32 BIT mode), 1 MB (64 BIT mode), 0 for default

DEFAULT_DB_MAX_ROWS = 0;  # default is 0, unlimited.

DEFAULT_DB_MAX_EXEC_TIME = 0;  # in seconds, default is 0, unlimited.

HTTP_CLIENT_THREAD_RANGE = 0 - 100; 

HTTP_CLIENT_THREAD_STACK_SIZE = 0;  # default is 256 KB (32 BIT mode), 1 MB (64 BIT mode), 0 for default

ADF_SQL_BYPASS_THREAD_RANGE = 40 - 200; 

MAX_EXPANDED_SUBQUERY_PREDICATES = 8192;  # default is 8192

MAX_QUERY_PLAN_CACHE_ENTRIES = 1024;  # default is 1024

MAX_QUERY_PLAN_CACHE_ENTRY_SIZE = 0;  # default is 256 KB,(32 BIT mode), 1 MB (64 BIT mode), 0 for default

MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024;  # default is 1024

MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024;  # default is 1024

INIT_BLOCK_CACHE_ENTRIES = 20;  # default is 20

CLIENT_MGMT_THREADS_MAX = 5;  # default is 5

DEFAULT_JOBQUEUE_SIZE_PER_THREAD = 100;  # default is 100, 0 is unlimited.

# Specify the global query limit, it's not enforced by default

# MAX_COLUMNS_IN_SELECT = 50;

# MAX_LOGICAL_DIMENSION_TABLES = 30;

# MAX_LOGICAL_FACT_TABLES = 5;

# MAX_LOGICAL_MEASURES = 15;

# MAX_SET_OPERATION_BLOCKS = 15;

# If not specified, the default value of above 5 parameters are all UNIT32_MAX (4294967295) which means unlimited.

# QUERY_LIMIT_WARNING_INSTEAD_OF_ERROR=OFF; # default is OFF

# Following are low priority query governance limits parameters:

# LOW_PRIORITY_MAX_SERVER_THREAD_COUNT = 0; # 0 means no low priority query allowed. The default value is 0.

# LOW_PRIORITY_DB_MAX_ROWS = 0; # 0 means unlimited. The default value is 0.

# LOW_PRIORITY_DB_MAX_DATA_SIZE = 0; # 0 means unlimited. The default value is 0. The value can be in KB, MB, GB.

# LOW_PRIORITY_DB_MAX_EXEC_TIME = 0; # 0 means unlimited. The default value is 0.

# LOW_PRIORITY_MAX_LOGICAL_QUERY_EXEC_TIME = 0; # 0 means unlimited. The default value is 0.

# This specifies the ip address and port number that the server will

# listen to. When it's set to 0.0.0.0, the server listens on all ip

# address on the machine, otherwise the server will bind to the

# specified ip address.

RPC_SERVICE_OR_PORT = "9703";  # default is 0.0.0.0:9703 - This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control

LISTEN_ADDRESS = "0.0.0.0";  # default is 0.0.0.0

LISTEN_PORT = 9703;  # default is 9703

ENABLE_DB_HINTS = YES;  # default is yes

PREVENT_DIVIDE_BY_ZERO = YES; 

CLUSTER_PARTICIPANT = YES;  # This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control

# Following required if CLUSTER_PARTICIPANT = YES

# The publishing directory should be a complete path as it must be

# a shared drive.

# REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";

# REQUIRE_PUBLISHING_DIRECTORY = NO;  # Don't join cluster if directory not accessible

DISCONNECTED = NO; 

AUTOMATIC_RESTART = YES; 

VARIABLE_VALUE_LIMIT = 4096; 

# EVALUATE_SUPPORT_LEVEL:

# 1: evaluate is supported for users with manageRepositories permssion

# 2: evaluate is supported for any user.

# other: evaluate is not supported if the value is anything else.

EVALUATE_SUPPORT_LEVEL = 2; 

FMW_SECURITY_SERVICE_URL = "http://localhost:7001";  # This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control

FMW_SECURITY_SERVICE_MAX_NUMBER_OF_CONNECTIONS = 2000; 

FMW_SECURITY_SERVICE_MAX_NUMBER_OF_RETRIES = 0; 

# FMW_SECURITY_SERVICE_RETRY_EXCEPTION_SUBSTRING = "forcibly closed";

FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO; 

# ENABLE_NUMERIC_DATA_TYPE:

# When this parameter is enabled, the Administration Tool will

# import Oracle/TimesTen Number data type as Numeric data type in physical

# column definition.  Oracle BI Server will interpret Oracle Number data

# type as Numeric data internally during query execution.

ENABLE_NUMERIC_DATA_TYPE = NO; 

# ENDECA_SERVLET_URL:

# BI Endeca Integration, Server Configuration for Endeca Servlet

ENDECA_SERVLET_URL = "http://localhost:7001/EndecaIntegration/EndecaServlet";

Thanks,

Sandeep

[Deleted User]

Thanks. So all these checks confirm it: you're running a perfecty normal setup without any specific configuration which forces / causes timeouts.

No reason to worry this is normal to have it appear in the logs. It's not an error or an issue.