Resizing the Teradata Database with DBSIZEFILE - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

To resize a database during a restore operation, use the DBSIZEFILE option. DBSIZEFILE is valid only when restoring one of the following:

  • Database DBC by itself
  • '(DBC) ALL'

The option, 'DBSIZEFILE=filename', prompts Teradata ARC to read the file indicated by filename.The file specifies the perm space size for each specified database or user. The format is one or more pairs that indicate each of the following:

  • Database or user name
  • Perm space size

Each name and size pair must appear on a separate line. Specify the new size in bytes, for example:

'database_name1 5000000'
‘foo_database 3000000’
‘user1 1000000’

The following table lists requirements for the file specified by filename.

File Characteristics 
File Characteristics
File Extension
The file extension must be:
  • Valid for the operating system
  • Valid on the statement

When specifying one or both of the following as part of the file name, enclose the entire file name in double quotes:

  • A file extension
  • Path

EXAMPLE

dbsizefile="<path>filename.extension"
Perm Space
The perm space amount can be any value. This is useful when reducing the size of a source database or user, which may have unused perm space. When the source database or user is restored to a target system, it fits within the target system's perm space.
File Location
Store the file anywhere on the system where Teradata ARC is running. Teradata ARC must have the appropriate permissions to access the file.
Quotation Marks and Parentheses
Do not use quotation marks or parentheses to enclose the name and size pair. If specified with the name, the quotation marks or parentheses are included and used as part of the name.
Spaces
  • Only spaces are considered whitespace. Other non-printable characters are valid characters.
  • A space delimits each element of the name and size pair, plus any comments at the end of the line.
  • In the areas where space acts as a delimiter, any number of consecutive spaces are valid.
Special Characters
When including special characters in the name, use the escape character '\', plus the special characters. Valid special characters include, but are not limited to:
  • '\ '

    insert a single space

  • '\\'

    insert a single '\' character

  • '\#'

    insert a single '#' character

  • '\a'

    insert a single 'a' character (this can be any alphabetic character)

  • '\*'

    insert a single '*' character

The value of the perm size can include commas, however their positioning in the value will not be validated. ARC strips all commas to form a single number without any commas.

The value of the perm size can be specified fully, or in exponential format (for example, '123000000' or '123E6').

File Comments
  • Begin a comment with '#' (without the '\' character).
  • No character is required to end a comment.
  • A comment can start at the beginning of a line (the entire line would be a comment), or after the name and size pair (the rest of the line would be a comment).
  • Comments do not wrap to the next line. However, multiple line comments are valid if each comment line begins with '#'.

Teradata ARC restores DBC first, then resizes it according to the perm value stored in the file. After the resize operation is completed, the restore job continues restoring and resizing, starting with database SYSUDTLIB.

If Teradata ARC encounters errors while preparing to resize (for example, read errors on the file, errors in syntax on the resize file contents, or any problems in communications with the Teradata Database), it aborts the Teradata ARC restore job. Correct the errors and resubmit the job.

After Teradata ARC starts the resize operation, it reports but ignores any errors that it encounters (for example, missing privileges or database not found). Teradata ARC attempts all resize requests and reports those results. If there was a resize failure, the restore operation will fail again at a later point if enough perm space is still not available. If this occurs, manually resize the user or database that failed or correct the errors causing the resize failures. Resubmit the restore job.