| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4944.1 | Not that I know | 4177::UWAHLQVI | | Thu Jan 23 1997 07:25 | 7 |
| 4944.2 | | ORAREP::METSYS::THOMPSON | | Wed Jan 29 1997 11:24 | 11 |
|
DEC/EDI Software uses SQLMOD in ObjectBroker Implementation Servers and
it all works. Theres no fundamental reason why there should be any problems.
The only real disconnect is that ObjectBroker wishes to manage process
creation and it may not always do what you want it to do. E.g. if your
system has RDB Multiversion and you depend upon a login procedure to
call @sys$library:rdbvms_setver. But these only require planning and
are not too difficult to resolve.
M
|
| 4944.3 | How to rdb$setver from Objectbroker? | chsr38.ch.oracle.com::ROHR | The Packers did it! | Thu Mar 06 1997 10:24 | 20 |
| I knew there was more I should know about Objectbroker ;-)
We have an executable we wish to run under V7. The executable has been
compiled and linked under V7 environment and works ok when we set
rdb$setver to V7 before running the image.
But this V7 compiled image is called from object broker where we dont
have the opportunity to run rdb$setver V7 before calling the executable.
The error message is NOENTRYPT.
How do we run this executable compiled under V7 with a default V6
environment?
I requested the customer to log a call with DEC as what we really need
is defining symbols and logicals from within objectbroker, but if
anyone knows?
Thanks,
Regina
|
| 4944.4 | | svrav1.au.oracle.com::MBRADLEY | I was dropped on my head as a baby. What's your excuse? | Thu Mar 06 1997 18:13 | 13 |
| Regina,
Hoqw about :-
$ @sys$library:rdb$setver 7.0 /system
or
$ @sys$library:rdb$setver 7.0 /group
G'day,
Mark.
|
| 4944.5 | | CHSR38::ROHR | The Packers did it! | Fri Mar 07 1997 02:35 | 10 |
| Mark,
they have multiversion and they do run objectbroker against both
versions. So whatever version you set to system, it will not be the one
wanted from another program.
I don't know if Objectbroker's agents can do will make use of group
logical names. I will check into this.
/Regina
|
| 4944.6 | | svrav1.au.oracle.com::MBRADLEY | I was dropped on my head as a baby. What's your excuse? | Tue Mar 11 1997 23:21 | 10 |
| Regina,
Well any one process can only be using a particular rdb version, so I
presumed that the processes that want to use Rdb7 could run setver from
their login.com, or perhaps could be isolated to a particular UIC group in
which case setver /group could be used.
G'day,
Mark.
|
| 4944.7 | | ORAREP::METSYS::THOMPSON | | Sat Mar 15 1997 10:44 | 25 |
|
Without knowledge of how their application is constructed it is difficult
to offer any advise.
ObjectBroker usually does run "Implementation Servers" in the context of
a process that it starts itself. When they start processes they do run
a procedure: sys$login:obb$login.com for the account that the Implementation
Server runs under. For DEC/EDI this is just fine as we only use one version
of the Database, no matter what proxy is used.
If your application sends requests, that require different RDB versions,
to Implementation servers that all run from the same account - then this
method will not work.
You would need some 'out of band' signaling method to the obb$login.com
procedure.
I think this area is a weakness of Oracle RDB and ObjectBroker. RDB should
have a routine you can call to change versions, ObjectBroker should let you
have more control over process environment. However this would represent
a significant design change for both products.
Mark
|