467,864 Members | 1,979 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,864 developers. It's quick & easy.

SQL6048N/DBI1281E on SuSE 9, doesn't go away after reinstall

Hi,

I'm having a hard time getting ESE 8.1 to run on a freshly installed
SuSE 9.0 linux box. It was actually up and running, but after a reboot
(one disk in the RAID 5 had to be replaced) it wouldn't start, saying
SQL6048N (communication error, see below).

As it was a test installation on a newly installed server I decided to
throw the DB2 installation away and start again (uninstalling DB2 and
removing everything DB2-related from /etc/, /var/db2 and /opt, and
removing the DB2 specific users).

Now, unfortunately, whenever I install from scratch and try to create an
instance, db2icrt complains about

SQL6048N A communication error occurred during START or STOP DATABASE
MANAGER
processing.
Update DBM cfg SYSADM_GROUP errcode = 8
DBI1281E The database manager configuration file could not be
initialized.
(from db2icrt.log.xxxx)

I've tried quite a lot - if not all - possible combinations of

- using db2setup or db2icrt to create instances
- letting db2setup create the users, or create them beforehand
- making sure that rsh works for the instance owner and for root
(although I'm not trying to install a multi-node database)
- making sure that all DB2 users have write permissions in their homes
- increasing the numbers of IPC resources via /proc/sys/kernel/shmmax
etc.

Older threads in this group point to potential problems with
/etc/services, but it looks like the installer set up a range of ports:

DB2_db2inst2 60000/tcp
DB2_db2inst2_1 60001/tcp
DB2_db2inst2_2 60002/tcp
DB2_db2inst2_END 60003/tcp

Maybe someone has an idea of what's going wrong here?

Thanks a lot in advance,

Christoph Schmitz
Nov 12 '05 #1
  • viewed: 4029
Share:
1 Reply
Christoph Schmitz wrote:
Hi,

I'm having a hard time getting ESE 8.1 to run on a freshly installed
SuSE 9.0 linux box. It was actually up and running, but after a reboot
(one disk in the RAID 5 had to be replaced) it wouldn't start, saying
SQL6048N (communication error, see below).


You do know that SUSE 9 is not yet supported, don't you?
Have a look here: http://www-306.ibm.com/software/data...inux/validate/

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by bonehead | last post: by
4 posts views Thread by Data Goob | last post: by
5 posts views Thread by michael | last post: by
24 posts views Thread by Denis S. Otkidach | last post: by
2 posts views Thread by SmoothJazz | last post: by
4 posts views Thread by Vitaly Sedov | last post: by
reply views Thread by jack112 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.