Microsoft KB Archive/113471

{|
 * width="100%"|

FIX: SQL Server FixList for Version 4.20bK12
'Article ID: Q113471

Creation Date: 05-APR-1994

Revision Date: 29-APR-1997' 

The information in this article applies to:

- Microsoft SQL Server version 4.2bK12 for OS/2 The following is a list of fixes and other various improvements that have been made in SQL Server version 4.2bK12. SQL Server version 4.2bK12 is now available from your primary support provider. For more information, contact your primary support provider.

Please note that workarounds have been provided for your information only. It is not necessary to implement these workarounds if you have the updated software.

List of Problems Corrected in 4.20bK12:


 * FIX: Message 233 When Running Stored Procedure
 * FIX: GP Fault Issuing Update Statistics
 * FIX: RPC and DUMP TRANSACTION May Cause Timeslice or Trap

Description of Problems Corrected in 4.20bK12:

FIX: Message 233 When Running Stored Procedure

ARTICLE ID: \[\[..\/\|Q\]\] BUG# OS/2: 1657 (4.2a)

SYMPTOMS

When executing a stored procedure with SQL Server version 4.2 for OS/2, the following error message 233 may be incorrectly generated:

The column X in table Y may not be null. Table Y represents a temporary table and column X is a column that is not in table Y. The generation of this error is linked to the creation of multiple temporary tables after logging into SQL Server and the execution of a stored procedure that makes use of temporary objects that it creates. It is also usually seen initially after SQL Server has been started.

CAUSE

Upon execution of the stored procedure, an incorrect column from syscolumns in the tempdb database is referenced for the temporary object in the stored procedure. This column (which does not belong to the temporary object) does not allow nulls, thus resulting in message 233 being generated.

FIX: GP Fault Issuing Update Statistics

ARTICLE ID: \[\[..\/\|Q\]\] BUG# OS/2: 1733 (4.2a)

SYMPTOMS

Under specific conditions, SQL Server may infrequently general protection fault (GP fault) when an UPDATE STATISTICS command is issued for a table or an index.

WORKAROUND

In some cases, re-issuing the UPDATE STATISTICS command will succeed. If it fails repeatedly, the statistics for the indexes can be updated by dropping and re-creating the indexes for the table.

FIX: RPC and DUMP TRANSACTION May Cause Timeslice or Trap

ARTICLE ID: \[\[..\/\|Q\]\] BUG# OS/2: 1745 (4.2)

SYMPTOMS

If server1 is dumping a transaction log to a disk device (for example, not "with truncate_only" or "with no_log") and a RPC is running on server1 to server2 when server2 is shut down or powered off, server1 may timeslice and hang the SQL Server on that server (server1). In some instances, SQL Server might also trap.

These errors are often accompanied by the following error in the error log:

7223: Cannot read from site '%.*s'
 * }

-

 Additional query words: K12

Keywords : SSrvGen kbfixlist

Version : 4.2b

Platform : OS/2

Issue type : kbref

"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." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''