Using Oracle with BMC Remedy AR System
Diary and Character field qualifications
When specifying search criteria, you cannot use diary fields or character fields that contain more than 4000 characters. The database system does not support qualifications on these field types. If you specify a qualification for one of these field types, you receive an error.
When the Oracle-Search-On-Clob setting option in the AR System Configuration Generic UI form is set to true (the default), you can perform a string search (without wildcards) on these field types. For more information, see Configuration-settings-N-R.
For searches on database entries, the only wildcard character supported in the LIKE comparison is the percent symbol (%). There is no support for sets or ranges of values.
When used with the LIKE operator, the underscore (_) character cannot function as a wildcard or as literal text.
Wildcards are fully supported in filter, escalation, and active link qualifications and in pattern specifications for character fields.
Case sensitivity in queries
By default, the Oracle database is case sensitive. To enable a case-insensitive search for fixed-length text fields in BMC Remedy AR System server that uses an Oracle database, see Oracle case-insensitivity in Tuning the Oracle database server in BMC Remedy ITSM Deployment documentation.
JDBC query with LPAD and RPAD functions
When using an Oracle database, if you use a JDBC query with the LPAD and RPAD functions, the following error occurs: