Kbase 16761: Message: Cannot access <db-type> with current CONFIG file.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/04/2003 |
|
Solution ID: 16761
SYMPTOM(s):
Cannot access 3rd party database.
Cannot access <db-type> with current CONFIG file. (1246)
Cannot access SYBASE with currect CONFIG file. (2222)
Cannot access ORACLE with current CONFIG file. (2364)
CAUSE:
In order to access any third party database from a PROGRESS client (4GL or ESQL/C), an appropriate DataServer license is needed. This solution describes where those licenses are needed, and what DataServer license is needed for each supported foreign (third party) database.
FIX:
The following third party databases can be accessed using the appropriate DataServer through either PROGRESS networking, the native's database networking, or local (direct) access. If using PROGRESS networking (also called Remote DataServer), the DataServer license needs to be available on the remote machine. Those databases are:
ORACLE (using ORACLE DataServer)
MS SQL Server (using MS SQL Server DataServer)
The following third party record management facilities maybe accessed through a DataServer, with a local connection, a remote connection, or using the apropriate operating systems remote file access:
RMS DataServer (one VMS machine can access RMS files on another machine using VMS remote file system facility)
C-ISAM DataServer (one UNIX machine can access remote C-ISAM files through NFS if NFS access is supported for that C-ISAM version)
The remaining databases are supported using ODBC Dataserver only. Please, refer to Progress Knowledge Base Soluton # 18240 for more details about which datasources Progress ODBC Dataserver supports.
Up to PROGRESS version 8.1, only 16-bit ODBC drivers are supported. PROGRESS supports 32-bit ODBC drivers with PROGRESS 8.2A and above and Progress 9.X.
Notice that ODBC access to ORACLE, and all other datasources that have their own direct dataservers are not supported.
1 - Make sure you have the correct license to access the third-party database.
2 - Make sure you have the environment variables set to the correct environment (DLC, PROCFG).