|Oracle FAQ||Your Portal to the Oracle Knowledge Grid|
ORACLE Server Parameters >
Related Error Messages:ORA-00018: maximum number of sessions exceeded
Action: Increase the value of the SESSIONS initialization parameter.
ORA-00019: maximum number of session licenses exceeded
Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter.
ORA-00038: Cannot create session: server group belongs to another 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
Action: Find the other sessions and log them out and resubmit the command
ORA-01153: an incompatible media recovery is active
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
Action: Close database in all instances and end all recovery sessions
ORA-01353: existing Logminer session
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
Action: End all logminer sessions and retry.
ORA-01373: insufficient memory for staging persistent LogMiner session
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
ORA-02045: too many local sessions participating in global transaction
Action: use an existing link so another session need not be created.
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
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
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
Action: Ensure there are no other connections to the database
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions.
ORA-16255: Log Auto Delete conflicts with another LogMiner session
Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.
ORA-16727: resource guard cannot close database
Action: Check if there any active sessions connect to the database, terminate them, then reissue the request.
ORA-24413: Invalid number of sessions specified
Action: Specify a valid combination of parameters.
ORA-24414: Only %d sessions could be started.
Action: This is a warning. Check the maximum number of sessions allowed on the server.
ORA-24417: Session pool size has exceeded the maximum limit
Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters.
ORA-24418: Cannot open further sessions.
Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and increase the value of the sessMax parameter.
ORA-24422: error occurred while trying to destroy the Session Pool
Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
ORA-31398: DBMS_LDAP: Shared servers are not supported.
Action: Use dedicated database sessions to execute functions in the DBMS_LDAP package.
ORA-37115: New OLAP API history is not allowed
Action: Wait until all active OLAP API sessions terminate before resetting _olapi_history_retention parameter to true.
ORA-39171: Job is experiencing a resumable wait.\n%s
Action: Correct the condition causing the wait. This will typically involve adding datafiles to the tablespace that is full.