Databases Wizard (DB2 LUW)

From DBArtisan
Jump to: navigation, search

Go Up to IBM DB2 for Linux, Unix, and Windows Object Wizards

The Database Wizard lets you create a database (a structured collection of data that can be updated or queried) without knowing the underlying commands. Databases can be simple, that is one file with many records and the same fields, or much more complicated with multiple files with different fields.

To open the IBM DB2 for Linux, Unix, and Windows Database Wizard

On the Registration tool bar, click New UDB Database.
OR
On the Navigator/Explorer, right-click an instance node or the Datasources node, and then click New UDB Database.

The tables below describe the fields you may encounter as you complete the wizard.

Naming the New Database

Required Information Description

What is the name of the database?

Each database requires a unique name. The database name should be between 1 - 8 characters and must begin with a letter A-Z. It’s wise to avoid the symbols @, #, and $ if the database will exist in a communications environment or be summoned from an area where those characters do not exist in the language (and hence, on a keyboard).

What is the datasource name for the new database?

Each datasource should have a unique name. This is the name that will appear on the Navigator/Explorer.

What is the alias name of the database.

OPTIONAL: A database alias is the local synonym given to the database you are creating, and must be unique. If you don’t assign an alias, the database name becomes the default alias. Note that a DB2 client can have connections to two different databases with the same name if those databases live on different servers and each database has its own alias.

What is the comment used for the database?

OPTIONAL: Lets you type a comment up to 30 characters. Any comment you enter can be changed later.

Drive Path and Parameters

Required Information Description

On what drive/path will the database reside?

OPTIONAL: Leave blank if you want to create the database using the DFTBPATH (default database path configuration) parameter.

What default tablespace parameters should be used?

OPTIONAL Extent size: This is the number of pages of table data that will be written before data is written to the next container.

Number of segments: The default is 0. The number you designate specifies the number of extended memory segments available for the database to use. You should only set this number if you have a large amount of real memory.

What global default parameters should the database use?

Territory: The territory where the database was created. This is purely informational, for example, en_US and is related to region-specific support. Codeset: IBM-1252 or UTF-8 are the options for language support. Collating Sequence: Compatibility, Identity, System are your choices for comparing character data. Note: The collation sequence can’t be changed after the database has been created.

Finish

Opens the Preview SQL dialog.

Add Catalog/Temporary/User Containers

There are three distinct wizard panels, one for each container type, that enable you to customize your database. Click Next or Finish depending on how you want to proceed.

Required Information Description

What container(s) will be used to store the catalog/temporary tables?

Use System Managed Space: If you select this option, the operating system’s file system manager allocates and manages the space where the catalog tables are stored. This is the default. Use Database Managed Space: If you select this option, the database manager controls the storage space for catalog tables. Add or Edit - For details, seeAdd/Edit Container for Tablespace.

What optional default storage parameters should be used.

Optionally identify values for extent size, pre-fetch size, transfer rate, and overhead.

Finish

Opens the Preview SQL dialog.

Add/Edit Container for Tablespace

The table below describes the options and functionality on this dialog:

Required Information Description

Container Parameters

These parameters are enabled for modification only if you have opted to use database managed space. When enabled, you can either indicate file size parameters or specify device information.

Directory

Identify the directory where the catalog table container will be stored.

File Name

Identify a name for the file where the catalog table container will be stored.

Device Information

Enable either raw partition and type a value, or raw drive, and select a value.