Oracle9i MSI package
I am working on Oracle9i msi package using Wise packager that comes with Altiris. I have a good working package except for one small problem. I get garbage in the drop down box of the Oracle in Orahome90 driver TNS Service Names instead of the server list from the tnsnames.ora file being propagated. Does anyone have any good ideas how I might fix this ??? thankyou ..
Vegas Luna
Vegas Luna
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
spartacus
17 years ago
Hello,
Can I ask how the tnsnames.ora file was created - manually, or via Net Manager ?
It may be worth a try opening the existing tnsnames.ora file in Notepad, selecting and copying all the text in it to the clipboard, then renaming the original tnsnames.ora and creating a new tnsnames.ora in notepad and pasting back the contents you just copied.
Make sure you save the new file as ANSI, not Unicode just to be on the safe side.
As an aside, it's been my own experience that many corporates do not like to include tnsnames.ora (or sqlnet.ora for that matter) in their repackaged Oracle applications.
Instead, they choose to distribute it/them from a central location via some another mechanism (e.g. logon script &c). This is presumably because these are potentially volatile files subject to fairly frequent change / additions.
If included, MSI self-healing, for example might revert these files to an outdated state.
Regards,
Spartacus
Can I ask how the tnsnames.ora file was created - manually, or via Net Manager ?
It may be worth a try opening the existing tnsnames.ora file in Notepad, selecting and copying all the text in it to the clipboard, then renaming the original tnsnames.ora and creating a new tnsnames.ora in notepad and pasting back the contents you just copied.
Make sure you save the new file as ANSI, not Unicode just to be on the safe side.
As an aside, it's been my own experience that many corporates do not like to include tnsnames.ora (or sqlnet.ora for that matter) in their repackaged Oracle applications.
Instead, they choose to distribute it/them from a central location via some another mechanism (e.g. logon script &c). This is presumably because these are potentially volatile files subject to fairly frequent change / additions.
If included, MSI self-healing, for example might revert these files to an outdated state.
Regards,
Spartacus
Posted by:
BigGuy_NZ
17 years ago
With Oracle, it's really fussy about what case the characters are from BIN\ onwards in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Oracle in OraHome92.
I had to change:
Driver entry from C:\PROGRA~1\Oracle\Ora92\bin\sqora32.dll to C:\PROGRA~1\Oracle\Ora92\BIN\SQORA32.DLL
and
Setup entry from C:\PROGRA~1\Oracle\Ora92\bin\sqoras32.dll to C:\PROGRA~1\Oracle\Ora92\BIN\SQORAS32.DLL
NOTE: all uppercase from BIN onwards.
Go figure [8|]
I had to change:
Driver entry from C:\PROGRA~1\Oracle\Ora92\bin\sqora32.dll to C:\PROGRA~1\Oracle\Ora92\BIN\SQORA32.DLL
and
Setup entry from C:\PROGRA~1\Oracle\Ora92\bin\sqoras32.dll to C:\PROGRA~1\Oracle\Ora92\BIN\SQORAS32.DLL
NOTE: all uppercase from BIN onwards.
Go figure [8|]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.