Search results

Are you asking what you need to do in a "fail over" situation to be able to replace an existing database on a PROD server with one of the TEST databases? Presumably in a situation where the PROD server has failed?

Maybe you could share some simple sample code that shows what you have so far and where you need these current buffers? I'm having difficultly understanding how it is that you are able to iterate & return them but somehow don't know what they are.

Perhaps you can share a description of the problem and your eventual solution?

Maybe. Or maybe he is testing to see if some series of operations can corrupt his configuration. I can’t tell. The steps do appear to be 90% similar to an easily found kbase for reinitializing the OEM password. But the title talks about “recovery” not initialization. So it is quite unclear (to...

And while we are at it... what version of OpenEdge are we talking about?

What is "it" and what did you expect it to do that would constitute "working"?

That is an interesting series of events. Is there a question somewhere in there?

Stefan is pointing out that "Eclipse Jetty" is used by OpenEdge Explorer. And you very likely are using that. So it is more a matter of needing to restrict access to that port because, otherwise, anyone can fire up OpenEdge Explorer and wreak havoc on your systems. (Instead of just a few...

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?