Hi all,
I recently upgraded to SQL 6.5- sp5a. I run DBCC TEXTALL as part of my nightly maintenance. Our db is about 3 GB and is heavy on text
fields. Since the upgrade, DBCC TEXTALL hangs up the server until I reboot it. The last message in the error log is "Warning:
out of RA slots... comfigure more RA slots." (or something like that). This never happened before.
BOL says don't monkey with the RA slots per thread, so
I've been adjusting the number of RA worker threads. I raise it, bounce SQL SERVER, and try to run the DBCC TEXTALL again.
Same results. Eventually I got up to 10 RA worker threads, at which point I got an "IO buf_wait" error, which also hung up the server.
I've read that increasing RA worker threads will eventually run you out of buffer space, and it looks like that's what happened.
I'm beginning to think that the problem isn't really with isn't really with the number of RA worker threads I have configured,
but rather with something that sp5a changed. Or maybe DBCC TEXTALL is running into some sort of corruption it can't handle...
Or something...
So, I'm reading up on the relationship between buffer cache, RA, etc., but
the sad fact is that information on that low down level is hard to find, and I don't understand most of it anyway.
Any suggestions, reading recommendations, comments, or jeers would be highly appreciated.
I am trying to apply SQL Server Service Pack 5a to my original SQL Server 6.5 but an error keeps coming up "Setup initialization could not be successfully executed. ISQL,EXE could not be executed.Pls check relevant .out file".
The last line of the relevant .out file produced by this error is:
You cannot run SELECT INTO this database. The DBO would have to run sp_dboption to enable this option.
Msg 208, Level 16, State 1, Server REYWINNT, Procedure sp_helpsort, Line 295
I have a third party app that has been 'certified' by the vendor on SQL 6.5 SP5. We are aware of the dump database issues when using SP5 and Enterprise Manager. We would like to use SP5a to get around those issues.
Is anyone aware of any other 'bugs' or problems that have come about in SP5a....
I've got a script that runs regularly to monitor log space usage on a SQL 6.5 sp5a server. Where the log space usage is greater than 75% it then dumps the log. However the Enterprise Manager screen still shows usage as being above 75%. I'm aware that I need to run dbcc checktable(syslogs) to have EM reflect the change, and my question is: Within my sql script how do I switch context to the database where I need to run the dbcc checktable(syslogs) command?
I run replication among several SQL 6.5 Servers with SP3. Recently, I've applied SP5a to publisher/distributor. After that, some publications continued to replicate normally, but two of them started to act strangely - the distribution tasks end succesfully, but it seems that no transactions were marked for replication.
After investigating a bit, I've found that the data that continued to replicate normally is modified by stored procedures, while problematic tables are updated directly. Then I've tried to run isql/w updates against problematic tables - all the changes were succesfully applied to the subscribers. The other difference between problematic and non-problematic tables is their size - problematic tables are much bigger and more frequently updated.
All the subscribers are still SQL 6.5 Servers with SP3. One of them is also a publisher that uses SP5a-upgraded SQL Server as remote distributor. Its publications replicate OK.
I've installed SQL Server Service pack 5a on our test lab Database and have come up with problems with my protocol. Everything works fine IF I set the Net Library to Named pipes. But before the service patch, I was running Multi-Protocol WITH TCP/IP (much faster). How can I make SQL use Multi? Using Named pipes screws up my replication. Any suggestions???
I am playing with DBCC command to check the contsrainst on a perticular table (DBCC CHECKCONSTRAINTS ('myTable') WITH ALL_CONSTRAINTS), it always gives the following result:
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
While installing the service pack 5a, I had the following error "setup could not be successfully completed, ISQL.EXE could not be executed. Please check the relevant *.Out file.
Now I am unable to start up my SQL service. When I try to start it , I get the following message: Error : 1105, Severity: 17, State: 2 Can't allocate space for object 'Syslogs' in database 'master' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
Apparently 4 mb of free space in my master database was not enough for the service pack. I can't extend the size of my Master database because I can't get the SQL service to start.
I am having problems with stack dumps (as many as 12 a day) at a production site running NT 4.0 SP4 with Sql Server 6.5 SP5A. I've tried running every diagnostic utility on the server but it shows no problems. Before I open a ticket with Microsoft on the stack dumps, I'd like to upgrade the server to NT Service Pack 6A. My question is, do I need to re-install SqlServer SP5A? Will the NT Service Pack 6A invalidate SQL SP5A?
we have a client that just upgraded to sp5a and are encountering problems...one stored procedure seems to routinely become corrupted, and does not complete correctly. however, it does not error out, and the only way to tell that it did not complete successfully it to query the data.
the only solution that i have found to this problem is to recreate the procedure. i have tried using sp_recompile to force a recompile at next runtime, and the problem still occurs. i have tried recreating the calling procedure, and recreating procedures it calls, but neither fix the problem. after recreating the procedure, it continues to run fine for anywhere from 1 hour to 8 hours, and then starts to fail again.
microsoft so far has not been able to give us help in diagnosing this, and i am coming up with nothing in my own investigations.
has anyone seen a problem like this in sp5a?
also, it is occurring on 5 similar dbs that are on the same server...
When running Enterprise Manager from my desktop pc to try and expand a database device I am unable to do so. The size shown is negative, and the max size is the same, with the 'Change Now' box greyed out. When I log on directly onto the server I can easily expand the db device. There is lots of free space on the server. Our set up is quite small with four NT workstations and two NT servers with SQL Server 6.5 on them. All these six machines are in the same workgroup. The workstations are on a separate floor to the servers, which are in the computer room. I have a feeling this is a networking issue. Can anyone suggest why this is happening?
After applying SP 5a I found out that my SQL strings with sums and groups produced double rows. I found out that grouping one column (type CHAR(6)) produced two distinct rows of the equal values.
All the values in that column have 4 characters, but it seemed like some distinct values were grouped by the whole field length i.e 6 characters. I haven't seen earlier that those blanks after field value change the grouping results.
When I transferred the table and data to old SQL Server without any SPs, query showed distinct values correctly.
The sort order and other settings are the same. Can anyone tell where to look for help?
Hi I've recently upgraded 4 sql servers to sp5a and have just found that BCP fails on all of them with a DR Watson error. I did reinstall the Nt sp after installing sql server sp5a. Can anyone help ? Thanks
Has anyone gotten clustering to work via the Cluster Wizard in SP5a?
I've got two ProLiant 5500's with the Compaq Clustering S/100 option. I've done a fresh install of NT Enterprise 4.0 SP3, then installed clustering with the Compaq S/100 drivers... everything fails over nicely, can make shares off the virtual server, etc. I then install SQL Server 6.5 EE, then apply SP5a -- so far, so good.
Now I try to run the clustering wizard. The wiz prompts me for my SA password. I enter it, and it gives me a message box that it can't start or log onto the database... but when I look in the event log it appears to have logged on successfully with a Non-trusted connection.
I followed the advice of Paul Randal, but Im stumped as I am not able to determin what the corruption issues are. This is SQL 2000 and the database is a Solomon database that was recently upgraded to 6.5. the error I get when running the DBCC checkdb is as follows:
Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:18645) with latch type SH. sysindexes failed. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
DBCC execution completed. If DBCC printed error messages, contact your system administrator. DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Now, the bad news. I am a bit of a novice and have picked this up from someone who left my company. It appears the latch error has been around for some time and only reared up when I instituted a new back up system that runs a dbcc check befor backing up. I don't think I have any clean backups.
Hello, Just in case anybody has had this problem after applying service pack 5a. a stored procedure that sets serial numbers on records on a temporary table is skipping every other record. I ran the code manually on isql and could not replicate the error, however when re-compiled on stored procedure it fails misserably. when is Microsoft going to release a service pack that actually works?
Did you know that Executive does not recognize 2000 as a leap year?
If anybody has any suggestions on this problem, besides the obvious (using a real table) please write back thanks.
Hi my name is Rodrigo and Im from Brasil, so, sorry about my english.
I have a problem using MSSQL 2000. Iīm using a client/server application, and sometimes (almost every day) the sql server start to use 100% of CPU and crash the system. I donīt know how and when but it hapens always. I never found a reason for it, but looking at the event viewer in windows 2000 i saw an error about www publishing (something like that). Maybe my sqlserver is trying to connect to internet to do something (i donīt know). Please if somebody can help me send me a mail. Thanks a lot.
Hi, I'm trying to install SQL Server 2000 Dev Edn. When I install client and server tools it will crash after I enter the administration password. But this only happens when I install it with server tools, its OK with just client tools. Thanks
My Sql server went down last night. Is there a way to find out what could have caused system to crash? Is there any way to notify the DBA when sql services have stopped running?
Recently my computer had a crash on which SQL Server was installed. And if that wasn't enough, the backup failed to. Now I've installed SQL Server again, but I have these *.mdf and *.ldf files, which contains my data and my tables etc. So my question is, how do I get this data into my newly installed SQL Server? Maybe it's quite simple, but I can't find it. Im using SQL Server Enterprise version 7.0 on Win2k Advanced Server.
Hi, My sql server stopped unexpectedly and restarted itself today, and I have no clue why. The NT Event Viewer provides this "insight":
The MSSQLService terminated unexpectedly.
The event id is 17052, which isn't documented in BOL. Does anyone have any explanation, and some suggestions on how to avoid this in the future? thanks, Jason
Does anyone have any input on why my SQL Server keeps crashing? I get the following errors: Error : 17805, Severity: 18, State: 0 00/03/21 09:06:06.42 ods Invalid buffer received from client. 00/03/21 09:09:51.56 kernel SQL Server terminating due to 'stop' request from Service Control Manager At other times, there were some STACK DUMP ERRORS. We are on service pack 4 (I have been pushing to apply 5a) Please help, Thank you.
I got the following message in the error log when SQL Server 6.5 crashed. ''Stored function 'xp_runwebtask' in the library 'xpsqlweb.dll' generated access violation; SQL Server is terminating process 60'' Source:spid 60 Anyone know what this means ? If you think you know of have come across it before, please inform me.
I need help. I am facing following problems since days here you have the errors messages:
Mesg 18264 : DATABASE dumped with following info: Database Name:IITMSDB, Creation Date and Time:Feb 12, 99(23:00), Pages dumped:3898618, Current Sequence:36201 19370307, Sort Order:52, Striped:NO, Number of Dump Devices:1, device info:(VOLID=SS0001 NAME=iitmsdb_dump TYPE=DISK FILE=1)
Mesg 17562 : Checking space allocation for database 6
