Troubleshooting ODI on OCI

3 Troubleshooting ODI on OCI

This chapter describes about various services associated with ODI on OCI and ways to troubleshoot them when you encounter issues while using them.

Note:

If you are facing issues connecting to ADW dataserver and MySQL repository after long hours of inactivity, try reconnecting to ODI repository to overcome this problem.

Services available in ODI VIM are:

jettyodi.service
agentodi.service
mysqlodi.service

Essential commands necessary for troubleshooting these services are:

Use the following command to check the status of embedded jetty service:
```
systemctl status jettyodi.service
```
Use the following command to check the log of embedded jetty service:
```
In a commandline type: journalctl -u jettyodi.service -f
```
systemd-journald can be configured to persist your systemd logs on disk, and it also provides controls to manage the total size of your archived logs. These settings are defined in /etc/systemd/journald.conf. To start persisting your logs, uncomment the Storage line in/etc/systemd/journald.conf and set its value to persistent. Your archived logs will be held in /var/log/journal. If this directory does not already exist in your file system, systemd-journald will create it. After updating your journald.conf, load the change: sudo systemctl restart systemd-journald
Use the following command to restart the embedded jetty service:
```
systemctl daemon-reload
systemctl restart jettyodi.service
```

Use the following command to restart mysql service:

systemctl daemon-reload
systemctl restart mysqlodi.service

Note:

Use the following commands to start or stop any of the services:

sudo systemctl start <service_name>
sudo systemctl stop <service_name>