Search results

You cannot empty the extents while their status is LOCKED. You will need to fix that first. The information provided so far doesn’t help to identify why they are locked beyond the obvious “replication is not currently synchronized”. To get to the bottom of that some dsrutil status / monitor...

I would think that mostly you just want to review conmgr.properties and ensure that your script uses the same (or better) values for startup parameters and things like the number of APWs started etc. Then just stop using OEE... That is especially straight-forward if you are running on UNIX...

Seems like a bug… easy enough to fix it and test the impact.

It would be interesting to figure out how uniform the wait times are for all of the processes. From a "real world" perspective you probably don't want a situation where one or two ATM machines out of several hundred are fast but the remainder are ridiculously slow.

I'm glad that you figured it out but, just for completeness, if you had not figured it out we probably would have needed to ask you to share the content of load_vision.bat. We may have also needed to know what commands you used to create the .bd file in the first place.

I know nothing about "webM jms queue" and cannot, therefore, offer any direct help. However... If you are going to ask for help and report that you "are getting multiple errors" you should: 1) Post the actual error messages. 2) Really, post the errors. Don't talk about them or describe them...

Perhaps you could try posting the actual commands that you are using along with the messages being produced? It is generally much more fruitful to respond to the actual commands and errors than it is to attempt to infer them from brief descriptions of the results thereof…

"Unsupported" all too often means "we can't be bothered".

You understand incorrectly. Binary dump files are portable across operating systems, bitness, endianness, and (upwardly) through Progress releases. They can also be backwards compatible if they do not contain features that would prevent that (like an INT64 trying to go back to v9...) You can...

I recently had a customer that wanted to be able to revert from oe12 back to oe11 if something were to go wrong after going live with their migration. We scripted, and tested, a reverse dump & load. We would have needed 6 or 8 hours to revert a couple TB of databases. They almost exercised the...

“PUB” suggests, to me, that SQL92 was involved in some way.

Aside from what Rob said (which is excellent): This code is not the complete set of code. For one thing we are missing the definition of wkCantidad. So there is clearly more stuff going on. You really need to show the COMPLETE code in order to get useful help. The code used from Developer...

You might find this helpful: Session: Inside The OpenEdge RDBMS: After-Image Log Records And Their Uses Speaker: Gus Bjorklund Excerpt: In this talk we will open the bonnet on the topic of After-Image Journaling and Recovery Log Records (aka “Notes”). We will describe what they are, what they...

One potentially valid reason to delete data is that retaining records beyond your required legal responsibility may expose you to a requirement to produce those records in legal proceedings. If your company has a record retention policy for that reason then you should certainly follow that...

NO! YOU DO NOT WANT TO USE THE -i PARAMETER! That is suicidal when updating a production database. If *anything* goes wrong - like the error below, you are in an UNRECOVERABLE state if you used -i. You might also want to post a bit more than "delete where" as a code snippet. Having said that...

The stream isn't shared among sessions so "deadly embrace" really doesn't come into play. More likely is that if you have multiple sessions writing to a single log file you will get "blended" log content. IOW lines that are overwriting and interspersing one another. Especially if you open your...

Indeed I can. I was amused. And chastised.

Bigger fish to fry in the code purity campaign?

Also... your title says "performance question"... but if you are asking something about performance I am failing to see it.

I'm kind of old-school so I still create my libraries as persistent procedures that set themselves to be session super procedures, i.e. session:add-super-procedure( this-procedure ). when they are instantiated. I have recently decided to take steps to explicitly ensure that only one copy of...