What can you do to make the optimizer detect the actual number of rows?

View Exhibit1 to examine the description of the CUSTOMERS table.
You observed that optimizer selectivity is not accurate when the CUST_STATE_PROVINCE and COUNTRY_ID columns are used together in the WHERE clause of a query. View Exhibit2 to examine the query execution plan and the commands executed to gather the statistics.
The optimizer predicts that 20 rows will be processed rather than the 3,341 rows, which is the actual number of rows returned from the table.
What can you do to make the optimizer detect the actual number of rows?
Exhibit 1 (exhibit):
Exhibit 2 (exhibit):

View Exhibit1 to examine the description of the CUSTOMERS table.

You observed that optimizer selectivity is not accurate when the CUST_STATE_PROVINCE and COUNTRY_ID columns are used together in the WHERE clause of a query. View Exhibit2 to examine the query execution plan and the commands executed to gather the statistics.

The optimizer predicts that 20 rows will be processed rather than the 3,341 rows, which is the actual number of rows returned from the table.