Solved

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

Posted on 2004-04-07
4
2,437 Views
Last Modified: 2008-02-01
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
Comment
Question by:Phawkins55
  • 2
4 Comments
 
LVL 6

Expert Comment

by:musdu
ID: 10777492
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
 
LVL 6

Accepted Solution

by:
musdu earned 500 total points
ID: 10777508
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

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains all about SQL Server Piecemeal Restore with examples in step by step manner.
Shadow IT is coming out of the shadows as more businesses are choosing cloud-based applications. It is now a multi-cloud world for most organizations. Simultaneously, most businesses have yet to consolidate with one cloud provider or define an offic…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question