Help needed getting the oracle dataserver to connect to a oracle database

Chris Kelleher

Administrator
Staff member
PROGRESS V9.B14 (Enterprise DB, Oracle Dataserver)
Sun E4500 4GB memory, 130 GB disk space
Oracle version 7.3.4/8.0.4
I'm looking for help setting up a local Oracle Dataserver in my test
environment any help will be greatly appreciated. I cannot connect to the
oracle and progress at the same time.
My connection steps
1. Start oracle database - Oracle database is up and running (I'm testing
against a 7.3.4 instances)
2. Start oracle dataserver broker - $PROBRKR -S unifitora -H
ral-dev04 -N tcp. Started
3. pro oratestds -db oratest -dt oracle -ld orams2 -U
test_app@ora_devl_ms2 -P test1. I get errors
I get the following messages
non-PROGRESS database oratest unknown. (1008)
When I try to connect via the data administration toll I get the following
error message:
Could not connect to "oratest" as user "unifi_app@ora_devl_ms2" This module
can access ORACLE only through the PROGRESS network. (1894)
Can some one show me the correct steps to get the connection going.

GE Capital
__________________________________

Jeffrey Gaiters
Database Specialist

GE Capital Mortgage Services, Inc.
A Unit of GE Capital Mortgage Corporation
856.661.7416, 800.257.7818
Dial Comm 8*243.7416, Fax: 856.661.7171
Email: Jeffrey_Gaiters@mortgage.ge.com
 

Chris Kelleher

Administrator
Staff member
In a message dated 1/8/2000 5:52:36 PM Eastern Standard Time,
Jgaiters@earthlink.net writes:

> PROGRESS V9.B14 (Enterprise DB, Oracle Dataserver)
> Sun E4500 4GB memory, 130 GB disk space
> Oracle version 7.3.4/8.0.4
> I'm looking for help setting up a local Oracle Dataserver in my test
> environment any help will be greatly appreciated. I cannot connect to the
> oracle and progress at the same time.
> My connection steps
> 1. Start oracle database - Oracle database is up and running (I'm testing
> against a 7.3.4 instances)
> 2. Start oracle dataserver broker - $PROBRKR -S unifitora -H
> ral-dev04 -N tcp. Started
> 3. pro oratestds -db oratest -dt oracle -ld orams2 -U
> test_app@ora_devl_ms2 -P test1. I get errors

I skip the -P param in my ver 8.3B. Try:
pro oratestds -db oratest -dt oracle -ld orams2
-U test_app/test1@ora_devl_ms2

> I get the following messages
> non-PROGRESS database oratest unknown. (1008)
> When I try to connect via the data administration toll I get the following
> error message:
> Could not connect to "oratest" as user "unifi_app@ora_devl_ms2" This module
> can access ORACLE only through the PROGRESS network. (1894)
> Can some one show me the correct steps to get the connection going.
>

Regards,
Bill Landin.

The beauty of a diamond is in its simplicity!
 

Chris Kelleher

Administrator
Staff member
Jeff and Bill,

It's been a while since I've worked with the Oracle DataServer, but the -P
shouldn't matter. That's the password to the -U username you specified,
and the error that shows up doesn't say anything about passwords.

I'd look at one of several things:

1. Do you have a local Oracle Data Server license on this server? If not,
there's your problem -- you can't connect to Oracle because you don't have
the license. This is not as outlandish as it seems -- it's entirely
possible that all the ODS licenses are on the clients. A quick review of
your progress.cfg should rule this one in or out.

2. With the -U parameter, you are connecting "username@instancename".
Specifying the "@instancename" enables you to use SQL*Net for client
access, which implies to me that you're trying to make a client/server
connection to the database. From what you described as a local machine, I
am not sure this is what you want to do. Of course, it's been a while, so
take this (and all else) with a grain of salt.

3. On a minor issue, connect to your schema holder read-only (-RO), and
connect to it before connecting to the Oracle database.

I'm sure there are some other suggestions I could present, but it's been
long enough that I don't know what they are...

A few thoughts from a rusty mind... take 'em for what they're worth.

Good luck.

Scott
===============================================================
Scott M. Dulecki /* 1998061901 */ +1 616 975 6322
Product Manager scott_dulecki@qad.com
QAD, Inc. http://www.qad.com
1188 East Paris SE Grand Rapids, MI 49546 USA

Next Michigan Progress Users Group: 19 January 2000

All opinions are my own, and don't necessarily reflect those of
any other living being.
===============================================================
 

Chris Kelleher

Administrator
Staff member
Jeffrey,

You say you want to setup a local Oracle DataServer in your test
environment, yet you are trying to use the remote DataServer broker. You
may want to rethink your Progress-to-Oracle connection approach. If
Progress and Oracle both reside on the same server where you'll be running
the client from, then create a local DataServer executable and forget about
the remote DataServer broker. This simplifies things greatly. If your
Progress and Oracle reside on different Unix servers, then you'll need the
remote DataServer broker and client executables on the Oracle Unix server.

The 1008 and 1894 errors basically mean that the Progress client executable
does not recognize the non-Progress (Oracle) database you've told it to
access. This is typically caused by one of the following things:
a) failure to probuild the Progress client executable to include the local
or remote Oracle DataServer
b) failure to execute the probuild-generated link script to create the
Progress client DataServer executable
c) link failure due to improperly set environment variables such as ORALIB,
ORACLE_HOME or ORACLE_SID during the probuild
d) Using the wrong Progress client executable. For example, I typically
name my client DataServer executable _proora. However, the Progress pro
script calls _progres. So if you created the DataServer with a name other
than _progres, the 1008 and 1894 errors will result because the standard
Progress client executable does not contain the DataServer components.
Also, if you called the DataServer _progres but failed to move it to the
$DLC/bin directory, the pro script is still calling the original client
(non-DataServer) executable and the errors will result.

Those are the typical causes of the 1008 and 1894 errors I've encountered.
They should at least point you in the right direction.

Alan Wahner
Technical Support
QAD, Inc.
 

Chris Kelleher

Administrator
Staff member
I had the same error and the solution was to re-make the progress _prohlc executable. I believe that you need to have some type of networking set up, either the progress networking or sql net.

Mike O.
 

zhonghong

New Member
Jeff,
Bill has made very good points. I'll just give some contribution.
There are 2 ways to connect to Oracle databases from Progress, SQL*NET or TCP/IP, if you use SQL*NET, it's important to set up SQL*NET properly(the way to check is try connect to Oracle database from Oracle SQLPLUS and specify the domain name). If you use Progress client/server infrastructure with TCP/IP, make sure you have your Progress Oracle dataserver product installed local to the Oracle server and make sure you are able to connect to Oracle database through Oracle sqlplus without specifying the domain name.
Good luck!

Zhong Hong
P.S. do you remember me? I was there for a project to merge UNIFI patches a little over a year ago.
<BLOCKQUOTE><font size="1" face="Arial, Verdana">quote:</font><HR>Originally posted by progresstalk:
PROGRESS V9.B14 (Enterprise DB, Oracle Dataserver)
Sun E4500 4GB memory, 130 GB disk space
Oracle version 7.3.4/8.0.4
I'm looking for help setting up a local Oracle Dataserver in my test
environment any help will be greatly appreciated. I cannot connect to the
oracle and progress at the same time.
My connection steps
1. Start oracle database - Oracle database is up and running (I'm testing
against a 7.3.4 instances)
2. Start oracle dataserver broker - $PROBRKR -S unifitora -H
ral-dev04 -N tcp. Started
3. pro oratestds -db oratest -dt oracle -ld orams2 -U
test_app@ora_devl_ms2 -P test1. I get errors
I get the following messages
non-PROGRESS database oratest unknown. (1008)
When I try to connect via the data administration toll I get the following
error message:
Could not connect to "oratest" as user "unifi_app@ora_devl_ms2" This module
can access ORACLE only through the PROGRESS network. (1894)
Can some one show me the correct steps to get the connection going.

GE Capital
__________________________________

Jeffrey Gaiters
Database Specialist

GE Capital Mortgage Services, Inc.
A Unit of GE Capital Mortgage Corporation
856.661.7416, 800.257.7818
Dial Comm 8*243.7416, Fax: 856.661.7171
Email: Jeffrey_Gaiters@mortgage.ge.com

<HR></BLOCKQUOTE>
 

hanifku

New Member
Hi Chris,

I have following problems, My Solaris 64 bit are installed with Oracle 11g and Progress OpenEdge 10.2B, I am using trial Oracle Data Server and licensed oracle because my company are still considering to buy Oracle data server so I need to take test.

My question is, I am trying to connect to my local Oracle instance from local Progress OpenEdge. When I am trying to connect/create data server schema with a correct ORACLE instance (with correct Username/Password), my Progress crashes and automatically quit. Here is the log:

Here is the log from protrace.log:
PROGRESS stack trace as of Tue Oct 26 10:41:11 2010
Command line arguments are
_progres

Startup parameters:
-pf /Web/progress/dlc10/startup.pf,-cpinternal ISO8859-1,-cpstream ISO8859-1,-cpcoll Basic,-cpcase Basic,-d dmy,-numsep 44,-numdec 46,(end .pf)

(1) ??() +0x84942b from: ??
(2) drexit() +0x3f0 from: /Web/progress/dlc10/bin/_progres
(3) drExitOnTerm() +0x228 from: /Web/progress/dlc10/bin/_progres
(4) _thr_slot_offset() +0x5b0 from: /lib/sparcv9/libc.so.1
(5) sema_post() +0x628 from: /lib/sparcv9/libc.so.1
(6) oradbopnf() +0x650 from: /Web/progress/dlc10/bin/_progres
(7) oradbfilck() +0x1c from: /Web/progress/dlc10/bin/_progres
(8) orafilck() +0x90 from: /Web/progress/dlc10/bin/_progres
(9) orascmanb() +0x114 from: /Web/progress/dlc10/bin/_progres
(10) fdscmanb() +0xd0 from: /Web/progress/dlc10/bin/_progres
(11) scrnci() +0xb4 from: /Web/progress/dlc10/bin/_progres
(12) rnreloc() +0x234c from: /Web/progress/dlc10/bin/_progres
(13) rnproc_entry() +0x28f4 from: /Web/progress/dlc10/bin/_progres
(14) rninterpret() +0x50 from: /Web/progress/dlc10/bin/_progres
(15) umeDispatchEvent() +0x144c from: /Web/progress/dlc10/bin/_progres
(16) wvRunDispatcher() +0xb20 from: /Web/progress/dlc10/bin/_progres
(17) iodispatch() +0xd0 from: /Web/progress/dlc10/bin/_progres
(18) rnrq() +0x150 from: /Web/progress/dlc10/bin/_progres
(19) main() +0x648 from: /Web/progress/dlc10/bin/_progres
(20) _start() +0x17c from: /Web/progress/dlc10/bin/_progres

** ABL Stack Trace **

--> prodict/ora/_ora_lkl.p (prodict/ora/_ora_lkl.r) at line 0
prodict/_dctexec.p (prodict/_dctexec.r) at line 978
Perform_Func prodict/_dictc.p (prodict/_dictc.r) at line 3261
USER-INTERFACE-TRIGGER prodict/_dictc.p (prodict/_dictc.r) at line 5119
prodict/_dictc.p (prodict/_dictc.r) at line 6493
_dict.p (/Web/progress/dlc10/tty/_dict.r) at line 417
_RunTool adeedit/_proedit.p (adeedit/_proedit.r) at line 2870
USER-INTERFACE-TRIGGER adeedit/_proedit.p (adeedit/_proedit.r) at line 3100
adeedit/_proedit.p (adeedit/_proedit.r) at line 12279
_edit.p (/Web/progress/dlc10/tty/_edit.r) at line 408

** Persistent procedures/Classes **


And here is from dataserv.lg:
[10/10/22@17:10:22.297+0700] P-012297 T-000001 1 ORA -- Executable was compiled on Nov 24 2009 at 17:39:00 (5067)
[10/10/22@17:10:22.297+0700] P-012297 T-000001 1 ORA -- Login to dataserver db as user HANIF. (2689)
[10/10/22@17:10:22.538+0700] P-012297 T-000001 1 ORA -- Using shared library /database/oracle/product/11.2.0/dbhome_1/lib/libclntsh.so (oci 8.1) (14874)
[10/10/22@17:10:22.538+0700] P-012297 T-000001 1 ORA -- ORACLE_HOME set to '/database/oracle/product/11.2.0/dbhome_1' (14875)
[10/10/22@17:10:22.538+0700] P-012297 T-000001 1 ORA -- ORACLE_SID set to 'ccnbcoba' (14877)
[10/10/22@17:10:22.538+0700] P-012297 T-000001 1 ORA -- OCI call OCIInitialize <0>
[10/10/22@17:10:22.549+0700] P-012297 T-000001 1 ORA -- OCI retr OCIInitialize <0> rc = 0 (11095 us)
[10/10/22@17:10:22.549+0700] P-012297 T-000001 1 ORA -- OCI call OCIEnvInit <0>
[10/10/22@17:10:22.550+0700] P-012297 T-000001 1 ORA -- OCI retr OCIEnvInit <0> rc = 0 (375 us)
[10/10/22@17:10:22.550+0700] P-012297 T-000001 1 ORA -- OCI call OCIHandleAlloc <0>
[10/10/22@17:10:22.550+0700] P-012297 T-000001 1 ORA -- OCI retr OCIHandleAlloc <0> rc = 0 (363 us)
[10/10/22@17:10:22.550+0700] P-012297 T-000001 1 ORA -- OCI call OCILogon <0>
[10/10/22@17:10:22.685+0700] P-012297 T-000001 1 ORA -- OCI retr OCILogon <0> rc = 0 (135135 us)
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- OCI call OCIHandleAlloc <0>
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- OCI retr OCIHandleAlloc <0> rc = 0 (111 us)
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtPrepare <1> sqlcrc = -1
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- ALTER SESSION SET NLS_NUMERIC_CHARACTERS = '.,'
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtPrepare <1> rc = 0 (98 us)
[10/10/22@17:10:22.686+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtExecute <1>
[10/10/22@17:10:22.687+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtExecute <1> rc = 0 (932 us)
[10/10/22@17:10:22.687+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtPrepare <1> sqlcrc = -1
[10/10/22@17:10:22.687+0700] P-012297 T-000001 1 ORA -- ALTER SESSION SET NLS_DATE_FORMAT = 'YYYYMMDDHH24MISS'
[10/10/22@17:10:22.687+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtPrepare <1> rc = 0 (91 us)
[10/10/22@17:10:22.687+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtExecute <1>
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtExecute <1> rc = 0 (678 us)
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtPrepare <1> sqlcrc = -1
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- ALTER SESSION SET TIME_ZONE = '00:00'
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtPrepare <1> rc = 0 (77 us)
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtExecute <1>
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtExecute <1> rc = 0 (258 us)
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtPrepare <1> sqlcrc = -1
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- SELECT VALUE FROM NLS_SESSION_PARAMETERS WHERE PARAMETER = 'NLS_T
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- IMESTAMP_FORMAT'
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtPrepare <1> rc = 0 (110 us)
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI call OCIDefineByPos <1>
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- OCI parm OCIDefineByPos <1>
[10/10/22@17:10:22.688+0700] P-012297 T-000001 1 ORA -- type 5 var :1 addr: 0x7fffe954 size 50/0 value: '...'
[10/10/22@17:10:22.689+0700] P-012297 T-000001 1 ORA -- OCI retr OCIDefineByPos <1> rc = 0 (143 us)
[10/10/22@17:10:22.689+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtExecute <1>
[10/10/22@17:10:22.689+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtExecute <1> rc = 0 (912 us)
[10/10/22@17:10:22.690+0700] P-012297 T-000001 1 ORA -- -Dsrv qt_debug: 122879 (0x1dfff Verbose) (6489)
[10/10/22@17:10:22.690+0700] P-012297 T-000001 1 ORA -- Cursor limit: 84 (-c setting) (6490)
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- OCI call OCIHandleAlloc <0>
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- OCI retr OCIHandleAlloc <0> rc = 0 (205 us)
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtPrepare <2> sqlcrc = 46181
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- SELECT /*+ ROWID(T0) */ USER#,NAME FROM sys.user$ T0
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtPrepare <2> rc = 0 (110 us)
[10/10/22@17:10:38.855+0700] P-012297 T-000001 1 ORA -- OCI call OCIStmtExecute-DescribeOnly <2>
[10/10/22@17:10:38.858+0700] P-012297 T-000001 1 ORA -- OCI call OCIErrorGet <0>
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI retr OCIErrorGet <0> rc = 0 (295 us)
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI retr OCIStmtExecute-DescribeOnly <2> rc = -1 (338 us)----------
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI call OCIErrorGet <0>
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI retr OCIErrorGet <0> rc = 0 (96 us)
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI call omru <2>
[10/10/22@17:10:38.859+0700] P-012297 T-000001 1 ORA -- OCI call OCIHandleAlloc <0>
[10/10/22@17:10:38.860+0700] P-012297 T-000001 1 ORA -- OCI retr OCIHandleAlloc <0> rc = 0 (75 us)
[10/10/22@17:10:38.860+0700] P-012297 T-000001 1 ORA -- SYSTEM ERROR: Memory violation. (49)
[10/10/22@17:10:38.860+0700] P-012297 T-000001 1 ORA -- ** Save file named core for analysis by Progress Software Corporation. (439)

The error is : MEMORY VIOLATION.

And how do I can workaround this? Need suggestion. Thanks
 
Top