|
On one site we are getting the following message in the dbremote log I. 2017-12-12 00:08:48. sopen "C:\SDATA\CONSOL\STORE18.kdp" failure 5: Permission denied We are getting very many request resends (currently have 11K in the remote site) Any idea how to fix and how I can catch up the remote site with the consolidated. On the consolidated dbremote log it looks like this ? I. 2017-12-13 11:56:27. Received message from "STORE18" (776-098318973154-098318973154-501) W. 2017-12-13 11:56:27. Not applying operations with old resend count I. 2017-12-13 11:56:27. Received message from "STORE18" (776-098318973154-098318973154-503) |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 13 Dec '17, 08:19
question was seen: 1,143 times
last updated: 19 Dec '17, 10:47
AFAIK, that is simply the OS error, i.e. dbremote cannot open the according file. Can you check whether that file is locked by another process or has unusual permissions?
There seems to be quite a lot of them so might not be easy to check
Looks like the consolidated server is now catching up but it has taken several hours of copying transaction files back and forth - not sure why it has generated so many
I've added an -rd -rp option on the dbremote to see if that helps (online help says it helps in slow connections ?)
Is it possible that you've somehow setup two remote databases that are both defined with STORE18 as the publisher? Perhaps a backup was taken of the database and now both are running dbremote at the same time?
That could explain the "Permission denied" error (the other dbremote was writing to the file), the not applying operations with old resend count (consolidated applied messages from the "other" remote), and the fact that things are now appearing to be catching up (the "other" remote stopped running).
Reg