Home » RDBMS Server » Networking and Gateways » Not being able to connect to Oracle 9i from 7.3.4
Not being able to connect to Oracle 9i from 7.3.4 [message #67105] Wed, 01 October 2003 16:56 Go to next message
Kuldeep
Messages: 21
Registered: June 2002
Junior Member
The Oracle database is on Windows 2000 Server SP3 ver 9.1
The Oracle client is on HP MPE3000 MPE/iX Running Oracle discoverer and sqlplus 2.3.4
***********************************************

We have a unique problem. We upgraded our database to 9i and since then one of
the client programs that reside on HP E3000 [[ver 7.3.4]], Cobol Precompiler has
stopped working. Has anyone seen this type of error before? The HP 3000 has the
operating system MPE. All the programs were written in COBOL in the stone ages
and the business cannot migrate to Oracle 8i or 9i client due to desupport of
Oracle products for the HP3000 platform. Any help would be appreciated.
The sqlplus to the Oracle 9i database worked. I just got confirmation from the
developer. However, the connection from the HP which is a COBOL program is not
working and gives the error.
********************************************

Scenario 1: From the MPE command prompt: SQLPLUS HOLD/<password>@HTR ---Works

Scenario 2: From within the COBOL program: CONNECT HOLD@HTR IDENTIFIED BY READRITE-----Does not work

Scenario 3: From within the COBOL Program: CONNECT SMPROC INDENTIFIED BY READRITE USING HTR ------Does not work

Scenario 4: From within the COBOL Program: CONNECT
SMPROC/READRITE@HTR------Does not work

Gives error ORA-01004

Has anyone tested this in their environment. The client cannot upgrade the client, but wants to be in Oracle 9i by Nov 15th. A difficult situation. Please help.
Thank you for your help.

Kuldeep
Re: Not being able to connect to Oracle 9i from 7.3.4 [message #67108 is a reply to message #67105] Thu, 02 October 2003 11:50 Go to previous message
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
ORA-01004 is supposed to deal something with os_authentication
i beleive OS authentication is turned ON.
thats why your scenario 1 works.
and
you may need to look into your cleints tnsnames.ora.
Becuase the earlier releases must have SID in CONNECT_DATA and NOT SERVICE_NAME.
IF the above is not working for you,
check your sqlnet.ora in server side.
if you are not using ASO or Namesserver or any special authentication methods, comment off all the entries in sqlnet.ora and try again.

Previous Topic: ORA-12571: TNS:packet writer failure
Next Topic: Connect to oracle database through dial up
Goto Forum:
  


Current Time: Thu Nov 21 21:44:08 CST 2024