Is this 32 bit of 64 bit? Are you absolutely sure of your version? It looks like this bug: Progress KB - Database experiences a forced shutdown with error 793 and 744
Usually when a program crashes you get a protrace or a procore file which will give you more error detail. You may have to search around a but to find it though. Often it's in the start directory of the application, or possibly in the temp directory.
You may be better served to start your own thread, linking this one. Starting a new conversation on a thread that is 19 years old is unlikely to bear much fruit.
Following is a newsletter from White Star Software, Consultingwerk and Riverside Software:
You may have heard that there is a critical security vulnerability in the “log4j” Java library that is used by many applications in the Java ecosystem and you might be wondering if this impacts your...
You need some sort of license for the database on the second machine. A DR license is what you need to do that. It will be cheaper than a full license.
The trigger code needs updating then to better handle the record not being lockable. And then you need to find the code that is locking the record for too long and fix that too.
I would be very surprised if that's a working database. 4GB backup, 8MB data, 1.6GB of BI looks weird. But the "odbk" probably stands for OpenEdge Database Backup and is therefore probably where I would start looking.
The good news is that Sage Intergy still looks like it has an active website...
Even without the output your process is completely wrong. It should be something along the lines of the following:
Enable AI on the source (and enable the ai archiver too probably)
Configure the sports2000.repl.properties files for both source and target.
Enable the source DB for Replication...
First of all, Auditing requires a license. It may be it's already included in your license, but a license is required for the tool nonetheless.
That being said, and IMHO, you are approaching this all wrong. Not all data replication are created equal. You first need to evaluate what you want to...
I've no idea if it's the most efficient, in fact it almost certainly isn't, but it definitely plays to my geeky side...
https://abldojo.services.progress.com/?shareId=619bbe4ac552423dc846eb6a
Can't beat a bit of recursion on a Monday morning.
Definitely heading the right way. As Patrice said, the chances of there being an update elsewhere are very slim but if you have to account for it then you're ok.
One note though - FIND FIRST should almost never be used. If there really are multiple records that satisfy the FIND then you want...
DEFINE VARIABLE cChanges AS CHARACTER NO-UNDO.
DEFINE TEMP-TABLE ttRechnung LIKE Rechnung.
FIND FIRST Rechnung NO-LOCK.
CREATE ttRechnung.
BUFFER-COPY Rechnung EXCEPT Rechnung.RG-DAT TO ttRechnung.
BUFFER-COMPARE Rechnung TO ttRechnung SAVE RESULT IN cChanges.
MESSAGE cChanges
VIEW-AS...
Just to make sure I understand - you want to ensure at the point of locking the record in the new buffer that it hasn't been changed by another process?
If so, then you can use the BUFFER-COMPARE keyword to compare the find-customer to the upd-customer and at that point make a decision as to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.