This is bug OE00208701/PSC00234422. I am rather surprised that, according to the KB article, it was re-introduced in 11.x and exists all the way up to 11.7.4. If that is true then your statement is correct. You can check the LRU2 replacement policy status in several ways:
in promon R&D 2 3...
Your description is brief so I am guessing somewhat about what you are trying to accomplish.
This may help: How to programmatically dump and load database definitions (.df's) and data (.d's) files using Data Administration routines
That will work if the "existing DB" is an empty database...
I confess I don't know a lot about Linux memory management. But I believe your understanding is not quite correct, for a few reasons. First, my understanding is that the swap file is used only when there is memory pressure and pages of physical memory must be freed to service new requests...
Funny, I've never run into this before. I guess I tend to run my own code for looking at schema, as the Data Dictionary UI is rather limiting. It looks like it's a known issue: https://knowledgebase.progress.com/articles/Article/cannot-see-metaschema-tables-in-the-dictionary-chui-in-11-7-5/p...
As a counterpoint, I have seen lots of bad code get into production precisely because developers weren't paying attention to their CRUD stats. I recommend configuring your DBs so you can look at your CRUD stats wherever you run, and especially where you develop, data-access code.
I do agree...
The _file._category field can also be updated. If you would like your schema to be more self-documenting, you can define categories for your application tables. They will be preserved when you export the schema to a .df.
ADD TABLE "foo"
CATEGORY "my category"
Kudos to you @ron for doing this. I'm a proponent of looking at system object logical I/O. In looking at your audit I/O, you'll also be able to see all of your meta-schema I/O, if your statistics parameters are set correctly. It can be surprising how much there is for some applications.
Close; they both default to 1. ;)
Some are, some aren't. A good way to understand what these tables are is to look at their categories (available in 11.0+). Example:
for each dictdb._file no-lock use-index _file-number:
I assume you're referring to this Excel function:
Returns the internal rate of return for a schedule of cash flows.
I have no idea what this function actually does, and certainly there's no ABL equivalent.
Probably the best bet is to programmatically create an Excel...
First off, I don't think you're going to write a query to do this, unless your application already writes information about run and publish statements, method and function invocations, etc. to a table.
Also, maybe a minor point: individual programs don't run in batch mode; ABL clients do. So...
It should be fast, if you have the right licenses. You could see if you can get an eval license for the source platform in question, then follow the instructions I gave you. But that will result in a v12 database on that Unix platform.
In your latest message you have hinted at what you want...
There's your problem.
The file custdb.bak is a database backup from some Unix system, in directory /prod/db/proddb.
You cannot restore cross-platform. This file must be restored with an OpenEdge installation on the same platform as the database from which it was taken.
Can you open that backup file in a hex editor? The start of it should look something like this:
00000000h: 76 6F 6C 75 6D 65 20 31 20 6F 66 20 62 61 63 6B ; volume 1 of back
00000010h: 75 70 20 74 61 6B 65 6E 20 57 65 64 20 46 65 62 ; up taken Wed Feb
00000020h: 20 20 33 20 31 35 3A 31 37 3A...