You cannot use FastLoad, MultiLoad, or the Teradata Parallel Transporter operators LOAD and UPDATE to load data into base tables that have join indexes because those indexes are not maintained during the execution of these utilities (see Teradata® FastLoad Reference, B035-2411, Teradata® MultiLoad Reference, B035-2409, and Teradata® Parallel Transporter Reference, B035-2436 for details).
If you attempt to load data into base tables with join indexes using these utilities, an error message returns and the load does not continue.
To load data into a join-indexed base table, you must drop all defined join indexes before you can run FastLoad, MultiLoad, or the Teradata Parallel Transporter operators LOAD and UPDATE.
Load utilities like BTEQ, Teradata Parallel Data Pump, and the Teradata Parallel Transporter operators INSERT and STREAM, which perform standard SQL row inserts and updates, are supported for join-indexed tables (see Basic Teradata® Query Reference, B035-2414, Teradata® Parallel Data Pump Reference, B035-3021, and Teradata® Parallel Transporter Reference, B035-2436 for details).
You cannot drop a join index to enable batch data loading by utilities such as MultiLoad and FastLoad if queries are running that access that index. Each such query places a lock on the index while running, blocking the completion of any DROP JOIN INDEX transactions until the lock is removed.
Furthermore, if a DROP JOIN INDEX transaction is running, batch data loading jobs against the underlying tables of the index cannot begin processing because of the EXCLUSIVE locks DROP JOIN INDEX places on the base table set that defines them.