FIX: Database Fallback May Cause Dbid to Change

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q180603

BUG #: 17807 (SQLBUG_65)

Expand all | Collapse all

SYMPTOMS

When a database is brought online by a fallback server, the dbid that was originally assigned to the database may not be available. This causes the fallback server to assign a new dbid number to the database. If execute permissions for objects have been established in the original database, users may not have access to the objects until they have been recompiled.

Back to the top

CAUSE

When a user attempts to use an object (a view, stored procedure, table, and so on), permissions are checked before the user is allowed access to the object. In the case of a stored procedure, the pre-complied version is resolved by using the original dbid. If the user does not exist in the corresponding dbid on the fallback server, an error message (error 916) will be generated, indicating the user was not found in the database. This message will then resolve and show the correct database name on the fallback server for the original dbid.

The text of error 916 is:

Msg 916, Level 14, State 1
Server user id %d is not a valid user in database '%.*s'

For an example of this situation, see the MORE INFORMATION section of this article.

Back to the top

WORKAROUND

To work around this problem, ensure that the dbid of the original database is not in use on the fallback server.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 (http://support.microsoft.com/kb/197177/ ) INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

Back to the top

MORE INFORMATION

The following example illustrates the problem:

   Before Fallback
   ---------------

    - Original server: mydb_1 = dbid 7
    - Fallback server: mydb_2 = dbid 7

   After Fallback
   --------------

    - Fallback server: mydb_2 = dbid 7; mydb_1 = dbid 8

In this example, if a user in mydb_1 attempted to execute a stored procedure that he or she had execute permissions on, the stored procedure would fail to execute. The error message would show that the user was not found in database mydb_2 (dbid of 7 on the fallback server). If the user did exist in dbid 7, the stored procedure would be executed.

If any user who has create permissions attempted to use the stored procedure, the stored procedure would be recompiled on error. This would then re-resolve the database name to the new dbid and allow subsequent users that had execute permissions to use the object.

Back to the top

APPLIES TO

Microsoft SQL Server 6.5 Standard Edition

Back to the top

kbbug kbfix KB180603

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top