Progress OpenEdge Database 10.1b install on Centos (RHEL)

What follows is a braindump of every thing I stumled into while getting Progress OpenEdge Database 10.1b up and running on Centos (Red Hat Enterprise Linux). Where Centos is a VMWare virtual machine (guest) with Windows XP as the host operating system. …

Install Centos

I had trouble installing Centos in a VMWare guest (Windows XP being the host operating system). Solution was to download a ‘CentOS 5.0, server install’ from thoughtpolice to get Centos up and running as a VMWare virtual machine. Read about this here. …

Download and install Java (JDK)

see /nix/download-and-install-of-java-jdk.html for instructions as to the installation of JDK on Centos. …

Run the installer.

The installation process is pretty straight forward. I choose to install in /pro/product/101b (like Oracle’s Optimal Flexible Architecture (OFA) Convention) …

[root@localhost remivisser]# tar -xvf oe101b_linux.tar
[root@localhost tmp]# /home/remivisser/proinst

     |                              Welcome                              |
Read more →

Create a progress database

Example of manual creation of a progress database using the prostrct utility. …

Create a structure file

First create a structure file with a text editor. …

Rules for creating storage areas and extents
When you are defining storage areas and extents in order to create a new database: …

The minimum information required in a .st file is one schema area extent definition
statement and one primary recovery (BI) area extent definition statement. …

The minimum information needed to specify any extent is the storage area type and extent
pathname. For example:
If you do not define a primary recovery extent path in the .st file, the PROSTRCT
CREATE utility generates an error. …

You cannot use any of the reserved storage area names as application data storage area
names. …

So I created a structure file … structure file
# bi file, location, variable size, size
b /m001/prodata/db01/db01.b1 v 1024

# schema area, location, fixed size, size
d "schema Area",32 /m001/prodata/db01/db01.d1 f 1024
Validate the structure file

The structure file can be validated for errors using the prostrct utility: …

$ prostrct create /m001/prodata/db01/db01 -validate
The structure file format is valid. (12619)
Device: /m001/, KBytes needed: 1088, KBytes available: 4811017 (12616)
There is sufficient free space to initialise the defined extents. (12618)
Create the database

Use prostrct create to create a progress database. …

$ prostrct create /m001/prodata/db01/db01

Formatting extents:
   size                area name   path name
Read more →