Troubleshooting log cleanup and archival
Configuration Issues
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Issues with the CLASSPATH. JARS mentioned in the CLASSPATH may not be present in the specified folder. | Check whether the JARS used in the CLASSPATH are present at the specified location or not. To check for the path of the JAR files, open logs-archive-cleanup.bat or logs-archive-cleanup.sh file. Here you will find all the JARS used in the CLASSPATH. The log cleanup and archival process will fail and no log will be generated even if a single JAR file is missing from its specified location. In such a case, contact Adeptia support. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Issues with application settings. | Do the followings:
|
Database issues
Common issues
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | The database server is heavily loaded to handle the request, or doesn't have enough number of connections available. | You should always run log cleanup and archival process when either the server has no load or have minimum load. Also make sure that there are enough database connections available to use. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Compatibility issues between the database driver version and database server. | You should always make sure that database driver jars should be compatible with the database server. |
Database Errors
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | One or more columns in log table and their corresponding columns in log archive table differ in size(s). | Alter the log archival table to correct the structure of the table in line with the log table. It can be done by using alter query.
|
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Log cleanup and archival process interrupted due to Oracle database connectivity issues. This is Oracle specific error. | Restart the server, and the log cleanup and archival process should start running successfully.
|
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | One or more columns in log table and their corresponding columns in log archive table differ in size(s). | Alter the log archival table to correct the structure of the table in line with the log table. It can be done by using alter query.
|
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Stored Procedures such as AU_SP_DELETE_ARCHIVE_LOGS, AU_SP_DELETE_LOGS, etc. are missing. | Create the missing Stored Procedures in the database. You can find these Stored Procedure in initialize-log-msq-{dbname}.sql file. For example: initialize-log-msq-mysql.sql for MySQL. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | The "undo Tablespace" size is completely occupied or the size for "AU_TransactionLog" is very large. | Set the size of "undo tablespace" to auto-extend in the Database. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | The table is locked out due to large amount of data present in it, large number of uncommitted transactions, etc. You may encounter this error while trying to delete a bunch of records using MySQL administrator or some other DB tool. | Increase the value for innodb_lock_wait_timeout property. |
Files/folders related issues
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | User may not have permission to delete the file/folder. | Check and grant the necessary permissions to the user. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | The specified file/folder is deleted. This may happen because the file/folder has been deleted manually, or by any other process, or it never existed. | Create the required file/folder manually. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | The file/folder may be in use or opened by any other process. | Check for and close the files that are open in any editor or accessed by any other tool. |
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Disk space on the sever is low or completely exhausted. There is no space to copy new repository files. | Delete the files/folders manually. |
Mail notification issues
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|---|---|---|
| 1 | Incorrect configuration of mail server properties. | Check for and correct the mail server properties configuration. | If not solved, follow the step 2. |
| 2 | Connectivity issue with the mail server. | Check for and fix any mail server connectivity issues. | If not solved, follow the step 3. |
| 3 | Mail notifications not allowed from an external app. | Check for and allow the email account/mailbox to accept notifications from an external app. | If not solved, contact Adeptia support. |
Issues leading to Force Cleanup
| Step | Possible reason(s) | Possible solution(s) |
|---|---|---|
| 1 | Increased logs size in the database. | Perform a force cleanup to clean the logs data. |
If you're still unable to fix any of the issues, contact Adeptia support.