Search results

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...

I stand corrected. I thought it was an Enterprise feature.

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.

Have you tried a Knowledgebase search? This one looks relevant: Progress KB - Error 9908 9909 trying connect to AdminServer on UNIX.

_proapsv is an appserver process.

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...

If you define "changed" as a character you should get a list of the changes. I think.

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...

One thread will suffice. I've closed this so there's no confusion.

The obvious question is why you want to do that. What are you trying to achieve?

It's superbly good for little snippets of code. I'm with Stefan - if it has meaning it goes into SCM. I use it in 12.2.6 without any issues like you mention. It's still dysfunctional as Stefan says but I never lose code. I don't remember it being a problem in 11.6 either but that was a very...

It would help if you would give us the errors you receive rather than just saying it doesn't work. In this case I guess it doesn't work because you need to define the output location: output to value (vCSVFileName) [append]. And you'll need to close the output as well once done.

Another one to watch out for is changes to the length of an extent.

I've worked under numerous folks over the years, all with different approaches, but the one that caused the most food for thought was the policy that all schema change requests had to also come with sample data in a .d file. This had a number of purposes. 1) The developer has actually tested...

Aren't they in the df of the database? Can't you just therefore create an incremental df to load?