4GL way to determine Workgroup or Enterprise DB?

TheMadDBA

Active Member

• Nov 24, 2014

• #1

I have a new need to determine if an install is running Workgroup (yuck) or Enterprise. Is there anything I can run in the 4GL to reliably check this?

I can run showcfg and parse the output... but this is less elegant to me and in some cases I might not actually have direct access to the DB server and have to run this from a client.

I thought about checking the spin value in _Startup, but then again I have run into places where this was set to 1 in a parameter file/script even for an enterprise license.

Thanks

 

TomBascom

Curmudgeon

• Nov 24, 2014

• #2

Try changing _startup-spin?

 

TheMadDBA

Active Member

• Nov 24, 2014

• #3

Heh.. does that throw an error on Workgroup?

I would much rather read than touch if at all possible. Mildly surprised this isn't stored somewhere in the VSTs but I guess I shouldn't since it isn't a DB feature but just limitations on the executables.

Guess I am going to have to send out a bunch of emails and wait for backend system access on some of these

 

TomBascom

Curmudgeon

• Nov 24, 2014

• #4

Actually...

if _startup-spin > 1 then it is definitely Enterprise.

If _startup-spin <= 1 then it might be WG. At that point you could try setting it higher. But I don't have a WG handy to test that with...

 

TomBascom

Curmudgeon

• Nov 24, 2014

• #5

I tend to shoot WG systems first and ask questions later...

 

TheMadDBA

Active Member

• Nov 24, 2014

• #6

Yep.. spin > 1 is the easy check for enterprise. When it is set to 1 or 0 (shudder) that is when it gets a bit murkier, especially with what I have seen so far with the parameter files I have access to. Until I get access to all of the systems this could probably be a starting point to at least identify most of the enterprise installs.

The problem is they have quite a few servers with many mixed versions (V9,V10,V11,Enterprise,Workgroup) of Progress installs on each. Trying to get a head start on an inventory but I guess I can collect other stats for now.

 

Rob Fitzpatrick

ProgressTalk.com Sponsor

• Nov 24, 2014

• #7

Workgroup doesn't support:

• AIW, BIW, APWs
• Alternate Buffer Pool
• quiet points
• JTA distributed transactions
• failover clusters
• large files
• multi-tenant tables
• TDE
• table partitioning
• -n > 65

So there are a few params and database features you can test for. But it would be nice if you could test for it directly.

 

Rob Fitzpatrick

ProgressTalk.com Sponsor

• Nov 24, 2014

• #8

And of course, the absence of features like large files doesn't mean it isn't Enterprise; it just makes it unlikely. How unlikely depends on who's managing the DB.

 

Rob Fitzpatrick

ProgressTalk.com Sponsor

• Nov 24, 2014

• #9

According to my notes (I haven't verified this) Workgroup only supports up to 1 GB of buffer pool. So that's another bit of circumstantial evidence you could test for programmatically.

 

TheMadDBA

Active Member

• Nov 24, 2014

• #10

Alas about half of those things also describe a poorly tuned or untuned install

No big deal, it is just going to take a while to process all of the systems/installs which are hardly documented. One of their homegrown monitor apps actually (or at least supposedly) has a list of every database with -H and -S connection info.

Already plugged into that with some of my homegrown VST code to look for obvious config/performance issues and was adding a few extra checks and thought workgroup vs enterprise would be a nice add.

 

TomBascom

Curmudgeon

• Nov 24, 2014

• #11

One way to think of it might be that if it fails the -spin and APW tests etc then whether it is, in fact, WG or ENT is moot -- it is configured as if it is WG. I guess it would be nice to know if it is "Enterprise Capable" but it certainly isn't making any attempt to be.

 

TheMadDBA

Active Member

• Nov 24, 2014

• #12

Yeah... once I get my logins set up I can just go thru install by install and run showcfg and make the appropriate changes.

Step 0 is to make sure the backups are working.

Step 1 is to get anything quickly tuned/fixed that can be by tweaking startup parameters and background processes (APWs,BIWs).

Step 2 is to get the workgroups converted to enterprise and the DLC installs consolidated... the licenses are available just not installed consistently (old versions, tons of bad DBAs in the past,etc).

Step 3 is to get AI running everywhere... I know they need disk space and/or some cleanup.

Step 4 start really tuning the databases and applications.

Lots of hair pulling and crying involved between/during all of those steps. Amazing how long some places can function with things so messed up.

 

Cringer

ProgressTalk.com Moderator

Staff member

• Nov 25, 2014

• #13

I'm around 75% sure there's a way of doing this. Pretty sure a PSC Consultant showed me a few weeks ago. I've emailed him for clarification so will let you know when I get an answer.

 

O

oli

Member

• Nov 26, 2014

• #14

Alternatively, you can look at the "installd.ini" file (in the OE Install directory), section "[Installed Products]" to possibly find the string "OE Enterprise RDBMS".
Not sure it is 100% reliable.