Miscellaneous Error Messages
| Code | 110000 |
| Severity | Debug |
| Message | {0}({1})::setDebugLevel(): Debug level {2} |
| Description | A debugging message, about changes in the debug messages level. |
| Code | 111000 |
| Severity | Critical |
| Message | Store type "{0}" not supported in this version of the platform. |
| Description | An unknown store kind has been requested. Check the model and correct the error. |
| Code | 111001 |
| Severity | Critical |
| Message | Element "{0}" is not valid in this version of the platform. |
| Description | An unknown XML element has been used in the model. Check the model and correct the error. |
| Code | 112000 |
| Severity | Critical |
| Message | DOMParser()::DOMParser(): Fatal error initializing xerces: {0} |
| Description | The XML parser failed to initialize. It should normally never happen. Probably there is some issue with the shared libraries configuration. |
| Code | 112001 |
| Severity | Error |
| Message | DOMParser()::handleError() -- {0} at line {1}, column {2}: {3} |
| Description | A syntax error in an XML file, an CCL Prime model or other. Check the file and correct the error. |
| Code | 113000 |
| Severity | Info |
| Message | Monitor() Lost connection to subscriber {0}, error {1} |
| Description | Obsolete. It was used with the old method of sending the monitoring data. |
| Code | 113001 |
| Severity | Critical |
| Message | Monitor() Could not start timer. |
| Description | Obsolete. It was used with the old method of sending the monitoring data. |
| Code | 113002 |
| Severity | Critical |
| Message | Monitor() Could not initialize XML-RPC. |
| Description | Obsolete. It was used with the old method of sending the monitoring data. |
| Code | 113003 |
| Severity | Error |
| Message | Monitor() Could not establish connection to subscriber {0}, error {1} |
| Description | Obsolete. It was used with the old method of sending the monitoring data. |
| Code | 114000 |
| Severity | Info |
| Message | Platform({0})::Platform(): Created Platform. |
| Description | Information about the internal stages of initialization. |
| Code | 114001 |
| Severity | Info |
| Message | Platform({0})::pauseQueries(): Pausing all SQL queries... |
| Description | Obsolete. |
| Code | 114002 |
| Severity | Info |
| Message | Platform({0})::resumeQueries(): Resuming... |
| Description | Obsolete. |
| Code | 114003 |
| Severity | Info |
| Message | Platform({0})::pauseStreams(): Pausing all streams... |
| Description | Obsolete. |
| Code | 114004 |
| Severity | Info |
| Message | Platform({0})::resumeStreams(): Resuming... |
| Description | Obsolete. |
| Code | 114005 |
| Severity | Info |
| Message | Platform({0})::dumpStreams(). |
| Description | The platform was requested to dump the contents of the streams to XML files. |
| Code | 114006 |
| Severity | Info |
| Message | Platform({0})::run() -- Starting the Platform. |
| Description | Information about the internal stages of initialization. |
| Code | 114007 |
| Severity | Info |
| Message | Platform({0})::run() -- Starting Stream threads. |
| Description | Information about the internal stages of initialization. |
| Code | 114008 |
| Severity | Info |
| Message | Platform({0})::run() -- Starting thread for {1}({2}). |
| Description | Information about the internal stages of initialization. |
| Code | 114009 |
| Severity | Critical |
| Message | Platform({0})::run() -- Thread start failed for {1}({2}). |
| Description | The limit of threads per process is probably exhausted. Consult your system administrator. |
| Code | 114010 |
| Severity | Info |
| Message | Platform({0})::run() -- Waiting to join remaining Stream threads. |
| Description | Obsolete. |
| Code | 114011 |
| Severity | Info |
| Message | Platform({0})::run() -- Joined thread for Stream({1}). |
| Description | The Sybase Event Stream Processor has detected that the thread for this stream has completed. The Sybase Event Stream Processor collects the stream threads in order so a thread that has not yet exited may prevent the following threads from being collected. |
| Code | 114012 |
| Severity | Info |
| Message | Platform({0})::run() -- cleaning up {1}({2}). |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 114013 |
| Severity | Alert |
| Message | Platform({0})::run() -- Platform shutdown complete. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 114014 |
| Severity | Info |
| Message | {0}({1})::initialize() -- Full model checked successfully. |
| Description | In a clustered configuration, the Sybase Event Stream Processor checks that the full clustered model is correct before implementing its part of the cluster. |
| Code | 114015 |
| Severity | Info |
| Message | {0}({1})::initialize() -- Disposing of the full model. |
| Description | In a clustered configuration, the Sybase Event Stream Processor checks that the full clustered model is correct before implementing its part of the cluster. The full model is temporarily instantiated and then disposed of. |
| Code | 114016 |
| Severity | Info |
| Message | {0}({1})::initialize() -- type checking the full model... |
| Description | In a clustered configuration, the Sybase Event Stream Processor checks that the full clustered model is correct before implementing its part of the cluster. |
| Code | 114017 |
| Severity | Info |
| Message | {0}({1})::initialize() -- initializing... |
| Description | Information about the internal stages of initialization. |
| Code | 114018 |
| Severity | Info |
| Message | {0}({1})::initializeStreams() -- Stream {2} subject to insert-only optimizations. |
| Description | The Sybase Event Stream Processor has detected that this stream may only ever receive the INSERT messages and may use this fact for optimization of the processing. |
| Code | 114019 |
| Severity | Critical |
| Message | Platform()::initialize---Two different persistent Stores have the same "file" attribute "{0}"; on dynamic changes any incompatible change of a Store requires changing the file too. |
| Description | Each persistent store must use a different file for its data. If multiple stores were to use the same file, it would corrupt the data. Check the model to ensure that the files for all the stores are different. In case of a dynamic modification, any incompatible changes to a store require a switch to a new file, as the data is converted from the old file to the new one. |
| Code | 114020 |
| Severity | Info |
| Message | {0}({1})::initialize() -- initialization complete. |
| Description | Information about the internal stages of initialization. |
| Code | 114021 |
| Severity | Info |
| Message | Platform::syncSourceStreams() -- pausing all Source Stream input. |
| Description | To synchronize the data, the Sybase Event Stream Processor pauses the input to all source streams and lets it fully process the existing input queues. Afterwards, it syncs all persistent stores to disk, and in case of a cluster, makes sure that the data is propagated to the backup nodes. Eventually it restarts the processing. |
| Code | 114022 |
| Severity | Info |
| Message | Platform::syncSourceStreams() -- took: {0} secs to pause Source Streams. |
| Description | To synchronize the data, the Sybase Event Stream Processor pauses the input to all source streams and lets it fully process the existing input queues. Afterwards, it syncs all persistent stores to disk, and in case of a cluster, makes sure that the data is propagated to the backup nodes. Eventually it restarts the processing. |
| Code | 114023 |
| Severity | Info |
| Message | Platform::syncSourceStreams() -- took: {0} secs for Source Streams.to drain. |
| Description | To synchronize the data, the Sybase Event Stream Processor pauses the input to all source streams and lets it fully process the existing input queues. Afterwards, it syncs all persistent stores to disk, and in case of a cluster, makes sure that the data is propagated to the backup nodes. Eventually it restarts the processing. |
| Code | 114024 |
| Severity | Info |
| Message | Platform::syncSourceStreams() -- took: {0} secs to sync stores. |
| Description | To synchronize the data, the Sybase Event Stream Processor pauses the input to all source streams and lets it fully process the existing input queues. Afterwards, it syncs all persistent stores to disk, and in case of a cluster, makes sure that the data is propagated to the backup nodes. Eventually it restarts the processing. |
| Code | 114025 |
| Severity | Info |
| Message | Platform::syncSourceStreams() -- resumed all Source Stream input. |
| Description | To synchronize the data, the Sybase Event Stream Processor pauses the input to all source streams and lets it fully process the existing input queues. Afterwards, it syncs all persistent stores to disk, and in case of a cluster, makes sure that the data is propagated to the backup nodes. Eventually it restarts the processing. |
| Code | 114026 |
| Severity | Info |
| Message | Platform::quiesced() -- waiting on all queues to drain. |
| Description | The Sybase Event Stream Processor has received a request to quiesce and started draining the queued up data. |
| Code | 114027 |
| Severity | Info |
| Message | Platform::quiesced() -- all queues have drained. |
| Description | The queued up data has been fully processed and drained throughout Sybase Event Stream Processor, the normal processing will resume. |
| Code | 114028 |
| Severity | Info |
| Message | Platform::areQueuesEmpty() -- path rooted at stream {0} still has data in it. |
| Description | On an XMLRPC call asking if the platform is quiesced, these message provide the information on which stream queues still contain data and are busy processing it. |
| Code | 114029 |
| Severity | Critical |
| Message | Platform::initializeStreams() Inner join found in non-insert-only stream {0}. |
| Description | The inner joins are only allowed on the insert-only streams. That is, from a source stream with attribute insertOnly="true" or a stream that is derived only from such source streams and doesn't use certain features like InputWindows. |
| Code | 114030 |
| Severity | Critical |
| Message | Platform({0})::initialize---Two different Streams have the same "ofile" attribute "{1}". |
| Description | The "ofile" attribute may be used to dump the stream contents automatically on the Sybase Event Stream Processor exit. If multiple streams were to dump the data into the same file, it would overwrite each other. Check the model and correct the file names. |
| Code | 114031 |
| Severity | Critical |
| Message | Platform({0})::initialize---the store associated with stream {1} must be not be "stateless". |
| Description | Only some very limited streams may use the stateless store. Most of the streams can't. See the Authoring Reference for details. |
| Code | 114032 |
| Severity | Critical |
| Message | Platform()::buildLogGraph() -- cyclic dependency in logstores, consistent recovery impossible, aborting. |
| Description | For the Log Stores to provide a correct persistence, the streams that use it must follow certain rules of interconnection. If stream S1 uses the persistent store A, and its derived stream S2 uses the persistent store B, none of the streams derived from S2 may use the store A. In general, it's best to either put only the source streams into a persistent store or put the whole "vertical slices" of a model, starting from a source stream and all the streams derived from it into the same persistent store. |
| Code | 114033 |
| Severity | Info |
| Message | Platform()::buildLogGraph() -- logstore checkpoint order: {0} |
| Description | For the Log Stores to provide a correct persistence, the streams that use it must follow a certain order for checkpointing the stores from those containing the most derived information to the ones containing the source information. This informational message shows the order. |
| Code | 114034 |
| Severity | Critical |
| Message | Platform()::buildLogGraph() -- logstore {0}: has children {1} |
| Description | For the Log Stores to provide a correct persistence, the streams that use it must follow a certain order for checkpointing the stores, from those containing the most derived information to ones containing the source information. As this order is being created, these messages show the derivation. |
| Code | 114035 |
| Severity | Debug |
| Message | Platform()::lockExternal() -- locking |
| Description | Only one XMLRPC command may be executed at a time (with the exception of certain long-running commands that wait for a condition). This message shows that a command is acquiring the lock before starting the execution. |
| Code | 114036 |
| Severity | Debug |
| Message | Platform()::unlockExternal -- unlocking |
| Description | Only one XMLRPC command may be executed at a time (with the exception of certain long-running commands that wait for a condition). This message shows that a command has completed its execution, and other commands may run now. |
| Code | 114037 |
| Severity | Error |
| Message | Platform()::syncSourceStreams -- redundancy is set, but sync of secondary failed! |
| Description | You should check if the slave node of the cluster has failed or was not yet started. |
| Code | 114038 |
| Severity | Error |
| Message | Platform()::setStreamRedundancy -- could not establish XMLrpc connection to secondary! |
| Description | You should check if the slave node of the cluster has failed or was not yet started. |
| Code | 114039 |
| Severity | Info |
| Message | Platform({0})::XML Model Version: {1} |
| Description | It has information about the CCL Prime version of the model being loaded. |
| Code | 114040 |
| Severity | Warning |
| Message | Platform({0})::Warning, no XML Model Version Specified. |
| Description | The information about the CCL Prime version of the model being loaded is not present in the model. If no syntax errors are found, the Sybase Event Stream Processor attempts to execute the model anyway. |
| Code | 114041 |
| Severity | Critical |
| Message | Platform({0})::Mismatched XML Model Version detected, expected: {1}, found: {2} |
| Description | Probably the model was developed for a different version of CCL Prime. Use the tool esp_upgrade for conversion of the models to the current version. |
| Code | 114042 |
| Severity | Critical |
| Message | {0}({1})::Bad access control specification: '{2}' is not a pair of strings separated by ':'. |
| Description | The attribute "restrictAccess" has been misformatted. It must contain a space-separated list of colon-separated pairs. Check the model and correct it. |
| Code | 114043 |
| Severity | Critical |
| Message | {0}({1})::Bad access control specification: unknown access control type in pair '{2}'. |
| Description | The attribute "restrictAccess" has been misformatted. Check the model and correct it. |
| Code | 114044 |
| Severity | Critical |
| Message | Platform()::initialize -- cluster '{0}' module '{1}' is not in the config file. |
| Description | In a clustered model, the module specified with option -M of the cluster specified with the option -C of the command line is not present in the model. Check and correct the command line arguments and/or the model. |
| Code | 114045 |
| Severity | Critical |
| Message | Platform()::changeRestriction -- Bad 'from' restriction value {0} |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114046 |
| Severity | Critical |
| Message | Platform()::changeRestriction -- Bad 'to' restriction value {0} |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114047 |
| Severity | Critical |
| Message | Platform()::changeRestriction -- Can't change restriction when a platform is down. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114048 |
| Severity | Critical |
| Message | Platform()::changeRestriction -- State consistency error, no restrictions of {0} seen yet. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114049 |
| Severity | Critical |
| Message | Platform(): unknown platform modification option '{0}'. |
| Description | The dynamic modification XMLRPC command may be given a number of options. See the Administrator's Guide for the information on the Dynamic Services. |
| Code | 114050 |
| Severity | Info |
| Message | Platform()::modify(): modifying stream config {0}({1}). |
| Description | The dynamic modification has requested a compatible modification of this stream. The stream is modified in place. |
| Code | 114051 |
| Severity | Info |
| Message | Platform()::modify(): modification of {0}({1}) succeeded. |
| Description | The dynamic modification has requested a compatible modification of this stream. The stream was successfully modified. |
| Code | 114052 |
| Severity | Critical |
| Message | Platform()::modify(): modification of {0}({1}) FAILED. |
| Description | The dynamic modification has requested a compatible modification of this stream. The stream could not be modified. See the preceding error messages for error details. The whole modification is rolled back. Check the new model and correct the error. |
| Code | 114053 |
| Severity | Info |
| Message | Platform()::modify(): committing modification of {0}({1}). |
| Description | The dynamic modification has requested a compatible modification of this stream. All the modifications have succeeded, so now it is committed. |
| Code | 114054 |
| Severity | Info |
| Message | Platform()::modify(): rolling back modification of {0}({1}). |
| Description | The dynamic modification has requested a compatible modification of this stream. An attempt to modify this or another stream has failed so all modifications are rolled back. |
| Code | 114055 |
| Severity | Critical |
| Message | Platform()::modify(): Failed to add node {0}({1}). |
| Description | The dynamic modification has requested to add a new XML element, but the addition has failed. The preceding error messages may contain more information about the reasons of the failure. |
| Code | 114056 |
| Severity | Info |
| Message | Platform()::modify(): Initializing the newly added {0}({1}). |
| Description | The dynamic modification has requested to add a new stream so it is now added. |
| Code | 114057 |
| Severity | Critical |
| Message | Platform()::modify(): Dynamic configuration modifications are not supported in clustered mode. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. The dynamic modifications may not be applied to an instance of Sybase Event Stream Processor that is a part of a cluster. |
| Code | 114058 |
| Severity | Info |
| Message | Platform()::modify(): Preparing to delete old {0}({1}). |
| Description | MSG_PLATFORM_MOD_PREP_DELSTREAM |
| Code | 114059 |
| Severity | Info |
| Message | Platform()::run() -- Starting platform shutdown. |
| Description | MSG_PLATFORM_START_SHUTDOWN |
| Code | 114060 |
| Severity | Critical |
| Message | Platform()::initialize: Non-metadata stream {0}({1}) is not allowed to use ESPMetadataStore. |
| Description | The names starting with "ESP" are reserved and cannot be used in a model. |
| Code | 114061 |
| Severity | Info |
| Message | Platform()::modify(): Renaming node {0}({1}) to {2}({3}). |
| Description | The dynamic modification has requested to rename an XML element. It is now renamed. |
| Code | 114062 |
| Severity | Info |
| Message | Platform()::modify(): Renaming node {0}({1}) back to {2}({3}). |
| Description | The dynamic modification has requested to rename an XML element. Some part of the modification has failed so the element is renamed back. |
| Code | 114063 |
| Severity | Info |
| Message | Platform()::modify(): The old node {0}({1}) will be deleted. |
| Description | The dynamic modification has requested to delete an XML element. It is now deleted. |
| Code | 114064 |
| Severity | Critical |
| Message | Platform()::modify(): Requested modification on the Source Stream {0}({1}) is potentially unsafe, use option "base" to override. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. The source streams are different from the other streams in the way that its contents can not be regenerated. Any incompatible changes would cause a data loss. Therefore, the option "base" must be specified to allow any incompatible changes to prevent the accidental data loss. If it was not intended, check the model and correct it. The data in the changed source streams may be transferred from the old model to the new one through use of the conversion model. |
| Code | 114065 |
| Severity | Critical |
| Message | Platform()::modify(): The data directory "{0}" for dynamically added store {1}({2}) already exists. |
| Description | Each persistent store must use a different file for its data. If multiple stores were to use the same file, it would corrupt the data. Check the model to ensure that the files for all the stores are different. In case of a dynamic modification, any incompatible changes to a store require a switch to a new file, as the data is converted from the old file to the new one. |
| Code | 114066 |
| Severity | Critical |
| Message | Platform()::modify(): Invalid renaming attempt of node {0}({1}) to {2}({3}). |
| Description | The renaming must be direct. The new name must not be the same as the name of any other node in the new model. Also an old node can not be renamed to more than one new name. Check the new model and correct the error. |
| Code | 114067 |
| Severity | Info |
| Message | Platform()::modify(): modifying store config {0}({1}). |
| Description | The dynamic modification has requested a compatible modification of this store. The store is modified in place. |
| Code | 114068 |
| Severity | Info |
| Message | Platform()::modify(): Node {0}({1}) is marked as modified because it depends on a modified node {2}({3}). |
| Description | Certain XML nodes in the model are used by other nodes. For example, the <Globals> node is used by the streams. Any change to such underlying node requires all the dependent nodes to be recompiled, even though they might not be changed themselves. The dynamic modification does such recompilation automatically. This message displays such dependencies found by the dynamic services. |
| Code | 114068 |
| Severity | Info |
| Message | Platform()::modify(): Stream {0}({1}) will be deleted and re-created, because its store {2}({3}) gets re-created. |
| Description | In case if a store is dynamically modified in an incompatible way, this is processed by deleting the store and creating a new one with the same name but different configuration. Since the streams are tied to a store, this means that any streams using this store must also be deleted and reincarnated even if these streams have no incompatible changes. |
| Code | 114069 |
| Severity | Critical |
| Message | Platform()::modify(): options '{0}' and '{1}' are mutually exclusive. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. The requested dynamic modification options are incompatible. Check and correct your request. |
| Code | 114069 |
| Severity | Info |
| Message | Platform()::modify(): Deleting old {0}({1}). |
| Description | A node was present in the old model but not in the new one. It will be deleted during the modification. |
| Code | 114070 |
| Severity | Info |
| Message | Platform()::modify(): modifying node {0}({1}). |
| Description | The dynamic modification has requested a compatible modification of this node. It is modified in place. |
| Code | 114071 |
| Severity | Critical |
| Message | Platform()::modify(): An incompatible change requested for {0}({1}), possibly as a propagation of other changes. Not allowed with option 'noregen'. |
| Description | The option "noregen" bypasses the regeneration after the dynamic modification. It expects that the user knows this would not introduce a major discrepancy in the data or accept such a discrepancy, such as a tradeoff for a faster modification. The incompatible changes are not allowed with the option "noregen" since this combination would cause grossly misformatted data that may cause the Sybase Event Stream Processor to crash. Remove the option "noregen" from the dynamic modification request to resolve this issue. |
| Code | 114072 |
| Severity | Critical |
| Message | Platform()::initialize(): A conversion model may not use log stores, found {0}({1}). |
| Description | The conversion model is temporary by definition, and it takes the data from the old model and creates the data to be put into the new model. The persistent stores may not be used in the conversion model. Change the conversion model to use the memory store. |
| Code | 114073 |
| Severity | Critical |
| Message | Platform()::initialize(): Stream {0}({1}) in a normal platform may not use attributes 'convsrc' and 'convdst'. |
| Description | The attributes "convsrc" and "convdst" are reserved for use in the conversion model, to describe how it is connected to the streams in the old and new model. Change your model to not use these attributes. |
| Code | 114074 |
| Severity | Critical |
| Message | Platform()::initialize(): Stream {0}({1}) in a conversion must have the 'convsrc' attribute. |
| Description | Each source stream in the conversion model must take its data from a stream in the old model. The attribute "convsrc" sets up this connection. Correct your conversion model. |
| Code | 114075 |
| Severity | Critical |
| Message | Platform()::initialize(): Attribute 'convsrc' of {0}({1}) refers to an unknown stream '{2}'. |
| Description | Each source stream in the conversion model must take its data from a stream in the old model. The attribute "convsrc" names the stream in the old model. No such stream exists in the old model. Correct your conversion model. |
| Code | 114076 |
| Severity | Critical |
| Message | Platform()::initialize(): Attribute 'convdst' of {0}({1}) refers to an unknown or unsuitable stream '{2}', which must be a Source Stream. |
| Description | The results of the conversion model are to be placed into the source streams of the new model. The attribute "convdst" names the stream in the new model. No such source stream exists in the new model. Correct your conversion model. |
| Code | 114077 |
| Severity | Info |
| Message | Platform()::run() -- All stream threads exited. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 114078 |
| Severity | Warning |
| Message | Platform()::setMtDebugString() -- Unknown suboption '{0}'. |
| Description | The option -D may be used to specify a set of debugging features. Only a limited subset of these features is published, the rest are used internally by ESP. The suboptions are specified as the letter(s) following -D, such as -DD. Check and correct your command line. |
| Code | 114079 |
| Severity | Alert |
| Message | Platform()::run -- Platform Server alive & ready for services |
| Description | Information that the initialization is completed. |
| Code | 114080 |
| Severity | Info |
| Message | Platform::quiesceMeta() -- waiting on metadata queues to drain. |
| Description | The shutdown procedure, dynamic modifications and certain other requests require that all the streams in the Sybase Event Stream Processor be quiesced, including the metadata streams. This indicates the start of the quiescence of the metadata streams. |
| Code | 114081 |
| Severity | Info |
| Message | Platform::quiesceMeta() -- metadata queues have drained. |
| Description | The shutdown procedure, dynamic modifications and certain other requests require that all streams in the Sybase Event Stream Processor be quiesced, including the metadata streams. This indicates the completion of the quiescence of the metadata streams. |
| Code | 114082 |
| Severity | Critical |
| Message | PlatformControl()::quiesceMeta -- called at wrong restriction level {0}, ignored |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114083 |
| Severity | Info |
| Message | Platform()::enableTrace() -- {0} the trace mode. |
| Description | The request to enable or disable trace mode was received and processed. |
| Code | 114084 |
| Severity | Warning |
| Message | Platform()::modify() -- can not be modified while in trace mode. |
| Description | While the Sybase Event Stream Processor is in the trace mode, the dynamic modifications may not be applied. Disable the trace mode and retry the dynamic modification. |
| Code | 114085 |
| Severity | Info |
| Message | Platform()::traceRequestPause() -- Platform is being paused. |
| Description | The pause request was received and processed from XMLRPC or on a breakpoint. The state of the Sybase Event Stream Processor may now be examined. |
| Code | 114086 |
| Severity | Info |
| Message | Platform()::traceRun() -- Platform has continued running. |
| Description | The Sybase Event Stream Processor has continued running after being paused. |
| Code | 114087 |
| Severity | Critical |
| Message | Platform()::loadConnections(): Connections initialization failure: {0} |
| Description | A connection type shared library could not be loaded. The message contains the detailed reason. This connection type then may not be used in the models, and attempts to use it are reported as a syntax error. Check that the shared library is present, has correct permissions, was built for the correct architecture and this exact version of the Sybase Event Stream Processor. |
| Code | 114088 |
| Severity | Critical |
| Message | Platform({0})::initialize -- Two different Connectors have the same "name" attribute "{1}". |
| Description | Each Connection must have an unique name. Check and correct the model. |
| Code | 114089 |
| Severity | Info |
| Message | Platform()::run() -- Starting the Connectors. |
| Description | Information about the internal stages of initialization. |
| Code | 114090 |
| Severity | Info |
| Message | Platform()::run() -- Waiting for Connectors to complete the initial loading. |
| Description | Some connection types are "one-shot", in that it loads a set of data when started and exited. The Sybase Event Stream Processor lets these connections load data to initialize the model before continuing with the normal operations. See the Authoring Guide for more information on the connection states. An incorrectly programmed connection type (especially the user-defined types) may never report that it has completed the initial loading and would cause the Sybase Event Stream Processor to be stuck forever. If such a situation occurs, check your connections. |
| Code | 114091 |
| Severity | Info |
| Message | Platform()::run() -- Connectors completed the initial loading. |
| Description | Information about the internal stages of initialization. |
| Code | 114092 |
| Severity | Critical |
| Message | Platform()::initialize -- A connector on stream '{0}' has no name. |
| Description | Each Connection must have an unique name. Check and correct the model. |
| Code | 114093 |
| Severity | Critical |
| Message | Platform()::initialize -- The 'connection' attribute is missing in ConnectionRef node {0} |
| Description | Each ConnectionRef in the start-up sequence must refer to an existing Connection node. Check and correct the model. |
| Code | 114094 |
| Severity | Critical |
| Message | Platform()::initialize -- The StartUp has multiple references to Connection '{0}'. |
| Description | If the start-up sequence is specified explicitly in the StartUp node, it must refer exactly once to each of the Connection nodes. Check and correct the model. |
| Code | 114095 |
| Severity | Critical |
| Message | Platform()::initialize -- ConnectionRef refers to a non-existing Connection name '{0}'. |
| Description | Each ConnectionRef in the start-up sequence must refer to an existing Connection node. Check and correct the model. |
| Code | 114096 |
| Severity | Critical |
| Message | Platform()::initialize -- The StartUp has no references to Connection '{0}', list it under <ConnectionGroup type="nostart"> if it doesn't need to be started automatically. |
| Description | If the start-up sequence is specified explicitly in the StartUp node, it must refer exactly once to each of the Connection nodes. Check and correct the model. |
| Code | 114097 |
| Severity | Warning |
| Message | Platform()::run() -- Connector '{0}' start failure: {1} |
| Description | A connection has failed to start, with the specified reason. Check and correct the connection parameters if necessary. Check the external environment for possible issues (such as sockets being already used by other processes, incorrect paths etc). |
| Code | 114098 |
| Severity | Warning |
| Message | Platform()::run() -- Internal error, can not find the stream for Connector '{0}'. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 114099 |
| Severity | Critical |
| Message | Platform()::initialize -- Only one StartUp node is supported per module. |
| Description | The model may have at most one StartUp node for each module of the cluster, or one StartUp node for the whole non-clustered model. Check and correct the model. |
| Code | 114100 |
| Severity | Critical |
| Message | Platform()::initialize -- Only one Global node is supported per module. |
| Description | The model may have at most one Global node for each module of the cluster, or one Global node for the whole non-clustered model. Check and correct the model. |
| Code | 114101 |
| Severity | Critical |
| Message | Platform()::initialize -- Error found in Global declarations: {0} |
| Description | The global declaration contains a syntax error. Check and correct the model. |
| Code | 114102 |
| Severity | Critical |
| Message | Platform(): dynamic modification of Global is not permitted in 'noregen' mode. |
| Description | The option "noregen" bypasses the regeneration after the dynamic modification. It expects that the user knows this would not introduce a major discrepancy in the data or accepts such a discrepancy, as a tradeoff for a faster modification. The changes to the Globals are not allowed with the option "noregen" since this combination may cause the stream types to change, which would cause grossly misformatted data that may cause the Sybase Event Stream Processor to crash. Remove the option "noregen" from the dynamic modification request to resolve this issue. |
| Code | 114103 |
| Severity | Critical |
| Message | Platform(): Error in compiling Global initializer expression: {0} |
| Description | The global declaration contains a syntax error. Check and correct the model. |
| Code | 114104 |
| Severity | Info |
| Message | Platform()::run -- Platform Command Server is started. |
| Description | Information about the internal stages of initialization. |
| Code | 114105 |
| Severity | Alert |
| Message | Platform()::notifyRequestExit() -- Platform shutdown sequence initiated. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 114108 |
| Severity | Info |
| Message | Platform::quiesceSource -- waiting for SourceStreams input queues to drain. |
| Description | Committing the input to the store requires that the source streams fully process their current input queue. No new data will be put into their input queue until the existing requests are processed and committed to the store. |
| Code | 114109 |
| Severity | Info |
| Message | Platform::quiesceSource -- SourceStreams input queues have drained. |
| Description | The source streams have fully processed their input. |
| Code | 114110 |
| Severity | Error |
| Message | Platform()::daemonize(): Switching to daemon mode. |
| Description | All the log messages after this one are written to syslog. |
| Code | 114111 |
| Severity | Error |
| Message | Platform()::daemonize(): Daemon process current directory set to '{0}'. |
| Description | During daemonization the Sybase Event Stream Processor may change its current directory to avoid holding down the directory where it was started. It expects all file pathnames to be specified either as absolute or relative to the new current directory. |
| Code | 114112 |
| Severity | Error |
| Message | Platform()::validateLicense(): Could not allocate license control object. |
| Description | Contact your system administrator to either increase the per-process memory usage limits or add physical memory to the machine. |
| Code | 114113 |
| Severity | Error |
| Message | Platform()::processSignal(): fatal error in thread id {0}, thread name '{1}'; aborting. |
| Description | Some major crash has happened in the Sybase Event Stream Processor. Ideally, this should never happen. If it happens, collect the log file, the core dump and the Sybase Event Stream Processor binaries and contact the Sybase support. If you can provide a way to reproduce this crash, preferably with a smaller model and data set, it would be very helpful and lead to a quicker fix. |
| Code | 114113 |
| Severity | Error |
| Message | Platform()::initialize(): Unable to set the time rate {0} |
| Description | The time rate specified at command line with option -R is incorrect. Check and correct your command line. |
| Code | 114114 |
| Severity | Error |
| Message | Platform():daemonize(): could not fork the daemonized process: {0} ({1}) |
| Description | The fork() system call that creates the daemonized process has failed. Possibly the system has run out of resources. Check with your system administrator. |
| Code | 114115 |
| Severity | Critical |
| Message | Platform()::lockExternal() -- timed out at {0} sec., the current owner of the lock is '{1}'. |
| Description | Only one XMLRPC command may be executed at a time (with the exception of certain long-running commands that wait for a condition). This message shows that a command could not get this exclusive access for a relatively long period of time and gave up. The message shows the information about the other outstanding command that is currently hogging the exclusive access. For some commands, such as those that perform the Dynamic Service modifications, taking a long time is normal. |
| Code | 114116 |
| Severity | Critical |
| Message | Platform(): -- no value supplied for required parameter {0}. |
| Description | Value was not supplied for a required parameter. You need to supply a value, or make the parameter optional by specifying a default value in CCL. |
| Code | 114117 |
| Severity | Warning |
| Message | Platform(): -- value(s) supplied for undeclared parameter(s) {0}. |
| Description | Values supplied for parameters that have not been declared. Check to make sure you spelled the parameter name correctly, and make sure you've declared the parameter in CCL. |
| Code | 114118 |
| Severity | Critical |
| Message | Platform(): -- a module parameter {0} has no default value. Either compilation has failed to produce a valid model, or the server's CCX file has been altered. |
| Description | A module parameter does not have a default value. This should never happen, as the compiler should always ensure that a module's parameter is given a value. |
| Code | 114119 |
| Severity | Critical |
| Message | Platform(): -- the module parameter {0} has rejected the value of the parameter it was mapped to. Either compilation has failed to produce a valid model, or the server's CCX file has been altered. |
| Description | The value of a mapped parameter should ALWAYS be accepted. If not, then there is a possible type mismatch or a failure to ensure type compatibility in the compiler. |
| Code | 114120 |
| Severity | Critical |
| Message | Platform(): -- the module parameter {0} is mapped to a nonexistent parameter. Either compilation has failed to produce a valid model, or the server's CCX file has been altered. |
| Description | The compiler should always ensure that a mapping is valid, meaning that among other things the external parameter should exist. |
| Code | 115000 |
| Severity | Critical |
| Message | Authenticate(): Could not initialize PAM layer. |
| Description | Probably PAM is not configured in the operating system. Check with your system administrator. |
| Code | 115001 |
| Severity | Critical |
| Message | Authenticate(): Could not shutdown PAM layer. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 115002 |
| Severity | Critical |
| Message | Authenticate()::setDirectDatabase(): Syntax error in user name at '{0}-.20s...'. |
| Description | The testing user database specified with option -A is misformatted. Check and correct your command line. |
| Code | 115003 |
| Severity | Critical |
| Message | Authenticate()::setDirectDatabase(): Syntax error after user name '{0}'. |
| Description | The testing user database specified with option -A is misformatted. Check and correct your command line. |
| Code | 115004 |
| Severity | Critical |
| Message | Authenticate()::setDirectDatabase(): Syntax error after password for user '{0}'. |
| Description | The testing user database specified with option -A is misformatted. Check and correct your command line. |
| Code | 115005 |
| Severity | Critical |
| Message | Authenticate()::setDirectDatabase(): Syntax error after role '{0}' for user '{1}'. |
| Description | The testing user database specified with option -A is misformatted. Check and correct your command line. |
| Code | 116000 |
| Severity | Notice |
| Message | SqlControl({0}): Authentication successful for user {1}, database {2} |
| Description | Informational message about a successful login to the ODBC service. |
| Code | 116001 |
| Severity | Error |
| Message | SqlControl({0}): Authentication rejected for user {1}, database {2} |
| Description | A client tried to log in to the ODBC service with a wrong password or unknown RSA key. If you believe that the password is correct and PAM authentication method is used, contact your system administrator to check the PAM configuration. If you believe that the RSA key is correct, and the RSA authentication is used, check whether the matching public key is installed in the server's RSA public key directory. Make sure that the client uses the secret key file and the server has the public key file, not the other way around. See the Administrator's Guide for details. |
| Code | 116002 |
| Severity | Notice |
| Message | SqlControl({0}): exited control thread on port {1} |
| Description | The Sybase Event Stream Processor has completed servicing queries from an ODBC client. |
| Code | 116003 |
| Severity | Notice |
| Message | SqlControl({0}): Skipping message from client of size {1} because it's too large |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 116004 |
| Severity | Notice |
| Message | SqlControl({0}): Detected shutdown of client socket |
| Description | An ODBC client has disconnected from the socket. |
| Code | 116005 |
| Severity | Notice |
| Message | SqlControl({0}): Detected large, possibly bad message from client of size {1} |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 116006 |
| Severity | Notice |
| Message | SqlControl({0}): started control thread |
| Description | A new ODBC service thread was created for a new ODBC connection. |
| Code | 116007 |
| Severity | Debug |
| Message | SqlControl({0}): Received SQL statement {1} |
| Description | An SQL query was received from an ODBC client. |
| Code | 116008 |
| Severity | Debug |
| Message | SqlControl({0}): started SQL statement execution. |
| Description | The SQL query was parsed successfully, and its execution has started. |
| Code | 116009 |
| Severity | Debug |
| Message | SqlControl({0}): ended SQL statement execution. |
| Description | The SQL query execution has completed. If any errors were detected, it was reported to the ODBC client. |
| Code | 116010 |
| Severity | Debug |
| Message | SqlControl({0}): started result set send. |
| Description | The SQL query has completed successfully, and the results are about to be sent to the ODBC client. |
| Code | 116011 |
| Severity | Debug |
| Message | SqlControl({0}): ended result set send. |
| Description | The SQL query results have been fully sent to the client. |
| Code | 117000 |
| Severity | Critical |
| Message | SqlQuery(): could not get ephemeral port. |
| Description | An attempt to find an unused port number for ODBC service has failed. Probably there is some major issue in the machine's networking configuration. There is also a possibility of a rare failure if two instances of Sybase Event Stream Processor or a similar program try to allocate unused port numbers at the same time. |
| Code | 117001 |
| Severity | Critical |
| Message | SqlQuery({0}): could not bind port {1} |
| Description | The explicit port specified with the command line option -q is already taken by another program, or possibly by another copy of the server already running. Check with your system administrator. |
| Code | 117002 |
| Severity | Info |
| Message | SqlQuery({0}): listening on port {1} |
| Description | An informational message about starting the ODBC service. Shows the port number that may have been specified with option -q or chosen automatically with the parameter -q 0. Lack of this message may mean that the option -q was not specified and the ODBC service was not started. |
| Code | 117003 |
| Severity | Notice |
| Message | SqlQuery({0}): spawned control thread on port {1} |
| Description | A connection has been received from an ODBC client and a server thread has been created to service it. |
| Code | 118000 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- file exists, but is truncated, cannot continue. |
| Description | The Log Store data file is probably corrupted in some way. |
| Code | 118001 |
| Severity | Info |
| Message | LogFile({0})::LogFile() -- opening existing log file of size {1} |
| Description | An informational message about the file used for LogStore. |
| Code | 118002 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- could not open file: {1} |
| Description | The Sybase Event Stream Processor has experienced an error when trying to open a LogStore file. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is correct. |
| Code | 118003 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- could not create file: {1} |
| Description | The Sybase Event Stream Processor has experienced an error when trying to open a LogStore file. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is correct. |
| Code | 118004 |
| Severity | Info |
| Message | LogFile({0})::LogFile() -- extending new log file to {1} bytes. |
| Description | The LogStore file already existed but was shorter than specified in the model. It was extended to the new specification. |
| Code | 118005 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- could not map file: {1} |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118006 |
| Severity | Critical |
| Message | LogFile({0})::~LogFile( ) -- could not unmap file. |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118007 |
| Severity | Critical |
| Message | {0}({1})::LogFile() -- bad magic number. |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118008 |
| Severity | Critical |
| Message | {0}({1})::LogFile() -- bad checksum. |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118009 |
| Severity | Critical |
| Message | {0}({1})::LogFile() -- incompatible version number {2}{3}, current {4}{5} |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118010 |
| Severity | Debug |
| Message | LogFile({0})::~LogFile() -- logfile closed. |
| Description | The LogStore file has been unmapped and closed. |
| Code | 118011 |
| Severity | Debug |
| Message | LogFile({0})::alloc( {1} ) -- at address {2} |
| Description | The details of the internal space allocation in the LogStore. |
| Code | 118012 |
| Severity | Debug |
| Message | LogFile({0})::append( {1}, {2} ) -- written to address {3} |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118013 |
| Severity | Debug |
| Message | LogFile({0})::write( {1}, {2}, {3} ) |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118014 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- could not extend file: {1} |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118015 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- could not mark file with EOF mark: {1} |
| Description | An attempt was made to open a LogStore file in a newer format, created with a newer version of the Sybase Event Stream Processor. It may also happen the other way around, when opening a much older file with a new version of the platform, that does not know any more, how to upgrade such a file. When the Sybase Event Stream Processor opens an older supported LogStore file, it upgrades its format to the new version, and the older version of the Sybase Event Stream Processor won't be able to open this file any more. The workaround is to dump the data with a compatible version of the Sybase Event Stream Processor and reload it from scratch. |
| Code | 118016 |
| Severity | Info |
| Message | LogFile({0})::alloc() -- wrapping logfile(len), tail={1}, size={2}, requested length={3} |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118016 |
| Severity | Info |
| Message | LogFile({0})::alloc() -- wrapping logfile(align), tail={1}, size={2}, requested length={3} |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118017 |
| Severity | Info |
| Message | LogFile({0})::append() -- wrapping logfile(len), tail={1}, size={2}, requested length={3} |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118017 |
| Severity | Info |
| Message | LogFile({0})::append() -- wrapping logfile(align), tail={1}, size={2}, requested length={3} |
| Description | The last write position in the LogStore has reached the end of file and continued writing circularly from the start of the file. The log cleaning makes sure that the valid data does not get overwritten. The frequency of log wraps shows the intensity of the data modifications in the store. |
| Code | 118018 |
| Severity | Info |
| Message | {0}({1})::LogFile() -- upgraded file version from {2}{3} to {4}{5} |
| Description | When the Sybase Event Stream Processor opens an existing LogStore of an older version, it transparently upgrades the format of the store to the newer version. The LogStore version numbers are not directly related to the Sybase Event Stream Processor version numbers. Such an upgraded LogStore can not be opened by the old version of the Sybase Event Stream Processor any more. To preserve the compatibility with the older versions, either make a backup copy of the LogStore in advance or dump the contents of the store into XML with the new Sybase Event Stream Processor version and load the data back into the old platform version. |
| Code | 118019 |
| Severity | Critical |
| Message | LogFile({0}) -- overfilled, tried to overwrite its head, stopping. |
| Description | The specified Log Store size was too small and ran out of space. Monitor the Log Store usage and increase it in advance to prevent this fatal error. The store reserve is intended to guarantee against this situation, but in exceptional circumstances it still may happen. If the log store comes to this condition, it can not be resized any more. You must start with a new clean store (and increase its size too). |
| Code | 118020 |
| Severity | Critical |
| Message | LogFile({0})::LogFile() -- probably another platform instance is already running, could not lock file: {1} |
| Description | To prevent multiple instances of Sybase Event Stream Processor from trying to write to the same file and corrupting it, the Sybase Event Stream Processor locks its LogStore files. If the file is already locked by some other process, it can not be used. |
| Code | 118021 |
| Severity | Info |
| Message | LogFile({0})::LogFile() mapped at address, 0x{1}, size, {2} bytes. |
| Description | Informational message that the LogStore file has been successfully mapped into memory. |
| Code | 118022 |
| Severity | Info |
| Message | LogFile({0})::LogFile() The log file size can not be reduced, running with the old size {1} MB. |
| Description | The log file size can not be safely reduced in the model before restarting it. The model will continue running with the old file size. The only way to reduce the log file is to delete the store and have it re-created from scratch. To preserve the data, save it and reload afterwards. |
| Code | 119000 |
| Severity | Critical |
| Message | LogFile({0})::sync( {1}, {2} ): msync() failed, errno: {3}, errmsg: {4} |
| Description | Possibly the underlying disk drive or filesystem has failed. Consult the system administrator. If no disk error, contact the Sybase support. |