Loading Job status & troubleshooting
On this section, you'll learn how to check the status of your created loading jobs and its execution history, troubleshooting failed jobs.
Checking a loading job status
You can check the status of your Loading Jobs on the Loading Jobs page.
There you can check all the current information about some loading job as the the latest execution time, when the latest change occured on your job and the current status.
The four possible status for a given loading job are:
|Started||The Loading Job is in the execution queue and will be running soon.|
|Running||The Loading Job is retrieving data from your data source and adding it into SlicingDice.|
|Completed||All data from your source was successfully inserted into SlicingDice and can now be queried.|
|Failed||- The Loading Job can't connect or add all the data from the data source.
- The Loading Job will retry up to 10 times.
- If the retries aren't successful, check the Troubleshooting Failed Jobs section.
Checking a loading job history
You can check the history of all your Loading Jobs executions and their respective status clicking on the little triangle on the left of your Loading Job Name on the Loading Jobs page.
Troubleshooting failed jobs
If the status of a loading job is Failed, something went wrong. Checking the loading jobs history you can find details about what went wrong in their execution. Below are some possible problems and solutions for failed loading jobs.
- The data source does not exist anymore or its location was modified: Maybe your data source got deleted or its location modified. Make sure you supplied the right location of the database and execute the Loading Job again.
- Network failure: Maybe SlicingDice or your data source provider had a momentary network failure. The Data Loading module will try to connect to the data source continuously for some time. Check with the data source provider if their network is OK or check SlicingDice status.
- Modified credentials: If your data source connections needs a credential, maybe the
supplied credentials that have been added to SlicingDice have been modified, such as the password.
Verify if the supplied credentials are valid and execute the Loading Job again.
- Credentials with revoked permission: If your data source connection needs a credential,
maybe an essential permission just got revoked by your data source administrator.
Check with the administrator if the supplied credentials have the correct permission to read/analyze/extract the data.
- Revoked credentials: If your data source connection needs a credential, maybe the supplied
credentials that were added to SlicingDice have been revoked by your data source administrator.
Check with the system administrator if the credentials were revoked.
- Revoked SSH Key: If the data source is connected via an SSH Tunnel, maybe the SSH Key was
revoked by the data source provider, so check with the system administrator if it happened.
If the SSH Key is revoked, modify the SSH Key supplied to SlicingDice and execute the Loading Job again.
If you couldn't solve your problems, please contact us!