OPEN ALLOWING READERS is not supported by Oracle. You determine in your runtime configuration file how this phrase will be interpreted. Set the variable STRENGTHEN-LOCKS to 1 (one) to cause this phrase to be treated as OPEN ALLOWING NO OTHERS. Set the variable to 0 (zero) to cause the phrase to be treated as OPEN ALLOWING ALL. The default value is 0.
Transactions are enforced in Oracle. Within a transaction, records locked by I/O operations that modify, delete, or otherwise result in a COBOL record-lock, will remain locked until a COMMIT WORK or a ROLLBACK WORK is issued, or until your COBOL program encounters a COMMIT or ROLLBACK verb. See the description of the COMMIT-COUNT configuration variable in Oracle: Configuration File Variables section.
Oracle does not support record encryption, record compression, or alternate collating sequences. You may include these options in your program; they will be disregarded if they are specified.
The ACUCOBOL-GT utility program vutil cannot be used with Oracle files. Instead, use utilities supplied by Oracle.
Whenever you are using the library routine RENAME, you must specify that you are using indexed files. This information is passed by the value I in the fourth parameter.
Unless you have DBA privileges, or special privileges provided by Oracle Version 7.3.3, you can't:
1) delete a table you don't own, or
2) create a table under another user's name