Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts

Thursday, March 22, 2012

Error: 5180 - Could not open FCB for invalid file ID #

When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
databases we get following errors:
- spid333 Error: 5180, Severity: 22, State: 1
- spid333 Could not open FCB for invalid file ID <#> in database '<dbname>'.
Is there anyone here that has a hint on what is causing this.This error stated that the file was dropped or the database was corrupted.
- Please run DBCC SHRINKDATABASE again.
- If the error shows up again, please run DBCC CHECKDB to see if the
database is corrupted.
- If the database is not corrupted, then probably there is a bug in shrink
code, you can contact PSS for further assistant.
--
Stephen Jiang
Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tor Lynge Olsen" <TorLyngeOlsen@.discussions.microsoft.com> wrote in message
news:A5E9AA7C-6A4D-4527-A9EC-687A15216E91@.microsoft.com...
> When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
> databases we get following errors:
> - spid333 Error: 5180, Severity: 22, State: 1
> - spid333 Could not open FCB for invalid file ID <#> in database
'<dbname>'.
> Is there anyone here that has a hint on what is causing this.
>

Friday, March 9, 2012

Error writing binary data

Dear all,
we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
We have three similar databases, which all contain a table to store binaries
as base64-Text.
From time to time we face a problem writing in one of this tables. The
requests get a timeout.
Its always the same table in the same database. The other tables never
caused any problem.
Reading access ist no problem, but writing doesn't work.
We can fix the problem by copying the data in a new table an rename them
that the new table replaces the old one. Sometimes the problem ist solved
when we add a new index (doesn't matter which column) and save the table.
You can't see any difference between the the table in the relevant database
and the other ones.
Even a restart of the whole machine doesn't solve the problem, so that locks
shouldn't be the cause.
Any tips?
Greeting from Germany
Matthias MerzHi
There are a significant number of changes between the version you are
running and the current version (2187) so you may want to review the KB
article to see if there is anything that may have fixed this
http://www.aspfaq.com/sql2000builds.asp
If you are getting any error messages in the SQL Server log or the Windows
Event log will help.
You don't say if dropping all indexes helps!!!
John
"Matthias Merz" wrote:
> Dear all,
> we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
> We have three similar databases, which all contain a table to store binaries
> as base64-Text.
> From time to time we face a problem writing in one of this tables. The
> requests get a timeout.
> Its always the same table in the same database. The other tables never
> caused any problem.
> Reading access ist no problem, but writing doesn't work.
> We can fix the problem by copying the data in a new table an rename them
> that the new table replaces the old one. Sometimes the problem ist solved
> when we add a new index (doesn't matter which column) and save the table.
> You can't see any difference between the the table in the relevant database
> and the other ones.
> Even a restart of the whole machine doesn't solve the problem, so that locks
> shouldn't be the cause.
> Any tips?
> Greeting from Germany
> Matthias Merz
>
>

Error writing binary data

Dear all,
we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
We have three similar databases, which all contain a table to store binaries
as base64-Text.
From time to time we face a problem writing in one of this tables. The
requests get a timeout.
Its always the same table in the same database. The other tables never
caused any problem.
Reading access ist no problem, but writing doesn't work.
We can fix the problem by copying the data in a new table an rename them
that the new table replaces the old one. Sometimes the problem ist solved
when we add a new index (doesn't matter which column) and save the table.
You can't see any difference between the the table in the relevant database
and the other ones.
Even a restart of the whole machine doesn't solve the problem, so that locks
shouldn't be the cause.
Any tips?
Greeting from Germany
Matthias MerzHi
There are a significant number of changes between the version you are
running and the current version (2187) so you may want to review the KB
article to see if there is anything that may have fixed this
http://www.aspfaq.com/sql2000builds.asp
If you are getting any error messages in the SQL Server log or the Windows
Event log will help.
You don't say if dropping all indexes helps!!!
John
"Matthias Merz" wrote:

> Dear all,
> we run a SQL Server 2000 SE 8.00.534 SP2 on a 2 CPU server.
> We have three similar databases, which all contain a table to store binari
es
> as base64-Text.
> From time to time we face a problem writing in one of this tables. The
> requests get a timeout.
> Its always the same table in the same database. The other tables never
> caused any problem.
> Reading access ist no problem, but writing doesn't work.
> We can fix the problem by copying the data in a new table an rename them
> that the new table replaces the old one. Sometimes the problem ist solved
> when we add a new index (doesn't matter which column) and save the table.
> You can't see any difference between the the table in the relevant databas
e
> and the other ones.
> Even a restart of the whole machine doesn't solve the problem, so that loc
ks
> shouldn't be the cause.
> Any tips?
> Greeting from Germany
> Matthias Merz
>
>

Friday, February 24, 2012

Error while using first time!

I'm trying to learn about SQL databases and use them for my asp.net app sine I cant get the hang of MySQL in ASP. Every time I go to create a new SQL Database it saids: Would you like to place it in the App_Data folder basicly and I say yes. Then the error:

Unable to find DbProivderFactory for type System.Data.SqlClient.SqlConnection

Hi Clanstyles,

Based on the error message, I think the provider factory was not installed properly on you machine. Or the configuration files might not be written correctly.

Please try the following:

1. Open machine.config file under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG
2. Check the nodes under configuration/system.data/DbProviderFactories to see if all the provider has been installed successfully. It has to look like this.

<DbProviderFactories>
<add name="Odbc Data Provider" invariant="System.Data.Odbc" description=".Net Framework Data Provider for Odbc" type="System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add name="OleDb Data Provider" invariant="System.Data.OleDb" description=".Net Framework Data Provider for OleDb" type="System.Data.OleDb.OleDbFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add name="OracleClient Data Provider" invariant="System.Data.OracleClient" description=".Net Framework Data Provider for Oracle" type="System.Data.OracleClient.OracleClientFactory, System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add name="SqlClient Data Provider" invariant="System.Data.SqlClient" description=".Net Framework Data Provider for SqlServer" type="System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</DbProviderFactories>

HTH.