IBM Support

audit-trail-service pod goes into CrashLoopBackOff after upgrading from 11700 to 11702 in UG

Troubleshooting


Problem

After upgrading from 11700 to 11702 in UG environment the audit-trail-service pod goes into CrashLoopBackOff Status.

Symptom

Run the follwoing from UG node

kubectl get pods | grep audit-trail-service

The output should be something similar to

audit-trail-service-2622810079-bp266          1/1       CrashLoopBackOff                                                          0          6h

 

 

Cause

The AUDIT_TRAIL schema is not present in the xmeta database.

Diagnosing The Problem

Run the following to get the exact name of the audit-trail-service pod.

kubectl get pods | grep audit-trail-service

The output should contain a line like

audit-trail-service-2622810079-bp266          1/1       CrashLoopBackOff                                                          0          6h

The name of the pod is audit-trail-service-2622810079-bp266
Get the logs of pod by running the following

kubectl logs audit-trail-service-2622810079-bp266

The output will contain lines like

Creating schema "AUDIT_TRAIL" ...
ERROR:
Unable to create schema "AUDIT_TRAIL"

 

Resolving The Problem

For db2 database

Run the following as db2 admin user to create the schema

db2 connect to <xmeta db name>
db2 create schema AUDIT_TRAIL
db2 grant CREATEIN, ALTERIN, DROPIN ON SCHEMA AUDIT_TRAIL TO USER <xmeta db user>

e.g.

db2 connect to xmeta
db2 create schema AUDIT_TRAIL
db2 grant CREATEIN, ALTERIN, DROPIN ON SCHEMA AUDIT_TRAIL TO USER XMETA

 


For Oracle database

Download the attached zip archive and extract the contents of it.
Oracle_0.zip
Navigate to the directory Oracle in the archive.
Run the following command to create the required schema. All arguments are required and must be specified in the order that is shown in the following example.

./create_audit_trail_schema.sh OracleSystemUser OracleSystemPassword ServiceName TableSpaceName

For example :

./create_audit_trail_schema.sh SYS MANAGER DBNAME xmetaspace

OracleSystemUser
The Oracle system user used to log in to the sqlplus utility to create the schema. This user must be assigned the database administrator role.

OracleSystemPassword
The password for the Oracle system user.

ServiceName
The Oracle TNS service name. The name is the same as the TNS service name that is provided as the NetServiceName argument to the create_xmeta_db.sh script in step 2 during Pre-installing the metadata repository database.

TableSpaceName
Name of the tablespace to use for the new schema. The name is the same as the metadata tablespace that is provided as the XmetaTableSpaceName argument to the create_xmeta_db.sh script in step 2 during Pre-installing the metadata repository database.

 

 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Component":"IBM InfoSphere Metadata Asset Manager","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.7.0.2","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2018

UID

ibm10732739