Known issues for Common Core Services

These known issues and limitations apply to Common Core Services.

You cannot preview an Oracle connection dataset that contains objects as data types

If the Oracle connection dataset contains objects as data types, you cannot preview the dataset and you receive the following error: An error occurred attempting to preview this asset. For information on Oracle object types, see Introduction to Oracle objects.

Applies to: 4.6.5 and later

You cannot open a Generic JDBC connection that use personal credentials

When you try to open a Generic JDBC connection that use personal credentials, you receive an error and the connection doesn't open. This error occurs for all services that use the asset browser.

Workaround: Click the key icon (Shows the key icon) next to the connection that uses a Generic JDBC driver and enter your personal credentials.

Applies to: 4.6.4 and later

Cannot view catalogs after upgrading from 4.5.x to 4.6.x

You receive an unknown error message when you try to view catalogs after upgrading from Cloud Pak for Data version 4.5.x to Cloud Pak for Data version 4.6.x.

Diagnosing the problem

To verify whether the upgrade was successful, check the ccs-cr to get the values for the version and reconciled version. If the upgrade was successful, both values should match. If the version and reconciled version values don't match, the upgrade has failed.

  1. To check the version value, run:

    oc get ccs ccs-cr -o jsonpath={.spec.version}
    
  2. To check the reconciled version value, run:

    reconciled version = oc get ccs ccs-cr -o jsonpath={.status.versions.reconciled}
    

Resolving the problem

If the version and reconciled version values don't match, or you see this issue after an upgrade, manually clear the cache by running:

redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern sess:* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern PLATFORM_PERMISSIONS* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern WKC_INVITED_USERS* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern ASSET_DATA_PREVIEW* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern ASSET_PREVIEW* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern TRANSFORMED_ASSET* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern NOTIFICATIONS* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern ACCESS_GROUPS* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern SOVEREIGNTY_VALUES* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern LOCATION_VALUES* | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;
redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt --scan --pattern ????????-????-????-????-???????????? | xargs -r redis-cli -h redis-ha-master-svc -p 6380 --no-auth-warning -a `cat /etc/.secrets/AUTH` --tls --cacert /etc/ssl/certs/ca.crt del;


Parent topic: Limitations and known issues in IBM Cloud Pak for Data