Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
- 2 Answers
- 17671 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / guest
Cause: An attempt was made to exceed the maximum number of
concurrent sessions allowed by the SESSION_PER_USER clause
of the user prfile.
Action: End one or more concurrent sessions or ask the
database administrator to increase the SESSION_PER_USER
limit of the user profile.
Please add more information about this Error
| Is This Answer Correct ? | 5 Yes | 2 No |
Answer / marcela alejandra saucedo
necesito con urgenciaacceder a las solicitudes que hay que
completar para poder cobrar el salario de mis hijas. soy
sola con ellas y tengo seguimiento oncológico. mil gracias.
no tengo computadora y todos los dias voy a un ciber.mil
gracias.
| Is This Answer Correct ? | 0 Yes | 0 No |
TNS-01005: trace OFF | USER | ADMIN | SUPPORT [<listener_name>] : set tracing to the specified level
NID-00421: Change of database name failed during validation - database is intact.
ORA-22338: must specify CASCADE INCLUDING DATA when altering the final property
RMAN-08527: channel string: starting string proxy datafile backup at string
PLS-01424: Non-ANSI order of clauses
ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be specified
LPX-00320: No more attributes can be added to a non empty element
PCC-00056: FOR clause not allowed on SELECT statement at line number in file string.
DRG-10854: Invalid scoring algorithm string specified for query template
ORA-01077: background process initialization failure
ORA-23373: object group "string"."string" does not exist
ORA-09283: sllfsk: error skipping records
Oracle Errors 
