The section gives you information on the key features of memory guard and data model properties.
The full set of properties is listed in Configuring Memory Guard & Data Model Properties. The properties enable you to protect against out of memory errors and enhance data processing by setting controls such as:
Maximum data size for reports
Maximum data size for scheduled reports
SQL pruning for unused data set columns
Time out for SQL queries and also for reporting
The following section highlights some of the properties and provides detail on how the system responds to the settings:
The data engine property settings provide additional points to protect your system against out of memory errors.
These include:
Set Maximum Data Size That Can Be Generated by the Data Engine
This property is used only when you generate XML data via data model editor. In a normal report generation scenario, since template is chosen always, memory guard side properties (maximum report data size for online/offline for each template type) take precedence over this property.
Setting maximum data size sets an absolute limit to the data that can be generated from the execution of a data model. This setting applies to both online report requests and to requests submitted through the scheduler. When the size of the file generated by the data engine exceeds the limit, the data engine terminates execution of the data model and throws the exception:
"oracle.xdo.dataengine.diagnostic.XMLSizeLimitException: XML Output (NNNNNNbytes) generated exceeds specified file size limit (NNNNNbytes)..!!!!!!!".
If the report request was submitted through the scheduler, the job will show as failed in the Report Job History page. The exception error noted above displays when you rest your cursor over the status. If the report request was submitted online, the user will get the error "Unable to retrieve the data XML."
Set Maximum Sample Data Size
A sample data set is required for all data models. The sample data is used during template design. Sample data can be generated by the data model editor or uploaded to the data model. Large sample data sets can impact the performance of the design tools.
Set this property to limit the size of the sample data file that can be uploaded to the data model.
Set Automatic Database Fetch Size
This setting calculates and sets database fetch size at run time depending on total number of data set columns and total number of query columns. Setting this property will override the server-level and data model-level database fetch size properties. When set, this property takes effect for all data models and can significantly slow processing time. This setting is recommended for implementations of BI Publisher that frequently process complex queries of hundreds of columns, such as Oracle Fusion Applications implementations. This setting is not recommended for most general implementations of BI Publisher.