We have a Microsoft SQL Server 2000 SP3 running database for Microsoft
Navision 3.7
From time we encounter problems, especially when running heavy query
procedures from Navision, with the transaction log. It's actually setup as
folows:
We get the following errors (once every 2-3 months so far):
The log file for database 'ME_Prod' is full. Back up the transaction log for
the database to free up some log space..
in between numerous abovementioned messages I have the following:
Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement to install..
Could not write a CHECKPOINT record in database ID 9 because the log is out
of space.
Automatic checkpointing is disabled in database 'ME_Prod' because the log is
out of space. It will continue when the database owner successfully
checkpoints the database. Free up some space or extend the database and then
run the CHECKPOINT statement.
Our software vendors upgraded their software and our environment - and applications do not interface as they ought. The vendors do not appear to have any further ideas (to those listed below) and at this stage neither do I. It is now a week since the *upgrade* went live. Looking for new suggestions....
Full story (epic) below. Object names have been changed to protect the *innocent*.
Our organisation had 2 applications:-
appBank appHouse
both running on the respective platforms:
Server name svrCAT: Windows Server 2000 sp 4 / SQL Server 2000
Server name svrDOG: Windows Server 2000 sp 4 / SQL Server 2000
Transactions were "posted" from svrDOG to svrCAT via a linked SQL Server, using login dbL1nkLogin.
dbL1nkLogin was made a user of (with relevant table permissions) of the respective databases:
dbForBank dbForHouse
*** At this point all was working ***
Upgrading appBank to appBigBank required SQL Server 2005 (and more diskspace).
A new server was purchased:
Windows Server 2003 R2 sp 2 / SQL Server 2005 (Server name svrHORSE)
A linked server was created from the SQL instance on svrHORSE to svrDOG using login name dbL1nkLogin. dbL1nkLogin was made a user (with relevant table permissions) on database:
dbForBigBank
Attempts to "post" transactions were "posted" from svrDOG to svrHORSE via the linked SQL Server fail with the appBank application generating the following errors:
On first attempt:
************* FILE ERROR ************* Error Code...... 3902- Error Message...The COMMIT TRANSACTION request has no co .rresponding BEGIN TRANSACTION. Table Name......** NOT APPLICABLE ** Description.....** NOT APPLICABLE ** Function....... COMMIT sys991: Program already in use COBOL error at 000444 in sys500 Called from 00076A in sys990ssv Called from 000457 in sys991 Called from 01177D in gls489 Called from 000DFA in gls396 Called from 003961 in gls394 Called from 000258 in glp900 Called from 003DC1 in syp250
On subsequent attempts:
************* FILE ERROR ************* Error Code...... 1206- Error Message...The Microsoft Distributed Transaction Co .ordinator (MS DTC) has cancell Table Name......tblHouseFinancials Description.....DYNAMIC SQL CALL INTERLUDE Function....... UPDATE *FAILED* Processing Job 'WIN/'
* Parameters and controls within the appBank application were verified.
* Password on dbL1nkLogin was reset in the SQL instances on svrHORSE and svrDOG
* Compared the link server settings on svrHORSE to svrCAT:
Security tab: Be made using security context - Remote Logging: dbL1nkLogin / password
Server Options: Collation Compatible checked (on svrHORSE only) Data Access checked RPC checked RPC Out checked
* Made dbL1nkLogin dbo on databases dbForBigBank and dbForHouse. * Changed default database from master to dbForBigBank on svrHORSE * Rebooted svrHORSE and svrDOG (multiple times) * Verified that svrHORSE could ping svrDOG, and vice versa * Using DTCping.exe, Verified that the SQL instance on svrHORSE could ping svrDOG, and vice versa * On svrHORSE, Administrative Tools -> Component Services -> Computers has the following settings for "My Computer" Network DTC Access:
These settings were already set. My understanding of KB329332 suggest they are correct. As I could not establish the configuration date of these settings rebooted the server to ensure they'd taken effect.
* Loaded SQL Server 2000 sp4 on svrDOG (Rebooted afterwards in case services not stopped and started correctly) srvDOG now has MDAC 2.8 sp1 (2.81.1117.6) while srvHORSE has a later version (2.82.3959)- I assume sp2. While they are not the same version, MDAC 2.8 sp2 KB 231943 advises that 2.8 sp2 is not available via the web - so I think it's the best I can do).
* Stopped and manually started MSDTC and SQL Server (via Administrative Tools - Services) in case MSDTC was not being started first.
* KB873160 suggests opening port 135 and adding msdtc.exe as an exception in the Windows Firewall. At present there is no firewall on svrHORSE - which I would assume negates this necessity (at present). In Administration Tools - Services there was a service for the firewall running. Stopping this service has no effect on this issue.
* ( The svrHORSE machine was not created from an ghosted image ).
** None of these things have resolved the issue. **
After Having installed the SQL Server 2000 DTS Designer Components necessary to edit legacy DTS packages on 2005 server, I keep getting the following message when trying to open SQL Server 200 Enterprise Manager:
"The procedure entry point ?ProcessExecute@@YAXPAUHWND_@@PBG1@Z could not be located in teh dynamic link library SEMSFC.dll."
Is there a way to fix so that I can open Enterprise manager?
I setup a new ODBC connection to MS SQL Server 2000 on Windows XP and keep getting the following errors when I try to either register a new SQL Server 2000 group within Enterprise Manager or test the new ODBC connection:
Current configuration
- MS SQL Server 2000 -Windows XP -ODBC 3.85.1117
Errors:
I. Within SQL Server 2000 Enterprise Manager
Error: SQL Server connection open
II. When I test the ODBC connection:
Microsoft SQL Server ODBC Driver Version 03.85.1117
Running connectivity tests...
Attempting connection [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
TESTS FAILED!
Now here is what has me totally confused:
I can use the command line ISQL to access the database on the server and IP is all correct and port is available.
I was getting this error message from our Cold Fusion application front end when it was trying to execute one of our stored procedures.The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "SERVERNAME" was unable to begin a distributed transaction.
I was a bit puzzled by this because we don't use distributed transactions (at least I don't specifically code them). I did some research online and I found out how to modify the DTC component on the server to have the proper configurations.Then, when trying again we got this error message:
Unable to start a nested transaction for OLE DB provider "SQLNCLI10" for linked server "SERVERNAME". A nested transaction was required because the XACT_ABORT option was set to OFF.
So, I was able to resolve that as well by changing that option in the stored procedure...Now, there are 3 stored procedures - One does inserts; one does updates; and one does deletes.The actions are being done to a view in a database on another server. The view definition uses a linked server.
The error was/is only happening on the INSERT stored procedure. So, I'm a little baffled as to why it only bombs on the insert stored procedure and not the others. They are all coded in the same fashion..Do distributed transactions work differently if its an insert vs. update or delete? Why is it all of the sudden treating these as distributed transactions when they aren't coded as such?
The code is very simple and looks just like this:
INSERT vw_Name SELECT bla, bla2, bla3 FROM local table WHERE bla bla
And again vw_Name would be a table on another server that we have via Linked Server. It is also a SQL Server (but its SQL 2000).
Hi All:I am getting an error when trying to open a recordset in SQL Server 2000.The error states that the transaction log is full. Is there any way I canclear out or empty the transaction log, or get rid of it alltogether as itis not really needed?Any help would be appreciated.Thanks and regards,Ryan
Greetings: When I script out my log shipping configuration from the GUI and subsequently drop the log shipping and try to recreate it with the created script, the backup and restore functions do not seem to be working; please see script below. Is there an additional step (or steps) that the SSMS GUI does not output when it creates the script for log shipping? I noticed in the GUI after I run the script that the destination folder for copied files is blank as well.
Example error from backup/restore job - Error: The path is not of a legal form.(mscorlib)
-- Execute the following statements at the Primary to configure Log Shipping
-- for the database [rdevsql2].[SymbolLookUp],
-- The script needs to be run at the Primary in the context of the [msdb] database.
Hey Folks! I have a typical requirement by my client. On submitting a Update (Bulk) button a huge database operation starts. A huge bulk update operation need to be performed. This would take 2-3 minutes some times. Client wants a cancel button in this case where he can be given a way to cancel the database Transaction. Please let me know in case if there is a way out. Thanks, in advance. Regards, Uday.D
Hi All:I am getting an error when trying to open a recordset in SQL Server 2000.The error states that the transaction log is full. Is there any way I canclear out or empty the transaction log, or get rid of it alltogether as itis not really needed?Any help would be appreciated.Thanks and regards,RyanThe error msg is: tempdb transaction log is full. B/U transaction log tofree up space..."
(I may be in the wrong forum.) How do I obtain/find the properties of a table using SQL Query Analyer (SQL Server 2000)? Specifically, I would like to run a query to find the most recent date of any transaction on a table. I have a script that I use for SQL Server 2005 but it doesn't work in 2000. I don't know 2000 but I'm guessing that the syntax is different?
Here's the 2005 SQL Server script (stolen from 2005 Books Online BTW):
I know i can use the sentence SET IMPLICIT_TRANSACTIONS ON in a Stored Procedure to force SQL Server to set the connection into implicit transaction mode.
Have i a sentence or configuration to force all SQL Server connections to implicit transaction mode?
Has anybody encountered a physical size limit for a sql server 2000 transaction log running on win2k?
Transaction log reached ~6Gb before rolling back the delete stating transaction log was full. There was 42Gb free on the server and the log was set to unlimited growth.
Can anyone help me with this scenario!!!! I have a sybase database and a sqlserver 2000 database. I want to insert data into sybase database table thru sql-server 2000 using distributed queries When i execute the following the transaction
Create procedure myCurrentDataBaseProcedure as begin
begin tran insert into mytable values(1) if @@error <>0 begin rollback transaction return end insert into sybasedatabaseserver.databasename.dbo.tablename values(1) if @@error <>0 begin rollback transaction return end commit transaction end
The procedure is created in sql server database trying to execute this procedure..shows error The first part of the procedure is executed.
But the error is here insert into sybasedatabaseserver.databasename.dbo.tablename values(1) The data is succesfully inserted in the local database I am unable to insert data into the remote database Can anyone suggest me wht shd i do in this scenario Are there any drivers to be loaded to commit this transactions
Hi techiesI have set up a Transaction replication from My Primary Server toSecondary Server on Orders table.Thousand of records gets inserted on Orders every hour which getreplicated on the secondary server. it works finereporting apps uses Secondory server's Orders table data for generatingreports .The Problem :Let say if i want to Remove older records from Orders table in theprimary serverwith out reflecting this change on the secondary server.is there a way to PREVENT this operation /transaction to be propogatedto the secondary server.Note : i am moving the records to another table (orders_Archive ) anddeleteing the rows from orders table . Also I need all the rows to bepresent on the secondary server table.Please advice ASAPRegards,Raj
How I can run a SQL Server Transaction Log Backup using a Windows CMD File. It's that posible? Anyone know the command or how do this?
We already have a application monitoring our SQL databases. Everytime the transaction log get full, it sends us an alert. Would be better if our application repair the problem itself, executing a command (Windows CMD File).
I'm not a expert using SQL databases or MS DOS Prompt commands.
We have two SQL Server 2005 production DB at remote sites. Due to network bandwidth issue, we need to replicate these DBs (publishers and distributers) to central corporate SQL 2000 DB (subscriber for backup and possible reporting (and in rare case as a failover server).
We would start out with backup from SQL 2000 db restored on remote SQL 2005 DBs. When we have DB issue on remote 2005 DB, we want to restore it from central corp. 2000 DB backup. Since two DBs are replicating to central DB, we DO NOT want combined db back up data on restored remote 2005 db. We can restore the db and delete unwanted data before we turn on replication from this restored server. So, this is not a problem.
The real problem is how to avoid snapshot replication (during initialization) when we create a transaction replication on this restored server to avoid over writing data on the central subcriber sql 2000 DB???
Hello, I currently have a Transactional Log reader agent failing with the below error: The process could not execute 'sp_replcmds' Error: 14151, Severity: 18, State: 1 SQL Server Assertion: File: <logscan.cpp>, line=2223 Failed Assertion = 'm_noOfScAlloc == 0'. Stack Signature for the dump is 0x24642FE5 Error: 3624, Severity: 20, State: 1. SQL Server Assertion: File: <logscan.cpp>, line=1985 Failed Assertion = 'startLSN >= m_curLSN'. Stack Signature for the dump is 0xD7150BD4 Now, I understand that SP4 is supposed to fix a similar issue. SP4 has been installed and the errors keep happening. I do notice that the hot fix mentions different line numbers than the above errors. Does anyone know if this is a new bug? If not can someone explain the fixes to me, thanks,
I recently updated the datatype of a sproc parameter from bit to tinyint. When I executed the sproc with the updated parameters the sproc appeared to succeed and returned "1 row(s) affected" in the console. However, the update triggered by the sproc did not actually work.
The table column was a bit which only allows 0 or 1 and the sproc was passing a value of 2 so the table was rejecting this value. However, the sproc did not return an error and appeared to return success. So is there a way to configure the database or sproc to return an error message when this type of error occurs?
I’ve got a big problem with my Database, Whenever I runs my query I’ve got error on the half way. I’m using MSSQL 2000. So I run DBCC CHECKDB and the follow errors result shown. I don’t know how to solve that problem.
Plz help me plz help me If that database crush I’m gonna be fu*ked up by my boss. :...( plz
DBCC results for 'Table_1'. Server: Msg 8928, Level 16, State 2, Line 1 Object ID 795149878, index ID 0: Page (1:352679) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 795149878, index ID 0, page (1:352679), row 44. Test (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_A | RECTAG_RESV_B))) failed. Values are 157 and 193. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 795149878, index ID 0, page (1:352679), row 44. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 18754 and 3160.
There are 0 rows in 1 pages for object 'Total_Profit_Loss'. Server: Msg 2511, Level 16, State 2, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:161199), slots 25 and 26. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:173791), slots 4 and 5. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1211151360, index ID 0: Page (1:206443) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 1211151360, index ID 0, page (1:206443). Test (m_freeCnt == freeCnt) failed. Values are 660 and 692. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:217603), slots 18 and 19. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:266945), slots 26 and 27. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:268051), slots 28 and 29. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1211151360, index ID 0: Page (1:277634) could not be processed. See other errors for details.
DBCC results for 'Pin'. Server: Msg 8939, Level 16, State 106, Line 1 Table error: Object ID 1211151360, index ID 0, page (1:277634). Test (m_freeCnt == freeCnt) failed. Values are 2168 and 2164. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1211151360, index ID 0: Page (1:299697) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 1211151360, index ID 0, page (1:299697). Test (m_freeCnt == freeCnt) failed. Values are 3435 and 3431. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1211151360, index ID 0: Page (1:302290) could not be processed. See other errors for details. Server: Msg 8944, Level 16, State 1, Line 1 Table error: Object ID 1211151360, index ID 0, page (1:302290), row 12. Test (((UNALIGNED DataRecHdr*) m_pRec)->r_tagB == 0) failed. Values are 4 and 0. Server: Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1211151360, Index ID 0. Keys out of order on page (1:900223), slots 2 and 3. There are 5940869 rows in 210312 pages for object 'Pin'. CHECKDB found 0 allocation errors and 14 consistency errors in table 'Pin' (object ID 1211151360).
CHECKDB found 0 allocation errors and 23 consistency errors in database 'MY_SQL_DB'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MY_SQL_DB ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I have several SQL 2000 servers that are running SQL 8.002162. Most are Windows 2003. Because of a note I saw in a non MS forum, I was testing these servers for the numeric comparison issue in MS article 899976, "FIX: A query that involves data that is the numeric data type may return incorrect results in SQL Server 2000 SP3 and in earlier SQL Server 2000 service packs". All the servers act as expected (fixed) since they are running post SP4 and patches. But, one server fails the comparison test scripts in the KB. All these servers are running the same version of SQL. The server that still fails is windows 2003 SP1.
Why does one server reporting to be version 8.002162 fail a test that should be patched and does it mean that although the server is reporting it is version 8.00.2162 it has failed some updates and might be upatched for other issues?
Is there any way to emulate the try/catch mechanism that SqlServer2005 provides using SqlServer2000? Or more simply, Is there any kind of IGNORE_ERROR or CONTINUE_ON_ERROR setting for SqlServer 2000?
I'm trying to use a SQL 2000 view in one of my sources. The view isnt anything special --- just three tables that have been unioned together. All these three tables have the EXACT same datatypes as well as column names. There are no constraints on these tables (yet). There is an identity seed on the first ID column. However, when I try to access this view, it generates the following error:
Server: Msg 4502, Level 16, State 1, Procedure MyView, Line 5 View or function 'MyView' has more column names specified than columns defined. Server: Msg 4413, Level 16, State 1, Line 1 Could not use view or function 'MyView' because of binding errors.
1) When I run a query Select * from MY_Table the query never completes. If I press cancel in Query Analyzer after 1 second or 2 minutes, it always shows the same 174 records. The total table size is 800 KB with 3148 rows .. according to TaskPad
2) No queries, even queries that would return only 1 record complete execution against that table
3) I am unable to rename the table, if I try to rename the table Enterprise Manager becomes unresponsive and has to be closed.
4) If I try to browse the rows through Enterprise manager by scrolling through the records, it allows me to go down through a number of rows and then Enterprise manager gives me a timeout expired error.
5) I ran a DBCC CheckDB command ran for 1 hr and 7 minutes. It says there are 0 allocation errors and 0 consistency errors in the database.
6) The other database tables seem to be OK and the Database is operational except for calls involving the 1 Table
We are going insane trying to start Report Manager on a SQL Reporting Services 2000 installation. The programmer/admin who originally set this up for us is gone.
We recently upgraded a database/application server to a new server, causing the data source being used by reports in reporting services to no longer be valid. Unfortunately, we do not have access to the original report project to 're-deploy' with the corrected data source.
We desperately need to get the reports that are installed to retrieve their data from the new database location/machine. We understand this can be done by specifying a new data source in Report Manager. (To clarify, we have NOT moved the report servier installation or database, these remain in place - it's just the deployed reports that no longer point to the correct data source.)
For some reason, our Report Manager will no longer run - when we try to launch it, we get a windows login dialog - nothing will work here. We've tried both local and domain admins and constantly get ACCESS IS DENIED 401.3 error messages that we do not have permission/problems with ACL's.
We've gone so far as to allow EVERYONE read/write access to the ReportManager and ReportServer folders and the RS virtual directories, but nothing seems to help.
Can anyone help with this? Ideas on how to change our data source, or how to get back into Report Manager?
Since we are somewhat technical, but not experts, and don't have much more time to waste, we are willing to pay $500 for this project to someone willing to access the server and fix the problem so that the reports point to the correct database and restore access to Report Manager.
I have Full database backup upto previous day and transaction logfile of Today transaction. my database has crashed. I have restored previous day's Full backup. I have faced difficulty to restore today's transaction from today's transaction log. What are the steps to restore full database back and one day's transaction log file. Note: there is no differential database backup and transaction backup.
I'm having an issue shrinking a transaction log, and am hoping that one of you guys could give me some advice....
Currently, this database (DB1) has approximately 20GB of data, and my transaction log has grown to 22GB.
The database is in Simple Mode (although may have been created as Full, then changed)
I have a Maint. Plan backing up the DB daily, but noticed today that this has not been working for the last week :'(
There are 3 other databases on this same server, which are similar sizs in GB, but have tiny Trans Logs - their backups have of course been working fine.
I've backed up DB1 this morning - a whopping 42GB file - then issued a "dbcc shrinkfile", followed by a "backup log ... truncate_only", followed by another "shrinkfile", but the log is still 22GB
My database log file is now 53M, is it a way to minimize it, delete it or erase it, this log file is to big for nothing, I try to shrink it and delete it manually, but this corrupt the database, can someone help me thx ?
The size of my transaction log file is out of control. I've backed up the database and the transaction log went from 120 GB to 120 MB. Now, I can't reduce the size of the transaction log file. It's still at 120 GB (w/ almost all of that being held as Free Space). I get errors when I try to manually reduce the file size. Any tips?
I'm getting this when executing the code below. Going from W2K/SQL2k SP4 to XP/SQL2k SP4 over a dial-up link.
If I take away the begin tran and commit it works, but of course, if one statement fails I want a rollback. I'm executing this from a Delphi app, but I get the same from Qry Analyser.
I've tried both with and without the Set XACT . . ., and also tried with Set Implicit_Transactions off.
set XACT_ABORT ON Begin distributed Tran update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.TRANSACTIONMAIN set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.TRANSACTIONMAIN set REPFLAG = 0 where REPFLAG = 1 and DONE = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.WBENTRY set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.WBENTRY set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.FIXED set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.FIXED set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.ALTCHARGE set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.ALTCHARGE set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.TSAUDIT set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.TSAUDIT set REPFLAG = 0 where REPFLAG = 1 COMMIT TRAN
It's got me stumped, so any ideas gratefully received.Thx
Is it possible to load both the SQL 7 database and transaction logbackups to SQL 2000 ? I assume it will perform the upgrade during theload.Thanks,James
Just curious if anyone out there has had success running a Distributed Transaction on Windows 2000 Professional SP4 lately?
I have come to the conclusion that is is virutally impossible. I am running MSDE on a Win2k Pro machine and trying to run a distributed transaction via linked server and am getting the
"The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction."
error. Yes I have been scouring the web looking for answers and have implemented pretty much everything I have run accross... and Yes the MSDTC service is started on both machines... BTW: If I run the procedure on XP it works great!!!
I am wondering if anyone even uses Win2k Pro anymore let alone trying to run a distributed tarnsaction on the darn thing.
If anyone out there has it running let me know I would love to chat with you for a minute or two.
