Troubleshooting log cleanup and archival

Configuration Issues

No logs generated in the log file

Step

Possible reason(s)

Possible solution(s)

Remarks

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.

Unable to perform cleanup for table <table name>

Step

Possible reason(s)

Possible solution(s)

Remarks

1

Issues with application settings.

Do the followings:

Set the property abpm.logs.archival.batch.enable to no.
Set the property abpm.logs.delete.chunks.enable to no.
Retry executing the log cleanup and archival process.

If not solved, contact Adeptia support.

Database issues

Sluggish Transaction/Process Flow execution

Step

Possible reason(s)

Possible solution(s)

Remarks

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.

If not solved, contact Adeptia support.

Error at runtime and failure of query execution

Step

Possible reason(s)

Possible solution(s)

Remarks

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.

If not solved, contact Adeptia support.

SQL

Data truncation: Out of range value for column

Step

Possible reason(s)

Possible solution(s)

Remarks

1

One or more columns in log table and log archive table differ in size(s).

It means that the at least one of the column size of the log table is different then log archive table.

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.

If not solved, contact Adeptia support.

Oracle: No more data to read from socket

This is Oracle specific error. Oracle database server disconnect connection forcefully. This can be because of the server were shutting down at the same moment when archival starts. Once oracle restarts then log cleanup and archival process should run successfully.

Transaction (Process ID 543) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

This issue should not occur but if it does then it will be a bug into the product. It should be fixed in the product so log the defect to product team.

No of columns mismatch

It means that number of the columns in the log table is different then log archive table. It can be fixed by altering the log archival table to correct the structure of the table(same as log table). It can be done by alter query.

Parameter Number 4 is not an OUT parameter

This error comes when stored procedures are missing. For example, AU_SP_DELETE_ARCHIVE_LOGS, AU_SP_DELETE_LOGS. Create the stored procedures in the database. You can find these procedure in initialize-log-msq-{dbname}.sql file. For example, initialize-log-msq-mysql.sql for mysql.

ORA-30036: unable to extend segment by 8 in undo > tablespace 'UNDOTBS1'

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.

Lock wait timeout exceeded; try restarting transaction

This error usually comes when the table is locked out in case of large data present in it or due to the large number of uncommitted transactions etc. If you'll try to delete a bunch of records using MYSQL administrator or some other DB tool then you'll receive the same error. Increasing value of innodb_lock_wait_timeout should resolve your issue.

Files or folders operation issues

File/Folder Permission issue

Sometimes logged-in user does not have permission to delete the file/folder. So please check that user have appropriate permission for this. Provide the necessary permission to the user.

File/Folder does not exist

The specified file/folder has been deleted in between the process. This can happen if the file/folder has been deleted manually or by any other process. Or May be this folder is not created ever. You can create that folder manually.

File/Folder are in use

Sometimes at the time of cleanup, the same can be in use by any other process or opened by any process. In this case file will not be deleted. Check if any files are open in any editor or it is accessed by any other tool and close that file from editor/tool.

Not Enough Disk Space

Sometimes disk space is full at the server and in this case there is no space to copy new repository files. Delete the files/folder manually.

Mail notification issues

Error while sending the mail notification for log clean and archival process failure.

In log cleanup and archival process, if there is any issue occurred in the process then user will get an mail notification with error details. Below is a sample,
java.lang.Exception: java.lang.Exception: Failed to connect to mail server.Either mail server is not available or host/port/username/password parameters are invalid.
at notification.SendNotificationMail.sendMail(SendNotificationMail.java:169)
at notification.SendNotificationMail.sendMail(SendNotificationMail.java:60)
You need to check that mail configuration are correct for mail notification. You can find these properties under “Mail Server Properties” group in server-configure.properties file.
You also need to verify that there is no connectivity issue with the mail server.
Sometime you may have to enable the less secure apps property. For example if you are using gmail id for mail Notification then you may need to enable this: