Instance home dir = /export/home/db2inst1, Sysadm group = db2iadm1
Instance type = 3, Auth type = SERVER
SQL10007N Message "-1390" could not be retrieved. Reason code: "5".
Update DBM cfg SYSADM_GROUP errcode = 8
DBI1281E The database manager configuration file could not
be initialized.
Cause: An error occurred when attempting to initialize the
database manager configuration file. A DB2 Version 5
instance could not be created or migrated.
I've located the script line that falls over. It is in the
/opt/IBMdb2/V5.0/instance/db2idbm file at:-
#-----------------------------------------------------------------------
# Update the database manager configuration file to set SYSADM_GROUP to
# the specified group. Check for SQL6031N message.
#-----------------------------------------------------------------------
errmsg=`db2 update database manager configuration using SYSADM_GROUP
${SysAdmGrp?} 2>&1 `
errcode=$?
echo "${errmsg?}" >> ${TmpFile?}
errnum=`echo ${errmsg?} | /usr/bin/tail -1 | /usr/bin/awk '{print $1}'`
if [ ${errcode?} -ne 0 ]; then
echo "Update DBM cfg SYSADM_GROUP errcode = ${errcode?}" >>
${TmpFile?}
if [ "X${errnum?}" = "XSQL6031N" ]; then
# Assumption: The reason code for SQL6031N is 11.
echo " >>>>> Error message = ${errmsg?} <<<<< " >> ${TmpFile?}
exit_db2idbm 2
else
exit_db2idbm 1
fi
fi
The db2 statement cannot be executed.
John (jpmc...@hotmail.com)
It is common for instance creation to fail if installing for the first time
on Solaris, especially when updating the database manager parameters.Usually
because the /etc/system file does not contain the correct parameters. Here
is what to try. Do not let the db2setup program create the instance.
Instead after installing DB2, manually create the instance with the db2icrt
command after updating the /etc/system file and rebooting.
In the /opt/IBMdb2/V5.0/cfg directory there are several kernel parameter
sample files that can be used for the /etc/system file.
Hope it helps.
Cheers,
Howin.
---------------
You should also check that the DB2 instance owners environment variables
are set correctly. You should check the following:
default shell is ksh
LC_ALL = en_US
LANG = en_US
The LANG and LC_ALL can be check by running the command locale. I ran
into the same problems that you are having when I installed NC on
solaris.
HTH
david kutcipal
In article <37E7AADF...@ca.ibm.com>,
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
DB2 5.0 does not support Solaris 2.7. There are two options:
1. Upgrade to DB2 5.2 (I think you can do this by applying some FixPaks -
see DB2 web site). DB2 5.2 supports Solaris 2.7.
2. Use the following workarounds taken from the NC troubleshooting info for
a recent release:
A) While creating the DB2 instance, you encounter an error message like:
SQL10007N Message "-1390" could not be retrieved. Reason code: "5"
a. Log on as root.
b. Edit the file /etc/profile. Add the following line:
LANG=en_US; LC_ALL=en_US; export LANG LC_ALL
c. Source the profile.
d. Rerun the DB2 instance creation steps.
B. While creating a Net.Commerce instance, you encounter the following error
message:
Cannot create database xxxx.
where xxxx is the name of your database.
a. Log on to the database instance ID.
b. Edit the file .profile.
c. Ensure the following two lines are present:
export LANG=C
export LC_ALL=C
If these two lines are not in the file, add them and also add the
following two lines:
export LANG=en_US
export LC_ALL=en_US
d. Delete the Net.Commerce instance and recreate it using the
Configuration Manager.
Some additional information about installing DB2 on Solaris:
When installing DB2 on Solaris:
1. You MUST set your Solaris kernel parameters as outlined in the
Pre-Installation requirements of the NC 3.1.2 or NC 3.2 Solaris Install
Guide. If you do not set the Solaris kernel parameters correctly, DB2 will
be unable to create an instance.
2. After install, the DB2 instance ID must run in the Korn shell.
3. DB2 creates the instance user ID under the /export/home directory. This
directory must exist before you begin to install DB2 UDB. If the directory
does not exist, the DB2 instance creation will fail.
4. If you have uninstalled a previous version of DB2 from your machine,
ensure that all DB2 files, user IDs and groups have been deleted. If there
is any DB2 information or any DB2-related files left on the system, you may
be unable to successfully install DB2 or create the instance. The NC 3.1.2
Solaris Install Guide (available from: www.ibm.com/net.commerce) has
complete uninstall instructions for DB2 in the Appendix.
5. If you are using NIS (Network Information Services), you must disable it
before installing DB2. If you do not disable NIS, the DB2 instance will not
be created.
Hope this information helps,
Maureen Foulds
IBM Net.Commerce, Install Test Team Lead