?
Solved

ALTER INDEX command fails during Maintenance Plan - SQL Server 2005

Posted on 2010-08-16
5
Medium Priority
?
1,057 Views
Last Modified: 2012-05-10
Hi,

During the execution of maintenance plan, it rebuilds the indexes on the tables.  An ALTER INDEX command is executed, but the command stalled and hung the maintenance job.  Error that was reported in the log said it failed (see the error message below).

I am not sure what to do with this error or how to fix the error.  Appears to be a problem with the index [a215_ix1_a]  being used for the table [a255].

What could I do to resolve the error?

Rebuild Index (TOMLINSON)
Rebuild index on Local server connection
Databases: pbtf_ArcSDE
Object: Tables and views
Original amount of free space
Task start: 2010-08-16T10:17:13.
Task end: 2010-08-16T12:18:07.
Failed:(-1073548784) Executing the query "ALTER INDEX [a215_ix1_a] ON [cf_pbtf].[a255] REBUILD WITH ( PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "A severe error occurred on the current command.  The results, if any, should be discarded.
A severe error occurred on the current command.  The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Open in new window

0
Comment
Question by:gtrapp
  • 3
5 Comments
 
LVL 7

Assisted Solution

by:lundnak
lundnak earned 150 total points
ID: 33450085
Did you receive any errors in the SQL Server error log at around 12:18:07.  If so, could you post them?
0
 

Author Comment

by:gtrapp
ID: 33450270
No errors in the SQL Server log and nothing in the Event View.

Is there something that I could do with the index or the table?
0
 
LVL 8

Accepted Solution

by:
dba2dba earned 1350 total points
ID: 33451282
The error message you see is a generic error. I have received similar error with a backup failure due to space issues.

Did you check the log space in the database while the index rebuild is executing, please check it using dbcc sqlperf while the job runs and ensure that the log has enough space for index rebuild.

You can also use an output file in the maintenance plan job properties, it might log additional details when it fails. Also, you could try running the alter index command in the error in Management Studio, to see if you get any errors.

Thanks.
0
 

Author Comment

by:gtrapp
ID: 33458870
I checked the log file size during the execution of the job and the size showed the usage was only 2%. 1.5 GB was available.

What I did to solve the problem was restart the ArcSDE service. Then, the backup completed successfully.
0
 

Author Closing Comment

by:gtrapp
ID: 33458892
I restarted the service and clearned out locks on tables and objects in the database and that cleared the problem.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've encountered valid database schemas that do not have a primary key.  For example, I use LogParser from Microsoft to push IIS logs into a SQL database table for processing and analysis.  However, occasionally due to user error or a scheduled task…
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question