UDB Commands

[Raquel]

Ok...So there is a "CREATE DATABASE" command to create a Database (as
a "CLP" command), while there is a "db2icrt" command (as a "System"
Command) to create an instance...why such variation? Why is there not
a "CREATE INSTANCE" command?

TIA Raquel.

[Lee Dilworth]

Re: UDB Commands

Instance creation requires changes to be made at the OS level, this is the
key really. db2icrt requires either root (unix) or local admin (windows) to
run. During instance creation it is necessary to run operating system
commands using these high authority levels to ensure that the instance is
created correctly and the appropriate files / services are setup.

On unix for example the userid passed to db2icrt will have a directory
created (sqllib) in $HOME by default, symlinks will also be created in
sqllib back to your install directory (/usr/opt for example), entries will
also be added to various system files owned by root such as /etc/services,
files in /var/db2 (so root authority is required to edit these). Similar
files will be edited on windows also on windows the local admin userid has
the authority to create the windows service for your new instance.

Once the instance is created your userid can now source the db2profile to
setup the correct environment variables, then run the db2 commands from an
initialized command line environment. Your installation is complete.

From a self preservation point of view it is also probably a very GOOD thing
that there is no CREATE/DROP INSTANCE combination of commands that could be
run as your SYSADM users...imagine running DROP INSTANCE at the wrong moment
:)

"Raquel" <raquel_rodrigu ezus@yahoo.com> wrote in message
news:9a73b58d.0 312050751.2732d 380@posting.goo gle.com...[color=blue]
> Ok...So there is a "CREATE DATABASE" command to create a Database (as
> a "CLP" command), while there is a "db2icrt" command (as a "System"
> Command) to create an instance...why such variation? Why is there not
> a "CREATE INSTANCE" command?
>
> TIA Raquel.[/color]