You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
Configuration Issues
No logs generated in the log file
| Step | Possible reason(s) | Possible solution(s) |
|---|
| 1 | Issues with the CLASSPATH. | 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) |
|---|
| 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.
|
Database issues
Common issues
Sluggish Transaction/Process Flow execution
| 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. |
Error at runtime and failure of query execution
| 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
Data truncation: Out of range value for column
| 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. |
Oracle: No more data to read from socket
| Step | Possible reason(s) | Possible solution(s) |
|---|
| 1 | Log cleanup and archival process interrupted due to Oracle database connectivity issues. | Restart the server, and the log cleanup and archival process should start running successfully.
|
No of columns mismatch
| 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. |
Parameter Number 4 is not an OUT parameter
| 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.
|
ORA-30036: unable to extend segment by 8 in undo> tablespace 'UNDOTBS1'
| 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.
|
Lock wait timeout exceeded; try restarting transaction
| 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. | Increase the value for innodb_lock_wait_timeout property.
|
File/Folder Permissions issue
| 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. |
File/Folder does not exist
| Step | Possible reason(s) | Possible solution(s) |
|---|
| 1 | The specified file/folder is deleted. | Create the required file/folder manually. |
File/Folder is in use
| 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. |
Insufficient disk space
| 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
Unable to receive mail notifications for a failed log cleanup and archival process
| 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
Log cleanup and archival process is not running
| 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.
