1. In ADABAS, there are usergroups, so that it may happen that the <owner> of an object is not a user but a usergroup.
2. In ADABAS, a user can only create and delete database objects for himself or for his usergroup, and he can create database objects which are not assigned to a particular user (e.g., indexes). It is not possible to create database objects for other users.
3. In contrast to ORACLE, tables of a user are in a namespace. Sequences, procedures and functions build separate namespaces. Indexes and constraints in ADABAS must have unique names within a table.
4. In contrast to ORACLE, DBAs in ADABAS are also subject to the privileges concept and cannot execute any DDL statements (e.g., CREATE INDEX) or DML statements (e.g., DELETE) for which they have not received the corresponding privileges.
5. Numbers have only 18 significant digits in ADABAS, instead of 38.
6. While ORACLE distinguishes names of up to 30 characters in length, only 18 characters are significant in ADABAS.
7. The indication of a database link for a <table name> specification is neither possible nor required in ADABAS.
8. The following key words are not reserved in ADABAS:
ACCESS
COMPRESS
ELSE
FILE
IF IMMEDIATE INCREMENT INITIAL
MAXEXTENTS
NOAUDIT NOCOMPRESS
OFFLINE ONLINE
PRIOR
SESSION SIZE START SUCCESSFUL
THEN
VALIDATE
9. In contrast to ORACLE, a <fixed point literal> in ADABAS can begin or end with a '.'
10. In ADABAS, LONG columns can be specified in the <null predicate>.
11. The following <sql statement>s are not available in ADABAS:
ALTER / CREATE / DROP CLUSTER
CREATE CONTROLFILE
ALTER / CREATE DATABASE
CREATE / DROP DATABASE LINK
ALTER / CREATE / DROP FUNCTION
ALTER INDEX
VALIDATE INDEX
ALTER / CREATE / DROP PACKAGE
ALTER / CREATE / DROP PROCEDURE
ALTER / CREATE / DROP PROFILE
ALTER RESOURCE COST
ALTER / CREATE / DROP / SET ROLE
ALTER / DROP ROLLBACK SEGMENT
ALTER SEQUENCE
ALTER SESSION
ALTER SNAPSHOT
ALTER SNAPSHOT LOG
ALTER SYSTEM
ALTER / DROP TABLESPACE
ALTER / CREATE / DROP TRIGGER
ALTER USER
ALTER VIEW
ANALYZE
AUDIT
NOAUDIT
EXPLAIN PLAN
RENAME
SET TRANSACTION
12. Columns with the data type CHAR and with a length less than or equal to 30 characters are stored with a fixed length in ADABAS, not with a variable length as in ORACLE.
13. In ADABAS, the code attribute of a column of the data type CHAR, VARCHAR or LONG is determined by the code attribute specified during the configuration which should, but need not, correspond to the character set of the computer.
14. In ADABAS, data types cannot be defined for numbers with a negative scale. It is not possible to specify a scale that is greater than the number of significant digits.
15. In ADABAS, the possible maximum number of significant digits is always used for the data type FLOAT.
16. In ADABAS, a <constraint definition> defined in a <column definition> can also refer to several columns of the table.
17. In ADABAS, constraints cannot be deactivated temporarily.
18. The specification of the <oracle option>s in the <create table statement> and <create index statement> has no effect in ADABAS.
19. In contrast to ORACLE, tables for which no PRIMARY KEY was defined contain the key column SYSKEY in ADABAS. This column can be specified in a <select column> and in the <search condition> and its value cannot be changed. User-defined key columns can be changed in ADABAS.
20. For a <drop table statement> or <drop view statement>, all objects, synonyms, and view tables belonging to this table are deleted in ADABAS, not only marked as not being usable.
21. A <create synonym statement> is not possible for sequences, procedures or functions. The object for which the synonym is defined must exist and the current user must have at least one privilege for it.
22. In ADABAS, a time for an automatic refresh cannot be specified during the definition of snapshot table. An automatic refresh of a snapshot table is not possible.
23. In ADABAS, an index cannot be defined across a cluster.
24. In ADABAS, an index in descending order is created when DESC has been specified.
25. In ADABAS, an <index name> may only be unique together with a <table name>. In contrast to ORACLE, non-unique <index name>s require the specification of the corresponding <table name> in the <drop index statement>.
26. PUBLIC synonyms cannot be created and deleted in ADABAS.
27. The <sql statement>s
CREATE TABLESPACE
CREATE [ PUBLIC ] ROLLBACK SEGMENT
are accepted by ADABAS but have no effect.
28. The <grant statement> in ADABAS corresponds to the ORACLE GRANT (object privileges). The other types of the GRANT are not available in ADABAS. The same is valid for REVOKE.
29. In contrast to ORACLE, it is not possible in ADABAS to grant a user a privilege of two different, other users.