This means if you’re allocated 200G of spool and you’re on a system with 24 AMPS, you’re allocated ~8.3G of spool on each AMP. Spool space is allocated to a user as a total amount available for that user, however this total amount is spread across all AMPS. Spool is temporary disk space used to hold intermediate rows during query processing, and to hold the rows in the answer set of a transaction. Some forums mention tlogview for reading the logįor details about the spool space error see: What must be considered for NOPI Teradata tables NOPI tables are ideal for improving loading times with bulk load utilities. Finally, no more spool space can also be triggered by skewed queries or volatile tables.
#Dbschema no more spool space full
To easily read the full SQL statement, tick wordwrap in notepad++ No more spool space can also be caused by too many parallel sessions of the same user.
This should show the SQL statement and the response. The section of interest is the following: Avoiding Spool Space Errors for Queries Against Teradata Data Sources Importing Metadata from Relational Data Sources. The log may show a section in readable format similar to: No more spool space error, 5.2.9.1 setting up, 5.2.9, 16.4 test to production, 1.5. When opening the Teradata Parallel Transporter (TPT) job log L123.out file with notepad++ there are several nonprintable characters shown with a black background. Teradata Parallel Transporter Version 16.10.00.01 64-Bit lob log: C:\Program Files\Teradata\client\16.10\Teradata Parallel Transporter/logs/L123.out The script output should show something similar to:
0 kommentar(er)
