ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
- 2 Answers
- 17831 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 |
PCB-00575: PLS-number: string
ORA-02292: integrity constraint (string.string) violated - child record found
QSM-01034: materialized view, string, needs a dimension level to join table, string
O2I-00126: You must specify an INTYPE file with SCHEMA_NAMES=FROM_INTYPE
ORA-29870: specified options are only valid for altering a domain index
RMAN-06564: must use the TO clause when the instance is started with SPFILE
ORA-22895: referenced table "string" in schema "string" is not an object table
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.
PLS-00403: expression 'string' cannot be used as an INTO-target of a SELECT/FETCH statement
ORA-28153: Invalid client initial role specified: 'string'
ORA-10921: Cannot drop tablespace belonging to default temporary tablespace group
NNO-00853: failed to get LDAP attribute/value: error = number
Oracle Errors 
