Search results

That's too bad. Is the vendor at least still providing support and bug fixes and willing to move you to a modern OE release? To use the horizontal table partitioning approach someone will need to write some code and either compile it onsite or provide r-code. If you have an onsite compiler...

Do have access to the source code?

Just be aware that that technique requires the horizontal table partitioning add-on and that could create problems with older code if the old code uses RECID in inappropriate ways (almost all usage of RECID is inappropriate).

The space in a block freed by deleting records will be reused as new records are added (and if old records grow). For index blocks you need to run idxcompact to reclaim the space. (That can be done online.) There are many ways to dump and load. Some methods can greatly reduce the required...

The original post says: True, the concern is the speed of those tasks and there are ways to improve that stuff which do not involve purging data but I actually found this rationale to be a refreshingly solid set of reasons for wanting to purge. The more typical reasons usually boil down to...

IMHO if it takes more than an hour you need better disks.

... and if you do have such a policy to follow - make sure to destroy the old backups.

Data _can_ be a liability. Keeping it beyond legally mandated record retention periods can expose you to needing to provide it during legal "discovery" processes. Which can be fairly onerous in terms of work to be done to extract it, review it, and prepare it for whoever wants it. Whereas if...

You might want to share who the manufacturer is. Someone may be familiar with them and have specific advice. In any case, OEM provided storage area configurations are frequently "substantially less than optimal". Is "10.7" the application version number? (That's not a valid OpenEdge version...)...

As Patrice says - this won't work as you wish. When you delete data you also probably won't create much in the way of "free" and "empty" blocks so you are not going to see much evidence in prostrct db statistics either. To reclaim disk space you will need to dump & reload. And if you are...

"Oh Eee Oh Ex Oh Dee" has a nice rythm to it. I like it!

Oh Eee Oh Ex Oh Dee

I nominate Cecil as the new head of OE Marketing!

The lack of a username & password for the database does not, by itself, prevent ODBC access. But a simple 4gl program will also easily export the problem table: output to value( "problemTable.csv" ). for each problemTable no-lock: export delimiter "," problemTable. end. output close.

Just in case someone else comes along wondering about the same message... You have to first: "proutil dbname -C disablesitereplication target" (or "source" depending on how the backup was made).

Caching it as a temp-table will run circles around having it in the either of the buffer pools. Especially if you have client server connections. TT access can be 5x to 20x faster than db access - even when the db data is in the buffer pool. If your application just happens to have an include...

That is awfully vague. Surely the "requirement" specifies what sorts of events you must audit. From the rest of your post it almost sounds like you only need to be keeping track of certain events like "access to the Progress editor". If that is true and the if number of events is fairly limited...

I might be flogging a dead horse but just to clarify... do you mean that you lack a key to decrypt the xcoded files back to clear text? (That's normal. There is no Progress provided utility to convert xcoded source back to clear text. Obviously the compiler knows how to do it. There are also a...

There are really only two platforms that you should consider migrating to -- Linux or Windows. Of the two Linux will be far less likely to be a problem, since you are already on AIX Linux ought to be much more familiar. In either case you will need to dump & load for the platform change. AIX...

The reported error might be related to this kbase: Progress Customer Community Note that the recommended resolution is to upgrade to at least 10.2b04. 10.2b08 is the last release of OpenEdge 10 and that is what I would target. I see what look like additional error messages hidden behind other...