Hello Folks,
Here's wishing you MERRY CHRISTMAS and Festive seasons's greeting!!

Now this has been bugging me for quite a while and I seek your help in
setting my mind to peace.
As part of DB2 Instance creation on Unix, I issue this command (from
standard script):
__________________________________________________ _______
"db2iexec db2inst1 . sqllib/db2profile"
__________________________________________________ _______
[db2inst1 is the DB2 instance name]

ENVIRONMENT: DB2 UDB ESE 8.1 FPx on AIX 5.x

QUESTIONS:
(1) What does this command do (Do I really achieve anything)?
(2) What can happen if I skip this command?

TiA..................anurag

Anurag wrote:

> Hello Folks,
> Here's wishing you MERRY CHRISTMAS and Festive seasons's greeting!!
>
> Now this has been bugging me for quite a while and I seek your help in
> setting my mind to peace.
> As part of DB2 Instance creation on Unix, I issue this command (from
> standard script):
> __________________________________________________ _______
> "db2iexec db2inst1 . sqllib/db2profile"
> __________________________________________________ _______
> [db2inst1 is the DB2 instance name]
>
> ENVIRONMENT: DB2 UDB ESE 8.1 FPx on AIX 5.x
>
> QUESTIONS:
> (1) What does this command do (Do I really achieve anything)?
> (2) What can happen if I skip this command?

db2iexec is not exactly supported for use outside of DB2 install and
instance management tools - otherwise it would be documented in the command
reference ;-)

That command does nothing. It becomes db2inst1 (using 'su' - which means
that this only works if you're already root), runs ". sqllib/db2profile",
and then exits, losing any changes to the environment that db2profile does.

As it does nothing (it's an expensive no-op), nothing will happen if you
skip that command.