Data Exporter

• The Data Exporter can be configured to run as any Oracle Waveset administrator with the appropriate capabilities. The export task runs as a daemon, and is started and monitored by the Oracle Waveset scheduler. Audit records created by the Data Exporter will show the subject of the Oracle Waveset scheduler (Scheduler:IDMServer), rather than the subject the task is configured to use. (ID-18055)

• Forensic query does not support Edit/Modify actions against role types. (ID-18769)

• Users of Data Exporter must be aware of the following performance issues: After warehouse model configuration has been written, Data Exporter will not re-examine warehouse interface code. If you modify the warehouse interface code to add extended user attributes, these new attributes do not appear in the Configure -> Warehouse -> Warehouse Model Configuration (Model -> Attributes tab), and consequently do not appear for use within the Forensic Query interface. (ID-18975)

  You will see this problem when you configure your warehouse and afterward try to add custom attributes for export. The initial warehouse configuration looks at the WIC code and writes the Configuration -> Data Warehouse Configuration object. Subsequently, Data Exporter does not re-examine the WIC code.

  Subsequent warehouse upgrades with new versions of Oracle Waveset also experience this problem.

• When exporting data to the data warehouse, if the number of records being exported exceeds the 'Repository Read Limit', the exporter may write data to the warehouse more than once even when the 'Export Once' flag has been set.

  Workaround:

  • Increase the blockRowsList property of the RepositoryConfiguration object from the default of 10000 to a larger value. For example 50000 or 100000. Try to use the lowest value possible as returning large numbers of entries in one batch will increase memory consumption by the server. It may also be necessary to increase the JVM heap in order to accommodate the increase in batch size and therefore some testing should be done based on the new value.

  • Reduce the Repository read limit value within the Data Warehouse Task Configuration from the default of 250000 to the value you've specified for the blockRowsList property above. This will ensure that during an export Oracle Waveset does not attempt to read more entries from the repository than can fit within a single batch.