You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Configuration Issues
No logs generated in the log file
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 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) | 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
Common 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.
|
Database Errors
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 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. | If not solved, contact Adeptia support.
|
Oracle: No more data to read from socket
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 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.
| If not solved, contact Adeptia support.
|
No of columns mismatch
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 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) | Remarks |
|---|
| 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) | Remarks |
|---|
| 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) | Remarks |
|---|
| 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.
|
|
Files/folders operation issues
File/Folder Permissions issue
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 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) | Remarks |
|---|
| 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. |
|
File/Folder is in use
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 1 | 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. The file/folder may be in use by any other process or opened by any process. | Check if any files are open in any editor or it is accessed by any other tool and close that file from editor/tool. |
|
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:
