In Teradata there can be tens and thousands of user accounts and they appear as empty schemas. During the scans each classifier rule throws an error stating the result set contains zero rows. Each of these errors cost half a second or more delay/performance. If you have a large Teradata system with thousands of user accounts and a large number of rules in the policy, this can causes the classifier process to run for days.
java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 16.20.00.12] [Error 1323] [SQLState HY000] Cannot get data value for column 1 because the result set contains zero rows.
InitializationException: Could not access column(s) for table: 'XYZABC10XYZ10001.' on 'jdbc:teradata://xyxz.abccompany.com/DBS_PORT=1025' in 0.44 second
SQLException: [Teradata JDBC Driver] [TeraJDBC 16.20.00.12] [Error 1323] [SQLState HY000] Cannot get data value for column 1 because the result set contains zero rows. SqlState: HY000 Error Code: 1323
At the beginning of the scan the classifier process can take an inventory of all the schemas and their size. Any schema with zero or few bytes would be an indication of empty schema. The classifier process can exclude all those schemas from being scan by any of the rules.
Do not place IBM confidential, company confidential, or personal information into any field.