R12 Check Writer XML process failed
Issue:
When attempting to run the Check Writer XML process, the following error occurs.
stat_low = 86
stat_high = 0
emsg:was terminated by signal 6
/test/appltest/apps/apps_st/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1
Cause:
This issue is generally encountered after cloning. Main reason for this is wrong value of the DBC_FILE parameter in View "PAY_ACTION_PARAMETERS".
Use the following SQL Query to find the Value:
select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';
Solution:
1. Run the following query to confirm the extra space(s) in the DBC file parameter value
Query:
select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';
2. Modify the DBC file parameter value in PAY_ACTION_PARAMETERS.
Query:
UPDATE "APPS"."PAY_ACTION_PARAMETERS" SET PARAMETER_VALUE = '<Correct DBC Path>/FileName.dbc';
3. Retest the issue.
4. Confirm the result.
Issue:
When attempting to run the Check Writer XML process, the following error occurs.
stat_low = 86
stat_high = 0
emsg:was terminated by signal 6
/test/appltest/apps/apps_st/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1
Cause:
This issue is generally encountered after cloning. Main reason for this is wrong value of the DBC_FILE parameter in View "PAY_ACTION_PARAMETERS".
Use the following SQL Query to find the Value:
select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';
Solution:
1. Run the following query to confirm the extra space(s) in the DBC file parameter value
Query:
select length(parameter_value), Length(trim(parameter_value)), parameter_value from pay_action_parameters where parameter_name = 'DBC_FILE';
2. Modify the DBC file parameter value in PAY_ACTION_PARAMETERS.
Query:
UPDATE "APPS"."PAY_ACTION_PARAMETERS" SET PARAMETER_VALUE = '<Correct DBC Path>/FileName.dbc';
3. Retest the issue.
4. Confirm the result.