Messages 1299 through 1318

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-1299L Error 2988 WW127 "Drop multiplex server is allowed only in a multiplex setup." Drop multiplex server is allowed only in a multiplex setup.

Click here for a list of possible parameters and odbc states.

-1300L Error 2989 WW128 "Cannot add first multiplex server with excluded status." Users are not allowed to add the first multiplex server with status excluded.

Click here for a list of possible parameters and odbc states.

-1301L Error 2990 WW129 "Cannot create multiplex server with role coordinator." Users are not allowed to create a multiplex server with role as coordinator.

Click here for a list of possible parameters and odbc states.

-1302L Error 2982 WW121 "Host Port specification (%1) is invalid." Host port specification is invalid.

Click here for a list of possible parameters and odbc states.

-1303L Error 2991 54W16 "Too many MESSAGE...FOR CONNECTION messages" You executed a MESSAGE...FOR CONNECTION statement and the maximum number of messages for the connection have already been queued.

Click here for a list of possible parameters and odbc states.

-1304L Error 2992 WT021 "Could not create a new text index for this table with the same settings as \"%1\No message Two text indexes with the same column list and configuration settings cannot be created for a table.

Click here for a list of possible parameters and odbc states.

-1305L Error 2993 0AWD5 "MobiLink communication error -- code: %1, parameter: %2, system code: %3" An error was encountered while communicating with a MobiLink server.

Click here for a list of possible parameters and odbc states.

-1306L Error 2994 WW238 "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table.

Click here for a list of possible parameters and odbc states.

-1307L Error 2995 WW130 "Database mirroring options are not supported for this database" The current database does not have catalog support for database mirroring servers and options. To use this feature, upgrade your database to the most recent version.

Click here for a list of possible parameters and odbc states.

-1308L Error 2996 WW131 "Mirror server \"%1\" not found" The named mirror server was not found in the database.

Click here for a list of possible parameters and odbc states.

-1309L Error 2997 WW132 "Mirror server \"%1\" already exists" An attempt was made to create a mirror server that already exists in the database.

Click here for a list of possible parameters and odbc states.

-1310L Error 2998 WW133 "Mirror server \"%1\" is referenced by another server" An attempt was made to drop a mirror server that is referenced by another mirror server in the database.

Click here for a list of possible parameters and odbc states.

-1311L Error 2999 WW134 "Principal mirror servers are already defined" An attempt was made to create a mirror server without a parent server, but two principal mirror servers are already defined in the database.

Click here for a list of possible parameters and odbc states.

-1312L Error 3000 WW135 "Mirror server \"%1\" is not a valid parent server" An attempt was made to define a parent for a mirror server that would result in a cycle.

Click here for a list of possible parameters and odbc states.

-1313L Error 2969 54W17 "Maximum string length exceeded" A string operation attempted to create a string longer than the maximum allowed by the server.

Click here for a list of possible parameters and odbc states.

-1314L Error 3001 WW136 "Cannot force failover when current server is marked as preferred" An attempt was made to execute ALTER DATABASE SET PARTNER FAILOVER but the current server is marked as preferred. Attempting to force a failover in this situation is not allowed.

Click here for a list of possible parameters and odbc states.

-1315L Error 2931 WW046 "Script file missing statement \"go\" delimiter on a separate line" For UltraLite, all non-comment SQL statements in a script file (including the final one) must be followed by "go" on a line by itself. For strings, you can use "\ngo" to end a statement.

Click here for a list of possible parameters and odbc states.

-1316L Error 2930 0AW25 "Unsupported load column specification used for a catalog store table." For catalog store tables, only some of the load column specifications (for example, filler) are permitted.

Click here for a list of possible parameters and odbc states.

-1317L Error 2919 WW239 "Multiplex server '%1' is shutting down due to a successful configuration change" Successful execution of certain statements to change multiplex configuration forces a server shutdown. You will get the above error if you issue such a command.

Click here for a list of possible parameters and odbc states.

-1318L Error 2890 42W89 "More articles are being dropped from publication '%1' than are defined" The number of articles in a publication can never fall below one. Your ALTER PUBLICATION has more drop/delete article clauses than the current number of articles in the publication.

Click here for a list of possible parameters and odbc states.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com