Search results

You’re right. I got caught up in hyperbole. Obviously you should vote for things that you understand and support. I will edit my original comment to reflect that.

For those of you who may have forgotten... Progress has a portal for enhancement requests and there are a lot of good ideas there. Product management has also been a lot more responsive to these recently than they may have seemed to be in the past. If you have not been actively reviewing the...

Join fellow Progress/OE users in Burlington, MA Nov 12-15... PUG Challenge Americas is the premier event for those who design, develop and deploy applications based on OpenEdge and other Progress products. REGISTER NOW and take advantage of early-bird pricing! Over 50 sessions are now confirmed...

"Auditors want" is always a bit of a rabbit hole ;)

So "sudo". But with a license fee. And stuff.

I don't think it is the SQL engine per se that is doing that. I experimented a bit with the built in sqlexp tool and: 1) It does not return a count. 2) I can change the @ReportFormat from "standard" to "by label" with changes the output from what you describe to a format with no headers but...

It would not surprise me if there is a mismatch between your actual Java version and the Java version that OE9.1a expects. But I have no useful suggestions at this point. Other than the obvious - upgrade to a supported release.

You might want to consider sharing the name of tool that you are using to execute your query, the version of OpenEdge that you are querying, and the actual query being used.

I have added logging of such access, via OE Auditing, in the past as a result of “auditor concerns”. Part of that also involved writing some reports to demonstrate compliance. Or at least report on when the access was used. The work was done for a bank and I probably had to bill them for at...

This stuff was all 25 years ago... our memories are "dim". I believe that the properties file is just defaults. The -S that you provide on the sqlexp command line will override the one in the properties file. Speaking of command lines, your most recent example is not properly formed. You are...

Very old releases require the addition of a “-char” startup parameter to the sqlexp command line. https://community.progress.com/s/article/P92359

Sure. And as long as nobody finds out about the other port and tries to abuse it everything will be fine. I'm just saying: "don't trust the users to keep it straight".

So just remove the "-ServerType 4GL" and "-ServerType SQL" parameters but continue to start distinct brokers. Even though you cannot enforce it with -ServerType, you still want to have two distinct brokers, one for 4gl and one for sql. You will need to enforce it by not telling the 4gl users...

Like the others said, 9.1a apparently doesn't have the -ServerType option. Sorry about that, I got tricked into thinking that it must be there by the log message "Ce broker supporte et le groupe de serveur 4GL et SQL. (8865)" Have I mentioned that you really ought to upgrade this system?

That's an awful lot of connections for a database as poorly configured as this one is but I suppose that we can save performance considerations for later. For 400 4GL connections I suggest: -Mpb 40 -Ma 10 -Mi 1 In English that is 40 "remote servers" for this broker with each server supporting...

Ok, so how many concurrent connections do you actually need to support?

Perhaps I should clarify that question - do you have 400 users who need to simultaneously connect to the database?

A couple of things... 1) I am truly pleased that you are actually providing answers to questions. That is wonderful. Thank you! 2) Apparently someone tried to run SQLEXP back in 2012 3) It looks like "servpro" and "servpro-reseau" are the scripts that actually start Progress. They also look...

That looks like the old screen capture where it did not work. There does not seem to be a screen capture #2.

We are getting there :) Is "leopold" the system's DBA? Is leopold available to help with configuration? That message about root not being able to "dot" proenv is very strange. I'm going to file that under "ancient and obsolete release of AIX". On the bright side - "proenv" should also work...