1. If a <table name> is specified without an <owner> and if there is no private table of the user with the name <table name>, the behavior of ADABAS differs from that of ORACLE.
2. In ADABAS, numbers are not implicitly converted into date values or vice versa. Character strings are converted into numeric values, or vice versa, in application programs for comparisons or when variables are used. The arguments of functions are not implicitly converted.
3. When two character strings are compared in ADABAS, the shorter one is filled with blanks (code attribute ASCII or EBCDIC) or binary zeros (code attribute BYTE) up to the length of the longer character string. This is not done in ORACLE.
4. The range of values of numbers in ADABAS is between -9.99999999999999999E+62 and -1E-64 and between +1E-64 and +9.99999999999999999E+62. In ORACLE, the range comprises values between 0.999E-128 and 0.999E126.
5. ADABAS does not know a National Language Support; i.e., it does not know the corresponding functions nor the corresponding parameters in other functions.
6. The NULL value and the empty <string literal>, or <string literal>s only containing blanks are different in ADABAS.
7. In ADABAS, numbers cannot end with a 'K' or 'M'.
8. Date values in ORACLE are between 01-01-4712 BC and 12-31-4712 AC. In ADABAS, date values can be between 01-01-0001 and 12-31-9999.
9. The pseudo column LEVEL is not supported in ADABAS.
10. The functions:
NLSSORT
CHARTOROWID
ROWIDTOCHAR
CONVERT
DUMP
USERENV
NLS_INITCAP
NLS_LOWER
NLS_UPPER
TO_MULTI_BYTE
TO_SINGLE_BYTE
INSTRB
LENGTHB
SUBSTRB
are not provided in ADABAS.
11. In ADABAS, the pseudo column ROWNUM cannot be used in <update columns and values> of the <update statement>.
12. In ADABAS, a correlated subquery is not allowed for a <subquery> in a <set update clause>.
13. A <set update clause> of the format <column name> Names,... = <subquery> is not available in ADABAS.
14. The pseudo column ROWID is not supported in ADABAS.
15. The pseudo column ROWNUM is entered into the <select column> after sorting the result table.
16. The specification of CONNECT BY <search condition> [ START WITH <search condition> <search condition>~] is not available in ADABAS.
17. The specifications for the <connect statement> to be made in addition to the user name and password differ in ADABAS and ORACLE.
18. The effects of the <lock spec> in the <lock statement> partially differ in ORACLE and ADABAS.
19. In contrast to ORACLE, read and write operations performed on a table in the ISOLATION LEVELs 1, 2, and 3 can collide in ADABAS.
20. In ADABAS, locks are not released by a <rollback to statement>.
21. FORCE or COMMENT cannot be specified with the <connect statement> or <rollback statement>.