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. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. These errors are often accompanied by the following error in the error log: In some instances, SQL Server might also trap. 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). If it fails repeatedly, the statistics for the indexes can be updated by dropping and re-creating the indexes for the table.įIX: RPC and DUMP TRANSACTION May Cause Timeslice or TrapĪRTICLE ID: \\] BUG# OS/2: 1745 (4.2) In some cases, re-issuing the UPDATE STATISTICS command will succeed. 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. This column (which does not belong to the temporary object) does not allow nulls, thus resulting in message 233 being generated.ĪRTICLE ID: \\] BUG# OS/2: 1733 (4.2a) 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. It is also usually seen initially after SQL Server has been started. 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. Table Y represents a temporary table and column X is a column that is not in table Y. ![]() When executing a stored procedure with SQL Server version 4.2 for OS/2, the following error message 233 may be incorrectly generated: FIX: RPC and DUMP TRANSACTION May Cause Timeslice or Trapĭescription of Problems Corrected in 4.20bK12:įIX: Message 233 When Running Stored ProcedureĪRTICLE ID: \\] BUG# OS/2: 1657 (4.2a).FIX: GP Fault Issuing Update Statistics.FIX: Message 233 When Running Stored Procedure.It is not necessary to implement these workarounds if you have the updated software. Please note that workarounds have been provided for your information only. ![]() For more information, contact your primary support provider. SQL Server version 4.2bK12 is now available from your primary support provider. The following is a list of fixes and other various improvements that have been made in SQL Server version 4.2bK12. Microsoft SQL Server version 4.2bK12 for OS/2 The information in this article applies to: FIX: SQL Server FixList for Version 4.20bK12
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |