FIX: Database Fallback May Cause Dbid to Change (180603)
The information in this article applies to:
This article was previously published under Q180603
BUG #: 17807 (SQLBUG_65)
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.
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.
WORKAROUND
To work around this problem, ensure that the dbid of the original database
is not in use on the fallback server.
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 INF: How to Obtain SQL Server 6.5 Service Pack 5a For more information, contact your primary support provider.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix KB180603 |
---|
|