Compatibility features for Oracle

Big SQL provides features that enable applications that were written for an Oracle database to use Big SQL with only minor modifications.

In addition to the Oracle compatibility features that are now generally available in Big SQL, you can use the SQL_COMPAT global variable to activate the following custom Oracle compatibility features:
  • TRANSLATE parameter syntax

    The syntax and semantics of the TRANSLATE function in ORA compatibility mode are different than those in Big SQL. The from-string-exp is the second argument, and the to-string-exp is the third argument. If to-string-exp is shorter than from-string-exp, the extra characters in from-string-exp that are found in char-string-exp (the first argument) are removed; that is, the default pad-char-exp argument is effectively an empty string, unless a different pad character is specified in the fourth argument. For more information, see TRANSLATE scalar function.

  • PL/SQL support
    Attention: Setting of the DB2_COMPATIBILITY_VECTOR registry variable is not recommended in Big SQL. Custom compatibility features should be enabled only by using the SQL_COMPAT global variable.
  • SQL data-access-level enforcement
    Attention: Setting of the DB2_COMPATIBILITY_VECTOR registry variable is not recommended in Big SQL. Custom compatibility features should be enabled only by using the SQL_COMPAT global variable.
  • Oracle database link syntax
    Attention: Setting of the DB2_COMPATIBILITY_VECTOR registry variable is not recommended in Big SQL. Custom compatibility features should be enabled only by using the SQL_COMPAT global variable.