Table of Contents

Crash Magic oracle sessions

Issue

Users may receive an ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

Explanation

Crash Magic uses at least two connections to a database. This article covers the default connection to the client collision database. 

Each Crash Magic database connection can create multiple sessions. Oracle profiles can be used to limit oracle user sessions. Profiles that are too restrictive can cause the “ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit error from Oracle”.

The number of user sessions required depends on how your database and Crash Magic is configured. Users that have individual accounts on the database and use DBVerify will need fewer sessions per user. Databases that grant a single login for Crash Magic will need more sessions for the single Crash Magic user. Pd’ Programming recommends a minimum of 5 sessions per Crash Magic Online user.

Solution

Oracle uses profiles to set resource limits. Query to determine the profile assigned to the oracle Crash Magic user.

SELECT
USERNAME,
PROFILE
FROM DBA_USERS WHERE USERNAME = ‘

USERNAME              PROFILE
——————- ————–
CRASHDATAREADER       DEFAULT

Check the number of sessions per user for the profile in use:

SELECT
PROFILE,
RESOURCE_NAME,
LIMIT
FROM DBA_PROFILES
WHERE PROFILE = ‘DEFAULT’
AND RESOURCE_NAME = ‘SESSIONS_PER_USER’

PROFILE     RESOURCE_NAME       LIMIT
———– —————     —————– DEFAULT     SESSIONS_PER_USER   1

Alter the profile to allow more user sessions:

ALTER PROFILE DEFAULT LIMIT SESSIONS_PER_USER 5

SELECT
PROFILE,
RESOURCE_NAME,
LIMIT
FROM DBA_PROFILES
WHERE PROFILE = ‘DEFAULT’
AND RESOURCE_NAME = ‘SESSIONS_PER_USER’

PROFILE     RESOURCE_NAME       LIMIT
———– ————— —————– DEFAULT SESSIONS_PER_USER 5

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?