Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see High-speed Apply Engine 13.1.

Considerations for Oracle targets

This section describes requirements and considerations for using the High-speed Apply Engine for Oracle on the UNIX and Windows platforms.

For more information about installing High-speed Apply Engine, see Installing-High-speed-Apply-Engine-on-UNIX-or-Windows.

Operational considerations for Oracle targets

When you use High-speed Apply Engine, consider these constraints and recommendations:

  • For optimal performance, High-speed Apply Engine should be installed on the Oracle server that contains the target tables.
  • File names that use mixed case or lowercase are processed exactly as they appear. If your system is case-sensitive, be sure to specify the file names in the appropriate case. For more information, see Data-set-and-file-names-in-configuration-files.
  • Table names that use mixed case or lowercase must be delimited by quotation marks. For more information, see Object-names-in-configuration-files.
  • Unless the target Oracle database allows automated login, you must provide a user ID and password as part of the configuration. For more information about specifying these values, see Login.
  • The user ID that submits the apply request must have appropriate privileges on the target tables. For more information, see Oracle authorizations.
  • The value that you specify for the MaxPrepares parameter cannot exceed the value of the OPEN_CURSORS initialization parameter for your Oracle session. If you specify a value that is greater than OPEN_CURSORS, High-speed Apply Engine uses the OPEN_CURSORS value.

Database access for Oracle targets

Using information from the configuration files and the apply request, the High-speed Apply Engine updates the Oracle target tables. The database can continue to run while High-speed Apply Engine performs its updates, so you can update the target tables while they are online.

High-speed Apply Engine uses the Oracle Call Interface (OCI) to access Oracle databases. For some operations (such as dynamically determining the version of the Oracle client), High-speed Apply Engine uses the SQL*Plus application. The directory that contains SQL*Plus must be included in the PATH for the system, so that High-speed Apply Engine can run the program.

Oracle authorizations

To run the High-speed Apply Engine you must have the following Oracle authorizations:

  • Table privileges (INSERT, UPDATE, or DELETE) on the target tables
  • Table privileges (INSERT, UPDATE, DELETE, and SELECT) on the restart table

These authorizations can be granted during installation or after, but you must have these authorizations before you can run High-speed Apply Engine. The privileges that High-speed Apply Engine requires depend on the transactions that the apply request performs on the target tables.

Oracle data type support

The High-speed Apply Engine supports the same SQL data types and data type conversions as Oracle. For more information about compatible data types, consult the appropriate Oracle documentation.

If you want to create logical partitions for your target tables, be aware of some restrictions on the data types and functions that can be used as partition keys. For more information, see Considerations-for-Oracle-data-types.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*