HP3000-L Archives

May 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Philip E. Test" <[log in to unmask]>
Reply To:
Philip E. Test
Date:
Sat, 27 May 1995 05:40:24 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Denys Beauchemin ([log in to unmask]) wrote:
: Just to reinforce what George said;  2 weeks ago, I installed the Oracle
: transparent gateway on an HP3000 and mapped it to an IMAGE/SQL database.  The
: gateway was accessed from an Oracle instance on an HP9000 and, using a
: database link, the Oracle instance happily pointed to the IMAGE data and
: retrieved it quite nicely, thank you very much.
 
I find this interesting also.  Depending on the type and volume of access,
and the database structure, it is potentially an effective solution for
providing end-user SQL reporting.
 
Consider the type of reporting to be done and the IMAGE database structure
to determine if the load on the IMAGE database, the HP3000, and your network
would be acceptable.  Periodic (i.e. daily) Oracle table population would
be the alternative, although the gateway might be used to do this while
creating view(s) most effective for the reporting to be performed.
 
If necessary, data stored in sequential and KSAM files probably require use
of SQL*Loader, and you'll probably want to add indexes for this data also.
 
I'm curious whether IMAGE databases could be updated over the gateway.
That could open up some additional migration paths for us.
 
Philbert

ATOM RSS1 RSS2