Skip to Content
0

Issue with DMS Logshipping at Secondary Site

Oct 18, 2017 at 12:12 PM

41

avatar image
Former Member

Hello All

In our landscape we have configured DMS in DR with the Scripts available. Recently the log-shipping got stopped and we managed to fix the issue with the automatic log backup at primary site.

At secondary site the log are copied with the .BAT scheduled in the task scheduler. But the Restore Scripts are not working properly even when scheduled with task scheduler nor running them manually. We got no errors after running the BAT file. As per the import_scripts the log are getting replaced. But actually it is not replacing them.

But whereas when I restore them manually with the recovery option available in Database manager, the medium is working fine.

Any help on this is much appreciated.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

James Zhang
Oct 19, 2017 at 12:28 AM
0

Hi,

Can you share the script? Also did you see the recover command is passed to database (maxdb kernel log) from the script?

Best regards,
James

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Oct 19, 2017 at 05:11 AM
0

Hi James

Below is the standard Blog from which we created the Script.

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=72123826

I have also attached the Scripts that we run in our server for Automatic Restore

Regards

Manikandan


maxdbscripts.txt (2.0 kB)
Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi Manikandan,

Just like I thought you are using that script, then sorry, I have no idea on the logic of the script.
But this is log not shipped to standby, so this is not maxdb's problem.

Best regards,
James

0
Former Member

Hi James

Thanks for the comments

But help me in understanding this

"But this is log not shipped to standby, so this is not maxdb's problem"

Regards

Manikandan. N

0

Hi Manikandan,

"But this is log not shipped to standby, so this is not maxdb's problem"
=>For my understanding, the log is not transfered to standby via the script, correct?

If I got misunderstanding, would you please explain this issue with some screenshots? My point is if it is maxdb issue, then I can jump to work with you. If it is the script issue, then sorry, let us see whether someone can help with.

Best regards,
James

0