Previous |
Next |
After you have generated the offline instantiation scripts by completing the Template Script Generation Wizard, your scripts are stored on the same computer where you ran the wizard. If you plan to use online instantiation, then you generated scripts using the replication management API.
The Template Script Generation Wizard generated the following scripts:
One setup script. The default name for this setup script is TEMPLATE
_setup.sql
, where TEMPLATE is the name of the deployment template.
One or more template scripts. One script is generated for each user in the template. The default name for each template script is TEMPLATE_clientdb.sql
, where TEMPLATE is the name of the deployment template and clientdb
is the name of the database on the client.
One refresh script. All of the materialized views created by the template scripts are in the same refresh group. Therefore, all users can share the same refresh script. Also, because all of the materialized views are in the same refresh group, refreshing the refresh group refreshes all of the materialized views created by the deployment template. The default name for this refresh script is TEMPLATE_refresh.sql
, where TEMPLATE is the name of the deployment template.
After you have generated the online or offline instantiation scripts, you need to distribute these scripts to the target end-users. You can distribute the scripts by posting them to an FTP or web site or by saving the script to some storage medium (CD-ROM, floppy disk, and so on). Each user needs an instantiation script to build the materialized view environment at the remote site.
Instantiation scripts are required for online and offline instantiation at all of the following types of remote sites: Oracle Enterprise Edition, Oracle Standard Edition, and Oracle Personal Edition.
For instantiation instructions, see Instantiate at a Remote Materialized View Site if your clients are using Oracle Enterprise Edition, Oracle Standard Edition, or Oracle Personal Edition.