ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
- 2 Answers
- 16335 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 |
ORA-36778: (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
SQL*Loader-00129: Invalid number of rows for direct path column array
IMG-00609: unable to read image stored in a BFILE
ORA-06263: NETNTT: out of memory in pi_connect
NNO-00803: Error: OCI_INVALID_HANDLE
PLS-00583: size must be specified if opaque type is fixed-length
ORA-09850: soacon: Archmon unable to lock named pipe.
NNL-00850: Rename requests received: number
ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.
RMAN-08116: output filename is original SPFILE location
RMAN-06133: recovery catalog may have obsolete data for datafile string
ORA-12602: TNS: Connection Pooling limit reached
Oracle Errors 
