Messages WW147 through WW224

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

SQL State Msg Type Number SQL Code Message Possible Cause
WW147 Error 3023 -1343L "Feature '%1' is locked because synchronization is in progress" You attempted to use a feature that was previously locked because a synchronization is in progress.

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

WW148 Error 3024 -1344L "Rollback occurred due to blocking_others_timeout" This connection has been rolled back because another connection was blocked on this connection for longer than the blocking_others_timeout option setting. All requests on this connection will get this error until it is disconnected.

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

WW151 Error 3027 -1348L "Mirror server name '%1' does not match current server name" The server name specified in a CREATE MIRROR SERVER statement must match the current server name when the statement is executed on a child server.

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

WW152 Error 3028 -1349L "The parent of this mirror server is not currently connected" The statement being executed requires a connection from this mirror server to its parent, but the parent is not currently connected.

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

WW153 Error 3029 -1350L "The parent of this mirror server is not the primary server" The statement being executed requires a connection from this mirror server to the primary server, but the parent is not the primary server. The connection string to this server's parent does not match the connection string for the primary server.

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

WW154 Error 3030 -1351L "Mirror child server creation failed" The creation of a child server on the primary server failed or was disallowed.

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

WW155 Error 3031 -1352L "Mirror server with type '%1' is already defined" A CREATE MIRROR SERVER statement specified a server type that has already been defined.

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

WW156 Error 3040 -1360L "Cannot assign automatic mirror server parent" A CREATE MIRROR SERVER or ALTER MIRROR SERVER statement requested that a mirror parent be automatically assigned, but a parent server could not be found. The auto_add_server option may not be set, or might be set to an invalid server name.

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

WW159 Error 3060 -1381L "Database server name '%1' cannot be the same as either the primary or mirror server" The mirror servers defined with type PRIMARY or MIRROR cannot have names that match actual server names.

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

WW160 Error 3062 -1383L "The licensed maximum number of mirror servers with type COPY has been exceeded" The maximum number of mirror servers with type COPY that may be defined is limited by the database server license. An attempt was made to create a new mirror server with type COPY when the maximum allowed number of such servers already existed.

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

WW161 Error 3063 -1385L "Synchronization failed. Check the dbmlsync log file for more details." The synchronization was not successful. Check the dbmlsync log file for more details.

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

WW162 Error 3064 -1386L "Failed to connect to the dbmlsync server. Check the dbmlsync log file for more details." The MobiLink agent adapter failed to make a connection to the dbmlsync server. Check the dbmlsync log file for more details.

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

WW163 Error 3065 -1387L "Failed to shut down the dbmlsync server. Check the dbmlsync log file for more details." The MobiLink agent adapter encountered an error while attempting to shut down the server. Check the dbmlsync log file for more details.

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

WW164 Error 3066 -1388L "Failed to start the dbmlsync server. Check the dbmlsync log file for more details." The MobiLink agent adapter failed to start a new dbmlsync process or the server did not begin processing requests before the timeout expired. Check the dbmlsync log file for more details.

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

WW165 Error 3068 -1397L "The definition of temporary table '%1' has changed since last used" The definition of a temporary table has changed since it was last used in a stored procedure or trigger. The procedure must be recompiled.

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

WW166 Error 2363 -1597L "The transaction may not be committed because the primary server lost quorum" You attempted to commit a transaction on a primary server that just lost quorum with the partner and arbiter servers. The transaction may or may not have been committed. The partner servers will attempt to determine which server will become the new primary server.

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

WW207 Error 3222 -1580L "Failed to load the MobiLink client support libraries." In order to use the SYNCHRONIZE command, a MobiLink client must be installed on the same computer where the database server is running.

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

WW221 Error 2928 -1245L "Partition name '%1' already used" This partition name has already been used.

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

WW222 Error 2929 -1246L "Partition '%1' is not adjacent to or before partition '%2'" These partitions are not adjacent - they cannot be merged.

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

WW224 Error 2932 -1249L "Logical file '%1' is not part of dbspace '%2'" This logical file is not part of this dbspace.

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