Troubleshooting Oracle DB Exporter Database Access Issues

If the Oracle DB Exporter is unable to connect to the database, or if the Grafana dashboard displays the database status as "Dead," you must review the oracle-db-monitoring pod logs for the error "ORA-12154: TNS: could not resolve the connect identifier specified" or other database connection issues. If this error appears in the logs, perform the following steps to resolve the issue:

Verify that the /tnsadmin/ wallet directory inside the container includes the correct wallet files:
```
kubectl exec -it <oracle-db-monitoring-pod> -n <namespace> -- ls -l /tnsadmin/
```
If the wallet directory is empty, check the Kubernetes secret for wallet data. Confirm that the Kubernetes secret (for example, db-wallet-secret) includes the wallet data:
```
kubectl get secret db-wallet-secret -n <namespace> -o yaml
```
Note: Make sure that the .data section in the Kubernetes secret includes non-empty wallet files.
If the Kubernetes secret in the .data section is empty, disable Oracle DB monitoring, and then re-enable it to regenerate and populate the secret. For more information, see Disabling Oracle Database Monitoring in Siebel CRM and Enabling Oracle Database Monitoring for Siebel CRM.