Search results

What does "starting up a server" have to do with anything? That sounds like a new bit of information.

Using _progres, or not, doesn't matter. That's just me being annoyed at the "when all you have is a hammer everything is a nail" approach. You could make me even more annoyed if you tell me that the source file is a .w. (Which also doesn't affect the outcome.)

"What is happening is best examiined in the Task Manager..." "...the .exe is left as a background process and for some reason their (as I am now a contractor) stays connected and it appears there are now limits to the number of connections." So "the problem" is that each execution of the task...

You don't need to upgrade SX in order to upgrade OpenEdge anymore than you need to upgrade SX before applying a Windows update.

Are you also responsible for managing the server? They seem to want someone (you? or whoever manages the server or network) to setup some firewall rules to limit who can talk to services. That seems reasonable. Unless this server is public facing and needs to accept requests from everyone. If...

Why? It’s good for the soul. Aside from that… yes, the executables are clearly different; why carry around all of that excess baggage? Batch jobs don’t need support for mice and GUIs and all of that useless cruft.

Another observation... your startup command contains "-n 4 -Ma 4". Those are server startup parameters. They have no relevance to starting a client session.

No, it doesn't really make much sense. First of all - what is the *problem*? A task not terminating isn't, necessarily, a problem. It might be annoying and unsightly but is there an actual problem like maybe some data doesn't get exported or a report doesn't get generated or some business...

It sounds to me like you have a lot of serious architectural problems related to coupling and side effects. There is no magic wand to solve those, it takes hard work and dedication to undoing past mistakes.

It seems to me that this is (at least) a two step process. You seem to be gathering some information into temp-tables and then creating some stuff. But your transaction encompasses both phases. So, at the very least, it should look more like this: repeat while not hQuery:query-off-end: /*...

It sounds like you might have -usernotify (or -dbnotify, they changed the name and I can never recall which one goes with which version and I am far too lazy to look it up right now…) set to zero. Aka “disabled”. That results in the behaviour that you describe of needing to restart stuff. Set it...

I don’t understand the need to shut down everything. Why are you doing that?

Sorry, I don’t have the steps to reproduce your problem. Those steps would be in your missing logs.

As I mentioned, important parts of the logs are missing. I cannot say for sure that this is your root cause but it is well known that a backup during synchronization will spoil replication. From what you have shown so far I cannot rule that out and there is plenty of reason to think that it has...

Ok, I missed that. I blame it on trying to read the log on my phone ;) FWIW I really dislike those (-----) messages. But that's not your fault. The message at 11:23 says that it expected the last change timestamp to have been on or around Fri Feb 16 22:40:45 2024 but, instead, found a change...

So far as I can determine those logs do not contain any errors that suggest that the target was modified after creation.

I don't see any "please find attached for error screen shot". Going into pre-transition when the source is down is normal. That's kind of the point and not a worry. As for "how it is possible target database got modified?", first I would want to see the missing error message screen captures...

FWIW, I haven't noticed anything different.

To add an extent you want to create a structure file that only has new extents in it, you don't list the old ones in there. The new extent # needs to be one greater than the last existing extent. So if you end with .d1, you will be adding .d2. Something like this: # add.st # d "Schema...

The port specified for the DSN is the port used to login and validate credentials. Once the connection is established further communications occur on a port that is assigned from the min/max range.