SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Old Forums
 CLOSED - General SQL Server
 Error while setting up Log Shipping
 Forum Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

shahab03
Starting Member

USA
28 Posts

Posted - 06/13/2006 :  17:13:33  Show Profile  Click to see shahab03's MSN Messenger address
I am getting following error when setting up log shipping

Error 14261: The specified @name ('Log Shipping copy for NIMMAIN.vanxdb_logshipping') already exists.



I have cleaned up all the log shipping related tables in msdb database on primary, secondary and monitoring sql server instances but I am still getting this error.

Where else do I need to l look? or do?

tkizer
Almighty SQL Goddess

USA
35954 Posts

Posted - 06/13/2006 :  17:43:35  Show Profile  Visit tkizer's Homepage
Was the maintenance plan deleted as well as the jobs?

Each time the wizard fails, you must manually clear out the tables, so go back and make sure that all log_shipping* tables have been cleared out of all 3 instances.

Tara Kizer
aka tduggan
Go to Top of Page

shahab03
Starting Member

USA
28 Posts

Posted - 06/14/2006 :  09:23:50  Show Profile  Click to see shahab03's MSN Messenger address
Hello Tara

There were couple of jobs which were not deleted. Didnt have any problem after deleting them.

By the way have you successfully performed a Log Shipping Role Change? Documentation is doesnt cover every aspect.

Thanks
Shahab
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
35954 Posts

Posted - 06/14/2006 :  13:09:52  Show Profile  Visit tkizer's Homepage
I have never successfully performed a log shipping role change. We tried it quite a few times in our tests. When we switch between our primary and disastery recovery site, switching is done manually. We then have to resetup log shipping going the other way. We switch 2-3 times per year to ensure that our disaster recovery plan works.

Tara Kizer
aka tduggan
Go to Top of Page

shahab03
Starting Member

USA
28 Posts

Posted - 06/14/2006 :  13:48:26  Show Profile  Click to see shahab03's MSN Messenger address
changing Logshipping roles seems easy from BOL...but I ve experienced lots of hurdles in each step....
I am not able to execute:

EXEC sp_change_secondary_role
@db_name = 'test',
@do_load = 1,
@force_load = 1,
@final_state = 1,
@access_level = 1,
@terminate = 1,
@stopat = NULL
GO



when I executed this SP, I got an error:

Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed.


Per following

http://support.microsoft.com/default.aspx?scid=kb;en-us;294397&Product=sql2k

I can resolve the issue above by

1)Ensure that there are no outstanding transaction logs before you execute the sp_change_secondary_role stored procedure. Manually running the RESTORE job on the secondary server before you run sp_change_secondary_role ensures that there are no outstanding transaction logs.

2) You could pass the value of zero to the @terminate parameter (@terminate = 0) while you execute the sp_change_secondary_role stored procedure. However, the user must verify that there are no users connected to the database before the stored procedure is executed to ensure that the RESTORE LOG works successfully.




I would like to choose option 1. However I am not sure whats the best way to find which transaction logs need to be applied and how to apply them? any examples would be wonderful.
thanks
Go to Top of Page
  Previous Topic Topic Next Topic  
 Forum Locked
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.16 seconds. Powered By: Snitz Forums 2000