START CALL SICK error
Information about START_CALL_SICK and Database Inconsistency: Start Transaction SICK error.
Post system copy activity on in Release 7.40 & 7.50 and the system is a single-instance system of SAP Business Suite 7 this is a known issue.
The reason behind this is, In earlier release Enqueue work process leads to performance problems when using it within multi-instance systems. SAP decided desupport enqueue work process as of Release 7.50.
Set the parameter value as given below.
"enque/process_location = REMOTESA"
"rdisp/wp_no_enq = 0"
Please refer the SAP Note : 2146940 for details.
Regards,
Nischith Purushotham
Post system copy activity on in Release 7.40 & 7.50 and the system is a single-instance system of SAP Business Suite 7 this is a known issue.
The reason behind this is, In earlier release Enqueue work process leads to performance problems when using it within multi-instance systems. SAP decided desupport enqueue work process as of Release 7.50.
Set the parameter value as given below.
"enque/process_location = REMOTESA"
"rdisp/wp_no_enq = 0"
Please refer the SAP Note : 2146940 for details.
Regards,
Nischith Purushotham
Comments
Post a Comment