Consultor Eletrônico

Actuate - Cannot connect to database 3 (0) Progress db


When you start up Actuate and select connection, put in all the
needed parameters and then you select SQL to connect you may get the
following error message:

Database connection error 3 (0).
================================
Some reasons for this error are:

I. Have the Progress environment variables been set correctly?

There are two additional items for preparing the Progress environment
that are missing from steps one and two in Section "4. Preparing
the Progress Environment" in the Progress/Actuate Beta Release
Notes. The section should read:

There are a few steps that must be completed to prepare the Progress
environment before attempting to connect to it from report created
in Developer Workbench.

1. Set the following environment variables :
PROCFG=C:\DLC\PROGRESS.CFG
PROMSGS=C:\DLC\PROMSGS
DLC=C:\DLC

2. Add the directories C:\DLC;C:\DLC\BIN to the system's
PATH statement.

Once this is done, make sure that ACTUATE is started from within this
environment.

It may be easier to put all of this in a batch file such as:

c:\act.bat
set procfg=c:\dlc\progress.cfg
set promsgs=c:\dlc\promsgs
set dlc=c:\dlc
path=c:\dlc\bin;c:\dlc;%path%
c:\actuate\devwb\bin\designer.exe

Then you can create an icon to start ACTUATE using this batch file.

II. Another reason for a failed connection may be if your database is
networked server, for instance, on a Unix machine. In this case you
must also make sure that you have correctly defined environment
variables for the open interface broker and driver. These would be:
PROOIBRK=<complete path>/dlc/bin/_prooibk
PROOIDRV=<complete path>/dlc/bin/_prooidv

or on NT
PROOIBRK=<complete path>/dlc/bin/Oibrkr32.exe
PROOIDRV=<complete path>/dlc/bin/Oidrvr32.exe

There is also an additional startup parameter which is required when
using the Actuate Beta version 2.0.10. This has been identified as a
problem only with the Beta version and will not be required with the
first commercial release.

The parameter is for Lock Table Entries:
-L <large number>
where <large number> should be larger than the number of rows in the
largest table you plan to report on.

This parameter should be supplied when starting up each server you
want to access.

If you specify a value that is not a multiple of 32, Progress rounds
the value to the next hightest multiple of 32.

III. Another cause for this message may be that this version of
progress does not allow remote connections. Make sure that client
networking is available.


IV. Another reason for this message can be when you try to connect to
a database with parameters -cpinternal, -cpstream, ... different from
those in startup.pf and correct conversions are not in convmap.cp.
OIB/OID reads these parameters even when started manually with the
parameters on a command line.
If startup.pf cannot be modified - as it's used by all Progress
processes on a system, you can do the following:
- create a parameter file (e.g. start_oid.pf) with parameters you want
to use for OIB/OID (not only -cpinternal, -cpsteram but also -d and
-E startup parameters)
- setup an environment variable PROSTARTUP to point to a new file:
PROSTARTUP=$DLC/start_oid.pf; export PROSTARTUP
(start_oib.pf is in $DLC directory in this example)

Progress Software Technical Support Note # 16817