OTMZGNE - General application errors
The OTMZGNE exceptions are for the general errors that might occur when you use the Optimization service.
| Error code | Error message |
|---|---|
| OTMZGNE001 | File not found. |
| OTMZGNE002 | Naming exception. |
| OTMZGNE003 | Class not found. |
| OTMZGNE004 | IO exception. |
| OTMZGNE005 | Invalid date format. |
| OTMZGNE006 | Systematic failure. |
| OTMZGNE007 | Unknown error code returned. |
| OTMZGNE008 | Missing or incorrect arguments passed. |
| OTMZGNE009 | Log file path is not defined or path does not exit. |
| OTMZGNE010 | SPARK_HOME environment property is not set. |
| OTMZGNE011 | Invalid date for argument %s. |
| OTMZGNE012 | Duplicate file (%s) found. |
| OTMZGNE013 | JSON exception. |
| OTMZGNE014 | Collection not found exception '%s'. |
| OTMZGNE015 | Property not found exception '%s'. |
| OTMZGNE016 | UnknownHost exception. |
| OTMZGNE017 | Exception/Missing '%s' for '%s' '%s'. |
| OTMZGNE018 | Exception/Missing '%s' for '%s' '%s' and '%s' '%s'. |
| OTMZGNE019 | Illegal access exception. |
| OTMZGNE020 | Instantiation exception. |
| OTMZGNE021 | Runtime exception occurred while processing a request or getting a sourcing plan or null
values. Check for missing address information in the input to the Optimizer API or for missing data for SLA code. |
| OTMZGNE022 | CPELX exception. |
| OTMZGNE023 | JMS exception. |
| OTMZGNE024 | Generic exception. |
| OTMZGNE025 | JAXB exception. |
| OTMZGNE026 | Exception while getting documents from collection '%s'. |
| OTMZGNE027 | Failed to insert or update MongoDB , insert or update failed for Collection %s. |
| OTMZCACH001 | Update cache failed for <cacheName>.For example, Update cache failed for 'com.ibm.commerce.inb.data.cache.OTMZRefDataDerivedCapacity'. |