We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........
Showing posts with label directly. Show all posts
Showing posts with label directly. Show all posts
Monday, March 19, 2012
HELP! I/O error (torn page) when attaching mdf and ldf files
We are using cloning software to directly backup the mdf and ldf files. I a
m
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........
m
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........
HELP! I/O error (torn page) when attaching mdf and ldf files
We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........
Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........
Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........
Friday, February 24, 2012
Help with weird error
I am working with Access frontends and a SQL Server 2000 backend.
One user gets the following error when trying to insert directly into
a table through access or through a form into that same table: "String
or binary data would be truncated". It doesn't matter into which type
of column the data is entered. Int, datetime, varchar all produce the
same error.
This user has access to the db this table is stored in and can write
to other tables in that db with no problem. In fact, none of the other
users with the same permission settings to this db has this problem.
They can insert into or update this same table just fine.
This is also pc independent for this user. It does seem to be a matter
of account setting though, because none of the other users has this
problem.
What could be wrong? Does anybody have any ideas? As far as I know
this user has the exact same permission setting as others. What else
could I look into to solve this mystery?
Thanks for your help.> One user gets the following error when trying to insert directly into
> a table through access or through a form into that same table: "String
> or binary data would be truncated".
This sounds like a string is attempting to be inserted but it is too long to
fit in the column. This is not a "weird" error, in fact it is quite common.
I highly doubt it has anything to do with this user or his/her permissions,
unless there is a trigger on the table and the failure is occurring because
his domain username is too long to fit into the auditing table.|||I fixed the problem. As it turned out, for this particular user the
username is saved with its domain name. The table field to which this
user info is saved wasn't large enough to hold both the username and
domain name.
Thanks for your reply, Aaron. As you predicted, the username was too
long to be stored.
On Mar 11, 9:33 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> > One user gets the following error when trying to insert directly into
> > a table through access or through a form into that same table: "String
> > or binary data would be truncated".
> This sounds like a string is attempting to be inserted but it is too long to
> fit in the column. This is not a "weird" error, in fact it is quite common.
> I highly doubt it has anything to do with this user or his/her permissions,
> unless there is a trigger on the table and the failure is occurring because
> his domain username is too long to fit into the auditing table.
One user gets the following error when trying to insert directly into
a table through access or through a form into that same table: "String
or binary data would be truncated". It doesn't matter into which type
of column the data is entered. Int, datetime, varchar all produce the
same error.
This user has access to the db this table is stored in and can write
to other tables in that db with no problem. In fact, none of the other
users with the same permission settings to this db has this problem.
They can insert into or update this same table just fine.
This is also pc independent for this user. It does seem to be a matter
of account setting though, because none of the other users has this
problem.
What could be wrong? Does anybody have any ideas? As far as I know
this user has the exact same permission setting as others. What else
could I look into to solve this mystery?
Thanks for your help.> One user gets the following error when trying to insert directly into
> a table through access or through a form into that same table: "String
> or binary data would be truncated".
This sounds like a string is attempting to be inserted but it is too long to
fit in the column. This is not a "weird" error, in fact it is quite common.
I highly doubt it has anything to do with this user or his/her permissions,
unless there is a trigger on the table and the failure is occurring because
his domain username is too long to fit into the auditing table.|||I fixed the problem. As it turned out, for this particular user the
username is saved with its domain name. The table field to which this
user info is saved wasn't large enough to hold both the username and
domain name.
Thanks for your reply, Aaron. As you predicted, the username was too
long to be stored.
On Mar 11, 9:33 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> > One user gets the following error when trying to insert directly into
> > a table through access or through a form into that same table: "String
> > or binary data would be truncated".
> This sounds like a string is attempting to be inserted but it is too long to
> fit in the column. This is not a "weird" error, in fact it is quite common.
> I highly doubt it has anything to do with this user or his/her permissions,
> unless there is a trigger on the table and the failure is occurring because
> his domain username is too long to fit into the auditing table.
Help with weird error
I am working with Access frontends and a SQL Server 2000 backend.
One user gets the following error when trying to insert directly into
a table through access or through a form into that same table: "String
or binary data would be truncated". It doesn't matter into which type
of column the data is entered. Int, datetime, varchar all produce the
same error.
This user has access to the db this table is stored in and can write
to other tables in that db with no problem. In fact, none of the other
users with the same permission settings to this db has this problem.
They can insert into or update this same table just fine.
This is also pc independent for this user. It does seem to be a matter
of account setting though, because none of the other users has this
problem.
What could be wrong? Does anybody have any ideas? As far as I know
this user has the exact same permission setting as others. What else
could I look into to solve this mystery?
Thanks for your help.
> One user gets the following error when trying to insert directly into
> a table through access or through a form into that same table: "String
> or binary data would be truncated".
This sounds like a string is attempting to be inserted but it is too long to
fit in the column. This is not a "weird" error, in fact it is quite common.
I highly doubt it has anything to do with this user or his/her permissions,
unless there is a trigger on the table and the failure is occurring because
his domain username is too long to fit into the auditing table.
|||I fixed the problem. As it turned out, for this particular user the
username is saved with its domain name. The table field to which this
user info is saved wasn't large enough to hold both the username and
domain name.
Thanks for your reply, Aaron. As you predicted, the username was too
long to be stored.
On Mar 11, 9:33 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> This sounds like a string is attempting to be inserted but it is too long to
> fit in the column. This is not a "weird" error, in fact it is quite common.
> I highly doubt it has anything to do with this user or his/her permissions,
> unless there is a trigger on the table and the failure is occurring because
> his domain username is too long to fit into the auditing table.
One user gets the following error when trying to insert directly into
a table through access or through a form into that same table: "String
or binary data would be truncated". It doesn't matter into which type
of column the data is entered. Int, datetime, varchar all produce the
same error.
This user has access to the db this table is stored in and can write
to other tables in that db with no problem. In fact, none of the other
users with the same permission settings to this db has this problem.
They can insert into or update this same table just fine.
This is also pc independent for this user. It does seem to be a matter
of account setting though, because none of the other users has this
problem.
What could be wrong? Does anybody have any ideas? As far as I know
this user has the exact same permission setting as others. What else
could I look into to solve this mystery?
Thanks for your help.
> One user gets the following error when trying to insert directly into
> a table through access or through a form into that same table: "String
> or binary data would be truncated".
This sounds like a string is attempting to be inserted but it is too long to
fit in the column. This is not a "weird" error, in fact it is quite common.
I highly doubt it has anything to do with this user or his/her permissions,
unless there is a trigger on the table and the failure is occurring because
his domain username is too long to fit into the auditing table.
|||I fixed the problem. As it turned out, for this particular user the
username is saved with its domain name. The table field to which this
user info is saved wasn't large enough to hold both the username and
domain name.
Thanks for your reply, Aaron. As you predicted, the username was too
long to be stored.
On Mar 11, 9:33 am, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> This sounds like a string is attempting to be inserted but it is too long to
> fit in the column. This is not a "weird" error, in fact it is quite common.
> I highly doubt it has anything to do with this user or his/her permissions,
> unless there is a trigger on the table and the failure is occurring because
> his domain username is too long to fit into the auditing table.
Subscribe to:
Posts (Atom)