16.10 - Running System Initializer - Teradata Database

Teradata Database Support Utilities

prodname
Teradata Database
vrm_release
16.10
created_date
June 2017
category
Configuration
featnum
B035-1180-161K
Running sysinit on a previously initialized Teradata Database system destroys all existing data and deletes all tables.

Starting System Initializer

Start system initializer by typing start sysinit from the Supervisor Window of Database Window or from a comparable Linux command-line console tool, such as cnsterm.

The following message appears:

                          W A R N I N G
This program will destroy all user and dictionary data on the system.
SYSINIT Master AMP Vproc is 0 at 11:25:42 on 04/04/11

If the Teradata Database system is running, sysinit displays:

The DBS is currently running!!!
   SYSINIT cannot execute while the DBS is running.
   Would you like to restart the system without the DBS (YES/NO)?

At the prompt, answer one of the following:

IF you answer... THEN sysinit...
YES
  • sets the Start DBS configuration option to Off.

    The Start DBS setting can also be manually changed using the Control GDO Editor (ctl) utility. It determines whether the database software is started when PDE is started. For more information, see the “Control GDO Editor (ctl)” chapter in Utilities.

  • displays the following message and exits:
       SYSINIT terminated without updating disks.
  • automatically restarts PDE, the low level of Teradata Database, without starting the higher-level DBS database software.

You must start sysinit again when PDE has restarted.

NO displays the following message and exits:
Set the "Start DBS" flag to "Off" using the CTL utility program and restart the system prior to running SYSINIT again.
sysinit terminated without updating disks.

The startup process for Teradata Database involves first starting parallel database extensions (PDE). These extensions create an operating environment that supports the parallel features of Teradata Database. After PDE has started, the Teradata Database DBS software is usually automatically started.

The Start DBS flag can be set to prevent the DBS software from starting after PDE is started. This flag is set using the Control GDO Editor (ctl) utility. For more information about the ctl utility, see the “Control GDO Editor (ctl)” chapter in Utilities.

The following message appears when you restart sysinit:

                              W A R N I N G
This program will destroy all user and dictionary data on the system.

A display indicating the console AMP vproc number, the current time, and the current date, as shown below:

SYSINIT Master AMP Vproc is 0 at 11:25:42 on 04/04/11

Sysinit begins by attempting to read the DBS Control Record.

The DBS Control Record is a Teradata Database globally distributed object (GDO) that contains system settings for Teradata Database. Sysinit handles the DBS Control Record differently, depending on whether the Teradata Database system was initialized previously or is being initialized for the first time.

IF the DBS Control Record GDO... THEN sysinit displays...
is corrupted or does not exist
A new DBS Control Record will be initialized to default values.
exists
The existing DBS CONTROL GDO will be used.

Sysinit displays information from the current DBS Control settings, and may prompt for further information or action based on those settings.

If the existing GDO is from the Teradata Database release immediately prior to the release being installed, the fields will be upgraded as necessary for the version installed.

Choosing the Hash Algorithm and Language Support

One of the DBS Control settings reflects the hash function Teradata Database will use for row distribution amongst AMPs. New Universal hash is the default, and is recommended for all new Teradata Database installations.

  • For existing Teradata Database installations, if the hash had previously been set to something other than New Universal or Pre-13.10 Universal, sysinit asks for confirmation, and offers to change the hash type and language support mode.
  • For new installations, sysinit asks if you wish to use New Universal Hash. If you respond No, you are able to select one of the older hash functions for backward compatibility.

The following table describes the available hash types.

Hash Type Description
New Universal The recommended hash for most Teradata Database installations. New Universal hash can be used with standard (non-Japanese) language support or with Japanese language support.

This corresponds to the HashFuncDBC setting of 6 in the DBS Control utility.

Pre-13.10 Universal This hash type is supported for compatibility with earlier releases of Teradata Database. This hash type can be used in either Standard or Japanese Language Support Mode.

This corresponds to the HashFuncDBC setting of 5 in the DBS Control utility.

Kanji Hash that supports Japanese language.

This hash type is supported for compatibility with earlier releases of Teradata Database. For non-character data, it produces more hash collisions than either of the Universal hashes.

This corresponds to the HashFuncDBC setting of 3 in the DBS Control utility.

International Hash that supports international languages, excluding Japanese.

This hash type is supported for compatibility with earlier releases of Teradata Database. For non-character data, it produces more hash collisions than either of the Universal hashes.

This corresponds to the HashFuncDBC setting of 4 in the DBS Control utility.

If you choose either New Universal or Pre-13.10 Universal Hash, System Initializer displays:

Enable Japanese language support (YES/NO/QUIT)?


Japanese and Standard language support modes are included for compatibility with earlier releases of Teradata Database. If you are migrating an existing system to the current release, Teradata recommends that you maintain the language support mode of the prior installation. This allows limiting object names to the rules of prior releases.

The following table describes the differences between Standard and Japanese language support.

Standard Language Support Japanese Language Support
The character set of the locale used for the TRANSLATE functions Unicode_to_Locale and Locale_to_Unicode is LATIN. The character set of the locale used for the TRANSLATE functions Unicode_to_Locale and Locale_to_Unicode is Kanji1.
The compatibility encoding used for the processing of object names specified in internal hexadecimal form (XN) is LATIN. The compatibility encoding used for the processing of object names specified in internal hexadecimal form (XN) is Kanji1.
The value of the Language Support Mode column of DBCInfoTbl in the Data Dictionary is ‘Standard’. The value of the Language Support Mode column of DBCInfoTbl in the Data Dictionary is ‘Japanese’.

For both Language Support Modes:

  • Object names are processed and stored in the Data Dictionary as UNICODE.
  • Object name validation rules used by Teradata Database are determined by the NameValidationRule setting in DBS Control. For more information see the DBS Control utility chapter of Utilities.

Reading the Current Configuration Map and Destroying Old Data

Sysinit next attempts to read the current configuration map.

IF a valid configuration map... THEN sysinit...
does not exist or is corrupted initializes the configuration to a full configuration based on vprocconfig GDO and displays:
Config Map will be initialized.
does exist retains the current configuration and displays:
The current configuration map has been read.

Sysinit displays a message about destroying user and dictionary data and prompts you to confirm this action:

SYSINIT is about to destroy all user and dictionary data.  Are you sure that you want to do this? (YES/NO/QUIT)?
IF you answer... THEN sysinit displays
YES
Deleting all tables...
NO or QUIT before terminating:
SYSINIT terminated without updating disks.

Verifying Vprocs

Sysinit checks to see if AMP vproc 0 is defined or if the hardware required to run AMP vproc 0 is available. If not, one of the following messages is displayed before sysinit terminates:

   AMP vproc 0 is not operational.
      SYSINIT terminated without updating disks.

or

   AMP vproc 0 is not defined.
      SYSINIT terminated without updating disks.

Sysinit will not initialize any AMPs that are not operational, that is, their VprocState is NONODE. The following message is displayed if any are found:

The following AMPs are defined in the current configuration map and the physical hardware required to run them is not available. Hence, they will not be initialized by SYSINIT.
   nnnn nnnn nnnn ...

where nnnn nnnn nnnn ... represent the vproc numbers of the AMPs in question.

For a previously initialized Teradata Database system where sysinit was able to read the current configuration, sysinit first displays the current number of AMPs and PEs, as follows:

Accessing the current configuration map...
   The current configuration map includes:
   4 PE(s) and 8 AMP(s)

Specifying the Configuration Map to Use

If more than one AMP and one PE exist, sysinit displays four options for the current and new configuration maps:

The current configuration map includes:
   4 PE(s) and 8 AMP(s)
   Enter a value for the current/new configuration maps:
   1 for current:    4 PE(s)  and    8 AMP(s)
   new:    4 PE(s)  and    8 AMP(s)
   2 for current:    4 PE(s)  and    1 AMP(s)
   new:    4 PE(s)  and    1 AMP(s)
   3 for current:    0 PE(s)  and    1 AMP(s)
   new:    4 PE(s)  and    8 AMP(s)
   4 for current:    0 PE(s)  and    1 AMP(s)
   new:    0 PE(s)  and    1 AMP(s)

Type a value for the current/new configuration maps (for most situations, choose 
option 1)

System Initializer displays the following messages to confirm your selection:

Updating the new configuration to: 
   4 PE(s)  and    8 AMP(s)
   Updating the current configuration to: 
   4 PE(s)  and       8 AMP(s)
   
   Updating current hash maps...

Concluding Sysinit

Before terminating, sysinit prompts you for the following action:

Would you like to continue with startup (YES/NO)?
IF you answer... THEN ...
YES sysinit restarts the PDE and DBS components of the system.
IF you answer... THEN the following message appears...
NO
Don't forget to set the "Start DBS" flag to "On" using
CTL utility program prior to restarting the system.
Removing old UDF, Java libraries and UIFs if any ....
SYSINIT complete.

After displaying the message, sysinit quits.