Scripts Produced by the Copy Database Operation
When you perform the copy database operation, the following two scripts are produced:
copy.out
The copy.out script contains query language statements to copy your tables to operating system files. The script contains a copy statement for each table being copied
copy.in
The copy.in script contains query language statements to recreate your tables, views, procedures, and associated indexes, permissions, and integrities, and copy the table’s data from the operating system files into a database.
To copy the tables out of the database, you run the copy.out script. To copy them into the same or another database, you run the copy.in script.
If you specify a particular table or view, the copy.in script contains statements to recreate the specified table or view only (along with applicable permissions and so on). The script does not contain statements to create all tables, views, and procedures.
Ingres tables can also be copied into XML format, as described in
Generate XML and Import XML Operations.
Reloading Order
When using the copy.in script, database objects are reloaded in the following order:
• Users, groups, and roles (only when recreating the iidbdb)
• Tables
ALTER TABLE statements are used as needed for deferred creation of referential integrities.
• Data
• Table permissions
Permissions are recreated to the original time stamp order, and can or cannot be those of the table owner (depending on the grant options for the table).
• Indexes, index modifications, and integrities
• Views and related permissions
Like tables, these are recreated to the original time stamp order.
• Synonyms
• Database procedures and related permissions
Procedures depend on tables, views, events, and synonyms. Procedures can also see other procedures. To handle reloading of procedures, two passes are made during the unload database process through the iiprocedures catalog (see
iiprocedures Catalog).
• Comments
Last modified date: 08/28/2024