- Newest
- Most votes
- Most comments
The "Transaction Not Found" error you're experiencing is often an indication that the database table is empty or not properly configured. This issue can occur even if the batch tests were successful. Here are some steps you can take to troubleshoot and resolve this issue:
-
Check your database configuration: Ensure that your database is set up correctly according to the workshop documentation. This includes verifying the connection details and table structures.
-
Verify data presence: Query the database manually to confirm if it contains the necessary data. The error suggests that the required transaction information might be missing.
-
Review the initJics.sql file: Make sure this file is located in the correct folder in your S3 bucket. It should be under artifacts/jics/sql/initJics.sql. An incorrectly named or misplaced folder can cause this issue.
-
Examine application properties: Double-check your application.yml or application-main.yml file to ensure all database-related configurations are correct, including the data source settings for jics, bluesam, bac, and primary.
-
Add a configuration key: Try adding the following key to your application-main.yml file:
stopExecutionWhenProgNotFound: false. This may help if there are issues with program execution. -
Check Bluesam configuration: In the application definition, ensure that the "bluesam" parameter (not "blusam") is correctly set with the appropriate secret manager ARN.
-
Verify BluAge engine version: The error message you're seeing about data set operations suggests you're using BluAge engine version 4.2.0. Consider upgrading to version 4.3.0 or later to support data set operations.
If these steps don't resolve the issue, you may need to review the batch jobs that were run earlier to ensure they populated the database correctly. If the problem persists, consider opening a support case with AWS for more specialized assistance.
Sources
L3 Workshop - Go Live - Test Online - Transaction not Found | AWS re:Post
Transaction not found in Blu Age modernized application | AWS re:Post
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post
BluAGE L3 workshop issue with Go-Live Test batches and Online | AWS re:Post
answered 2 years ago
Relevant content
asked 3 years ago
