Handling Exceptions
SSOLite stored procedures
| • | The error text is always preceded by the string (SWERROR). |
| • | Each error has a unique ID, which is displayed at the end of the error text. |
It is the application’s responsibility to handle any such database exceptions, and issue a rollback if appropriate.
The following table describes the different errors (and their unique IDs) that may be returned by the SSOLite stored procedures.
|
Stored Procedure |
|
Error Text |
|
|
|
Node details not found in database (ID:001007) |
|
|
|
MBox Queue Name(s) not found in database (ID:001008) |
|
|
|
Procedure details not found in database for procedure name= |
|
|
Procedure version not found in database for procedure name= |
|
|
|
Latest Released or Unreleased Procedure version not found in database for procedure name= |
|
|
|
Procedure version not found in database for procedure name= |
|
|
|
Suspend type (suspend_type) is invalid, expected |
|
|
|
Case (case_num) is already active (ID:001036) |
|
|
|
Case (case_num) is dead (ID:001037) |
|
|
|
Case (case_num) is already suspended (ID:001038) |
|
|
|
|
Sub-Proc casenum not found in database for Procedure proc_name, Case Number case_num, Step Name step_name, Sub-proc sub_proc_name (ID:001018) |
|
|
Failed to find case information for case: case_num (ID:001019) |
|
|
|
-20000 |
Unexpected inconsistency between node name nodename and delayed release id procedure node name nodename (ID:001020) |
|
-20000 |
Unexpected inconsistency between node name nodename and delayed release id queue node name nodename (ID:001021) |
|
|
|
-20000 |
Failed to get node ID (ID:001022) |
|
-20006 |
Case (case_num) is dead (ID:001037) |
|
|
-20006 |
Procedure and case information does not match (ID:001041) |
|
|
-20006 |
Case (case_num) is dead (ID:001037) |
|
|
-20006 |
Procedure and case information does not match (ID:001042) |