Does anyone know a process for repairing a corrupt syslogs table (mssql 6.5). I have tried checkdb, newalloc and rebuilding the extents. All the latter did was screw up the device assignment. Any suggestions?
View 1 RepliesHi,
I am having problems with my SQL server Agent.
1) When I try to create a New Job/Alert/Operator, I get an error message:
Error 207: Invalid Column Name "category_id"
Invalid Column Name "netsend_address"
Invalid Column Name "last_netsend_date"
Invalid Column Name "last_netsend_time"
.....All these are referring to columns in System Tables of the system Database MSDB.
2)In another SQL Server...say "A", in it's SQL Server Agent, using the Multi-Server Administration, I set up the SQL Server Agent of "A" as the Master (MSX) server, and set up a Target(TSX) server pointing to the Server "B" that has problems in SQL Agent....referred in 1) above. When I try to "Detach the MSX Server" from server B, i get a message Error 207: Invalid Column Name "netsend_address", and cannot detach..........This is again referrring to a System Table.
It appears that the problem is with the MSDB database being corrupt. Is there a way I can Repair a Corrupt MSDB without Re-installing SQL Server 2000 and without a Backup.
Any help greatly appreciate.
Thanks
Russell
hello everyone,
how can i fix my corrupt syslogs? i've tried dbcc checktable , dbcc checkalloc, and dbcc fix_al and still reports the same message.we're using ms sql 6.5. PLEASE HELP!
Hi!
I had following problem:
dbcc checktable('syslogs')
Checking syslogs
Msg 2503, Level 16, State 1
Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=438165; page# pointing to this page=438166; previous page# indicated in this page=0)
DBCC execution completed. If DBCC printed error messages, see your System Administrator.
dbcc newalloc(kmn,NOINDEX)
************************************************** *************
TABLE: syslogsOBJID = 8
INDID=0 FIRST=420675 ROOT=460295 DPAGES=57143SORT=0
Msg 2525, Level 16, State 1
Table Corrupt: Object id wrong; tables: alloc page 420608 extent id=420672 l page#=420675 objid in ext=0 (name = 0) objid in page=8 (name = syslogs)objid in sysindexes=8 (name = syslogs)
Page linkage failed for INDID 0; Processed 1 pages;
Data level: 0. 0 Data Pages in 1 extents.
TOTAL # of extents = 0
************************************************** *************
Restoring a database from a backup copy is impossible.
Alexandr.
Hi ALL,
Somehow one of tables in my database with clustered index got tempered and the pageid are not in proper order. I tried the checkdb command with repair_rebuild option but it is giving the following error.
Table error: Object ID 1984530649, index ID 1. Page (1:254682) is missing a reference from previous page (1:254681). Possible chain linkage problem.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1984530649, index ID 1. B-tree chain linkage mismatch. (1:254680)->next = (1:256198), but (1:256198)->Prev = (1:256197).
Not able to reindex the index of table. I can not even export the data to any other table with same structure.
Please help me...........
Thanks,
Pracheer
Suddenly one day I found some corruptions have occurred in my SQL Server 2012 installation. Because my 'msdb' has been marked SUSPECT/CORRUPT; hence no new work can be done as per my schedules.
I have gone about trying to repair it. I followed this article here: [URL] [the region 'Create new MSDB Database'].
I am facing some sizeable difficulties in doing this on my own. Steps 1. & 2. I have done. I am now stuck at step no. 3.My instance name is SQLEXPRESS. So, when I give,
SQLCMD -E -S<SQLEXPRESS> -dmaster -Q"EXEC sp_detach_db msdb" [as per the article], what I get is:
The System cannot find the file specified.
So I am stuck at that point. What's with the 'cannot find file specified'? The stored procedure, or the mdf, ldf files for my msdb? What is it?Also, if and when I am through with step no. 3 I would like to know about steps 5. & 6. also which are soon to follow [like how to do them correctly, safely and from where, the different options]. This is a huge priority for me to get my sql server up and running again because I can't do my other coding works without it. Everything is stalled. Slowly reaching the desperation, SOS mode..
I have a bank and your SYSLOGS is growning everyday.
I do not can stop this.
I try stop and start the SQL, DBCC CHECKTABLE, CHECKDB, DUMP TRANSACTION and other things.
Resize the space is not a good solution, because SYSLOGS cannot have this size.
I have a problems with syslogs being filled constantly and running out of space for my users to get anything done. Me and another consultant thought that it may have been due to the fact that the logins for this database were corrupt and a query was run to update certain table. Good thought but we changed it to another database and it occurred again. Question? What can cause this too occur and what can I do to prevent it from happening? I am going tonight to delete database on previous server and reinstall the sql script to create database and restore from a backup and hopefully correct this problem. What does anybody think about this situation?
View 1 Replies View RelatedHow can I resolve this issue?? it has filled up MSDB.
View 1 Replies View RelatedI have a large database that I am trying to BCP into. The BCP is approximately 12 million rows.
I have used the '-b' option for every 20000 records. Doesn't that clear the transaction log? I have multiple
BCP jobs that need to be run of this size. I am having problems with syslogs filling up which
I believe is just a reference to the transaction log? This has me confused because after the BCP I
check the transaction log size in EM and it looks empty. Can anyone help?
Hi,
i am porting data using bcp. Everytime my syslogs table is running out of space. I am not able to get the data. Why my syslogs is filling everytime. I did trucate log also, still my syslogs table is full.
This is 65 environment, it is very urgent pls any one respond to it.
---KR
My tempdb keeps filling up. A look at sysindexes indicates that all of the space used is in syslogs. Running dump tran (no_log, truncate_only), dump database, and checkpoint
give no relief. No transactions are open. Log and data are on shared devices (2MB on master device, 1024MB on a dedicated tempdb device).
Why won't my tempdb log dump off?
Thanks,
Chris
We are using SQL 6.5 and we have had problems before with our SEM reporting an incorrect value for the log size when we had just truncated the log. I would run DBCC CHECKTABLE (syslogs) just like MS Tech article Q183100 states and it would update sysindexes and correct the problem. That was on a database that is only 500mb and only has 21 rows in syslogs and it would take only a few second to run the checktable command. Now I have to run it on a database that is 5gigs and has 2,877,358 rows in syslogs. My concern is that this will take an extremely long time to run.
Does anyone have any ideas on how long this could run?
I have a MS SQL Server 6.5, SP5A database running in a MS Cluster Server environment. The transaction log (500MG)is dumped every 30 minutes to control the size and ease the point in time recovery. I have noticed that many times throughout the day, when you do a sp_spaceused on the database, the transaction log space doesn't get reported as going back to zero or near zero. It more or less stays where it was at, maybe a few MG relief. When I look at the output from the dump transaction statement (Dump Transaction dbname to dbname_tlog_dump with NOINIT, STATS), it reports that many, many pages have been dumped. However, I have been watching the sp_spaceused and it doesn't really seemed to be reflected in the numbers. (Or even in the Enterprise Manager Tool/Manage Databases - which I know has been known to report incorrectly). I have had to run dbcc checktable(syslogs) to ensure that the transaction log doesn't fill up.
Question: Does this hurt anything on recoverability by running dbcc checktable(syslogs)? Does anyone know of a bug around space not being freed in SP5A or in a MS Cluster Server environment? The application is relatively new, so I don't discount the fact that something could be going on there as well. Ideas?
I inherited an application (or two) that run on SQL Server 6.5, which Ihaven't used in years, and am having a problem. I get the error:------------------------------------------------------------------------Can't allocate space for object 'Syslogs' in database 'master' becausethe 'logsegment' segment is full. If you ran out of space in Syslogs,dump the transaction log. Otherwise, use ALTER DATABASE orsp_extendsegment to increase the size of the segment.------------------------------------------------------------------------....when I... well... just about everything. If I try:DUMP TRAN master WITH NO_LOG....I get:------------------------------------------------------------------------Can't allocate space for object 'Syslogs' in database 'master' becausethe 'logsegment' segment is full. If you ran out of space in Syslogs,dump the transaction log. Otherwise, use ALTER DATABASE orsp_extendsegment to increase the size of the segment.Unable to write CHECKPOINT record in database 1 because the log is outof space.Unable to continue logged version of DUMP TRANsaction. Please free upsome space in database 1 or use the NO_LOG option.------------------------------------------------------------------------....If I try to expand the device or database, I get the "Can't allocatespace..." error. If I use "DBCC UPDATEUSAGE(0)" I get nothing, "DBCCCHECKTABLE(syslogs)" tells me it's using one page and has 29 rows(which is what I get if I "SELECT * FROM syslogs").How can I expand the space available to the master database orotherwise resolve this problem?Thanks in advance for any help anyone can offer. I know there probablyaren't many of you still using 6.5.Regards,Brian
View 6 Replies View RelatedI found this script some where on internet..i am not sure what it does and how to i solve the problem because my friend has already run the script and i donno how to get back to the original configuration.
/* this script works on a database that is a copy of pubs. I created this database easily with DTS
This only works on SQL Server 7 databases
*/
/* NOTE: This script will truly corrupt a database. It should not be run on ANY real
database. It is only for simulating corruption for training purposes.
*/
sp_configure allow, 1
go
reconfigure with override
go
update sysindexes set FirstIAM = 1234
where id = OBJECT_ID('roysched')
go
sp_configure allow, 0
go
reconfigure with override
go
How to sovlve the issue after the corrupt is done...how do i modify the info back to original..
Are there any other process or script that i can simulate to corrupt the databse and solutions pertaining to the same..i would like to experiment and then see how it goes and how quickly i can solve...
Thanks,
Jeff
The ldf file of a db was deleted by mistake. This was done whilst the SQL Server Service was still running. The db was not detached cleanly. I ran sp_detach_db on the db and tried re-attaching but got the error message:
"Database [dbname] cannot be opened because some of the files could not be activated".
Subsequently I have tried creating a new db called the same as the old one. Stopping the MSSQL service, copying over the mdf and re-starting the service. The db still comes up as suspect and the error log shows "Device activation error. The physical file name 'D:LogsETERBK_Log.LDF' may be incorrect". I have tried copying over the new ldf to the correct location but the same message appears.
I am not interested in getting the data back but would like to get back the stored procedures. Can anyone help this is urgernt?
Have a corrupt SQL database that I am unable to repair using any of the repair options with DBCC CHECKDB. Below is the output from the repair_allow_data_loss option.
I can't seem to figure out how to go about fixing this. Any takers?!
Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:24264) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 8921, Level 16, State 1, Line 1
CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test ((m_type >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test ((m_type >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:24264). Test (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 7 pages from (1:24264) to (1:32351). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:32352). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:32352). Test ((m_type >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:32352). Test (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 7 pages from (1:32352) to (1:40439). See other errors for cause.
DBCC results for '8602955'.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 8 allocation errors and 3 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 1395 rows in 27 pages for object 'sysobjects'.
CHECKDB found 8 allocation errors and 3 consistency errors in database '8602955'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I have a table that I can't read any data.
It hangs up when I try to drop it as well.
So, what are my options here? Secondly, what has caused this?
I had installed a third-party software on my server and that corrupted my Master DB. Over the weekend when we bought SQL server down, we could not bring it back up. I had to re-install SQL server and then restore all my databases from the backup. Is there a better way of doing this???
Curiously
Someone who calls himself a DBA
Hi everybody,
I have a strange problem with one of the jobs created through a maintenace plan. The idea is that every 2 hours a transaction log backup is created and backups older than 2 days should be removed. This worked for several months without a problem, but suddenly today the job reports failed as status.
I looked into jobhistory but all I got is the following message:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Strange enough reports the sqllog that the t-log has been backed up succesfully. The files are on disk and I can restore them without a problem.
Any ideas what is going on ???
Tia Markus
Hi All,
I am working in a test environment where I need to corrupt a database for test purpose/R&D. After corrupting the database, I ran the DBCC CHECKDB (pubs, repair_fast) and then DBCC CHECKDB (pubs, repair_rebuild) commands. But DBCC is not fixing the corrupt database.
My question is why DBCC is not fixing the corrupted Database? Is that a limitation of DBCC or is there any other way/command or tool to fix the corrupted database other then restoring from the previously backed up file.
The following are the steps that I followed to corrupt the database:
I used the following script (available in the script section of www.swynk.com) to corrupt the pubs database.
sp_configure allow, 1
go
reconfigure with override
go
update sysindexes set FirstIAM = 1234
where id = OBJECT_ID('roysched')
go
sp_configure allow, 0
go
reconfigure with override
go
Then I did a select * from roysched. I got the error:
Server: Msg 5180, Level 22, State 1, Line 1
Could not open FCB for invalid file ID 53764 in database 'pubs'. Table or database may be corrupted.
The pubs database got corrupted. Now, I want to fix this error. So I set the pubs database to single user mode and ran the DBCC command :
DBCC CHECKDB (pubs, repair_fast) that doesn't help so I ran the DBCC CHECKDB (pubs, repair_rebuild) command.
I got big DBCC output. I doesn't seems to fix the pubs database. When I did a select * from roysched again it gave the same corruption error.
I would appreciate any help in this issue.
Thanks
Sri
Hi,
One of my tables got corrupt and it is not possible to bring down the Database into Single user mode to run the dbcc to repair it. Is there any other way that I could correct.
Thanks
Cynthia
Msg 8978, Sev 16: Table Corrupt: Object ID 901630305, index ID 8. Page (5:572498) is missing a reference from previous page (8:98777). Possible chain linkage problem. [SQLSTATE 42000]
Msg 8928, Sev 16: Object ID 901630305, index ID 8: Page (8:98777) could not be processed. See other errors for details. [SQLSTATE 42000]
Msg 8976, Sev 16: Table Corrupt: Object ID 901630305, index ID 8. Page (8:98777) not allocated or corrupt. Parent (5:335525) and previous (5:572497) refer to it. [SQLSTATE 42000]
Msg 8944, Sev 16: Table Corrupt: Object ID 901630305, index ID 8, page (8:98777), row 38. Test (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 525 and 26. [SQLSTATE 42000]
What is the best approach to repairing a corrupt table? I received the following error from last night's maintenance. (SQL 6.5)
Thanks, Kevin
[2] Check Data Allocation...
WARNING: Database AHSDATA is currently being used by 1 user(s).
This may cause spurious problems to be reported.
The following errors were found:
Table Corrupt: object id does not match between extent in allocation page and Sysindexes; check the following extent: alloc pg#=247552 extent#=247720 object id on extent=-1175060352 (object name = -1175060352) object id in Sysindexes=1329491865 (object name = PS_AHS_RETIRE_2000)
Table Corrupt: Index id on extent should be 0; check the following page and ids: alloc page=247552 extent=247720 index id on extent=200
Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc pg#=247552 extent#=247720 previous extent# on this extent=-1 previous extent should be=247712
Table Corrupt: Object id wrong; tables: alloc page 247552 extent id=247720 l page#=247720 objid in ext=-1175060352 (name = -1175060352) objid in page=1329491865 (name = PS_AHS_RETIRE_2000)objid in sysindexes=1329491865 (name = PS_AHS_RETIRE_2000)
** Execution Time: 0 hrs, 10 mins, 50 secs **
[3] Update Statistics...
[Microsoft SQL-DMO] Error 605: [SQL Server] Attempt to fetch logical page 247792 in database 'AHSDATA' belongs to object 'PSPNLDEFN', not to object 'PS_AHS_RETIRE_2000'.
[Microsoft SQL-DMO] Error 10025: [DB-Library] Possible network error: Write to SQL Server Failed.
** Execution Time: 0 hrs, 5 mins, 11 secs **
Hi,
I am receiving an Msg 2540 on a database when I perform the DBCCs. It looks like the indexes on this one table got corrupt. I know this because when I perform the DBCCs with the noindex option then I do not get any errors. I tried to drop and recreate the indexes (two indexes - one clustered and one unique) but to no avail. The dbccs continued to produce the error.
If someone has any ideas please respond. This is a prodn problem and so any input would be greatly appreciated.
Thanks again
Kiran
I have been having problems with the SQL 7 server when temporary tables are being created, so I ran a DBCC checkdb against tempdb,
and this is what came back. When I try to run the dbcc with repair_allow_data_loss it says the database must be in single user mode.
This option is not allowed in tempdb. So now what? Does any one have any suggestions?
Server: Msg 8999, Level 16, State 1, Line 1
Database tempdb allocation errors prevent further CHECKDB processing.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:109) in database ID 2 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'IAM_PG MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:1000) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
Server: Msg 8905, Level 16, State 1, Line 1
Extent (1:1016) in database ID 2 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
DBCC results for 'tempdb'.
CHECKDB found 3 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 3 allocation errors and 0 consistency errors in database 'tempdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (tempdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I have a problem for dropping a table from my database and I got the error message: ""Extent chain for object 736005653 is not correctly linked." The problem indicates table corrupt on the database from DBCC checknewalloc. Instead of reloading the database from a dump, do you have anyway to repair the damage table or drop it.
TIA,
Stella Liu
I am running SQL server 6.5 with sp3 on NT4.0 with sp6. I ran DBCC checkalloc on one of my database and got the following message.
Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc pg#=6815488 extent#=6815736 previous extent# on this extent=8625424 previous extent should be=6815728
I have previouly ran dbcc checkdb on the database and I was not able to correct the problem. Please help!
This morning no one was able to connect to the SQL server. At the server, the RAID set showed no activity. I could not bring up any applications. When clicking the start button, it would take 5 minutes to get a response. I connected to the server from a different machine and tried to restart the SQL services, without success. I could access the Event Viewer Application log. All entries in the log read "DB-LIBRARY error - SQL Server connection timed out." The SQL error log listed the following error " Lazywriter: LRU list is corrupt, bhead 0xe50040, bnew 0, bold 0x130bb00, stat 0x1004/0, page 0x1e1608, bufno 0, freebufs 5528, freelist 0xf1bfe0
99/04/10 22:22:10.10 spid2 Lazywriter: LRU list is corrupt, bhead 0xe50040, bnew 0, bold 0x130bb00, stat 0x1004/0, page 0x1e1608, bufno 0, freebufs 5498, freelist 0x118274"
What does this error indicate? We have received this error in the past and have upgraded our RAID controller because. This is the first time we have had this error since upgrading the controller a month ago.
Thanks.
Philip Talavera
System Administrator
SVG Distribution
After implementing a recommendation to perform dbcc checkalloc before nightly backup, I began getting the error below on msdb. Books Online suggests restoring from a known clean backup. We have only been using SQL Server for a few weeks and it seems that all our backups of msdb have the same problem. Is there any way of correcting this problem?
Msg 2521, Level 16, State 1
Table Corrupt: Page is linked but not allocated; check the following pages and table: alloc page#=3584 extent id=3816 logical page#=3816 object id in extent=8 (object name = syslogs) index id in extent=0
Hello!
I'm intrested in all possible ways to corrupt data or log files in SQL server 2000 except of manualy editing them or cutting the comp's power abruptly.
Thank you.
Very strange. I suspect McAfee Anti-Virus was run against SQL 6.5 files, but don't know for sure. Now server won't start. Rebuild master, it starts. Restore Master, it hangs. Rebuild master, Disk ReInit & ReFit devices, user database and server hangs while recovering db log on restart. A backup was made after the corruption got into db, so restoring db has same result, hang. Cannot open db to begin anything. Help?
View 1 Replies View RelatedI run a daily maintaince job and it fails.But when i go through the error log. i get
this eror "'Table Corrupt: Extent id 30464 on allocation pg# 30464 has objid 732178004 and used bit on, but reference bit off"
how do i get the table name fron sysobjects as i have had no luck when i do a simple select query to get the details i need
Getting the name would make it easier to solve the problem
thanks
safac