ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
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 |
LRM-00116: syntax error at 'string' following 'string'
RMAN-05515: Duplicate for standby does not allow the use of SET UNTIL
RMAN-00551: initialization of parser package failed
ORA-39049: invalid parameter name string
ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
ORA-03252: initial extent size not enough for LOB segment
ORA-16724: the intended state for the database has been set to OFFLINE
ORA-34358: (MXDSS14) number other users reading
ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
ORA-31162: element or attribute "string" has no SQLType specified
ORA-24359: OCIDefineObject not invoked for a Object type or Reference
TNS-12198: TNS:could not find path to destination