1. Cache Guide
  2. Compatibility Between TimesTen and Oracle Databases
  3. SQL Compatibility
  4. SQL Functions

SQL Functions

TimesTen supports a subset of functions that are supported by the Oracle Database.

  • ABS
  • ADD_MONTHS
  • ASCIISTR
  • AVG
  • CAST
  • CEIL
  • COALESCE
  • CONCAT
  • COUNT
  • CHR
  • DECODE
  • DENSE_RANK
  • EMPTY_BLOB
  • EMPTY_CLOB
  • EXTRACT
  • FIRST_VALUE
  • FLOOR
  • GREATEST
  • GROUP_ID
  • GROUPING
  • GROUPING_ID
  • INSTR
  • LAST_VALUE
  • LEAST
  • LENGTH
  • LOWER
  • LPAD
  • LTRIM
  • MAX
  • MIN
  • MOD
  • MONTHS_BETWEEN
  • NCHR
  • NLS_CHARSET
  • NLS_CHARSET_NAME
  • NLSSORT
  • NULLIF
  • NUMTOYMINTERVAL
  • NUMTODSINTERVAL
  • NVL
  • POWER
  • RANK
  • REPLACE
  • ROUND
  • ROW_NUMBER
  • RPAD
  • RTRIM
  • SIGN
  • SQRT
  • SUBSTR
  • SUM
  • SYS_CONTEXT
  • SYSDATE
  • TO_BLOB
  • TO_CLOB
  • TO_CHAR
  • TO_DATE
  • TO_LOB
  • TO_NCLOB
  • TO_NUMBER
  • TRIM
  • TRUNC
  • UID
  • UNISTR
  • UPPER
  • USER

These TimesTen functions are not supported by Oracle Database:

  • CURRENT_USER
  • GETDATE
  • ORA_SYSDATE
  • SESSION_USER
  • SYSTEM_USER
  • TIMESTAMPADD
  • TIMESTAMPDIFF
  • TT_HASH
  • TT_SYSDATE

TimesTen and the Oracle Database interpret the literal N'\UNNNN' differently. In TimesTen, N'\unnnn' (where nnnn is a number) is interpreted as the national character set character with the code nnnn. In the Oracle Database, N'\unnnn' is interpreted as 6 literal characters. The \u is not treated as an escape. This difference causes unexpected behavior. For example, loading a cache group with a WHERE clause that contains a literal can fail. This can also affects dynamic loading. Applications should use the UNISTR SQL function instead of literals.