Change Permanent Space
Teradata Set uses a formula to automatically calculate the permanent space (also called permspace) required for creating a database. Permanent space calculations are based on the number of objects selected and the space required for creating child databases. However, the amount of space calculated can be more or less than the system can spare. Follow the permanent space messages to correct this situation.
Permanent space requirements can be specified before importing objects from a target system. Change the permanent space allotment to avoid messages about permanent space.
To change the permanent space
Before proceeding, connect to a Teradata Database, and perform an export operation. See “Connect to a Teradata Database” on page 31andChapter 6 “Export Methods and Options”
1 From the Import window, click .
The Change PermSpace dialog box appears.
Note: Existing databases are highlighted in blue. Space cannot be specified for existing databases.
The only editable box is Scale Factor(KB). The only editable column is User Specified Space(KB).
|
Option |
Description |
|
Information |
Information about using the dialog box. |
|
Warnings |
For rows shown in bold, warnings about the database or QCD. |
|
Scale Factor(KB) |
An integral number Teradata SET uses to automatically calculate space required to create the objects in a database. Change Scale Factor(KB) to a number between 1 and 100. The default is 32. Scale Factor(KB) has an effect on the value displayed in the Calculated Space(KB) column. |
|
Databases |
The space requirements for the databases in the left pane (import tree). |
|
Query Capture Databases |
The space requirements for the QCDs in the left pane (import tree). |
|
Database Name or |
The name of the database that will be created during the import operation. Note: The column label (Database Name or Query Capture Database) is determined by whether Databases or Query Capture Databases is selected. |
|
Calculated Space(KB) |
The space required to create the database based on the number of objects selected in the left pane (import tree). This amount includes the calculated or user‑specified space of any child databases. The space requirements for each database are based on the number of tables and objects selected in the left pane (import tree) and the space required for creating child databases. An approximation of the deficit space, determined by comparing the calculated space and the available space, appears in this column. |
|
User Specified Space(KB) |
The calculated space for the new database. If entered, this number overrides the Calculated Space(KB) value. If a discrepancy is found, a warning appears recalculated. If specifying space for a child database, it is considered when calculating the space required for the parent database. Minimum value is 0 KB. Maximum value is 2,097,151 KB. Right‑click in this field for more options. See step 2 and step 3. Note: Space cannot be specified for an existing database. |
|
Available Space (Existing Databases) MaxPerm‑CurrentPerm(KB) |
The available permanent space for the database if it already exists on the system. Existing databases are highlighted in blue. |
|
Parent Database |
The immediate parent database of the database that will be created. |
|
Available or Required Parent Database Space(KB) |
If the parent database does not exist, the projected space required to create the child databases and any objects within the parent database. If the parent database exists, the available space (MaxPerm ‑ CurrentPerm) for the parent database. |
|
Import Parent Database(KB) |
The owner for the databases created during the import operation. This is specified in the Parent Database box of the Import Options dialog box. |
|
Space Available(KB) |
The available space (MaxPerm ‑ CurrentPerm) for the import parent database. |
|
Space Required(KB) |
If Databases is selected, the space required to create the databases. If Query Capture Databases is selected, the space required to create the QCDs. |
Note: Selecting stored procedures in the left pane (import tree) does not affect the permanent space calculation.
2 [Optional] If Databases is selected, right‑click in the User Specified Space(KB) column and choose a command from the shortcut menu.
|
Command |
Description |
|
Check user specified space against child database(s) space |
Determine if the child databases can be accommodated in the user‑specified space. Teradata SET displays a warning if space cannot be accommodated. |
|
Check and update parent database(s) space |
Determine if the user‑specified space for a database can be accommodated by each parent database. If the calculated space for the parent database cannot accommodate the space specified, Teradata SET attempts to update the parent database space. Teradata SET displays a message if either the existing parent or user‑specified database space is insufficient. |
|
Clear user specified space |
Clear the user‑specified space for a database. |
3 [Optional] If Query Capture Databases is selected, right‑click in the User Specified Space(KB) column and choose a command from the shortcut menu.
|
Command |
Description |
|
Check total QCD space against available Parent space |
Determine if there is enough available space in the parent database to accommodate the creation of the QCDs. |
|
Check user specified space against calculated space for QCD |
Check the user‑specified space against the calculated space for a QCD. |
|
Clear user specified space for QCD |
Clear the user‑specified space for a QCD. |
4 Click Recalculate to recalculate the space for each parent database.
Note: The recalculation is based on the amount in the User Specified Space(KB) column, the Calculated Space(KB) column of the child databases, and the current scale factor.
5 Do one of the following:
6 [Optional] Click to start the import operation.