Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Log shipping error Expand / Collapse
Author
Message
Posted Monday, June 16, 2014 3:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
Hi All,

while restoring database in secondary server I am getting below error
"row index must be greater than or equal to zero and less than the number of rows. ParameterName: nRowIndex. Actual value was 4(microsoft.sqlserver.Gridcontrol)"

I have searched in so many and they are saying restart the seconadry server instance. I have restarted sql services, but still the error is remain same.

Thanks
Post #1581034
Posted Monday, June 16, 2014 4:10 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:24 AM
Points: 499, Visits: 1,828
You need to give a bit more information with your questions. Are you doing this manually or as part of the LSRestore job?
Post #1581044
Posted Monday, June 16, 2014 4:35 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
i am getting error while configuring log shipping in the secondary server. backup has been taken while restoring error is coming
Post #1581057
Posted Friday, June 20, 2014 1:21 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
Hi All,

I am getting below error while restoring log backup in secondary server.

"Message
2014-06-20 06:04:01.25 Skipped log backup file. Secondary DB: 'OS_Test', File: 'M:\Secondary DB\OS_Test_20140619073534.trn'
2014-06-20 06:04:01.25 Could not find a log backup file that could be applied to secondary database 'OS_Test'.
2014-06-20 06:04:01.26 The restore operation was successful. Secondary Database: 'OS_Test', Number of log backup files restored: 0
2014-06-20 06:04:01.26 Deleting old log backup files. Primary Database: 'OS_Test'."

Everytime Log shipping job is failing. I schedcule job every 24 hours. First day it was running fine but from second day it start giving error. Is there any permanent solution to resolve this issue.

----Thanks in advance----
Post #1584218
Posted Friday, June 20, 2014 3:01 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:24 AM
Points: 499, Visits: 1,828
Beatrix Kiddo (6/13/2014)
Ok, then something else may well be backing up your database and breaking your log chain (as far as log-shipping is concerned). I'd check that with your sysadmins.

It sounds like they're doing this overnight.

Have you checked this?
Post #1584244
Posted Friday, June 20, 2014 3:45 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
Yes , log backup is running @ 6:oo AM and full backup is running @8:00 PM
Post #1584255
Posted Friday, June 20, 2014 4:04 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:24 AM
Points: 499, Visits: 1,828
So you're only taking one log backup a day right before your full backup? Then that "error message" you're getting makes sense, no?
Post #1584264
Posted Friday, June 20, 2014 4:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
what is the solution for that , should i take full backup first and after that if i run log backup then that error message will come , and log shipping will also work fine
Post #1584267
Posted Friday, June 20, 2014 4:40 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 9:08 AM
Points: 100, Visits: 328
should i stop the tape backup which has scheduled, or I need to change the backup schedule timing.
Post #1584281
Posted Friday, June 20, 2014 4:42 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 3:24 AM
Points: 499, Visits: 1,828
I don't really understand your backup strategy. Why are you only backing up the log once a day? Did you switch recovery model to Full purely because you wanted to set up log-shipping? If you can explain a bit more about that it will be easier to know what to suggest.
Post #1584282
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse