Messages 1319 through 1338

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
-1319L Error 3002 WW137 "Synchronization schema changes and script versions are not supported for this database" The current database does not have catalog support for synchronization schema changes and script versions. To use this feature, upgrade your database to the most recent version.

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

-1320L Error 2822 QFA62 "Error raised by user-defined function: %1" An error was raised by a user-defined function.

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

-1321L Error 3004 WW139 "Table or view '%1' is not valid for use with this statement" The named table or view cannot be used with this statement. For example, the statement may not allow temporary tables or views.

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

-1322L Error 3005 WW140 "A synchronization schema change is already in progress" A START SYNCHRONIZATION SCHEMA CHANGE statement is already in progress.

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

-1323L Error 3006 WW141 "Subscription to publication '%1' for '%2' omitted from statement" A START SYNCHRONIZATION SCHEMA CHANGE statement lists a table that will be modified, but a subscription which refers to that table was omitted from the statement.

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

-1324L Error 3007 WW142 "Connection is not allowed to have table locks when executing this statement" An attempt was made to execute a statement by a connection that is holding table locks. Because the statement could release all locks, including those held before the statement started, the locks must be released before the statement can be executed.

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

-1325L Error 3003 WW138 "Column subset for table '%1' in publication '%2' does not match that specified in publication '%3'" The columns included for a table must be identical for all subscribed publications which reference the table.

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

-1326L Error 3008 5RW40 "Subscription '%1' not found" You attempted to ALTER, DROP, or otherwise reference a subscription that does not exist.

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

-1327L Error 3009 42WCE "The materialized view cannot be changed to immediate because its SELECT list contains a SUM function over a nullable expression and it doesn't contain a COUNT function over the same expression" You attempted to change the refresh type to immediate for a materialized view whose definition contains a SUM function over a nullable expression but it doesn't contain COUNT function over the same expression.

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

-1328L Error 3010 WW143 "Table '%1' must synchronize to be in publication '%2'" A publication cannot contain a table with a SYNCHRONIZE OFF constraint; all tables in a publication must synchronize. You attempted to add a table with a SYNCHRONIZE OFF constraint to a publication, or to alter a table to use SYNCHRONIZE OFF when the table is already in a publication.

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

-1329L Error 3011 5RW41 "This operation is only allowed within a synchronization schema change" You attempted an operation that is only allowed within a synchronization schema change.

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

-1330L Error 2823 42WE0 "The function '%1' does not allow use of the '%2' clause" You have attempted to use the specified SQL clause within the context of a function that does not permit such use. Note that the function may have been used directly in the query or indirectly within a named window.

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

-1331L Error 2807 42WE1 "The function '%1' requires the use of the '%2' clause" You have attempted to invoke the specified function without the use of a mandatory SQL clause within the context of the function. Note that the function may have been used directly in the query or indirectly within a named window.

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

-1332L Error 3012 WW144 "Feature '%1' is unknown or invalid" You attempted to lock or unlock an unknown feature.

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

-1333L Error 3013 WW145 "Feature '%1' was not locked by this connection" You attempted to unlock a feature that was not previously locked by this connection.

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

-1334L Error 3014 WW146 "Feature '%1' is locked by another connection" You attempted to use a feature that was previously locked by another connection.

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

-1335L Error 3015 42X00 "Type '%1' does not support method calls (near '%2')." You attempted to invoke a method on a value of a data type that does not define any methods.

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

-1336L Error 3016 42X01 "Type '%1' has no method named '%2' (near '%3')." When attempting to match a method invocation, no method was found with the appropriate name. Check for spelling errors.

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

-1337L Error 3017 42X02 "Method invocation '%1' does not match an overload (near '%2'). Available overloads are '%3'." When attempting to match a method invocation, none of the defined overloads was found to match the provided argument types. You may need to use CAST to select the appropriate call.

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

-1338L Error 3018 42X03 "Type '%1' is not instantiable (near '%2')" A NEW expression was used for a data type that does not define any constructor methods.

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