New Versus Previously Initialized Systems
Running sysinit is part of the overall Teradata Database system initialization process. Sysinit handles Teradata Database system configuration differently, depending on whether the system is being initialized for the first time, or has been previously initialized on the same or a previous version of Teradata Database
First-Time Initialization for New Systems
When used to initialize a new Teradata Database system, sysinit initializes a configuration that includes all the vprocs defined in a vprocconfig GDO.
On a new, uninitialized, Teradata Database system (or on a corrupted Teradata Database system whose configuration map cannot be read), sysinit creates a full configuration based on the vprocconfig GDO. All vprocs are set to an online, operational state. If a problem exists with any vproc, then a 0 PE, 1 AMP configuration is created. If a full configuration was created, then you are given options later for selecting a particular configuration for the new and old config maps.
Previously Initialized Systems
On a previously initialized Teradata Database system, sysinit retains the current configuration map and prompts you to do one of the following:
Sysinit will destroy all user and dictionary data currently in the Teradata Database system.
Sysinit may reset the configuration settings stored in various GDOs and normally set using various system utilities to default values for the new version of Teradata Database.
If you need to run sysinit on an existing system, first collect information from the following to ensure that customized settings can be restored and set as required after the sysinit:
System Control Files: