The dblook utility generates all of the following
objects when generating the DDL for a database.
- Checks
- Functions
- Indexes
- Jar files
- Keys (primary, foreign, and unique)
- Schemas
- Stored procedures
- Triggers
- Tables
- Views
- Roles
- User-defined types
- User-defined aggregates
When
dblook runs against a database that has jar files
installed, it creates a new directory, called
DERBYJARS,
within the current directory, where it keeps copies of all of the jar files it
encounters. In order to run the generated DDL as a script, this
DERBYJARS directory must either
- Exist within the directory in which it was created, or
- Be moved manually to another directory, in which case the path in the
generated DDL file must be manually changed to reflect to the new location
The dblook utility ignores any objects that have system
schemas (for example, SYS), since DDL is not able to directly create or modify
system objects.