DB2 Error SQL6048N

Pada saat melakukan db2start atau db2stop, kita mungkin pernah mengalami error sebagai berikut
SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.

Penyebabnya kebanyakan adalah karena terjadi kesalahan hostname. Untuk mengatasinya cukup mengubah db2nodes.cfg yg ada di sqllib directory atau mengubah hostname di /etc/hosts.

Namun jika errornya terjadi di multi partition database, maka kemungkinan terjadi kesalahan di beb
- cek hostname di file .rhosts atau host.equiv
- cek hostname di file db2nodes.cfg di masing-masing sqllib di partisi yg ada
- cek apakah registry variable DB2FCMCOMM sudah benar.

Jika masih belum benar, bisa di cek kondisi berikut sesuai link resmi IBM
• Ensure that the application is not using more than (500 + (1995 – 2 * total_number_of_nodes)) file descriptors at the same time.
• Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
• Ensure the profile file is written in the Korn Shell script format.

This entry was posted in DB2 and tagged , , , , , , , , , , . Bookmark the permalink.

One Response to DB2 Error SQL6048N

  1. Pingback: DB2 SQL6048N | Deny Sutani

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>