Search results

You can use proutil dbname -C describe to see the internal version number of the database. Here are two examples: $ proutil sports -C describe OpenEdge Release 11.7.16 as of Fri Nov 18 14:05:47 EST 2022 OpenEdge Database Description Database Name : /data/rob/db/11/11.7/sports...

Well done on installing OE 12.8. A database upgrade is not the same thing as an OpenEdge upgrade! A database has an internal version number that is tied to the OpenEdge major version that either created or upgraded the database. In other words, a database created in OpenEdge 11.x, or upgraded...

Some more info on the Client Statement Cache and how to use it.

Please provide your OpenEdge version number. It matters when dealing with issues of how OpenEdge behaves, and in particular when parsing output of Progress utilities. When providing data from promon, please also provide the column headers so we don't have to guess what the data means.

Unfortunately, Progress doesn't provide a useful way to document structure. Structure file comments are useless as they are not written into the database. So, for example, they are discarded after a prostrct list. It is yet another limitation with structure management. One solution is to...

Yes, you do. From late v11 to 12.8.3, you could directly install an up-to date OpenEdge installation with just the update install package. E.g. you could install 12.8.3 in an empty directory, without having 12.8 already installed. As of 12.8.4, you need two install packages: the 12.8.0...

Great idea. Lots of developers/DBAs have spent lots of hours extending and contextualizing PSC's tool output to make it more useful. There is so much more they could do. As a community, we would be much better off if they did it. A rising tide lifts all boats, as they say. Also, in this...

This is an excellent point. It would be very useful to have information about field-level distribution of field lengths. I suppose we can get a list of the worst offenders with a dbtool SQL width scan.

Objects to areas I have a loose collection of unwritten rules in my head about assignment of objects to areas. I should write a blog post about that at some point. In no particular order: There should be no application objects in the schema area. All data storage areas should contain objects...

I never did figure that out. It is eight bytes, so it could be a block address. I guess it's a question for Gus or Rich, or someone else who was on the engine team in the v9 days. I'm not sure what it's purpose would be. It seems like several ideas that got past some review stage in the...

My choice would be to let it happen on the next create. It may not make much difference if record sizes are quite uniform, or always larger than the toss limit. But for tables with smaller records or more variability in the record sizes, it may be that another record the same size the one just...

Sorry, I'm writing faster than I'm thinking. That's the correct calculation. I think they are comparing physical block offsets to the clustersize, which gets thrown off by EH blocks in extent 2 and beyond.

Some remaining bugs in option 13: bad parsing of EH block as Type 2: Customer/Order Area (8) Extent 1 Block 1 ----------- 0000 bk_dbkey: 0x00000000 0 bk_type: 0xfe 254 (Extent Header Block) bk_frchn: 0x7f 127 (NOCHN) bk_incr...

Yes. What I refer to as "the RM header" is numdir, freedir, and free. Dbrpr was enhanced in 12.8, to show more details of the RM header and the row directory. Rowids are new, along with some new base conversion. They also fixed one or two bugs. E.g. the phantom partitionId field between...

I do consider those two data structures as part of the fragment, as they are not pre-allocated. There is one each per fragment. I was referring to the RM header, the four-byte structure between the block header and the row directory, which is a fixed part of the block overhead.

In the past, I had some very security-conscious customers in the financial services sector who refused to provide root access for anything, including the installation of OpenEdge. They were told it couldn't be done and they fought tooth and nail, insisting we escalate to Progress. I have been...

I've heard there is an AI plug-in for PDSOE, but it's just a wrapper for ChatGPT. It doesn't matter to me as I've given up on PDSOE in favour of VS Code.

For record block overhead, we should also add four bytes for the RM header. This brings up the larger question of rules of thumb. What's the right way to tune X in all cases? In a few lucky cases, we have an answer, e.g. -omsize should be at least the record count of _StorageObject. In most...

These considerations don't matter for existing areas, as RPB cannot change. It only matters when thinking about new areas: added areas, or areas recreated via dump and load. So I don't bother with the "16 or" as no new Type 1 areas should be created. I use 65 in this calculation rather than...

Prior to OE 12.5, the maximum extent size was 2 GB, unless the Large File Support feature was enabled, which made the maximum size 1 TB. This feature was exclusive to the Enterprise RDBMS license. In OE 12.6+, Large File Support is enabled in all databases, regardless of license type. So you...