Logical I/O consumed by the following functions are excluded from the calculation of Vantage Units:
- Consumption collector queries by the consumption service (by vcmuser) and activities by system users
- Movement of usage data from DBC/DBQL to PDCR
- SQL usage by the PDCR Admin in the Performance Data Collection Portlet
- User-initiated queries that fail to complete successfully due to the following internal database errors:
- 2631: Request aborted by the system
- 2646: No more spool space
- 3610: Request created a general error
- 3702, 3710, 3711: Not enough memory available
- 4950: A generic error
- 4951: Missing or incorrect input
- 4952: An internal error
- 4953: An external record caused a runtime exception
- 4954: Request canceled due to unexpected issues
- 4966: AMP found a table header that does not match
- 4968: Warning that the bucket or path do not exist in NOS location
- 4978: Parquet data was not converted properly to Teradata data type
- 4980: Required table header for foreign table access is not set up
- 4981: Field 5 of the table header is incorrect
- 4984: Unexpected error when constructing the external payload data row
- 4985: Unexpected error when the diagnostic flags were set
- 4992: All records in the external file have been fetched
- 4993: Request created a general error
- 4994: Enabling diagnostic flags created an error in NOS block builder
- 4995: Memory corruption error
- 4996: Index is out of range
- 5405, 7453: An interval was calculated that was too large
- 7487: Request created a general error
- 7583: Running a stored procedure ran out of needed resources
- 7596: An object is unavailable for use because it is being backed up
- 9124: Request created a general error
- 9134: File system out of memory
- 9990: Request completed but it is too large for the client software
See Teradata Vantage™ - Database Messages, B035-1096.