Progress Database

Agenda
Process Architecture.
Database Architecture.

Server 1 Server 2

Broker

TCP

Disk Files
Remote Clients
Self service Clients
Connectivity Model.
 Remote TCP connections.

 Self service clients.

Logical and Physical Component Architecture.
Memory Architecture.
Physical Database files.
 The database “.db” file.
 Datafiles.
 Before image files.
 After image files.
 Database structure files.
 Database lock “.lk” file.
 Log files.
 .LIC
 Parameter (PF) files
Database Startup Parameters.
 Basic configuration parameters.
 -H
 -S
 -N
 -B
 -l
 -aistall/-bistall

 Using PF files defining startup parameters.

Connection Parameters

-n : Maximum number of connections to the

database. Includes remote and local connections.
-Mn : Maximum number of servers that can be started.
-Ma : Maximum number of connections that a server
can have.
-Mi : Minimum number of connections that a server can
have.
-Mpb : Maximum number of servers a broker can spawn.
-m3 : Helps to identify as secondary broker
Database Administration.
 Create Database
 Procopy C:\DLC102B\empty4 <dbname>

 Prostrct create <dbname> [.st file] –validate

 Prostrct create <dbname>

 Prodb <dbname> C:\DLC102B\empty4

The structure file should be properly defined and put into the
required location to create a structured database.
 Add Extent

 Create a new structure file with the extents that need to be

added and use the following command.

 Prostrct add <dbname> <newstructurefile>.st

Note : List the database after adding additional extents.
 Online Offline Backup

 Probkup online <dbname> <backupname>.bck

 Probkup <dbname> <backupname>.bck

 Restore Backup
 Prorest <dbname> <backupname>
 Database Repair
 Prostrct repair <dbname>

 Index Rebuild
 Proutil <dbname> -C idxbuild all
 Proutil <dbname> -C idxbuild all –T C:/Temp –TB 31 –TM
32 –SG 8

 Truncate BI
 Proutil <dbname> -C truncate bi
Database Administration Tools
 Data dictionary and Data Administration tools.
 Data dictionary.
Tools for Database Administration.
 Data Administration tool.
Database Utilities - proenv.
 Proenv – provide an interface to call all OpenEdge utilities.
 Set all related environment variables.
Tools for Database Administration.
 Admin server aware tools.
 What is the admin server?
 Admin server control.
proadsv –start|-stop|-query –port <port-number>|<port-name>
 OpenEdge Explorer.
 Accessing the explorer console.
 http://192.168.56.2:9090

 Database administration console.

 OpenEdge Management.
 Centralized monitoring.
 Advanced features to monitor and control OE environment.
Database Utilities.
 Proenv
 Prostrct
 Procopy
 Proutil
 Promon
 Probkup
 Prorest
 Rfutil
 Dsrutil
Database
Prostrct Utilities
– Used to -manage
prostrct.
structural operations on the database.
 ADD
 ADDONLINE
 BUILDDB
 CREATE
 LIST
 REMOVE
 REORDER AI
 REPAIR
 STATISTICS
Database Utilities - proutil.
 Proutil – Main utility which can be used for many db maintenance
tasks.
 DBANALYS
 DBIPCS
 DESCRIBE
 DUMP
 ENABLEENCRYPTION
 ENABLELARGEFILES
 HOLDER
 IDXBUILD
 TABLEMOVE
 TRUNCATE AREA/BI
04. Promon Option.
 Promon – Main monitoring utility. Will be discussed further
on remaining sections.

R&D
Replication
Database Analysis Report.
 The dbanalys report gives the physical information of the
entire database.
 The blocksize, no.of records, record size, extents,
indexes, scatter factor, fragments etc.. can be determined
for all areas from this.
 Proutil <dbname> -C dbanalys >> dbanalys.txt

 Finally this report gives the total blocks, empty blocks,

index blocks, free blocks and the sequence blocks as a
summary.
Advantages of using Enterprise DB
 Above 50 remote connections can be made (Upto 10000).
 Performance related asynchronous I/O processes are
available. APW, BIW, AIW.
 Largefile support, which enables database files to be larger
than 2GB, is available beginning with Progress 9.1C.
 Performance related parameters are available. -spin, -pwscan,
-pwwmax, -semsets.
Analyzing the Database Growth.

 Database growth can be monitored by the following factors :

 Monitor the variable length extent
 If the data are been currently written to the variable length extent,
then it is considered to add some extends to the database.
 Variable length extent can grow only upto 2GB.

 Fixed length extents can be allocated above 2GB by

enabling Large files.
 Proutil <dbname> -C enablelargefiles
Improve Database Performance

The Performance of the database can be improved by

considering on :
 Setting up the connection parameters accuratly and
correctly (Mn,Ma,Mi,n).
 Allocating appropriate Buffer values and block sizes (-B,
-Blocksize)
 Generate dbanalys reports frequently and check for the
scatter factor and the fragmentation. (Dump & Load need
to be done if required)
Some Useful Tips For Increasing Performance
 Make sure you have the right indexes for your application.
 Stripe data extents on as many separate spindles as
possible.
 Use appropriate database block size.
 Always run the before-image writer (BIW).
 Always run at least one asynchronous page writer (APW).
 Put bi log on separate drive from data extents if possible.
 Do not run other stuff on the database server machine.
Apply SP, Install Additional Products,
Licenses update

Configuration File :

License Update :
Install Additional Products and Apply SP :