help: cannot create instance
Frank Zeng
I just installed DB2 UDB EEE V5.2 and then tried to create an
instance with "db2icrt -u db2inst1 db2inst1", and I raninto the
following problem:
No valid service name or port number found.
The same error occured after I added two entries to the file
/etc/services for the main and interrupt port.
I really need your help. TIA
Frank
Frank Zeng
PS: The system is AIX 4.3.2.
Darin McBride
Possibility #1:
Read the help for error message SQL6031:
db2 ? sql6031 | more
Possibility #2:
Somehow the instance owner can't access something. Try becoming the instance
owner (-to-be) and creating a file in the directory. (The sqllib directory
probably isn't there, but, if it is, try writing there, too.) If you can,
it's obviously another problem, but, if you can't, check the rwx permissions
up the tree.
Frank Zeng
Darin McBride wrote:
Thanks.
To Possibility #1:
I can' execute "db2 ? sql6031 | more", because I haven't create any instance yet.
To Possibility #2:
The user to execute the command "db2icrt" must be super user, so I am sure that
it has the write permission in the directory. Is it possible due to the NIS
problem? I found the /etc/services files was updated regularly. However, even I
use the port existed, the same error occured.
Darin McBride
Oh, right. Of course. :-)
SQL6031N Error in the db2nodes.cfg file at line number
"<line>". Reason code "<reason code>".
Explanation: The statement cannot be processed because of a
problem with the db2nodes.cfg file, as indicated by the following
reason codes:
(1) Cannot access the sqllib directory of the instance.
(2) The full path name added to the db2nodes.cfg filename is too
long.
(3) Cannot open the db2nodes.cfg file in the sqllib directory.
(4) A syntax error exists at line "<line>" of the db2nodes.cfg
file in the sqllib directory.
(5) The nodenum value at line "<line>" of the db2nodes.cfg file
in the sqllib directory is not valid.
(6) The nodenum value at line "<line>" of the db2nodes.cfg file
in the sqllib directory is out of sequence.
(7) The nodenum value at line "<line>" of the db2nodes.cfg file
in the sqllib directory is not unique.
(8) The port value at line "<line>" of the db2nodes.cfg file in
the sqllib directory is not valid.
(9) The hostname/port couple at line "<line>" of the db2nodes.cfg
file in the sqllib directory is not unique.
(10) The hostname at line "<line>" of the db2nodes.cfg file in
the sqllib directory is not valid.
(11) The port value at line "<line>" of the db2nodes.cfg file in
the sqllib directory is not defined for your DB2 instance id in
the services file (/etc/services on UNIX-based systems).
(12) The port value at line "<line>" of the db2nodes.cfg file in
the sqllib directory is not in the valid port range defined for
your DB2 instance id in the services file (/etc/services on
UNIX-based systems).
(13) The hostname value at line "<line>" of the db2nodes.cfg file
in the sqllib directory has no corresponding port 0.
(14) A db2nodes.cfg file with more than one entry exists, but the
database manager configuration is not MPP.
User Response: The action corresponding to the reason code is:
(1) Ensure that the $DB2INSTANCE userid has the required
permissions to access the sqllib directory of the instance.
(2) Make the instance home directory path name shorter.
(3) Ensure that the db2nodes.cfg file exists in the sqllib
directory and is not empty.
(4) Ensure that at least 2 values are defined per line in the
db2nodes.cfg file and that the file does not contain blank
lines.
(5) Ensure that the nodenum value defined in the db2nodes.cfg
file is between 0 and 999.
(6) Ensure that all the nodenum values defined in the
db2nodes.cfg file are in ascending order.
(7) Ensure that each nodenum value defined in the db2nodes.cfg
file is unique.
(8) Ensure that the port value is between 0 and 999.
(9) Ensure that the new couple hostname/port is not already
defined in the db2nodes.cfg file.
(10) Ensure the hostname value defined in db2nodes.cfg at line
"<line>" is both defined on the system and operational.
(11) Ensure that the services file (/etc/services on UNIX-based
systems) contains an entry for your DB2 instance id.
(12) Ensure that you only use port values that are specified in
the services file (/etc/services file on UNIX-based systems) for
your instance.
(13) Ensure that the port value 0 has been defined for the
corresponding hostname in the db2nodes.cfg file.
(14) Perform one of the following actions:
o Remove the db2nodes.cfg file.
o Alter the db2nodes.cfg file to contain exactly one entry.
o Install the DB2 Enterprise - Extended Edition server.
>To Possibility #2:
>The user to execute the command "db2icrt" must be super user, so I am sure that
>it has the write permission in the directory. Is it possible due to the NIS
But some of the instance create is done by the user itself. Thus the user
must have write permission to its own directory.
NIS is its own problem - but this shouldn't be it.