Database Views

There are internal, private database views used by the components and external, public database views for use by customer applications. Each component that has public database views has them documented in the same DDL scripts that create the views. These DDL scripts are located in the same directory as the other DDL scripts for that component.

Note: Do not use the private views or tables to access data. They are for internal component use only and subject to change between releases.

By default, public views are defined using the database schema name FTMPUB. Check with the database administrator for the correct schema name to use.

To access the data, use standard SQL select statements against the views. Some SQL guidelines for using the views are:

To avoid database table access contentions, use "WITH UR" for uncommitted reads
When using even a select statement, perform a commit as soon as possible. For more information about when commits can be executed, see Holdability.
Try to avoid "like" functions in WHERE clause statements since they cause table scans instead of using the index. A table scan impedes performance. Some "like" functions are LOCATE_IN_STRING, SUBSTR, LOCATE, and INTEGER.