OpenInsight and Oracle (OpenInsight Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== OpenInsight and Oracle (OpenInsight Specific) ====
=== At 05 NOV 1997 03:38:25AM Peter Bowyer wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
Does anyone have any experience or advise when using Oracle and OpenInsight? I understand that OI can link to Oracle but have never used it so any advise would be appreciated.



Thanks

Peter Bowyer
</QUOTE>
----

=== At 05 NOV 1997 07:43AM Cameron Revelation wrote:  ===

<QUOTE>Peter,



[i]Does anyone have any experience or advise when using Oracle and OpenInsight? I understand that OI can link to Oracle but have never used it so any advise would be appreciated.[/i]



First, you need Oracle.  There are a couple of flavors, some local (like Personal Oracle) and some networked (like Oracle Workgroup Server on NT, which we use in-house for testing).



Second, there are several ways to hook up to Oracle.  First you can use SQL*Net, which is Oracle's communication layer.  There is the original SQL*Net, which works fine, and SQL*Net v2, which has some glitches with earlier versions but we are using the 2.3.3 release and it is working excellently.  There is one additional communication option you have, which is to use an ODBC driver that implements its own communication layer; for example [url=http://www.openlink.co.uk/]OpenLink Software[/url] provides Oracle ODBC drivers that are reported to be pretty without using (and specifically because they don't use) SQL*Net.



Third, you need to decide whether to use ODBC or go direct to Oracle (the Oracle direct Connection Object uses their low-level OCI interface).  If you are using ODBC, you will need to get and configure a driver.  Either way, go to the Connection Defaults dialog in the Client Server Workspace (under the Tools menu) and select the data source type you want (either Oracle or ODBC) as your default.



If you are using ODBC, you need to set up an ODBC data source before setting up OpenInsight's Connection definition.  Then you need to set up a Connection definition in OpenInsight.  Go to the Client Server Workspace, select New from the File menu, choose Connection, and:



If you are using the Oracle direct connection, select "Oracle" from the "Data Source Type" drop-down and enter a "host string".  That is all that is needed.  For SQL*Net v1, the connection string looks like "t:oracle:orcl" (protocol, host, database).  For SQL*Net v2, the connection string is a name that has been registered on your workstation using the "Oracle for Windows SQL*Net Easy Configuration Tool".



If you are using the ODBC Connection Object instead, select "ODBC" from the drop-down and supply the name of the data source.  (Double clicking on the data source cell will give you a list of all known ODBC 16-bit data sources.)



Save the connection definition and you are ready to go.  Select "Query Window" from the "Tools" menu.  Select the data source you just created, enter a login (like "SCOTT"), password (like "TIGER"), press "Advanced" to set some more options (like Timeout=30).  Press OK to connect.  If you are using the ORCL database, SCOTT/TIGER should log you in, and there should be a sample table named "EMP" or "EMPS" or something like that.  In the query portion of the Query Window, type "select * from emp".  Choose "Execute" from the "Query" menu (or press Ctrl-E).  There you go!



Cameron. Revelation

-----------------------------41792361811089--

</QUOTE>

----

=== At 05 NOV 1997 11:10AM dsig    (SigSOlutions) wrote:  ===

<QUOTE>In addition to Camerons post ..



We have had some problems off and on with the connection

to Oracle .. specifically using Sql*Net 2.x.  There

has been finger pointing etc but it looks like it

has become a stronger connection.  We will be doing

more testing starting the Dec 1.



As for testing in the Query window .. note that there

is a BUG in the qw which will not return data on

large queries.  THis has been reported to RTI and 

put down as a low priority.  Not to be fixed in 3.5



If you are going to use OI with CS you will probably

want to perform much of your work with XO instead of

dataset as it gives you greater control over the

processes and it does not incur the overhead associated

with datasets.  



For example we have generated a 'mfs' which works

against Oracle tables just as if they were LH tables.

The OI windows know no difference.



dsig

David Tod Sigafoos ~ SigSolutions

dsig@teleport.com  voice: 503-630-8080  cis:70302,77



**  NOTICE FOR RTI FORUMS:

**  The message above is an answer to a user request and should

**  be taken as personal opinion only.

**

**  Although care was taken to not hurt anyones feelings or impugn

**  the quality of any product, support or idea IF there is an 

**  exception taken please note in detail the offending portion of

**  the note and email me.  I will take all notes under advisement.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=76D560E7D07E768B85256546002F769C|View this thread on the  forum...]]