Hi all,
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lotOK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/default.aspx?scid=kb;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:
> > Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
> > [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> > Expression: spaceContig >= Align (spaceNeeded)
> > SPID: 54
> > Process ID: 1284
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:
> OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should not
> be in the product. I never check this option. I want to know if there is a
> problem so I can schedule a fix during non-peak times. I also want to know
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics and
> do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/default.aspx?scid=kb;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> > Hi all,
> > I'm Jose and first of all excuse my english:
> >
> > I have many problems with "Plan de mantenimiento de SQL" often when the
> > "Plan de mantenimiento" begin, have an errors during the reindex how:
> > Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
> > [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
> SQL
> > Server Driver][SQL Server]
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> > Expression: spaceContig >= Align (spaceNeeded)
> > SPID: 54
> > Process ID: 1284
> >
> > then marked how suspicous and can repair automatically, but when erros
> like
> > that occur for 4 or 5 times the database can't repair automatically and
> the
> > client lost data.
> >
> > W2K SP4 and SQL SP3
> >
> > Thanks a lot
> >
>
>|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last
> error that I wrote you:
> > > Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
> > > [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
[Microsoft][ODBC
> > SQL
> > > Server Driver][SQL Server]
> > > [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> > > Expression: spaceContig >= Align (spaceNeeded)
> > > SPID: 54
> > > Process ID: 1284
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
> > OK, I understand a little 'Spanglish'. If I read correctly, you have
chosen
> > the 'Repair minor problems Automatically' option in your Maintenance
plans
> > ("Plan de mantenimiento de SQL" ). The repair tried and failed and
marked
> > the database suspect.
> >
> > First, this repair automatically option a bad idea and I think it should
not
> > be in the product. I never check this option. I want to know if there
is a
> > problem so I can schedule a fix during non-peak times. I also want to
know
> > so I can find what is causing the error.
> >
> > The good news is you may be OK. the ws_indexes are actually statistics
and
> > do not directly impact the data. Look at 'Resetting Suspect Status' in
BOL
> > (Books On-Line). This may let you extract your data and recreate the
> > database.
> >
> > This KB Article may help if nothing else works.
> >
> > INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;165918
> >
> > Good Luck.
> >
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> > news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> > > Hi all,
> > > I'm Jose and first of all excuse my english:
> > >
> > > I have many problems with "Plan de mantenimiento de SQL" often when
the
> > > "Plan de mantenimiento" begin, have an errors during the reindex how:
> > > Reconstruyendo los ¡ndices de la tabla 'ws_Albaranes_Lineas'
> > > [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
[Microsoft][ODBC
> > SQL
> > > Server Driver][SQL Server]
> > > [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> > > Expression: spaceContig >= Align (spaceNeeded)
> > > SPID: 54
> > > Process ID: 1284
> > >
> > > then marked how suspicous and can repair automatically, but when erros
> > like
> > > that occur for 4 or 5 times the database can't repair automatically
and
> > the
> > > client lost data.
> > >
> > > W2K SP4 and SQL SP3
> > >
> > > Thanks a lot
> > >
> >
> >
> >sql
Showing posts with label base. Show all posts
Showing posts with label base. Show all posts
Monday, March 26, 2012
error index data base
Hi all,
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ?ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lot
OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/default...b;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>
|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:[vbcol=seagreen]
> SQL
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:
> OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should not
> be in the product. I never check this option. I want to know if there is a
> problem so I can schedule a fix during non-peak times. I also want to know
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics and
> do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/default...b;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> SQL
> like
> the
>
>
|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last[vbcol=seagreen]
> error that I wrote you:
[Microsoft][ODBC[vbcol=seagreen]
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
chosen[vbcol=seagreen]
plans[vbcol=seagreen]
marked[vbcol=seagreen]
not[vbcol=seagreen]
is a[vbcol=seagreen]
know[vbcol=seagreen]
and[vbcol=seagreen]
BOL[vbcol=seagreen]
the[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
and[vbcol=seagreen]
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ?ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lot
OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/default...b;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODBC
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>
|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:[vbcol=seagreen]
> SQL
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:
> OK, I understand a little 'Spanglish'. If I read correctly, you have chosen
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should not
> be in the product. I never check this option. I want to know if there is a
> problem so I can schedule a fix during non-peak times. I also want to know
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics and
> do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/default...b;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> SQL
> like
> the
>
>
|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last[vbcol=seagreen]
> error that I wrote you:
[Microsoft][ODBC[vbcol=seagreen]
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
chosen[vbcol=seagreen]
plans[vbcol=seagreen]
marked[vbcol=seagreen]
not[vbcol=seagreen]
is a[vbcol=seagreen]
know[vbcol=seagreen]
and[vbcol=seagreen]
BOL[vbcol=seagreen]
the[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
and[vbcol=seagreen]
error index data base
Hi all,
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ?ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.c
pp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lotOK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/defaul...kb;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.
cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:
> SQL
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> OK, I understand a little 'Spanglish'. If I read correctly, you have chos
en
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should n
ot
> be in the product. I never check this option. I want to know if there is
a
> problem so I can schedule a fix during non-peak times. I also want to kno
w
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics an
d
> do not directly impact the data. Look at 'Resetting Suspect Status' in BO
L
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/defaul...kb;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> SQL
> like
> the
>
>|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last[vbcol=seagreen]
> error that I wrote you:
[Microsoft][ODBC[vbcol=seagreen]
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
>
chosen[vbcol=seagreen]
plans[vbcol=seagreen]
marked[vbcol=seagreen]
not[vbcol=seagreen]
is a[vbcol=seagreen]
know[vbcol=seagreen]
and[vbcol=seagreen]
BOL[vbcol=seagreen]
the[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
and[vbcol=seagreen]
I'm Jose and first of all excuse my english:
I have many problems with "Plan de mantenimiento de SQL" often when the
"Plan de mantenimiento" begin, have an errors during the reindex how:
Reconstruyendo los ?ndices de la tabla 'ws_Albaranes_Lineas'
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.c
pp:2831
Expression: spaceContig >= Align (spaceNeeded)
SPID: 54
Process ID: 1284
then marked how suspicous and can repair automatically, but when erros like
that occur for 4 or 5 times the database can't repair automatically and the
client lost data.
W2K SP4 and SQL SP3
Thanks a lotOK, I understand a little 'Spanglish'. If I read correctly, you have chosen
the 'Repair minor problems Automatically' option in your Maintenance plans
("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
the database suspect.
First, this repair automatically option a bad idea and I think it should not
be in the product. I never check this option. I want to know if there is a
problem so I can schedule a fix during non-peak times. I also want to know
so I can find what is causing the error.
The good news is you may be OK. the ws_indexes are actually statistics and
do not directly impact the data. Look at 'Resetting Suspect Status' in BOL
(Books On-Line). This may let you extract your data and recreate the
database.
This KB Article may help if nothing else works.
INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
http://support.microsoft.com/defaul...kb;en-us;165918
Good Luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> Hi all,
> I'm Jose and first of all excuse my english:
> I have many problems with "Plan de mantenimiento de SQL" often when the
> "Plan de mantenimiento" begin, have an errors during the reindex how:
> Reconstruyendo los ndices de la tabla 'ws_Albaranes_Lineas'
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]
> [Microsoft][ODBC SQL Server Driver][SQL Server]Location: page.
cpp:2831
> Expression: spaceContig >= Align (spaceNeeded)
> SPID: 54
> Process ID: 1284
> then marked how suspicous and can repair automatically, but when erros
like
> that occur for 4 or 5 times the database can't repair automatically and
the
> client lost data.
> W2K SP4 and SQL SP3
> Thanks a lot
>|||Hi again:
If I undestand, the correct option is: no marked the option "Repair minor
problems Automatically" but when the maintenance plans fail, always fail
during the reindex, The question is: Why reindex fail? For example the last
error that I wrote you:
> SQL
Do you think I needn't reindex database?
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> OK, I understand a little 'Spanglish'. If I read correctly, you have chos
en
> the 'Repair minor problems Automatically' option in your Maintenance plans
> ("Plan de mantenimiento de SQL" ). The repair tried and failed and marked
> the database suspect.
> First, this repair automatically option a bad idea and I think it should n
ot
> be in the product. I never check this option. I want to know if there is
a
> problem so I can schedule a fix during non-peak times. I also want to kno
w
> so I can find what is causing the error.
> The good news is you may be OK. the ws_indexes are actually statistics an
d
> do not directly impact the data. Look at 'Resetting Suspect Status' in BO
L
> (Books On-Line). This may let you extract your data and recreate the
> database.
> This KB Article may help if nothing else works.
> INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
> http://support.microsoft.com/defaul...kb;en-us;165918
> Good Luck.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
> news:7592A326-4D93-4439-8BAB-1E95056C4809@.microsoft.com...
> SQL
> like
> the
>
>|||I understand. It failed during a reindex. Reindexing is a good thing.
Continue to reindex.
Make sure your database has enough free space to reindex. Do not
auto-shrink the database. Manually add the space rather than relying on
auto-grow. Run DBCC CHECKDB to make sure your database is error free. You
may have to run further DBCC commands to fix it. Always make sure you have
a backup before attempting repairs.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:2E29E2B7-0A30-4CFD-937F-CCAABEDDBDB0@.microsoft.com...
> Hi again:
> If I undestand, the correct option is: no marked the option "Repair minor
> problems Automatically" but when the maintenance plans fail, always fail
> during the reindex, The question is: Why reindex fail? For example the
last[vbcol=seagreen]
> error that I wrote you:
[Microsoft][ODBC[vbcol=seagreen]
> Do you think I needn't reindex database?
> "Geoff N. Hiten" wrote:
>
chosen[vbcol=seagreen]
plans[vbcol=seagreen]
marked[vbcol=seagreen]
not[vbcol=seagreen]
is a[vbcol=seagreen]
know[vbcol=seagreen]
and[vbcol=seagreen]
BOL[vbcol=seagreen]
the[vbcol=seagreen]
[Microsoft][ODBC[vbcol=seagreen]
and[vbcol=seagreen]
Monday, March 19, 2012
Error in scheduled back up
I've been pulling my hair over this message in my daily backup log...
I found an article for this error message in knowledge base (274743), and it
has something to do with SMS database. But we do not use SMS. So, I don't
know how to solve this problem...
This error moves around every day... sometimes Master doesn't get backed up
, sometimes model...
I'm not 100% sure, but maybe it started after I started to run optimization
job...
I'd appreciate any help on this... Thank you!
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]Backup, CHECKALLOC, bulk copy, SEL
ECT INTO, and file manipulation (such as CREATE FILE) operations on a databa
se must be serialized. Reissue the statemen
t after the current backup, CHECKALLOC, or file manipulation operation is co
mpleted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore
operation terminating abnormally.The error is from some other operation such as those listed,
was running when you executed the backup.
The optimizations option does have some activities that
would prohibit a backup at the same time as when that part
of the plan is run - e.g. the option to remove unused space
just does a dbcc shrinkdatabase and you can't run this and a
backup at the same time.
The best way to solve it is to just write your own jobs to
perform your maintenance. This allows a lot more control,
flexibility with your database maintenance.
-Sue
On Mon, 29 Mar 2004 15:26:08 -0800, "Amy Miller"
<amiller1@.sonomacourt.org> wrote:
>I've been pulling my hair over this message in my daily backup log...
>I found an article for this error message in knowledge base (274743), and i
t has something to do with SMS database. But we do not use SMS. So, I don'
t know how to solve this problem...
>This error moves around every day... sometimes Master doesn't get backed u
p, sometimes model...
>I'm not 100% sure, but maybe it started after I started to run optimization
job...
>I'd appreciate any help on this... Thank you!
>[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023: [Microsoft][ODBC
SQL Server Driver][SQL Server]Backup, CHECKALLOC, bulk copy, SELECT INTO, and f
ile manipulation (such as CREATE FILE) operations on a database must be serialized.
Reissue the stateme
nt after the current backup, CHECKALLOC, or file manipulation operation is completed.[color
=darkred]
>[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operat
ion terminating abnormally.[/color]
I found an article for this error message in knowledge base (274743), and it
has something to do with SMS database. But we do not use SMS. So, I don't
know how to solve this problem...
This error moves around every day... sometimes Master doesn't get backed up
, sometimes model...
I'm not 100% sure, but maybe it started after I started to run optimization
job...
I'd appreciate any help on this... Thank you!
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]Backup, CHECKALLOC, bulk copy, SEL
ECT INTO, and file manipulation (such as CREATE FILE) operations on a databa
se must be serialized. Reissue the statemen
t after the current backup, CHECKALLOC, or file manipulation operation is co
mpleted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore
operation terminating abnormally.The error is from some other operation such as those listed,
was running when you executed the backup.
The optimizations option does have some activities that
would prohibit a backup at the same time as when that part
of the plan is run - e.g. the option to remove unused space
just does a dbcc shrinkdatabase and you can't run this and a
backup at the same time.
The best way to solve it is to just write your own jobs to
perform your maintenance. This allows a lot more control,
flexibility with your database maintenance.
-Sue
On Mon, 29 Mar 2004 15:26:08 -0800, "Amy Miller"
<amiller1@.sonomacourt.org> wrote:
>I've been pulling my hair over this message in my daily backup log...
>I found an article for this error message in knowledge base (274743), and i
t has something to do with SMS database. But we do not use SMS. So, I don'
t know how to solve this problem...
>This error moves around every day... sometimes Master doesn't get backed u
p, sometimes model...
>I'm not 100% sure, but maybe it started after I started to run optimization
job...
>I'd appreciate any help on this... Thank you!
>[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3023: [Microsoft][ODBC
SQL Server Driver][SQL Server]Backup, CHECKALLOC, bulk copy, SELECT INTO, and f
ile manipulation (such as CREATE FILE) operations on a database must be serialized.
Reissue the stateme
nt after the current backup, CHECKALLOC, or file manipulation operation is completed.[color
=darkred]
>[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operat
ion terminating abnormally.[/color]
Friday, March 9, 2012
error in installing hot fix
i installed an service pack 2
Quick Details
the above installation , i was success. but the version is 9.00.3042. so what i did was i stalled the hot fix , http://support.microsoft.com/kb/933097
but this hox fis installation is success for all, but it failed for database services with below error message :
product Installation Status
Product : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 3152
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB933097_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
now i don't know what to do...
i don't want to uninstall sqlserver 2005 and redo the whole thing...
because thisd is my first assinment in the new job and if i redo the whole thing then it won't be good since it'll take 1 week..
is there any way i can solve this issue?
A Knowledge Based article has been published explaining the problem and workaround:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;918695
Please let us know if this article does not address your problem.
Thanks,
Sam Lester (MSFT)
the above kb is the issue with sp1
Wednesday, March 7, 2012
error in installing hot fix
i installed an service pack 2
Quick Details
the above installation , i was success. but the version is 9.00.3042. so what i did was i stalled the hot fix , http://support.microsoft.com/kb/933097
but this hox fis installation is success for all, but it failed for database services with below error message :
product Installation Status
Product : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 3152
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB933097_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
now i don't know what to do...
i don't want to uninstall sqlserver 2005 and redo the whole thing...
because thisd is my first assinment in the new job and if i redo the whole thing then it won't be good since it'll take 1 week..
is there any way i can solve this issue?
A Knowledge Based article has been published explaining the problem and workaround:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;918695
Please let us know if this article does not address your problem.
Thanks,
Sam Lester (MSFT)
the above kb is the issue with sp1
Subscribe to:
Posts (Atom)