We have numerous suspect databases across multiple serverse due to a hardware
failure on our SAN. The part of the SAN that failed had a combination of data
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
|||Thanks Greg. Once the hardware was repaired and we restarted the services (we
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>[quoted text clipped - 5 lines]
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
>2000/2005 database, so you may luck out.)
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1
|||"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com
Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts
Wednesday, March 28, 2012
Help! Suspect Databases - Hardware Failure
We have numerous suspect databases across multiple serverse due to a hardware
failure on our SAN. The part of the SAN that failed had a combination of data
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (we
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>> We have numerous suspect databases across multiple serverse due to a
>> hardware
>[quoted text clipped - 5 lines]
>> server
>> back up, after fixing our hardware failure, what would be the best steps?
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
>2000/2005 database, so you may luck out.)
>
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1|||"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via SQLMonster.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services (we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robert
failure on our SAN. The part of the SAN that failed had a combination of data
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (we
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>> We have numerous suspect databases across multiple serverse due to a
>> hardware
>[quoted text clipped - 5 lines]
>> server
>> back up, after fixing our hardware failure, what would be the best steps?
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
>2000/2005 database, so you may luck out.)
>
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1|||"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via SQLMonster.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services (we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robert
Help! Suspect Databases - Hardware Failure
We have numerous suspect databases across multiple serverse due to a hardwar
e
failure on our SAN. The part of the SAN that failed had a combination of dat
a
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200703/1
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (w
e
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>[quoted text clipped - 5 lines]
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQ
L
>2000/2005 database, so you may luck out.)
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1|||"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via droptable.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services
(we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run aft
er
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robertsql
e
failure on our SAN. The part of the SAN that failed had a combination of dat
a
and log files, but not both for a given database.
Right now we have services shut down on the server. When we bring the server
back up, after fixing our hardware failure, what would be the best steps?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6eca09c69ec9c@.uwe...
> We have numerous suspect databases across multiple serverse due to a
> hardware
> failure on our SAN. The part of the SAN that failed had a combination of
> data
> and log files, but not both for a given database.
> Right now we have services shut down on the server. When we bring the
> server
> back up, after fixing our hardware failure, what would be the best steps?
BEFORE bringing up the server, make complete backups of all files.
Then once you bring up the server, check the logs and find out why the
databases are suspect.
In some cases it may be as simple as the drive letters or paths no longer
being right and once you fix those, the database may come up cleanly.
If it's more complex, you'll have to do different things, but hard to
recommend w/o knowing in advance the exact nature of the problems.
No matter what I'd make sure to do a DBCC checkdb once the database is back
up, just to be sure.
(btw, I've found that it takes pretty bad problems to outright corrupt a SQL
2000/2005 database, so you may luck out.)
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200703/1
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||Thanks Greg. Once the hardware was repaired and we restarted the services (w
e
had complete backups available) all databases came up cleanly.
If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run after
hours, if there were errors encountered, would I still be informed, even
though I had the "WITH NO_INFOMSGS" option?
Greg D. Moore (Strider) wrote:
>[quoted text clipped - 5 lines]
>BEFORE bringing up the server, make complete backups of all files.
>Then once you bring up the server, check the logs and find out why the
>databases are suspect.
>In some cases it may be as simple as the drive letters or paths no longer
>being right and once you fix those, the database may come up cleanly.
>If it's more complex, you'll have to do different things, but hard to
>recommend w/o knowing in advance the exact nature of the problems.
>No matter what I'd make sure to do a DBCC checkdb once the database is back
>up, just to be sure.
>(btw, I've found that it takes pretty bad problems to outright corrupt a SQ
L
>2000/2005 database, so you may luck out.)
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1|||"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6ecae312206bc@.uwe...
> Thanks Greg. Once the hardware was repaired and we restarted the services
> (we
> had complete backups available) all databases came up cleanly.
>
Glad to hear it.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run
> after
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
I believe so.
>
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com|||On 06.03.2007 22:11, cbrichards via droptable.com wrote:
> Thanks Greg. Once the hardware was repaired and we restarted the services
(we
> had complete backups available) all databases came up cleanly.
> If I were to set a job to execute DBCC CHECKDB WITH NO_INFOMSGS to run aft
er
> hours, if there were errors encountered, would I still be informed, even
> though I had the "WITH NO_INFOMSGS" option?
Wouldn't it be better to run this first before using the DB again? I
mean if there were issues you'd rather want to fix them before you put
the DB back in production.
Kind regards
robertsql
Wednesday, March 21, 2012
HELP! Maintenance plan failure on ARITHABORT and QUOTED_IDENTIFIER
This has been going on for some time now. The only significant db change we
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated' I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated' I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options[/vbcol
]
have[vbcol=seagreen]
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite[vbcol=seagreen]
> SQL
> have
>|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options[vbcol=seagreen]
>sql
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated' I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated' I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options[/vbcol
]
have[vbcol=seagreen]
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite[vbcol=seagreen]
> SQL
> have
>|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options[vbcol=seagreen]
>sql
Labels:
arithabort,
bound,
creation,
database,
failure,
maintenance,
microsoft,
mysql,
oracle,
plan,
quoted_identifier,
schema,
server,
significant,
sql,
time,
time-wise,
track,
view,
wecan
HELP! Maintenance plan failure on ARITHABORT and QUOTED_IDENTIFIER
This has been going on for some time now. The only significant db change we
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated' I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
--
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated' I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> > This has been going on for some time now. The only significant db
change
> we
> > can track it to time-wise is the creation of a schema bound view for a
> > temporary project. This has since been deleted but the error continues
so
> > we don't believe there to be any relation. I include the result of our
> > maintenance plan log here. I do not understand how it got so far into
the
> > index rebuilds if the error is truly correct as these are database
options
> > not table options.
> >
> > Does anyone have any idea why these errors would be generated' I'm
quite
> > concerned. I manually rebuilt the indexes from the last table listed
> > through all other tables in the database and received no errors.
> >
> > Greatly appreciate any ideas you may have...
> >
> > [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> >
> > Rebuilding indexes for table 'atempdnrefunds'
> > Rebuilding indexes for table 'Audit1'
> > Rebuilding indexes for table 'BellevueDN2004Refunds'
> > Rebuilding indexes for table 'helpsql'
> > Rebuilding indexes for table 'IBONumbersUsed'
> > Rebuilding indexes for table 'IBOPasswords'
> > Rebuilding indexes for table 'IBOTree'
> > Rebuilding indexes for table 'IBOTreeWithNames'
> > Rebuilding indexes for table 'kateupdate'
> > Rebuilding indexes for table 'New Table'
> > Rebuilding indexes for table 'Resultss'
> > Rebuilding indexes for table 'tblAddressQueries'
> > Rebuilding indexes for table 'tblAppControl'
> > Rebuilding indexes for table 'tblAppModules'
> > Rebuilding indexes for table 'tblAttendeeLegCounter'
> > Rebuilding indexes for table 'tblBAccomodations'
> > Rebuilding indexes for table 'tblBAppHotel'
> > Rebuilding indexes for table 'tblBApplication'
> > Rebuilding indexes for table 'tblBAppLocations'
> > Rebuilding indexes for table 'tblBAttendeeMeetings'
> > Rebuilding indexes for table 'tblBAttendees'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]DBCC failed because the following SET options
> have
> > incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> >
> >
> >
>|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
--
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> > You have a table with a calculated column or possible an indexed view.
> > These need certain SET conditions to be set when you access them in
order
> > for them to work properly. The maintenance wizard can not deal
correctly
> > with those. The solution is to create your own Reindex job that has the
> > settings properly set.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> > news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> > > This has been going on for some time now. The only significant db
> change
> > we
> > > can track it to time-wise is the creation of a schema bound view for a
> > > temporary project. This has since been deleted but the error
continues
> so
> > > we don't believe there to be any relation. I include the result of
our
> > > maintenance plan log here. I do not understand how it got so far into
> the
> > > index rebuilds if the error is truly correct as these are database
> options
> > > not table options.
> > >
> > > Does anyone have any idea why these errors would be generated' I'm
> quite
> > > concerned. I manually rebuilt the indexes from the last table listed
> > > through all other tables in the database and received no errors.
> > >
> > > Greatly appreciate any ideas you may have...
> > >
> > > [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> > >
> > > Rebuilding indexes for table 'atempdnrefunds'
> > > Rebuilding indexes for table 'Audit1'
> > > Rebuilding indexes for table 'BellevueDN2004Refunds'
> > > Rebuilding indexes for table 'helpsql'
> > > Rebuilding indexes for table 'IBONumbersUsed'
> > > Rebuilding indexes for table 'IBOPasswords'
> > > Rebuilding indexes for table 'IBOTree'
> > > Rebuilding indexes for table 'IBOTreeWithNames'
> > > Rebuilding indexes for table 'kateupdate'
> > > Rebuilding indexes for table 'New Table'
> > > Rebuilding indexes for table 'Resultss'
> > > Rebuilding indexes for table 'tblAddressQueries'
> > > Rebuilding indexes for table 'tblAppControl'
> > > Rebuilding indexes for table 'tblAppModules'
> > > Rebuilding indexes for table 'tblAttendeeLegCounter'
> > > Rebuilding indexes for table 'tblBAccomodations'
> > > Rebuilding indexes for table 'tblBAppHotel'
> > > Rebuilding indexes for table 'tblBApplication'
> > > Rebuilding indexes for table 'tblBAppLocations'
> > > Rebuilding indexes for table 'tblBAttendeeMeetings'
> > > Rebuilding indexes for table 'tblBAttendees'
> > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC
> > SQL
> > > Server Driver][SQL Server]DBCC failed because the following SET
options
> > have
> > > incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> > >
> > >
> > >
> >
> >
>
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated' I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
--
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated' I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> > This has been going on for some time now. The only significant db
change
> we
> > can track it to time-wise is the creation of a schema bound view for a
> > temporary project. This has since been deleted but the error continues
so
> > we don't believe there to be any relation. I include the result of our
> > maintenance plan log here. I do not understand how it got so far into
the
> > index rebuilds if the error is truly correct as these are database
options
> > not table options.
> >
> > Does anyone have any idea why these errors would be generated' I'm
quite
> > concerned. I manually rebuilt the indexes from the last table listed
> > through all other tables in the database and received no errors.
> >
> > Greatly appreciate any ideas you may have...
> >
> > [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> >
> > Rebuilding indexes for table 'atempdnrefunds'
> > Rebuilding indexes for table 'Audit1'
> > Rebuilding indexes for table 'BellevueDN2004Refunds'
> > Rebuilding indexes for table 'helpsql'
> > Rebuilding indexes for table 'IBONumbersUsed'
> > Rebuilding indexes for table 'IBOPasswords'
> > Rebuilding indexes for table 'IBOTree'
> > Rebuilding indexes for table 'IBOTreeWithNames'
> > Rebuilding indexes for table 'kateupdate'
> > Rebuilding indexes for table 'New Table'
> > Rebuilding indexes for table 'Resultss'
> > Rebuilding indexes for table 'tblAddressQueries'
> > Rebuilding indexes for table 'tblAppControl'
> > Rebuilding indexes for table 'tblAppModules'
> > Rebuilding indexes for table 'tblAttendeeLegCounter'
> > Rebuilding indexes for table 'tblBAccomodations'
> > Rebuilding indexes for table 'tblBAppHotel'
> > Rebuilding indexes for table 'tblBApplication'
> > Rebuilding indexes for table 'tblBAppLocations'
> > Rebuilding indexes for table 'tblBAttendeeMeetings'
> > Rebuilding indexes for table 'tblBAttendees'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]DBCC failed because the following SET options
> have
> > incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> >
> >
> >
>|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
--
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> > You have a table with a calculated column or possible an indexed view.
> > These need certain SET conditions to be set when you access them in
order
> > for them to work properly. The maintenance wizard can not deal
correctly
> > with those. The solution is to create your own Reindex job that has the
> > settings properly set.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> > news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> > > This has been going on for some time now. The only significant db
> change
> > we
> > > can track it to time-wise is the creation of a schema bound view for a
> > > temporary project. This has since been deleted but the error
continues
> so
> > > we don't believe there to be any relation. I include the result of
our
> > > maintenance plan log here. I do not understand how it got so far into
> the
> > > index rebuilds if the error is truly correct as these are database
> options
> > > not table options.
> > >
> > > Does anyone have any idea why these errors would be generated' I'm
> quite
> > > concerned. I manually rebuilt the indexes from the last table listed
> > > through all other tables in the database and received no errors.
> > >
> > > Greatly appreciate any ideas you may have...
> > >
> > > [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> > >
> > > Rebuilding indexes for table 'atempdnrefunds'
> > > Rebuilding indexes for table 'Audit1'
> > > Rebuilding indexes for table 'BellevueDN2004Refunds'
> > > Rebuilding indexes for table 'helpsql'
> > > Rebuilding indexes for table 'IBONumbersUsed'
> > > Rebuilding indexes for table 'IBOPasswords'
> > > Rebuilding indexes for table 'IBOTree'
> > > Rebuilding indexes for table 'IBOTreeWithNames'
> > > Rebuilding indexes for table 'kateupdate'
> > > Rebuilding indexes for table 'New Table'
> > > Rebuilding indexes for table 'Resultss'
> > > Rebuilding indexes for table 'tblAddressQueries'
> > > Rebuilding indexes for table 'tblAppControl'
> > > Rebuilding indexes for table 'tblAppModules'
> > > Rebuilding indexes for table 'tblAttendeeLegCounter'
> > > Rebuilding indexes for table 'tblBAccomodations'
> > > Rebuilding indexes for table 'tblBAppHotel'
> > > Rebuilding indexes for table 'tblBApplication'
> > > Rebuilding indexes for table 'tblBAppLocations'
> > > Rebuilding indexes for table 'tblBAttendeeMeetings'
> > > Rebuilding indexes for table 'tblBAttendees'
> > > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC
> > SQL
> > > Server Driver][SQL Server]DBCC failed because the following SET
options
> > have
> > > incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> > >
> > >
> > >
> >
> >
>
Labels:
arithabort,
bound,
creation,
database,
failure,
maintenance,
microsoft,
mysql,
oracle,
plan,
quoted_identifier,
schema,
server,
significant,
sql,
time,
time-wise,
track,
view
HELP! Maintenance plan failure on ARITHABORT and QUOTED_IDENTIFIER
This has been going on for some time now. The only significant db change we
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated? I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated? I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>
|||You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated? I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>
|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite
> SQL
> have
>
|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite
> SQL
> have
>
|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options
>
|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options
>
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated? I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated? I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>
|||You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated? I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options
have
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>
|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite
> SQL
> have
>
|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite
> SQL
> have
>
|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options
>
|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options
>
Labels:
arithabort,
bound,
creation,
database,
failure,
maintenance,
microsoft,
mysql,
oracle,
plan,
quoted_identifier,
schema,
server,
significant,
sql,
time,
time-wise,
track,
view,
wecan
Friday, March 9, 2012
Help! a database can not be backed up!
Hi,
I have a 80 GB database. The backup can not be completed.
The error message were:
1. BackupMedium::ReportIoError: write failure on backup
device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.).
2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile:
d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
3. BACKUP failed to complete the command BACKUP DATABASE
[DistribuGIS] TO DISK = N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
NOSKIP , STATS = 10, NOFORMAT
I checked the disk were working fine.
I checked the database by using dbcc checkdb with
repair_rebuild option. It reported me no error found.
Please help if anything could be wrong/what should I do.
Thank you in advance.try backing up the database to a different machine that
has enough space for the database. This way you can verify
if there is something wrong with the local disk array.
>--Original Message--
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>
>.
>|||Unfortunately, since this database is big I can not try
backing up the database to a different machine.
But I have other databases in the same machine and they
all could be backed up successfully. Since this, can I say
the local disk array is ok?
Do you think this is because that the database files are
damaged?
Thank you.
>--Original Message--
>try backing up the database to a different machine that
>has enough space for the database. This way you can
verify
>if there is something wrong with the local disk array.
>
>>--Original Message--
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
>.
>|||It's the .bak backup file that's the issue, not your
database. Something else is accessing the file - are you
also running NT backup at the same time? That puts a lock on
the file. If you are always hitting the error, try just
backing up to another file name.
Filemon from www.sysinternals.com should tell you what
process has a lock on the file.
-Sue
On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>|||To ensure the database is in a good state run DBCC CHECKDB against it
--
HTH
Ryan Waight, MCDBA, MCSE
"Juan" <juan_wu@.hotmail.com> wrote in message
news:192401c3884a$93780660$a001280a@.phx.gbl...
> Unfortunately, since this database is big I can not try
> backing up the database to a different machine.
> But I have other databases in the same machine and they
> all could be backed up successfully. Since this, can I say
> the local disk array is ok?
> Do you think this is because that the database files are
> damaged?
> Thank you.
> >--Original Message--
> >try backing up the database to a different machine that
> >has enough space for the database. This way you can
> verify
> >if there is something wrong with the local disk array.
> >
> >
> >>--Original Message--
> >>Hi,
> >>
> >>I have a 80 GB database. The backup can not be
> completed.
> >>The error message were:
> >>1. BackupMedium::ReportIoError: write failure on backup
> >>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
> >>Operating system error 33(The process cannot access the
> >>file because another process has locked a portion of the
> >>file.).
> >>
> >>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
> >>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
> >>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
> >>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
> >>m_actualBytes: 0, m_errcode: 33, BackupFile:
> >>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
> >>
> >>3. BACKUP failed to complete the command BACKUP DATABASE
> >>[DistribuGIS] TO DISK => >>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
> >>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
> >>NOSKIP , STATS = 10, NOFORMAT
> >>
> >>I checked the disk were working fine.
> >>I checked the database by using dbcc checkdb with
> >>repair_rebuild option. It reported me no error found.
> >>
> >>
> >>Please help if anything could be wrong/what should I do.
> >>
> >>Thank you in advance.
> >>
> >>
> >>.
> >>
> >.
> >|||Hi,
It got backed up successfully to a different folder. But
in the meantime, I used to back it up as compressed file
since the shortage of my disk and this time I backed it up
as normal file. Do you think the compression also possibly
cause problem?
I will try the Filemon once I got a chance.
Thank you so much for your help.
--Juan
>--Original Message--
>It's the .bak backup file that's the issue, not your
>database. Something else is accessing the file - are you
>also running NT backup at the same time? That puts a lock
on
>the file. If you are always hitting the error, try just
>backing up to another file name.
>Filemon from www.sysinternals.com should tell you what
>process has a lock on the file.
>-Sue
>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>.
>|||I'm not sure Juan - I've never messed with compression for
database backups. Filemon should show you what's locking the
file though and if it's a system process, you'll see that.
It's a good tool to have and pretty easy to use.
-Sue
On Thu, 2 Oct 2003 14:01:20 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>It got backed up successfully to a different folder. But
>in the meantime, I used to back it up as compressed file
>since the shortage of my disk and this time I backed it up
>as normal file. Do you think the compression also possibly
>cause problem?
>I will try the Filemon once I got a chance.
>Thank you so much for your help.
>--Juan
>>--Original Message--
>>It's the .bak backup file that's the issue, not your
>>database. Something else is accessing the file - are you
>>also running NT backup at the same time? That puts a lock
>on
>>the file. If you are always hitting the error, try just
>>backing up to another file name.
>>Filemon from www.sysinternals.com should tell you what
>>process has a lock on the file.
>>-Sue
>>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
>><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
>completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
I have a 80 GB database. The backup can not be completed.
The error message were:
1. BackupMedium::ReportIoError: write failure on backup
device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.).
2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile:
d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
3. BACKUP failed to complete the command BACKUP DATABASE
[DistribuGIS] TO DISK = N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
NOSKIP , STATS = 10, NOFORMAT
I checked the disk were working fine.
I checked the database by using dbcc checkdb with
repair_rebuild option. It reported me no error found.
Please help if anything could be wrong/what should I do.
Thank you in advance.try backing up the database to a different machine that
has enough space for the database. This way you can verify
if there is something wrong with the local disk array.
>--Original Message--
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>
>.
>|||Unfortunately, since this database is big I can not try
backing up the database to a different machine.
But I have other databases in the same machine and they
all could be backed up successfully. Since this, can I say
the local disk array is ok?
Do you think this is because that the database files are
damaged?
Thank you.
>--Original Message--
>try backing up the database to a different machine that
>has enough space for the database. This way you can
verify
>if there is something wrong with the local disk array.
>
>>--Original Message--
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
>.
>|||It's the .bak backup file that's the issue, not your
database. Something else is accessing the file - are you
also running NT backup at the same time? That puts a lock on
the file. If you are always hitting the error, try just
backing up to another file name.
Filemon from www.sysinternals.com should tell you what
process has a lock on the file.
-Sue
On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>|||To ensure the database is in a good state run DBCC CHECKDB against it
--
HTH
Ryan Waight, MCDBA, MCSE
"Juan" <juan_wu@.hotmail.com> wrote in message
news:192401c3884a$93780660$a001280a@.phx.gbl...
> Unfortunately, since this database is big I can not try
> backing up the database to a different machine.
> But I have other databases in the same machine and they
> all could be backed up successfully. Since this, can I say
> the local disk array is ok?
> Do you think this is because that the database files are
> damaged?
> Thank you.
> >--Original Message--
> >try backing up the database to a different machine that
> >has enough space for the database. This way you can
> verify
> >if there is something wrong with the local disk array.
> >
> >
> >>--Original Message--
> >>Hi,
> >>
> >>I have a 80 GB database. The backup can not be
> completed.
> >>The error message were:
> >>1. BackupMedium::ReportIoError: write failure on backup
> >>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
> >>Operating system error 33(The process cannot access the
> >>file because another process has locked a portion of the
> >>file.).
> >>
> >>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
> >>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
> >>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
> >>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
> >>m_actualBytes: 0, m_errcode: 33, BackupFile:
> >>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
> >>
> >>3. BACKUP failed to complete the command BACKUP DATABASE
> >>[DistribuGIS] TO DISK => >>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
> >>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
> >>NOSKIP , STATS = 10, NOFORMAT
> >>
> >>I checked the disk were working fine.
> >>I checked the database by using dbcc checkdb with
> >>repair_rebuild option. It reported me no error found.
> >>
> >>
> >>Please help if anything could be wrong/what should I do.
> >>
> >>Thank you in advance.
> >>
> >>
> >>.
> >>
> >.
> >|||Hi,
It got backed up successfully to a different folder. But
in the meantime, I used to back it up as compressed file
since the shortage of my disk and this time I backed it up
as normal file. Do you think the compression also possibly
cause problem?
I will try the Filemon once I got a chance.
Thank you so much for your help.
--Juan
>--Original Message--
>It's the .bak backup file that's the issue, not your
>database. Something else is accessing the file - are you
>also running NT backup at the same time? That puts a lock
on
>the file. If you are always hitting the error, try just
>backing up to another file name.
>Filemon from www.sysinternals.com should tell you what
>process has a lock on the file.
>-Sue
>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>.
>|||I'm not sure Juan - I've never messed with compression for
database backups. Filemon should show you what's locking the
file though and if it's a system process, you'll see that.
It's a good tool to have and pretty easy to use.
-Sue
On Thu, 2 Oct 2003 14:01:20 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>It got backed up successfully to a different folder. But
>in the meantime, I used to back it up as compressed file
>since the shortage of my disk and this time I backed it up
>as normal file. Do you think the compression also possibly
>cause problem?
>I will try the Filemon once I got a chance.
>Thank you so much for your help.
>--Juan
>>--Original Message--
>>It's the .bak backup file that's the issue, not your
>>database. Something else is accessing the file - are you
>>also running NT backup at the same time? That puts a lock
>on
>>the file. If you are always hitting the error, try just
>>backing up to another file name.
>>Filemon from www.sysinternals.com should tell you what
>>process has a lock on the file.
>>-Sue
>>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
>><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
>completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
Subscribe to:
Posts (Atom)