I would like to know how read consistency is managed by teradata Fast Export.When it tries to read data from the database does it automatically request for rows on the table before the export process starts.Is there any special variable that needs to be used to maintain read consistency?I do find something like LOCKING modifier in the FastExport reference guide but the usage is not clear?
As with a normal SQL SELECT, by default a READ lock would be applied at the beginning of the process. A locking modifier can be used, e.g. to downgrade to ACCESS lock (which does not maintain read consistency).
Once the result set has been built in spool, the lock is released. Or in NoSpool mode, the lock will be released when the export completes.