nick.battle@gmail.com wrote:
> Incidentally, if we did use Memory Windows, the easiest thing for us to
> do would be to split the application and Oracle (9i) into their own
> windows - Oracle is a large user of shared memory in Q3.
>
> But does that work: can an application be the client of an Oracle
> database running in a different memory window? (If the communication
> between the two relies on shared memory, this might be a problem...?).

If they literally rely on attaching to each other's shared memory - then
no, that wouldn't work to have them in different windows. Whichever
app created the new shared object would succeed, but the other app
would fail to attach.

(Unfortunately, I don't know the details of how Oracle handles their
client communication...).

If they create *new* segments to communicate between the client and
the database server, and said segments are created using IPC_GLOBAL,
then things would be okay. But you'd have to check with Oracle to
see if that's the way things work. (Oracle supply you with any
HP-UX documentation? A quick search on their site with "HP-UX
memory windows" apparently liked "Windows" more than the other
terms, which wasn't helpful).

Don