Contents of the schema file that dbexport creates
The dbexport utility creates a schema file. This file contains the SQL statements that you need to re-create the exported database.
You can edit the schema file to modify the schema of the database.
If you use the -ss option, the schema file contains server-specific information, such as initial- and next-extent sizes, fragmentation information, lock mode, the dbspace where each table resides, the blobspace where each simple-large-object column resides, and the dbspace for smart large objects. The following information is not retained:
- Logging mode of the database
For information about logging modes, see the HCL OneDB™ Guide to SQL: Reference.
- The starting values of SERIAL columns
- The dormant window interval values for time series rolling window containers
The statements in the schema file that create tables, views, indexes, partition-fragmented tables and indexes, roles, and grant privileges do so with the name of the user who originally created the database. In this way, the original owner retains DBA privileges for the database and is the owner of all the tables, indexes, and views. In addition, the person who runs the dbimport command also has DBA privileges for the database.
The schema file that dbexport creates contains comments, which are enclosed in braces, with information about the number of rows, columns, and indexes in tables, and information about the unload files. The dbimport utility uses the information in these comments to load the database.
The number of rows must match in the unload file and the corresponding unload comment in the schema file. If you change the number of rows in the unload file but not the number of rows in the schema file, a mismatch occurs.
If you delete rows from an unload file, update the comment in the schema file with the correct number of rows in the unload file. Then dbimport is successful.