• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2683
  • Last Modified:

I am getting an Oracle error message when trying to log on to the database.

I have an PB app that logs on to an Oracle Database.
The compiled app runs fine on my system even though I access from a net drive.

When users go to access the app I get an error 999 DBMS O84 Oracle 8.0.4 is not supported in current installation. Any Ideas on what this could be?
The .ini is located in the same folder as the .exe. The Oracle client has been checked and seem to be OK.

Because the initial login screen comes up which is done in PB I don't think its PB related.

This is a copy of the app .ini file.
[Database]
DBMS =O84 ORACLE 8.0.4
Database=vmis
UserId=
DatabasePassword=
LogPassword=
ServerName=tvm01
LogId=
Lock=
DbParm=
Prompt=0
0
Phawkins55
Asked:
Phawkins55
  • 2
1 Solution
 
musduCommented:
Hi,

to test connection to the database use tnsping (may be tnsping80) program. (It is in oracle \bin folder)

tnsping80 vmis

you should check tnsnames.ora file in your clients. It should have a definition for vmis. (tnsnames.ora is in network\admin folder)

regards.
0
 
musduCommented:
There's an article on sysbase web page about this error message;

 Connecting to Oracle 8.1.x Workaround for PowerBuilder or EA Server on Solaris


Overview
Depending on the version, Oracle supplies either a libclntsh.so.1.0 or libclntsh.so.8.0.  This problem affects both Powerbuilder 6.5.x and EA Server (versions 3.5, 3.6 and 3.6.1) for Solaris using the PBVM.


Common Error Messages
In EAServer, pinging the connection cache will fail and the following error will appear:

No such file libclntsh.so not found
ld.so.1 export/JaguarCTS/jagsrv: fatal:illegal pathname

In Powerbuilder, the following are the error messages you will encounter when trying to connect:
DBMS o84 oracle 8.0.4 is not supported in your current installation
Could not connect to database

Unable to load the requested Powersoft database interface.  Please make sure both the interface and client software are properly installed.

Workaround
The workaround is to log in as oracle and create a symbolic in the $ORACLE_HOME/lib directory as follows:

EAServer Workaround
ln ?s libclntsh.so.X.0 libclntsh.so

X ? Depending on the Oracle version, it will either be libclntsh.so.1.0 or libclntsh.so.8.0

PowerBuilder Workaround (only for Oracle 8.1.5)
ln ?s libclntsh.so.8.0 libclntsh.so.1.0
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now