Octopus Administrator's Guide
Octopus Error and Warning Messages

 

Octopus error messages are displayed on the screen, unless the process generating the message is running as a service, daemon, or background process.

All Octopus error and warning messages are recorded in the Octopus log file. The name and location of this file (given the extension .otl) are specified with the LogFile parameter in the OCTOPUS section(s) of the nucleus.ini file. On Windows platforms, errors, warnings, and other information can be viewed from the Event Viewer (Application Log) as well.

Each remote Octopus agent also writes the messages and warnings that pertain to the OctoEng’s under its control to its own log file, as specified in the [OCTOPUS AGENT] section of the Node's nucleus.ini file.

Octopus log files can be reset by executing the OctoRollLog program locally or remotely.

The Octopus error and warning messages are grouped as follows:


Note:

 

OctoEng Errors (O0062 - O0065)

O0062E Octopus Keep Change executed by authorization user FAILED. The command returned: message
The SET UPDATE KEEP CHANGE command could not execute successfully. View the message returned from the OctoEng for further information.

O0065E Octopus Keep Change Set Current executed by authorization user FAILED. The command returned: message
The SET UPDATE KEEP CHANGE SET CURRENT command could not execute successfully. View the message returned from the OctoEng for further information.

 

Octopus Startup/Shutdown Messages (O0095 - O0199)

O0095E Invalid LOGFILE: x
An internal error involving the LogFile parameter occurred. The log file could not be opened.

O0096E Error: Unable to open log file: x
When this error is returned, it may be because of an incorrect path specification for the log file in the LogFile parameter in the nucleus.ini file, because the file is already open for reading or writing (possibly by another instance of Octopus), or because there is insufficient space available on the system to open the file.

O0100E Invalid TRACEFILE: x
An internal error involving Octopus tracing occurred. The trace file could not be opened.

O0101E Unable to open trace file: x
When this error is returned, it may be because the file is already open for reading or writing (possibly by another instance of Octopus), or because there is insufficient space available on the system to open the file.

O0102E Invalid STATFILE: x
An internal error involving the StatFile parameter occurred. The detailed statistics file could not be opened.

O0103E Unable to open stat file: x
When this error is returned, it may be because of an incorrect path specification for the detailed statistics file in the StatFile parameter in the nucleus.ini file, because the file is already open for reading or writing (possibly by another instance of Octopus), or because there is insufficient space available on the system to open the file.

O0104E Invalid CSTATFILE file: x
An internal error involving the CStatFile parameter occurred. The cumulative statistics file could not be opened.

O0105E Unable to open cstat file: x
When this error is returned, it may be because of an incorrect path specification for the cumulative statistics file in the CStatFile parameter in the nucleus.ini file, because the file is already open for reading or writing (possibly by another instance of Octopus), or because there is insufficient space available on the system to open the file.

O0106E Unable to start this process: There is an OctoAgnt (pid=x) using the port y
This error is returned when attempting to start Octopus or Octopus Agent using a port (y) that is currently being used by another Octopus Agent process. See Error O0108E for further information.

O0107E Unable to start this process: There is an Octopus (pid=x) DB=y using the port z
This error is returned when attempting to start Octopus or Octopus Agent using a port (z) that is currently being used by another Octopus instance. See Error O0108E for further information.

O0108E The nucleus.ini section that it was started from is x. Check your settings and retry
If Octopus error O0106E or O0107E is returned, this message is included to provide additional information. Change the port number in the specified section (x) of the nucleus.ini file so that the port used by Octopus or Octopus Agent does not conflict with that of another Octopus/Octopus Agent process.

O0109E Maximum number of Octopus/OctoAgnt processes reached for this machine
This error is returned when attempting to start a 65th Octopus or Octopus Agent process on the same machine. The maximum number of combined Octopus and Octopus Agent processes per machine is 64.

O0110E Unable to start this process, there is an Octopus/OctoAgnt (pid=x) running with section named y.
This error is returned when attempting to start Octopus using an Octopus section (y) in the nucleus.ini file that was used to start another Octopus process. The error is also returned when attempting to start a second Octopus Agent process on the same machine.

O0111E Unable to find the section named ->x<- in file y
This error is returned on Octopus startup if the Octopus section name specified in the startup command is not found in the nucleus.ini file. The error is also returned on Octopus Agent startup if there is no [Octopus Agent] section in the nucleus.ini file.

O0112E Octopus usage: octopus OctopusSection
             where OctopusSection is a valid section from nucleus.ini

An attempt was made to start Octopus without a command line parameter. Octopus must be invoked with reference to a valid Octopus section in the nucleus.ini file.

O0113E Octoagnt usage: octoagnt
An attempt was made to start Octopus Agent with more than one command line arguments. The octoagnt executable should be started without any parameters.

O0114W Cannot open nucleus.ini, OctoStartup facility will be disabled
This warning is returned when the nucleus.ini file could not be opened for reading while attempting to start an Octopus instance using OctoStartup. Ensure that the SAND CDBMS SUPPORT path exists, the nucleus.ini file is located in the SUPPORT path, and the length of the full path does not exceed 1000 characters.

O0115W Cannot find Parameter Port in Section [ServiceOctopus], OctoStartup facility will be disabled
This warning is returned when attempting to start an Octopus instance using OctoStartup and the [ServiceOctopus] section in the nucleus.ini file does not contain a Port parameter. Ensure that a unique [ServiceOctopus] port value is specified in the nucleus.ini file.

O0121E DatabaseName not specified
This error is returned when Octopus cannot find a DatabaseName specification in the nucleus.ini file.

O0122W DatabasePath not specified
This warning is returned when Octopus cannot find a DatabasePath specification in the nucleus.ini file. The default value (current directory) will be used.

O0124W Invalid TraceLevel specified
This warning is returned when a value outside the range 0 - 255 is specified for the TraceLevel parameter in the nucleus.ini file. The default value (no trace) will be used. Note that only SAND personnel should set the TraceLevel parameter.

O0126W Invalid StatInterval specified
This warning is returned when a value less than 5 is specified for the StatInterval parameter in the nucleus.ini file. The default value (1800) will be used.

O0127W Invalid Port specified, 1024 < PORT < 65400
This warning is returned when a value less than 1024 or more than 65,400 is specified for the Port parameter in an Octopus section of the nucleus.ini file. The default port (1285) will be used.

O0128W Invalid Port specified for Node: x
This warning is returned when a value less than 1024 or more than 65,400 is specified for the Port parameter in the section for the indicated Node (x) in the nucleus.ini file. The default value (1285) will be used.

O0129W No definition found for Node: x
This warning is returned when the indicated Node (x) is specified by the Nodes parameter in the main Octopus section of the nucleus.ini file, but no corresponding Node section is present. The Node specification will be ignored.

O0130W No DatabasePath specified for Node: x
This warning is returned when Octopus cannot find a DatabasePath specification (location of the database) in the section for the indicated Node x in the nucleus.ini file. The value specified in the main Octopus section will be used.

O0131W Invalid FetchTimeout specified
This warning is returned when a negative number is specified for the FetchTimeout parameter in the nucleus.ini file. The default value (900) will be used.

O0132W Invalid FetchExclusiveTimeout specified
This warning is returned when a negative number is specified for the FetchExclusiveTimeout parameter in the nucleus.ini file. The default value (15) will be used.

O0133W Invalid StartupNbRetry specified: must be greater than or equal to 0
This warning is returned when a negative number is specified for the StartupNbRetry parameter in the nucleus.ini file. The default value (5) will be used.

O0134W Invalid StartupTimeRetry specified: must be more than 60 (sec)
This warning is returned when the StartupTimeRetry parameter in the nucleus.ini file is less than or equal to 60. The default value (3600) will be used.

O0135W Maximum number of Nodes reached: x is discarded
This warning is returned when 17 or more Nodes are defined in the nucleus.ini file of the main Node. A maximum of 16 Nodes are permitted when operating a distributed Octopus system. Any extra Node (x) is simply not used by Octopus.

O0136W The Node defined with the name x does not have a Host parameter,y will be used as Host
This warning is returned when a Node in the distributed Octopus system is missing a Host parameter in section x of the main Node nucleus.ini file. The computer named y will be used for this Node instead.

O0137E Connection not specified
This error is returned when the Octopus section of the nucleus.ini file is missing a Connection parameter. This required parameter specifies the SAND connection that clients will use to connect to the Octopus instance.

O0138W Invalid PrivateUpdateTimeout specified
This warning is returned when a negative number is specified for the PrivateUpdateTimeout parameter in an OCTOPUS section in the nucleus.ini file. The parameter value must be zero or greater. In this situation, the PrivateUpdateTimeout parameter is set to the default (900 seconds).

O0139W Invalid PrivateUpdateExclusiveTimeout specified
This warning is returned when a negative number is specified for the PrivateUpdateExclusiveTimeout parameter in an OCTOPUS section in the nucleus.ini file. The parameter value must be zero or greater. In this situation, the PrivateUpdateExclusiveTimeout parameter is set to the default (60 seconds).

O0143E Invalid NumberOfEngines definition for: x
This error is returned when a value greater than 50 or a negative number is specified for the NumberOfEngines parameter in the nucleus.ini section for the indicated Subclass x.

O0144E Invalid MaxDeltaFileSize definition for: x
This error is returned when a negative number is specified for the MaxDeltaFileSize parameter in the nucleus.ini section for the indicated Subclass x.

O0145E Invalid MaxDeltaFileRatio definition for: x
This error is returned when a negative number is specified for the MaxDeltaFileRatio parameter in the nucleus.ini section for the indicated Subclass x.

O0146W Invalid RescheduleTimeout definition for: x
This warning is returned when a value less than 15 is specified for the RescheduleTimeout parameter in the nucleus.ini section for the indicated Subclass x. The default value (15) will be used.

O0147E Second Definition of an Updatable Subclass: x
This error is returned when two or more Updatable Subclasses are defined in the nucleus.ini file, that is, when the Updatable Class (the last entry in the CLASSES list when operating in Public Update mode) is defined as working on more than one Node. There can be only be one Updatable Subclass.

O0149E No Update SubClass definition found for mode PublicUpdate.
This error is returned when the Updatable Class does not have a corresponding Sublcass. Ensure that the appropriate configuration information is defined in the nucleus.ini file.

O0150W NumberOfEngines defaults to 1 for PublicUpdate Subclass.
This warning is returned when the NumberOfEngines parameter for an Updatable Subclass is set to a value greater than 1 in the Subclass section of the nucleus.ini file. An Updatable Subclass can contain only one OctoEng.

O0151E No SubClass definition found.
This error is returned when the OCTOPUS section Class list contains an entry with no corresponding SUBCLASS section in the nucleus.ini file. Verify that each listed Class has a Subclass definition (containing at least the NumberOfEngines parameter), and that the spelling of the Class/Subclass names match.

O0152W SubClass defined insufficient to enable a Login SubClass.
This warning is returned when the LoginClass=TRUE parameter is set, but an insufficient number of Classes are defined to reserve one for login processing. As a consequence, the Octopus instance operates without a Login Class.

 

Octopus On-Demand Database (ODDB) Messages (O0153 - O0199)

O0153E ODDB Subclass <subclass> must have NUMBEROFENGINES=0
In a complex configuration with more than one Subclass, at least one Subclass must have the ODDBSubClass parameter set to TRUE with a NumberOfEngines value of 0.

O0154E ODDB Runmode requires a non-ODDB Subclass
In a simple configuration, the one defined Subclass must not have the ODDBSubClass parameter enabled. In a complex configuration with more than one Subclass, at least one Subclass must have ODDBSubClass=FALSE (or omitted from the nucleus.ini file).

O0159E Unable to open file database-file in directory path on node node-name
The database file(s) associated with the specified ODDB instance could not be opened by Octopus. Before attempting to start the ODDB instance again, ensure that the database files exist and are not locked by another process, and that Octopus has read access to the files.

O0160E Unable to find an active Subclass to start the ODDB instance-name
There are no ODDB-enabled Subclasses available to start the specified On-Demand Database instance. If this message persists, contact the Octopus administrator for assistance.

O0161E Unable to find section ->Database database-name<- in file path
The specified Octopus On-Demand Database (ODDB) does not have an associated [DATABASE database-name] section in the nucleus.ini file. Ensure the correct spelling of the database name before attempting to start the ODDB instance again.

O0162E ODDB configuration must define an ODDB SubClass or only have one SubClass
In ODDB mode, the current configuration has multiple Subclasses, none of which has ODDBSubClass=TRUE. At least one of the Subclasses must be defined as an ODDB Subclass, or else a simple configuration should be used, where there is only one Subclass with the ODDBSubClass parameter omitted or set to FALSE.

O0170E Unable to find an active SubClass with a MaxCache bigger than the ODDB instance-name defined Cache
This error is returned if the cache required by the ODDB instance exceeds the ODDBMaxCache value defined for all Octopus Agents/Nodes. The [ODDB]Cache setting for the ODDB instance will have to be lowered, and/or an Agent's ODDBMaxCache value increased, in order for the Agent to be able to start the instance.

O0171E ODDBDatabases parameter denies access to the database ->database-name<- in file configuration-file
The database specified by the client is not included in the ODDBDatabases list, and therefore cannot be started as an ODDB instance. To allow ODDB instances of the database to be started, the database must be added to the ODDBDatabases list in the relevant [OCTOPUS] section of the nucleus.ini file.

 

Session Management and Query Execution Messages (O0200 - O0299)

O0200E Unable to reconnect a virtual session
This error is returned when Octopus is unable to restart the OctoEng in the Updatable Class after a failure. Restart the Octopus system to resume operations.

O0201W Recovery of OctoEng: node-name_class-name_number
This warning is returned when Octopus is engaged in restarting an OctoEng (designated as node-name_class-name_number) after a failure.

O0202E Unable to restart OctoEng: node-name_class-name_number. Next attempt in 1h00m00s!
This error is returned when Octopus cannot start an OctoEng (designated as node-name_class-name_number) after a failure. Octopus will automatically attempt to restart the OctoEng at the interval specified by the StartupTimeRetry parameter in the nucleus.ini file (default= 1 hour); the number of restart attempts is specified by the StartupNbRetry parameter (default=5).

O0203E Communication lost between OctoEng: node-name_class-name_number and Octopus, retrying...
This error is returned when the user’s connection to the OctoEng (designated as node-name_class-name_number) is lost during the execution of an SQL command. The OctoEng will be restarted automatically. Resubmit the command.

O0204E Unexpected termination of the UPDATE OctoEng: Octopus is recovering!!!
This error indicates that the OctoEng in the Updatable Class has been stopped. Octopus will restart all OctoEng's in the system to recover operations.

O0204W User attempted connection in excess of maximum

O0205W Communication lost between Octopus and a client logged as user: x, during execution of: y

O0206E SockConnect(OctoEngId = a, Port = b) return c, errno = d:s

 

Octopus Execution Messages (O0300 - O0399)

O0300E Unable to start OctoEng: node-name_class-name_number. Next attempt in 1h00m00s!
This error is returned when Octopus cannot start an OctoEng (designated as node-name_class-name_number) after a failure. Octopus will automatically attempt to restart the OctoEng at the interval specified by the StartupTimeRetry parameter in the nucleus.ini file (default= 1 hour); the number of restart attempts is specified by the StartupNbRetry parameter (default=5).

O0301W Failed to start OctoEng: node-name_class-name_number: Retry attempt n!
This warning is returned when Octopus re-attempts and fails to start an OctoEng (designated as node-name_class-name_number) after a failure. Octopus will automatically attempt to restart the OctoEng at the interval specified by the StartupTimeRetry parameter in the nucleus.ini file (default= 1 hour); the number of restart attempts is specified by the StartupNbRetry parameter (default=5).

O0302W The remote agent on machine x is not responding and will be marked as STOPPED.
This warning is returned when Octopus cannot communicate with an Agent on the remote computer with the host name x. This could be because the Agent has not been started, because of network problems, or because the PORT numbers specified in the nucleus.ini file entry for the Agent and in the corresponding Node section are different.

If different PORT numbers were specified in the Agent and the Node configurations, Octopus must be restarted after the configuration has been corrected. In the other cases, Octopus will check for a connection with the Agent every two minutes; if the Agent has been successfully started and/or network communication re-established, Octopus will automatically start an OctoEng with the Agent and issue warning O0303W (see below).

O0303W The remote agent on machine x is now responding and will be restarted.
This warning is returned when Octopus detects that a previously unresponsive Agent (see Warning O0302W above) is now available for use.

O0304E Unexpected termination of OctoEng node-name_class-name_number with the following output:x
This error is returned when Octopus is unable to start an OctoEng (designated as node-name_class-name_number) for any reason. Any error output (x) from the startup attempt is appended to the error message.

O0305E Cannot open configuration file x
This error is returned when the nucleus.ini file could not be opened for reading. Ensure that the SAND CDBMS SUPPORT path exists and that the nucleus.ini file is located in the SUPPORT path.

O0306E Cannot find NUCLEUS environment variable
This error is returned when the NUCLEUS environment variable is not defined. Ensure that the NUCLEUS environment variable has been defined and contains at least the SUPPORT parameter.

O0307E Cannot find parameter SUPPORT in NUCLEUS environment variable
This error is returned when the NUCLEUS environment variable does not contain a SUPPORT parameter. The SUPPORT parameter, which lists the directory path of the nucleus.ini file, is a required element of the NUCLEUS environment variable.

O0310E Unable to start OctoEng for the ODDB "x" on SubClass y
This error is returned when Octopus attempted and failed to start an OctoEng for the specified On-Demand Database on the specified Subclass. View the message returned by the failed OctoEng for more information about the cause of the error.

O0311E Unexpected termination of the ODDB OctoEng for the ODDB "x" on SubClass y with the following output: z
This error is returned when an ODDB instance terminates abnormally. View the specified output for more information about the cause of the error.

O0312E Connection lost with x while processing a request
This error is returned when Octopus loses its connection to the client host while serving a request. Ensure that the client host is reachable before re-attempting the request.

O0313E Multiple consecutive errors on Node: x, reduced max servers to 0
This error is returned after five (5) successive OctoEng startup errors on the specified Node. The Node will then be "quiesced", preventing further OctoEngs from starting on that Node. To reactivate the Node, simply stop/restart the Octopus Agent on that Node.

O0314E Timeout on OctoEng startup
This error is returned if an OctoEng startup exceeds the time limit set by the StartOctoEngTimeOut parameter. Note that a pattern of startup timeouts on a specific Node can cause that Node to be disabled automatically (see error O0313E above).

 

Octopus Services Messages (O1100 - O1199)

O1100E The Startup of "x" failed with error: y
This error is returned when an Octopus or Octopus Agent process could not be started. See the exception message (y) and error O1101E below for further details.

O1101E Please correct the section x.
This error is returned following error O1100E. Verify the correctness of section x in the nucleus.ini file.

O1104W Removed section x
This warning is returned when the octohup (UNIX) or net pause/continue (Windows) command is executed after an Octopus or Octopus Agent section (x) in the nucleus.ini file was removed while a process started on that section was running. As a result, the process is stopped.

O1106W The process (pid=n) started on section y is not running; it will be restarted
This warning is returned when an Octopus or Octopus Agent process included in the internal Octopus/Agent process list is not currently running. The Octopus/Agent process is simply restarted.

O1108W Found new section x that is not AutoStartup
This warning is returned when the octohup (UNIX) or net pause/continue (Windows) command is executed after an Octopus section (x) was added to the nucleus.ini file. Since the section does not contain an AutoStartup parameter set to TRUE, the Octopus instance must be started manually.

O1109E Unable to find the section x in nucleus.ini
This error is returned when attempting to start an Octopus instance that does not have a corresponding section in the nucleus.ini file. Ensure that the appropriate section (x) exists in the nucleus.ini file before attempting the operation again.

O1111W An instance named x is already running. (pid=y)
This warning is returned when attempting to start an Octopus instance (x) that has already been started.

O1112E There is already a Service/Daemon Octopus running on this machine
This internal error is returned when attempting to start an Octopus service or daemon on a machine where the service/daemon is already running.

 

Internal Errors (O2100 - O3099)

O2100E There has been an api call with a bad parameter api number n
This error is returned when attempting an API call (function n) that specifies an invalid value for one of the following:

O3001E Error pthread_sigmask(SIGCHLD|SIGPIPE|SIGPOLL|SIGINT|SIGTERM|SIGABRT)
This internal error is returned when a pthread_sigmask() function call contains an invalid how argument.

O3002E Octopus Socket: accept error
This internal error is returned when an accept() socket function call fails.

O3003E Could not get string from strftime()
This internal error is returned when a strftime() time string format function call fails.

O3004E Octopus Statistics: WriteIntervalStatsToFile() write error
This internal error is returned when Octopus statistics could not be written to a file.

O3005E Unable to create a Shared memory block named x. Error:y
This internal error is returned when a shared memory block (x) could not be created. See the exception message (y) for further details.

O3006E SharedMemWrite()::MapViewOfFile(HANDLE=x) failed: GetLastError=y
This internal error is returned when a file view could not be mapped into the address space of the calling process. See the exception message (y) for further details.

O3007E There is a problem with the directory /tmp/.Octopus -- please remove it
This internal error is returned when information about the temporary Octopus directory could not be retrieved. This error might occur if there is a file (not a directory) called ".Octopus" in the tmp directory. If this is the case, delete the file before attempting the operation again.

O3008E Error creating file x for Unique identifier
This internal error is returned when a unique lock file for an Octopus or Octopus Agent process could not be created. This might occur if the specified file already exists and is read-only, or is a directory. Less commonly, the error can be produced if there are no more file handles available from the operating system. If the file already exists, remove the file before attempting the operation again. If there are no more file handles available, terminate some other processes before proceeding.

O3009E CreateThread Failed
This internal error is returned if a program thread could not be created. Any of the following conditions can produce this error:

Ensure that the function call is correct and that the appropriate permissions have been granted. If the thread could not be created because of operating system constraints, terminate other processes before attempting the operation again.

O3010E SockOpenSocket: can't open stream socket. socket() returned n
This internal error is returned when a socket could not be created. The socket() function returned n = –1.

O3011E SockBindSocket: setsockopt error
This internal error is returned when the options for a socket could not be set.

O3012E SockBindSocket: can't bind local address with bind()
This internal error is returned when a local address could not be associated with a socket.

O3013E Unable to open the OctopusInfo file (errno:n)
This internal error is returned if the .OctopusInfo.v3 file in the /tmp/.Octopus/ directory could not be opened for writing. The errno value (n) indicates the system error condition. Consult the system include errno.h file for information about this error condition.

O3015E Cannot open file x (errno:y)
This internal error is returned if the nucleus.ini file cannot be read when an Octopus service or daemon starts up. The errno value (y) indicates the system error condition. Consult the system include errno.h file for information about this error condition.

O3016E Error adding a section to the list in ReadIniSection()
This internal error is returned when a new Octopus or Octopus Agent process could not be added to the internal list of processes.

O3017E There is a Policy missing for this user.
             Please see the Microsoft KB article 821546
             The user must be member of Administrator
             or have the <Create global objects> user right.
             In the Start menu->Programs->Administrative Tools->Local Security Policy
             Expand <Local Policies>, and then click <User Rights Assignment>
             Add <Create global objects> to this user or to one group the user
             is member of.(ex:users).

 

SQL Request Messages

Octopus Error: DBA Authorization is required for this operation
This error message is returned if a user authorization other than the user DBA executes the SET UPDATE EXCLUSIVE TO command. Only the user DBA may designate a user authorization to save Octopus instance changes to a Snapshot.

Octopus Error: DBA or exclusive user Authorization is required for this operation
This error message is returned if the SET UPDATE KEEP CHANGE command is issued by a user authorization that has not been granted the ability to save changes to the Octopus instance. Only the authorization specified with the SET UPDATE EXCLUSIVE TO command, or an authorization with DBA privileges, may execute the SET UPDATE KEEP CHANGE command.

Octopus Error: Execution aborted. Lost connection to remote host. Please retry
This error is returned if all of the OctoEng's on a Node have to be restarted before a client's SQL request has been processed. Wait a few minutes for the OctoEng's to restart, and then resubmit the SQL query.

Octopus Error: Execution aborted. Server is in update exclusive mode
This error is returned if the following sequence of events occurs:

  1. A user makes changes to an Octopus instance in transaction A.
  2. Another user executes the SET UPDATE EXCLUSIVE TO command in transaction B.
  3. The first user attempts to COMMIT the changes in transaction A.

In this situation, the COMMIT command is disallowed and all changes from transaction A are discarded.

Octopus Error: Execution aborted. The Server processing this request was terminated. Please retry
This error is returned if an OctoEng has to be restarted before it has finished processing a client's SQL request. Resubmit the SQL query.

Octopus Error: Execution aborted. The Server terminated unexpectedly while processing this request
This error is returned if an OctoEng is shut down before it has finished processing a client's SQL request. Resubmit the SQL query.

Octopus Error: Function not supported
This error is returned if an unsupported API function call is encountered by Octopus. Resubmit the SQL query. If the problem persists, contact a SAND support representative for help.

Octopus Error: Internal Error...
This error is returned if an internal error occurs while executing the SET UPDATE EXCLUSIVE TO or SET UPDATE KEEP CHANGE command. Please report the circumstances of the error to a SAND support representative.

Octopus Error: Keep Change Failed. Check Octopus log for more details
This error is returned when the SET UPDATE KEEP CHANGE command could not successfully execute. Additional information about the cause of the error is written to the Octopus log file (database-name.otc).

Octopus Error: Keep Change Failed. No changes were made
This error is returned when the SET UPDATE KEEP CHANGE command is executed when no changes have been made to the Octopus instance. The SET UPDATE KEEP CHANGE can only be issued when there are actual changes to save to a Snapshot.

Octopus Error: Octopus is running in Read Only mode
This error is returned when a client attempts to execute an SQL command that changes the database. The Octopus instance has been configured to run in Read-Only mode, so the database cannot be altered.

Octopus Error: Private Update Mode, No Commit Work allowed
This error is returned when a client attempts to execute a COMMIT [WORK] command in Private Update mode. When the Octopus instance has been configured to run in Private Update mode, database changes cannot be saved by the client.

Octopus Error: Public update mode is required for this operation
This error is returned if the SET UPDATE EXCLUSIVE TO command is issued when the Octopus instance is not running in Public Update mode. In order to designate a user authorization that can save Octopus instance changes to a Snapshot, the instance must have been started in Public Update mode. To configure an Octopus instance to start in Public Update mode, add the following parameter to the appropriate [OCTOPUS instance-name] in the nucleus.ini file:

OctoRunMode=PUBLICUPDATE


Octopus Error: Rollback Work issued: Another transaction bound this user to another server.

Octopus Error: Rollback Work issued: This user was added in the Non-persistent change list.

Octopus Error: Rollback Work issued: This user was removed from the Non-persistent change list.

Octopus Error: SubClasses currently active cannot start the requested database due to Cache size.(ODDB)
This error is returned if the cache required by the ODDB instance exceeds the ODDBMaxCache value defined for all Octopus Agents/Nodes. The [ODDB]Cache setting for the ODDB instance will have to be lowered, and/or an Agent's ODDBMaxCache value increased, in order for the Agent to be able to start the instance.

Octopus Error: The Query ID used in this request does not exist
This error is returned if an attempt is made to access a query control block that does not exist while processing a client SQL request. Resubmit the SQL query. If the problem persists, contact a SAND support representative for help.

Octopus Error: The Query ID used in this request is already closed
This error is returned if the query control block used for a client SQL request is closed prematurely. Resubmit the SQL query. If the problem persists, contact a SAND support representative for help.

Octopus Error: The specified user does not have dba privileges
This error is returned if the SET UPDATE EXCLUSIVE TO command specifies a user without DBA privileges. Only a user with DBA privileges can be granted the UPDATE EXCLUSIVE ability.

Octopus Error: This SQL function is not supported by Octopus
This error is returned if the client submits an unrecognized SQL command. Consult the SAND CDBMS SQL Reference Guide for a full listing of valid SQL statements.

Octopus Error: Update exclusive is already set
This error is returned if a second SET UPDATE EXCLUSIVE TO command is issued in the same Octopus session. The SET UPDATE EXCLUSIVE TO command (which grants the specified user authorization the ability to execute the SET UPDATE KEEP CHANGE command) can only be issued once.

Octopus Error: Update exclusive mode is not set
This error is returned if a SET UPDATE KEEP CHANGE command is attempted before the SET UPDATE EXCLUSIVE TO command has been executed. In order to save Octopus instance changes to a Snapshot, the SET UPDATE EXCLUSIVE TO command must be used to designate a user authorization that will execute the SET UPDATE KEEP CHANGE command.

Octopus Error: Updates are disabled. The system is in maintenance mode
This error is returned when a user without the appropriate privileges attempts to make changes to the database after the SET UPDATE EXCLUSIVE TO command has been executed. In this situation, only the authorization specified in the SET UPDATE EXCLUSIVE TO command and users with DBA privileges can make changes to the database.

Octopus Warning: An administrator killed your query
This warning is returned if the client's query is cancelled by the database administrator.

Octopus Warning: Password changed. After committing changes, this user's connections will be severed
This warning is returned after a user’s password is changed (by either that user or a user with DBA privileges) and the change committed. All of the user’s connections are closed as the engines are restarted, but the user can reconnect immediately.

 

Other Messages

Cannot find a daemon running on this machine
This message is returned when the octohup command is executed when there is no Octopus daemon running. The octohup command is used to inform the Octopus daemon about changes to the configuration file.

Communication Media Error
This error is returned when a connection cannot be established with the server. Ensure that the server has been started and that the port is correctly specified.

Found octopus daemon (pid=n) ... sending SIGHUP
This message is returned if the octohup command is executed while there is an Octopus daemon running. It simply informs the user that the Octopus daemon process was found and is being sent the appropriate signal.

Insufficient privileges to process. This command requires dba privileges
This error is returned when a user without DBA privileges attempts to execute the OctoRefresh, OctoRollLog, or OctoShutdown commands. Only the user DBA, or users that possess DBA privileges, can execute OctoRefresh, OctoRollLog, or OctoShutdown.

Invalid Connection Name and/or Database Name
This error is returned when the OctoRefresh or OctoRollLog command is supplied an invalid connection name or database name. Execute the command again, and ensure that the connection and database names are correct.

Invalid username or password
This error is returned when the OctoInfo, OctoKill, OctoRefresh, OctoRollLog, or OctoShutdown command is invoked with a user name that does not exist in the specified database, or the password supplied for the user name is incorrect. Ensure that the user name exists in the database, and that the supplied password is correct.

The parameter HOST is not found.
This message is returned when the Host parameter for a connection specified by Octopus, OctoShutdown, OctoRefresh, or OctoRollLog could not be found. Ensure that the appropriate [CONNECTION connection-name] section in the nucleus.ini file contains a valid Host parameter.

The parameter PORT is not found.
This message is returned when the Port parameter for a connection specified by Octopus, OctoShutdown, OctoRefresh, or OctoRollLog could not be found. Ensure that the appropriate [CONNECTION connection-name] section in the nucleus.ini file contains a valid Port parameter.

Trying to find the daemon pid
This message is returned whenever the octohup command is executed. It simply informs the user that octohup is in the process of looking for a running Octopus daemon.

Unable to apply new settings: invalid cache specified
This message is returned when a invalid value is specified for the OctoRefresh Cache parameter. The Cache must be set to an integer value, zero or greater.

Unable to apply new settings: Invalid number of engines specified
This message is returned when an invalid value is specified for the OctoRefresh NumberOfEngines parameter. This value must not be a negative number. Also note that the maximum number of engines in the Octopus system is 50, and the Updatable Subclass can contain only one engine.

Unable to apply new settings: SubClass not found
The Subclass specified for OctoRefresh has not been defined in the nucleus.ini file. Make sure that the Subclass supplied with the OctoRefresh invocation has been spelled correctly.

Unable to process the Shutdown request
This message is returned when the OctoShutdown command could not successfully execute. Attempt the command again. If the error persists, the specified Octopus instance may have to be "killed" (the process ID can be determined through octops).

Unable to Roll the log.
This message is returned when the Roll operation cannot be completed. This happens, for example, if the file (Log, Stat, CStat, or trace) is already open.

Unable to Startup instance-name
This error is returned if an Octopus instance could not be started via the OctoStartup command. There are a number of possible causes for this error. Most commonly, this will occur if the relevant instance section could not be found in the nucleus.ini file. If this is not the problem, you can troubleshoot the error by attempting to start Octopus manually to see what error is returned.