IBM 000-8697 Contents of the Schema File

Utilities 7-9
Contents of the Schema File
Contents of the Schema File
The .sql file contains the SQL statements needed to re-create the exported
database, as well as some additional ownership and privilege information.
The schema file does not retain all the information that might have been
included in the original statements used to create the database and tables.
The following information is omitted:
■Initial and next extent values
■Lock mode
■Dbspace where the table should reside
■Blobspace where a blob column should reside
■Logging mode of the database, if there is one
Initialor next extent sizes are not retained in the .sql file statements. If you do
notedit the .sql file CREATE TABLE statements before you run dbimport, the
tableswill be created with the default extent sizes of eight pages. If you want
to change the extent sizes after the database is imported, use the ALTER
TABLE statement.
Thelock mode of the table is not retained in the .sql file statements. If you do
notedit the .sql file CREATE TABLE statements before you run dbimport, the
tablewill be created with the default lock mode, which is page-level locking.
If you want to change the lock mode after the database is imported, use the
ALTERTABLE statement.
The logging mode is not retained in the.sql file. You can specify any one of
three options when you import the database usingdbimport:
■ANSI-compliant database with unbuffered logging
■Unbuffered logging
■Buffered logging
Ifyou want to change the logging mode of the database and do not specify a
logging option in thedbimport command line, you can make the change
fromDB-Monitor after the database is imported. Refer to page 7-14 for more
details about starting logging from thedbimport command line.