Appendix A SQL/Services Messages ACCDENDAY, Access denied; network access not allowed to ac- count !AZ today Explanation: Network access to the account is not allowed on this day. User Action: Try again later, grant network access for the approproiate days, or grant the SQLSRV$CLIENT identifier to the user's account. - ACCDENPWD, Access denied; Attempt to access account !AZ with- out a password Explanation: This message adds additional information to the general authorization failure message. An attempt was made to access an account without a password when one is required User Action: Use the correct password - ACCDENPWD2, Access denied; Attempt to access account !AZ with- out secondary password Explanation: This message adds additional information to the general authorization failure message. An attempt was made to access an account without a secondary password when one is required User Action: Modify the account to remove thw secondary password, or use a different account for access via Oracle SQL/Services, secondary passwords are not supported. - ACCDENTIM, Access denied; network access not allowed to ac- count !AZ at this time Explanation: Network access to the account is not allowed at this time of the day. User Action: Try again later, grant network access for the appropriate time period, or grant the SQLSRV$CLIENT identi- fier to the user's account. - SQL/Services Messages A-1 ACCEPTERR, Error accepting connection, status Explanation: Could not accept a connection due to a system service failure. On UNIX, the system service is accept. User Action: N/A - ACTSTM, Prepared statement: [] is already active Explanation: sqlsrv_open_cursor: Passed in an active state- ment id. User Action: Pass in a statement id that hasn't been Declared or Opened - ALTER_RESTART, Restart object to have altered settings take effect Explanation: Alter was successful but the changes could not be made dynamically to the running system. User Action: Restart the component that was updated to have the changes take effect. - APIDRVREJCON, API driver rejected connection Explanation: The executor API driver rejected the request to create the new connection. User Action: Review the API-specific error to determine the reason. - APINOTSUP, Client API version is not supported by the server Explanation: Compatibility error between client and server. Possible errors are: 1. V4.1 and V4.2 clients are not sup- ported using the TCP/IP network transport. 2. The sqlsrv_ get_environment(), sqlsrv_set_environment(), and sqlsrv_set_ filter() API services are no longer supported. supported. User Action: 1. Install version V4.1A, V4.2A, or later of the client software to use the TCP/IP network transport. 2. Remove the calls to these deprecated services from the client application. - APPLNAME, Application : Explanation: Node name for internationalization User Action: N/A - A-2 SQL/Services Messages AUTH_FAILURE, Authentication/authorization failure Explanation: (1) The username/password combination supplied to dbs_client_connect() is invalid, or (2) the client is not authorized to access the specified service, or (3) the client may not access the specified service at this time. User Action: Contact your system administrator. - AUTH_REMEXEC, Explicit authentication required for remote executor creation Explanation: An attempt was made to create an executor on a remote node by a client that was implicited authenticated. User Action: Supply a username and password when connecting to the server. - BADCONNECTSTR, Bad connect string: !AZ Explanation: A Bad connect string was passed to the commu- nications subsystem that could not initialize listener or connect. User Action: N/A - BADDBAUTHATTR, Unsupported or unknown database access autho- rization attribute Explanation: (Internal Error) The service database access authorization attribute is either unknown or unsupported by the Oracle SQL/Services executor. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - BADLIS_MBXMSG, Bad DECnet listener mailbox message type: Explanation: An OpenVMS listener mailbox message had a type it did not know about. User Action: N/A - BADMESSAGE, Bad message detected Explanation: A bad message was detected; possibly a cor- rupted message. User Action: N/A - SQL/Services Messages A-3 BADMSGSIZE, Bad message size Explanation: The size of a message was determined to be too large or too small. User Action: N/A - BADMSGSTATUS, Bad message status in response message: Explanation: The status field of a response message had a bad status value. User Action: N/A - BADOFFSET, An invalid block offset was specified Explanation: The specified block offset is invalid, it was not found in the allocated list User Action: N/A - internal error - BADPARAM, Bad parameter passed to routine. Explanation: A bad parameter was passed to an internal Oracle SQL/Services routine. User Action: N/A - BADRDBINSTALL, Required Rdb dispatch entry-point not found Explanation: Oracle SQL/Services implements database access authorization by connect user name for database services using an Oracle Rdb dispatch service named rdb_register_ user() introduced in Oracle Rdb V6.1. During startup, the executor was unable to locate the entry-point in the Oracle Rdb dispatch shareable image, SYS$SHARE:RDBSHR.EXE. User Action: Verify the Oracle Rdb installation and re- install Oracle Rdb V6.1 or later, if necessary. - BADREUSEATTR, Unsupported or unknown service reusability at- tribute Explanation: (Internal Error) The service reusability at- tribute is either unknown or unsupported by the Oracle SQL/Services executor. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - A-4 SQL/Services Messages BADSQLINSTALL, Required Oracle Rdb SQL shared image entry- point not found Explanation: Oracle SQL/Services uses a number of internal Oracle Rdb SQL routines provided in Oracle Rdb V7.0 and later, but is unable to locate one or more of these routines in the Oracle Rdb SQL shared image. User Action: Verify the Oracle Rdb SQL installation and re-install Oracle Rdb SQL V7.0 or later, if necessary. - BADSQLSRVINSTALL, Required Oracle SQL/Services entry-point not found Explanation: Oracle SQL/Services implements database ser- vices using a number of new SQL module language proce- dures. During startup, the executor was unable to lo- cate the entry-points for these procedures in the Oracle SQL/Services SQLSRV$MOD(nn) shared image. In order to use database services with Oracle Rdb V6.1 databases, the Oracle SQL/Services V7.0 installation procedure updates the Oracle SQL/Services SQL module procedure shared image: SYS$SHARE:SQLSRV$MOD61.EXE or SYS$SHARE:SQLSRV$MOD.EXE. If you re-install Oracle Rdb V6.1 ECO01 or earlier after in- stalling Oracle SQL/Services V7.0 or later, the shared image may be overwritten. User Action: Verify the version of the SQLSRV$MOD image you're using. If it's V6.1-0 or V6.1-01, either re-install Oracle SQL/Services V7.0 or later, or install Oracle Rdb V6.1 ECO02 or later. - BADSTATE, Invalid internal state, expected but found Explanation: An invalid state was found on an internal com- ponent User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - BADTXNSTATEFLAG, Bad transaction state flag: Explanation: (Internal Error) SQL returned a bad transaction state flag. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-5 BAD_CONNECT_ATTR, Illegal connect attribute specified. Explanation: Illegal connect attribute specified. User Action: Check connect attribute codes in the connect attribute item list. - BAD_SERVICE_ATTR, Illegal service attribute specified. Explanation: Illegal service attribute specified. User Action: Check service attribute codes in the service attribute item list. - BINDERR, Error on bind call Explanation: An error was encountered on the UNIX bind sys- tem service call. User Action: N/A - BUFOVFL, Output buffer overflow Explanation: An output buffer is too small. User Action: Increase the buffer size. - BUF_SIZE_TOO_BIG, Buffer size requested exceeds client read buffer size Explanation: The buffer size requested exceeds the client read buffer size. User Action: Specify a buffer size less than or equal to the client read buffer size. - CFILE_CREATED, Configuration file has been created success- fully Explanation: The configuration file has been successfully created by the monitor. User Action: None. - CFILE_CREATED_OBS, this message is obsolete and should NOT be used Explanation: This is a place holder for an obsolete message. It's here to prevent other numbers from shifting User Action: Check the Oracle SQL/Services installation and make sure that the correct sqlsrv_messages.exe is in sys$message. The installed version, and the state of the SQLSRV_MESSAGES logical name/env variable should also be checked - A-6 SQL/Services Messages CFILE_OPENED, Configuration file has been opened successfully Explanation: The configuration file has been successfully opened by the monitor. User Action: None. - CFILE_OPENED_OBS, this message is obsolete and should NOT be used Explanation: This is a place holder for an obsolete message. It's here to prevent other numbers from shifting User Action: Check the Oracle SQL/Services installation and make sure that the correct sqlsrv_messages.exe is in sys$message. The installed version, and the state of the SQLSRV_MESSAGES logical name/env variable should also be checked - CHDIR_ERR, Could not change working directory of new process to !AZ Explanation: An error occured attempting to change the work- ing directory of the newly forked process. User Action: Verify that Oracle SQL/Servicws is properly installed and the listed directory exists and has the proper protection. - CLIREQBUFTOOBIG, Specified request buffer size is too large, requested = maximum = Explanation: A client requested request buffer size is too large. This can be because the transport can not support the buffer size or the negotiated buffer size is smaller than the requested buffer size. This error will *NEVER* be returned if the user has specified a DBS_E_CONATT_USED_ REQUEST_BUFSIZE connect attribute to receive the negotiated or transport maximum buffer size. User Action: Use the DBS_E_CONATT_USED_REQUEST_BUFSIZE at- tribute to get the negotiated or transport maximum request buffer size - CLIRESPBUFTOOBIG, Specified response buffer size is too large, requested = maximum = Explanation: A client requested response buffer size is too large. This can be because the transport can not support the buffer size or the negotiated buffer size is smaller than the requested buffer size. This error will *NEVER* be returned if the user has specified a DBS_E_CONATT_USED_ SQL/Services Messages A-7 RESPONSE_BUFSIZE connect attribute to receive the negotiated or transport maximum buffer size. User Action: Use the DBS_E_CONATT_USED_RESPONSE_BUFSIZE at- tribute to get the negotiated or transport maximum response buffer size - CLOSERR, Error on close call Explanation: An error was encountered on the UNIX bind sys- tem service call. User Action: N/A - COMPFAILMUTEX, Server component !AZ failed while holding mutex Explanation: A server process failed while holding a mutex. This will cause the monitor to shut down the server. User Action: N/A - COMPQUIESCED, Component has been quiesced Explanation: A server component has been quiesced. User Action: N/A - CONFIGOPEN, Configuration file already exists Explanation: Attempted to CREATE SERVER for a configuration file that already exists. User Action: Use SET CONFIGURATION FILE to change the name of what configuration file is being created or use DROP SERVER to delete the existing configuration file. - CONFIGTEXT, Text: !AZ Explanation: This is additional information from a previous error. It is used to display the config file line that is in error User Action: N/A - CONNBOUNDCANC, Server cancels bound connect !AZ Explanation: A bound connect was canceled possibly due to an unexpected client disconnect or executor failure. User Action: N/A - CONNECTERR, Error on connect call Explanation: An error was encountered on the connect system service call. User Action: N/A - A-8 SQL/Services Messages CONNECTNAME, Connect : Explanation: Connect name for internationalization User Action: N/A - CONNECTSTATE, Connect state: Explanation: State for internationalization User Action: N/A - CONNSCHEDCANC, Server cancels session reuse scheduled connect !AZ Explanation: User Action: N/A - CONNTIEDCANC, Server cancels tied connect !AZ Explanation: A tied connect was canceled possibly due to an unexpected client disconnect or executor failure. User Action: N/A - CONN_REJECTED, A new connect was rejected Explanation: An attempt to create a new connection failed, so the connection was rejected, for example shared memory was exausted. User Action: The reason why the connect was rejected should be near this message. Fix the cause and the connects will not be rejected. - CRE_SRVR, Write definition of server !AZ into the configura- tion file Explanation: The monitor is ready to write the server defi- nition into the configuration file User Action: None. - CRE_SRVR_OBS, this message is obsolete and should NOT be used Explanation: This is a place holder for an obsolete message. It's here to prevent other numbers from shifting User Action: Check the Oracle SQL/Services installation and make sure that the correct sqlsrv_messages.exe is in sys$message. The installed version, and the state of the SQLSRV_MESSAGES logical name/env variable should also be checked - SQL/Services Messages A-9 DATA_TOO_LONG, SQLDATA value too long for column name index (max. length ) Explanation: The length of the data value supplied for the named column exceeds the maximum permissible value for the column's data type. User Action: Modify the client application to supply a value of the correct length. - DBAUTHSVCNOTSUP, Database access authorization by connect user name not supported using Oracle Rdb V6.0 or earlier Explanation: The version of Oracle Rdb specified for this database service does not support database access authoriza- tion by connect user name. User Action: Modify the service specifying DATABASE AUTHORIZATION SERVICE OWNER or use Oracle Rdb version 6.1 or later to access the database. - DBSRCFILEERR, Error accessing .dbsrc file: "!AZ" Explanation: The .dbsrc file specified in the service defi- nition does not exist. User Action: Correct the definition of the service, the location or protection of the .dbsrc file, then restart the executor processes. - DBS_PROTOCOL_ERR, Internal message protocol error detected by dispatcher Explanation: This is an internal error that could be caused by a non Oracle SQL/Services program connecting to and send- ing data to the server. User Action: Check to ensure that all required protocol elements are specified in the correct format. - DISACCT, Access denied; Attempt to access disabled account !AZ Explanation: This message adds additional information to the general authorization failure message. The specified account is disabled User Action: Enable the account, or use a different account for access - A-10 SQL/Services Messages DISPSTART, Dispatcher process !AZ started (pid ) Explanation: Log event that the a dispatcher process was started. User Action: None. - DISPSTARTFAIL, Dispatcher startup failed for dispatcher Explanation: The startup of a dispatcher failed. User Action: Restart the server. - DLL_GETPROCADDR_FAILED, Obtaining address of a DLL in Windows failed. Error: Explanation: A dll routine was not found in the loaded DLL. User Action: Make sure the DLLs are named correctly. Or Internal error, contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - DLL_LOADLIBRARY_FAILED, Load of a DLL in Windows failed. Error: Explanation: A dll necessary for operation could not be dynamically loaded. User Action: Make sure necessary dlls for communications are in place. such as DNETW.DLL for decnet. - DNETNUMFAIL, Creation of DECnet listener with object number failed Explanation: A DECnet listener could not be created. User Action: N/A - DNETOBJFAIL, Creation of DECnet listener with object name !AZ failed Explanation: A DECnet listener could not be created. User Action: N/A - DUPCONFIGKEY, Duplicate keyword at line # in file !AZ ignored Explanation: A duplicate keyword was encountered while con- verting an old format Oracle SQL/Services config file to an sqlsrv_manage script file. This line of the old config file will be ignored User Action: Use your favorite editor to correct the config file, or the resulting script file. - SQL/Services Messages A-11 ENVALRDYALLOCED, Environment already allocated Explanation: An attempt was made to initialize a client environment more than once. User Action: N/A - EOF_READ, Attempted to read past end of file, read truncated Explanation: An attempt was made to read past the end of file marker in the configuration file. This could occur when running a new monitor with an older version file. This error is handled internally. User Action: N/A - internal error - EOF_WRITE, Attempted to write past end of file Explanation: An attempt was made to write past the end of file marker in the configuration file. User Action: N/A - internal error - ERRATTACHDB, Error attaching to database during executor ini- tialization Explanation: The executor failed to attach to the speci- fied database using the SQL attach statement in the service definition. User Action: Correct the attach statement in the service definition and restart the executor(s). - ERRGETTXNSTATE, Error determining transaction state in transaction-reusable executor !AZ Explanation: (Internal Error) An error occurred attempt- ing to determine whether or not a transaction is currently active. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - ERROR_TEXT, Error text: !AZ Explanation: This is additional information from a previous error. It is used to display the error in a textual format using the system service strerror. User Action: N/A - A-12 SQL/Services Messages ERRPRPTXNSTATE, Error preparing transaction-state SQL proce- dure Explanation: (Internal Error) An error occurred attempting to prepare the transaction-state procedure. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - ERRPRPTXNSTATEACT, Active transaction could not be ended after preparing transaction-state procedure Explanation: (Internal Error) A transaction was active and could not be ended after preparing the transaction-state procedure. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - ERRRELSTM, Error releasing SQL statement:!\!AZ Explanation: (Internal Error) An error occurred releasing a prepared statement. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - ERRRELTXNSTATE, Error releasing prepared transaction-state SQL procedure Explanation: (Internal Error) An error occurred attempting to release the transaction-state procedure. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - ERRSETPREPMODE, Error setting transaction mode for prepares Explanation: (Internal Error) An error was encountered while attempting to set the transaction mode for prepares to un- changed. This is done to avoid transactions being started implicitly by SQL in transaction-reusable services. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-13 ERRSETSCHEMA, Error setting default schema name Explanation: The executor failed to set the default schema name. User Action: Review additional error messages in the error log to determine the reason for the failure. - ERRTRNLNM, Error translating logical name Explanation: (Internal Error) User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - EVENT_LOG, event logged at line in file !AZ Explanation: Text message for internationalization. Used in error logging. User Action: N/A - EXCEPTION_RAISED, Exception raised: !AZ Explanation: An exception was raised. The exception raised may be of interest. User Action: N/A - EXECIDLETIMEOUT, Executor idle time out exceeded Explanation: The server timed out an idle executor. User Action: N/A - EXECINITFAILED, Executor initialization failed; process termi- nating Explanation: The executor process encountered a non- recoverable error during initialization and terminated. User Action: Review the error messages in the log file to determine the reason for the failure. - EXECLEANUP, Executor process error cleaning up transaction and/or database context Explanation: The executor was unable to clean-up the trans- action and/or database attach context when a client released an association or when an association failed. User Action: Review the associated error messages to deter- mine the reason for the failure. - A-14 SQL/Services Messages EXECSTART, Executor process !AZ started (pid ) Explanation: Log event that the a executor process was started. User Action: None. - EXECSTARTEXCEED, Max executor startup failures exceeded for service Explanation: The maximum number of executor startup failures has been exceeded for a target service. User Action: Restart the dispatcher. - EXECSTARTFAIL, Executor startup failed for executor Explanation: The startup of an executor failed. User Action: Restart the executors for the service. Make sure that the executor and service specific attributes are set properly. - EXECSTARTUPERR, Fatal executor process startup error Explanation: An executor process that was created for a new client connection failed to start correctly resulting in the termination of the network connection. User Action: Review the monitor and executor log files to determine the reason for the failure. Correct the problem and restart the service. - EXEC_BOUND, Executor is in a bound state Explanation: Executor is in a bound state. User Action: No need to issue a "bind" request. - EXEC_DISCONNECT, Executor needs to be unbound Explanation: Executor needs to be unbound. User Action: Unbind the executor. - EXEC_FAILURE, The executor process to which the client was connected has failed Explanation: The executor process to which the client was connected has failed resulting in the termination of the network connection. User Action: Review the log file from the executor to deter- mine the reason for the failure. - SQL/Services Messages A-15 EXEC_PROTOCOL_ERR, Executor protocol violated by API driver Explanation: The executor protocol has been violated by the API driver. This error occurs if the API driver issues a request such as receive, send, etc., before "binding" to an executor. This error will also occur if the API driver issues "unbind" twice in a row. User Action: You need to issue requests in the correct or- der. - EXEC_UNBOUND, Executor is in an unbound state Explanation: Executor is in an unbound state. User Action: Need to bind the executor. - EXEC_UNTIE, Executor needs to untie from a connect Explanation: The executor needs to untie from a connect. User Action: None. - EXMODEBADSERVICE, Bad exec-mode service call Explanation: (Internal error) User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - EXPACCT, Access denied; Attempt to access expired account !AZ Explanation: This message adds additional information to the general authorization failure message. The specified account has expired User Action: Enable the account, or use a different account for access - EXTRAEXECUTE, Execute command at line # in file !AZ must be manually placed in a SQL init file Explanation: The old version config file allowed multiple execute keywords and they were all executed at executor startup time. We now allow only 1 attach command. User Action: If the SQL commands are still necessary, they should be put into a SQL init file and the service modified to execute the file at executor startup time - A-16 SQL/Services Messages FATALEXECERR, Fatal executor process error Explanation: The executor process to which the client was connected encountered a fatal error resulting in the termi- nation of the network connection. User Action: Review the monitor and executor log files to determine the reason for the failure. - FCNTLERR, Error on fcntl call Explanation: An error was encountered on the UNIX fcntl system service call. User Action: N/A - FLOBCREATERR, Error on system service call Explanation: An error was encountered during failure object creation. User Action: N/A - FLOBDISPUNAVAIL, Dispatcher process failed Explanation: A dispatcher component is not available. User Action: Restart the dispatcher. - FLOBDROPERR, Error on system service call Explanation: An error was encountered during failure object removal. User Action: N/A - FLOBEXECUNAVAIL, Executor process terminated Explanation: An executor component is not available. User Action: Restart the executor. - FLOBMONUNAVAIL, Monitor component is unavailable Explanation: The monitor component is not available. User Action: Restart the monitor. - FLOBREGERR, Error on system service call Explanation: An error was encountered during registration for a failure object. User Action: N/A - SQL/Services Messages A-17 FORKERR, Error on fork call Explanation: An error was encountered on the UNIX fork sys- tem service call, or the VMS $CREPRC system call. See the trace log for details. User Action: N/A - GETACCINF, Oracle SQL/Services authorization failed Explanation: (1) The username/password combination sup- plied to sqlsrv_associate() is invalid, or (2) the client is not authorized to access the specified service, or (3) the client may not access the specified service at this time. User Action: Contact your system administrator. - HOMELESS, The requested HOME directory is not defined Explanation: An attempt was made to expand "~/...", "~user/...", or "dir/..." to a full file name, however: - the user does not have an account or has no home directory defined, or - the process UID does not have an account or has no home directory defined, or - the current working directory could not be determined. User Action: Correct the problem and retry the operation. - HOMELESSNOCWD, Error getting current working directory Explanation: An attempt was made to expand "dir/..." to a full file name, but the current working directory could not be determined. User Action: Correct the problem and retry the operation. - HOMELESSNOUIDDIR, No such UID or no home directory for UID: Explanation: An attempt was made to expand "~/..." to a UNIX home directory, but the process UID does not have an account or does not have a home directory. User Action: Correct the problem and retry the operation. - HOMELESSNOUSERDIR, No such user or no home directory for user: !AZ Explanation: An attempt was made to expand "~user/..." to a UNIX home directory, but the user does not have an account or does not have a home directory. User Action: Correct the file name and retry the operation. - A-18 SQL/Services Messages IDENTNOTSUPP, Identifiers are not supported on this server platform Explanation: An attempt was made to grant access to a ser- vice via an identifier but it is not supported on the plat- form that the server is running on. User Action: None. - IDLEUSERTIMEOUT, Server connect !AZ idle user timed out Explanation: The user of this connect was idle longer than the maximum allowed for their service (or dispatcher). User Action: N/A - IMAGEFILE, Successfully loaded shareable image : !AZ Explanation: Log the name of the shareable image about to loaded. User Action: N/A - INCOMPATVERS, Incompatible software version requested, ex- pected V., received V." Explanation: The installed version string passed to the mon- itor process at startup is not compatible with the version of the monitor software User Action: Check the installation, make sure that multi- version images have not been renamed/copied to the STANDARD equivilent, or vice versa - INPROGRESS, Could not perform operation because one is already in progress Explanation: An operation was attempted when one was already started. User Action: N/A - INSUFMEM, Insufficient memory to create process Explanation: Insufficient memory is available to create a new process. User Action: Add more memory. - INTERNAL, An internal error was encountered Explanation: An internal error occurred. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-19 INTERNAL_INFO, Internal error info: Explanation: An internal software error has been detected. This message supplies information to aid support personnel in isolating the cause of the error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - INTERR, Internal error in Oracle SQL/Services !AZ version !AZ at line in module !AZ Explanation: (Internal Error) Internal error identified by error message text and arguments. User Action: Contact your Oracle support representative for assistance. Please retain copies of any component log and dump files generated coincident to the error. - INVCONFIGREC, Invalid record at line # in file !AZ Explanation: An invalid record was encountered in the old Oracle SQL/Services config file being processed This line of the old config file will be ignored User Action: Use your favorite editor to correct the syntax error - INVCRSNAM, Invalid cursor name: !AZ Explanation: sqlsrv_fetch: received an invalid cursor name parameter. User Action: Pass a cursor name used in a successful sqlsrv_ open_cursor call - INVENCRSTR, Access denied; Unable to decrypt string Explanation: This message adds additional information to the general authorization failure message. User Action: Internal error, contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - INVLCLACCT, Access denied; Account !AZ has not been granted access to service !AZ Explanation: This message adds additional information to the general authorization failure message. The user does not have access to the service User Action: Grant access to the user, or use a different account - A-20 SQL/Services Messages INVPRTPRCHND, Invalid protected process descriptor handle Explanation: An invalid protected process descriptor handle was detected. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - INVPRXREC, Invalid Proxy record at line # in file !AZ Explanation: An invalid record was encountered in the proxy file User Action: Use your favorite editor to correct the syntax error - INVPWD, Access denied; Attempt to access account !AZ with an invalid password Explanation: This message adds additional information to the general authorization failure message. An attempt was made to access an account with the wrong password User Action: Use the correct password - INVRMTACCT, Access denied; Attempt to remotely access service !AZ from node: !AZ, user: !AZ Explanation: This message adds additional information to the general authorization failure message. The user does not have access to the service User Action: Grant access to the user, or use a different account - INVSQLDA, Parse error, invalid SQLDA structure Explanation: An invalid SQLDA structure was passed to the API. User Action: Pass a valid SQLDA structure to the API. - INVSQLLEN, Invalid SQLLEN value for column name index (max. valid SQLLEN ) Explanation: The SQLLEN field in the SQLDA or SQLDA2 has been set to 0 or to a value greater than the size of the column. User Action: Set the SQLLEN to a valid value. - SQL/Services Messages A-21 INVSTMID, Invalid statement id: Explanation: Invalid statement id passed into sqlsrv_open_ cursor or sqlsrv_execute User Action: Pass a statement id that has been returned by sqlsrv_prepare - INVSVCDEF, Invalid definition for service !AZ in file !AZ Explanation: The service definition for the named service in the old config file being converted contains an invalid combination of keywords 1) You must have either USER or STARTUP (or both) 2) If USER is present we must have an EXECUTE (attach) statement User Action: Use your favorite editor to correct the config file or the resulting script file. - INVTRANSPORT, Invalid Transport Explanation: Invalid transport specified. User Action: Select a different transport. - INVVERSION, Unsupported or invalid version string Explanation: The version string typed on the command line is invalid User Action: Ensure that the version string on the command line is correct - IOALRDYPOSTED, An I/O was already posted on this component Explanation: Only one I/O post is allowed on the message and communications subsystems. An attempt to exceed this limit has been made. User Action: N/A - IOCTLERR, Error on ioctl call Explanation: An error was encountered on the UNIX ioctl system service call. User Action: N/A - IONOTPOSTED, No I/O was previously posted Explanation: An attempt was made to complete an I/O that was not posted. User Action: N/A - A-22 SQL/Services Messages KILLERR, Error on kill call Explanation: An error was encountered on a UNIX kill system service call. User Action: N/A - LISTENERR, Error on listen call Explanation: An error was encountered on the UNIX listen system service call. User Action: N/A - LOGFILE, Log file : Explanation: File specification of process log file for internationalization. User Action: N/A - LWCCONNERR, Error creating a SQL connect !AZ Explanation: (Internal Error) An error occurred attempting to create a SQL connect for a new client. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - LWCCONNERRUSER, Error creating a SQL connect for username: !AZ !AZ Explanation: An error occurred attempting to create a SQL connect for a new client. User Action: This error is logged if a client application attempts to connect to a database service but the username does not have access to the database. If this error occurs for any other reason, contact your Oracle support represen- tative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - LWCDISCERR, Error disconnecting a SQL connect !AZ Explanation: (Internal Error) An error occurred attempting to disconnect a SQL connect. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-23 LWCSETERR, Error setting a SQL connect !AZ Explanation: (Internal Error) An error occurred attempting to establish an existing SQL connect as the current connect. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - MEMLOCKED, An attempt was made to deallocate locked memory Explanation: Memory that is locked cannot be deallocated until it is unlocked. User Action: N/A - MEMLOCKFAIL, An attempt to lock memory failed Explanation: Internal error. Request to lock memory failed. User Action: N/A - MEMNOTLOCKED, An attempt was made to unlock memory that was not locked Explanation: Memory that is not locked cannot be unlocked. User Action: N/A - MISSINGPARAM, A required parameter was missing Explanation: A required parameter was not supplied to an internal Oracle SQL/Services routine. User Action: N/A - MONALRDYSTARTED, Monitor for server is already active Explanation: The user has already started a monitor for the target server on this node. User Action: N/A - MONSTART, Monitor process !AZ started (pid ) Explanation: Log event that the a monitor process was started. User Action: None. - MSGOVERRUN, An attempt was made to put more data into a mes- sage than it can hold Explanation: The amount of data supplied for a single mes- sage was more than the message buffer could hold. User Action: Increase the message buffer size. - A-24 SQL/Services Messages NETACCDIS, Access denied; network access to account !AZ is disabled Explanation: Network access using this account is disabled. User Action: Grant network access for the appropriate time periods or grant the SQLSRV$CLIENT identifier to the user's account. - NODELOOKUPERR, Error looking for node name: !AZ Explanation: An error was encountered on the UNIX bind sys- tem service call. User Action: N/A - NODENAME, Node : Explanation: Node name message for internationalization User Action: N/A - NOIMAGEFILE, Error loading shared image: !AZ Explanation: Unable to load the specified shared image. User Action: Make sure the shared image is named correctly, is located in the appropriate disk and directory with the correct protection, and is installed on VMS if necessary. - NOLISCREATED, No listeners could be created Explanation: Creation of all listeners has failed. User Action: N/A - NOMEM, No heap memory Explanation: Heap memory is exausted. User Action: N/A - NOPRIV, No privilege for specified operation Explanation: The current process does not have the privilege for the specified operation. User Action: N/A - SQL/Services Messages A-25 NOPRTPRCDSC, No free protected process descriptors available Explanation: The monitor was unable to allocate a protected process descriptor. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - NORMAL, Normal successful completion Explanation: Normal Successful completion User Action: N/A - NOSQLINIT, No Oracle Rdb SQL version initialization procedure could be found Explanation: None of the Oracle RDB or Oracle Rdb SQL ini- tialization procedures could be found to set the desired Oracle Rdb SQL version. User Action: Check for valid Oracle RDB &/or Oracle Rdb SQL installation - NOSQSMSG, Oracle SQL/Services MSG layer not built into this dispatcher Explanation: The dispatcher image is not built to support Oracle SQL/Services. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - NOSUCHCLIENT, No clients found Explanation: No clients exist for the service you want to show. User Action: None. - NOSUCHEXEC, Executor not found Explanation: The requested executor was not found User Action: None. - A-26 SQL/Services Messages NOTIMERR, internal error: current time is not available Explanation: The system time was not available for use in determining if an account was currently allowed to access the system. User Action: Internal error, contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - NOTSERVERPROC, The current process is not part of the server environment Explanation: An attempt was made by a process outside of the server environment to access resources within the server environment. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - NOTSPECIFIED, Optional attribute was not specified Explanation: Internal status code User Action: N/A - NO_EXEC, No executor processes are available at this time Explanation: No executor processes are available to process your requests at this time. User Action: Please try again later. - NO_MCHRHT, Access denied; Account !AZ does not have rights access to class Explanation: The user does not have the correct Rights list entry to access the database class. User Action: Use authorize to grant the resource to the requesting user - NO_MEM, Server memory allocation failed Explanation: (Internal Error) Server is out of memory User Action: Contact your Oracle support representative for assistance. Please retain the executor's account parameters and copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-27 NO_REQUEST, Request buffer was not available Explanation: Request buffer was not available. User Action: Try "receive" again. - NO_SERVICE, The requested service is not configured Explanation: The requested service is not configured. User Action: Check the service name attribute supplied to dbs_client_connect(). - OFFLINEONLY, Command not valid when connected to a server Explanation: The attempted command can only be issued when not connected to a server. User Action: Disconnect all server connections and reissue the command. - OUTRANGE, An internal array index value is outside the valid range Explanation: Internal error. Array index is invalid. User Action: N/A - PENDING, Operation is pending completion Explanation: Although notified that a posted operation was completed, it was determined that the operation could not be completed. A future notification will be sent when the operation may complete. User Action: N/A - PROCLIM, Process limit for user excceded Explanation: The fork() or $CREPRC failed due to an insuffi- cient process limit. User Action: Increase the process limit for the user or stop some running processes. - PROCSHUT, Process !AZ shutting down Explanation: The newly forked process is shutting down due to an unrecoverable error This is additional information from a previous error. User Action: N/A - PROCSTART, Process !AZ started (pid ) Explanation: Log event that the a process was started. User Action: None. - A-28 SQL/Services Messages PROTOCOL, Protocol not understood by server Explanation: The protocol version requested by a client is not supported by the server. This client must fall back to a previous protocol version or terminate the network connec- tiuon if the range of returned protocols is not supported by the client. User Action: N/A - PWDEXPACCT, Access denied; Attempt to access account !AZ with an expired password Explanation: This message adds additional information to the general authorization failure message. An attempt was made to access an account with an expired password User Action: Reset the password for the account - PWDEXPIRED, Access denied; password has expired Explanation: An attempt was made to access an account with an expired password User Action: Reset the password for the account - READERR, Error on read Explanation: An error was encountered while attempting a read operation. User Action: N/A - READ_SRVR, Read definition of server !AZ from the configura- tion file Explanation: The monitor is ready to read the server defini- tion from the configuration file User Action: None. - READ_SRVR_OBS, this message is obsolete and should NOT be used Explanation: This is a place holder for an obsolete message. It's here to prevent other numbers from shifting User Action: Check the Oracle SQL/Services installation and make sure that the correct sqlsrv_messages.exe is in sys$message. The installed version, and the state of the SQLSRV_MESSAGES logical name/env variable should also be checked - SQL/Services Messages A-29 RECONNECT, Client should reconnect to the specified network object Explanation: The monitor has determined that the dialog must be redirected to a different network object. User Action: None: client programs should never receive this error status. - REGUSERFAILED, The call to rdb_register_user() failed Explanation: (Internal Error) The call to rdb_register_ user() to configure Oracle Rdb in the executor process failed. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - RMSERROR, Error on RMS call for file !AZ Explanation: An error was encountered by an OpenVMS RMS service call. See the trace log for details. User Action: N/A - RMU_FUNCNOTEXIST, Invalid Oracle RMU function code Explanation: The Oracle RMU function code being referenced does not exist. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SELECTERR, Error on select call Explanation: An error was detected on the UNIX select call. User Action: N/A - SERVER_INTERR, Internal error in server component; see server log files for details Explanation: (Internal Error) An internal error occured in an Oracle SQL/Services server component, please review server component log files for details. User Action: Contact your Oracle support representative for assistance. Please retain copies of any component log and dump files generated coincident to the error. - SERVICENAME, Service : Explanation: Node name for internationalization User Action: N/A - A-30 SQL/Services Messages SETENV_ERR, Could not create environment variable !AZ in cre- ated process Explanation: An error occured attempting to create an envir- inment variable in the newly forked process. User Action: N/A - SETSID_ERR, Create process - setsid failed Explanation: Internal software indicator status. If seen as a user error condition, it indicates an internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SETSOCKOPTERR, Error on setsockopt call Explanation: An error was encountered on the UNIX setsockopt system service call. User Action: N/A - SHMEMINITFAIL, Shared memory initialization failed Explanation: This message appears in the error log. When an Oracle SQL/Services component starts, it creates and/or maps the server shared memory. If there are errors with the shared memory initialization, this message will be writ- ten to the error log and the process will exit. Oracle SQL/Services components cannot operate without properly mapped shared memory. User Action: Check the reason string displayed after this message. Typically, the failure is environmental, such as: insufficient space on the disk where the shared memory back- ing file is placed; no privilege to create or write to the backing file; an invalid or nonexistent path to the file; and so forth. - SHRIMGLOADERR, Error loading shared image: !AZ Explanation: Unable to load the specified shared image. User Action: Make sure the shared image is named correctly, is located in the appropriate disk and directory with the correct protection, and is installed on VMS if necessary. - SQL/Services Messages A-31 SHRIMGLOOKUPERR, Error looking up symbol: !AZ in shared image: !AZ Explanation: Unable to load the specified shared image or locate the required symbol within the shared image. User Action: Make sure the shared image is named correctly, is located in the appropriate disk and directory with the correct protection, and is installed on VMS if necessary. - SIGACTIONERR, Error on sigaction call Explanation: An error was encountered on the UNIX sigaction call. User Action: N/A - SKIPGENERIC, GENERIC service is created during installation, the definition in file !AZ is being ignored Explanation: The GENERIC service definition is created by the installation so the convert utility ignores it when it encounters it in the old file. User Action: none - SM_BADCLIPEREXEC, Invalid CLIENTS_PER_EXECUTOR setting for service Explanation: The number of clients per executor cannot be greater than one for session reusable services. User Action: Either make your service transaction reusable, or set the number of clients per executor to 1. One is the default number of clients per executor. - SM_BADSMPROT, System management protocol must be specified as NATIVE Explanation: You specified PROTOCOL SQLSRV on a CONNECT command in the system management application. That protocol is not supported for performing system management. User Action: Omit the PROTOCOL attribute on system manage- ment CONNECT commands. - SM_CHILDREN, Cannot drop a parent with children Explanation: You either attempted to drop a server, but the server had dispatchers and/or executors defined or you A-32 SQL/Services Messages attempted to drop a service, but executors were defined for that service at some server. User Action: You must drop child objects (dispatchers and executors for services) before you drop parent objects (servers and services). - SM_CONNATTEMPT, Attempting connect to monitor Explanation: This message will be found in the sqs_ manage.log file. The system management application will try to connect to the named monitor. This message is to anno- tate the error log so connection failures can be more easily understood and diagnosed. User Action: If all retries fail, look at the sqs_manage.log, sqs_mon_out.log and sqs_mon_err.log files to understand the reason why the monitor failed or did not start successfully. - SM_CONNFAIL, Connect to server failed Explanation: The system management application failed to connect to the target server. User Action: Check subsequent errors to determine the cause. If the connect was to a remote node, ensure that the monitor is running at that node. - SM_CONNOEXIST, Connect "!AZ" does not exist Explanation: You tried to set to a connection or disconnect a connection using the name of a connection that does not exist. User Action: Perform a SHOW CONNECTIONS command to display the active connections. - SM_CONNRETRY, Retrying connect to monitor ( of retries) Explanation: This message will be found in the sqs_ manage.log file. The system management application will try to connect to the monitor several times before giving up. This is because if the monitor process has just been started, it may take awhile to become available. A previ- ous error log message will indicate why the previous connect attempt failed. This message is to annotate the error log so connection failures can be more easily understood and diagnosed. User Action: If all retries fail, look at the sqs_manage.log, sqs_mon_out.log and sqs_mon_err.log files to understand the SQL/Services Messages A-33 reason why the monitor failed or did not start successfully. - SM_CONST_GTRZERO, Value of attribute must be greater than zero Explanation: A value less than or equal to zero was speci- fied for an attribute in a CREATE or ALTER command. User Action: Use an integer value greater than zero for the attribute. - SM_CONST_POSITIVE, Negative number not allowed for attribute Explanation: A negative number was specified for an at- tribute in a CREATE or ALTER command. User Action: Use a valid, positive integer for the at- tribute. - SM_CREATE_DBSMGR, Error creating file !AZ, could not set file owner Explanation: The system management application failed to set the owner of a newly created config file to dbsmgr. Either the account does not exist or the attempt to create the file was issued from from other than the root account or dbsmgr User Action: Ensure that the dbsmgr account exists Ensure that the create is issued from root or dbsmgr - SM_CREATE_ERR, Error creating file !AZ Explanation: The system management application failed to create and open the listed file. User Action: Ensure that you have the correct privileges to access the file. Ensure that you have sufficient open file resources to access the file. - SM_DEFDNETOBJ_EXC, an attempt was made to specify the same DECnet object more than once Explanation: The same DECnet object name was specified (or defaulted) more than once. This resulted in the default DECnet object name being used more than once. A default DECnet object name can only be used once. User Action: Reissue the command and make the DECnet object is unique on all ports - A-34 SQL/Services Messages SM_DEFSNETLIS_EXC, an attempt was made to specify the same Oracle SQL*NET listener more than once Explanation: The same Oracle SQL*NET listener name was spec- ified (or defaulted) more than once. This resulted in the default DECnet object name being used more than once. A default DECnet object name can only be used once. User Action: Reissue the command and make sue the Oracle SQL*NET listener name is unique on all ports - SM_DEFSPXPID_EXC, an attempt was made to specify the same IPX/SPX port id more than once Explanation: The same IPX/SPX port id value was specified (or defaulted) more than once. This resulted in the default port id value being used more than once. A default port id value can only be used once. User Action: Reissue the command and make the IPX/SPX port id is unique on all ports - SM_DEFSRVREXISTS, Server is already defined in the configuration database Explanation: The configuration data base already contains a server definition. User Action: Alte the existing server, or create a new database with a new server definition - SM_DEFTCPPID_EXC, an attempt was made to specify the same TCP/IP port id more than once Explanation: The TCP/IP port id value was specified (or defaulted) defaulted more than once. This resulted in the default port id value being used more than once. A default port id value can only be used once. User Action: Reissue the command and make the TCP/IP port id is unique on all ports - SM_DISCONNFAIL, Disconnect from server failed Explanation: The system management application failed to disconnect from the target server. User Action: Check subsequent errors to determine the cause. - SQL/Services Messages A-35 SM_DISPALRDYCRE, Dispatcher has already been created Explanation: You tried to create a dispatcher that already exists. User Action: None. - SM_DISPALRDYRUN, Dispatcher has already been started Explanation: You attempted to start a dispatcher that is already running. User Action: None. - SM_DISPQUIESCING, Dispatcher has begun quiescing Explanation: A dispatcher shutdown was requested via sys- tem management. The first step of the shutdown is to place the dispatcher in the QUIESCING state and let it cleanly run down it connects. This message is written to the error log identifying the dispatcher that is being shut down. A subsequent log message indicates whether the shutdown was successful. User Action: N/A - SM_DISPSHUT, Shutting down dispatcher Explanation: Server shutdown was requested from the system management application. This message is written to the error log identifying one of the server components that is being shut down. A subsequent log message indicates whether the shutdown was successful. User Action: N/A - SM_DISPSTARTFAIL, Dispatcher could not be started Explanation: The dispatcher could not be started. User Action: Check the error log to determine why this oper- ation failed. - SM_DNETOBJNUMEXC, DECnet object number exceeds maximum limit Explanation: The DECnet object number has exceeded the maxi- mum limit of 255. User Action: Specify a DECnet object number less than 255. - SM_DROPNOOBJ, Drop object does not exist Explanation: You attempted to drop an object that does not exist. User Action: Use the SHOW commands to see what objects are defined in the configuration. - A-36 SQL/Services Messages SM_DROPOBJACTIVE, Drop object is running, so cannot be dropped Explanation: You attempted to drop an object that is active. You cannot drop objects that are running. User Action: Use the management application to shutdown the server that has the running components (SHUTDOWN SERVER command). Restart the monitor (START MONITOR command) and reconnect to the server (CONNECT command). You can now drop the object. - SM_DROPOBJCHILD, Drop object has children and cannot be dropped Explanation: You cannot drop objects that have children. If a server has a dispatcher or executors for a service de- fined, then that server has children. If there are executors for a service defined, then the service has children. User Action: You must drop all child objects before you can drop the parent. - SM_DUPCONNAME, Connect "!AZ" already exists Explanation: You tried to connect using the name of a con- nection that is already in use. User Action: Perform a SHOW CONNECTIONS command to display the active connections. Select a name that is not in use. Provide an AS argument on the CONNECT command to give that name to the new connection. - SM_DUPSRVRNAME, Server on this node already exists Explanation: A server with the given name is defined in the configuration database. So the user cannot rename the server to that name. User Action: Rename the server to a different unique name. - SM_EXECSALRDYCRE, Executors have already been created for service Explanation: You tried to create executors that already exist. User Action: None. - SQL/Services Messages A-37 SM_EXECSALRDYRUN, Executors are already started for service Explanation: Executors for the given service are already active. You cannot start executors when they are already running. User Action: If you need to change the number of active ex- ecutors, you must shutdown the server and recreate the ser- vice and executors with a different value for MIN_EXECUTORS. - SM_EXECSHUT, Shutting down executor Explanation: Server shutdown was requested from the system management application. This message is written to the error log identifying one of the server components that is being shut down. A subsequent log message indicates whether the shutdown was successful. User Action: N/A - SM_EXECSTARTFAIL, All executors for service could not be started Explanation: All executors for the given service could not be started. User Action: Check the error log to determine why this oper- ation failed. - SM_EXTEND_ERR, Error writing file !AZ Explanation: The system management application failed trying to extend the listed output file. User Action: Check the file access, disk space, and file system integrity. - SM_FCLOSE_ERR, Error closing file !AZ Explanation: The system management application failed to close the listed output file or the monitor failed to close the configuration file. User Action: Ensure that sufficient disk space exists to write the file. Ensure that you have sufficient privileges to write the file. Check the documentation for the DEC OSF/1 fclose function for other conditions under which you might get this failure. - A-38 SQL/Services Messages SM_FETCHACTIVE, Fetch already active Explanation: Internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SM_FETCHNOMORE, No more tuples to fetch Explanation: Internal software indicator status. If seen as a user error condition, it indicates an internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SM_FOPEN_ERR, Error opening file !AZ Explanation: The system management application failed to open the listed input file. User Action: Ensure that the file exists and that you have correct privileges to access it. Ensure that you have suffi- cient open file resources to access the file. - SM_FREAD_ERR, Error reading file !AZ Explanation: The system management application failed trying to read from the listed input file. User Action: Check the file access, disk space, and file system integrity. - SM_FVERSION_ERR, Unsupported configuration file version () Explanation: The config file version found in the newly opened file is not supported. User Action: Ensure that the correct configuration file is being used - SM_FWRITE_ERR, Error writing file !AZ Explanation: The system management application failed trying to write to the listed output file. User Action: Check the file access, disk space, and file system integrity. - SM_HELP_ERROR, Error in help facility; error number Explanation: An error has been detected accessing help. User Action: Check accessibility of the help file. - SQL/Services Messages A-39 SM_INPUTOVF, Input line exceeds 1024 octets Explanation: An input line to the system management appli- cation, either on the command line or in an input file, is longer than 1024 octets. User Action: Spaces and new lines are not significant to input parsing. Split your input line across multiple lines. - SM_INVOKE_ERR, Usage: sqlsrv_manage [-input infil] [-output outfil] [-startup startfil] Explanation: Invalid parameters were specified when invoking the system management application. User Action: Check the documentation for the complete syntax for invoking the system management application. Use each parameter only once. Parameter names can be abbreviated to a single character. For example, -input can be abbreviated -i. - SM_INVSQLVERS, Invalid Oracle Rdb SQL Version for Oracle RMU service Explanation: The Oracle Rdb SQL Version attribute for an Oracle RMU service does not match the current server version User Action: Alter the service definition to make sure that the Oracle Rdb SQL Version attribute is the same as the current server version - SM_INV_LCKMODE, File lock is in invalid mode for request Explanation: A call was made to one of the config file han- dling routines without the proper file lock. User Action: N/A - SM_KILLFAIL, Kill failed: pid = Explanation: This message is found in the error log file. During processing of the SHUTDOWN SERVER command, the moni- tor kills the other processes comprising the server. Errors during the kill process are logged, but are not fatal to the monitor. The value of pid is the process targetted to be killed. A pid of -1 indicates a process that did not start successfully or has already been killed. A prior log entry should tell you which server component failed. User Action: None. - A-40 SQL/Services Messages SM_KILLSUCCESS, Kill succeeded: pid = Explanation: This message is found in the error log file. During processing of the SHUTDOWN SERVER command, the mon- itor kills the other processes comprising the server. This message indicates the successful deletion of one of the server processes. The value of pid is the process that was killed. User Action: None. - SM_LOCK_ERR, Error on lock request, status: Explanation: An error was encountered while attempting to obtain the configuration file lock. User Action: N/A - SM_MAXEXECLSSMIN, Maximum number of executors less than mini- mum Explanation: The maximum number of executors specified is less than the minimum number of executors. User Action: Create executors again and specify a value for MAX_EXECUTORS that is greater than the value for MIN_ EXECUTORS. - SM_MAXEXECSTARTED, Maximum number of executors already started Explanation: The maximum number of executors for the given service have already been started. So no more executors for this service can be started. User Action: If you need to increase the value of MAX_ EXECUTORS, you must shutdown the server and recreate the service and executors with a different number for MAX_ EXECUTORS. - SM_MAXPORTSEXC, Maximium number of ports allowed has been exceeded Explanation: The maximum number of ports allowed has been exceeded. User Action: Refer to the documentation to determine the maximum number of ports allowed. Issue a system management command with fewer port numbers. - SQL/Services Messages A-41 SM_MINEXECNEQMAX, Min executors must equal max for transaction reusable service Explanation: For transaction reusable executors, the value for the minimum number of executors must equal the value for the maximum number of executors. User Action: Make the value of the MIN_EXECUTORS attribute equal to the value of the MAX_EXECUTORS attribute. - SM_MONCREFAIL, Monitor creation failed Explanation: The system management application attempted to create a monitor and failed. User Action: Check subsequent errors to determine the cause. You must have superuser privileges or run from the root account to create a monitor. - SM_MONSHUT, Shutting down monitor Explanation: Server shutdown was requested from the system management application. This message should be the last to be written to the error log. User Action: N/A - SM_NODECDB, The dbsmgr account does not exist on this system Explanation: The system management application tries to run the monitor under the dbsmgr account. If that account does not exist, the monitor creation fails. User Action: Check that Oracle SQL/Services is properly installed on your system. - SM_NOEXECSCRE, Executors for service have not been created Explanation: Executors for the given service have not been created. User Action: Create executors for the given service with attribute MIN_EXECUTORS greater than zero before attempting to start or alter them. - SM_NOFETCHACTIVE, No fetch active Explanation: Internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - A-42 SQL/Services Messages SM_NOHELP, Help is unavailable Explanation: An error was detected initializing help. This is not fatal to the management application. It prints an informational message and continues. If help is requested later on in the management session, this is the message you receive. User Action: Check accessibility of the help file. Rerun the management application. - SM_NOIMPERSONATE, IMPERSONATE ON is not supported for database versions prior to 6.1 Explanation: IMPERSONATE ON was specified, but the specified database version does not support impersonation. User Action: Either use a database of Version 6.1 or greater, or do not use impersonation for this service. - SM_NOOPEN, No output file is open to be closed. Explanation: An attempt was made to close an output file when no output file was open. User Action: Open an output file with the OPEN command. When you have captured the terminal session output you wish, close the file with a CLOSE command. - SM_NOPARENT, No parent for target of create Explanation: An attempt was made to create an object, such as a dispatcher or executor, or to grant a privilege, when the server or service did not exist. User Action: You can only create objects in the correct context. Create servers and services first. Then create their contents. - SM_NOSCANACTIVE, No scan active Explanation: Internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SM_NOSUCHDISP, Dispatcher does not exist Explanation: The dispatcher with the given name has not yet been created. User Action: Create the particular dispatcher. - SQL/Services Messages A-43 SM_NOSUCHSRVR, Server has not been created Explanation: The server with the given name has not yet been created. User Action: Create the particular server. - SM_NOSUCHSVC, Service does not exist Explanation: The service with the given name has not yet been created. User Action: Create the particular service. - SM_NO_CONNECT, No connection established on which to perform operation Explanation: You tried to create, start, or shutdown a server. However, you are not connected to any server, so the operation cannot be performed. User Action: Connect to a server before trying to manage the server. - SM_OBJEXIST, Object exists in the configuration database Explanation: The object being referenced exists in the con- figuration database. User Action: If you are attempting to create the object, you should use a unique name for the object. - SM_OBJNOTEXIST, Object does not exist in the configuration database Explanation: The object being referenced does not exist in the configuration database. User Action: Check the spelling of the object name. Use the SHOW commands to see the objects that exist. - SM_OBJPROTECTED, Attempt to delete protected object Explanation: The object to be dropped in the configuration database is protected against deletion. User Action: Do not attempt to drop or revoke protected objects. - SM_OBSOLETE_CLIENT, The system management client is obsolete. Explanation: The client is obsolete. The protocol is no longer supported. User Action: Upgrade system management application to a currently supported one. - A-44 SQL/Services Messages SM_ODSVERS_ERR, Unsupported configuration file on disk struc- ture, version Explanation: The ODS version found in the newly opened file is not supported. User Action: Ensure that the correct configuration file is being used - SM_OWNAUTHFAIL, Owner authorization failed for service Explanation: The owner of the service, for which executors are being started, does not have a valid account on the target node so executors are not started. User Action: Provide the service owner an account on all nodes where you want to run executors for the service. - SM_PORTIDEXC, Port ID exceeds maximum limit Explanation: The network port id has exceeded the maximum limit of 65535 User Action: Specify a port id less than 65535 - SM_PROTOCOL_ERR, System management protocol error Explanation: The system management application or monitor detected an error in the system management wire protocol. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SM_RENAME_ERR, Error renaming file !AZ to !AZ Explanation: The SQLSRV_MON image could not rename its out- put or error log file to a unique name User Action: Ensure that you have correct privileges to access the file. Ensure that you have sufficient open file resources to access the file. - SM_SCANACTIVE, Scan already active Explanation: Internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-45 SM_SCANNOMORE, No more objets to scan Explanation: Internal software indicator status. User Action: If seen as a user error condition, it indicates an internal software error. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SM_SIZGTRMIN, Shared memory size for server is less than mini- mum limit Explanation: Size of shared memory is less than the minimum value allowed. User Action: Check the documentation for the minimum value allowed and then specify a shared memory size greater than the minimum. - SM_SRVRALRDYCRE, Server has already been created Explanation: You tried to create a server that already ex- ists. User Action: None. - SM_SRVRVERSEXISTS, Server on this node has the speci- fied server version Explanation: Another server on the same node already sup- ports the specified server version. User Action: Specify a different server version for the server being created. - SM_SVCALRDYCRE, Service has already been created Explanation: You tried to create a service that already exists. User Action: None. - SM_SYNERR_FILE, from line offset in file !AZ Explanation: Syntax error traceback information. User Action: Use this information to locate the position at the end of the token that caused the syntax error. - SM_SYNERR_STDIN, from offset in standard input Explanation: Syntax error traceback information. User Action: Use this information to locate the position at the end of the token that caused the syntax error. - A-46 SQL/Services Messages SM_SYNTAX, Syntax error Explanation: A syntax error occurred during parsing of a system management application command. User Action: Check your command syntax against the documen- tation. - SM_SYNTAX_ATTACH, Syntax error - the ALIAS or REUSE clauses in the ATTACH string are badly formed Explanation: The ALIAS and REUSE clauses of the ATTACH string are parsed and used by Oracle SQL/Services. The syn- tax within the attach string is not valid. User Action: Repair the ATTACH string and resubmit the statement. - SM_SYNTAX_IDENT, Syntax error - identifier "" is longer than the 31 character maximum Explanation: The maximum length for an identifier is 31 characters. User Action: Rename the identifier listed in the error message to make it less than or equal to 31 characters in length. - SM_SYNTAX_INVALID, Syntax error - statement is badly formed Explanation: You entered a statement in the system man- agement application that was correctly parsed but is not semantically valid. User Action: Check the documentation for the correct syntax. - SM_SYSMANOFFLIM, The requested modification to the system management service is not allowed Explanation: An illegal attempt was made to create or drop the system management system management service, OR, an attempt was made to alter and unalterable attribute in the service. User Action: The system management service can only be cre- ated and dropped along with server. Select attributes, not all attributes of the system management service may be al- tered. At present you may alter Default Connect Username, Idle User Timeout, and Clients Per Executor - SQL/Services Messages A-47 SM_TRANSATTACH, An ATTACH argument must be specified for a transaction-reusable service Explanation: You must supply an ATTACH argument for a transaction-reusable service. That is because there must be an existing database attach available in order that Oracle SQL/Services can create a database connection for each client association. User Action: Add an ATTACH argument to the service defini- tion. - SM_UNTERMQUO, Unterminated quoted string or identifier Explanation: A quoted string or delimited identifier was not terminated before the end of the command line. User Action: Add an ending quote character to terminate the quoted string or an ending double quote character to terminate the delimited identifier. - SM_WISH_LIST, Feature is not yet implemented Explanation: Syntax will be supported in a future release of the software. User Action: Refer to the documentation for supported syn- tax. - SOCKETERR, Error on socket call Explanation: An error was encountered on the UNIX socket system service call. User Action: N/A - SPXFAIL, Creation of IPX/SPX listener with port id failed Explanation: A IPX/SPX listener could not be created. User Action: N/A - SQLINITERR, Error processing SQL initialization file Explanation: An error was encountered while processing a SQL initialization file. User Action: Review the error log to determine the reason for the failure. - A-48 SQL/Services Messages SQLINITERRCLOSE, Error closing SQL initialization file "!AZ" !AZ Explanation: An error was encountered closing a SQL initial- ization file. User Action: Correct the problem and restart the service. - SQLINITERREXEC, Error executing SQL initialization statement Explanation: An error was encountered while executing a statement in a SQL initialization file. User Action: Correct the problem and restart the service. - SQLINITERRLTL, Error reading SQL initialization file "!AZ"; line too long Explanation: A SQL statement in a SQL initialization file was more than 512 characters long. User Action: Correct the problem and restart the service. - SQLINITERROPEN, Error opening SQL initialization file "!AZ" !AZ Explanation: An error was encountered opening a SQL initial- ization file. User Action: Correct the problem and restart the service. - SQLINITERRPARSE, Error parsing SQL initialization file "!AZ" Explanation: An error was encountered parsing a SQL initial- ization file name. User Action: Correct the problem and restart the service. - SQLINITERRREAD, Error reading SQL initialization file "!AZ" !AZ Explanation: An error was encountered reading a SQL initial- ization file. User Action: Correct the problem and restart the service. - SQLNOTINSTALLED, Specified Oracle Rdb SQL version is not in- stalled Explanation: The Oracle Rdb SQL version specified in the service definition is not installed. User Action: Verify that the Oracle Rdb SQL version spec- ified in the service definition is correct; install the required version of Oracle Rdb SQL if necessary. - SQL/Services Messages A-49 SQLVERNOTFOUND, Could not determine Oracle Rdb SQL version; results unpredictable Explanation: The Oracle SQL/Services executor translates the SQL$IDENT logical name to determine the precise ver- sion of Oracle Rdb SQL being used. The SQL$IDENT logical name is defined by the RDB$SETVER.COM DCL command procedure during executor process startup. If RDB$SETVER.COM cannot determine the Oracle Rdb SQL version from the Oracle Rdb SQL shared image, then it does not define the SQL$IDENT logical name. If the Oracle SQL/Services executor cannot determine the precise version of Oracle Rdb SQL being used, then it logs this warning message and attempts to continue; how- ever, the results may be unpredictable if the Oracle Rdb SQL installation has been corrupted in some way. User Action: No action is necessary if no further errors are logged by the executor. However, you should review the Oracle Rdb SQL installation and reinstall Oracle Rdb SQL if necessary if the executor subsequently fails because the installation has been corrupted. - SQSBADASCMSG, Bad Oracle SQL/Services ASSOCIATE message Explanation: Oracle SQL/Services API software encountered an error while attempting to parse an ASSOCIATE message from a client. User Action: This error is usually the result of a network- message corruption problem between the client and the server. However, it can also result from an internal er- ror in an Oracle SQL/Services compatibility- mode client. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQSBADMSGSIZ, Bad Oracle SQL/Services message size (received: , min , max: ) Explanation: An Oracle SQL/Services client sent a message that was too small or was larger than the negotiated buffer size. User Action: This error is usually the result of a network- message corruption problem between the client and the server. However, it could also be the result of an inter- nal software error, where no user-level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - A-50 SQL/Services Messages SQSBADPKTHDR, Bad Oracle SQL/Services packet header Explanation: Oracle SQL/Services API software encountered an error while attempting to parse the packet header in a message from a client. User Action: This error is usually the result of a network- message corruption problem between the client and the server. However, it could also be the result of an inter- nal software error, where no user-level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQSEXECBADSTATE, Invalid Oracle SQL/Services API executor driver state: Explanation: The Oracle SQL/Services API executor driver detected an invalid state condition. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - SQSEXECSIERR, Unexpected error returned from ExecSI Explanation: This an internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQSMSGBADPKTLEN, Bad Oracle SQL/Services packet-length header Explanation: The Oracle SQL/Services compatibility-mode MSG layer encountered an error while attempting to parse the packet-length header in a message from a client. User Action: This error is usually the result of a network- message corruption problem between the client and the server. However, it could also be the result of an inter- nal software error, where no user-level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQL/Services Messages A-51 SQSMSGBADRES, Bad internal message response-type/status/data combination (args: , ) Explanation: This is an internal error that could be caused by a non Oracle SQL/Services program connecting to and sending data to the server. This could also be due to an internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SQSMSGERROR, Oracle SQL/Services MSG-layer error, client: Explanation: The Oracle SQL/Services compatibility-mode MSG layer has encountered an error. User Action: See the accompanying error text for more infor- mation. - SQSMSGINTERR, Internal error in Oracle SQL/Services compatibility- mode MSG layer (args: ) Explanation: An internal error occurred in the Oracle SQL/Services compatibility-mode MSG layer. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - SQSNOTCONNECTIN, Expecting a CONNECT-IN message; received instead Explanation: The Oracle SQL/Services API executor driver was expecting a CONNECT-IN message containing an Oracle SQL/Services ASSOCIATE message from the client, but re- ceived a different type of message. This error is usually the result of a network-message corruption problem between the client and the server. However, it could also be the result of an internal software error, where no user-level corrective action is possible. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - A-52 SQL/Services Messages SRVRNOTFORHOST, Server !AZ is not defined for the host machine Explanation: A definition of the given server exists in the configuration file but this server has been defined for another node and not the host node. Therefore, the given server cannot be started from the host machine. User Action: Start the given server on a machine for which it is defined. - SRVR_EXISTS, Definition of server !AZ exists in the configura- tion file Explanation: The monitor when attempting to write the server definition into the configuration file finds that the server definition already exists. If seen as a user error condi- tion, it indicates an internal software error. User Action: Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SSRVERR, !AZ service failure Explanation: This message adds additional information to the general authorization failure message. User Action: Internal error, contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the error. - SUCCESS, Normal successful completion Explanation: Normal successful completion User Action: None. - SVCNOTRUN, The requested service is not running Explanation: The requested service is not running (i.e. no executors have been started for this service). User Action: Start executors for this service. - SVC_FAILED, The service has failed. Explanation: A started service failed, it either failed to start up properly or something caused the running service to fail after starting. User Action: Check the log files for the reason that the service failed fix the situation and restart the service. - SQL/Services Messages A-53 SVC_SHUTDOWN, The service was shut down Explanation: The service was shut down typically by system management User Action: Kill the system manager so he won't do it again. - TCPIPFAIL, Creation of TCP/IP listener with port id failed Explanation: A TCP/IP listener could not be created. User Action: N/A - TERMINATE, Process should terminate Explanation: The monitor has sent a terminate message to this process. The process should do cleanup work and termi- nate. User Action: None: client programs should never receive this error status. - TNSEXTENDED, Oracle SQL*Net TNS error codes: primary () secondary () Explanation: These are the error codes returned by the Oracle SQL*Net TNS service. User Action: Look up the text of these error codes using Oracle SQL*Net tools and take action accordingly. - TNSFAILURE, Oracle SQL*Net TNS !AZ() service has failed Explanation: An error was returned from an Oracle SQL*Net TNS-level call. User Action: The error could be resulted from a network problem or an incorrect value in an Oracle SQL*Net parameter file. If it is the latter, modify the parameter file to fix the problem. - TOOMANYCONNECTS, Attempt to exceed the dispatcher maximum number of connects Explanation: A connect arrived at the dispatcher when the number of connects was at the maximum level. User Action: resurect the system manager and tell him to increase the maximun number of connects for the dispatcher. - A-54 SQL/Services Messages TXNREUSENOTSUP, Oracle Rdb version does not support transac- tion reusable services Explanation: The version of Oracle Rdb specified for this service does not support transaction reusable services. User Action: Re-create the service as a session reusable service or use Oracle Rdb version 6.1 or later to access the database. - UNIX_ERROR_TEXT, this message is obsolete and should NOT be used Explanation: This is a place holder for an obsolete message. It's here to prevent other numbers from shifting User Action: Check the Oracle SQL/Services installation and make sure that the correct sqlsrv_messages.exe is in sys$message. The installed version, and the state of the SQLSRV_MESSAGES logical name/env variable should also be checked - UNKACCT, Access denied; Attempt to access unknown account !AZ Explanation: This message adds additional information to the general authorization failure message. The specified account does not exist User Action: Check to make sure the correct account was specified, and if so contact your system manager - UNKDATATYPE, Attribute encoded with an unknown datatype Explanation: Internal error. An encoded attribute was re- ceived with an unknown datatype. User Action: N/A - UNKRESP, Unknown response in process cmd resp Explanation: Internal error. User Action: N/A - UNKSTMT, Unknown statement type Explanation: Internal error. User Action: N/A - SQL/Services Messages A-55 UNSUPPORT_CMD, Unsupported Management Command Explanation: The requested management command is not sup- ported by the server. This can happen when the Management Client is running a higher version of Oracle SQL/Services than the Server. User Action: N/A - USERNAME, User name: Explanation: Username message for internationalization User Action: N/A - WRITERR, Error on write Explanation: An error was encountered while attempting a write operation. User Action: N/A - WRNGPRTPRCHND, Wrong protected process descriptor handle Explanation: A handle was specified for a process other than the current one. User Action: This is an internal software error, no user- level corrective action is possible. Contact your Oracle support representative for assistance. Please retain copies of any dump and trace logs generated coincident to the er- ror. - A-56 SQL/Services Messages