Main Menu

Resources

Resources

Random Errors

ORA-00152: current session does not match requested session

Cause: The current session is not the same as the session that was passed into a upixado() call.

Action: Check your application.

Random Errors

ORA-00134: invalid DISPATCHERS specification #string

Cause: The syntax for the n-th DISPATCHERS specification was incorrect.

Action: Refer to the Oracle Reference Manual for the correct syntax.


Designed by:
SiteGround web hosting Joomla Templates
Kody błędów
articles.jpg

 

Oracle Error Codes category contains full list of Oracle RDBMS errors supplied in Oracle documentation. Each error is divided in 2 sections CAUSE and ACTION.

 
Filter     Display # 
# Article Title
1 ORA- 30075 TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
2 ORA-00001: unique constraint (string.string) violated
3 ORA-00017: session requested to set trace event
4 ORA-00018: maximum number of sessions exceeded
5 ORA-00019: maximum number of session licenses exceeded
6 ORA-00020: maximum number of processes (string) exceeded
7 ORA-00021: session attached to some other process; cannot switch session
8 ORA-00022: invalid session ID; access denied
9 ORA-00023: session references process private memory; cannot detach session
10 ORA-00024: logins from more than one process not allowed in single-process mode
11 ORA-00025: failed to allocate string
12 ORA-00026: missing or invalid session ID
13 ORA-00027: cannot kill current session
14 ORA-00028: your session has been killed
15 ORA-00029: session is not a user session
16 ORA-00030: User session ID does not exist.
17 ORA-00031: session marked for kill
18 ORA-00032: invalid session migration password
19 ORA-00033: current session has empty migration password
20 ORA-00034: cannot string in current PL/SQL session
21 ORA-00035: LICENSE_MAX_USERS cannot be less than current number of users
22 ORA-00036: maximum number of recursive SQL levels (string) exceeded
23 ORA-00037: cannot switch to a session belonging to a different server group
24 ORA-00038: Cannot create session: server group belongs to another user
25 ORA-00050: operating system error occurred while obtaining an enqueue
26 ORA-00051: timeout occurred while waiting for a resource
27 ORA-00052: maximum number of enqueue resources (string) exceeded
28 ORA-00053: maximum number of enqueues exceeded
29 ORA-00054: resource busy and acquire with NOWAIT specified
30 ORA-00055: maximum number of DML locks exceeded
31 ORA-00056: DDL lock on object 'string.string' is already held in an incompatible mode
32 ORA-00057: maximum number of temporary table locks exceeded
33 ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
34 ORA-00059: maximum number of DB_FILES exceeded
35 ORA-00060: deadlock detected while waiting for resource
36 ORA-00061: another instance has a different DML_LOCKS setting
37 ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
38 ORA-00063: maximum number of LOG_FILES exceeded
39 ORA-00064: object is too large to allocate on this O/S (string,string)
40 ORA-00065: initialization of FIXED_DATE failed
41 ORA-00066 LOG_FILES is string but needs to be string to be compatible
42 ORA-00067: invalid value string for parameter string; must be at least string
43 ORA-00068: invalid value string for parameter string, must be between string and string
44 ORA-00069: cannot acquire lock -- table locks disabled for string
45 ORA-00070: command string is not valid
46 ORA-00071: process number must be between 1 and string
47 ORA-00072: process "string" is not active
48 ORA-00073: command string takes between string and string argument(s)
49 ORA-00074: no process has been specified
50 ORA-00075: process "string" not found in this instance
 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
Page 1 of 139

Random Errors

ORA-00155: cannot perform work outside of global transaction

Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.

Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.

 

Resources

Latest

Most popular

Oracle Database Support, Powered by Joomla! and designed by SiteGround web hosting