Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Friday, March 30, 2012

Maintenance Plan for SQL Server 2005 64-bit doesn't work!

Hi all,
We have a SQL Server 2005 64-bit, and recently I upgrade from build 3042 to 3054 and I try to do a maintenance plan for transaction logs(TL) backup, including cleanup for two days (have full backup every night).

Problem I have is that I want the TL files to dump in a different location(due to disk space), so I put in the UNC path in the "Create a backup file for every database - >Folder:\\FileServer\TL\DBLogs"

NB: if using the local drives, it work

Check List
Security:
- The account that I used to create the plan is an sa account
- The location that I dump the TL files, I have full access to the folder

SQL Statement:
exec xp_cmdshell 'dir \FileServer\TL\DBLogs' (it list all files)

Is this a bug for 64-bit? because I can do this on SQL Server 2005 32-bit and it's work perfectly

Resolved: permission problems, u need to give permission to the folder for SQL Server Agent account

maintenance plan fails after upgrade to 2000

We upgraded to sql 2000 last night and now the maintenance
plans do not work. I'm using simple model, no tlog backup.
The error I'm working with is this:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The
step failed.
The log looks like this:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server '1s' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'DB Maintenance Plan1' on
7/31/2003 2:00:02 AM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database
state cannot be changed while other users are using the
database 'r'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER
DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption
command failed.
[1] Database rbcs: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
** Execution Time: 0 hrs, 0 mins, 1 secs **
[2] Database t: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 2 secs **
[3] Database r: Database Backup...
The backup was not performed since data verification
errors were found.
[4] Database t: Database Backup...
Destination: [D:\mssql7\BACKUP\t\t_db_200307310200.BAK]
** Execution Time: 0 hrs, 0 mins, 14 secs **
[5] Database t: Verifying Backup...
** Execution Time: 0 hrs, 0 mins, 5 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan1' on
7/31/2003 2:00:23 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)D
You are geting this error because the maintenance plan is
trying to put the database into single user mode. It fails
because there is a user (or at least an open transaction)
in the database. It is attempting to do this so it can
perform a dbcc checkdb with repair.
If this worked before, perhaps something in the upgrade
has lead to open transactions? Or have you changed the
time the job runs?
If you change the dbcc part of the maint plan, not to do
the repair it would not try to put the database into
single user mode. Check the output from your dbcc checkdb
and if you find you do need to run with repair, schedule a
job to run at a time when you can switch to single user
mode.
Hope this helps
John|||The plan was setup under sql 7 so I guess there wasnt a
problem in that version. I will remove the repair option,
but I suppose I'll have to run dbcc later.
Thanks
>--Original Message--
>D
>You are geting this error because the maintenance plan is
>trying to put the database into single user mode. It
fails
>because there is a user (or at least an open transaction)
>in the database. It is attempting to do this so it can
>perform a dbcc checkdb with repair.
>If this worked before, perhaps something in the upgrade
>has lead to open transactions? Or have you changed the
>time the job runs?
>If you change the dbcc part of the maint plan, not to do
>the repair it would not try to put the database into
>single user mode. Check the output from your dbcc checkdb
>and if you find you do need to run with repair, schedule
a
>job to run at a time when you can switch to single user
>mode.
>Hope this helps
>John
>.
>

Monday, March 26, 2012

Maintenance Plan after upgrade

Okay... here's my issue

I got a Win2k3/SP1 server, where I used to have SQL 2000 on it, upgraded to SQL 2005/SP1

everything seems fine, database access is working just great, thought, I'm trying to create a full backup schedule for the databases I have using the maintenance plan wizard, but I keep on receiving this error, anyone can help? :/


Maintenance Plan Wizard Progress

- Creating maintenance plan "MaintenancePlan1" (Error)

Messages

Create maintenance plan failed.

ADDITIONAL INFORMATION:

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

- Adding tasks to the maintenance plan (Stopped)

- Adding scheduling options (Stopped)

- Adding reporting options (Stopped)

- Saving maintenance plan "MaintenancePlan1" (Stopped)

I got the same problem,...|||Nothing to do with the upgrade. I am running SQL Server 2005 Developer edition on an XP professional box and get this message when I try to create any maintenance plan.|||

Hi guys...

the same problem ocorring after upgrate to SP1 of the sqlserver 2005.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124887

Not even in the Maintenance Plan, but, SISS and Notification Server. I din't upgrade my server, only when Microsoft give us SP2.

thanks.

Maintenance Plan after upgrade

Okay... here's my issue

I got a Win2k3/SP1 server, where I used to have SQL 2000 on it, upgraded to SQL 2005/SP1

everything seems fine, database access is working just great, thought, I'm trying to create a full backup schedule for the databases I have using the maintenance plan wizard, but I keep on receiving this error, anyone can help? :/


Maintenance Plan Wizard Progress

- Creating maintenance plan "MaintenancePlan1" (Error)

Messages

Create maintenance plan failed.

ADDITIONAL INFORMATION:

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

- Adding tasks to the maintenance plan (Stopped)

- Adding scheduling options (Stopped)

- Adding reporting options (Stopped)

- Saving maintenance plan "MaintenancePlan1" (Stopped)

I got the same problem,...|||Nothing to do with the upgrade. I am running SQL Server 2005 Developer edition on an XP professional box and get this message when I try to create any maintenance plan.|||

Hi guys...

the same problem ocorring after upgrate to SP1 of the sqlserver 2005.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124887

Not even in the Maintenance Plan, but, SISS and Notification Server. I din't upgrade my server, only when Microsoft give us SP2.

thanks.

Maintenance Plan after upgrade

Okay... here's my issue

I got a Win2k3/SP1 server, where I used to have SQL 2000 on it, upgraded to SQL 2005/SP1

everything seems fine, database access is working just great, thought, I'm trying to create a full backup schedule for the databases I have using the maintenance plan wizard, but I keep on receiving this error, anyone can help? :/


Maintenance Plan Wizard Progress

- Creating maintenance plan "MaintenancePlan1" (Error)

Messages

Create maintenance plan failed.

ADDITIONAL INFORMATION:

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

Cannot create a task with the name "STOCK:SqlTask". Verify that the name is correct.
(OnPreExecute)

- Adding tasks to the maintenance plan (Stopped)

- Adding scheduling options (Stopped)

- Adding reporting options (Stopped)

- Saving maintenance plan "MaintenancePlan1" (Stopped)

I got the same problem,...|||Nothing to do with the upgrade. I am running SQL Server 2005 Developer edition on an XP professional box and get this message when I try to create any maintenance plan.|||

Hi guys...

the same problem ocorring after upgrate to SP1 of the sqlserver 2005.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124887

Not even in the Maintenance Plan, but, SISS and Notification Server. I din't upgrade my server, only when Microsoft give us SP2.

thanks.

Monday, March 12, 2012

Maint. Plan Help

I need to set up a Maintenance Plan on a 6.5 DB. I know the version is old but the customer cannot upgrade at this time. When I try and run the wizard to set it up I get a warning about running a plan on a DB that is larger that 400MB. Whats the deal? Thanks for the help!!I need to set up a Maintenance Plan on a 6.5 DB. I know the version is old but the customer cannot upgrade at this time. When I try and run the wizard to set it up I get a warning about running a plan on a DB that is larger that 400MB. Whats the deal? Thanks for the help!!

As I recall (and it has been a while), one of the things that the maintenance plan will try to set up is an index reorg and (possibly) space reclamation. You don't want to touch either of these with your database. At least, I don't think you do. I would probably skip the maintenance plan wizard altogether and set up backup jobs to make sure your database is being backed up.

When I did this, I had to set up 5 backup devices (named FULL, 0600, 1200, 1800 and 0000). I then scheduled the full backup to write to the FULL backup device and four transaction log backups to write to the other four devices (at midnight, 6:00am, noon and 6:00pm). The backups would overwrite the files (so another process would have to copy the backup files to a remote location).

SQL 6.5. Ugh. It's the reason I drink so much now.

Regards,

hmscott