PRB: Moving Fallback DB Back to Primary Svr May Cause Error 913

Last reviewed: December 22, 1997
Article ID: Q178345
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

After moving databases back to the primary server, which runs the stored procedure sp_fallback_deactivate_svr_db on the fallback server, executing stored procedures or using views in the databases enrolled for fallback may cause the following error:

   Error: 913, Severity: 22, State: 2
   Could not find row in Sysdatabases with database id <x>. Run DBCC
   CHECKTABLE on Sysdatabases.

CAUSE

The stored procedures or views were used while the database was moved to the fallback server, and the dbid used for the database on the fallback server was not the same as the dbid on the primary server.

WORKAROUND

To work around this problem, do either of the following:

  • Make sure that the dbids of the databases enrolled for fallback are not in use on the fallback server.

    -or-

  • Ignore the error 913 because the stored procedure or view is still run correctly.

MORE INFORMATION

To create new databases on the fallback server while it does not control the fallback databases, do the following:

  1. Create temporary databases of any size to use the dbids from the primary server.

  2. Create the new databases.

  3. Drop the temporary databases.


Additional query words: stproc st proc
Keywords : SSrvAdmin
Version : WINNT:6.5
Platform : winnt
Issue type : kbprb
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.