Oracle Hell
i'm creating offsite packages for a customer that wants Oracle client 10 + odac components + patch 10.2.04.
I went for repackaging the stuff.
so far ok for the Oracle client and odac components, but after the installation of the patch, I get an error "the procedure entry point ocipisconnectstringbeq could not be located in the oci.dll".
Ok, so far for my promise to deliver this package today ...
fyi: the client and odac components have no advertising left
I hope messing with the procmon/regmon will help me further with this
or should I go for one big package instead of three separate?
the other thing that bothers me is that according to the customer I have to install the odac components before applying the oracle client patch. If this wouldn't be the case, I might create a patch package of it instead of a setupcapture
going for the response file is my last option, but since I do not have any physical access to the client's environment this might only postpone the implementation (what about av?, altiris deployment behavior, ?)
after all these years, why the ***** is oracle still going for this universal installer crap?
I went for repackaging the stuff.
so far ok for the Oracle client and odac components, but after the installation of the patch, I get an error "the procedure entry point ocipisconnectstringbeq could not be located in the oci.dll".
Ok, so far for my promise to deliver this package today ...
fyi: the client and odac components have no advertising left
I hope messing with the procmon/regmon will help me further with this
or should I go for one big package instead of three separate?
the other thing that bothers me is that according to the customer I have to install the odac components before applying the oracle client patch. If this wouldn't be the case, I might create a patch package of it instead of a setupcapture
going for the response file is my last option, but since I do not have any physical access to the client's environment this might only postpone the implementation (what about av?, altiris deployment behavior, ?)
after all these years, why the ***** is oracle still going for this universal installer crap?
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
audifreakje
15 years ago
thx for nothing
and yes I do have several years of packaging experience
guess I just wasted my time whilst typing out my problem
and yes I do have several years of packaging experience
guess I just wasted my time whilst typing out my problem
Posted by:
anonymous_9363
15 years ago
and yes I do have several years of packaging experienceGood for you. It was the statement "fyi: the client and odac components have no advertising left" that drew me to come to the opposite conclusion. It makes no sense to me. Thinking laterally, perhaps you meant that the patch has replaced advertised shortcuts with non-advertised ones?
As for wasting your time, you certainly did as far as the error with OCI.DLL is concerned, since you already know that ProcMon will show you what's going on there. To my mind, the patch has either changed the path, removed that file,or - less likely - replaced it with one which doesn't contain that entry-point. A snapshot with a lightweight snapshot tool will narrow that down.
Posted by:
MSIPackager
15 years ago
Ok, so far for my promise to deliver this package today ...
1 day to package up the Oracle 10 Client - that is brave.
Much as the OUI isn't the nicest thing to use, it works perfectly well and (as Ian said) removed the headache of managing the Oracle Home/s.
Perhaps you should reconsider.. I Don't really get your reasons for not using it.. surely deployment testing and UAT is part of the packaging process?
Cheers,
Rob.
Posted by:
jmcfadyen
15 years ago
if you insist on repackaging it I have posted how to do this numerous times in the past in this forum and the wise forums and included the necessary CA's and code to handle the Oracle homes stuff.
Its quite a hassle I just did it for kicks as I often find myself underworked. Boredom would be about the only reason I would attempt this.
if you search for OracleRegFix and OracleMsiFix or ask Owen Gilmore for the code I wrote u should be ok. I even wrote a macro for wise to automate the pain (that day I was very bored).
is it worth the effort probably not. up to you :-)
Its quite a hassle I just did it for kicks as I often find myself underworked. Boredom would be about the only reason I would attempt this.
if you search for OracleRegFix and OracleMsiFix or ask Owen Gilmore for the code I wrote u should be ok. I even wrote a macro for wise to automate the pain (that day I was very bored).
is it worth the effort probably not. up to you :-)
Posted by:
InterneToughGuy
15 years ago
Why do these versions of Oracle need to be installed in a certain order?
Posted by:
aogilmor
15 years ago
I hope he doesn't call me on that coz I'm not sure if I can even find it!
OG
OG
Posted by:
sbequette
15 years ago
pretty sure the issue is you are letting Wise/Installshield figure out which Dll's to register. if you don't register any of the dll's/OCX's in the package that error will go away. (and Oracle will work).
Posted by:
anonymous_9363
15 years ago
if you don't register any of the dll's/OCX's in the package that error will go away. (and Oracle will work).Ssssssooooooooooo....your contention is that not registering ANY of the Oracle DLLs or OCXs is the way to go. Hmmmm....
Out of curiousity, I ran my script which finds all DLLs and OCXs with the DLLRegisterServer entry-point and extracts the COM info to .REGs using WiseComCapture. I stopped it running when it passed 30.
I think what you meant to say was to remove any entries in the SelfReg (and, if using IS, the ISSelfReg) table and instead use the advertising tables.
Posted by:
jmcfadyen
15 years ago
so just for shits and giggles i thought i would add this in.
(agree with Ian as always)
the site i am on currently has adopted the packaging oracle route (site shall remain nameless) I see multiple versions all sharing Home0 and ID0
strangely coincidental the support teams are casually groaning about oracle issues when multiple versions are installed on a single machine.
so to close this one off if you don't understand the implications of packaging Oracle dont do it.
ps i found the scripts too just by chance if you want em. they are a little old and slightly wrong but the general idea is there if you can be bothered updating them (cant find the working set, cant be bothered looking either).
(agree with Ian as always)
the site i am on currently has adopted the packaging oracle route (site shall remain nameless) I see multiple versions all sharing Home0 and ID0
strangely coincidental the support teams are casually groaning about oracle issues when multiple versions are installed on a single machine.
so to close this one off if you don't understand the implications of packaging Oracle dont do it.
ps i found the scripts too just by chance if you want em. they are a little old and slightly wrong but the general idea is there if you can be bothered updating them (cant find the working set, cant be bothered looking either).
Posted by:
anonymous_9363
15 years ago
- Only the very brave (or foolish) would re-package Oracle. And, with the greatest respect to those who have, please resist the temptation to tell us that it can be done. We *KNOW* it can be but look at the OP's question and ask if you think that he/she has the necessary expertise (no offence, BTW!)
If nothing else gets in the way, one of the most important questions connected with re-packaging this behemoth is:
how are you going to handle the client's ORACLE_HOME or worse, ORACLE_HOMEs, plural?
- Why is Oracle persisting with OUI? My understanding is that the same installer is used for all platforms (you probably noticed that OUI is a Java app).
If nothing else gets in the way, one of the most important questions connected with re-packaging this behemoth is:
how are you going to handle the client's ORACLE_HOME or worse, ORACLE_HOMEs, plural?
- Why is Oracle persisting with OUI? My understanding is that the same installer is used for all platforms (you probably noticed that OUI is a Java app).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.