On Dec 26, 9:52 am, Darin McBride
<dmcbr...@naboo.to.org.no.spam.for.me> wrote:
> (The other thing it does on unix is gets rid of any server-based executables
> from sqllib/adm if you use -s client, to save a bit of space and a bit of
> confusion.)
I may be wrong, but I thought those files in sqllib were only symbolic
links to the install directory.
swami - 26 Dec 2007 18:55 GMT
I am getting
[db2inst2@SIVA ~]$ db2 "get dbm cfg" | grep -i node
Node type = Database Server with local and remote clients
[db2inst2@SIVA ~]$
for -s wse.
> On Dec 26, 9:52 am, Darin McBride
>
[quoted text clipped - 5 lines]
> I may be wrong, but I thought those files in sqllib were only symbolic
> links to the install directory.
Laurence - 27 Dec 2007 12:08 GMT
Yes,
As I create instance for the -s option with ese value, the Node Type
of dbm cfg is like below:
"Node type = Enterprise Server Edition with local and remote clients"
As I create instance for the -s option with wse value, the Node Type
of dbm cfg is like below:
"Node type = Database Server with local and remote clients"
Thank you and for your information!
Laurence
Darin McBride - 28 Dec 2007 05:39 GMT
> On Dec 26, 9:52 am, Darin McBride
> <dmcbr...@naboo.to.org.no.spam.for.me> wrote:
[quoted text clipped - 4 lines]
> I may be wrong, but I thought those files in sqllib were only symbolic
> links to the install directory.
Almost all of them are. Some are physical files - you can't do
setuid-instance-owner via symlink (because it gets difficult when you have
more than one instance). Almost all of these are in sqllib/adm.