Recommendations for Fusion Middleware Components 2-31
Managed Recovery mode, then you should manually synchronize the standby database.
Recovery Recommendations The databases containing the Oracle Portal schemas must be recovered to the most
recent point in time. The Managed Server running the Oracle Portal application and the Oracle instance must be restored.
2.6.2 Recommendations for Oracle Forms
Oracle Forms is Oracles long-established technology to design and build enterprise applications quickly and efficiently.
This section describes artifacts that are unique to Oracle Forms and provides recommendations for disaster recovery.
Artifacts in the Database Any user configured databases for the Oracle Forms applications.
Special Considerations Load balancer virtual hosts for accessing Oracle Forms should be configured on both
the production and standby sites
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making configuration changes, deploying applications, and applying patches.
Oracle Data Guard should be configured for the user configured application databases.
It is recommended that the standby database be synchronized when the application tier synchronization is initiated on the storage. This synchronization occurs
automatically because Oracle Data Guard is configured in Managed Recovery mode the recommended configuration for the database. If the standby database is not in
Managed Recovery mode, then you should manually synchronize the standby database.
Recovery Recommendations The Managed Server running the Oracle Forms application and the Oracle instance
must be restored. If there are any user configured databases, they must be recovered to the most recent point in time.
2.6.3 Recommendations for Oracle Reports
Oracle Reports is the reports publishing component of Oracle Fusion Middleware. It is an enterprise reporting service for producing high quality production reports that
dynamically retrieve, format, and distribute any data, in any format, anywhere. You can use Oracle Reports to publish in both Web-based and non-Web-based
environments.
This section describes various Oracle Reports artifacts and provides recommendations for disaster recovery.
2-32 Oracle Fusion Middleware Disaster Recovery Guide
Artifacts on the File System Reports home: This is a user defined location that contains the Report definition files.
This may also be under the Oracle instance or Oracle home.
Artifacts in the Database Oracle Reports can be configured to store job-related information, such as scheduled
job data, past job data, or job status data in a database. This is a user-configured database.
Special Considerations Load balancer virtual hosts for accessing Oracle Reports should be configured on both
the production and standby sites.
Synchronization Recommendations The application tier must be manually synchronized with the standby site after
making configuration changes and applying patches.
If the Reports Server is configured to store configuration or user information in other components like Oracle Portal and Oracle Internet Directory, make sure to synchronize
these components between the production and standby sites as well.
Oracle Data Guard should be configured for Oracle Reports databases. It is recommended that the standby database be synchronized when the application
tier synchronization is initiated on the storage. This synchronization occurs automatically because Oracle Data Guard is configured in Managed Recovery mode
the recommended configuration for the database. If the standby database is not in Managed Recovery mode, then you should manually synchronize the standby
database.
Recovery Recommendations The Managed Server running the Oracle Reports application and the Oracle instance
must be restored. If there are any user configured databases, they must be recovered to the most recent point in time. Also recover any associated Oracle Portal and Oracle
Internet Directory instances.
2.6.4 Recommendations for Oracle Business Intelligence Discoverer
