A Appendix: Exit Codes
This appendix describes all non-success exit codes from the Batch Framework services and batch administration tasks.
All EE batch scripts have consistent exit codes. Codes from 1 to 22 come from the BSA framework (although only 6 and 13 are commonly used by EE batch and so are included in the table below). Codes of 30 and above are from EE batch scripts themselves and are also listed in Table A-1.
Table A-1 lists the common (non-success) exit codes from the EE batch scripts and the BSA framework.
Table A-1 Common Exit Codes
Code | Reason |
---|---|
6 |
too few args / missing arg |
13 |
invalid application path |
30 |
required environment variable is not set |
31 |
batch config file is not found |
32 |
selected batch config entry is not found in file |
33 |
invalid or missing info in batch config file |
34 |
unknown error detected in RPASCE utility log output |
35 |
file/directory not found when moving or copying files |
36 |
file/directory permission error when moving or copying files |
37 |
measure load exceeded reject record limit. |
Note that in a live OCI-provisioned environment, it is not expected that customers will see any of these error codes except 31 through 33. These codes indicate issues in the customer-provided batch config files.
Table A-2 lists additional exit codes from eebatch_exporthier.ksh, eebatch_exportmeas.ksh, eebatch_loadhier.ksh, and eebatch_loadmeas.ksh, that result from the exit codes of the underlying RPASCE binary utilities (exportHier, exportMeasure, loadHier and loadMeasure). The exit codes from the binary utilities are reported by the EE Batch Framework as being 100 more than the raw utility results. This prevents overlap between the BSA/EE script result codes and the RPASCE binary utility result codes. If loadHier itself returns an error code of 5, then the EE batch framework will report the error as code 105.
Table A-2 Additional Exit Codes
Script | Code | Reason |
---|---|---|
Generic codes applied to all scripts |
103 |
Invalid application. Version mismatch. |
104 |
Generic argument error of the underlying utility. |
|
105 |
Generic exception occurred during main operation. |
|
106 |
Lock exception or parallel sub-process error. |
|
eebatch_calc.ksh |
107 |
Expression parsing error. |
eebatch_exportmeas.ksh |
108 |
Error during export preparation. |
109 |
Error during main execution. |
|
110 |
Error during post operation. Possible during the merging of local application files. |
|
eebatch_loadhier.ksh |
108 |
loadHier cannot add a new position to a partition dimension. For example, no store has been defined for the new position. |
109 |
Calendar prepending error. |
|
110 |
Input data contains conflicting information. |
|
111 |
Metadata error. Corrupted internal data. |
|
112 |
Unable to update the ITT table for the hierarchy that is shared by PDS. |
|
113 |
Data mover staging error. |
|
114 |
Data mover merging error. Hierarchy update was applied but measure data was not moved completely. The user must fix the underlying issue and re-run the operation to complete the hierarchy update. |
|
115 |
NA handler error. Hierarchy update was applied but measure data was not moved completely. The user must fix the underlying issue and re-run the operation to complete the hierarchy update. |
|
116 |
Purge all failed. |
|
117 |
Reindex is in progress. No operation was performed. |
|
120 |
PDS repartitioning is in progress. |
|
eebatch_loadmeas.ksh |
98 |
Internal aggregation error |
99 |
Internal aggregation error. Cannot load in CLR mode because the measure does not have a clear intersection. Unknown internal error. |
It is not expected that customers will encounter any of the RPASCE exceptions, internal errors, or C++ exceptions, which indicate corrupted data or a programming error.