Welcome to the Technical Portal: ORA-00026 to ORA-00050
| ORA Code | Code Description | Cause | Action |
| ORA-00026 | Missing or invalid session ID | Missing or invalid session ID string for ALTER SYSTEM KILL SESSION | Retry with a valid session ID |
| ORA-00027 | Cannot kill current session | Attempted to use ALTER SYSTEM KILL SESSION to kill the current session | None |
| ORA-00028 | Your session has been killed | A privileged user has killed your session and you are no longer logged on to the database | Login again if you wish to continue working |
| ORA-00029 | Session is not a user session | The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.) | Retry with a user session ID |
| ORA-00030 | User session ID does not exist | The user session ID no longer exists, probably because the session was logged out | Use a valid session ID |
| ORA-00031 | Session marked for kill | The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptible operation is done | No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner |
| ORA-00032 | Invalid session migration password | The session migration password specified in a session creation call was invalid (probably too long) | Retry with a valid password (less than 30 chars) |
| ORA-00033 | Current session has empty migration password | An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed | Create the session with a non-empty migration password |
| ORA-00034 | Cannot COMMIT or ROLLBACK in current PL/SQL session |
You tried to issue a COMMIT or ROLLBACK command from a PLSQL function,
procedure, or package. However, COMMIT and ROLLBACK have been disabled
with the following command: ALTER SESSION DISABLE COMMIT IN PROCEDURE |
The options to resolve this Oracle error are: 1. Do not issue a COMMIT or ROLLBACK command from your PLSQL function, procedure, or package while disabled 2. Enable COMMIT or ROLLBACK for this PLSQL session |
| ORA-00035 | LICENSE_MAX_USERS cannot be less than current number of users | Specified values for LICENSE_MAX_USERS is less than the current number of users | Check the license limit and drop extra users or purchase more licenses |
| ORA-00036 | Maximum number of recursive SQL levels (string) exceeded | An attempt was made to go more than the specified number of recursive SQL levels | Remove the recursive SQL, possibly a recursive trigger |
| ORA-00037 | Cannot switch to a session belonging to a different server group | An attempt was made to switch to a session in a different server group. This is not allowed | Make sure the server switches to a session that belongs to its server group |
| ORA-00038 | Cannot create session: server group belongs to another user | An attempt was made to create a non-migratable session in a server group that is owned by a different user | 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-00039 | Error during periodic action | An unexpected error occurred while executing a periodically invoked | Check the error stack for detailed error information |
| ORA-00040 | Active time limit exceeded - call aborted | The Resource Manager SWITCH_TIME limit was exceeded | Reduce the complexity of the update or query, or contact your database administrator for more information |
| ORA-00041 | Active time limit exceeded - session terminated | The Resource Manager SWITCH_TIME limit was exceeded | Reduce the complexity of the update or query, or contact your database administrator for more information |
| ORA-00042 | Unknown Service name string | An attempt was made to use an invalid application service | Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package |
| ORA-00043 | Remote operation failed | Execution of the inter-instance operation failed | Check the status of the target instance. The operation may have partially executed. Verify the result of the intended operation |
| ORA-00044 | Message 44 not found; product=RDBMS; facility=ORA | ||
| ORA-00045 | Message 45 not found; product=RDBMS; facility=ORA | ||
| ORA-00046 | Message 46 not found; product=RDBMS; facility=ORA | ||
| ORA-00047 | Message 47 not found; product=RDBMS; facility=ORA | ||
| ORA-00048 | Message 48 not found; product=RDBMS; facility=ORA | ||
| ORA-00049 | Message 49 not found; product=RDBMS; facility=ORA | ||
| ORA-00050 | Operating system error occurred while obtaining an enqueue | Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low | Look up the operating system error in your system documentation and perform the needed action |