Troubleshooting
Problem
What is the impact from Filenet Content Manager perspective if user limits the SESSIONS_PER_USER value for Object store database account?
Symptom
In Oracle formal documentation, you can see the following information about the SESSION_PER_USER except the following documentation:
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_6010.htm#SQLRF01310
resource_parameters
SESSIONS_PER_USER Specify the number of concurrent sessions to which you want to limit the user.
Additional update, if the SESSIONS_PER_USER limit is exceeded, the error ORA-02391 will happen. Please refer to the detailed explanation of this error.
Description：
exceeded simultaneous SESSIONS_PER_USER limit
Cause：
An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user profile.
Action：
End one or more concurrent sessions or ask the database administrator to increase the SESSION_PER_USER limit of the user profile.
From the FileNet perspective, due to the request from FileNet will finally pass to the database level, so the database will control the connection number (total session number) for each user. If the limit reaches, the database will throw the error ORA-02391 and you might see a connection refuse error from the FileNet side first.
So the conclusion is FileNet P8 can not control this database related setting, if the limit reaches in database level, an error should occur in FileNet P8 error log.
Resolving The Problem
There's nothing to do with the SESSION_PER_USER setting in FileNet side, so the best idea is to engage a support from Oracle and they can provide the detailed explanation and resolve the problem.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21672924