Search results

I don't use elapsed time as a measure of query efficiency as it can be inconsistent, even for consecutive runs of the same query. And it can be influenced by factors that are external to your code, including database cache contents, file system cache contents, system workload, I/O workload...

There are many ways to do authentication. If you want to modernize, look at OpenEdge Authentication Gateway. https://docs.progress.com/bundle/openedge-authentication-gateway/page/Learn-about-OpenEdge-Authentication-Gateway.html

This is a new one on me. What is the point, i.e. the business objective, of this process involving rfutil -C aimage extract? Is this an attempt at saving disk space?

Once the notes in the Locked extent have been sent to the target (or targets), the database does change its status from Locked to Full. But it does not empty the extent. You should use the AI File Management Daemon (AIMD), also known as the AI Archiver, to manage the switching and archiving of...

I prefer not to use fixed-length AI extents, for a few reasons. In a case like this where your AI extents are filling up, having fixed extents means you have a fixed amount of time (remaining AI extent space / AI write rate) left to resolve the problem. Whereas with variable-length extents...

In my opinion, PSC got the schema right for _DbParams, and the content wrong. IMHO, it should only contain primary broker parameters, not the client/server parameters of the primary broker when it also happen to be a login broker. Ideally, I would have liked to see an _LoginBroker VST with one...

Relying on logged startup parameters and their values is very hit-and-miss, especially with secondary brokers. The older the release, the worse it is (i.e. they just don't log much at all). Any database running under 11.5 - 11.7 should have an _DbParams VST, and the __SrvParam-* arrays in the...

I had never heard of DBConfigTool.sh before. What does it do?

Did you find an article that said this process is unsupported? If so can you share that? Database dump and load (whether by ASCII or binary dump) is in fact the only supported method of migrating a database from one OS to another.

Those are the basics, and if your database is very small, you can get away with a simple proutil -C idxbuild all. If you have a meaningful amount of data (a production-like DB), e.g. several GB or more, you likely want to specify options on that command to tune its resource utilization and...

There are undoubtedly lots of threads here about database platform migration. I'd suggest a site-specific Google search for related terms: dump & load, migration, etc. At a high level, you need to dump the data from your source database and load it into a target database. Dump and load can be...

More info on the conv1112 issue: https://blog.wss.com/upgrading-to-openedge-12

I asked about replication because not everyone is aware that, as of OE 12.3, it is possible to upgrade replicated databases to OE 12.x without having to reseed. And I asked about TDE because there is a data-loss bug in proutil -C conv1112 when TDE is in use with certain conditions.

Just curious, are OE Replication or TDE in use?

I'd suggest a follow-up conversation with the auditor about the perceived business risk. If they want the option to invoke a post-migration fallback, after a go/no-go decision has been made for "go" and new writes are happening in OE 12, then that suggests to me that they don't have confidence...

For what it's worth, the text "state", the name of the table from which I deleted the record, was not present in my ai scan verbose output. I wouldn't focus on the table name.

Welcome George! :)

"DELETE FROM" looked odd to me too. But it does compile in 10.1B, and it behaves like "DELETE".

The ai scan verbose output won't contain the table name. It contains a summary of the change notes. Let's look at a simple example (from 11.7.16). I created a copy of the sports database. I created four AI areas and two new Type 2 areas: $ cat add.st d "state":20,128;8 . d...

Your English is fine. :) (or my Spanglish is improving?) There is a lot to unpack here. If we're seeing all of the purge code here, and not just the bit that does the record deletion, then you are not archiving the data and you are not causing a long-running transaction that would cause BI...