Troubleshooting
Problem
Symptom
Resolving The Problem
1. Look in the `iis_db.yaml` (by default it is located in /opt/IBM/UGinstall directory) for an entry named `xmeta_db_oracle_type` with a value `""` or `serviceName` or `SID`
1.1 If there is not such an entry, then add one with `""` in case of DB2/SQL server and `serviceName` or `SID` for Oracle based on the setup
2. Look in the `iis_sr_db.yaml` (by default it is located in /opt/IBM/UGinstall directory) for an entry named `xmeta_sr_db_oracle_type` with a value `""` or `serviceName` or `SID`
2.1 If there is a value other than `""` for that property, then set the value to `""`
2.2 If there is no such property, then define the property with the value suggested in 2.1
3. Restart the services if the properties are updated as per the instructions provided in 1 & 2
3.1 kubectl delete service iis-db
3.2 kubectl delete service iis-sr-db
3.3 kubectl apply -f <<pathToYaml>>/iis_db.yaml
3.4 kubectl apply -f <<pathToYaml>>/iis_sr_db.yaml
4. Update the gov-catalog-search-index yaml
4.1 kubectl edit deployment gov-catalog-search-index
4.2 After the DB_XMETA_USER property definition, include the following:
- name: DB_XMETA_ORACLE_TYPE
valueFrom:
configMapKeyRef:
name: iis-db-config
key: xmeta_db_oracle_type
4.3 After the DB_STAGING_USER property definition, include the following:
- name: DB_STAGING_ORACLE_TYPE
valueFrom:
configMapKeyRef:
name: iis-db-sr-config
key: xmeta_sr_db_oracle_type
4.4 Update the tag version in the `image` property to use `b165_d58844393bf4` instead of `11.7.1-rc.1`
4.5 Save the deployment
5. The container will be recreated automatically
Alternatively, upgrading to 11.7.1 SP1 first and than to 11.7.1 SP2 will not require this procedure to be run.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
18 October 2019
UID
ibm11089004