Fallback behavior and defaults have become platform-specific. Newer platforms now always use fallback. All newly created databases, users, indexes, and tables are set to FALLBACK, even if you specify NO FALLBACK in the CREATE request. All databases or users are set to FALLBACK even if you specify NO FALLBACK in the ALTER TABLE or MODIFY DATABASE/USER request.
Older platforms that upgrade to this release still allow the NO FALLBACK option, and the default is NO FALLBACK for CREATE TABLE, ALTER TABLE, CREATE JOIN INDEX, CREATE HASH INDEX, CREATE DATABASE, MODIFY DATABASE, CREATE USER, and MODIFY USER requests.
Platforms that are optimized for fallback can recover quickly from data corruption.
The SYSINIT default for all platforms is now ALWAYS FALLBACK. However, the Parallel Upgrade Tool (PUT) will use the fallback setting appropriate to the platform.
For more information, see Teradata Vantage™ - Database Administration, B035-1093.