Federated queries can read record array data if you create a separate table for each array. You can insert, update, delete, and capture changes to record array data by flattening the column structure.
Record array definitions contain column definitions, and possibly additional record array definitions. To read, manipulate, or capture changes to record array data, create the required tables or column structure.
To query record array data, map a separate table for each record array in the data definition. To insert, update, or delete array data, flatten the array structure by choosing the array processing option Expand occurrences when you map the table in the New Table wizard.
A flattened structure provides a separate column for each array instance and field. For example, you map a record array for employee dependents that contains five fields:
If you want to support up to ten dependents, you must map 50 columns with names that uniquely identify each instance and field. In this example, the column names range from DEP_LAST_NAME_1 to DEP_DOB_10.
Change capture
Flatten the structure of a table to capture changes to array data.
You cannot map record array definitions for change capture. An ALTER TABLE statement on a table containing array structures mapped as arrays will fail, because change capture must send one notification per change. The mapping must return exactly one row per physical record to provide an accurate notification to consuming applications.