Messages 2979 through 2998

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

Number Msg Type SQL State SQL Code Message Possible Cause
2979 Error WW235 -1291L "Column '%1' Partition '%2' may not be assigned to a dbspace because partitioning is not supported for datatype '%3'." The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace.

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

2980 Error WW236 -1292L "Column '%1' may not be assigned to a dbspace because partitioning is not supported for datatype '%2'." The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace.

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

2981 Error WW237 -1293L "Partition key of '%1' is unsupported." Partitioning over the specified datatype is not supported.

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

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

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

2983 Error WW122 -1294L "Parameter (%1) length has exceeded its limit (%2)." Given parameter's length has exceeded the specified limit.

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

2984 Error WW123 -1295L "Database path must be absolute." Specified Database path must be absolute.

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

2985 Error WW124 -1296L "(%1) is not unique." Specified value for a given parameter already exist in the multiplex configuration.

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

2986 Error WW125 -1297L "No of servers in multiplex setup has reached to the maximum limit." No of servers in multiplex setup has reached to the maximum limit. User cannot add any more secondary servers.

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

2987 Error WW126 -1298L "Cannot alter multiplex failover node and other multiplex server properties in the same statement." Users are not allowed to alter the multiplex failover node status and other multiplex server properties in the same statement.

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

2988 Error WW127 -1299L "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.

2989 Error WW128 -1300L "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.

2990 Error WW129 -1301L "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.

2991 Error 54W16 -1303L "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.

2992 Error WT021 -1304L "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.

2993 Error 0AWD5 -1305L "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.

2994 Error WW238 -1306L "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.

2995 Error WW130 -1307L "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.

2996 Error WW131 -1308L "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.

2997 Error WW132 -1309L "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.

2998 Error WW133 -1310L "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.


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