Docs
...
SQL5105N error when you run a query

SQL5105N error when you run a query in Data Virtualization

Last updated: Mar 17, 2025
SQL5105N error when you run a query in Data Virtualization

When you try to run a query, you get an error with code SQL5105N and 'Component receiving the error: "External authorizer"'.

Symptoms

An SQL5105N error message is returned when you run a query. For example, you might see the following error message.
SQL5105N The statement failed because a Big SQL component encountered an error. Component receiving the error: "External authorizer". Component returning the error: "WKC Authorizer". Log entry identifier: "[SCL-0-<log_entry_id>]". Reason: "<reason_code>". SQLSTATE=58040

Causes

This error occurs when you encounter an exception while evaluating Data Virtualization objects against IBM Knowledge Catalog data protection rules.

To obtain more details about the error, run the following command:
select line from table(syshadoop.log_entry('SCL-0-<log_entry_id_from_the_error>'))

For more information on governing virtual data with data protection rules, see Governing virtual data with data protection rules in Data Virtualization .

Resolving the problem

To learn more about the reason code in the error message, refer to the following table.
Reason code Explanation
1

The system failed to check the status of the Enforce data protection rules for virtual objects option.

For more information on the Enforcing data protection rules for virtual objects option, see Enabling the enforcement of data protection rules in Data Virtualization.
2

The system failed to retrieve the platform user ID from the username.

Ensure that the Cloud Pak for Data user management is working correctly. For example, you can view users in the Cloud Pak for Data Menu > Administration > Access control page.
3

The system failed to fetch a user's groups.

Ensure that the Cloud Pak for Data user management is working correctly. For example, you can view users in the Cloud Pak for Data Menu > Administration > Access control page.
4

The system failed to initialize the policy enforcement point (PEP) instance.
5

The system failed to get the IBM Knowledge Catalog policy service governance convention.

Check that the IBM Knowledge Catalog policy service settings are retrievable by going to Cloud Pak for Data Menu > Governance > Rules > Manage rule settings and ensuring that the Default data access convention option is selected.

For more information on changing the default rule behavior, see: Planning to protect data with rules.
EVAL-1

An exception was detected during an evaluation against Watson Knowledge Catalog policy service.

Check that the IBM Knowledge Catalog policy service is working correctly by editing a data protection rule or previewing the object with a data protection rule applicable from a governed catalog.
EVAL-2

No valid evaluations were returned by the IBM Knowledge Catalog policy service.
EVAL-3

An unexpected outcome was returned by the IBM Knowledge Catalog policy service.
AUTH-0

An unhandled exception was encountered when checking for Allow or Deny authorization for the object.
AUTH-1

The system failed to retrieve the catalog resource key for the object.
RCAC-0

An unhandled exception was encountered when checking for column masks or row filters for an object.
RCAC-1

The system failed to construct external RCAC requests to evaluate the requested objects against the IBM Knowledge Catalog policy service.
RCAC-2

The system failed to retrieve row-level filters from the IBM Knowledge Catalog policy service response.
RCAC-2.1

The asset referenced in the row filtering rule is not a valid Data Virtualization object.

Ensure that the referenced object in your row filtering data protection rule is a valid object in Data Virtualization.
RCAC-3

The system failed to extract column masks from the transformation specification returned by the IBM Knowledge Catalog policy service.