Applications → Managing Fields → About Fields → Invalid and Restricted Field Names
This topic describes field names that cannot be used in SBM Composer.
The following fields are considered invalid database names, so they cannot be used for non-system fields or non-Sub-Relational fields:
ACCESS, ADD, ALL, ALTER, AND, ANY, ARRAYLEN, AS, ASC, AUDIT, BETWEEN, BY, CHAR, CHECK, CLUSTER, COLUMN, COMMENT, COMPRESS, CONNECT, CREATE, CURRENT, DATE, DECIMAL, DEFAULT, DELETE, DESC, DISTINCT, DROP, ELSE, EXCLUSIVE, EXISTS, FILE, FLOAT, FOR, FROM, GRANT, GROUP, HAVING, IDENTIFIED, IMMEDIATE, IN, INCREMENT, INDEX, INITIAL, INSERT, INTEGER, INTERSECT, INTO, IS, LEVEL, LIKE, LOCK, LONG, MAXEXTENTS, MINUS, MODE, MODIFY, NOAUDIT, NOCOMPRESS, NOT, NOTFOUND, NOWAIT, NULL, NUMBER, OF, OFFLINE, ON, ONLINE, OPTION, OR, ORDER, PCTFREE, PRIOR, PRIVILEGES, PUBLIC, RAW, RENAME, RESOURCE, REVOKE, ROW, ROWID, ROWLABEL, ROWNUM, ROWS, START, SELECT, SESSION, SET, SHARE, SIZE, SMALLINT, SQLBUF, SUCCESSFUL, SYNONYM, SYSDATE, TABLE, THEN, TO, TRIGGER, UID, UNION, UNIQUE, UNUSED, UPDATE, USER, VALIDATE, VALUES, VARCHAR, VARCHAR2, VIEW, WHENEVER, WHERE, WITH
SBM Composer checks for "reserved" database names for non-system fields that have never been published. If any are found, validation fails.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.