sessions

Oracle 10.0.1:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: All session state objects are in use.

Action: Increase the value of the SESSIONS initialization parameter.

ORA-00019: maximum number of session licenses exceeded

Cause: All licenses are in use.

Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter.

ORA-00038: Cannot create session: server group belongs to another user

Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user.

Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner.

ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected

Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.

Action: Find the other sessions and log them out and resubmit the command

ORA-01153: an incompatible media recovery is active

Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs

Action: Complete or cancel the other media recovery session or RMAN backup

ORA-01182: cannot create database file %s - file is in use or recovery

Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered.

Action: Close database in all instances and end all recovery sessions

ORA-01346: Dependent LogMiner sessions relying on supplementally logged data exist

Cause: LogMiner sessions exist on this database instance which rely on the existance of supplemental log data.

Action: Destroy all LogMiner sessions on this instance which are mining log files from this same instance then reissue the command.

ORA-01353: existing Logminer session

Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.

Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.

ORA-01356: active logminer sessions found

Cause: Logminer sessions are currently active.

Action: End all logminer sessions and retry.

ORA-01373: insufficient memory for staging persistent LogMiner session

Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.

Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.

ORA-02045: too many local sessions participating in global transaction

Cause: too many sessions at this site for this transaction.

Action: use an existing link so another session need not be created.

ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

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.

ORA-06604: LU6.2 Driver: Unable to allocate session with remote LU

Cause: Allocate system call failed.

Action: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter.

ORA-12721: operation cannot execute when other sessions are active

Cause: This command can only be run when there are no other sessions active

Action: Ensure there are no other connections to the database

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ sessions ] on the Oracle FAQ.