cancel
Showing results for 
Search instead for 
Did you mean: 

db2nodes.cfg reading error

Former Member
0 Kudos

Hi,

When i enter to db02 transaction this error appears in SM21:

SQL0443N Routine "SYSPROC.DB_PARTITIONS" (specific name

"DB_PARTITIONS") has returned an error SQLSTATE with

diagnostic text "db2nodes.cfg reading error". SQLSTATE=560B

tabase error -443

Someone can tell me the solution?

Our system is ECC 6.0 EHP4 in Windows 2008 R2 and DB2 V9.5 FP8

Thanks in advanced

Best Regards

Aldo Garcia

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi all,

I solve this issue by changing my instance to partitioned instance, i need to drop the actual instance and recreate it with the DB2 commands for partitioned instance.

Thanks all Regrads

Former Member
0 Kudos

Hi,

did you check SAP notes 989596 and 1515369? They will probably help by suppressing accesses to the cfg file

Best regards

Ralf

former_member189725
Active Contributor
0 Kudos

Please check the instance directory (sqllib directory) if the file db2nodes.cfg exist.

Please check if the following entry is there in the db2nodes.cfg .

0 <hostname> 0

(I hope your database is a single partion database)

Also check if the file has the required permission .

former_member188883
Active Contributor
0 Kudos

Hi,

You can perform a windows search for the file db2nodes.cfg.

If its missing re-create the same with below mentioned entries

0 <hostname> 0

Restart database and application.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi,

The file exists in H:\SQLLIB, in H:\SQLLIB\db2 and C:\Prgramdata\IBM\DB2\DB2PRO\DB2PRO

The contest of file is:

0 netprod NETPROD 0

and i give permissions everyone but not success

Regards

Former Member
0 Kudos

Hi,

Yes but the first note doesn´t apply because my realese is 701 and the second note not solve the problem.

Regards

former_member189725
Active Contributor
0 Kudos

Can you give us the output of db2level.

Also the convention for db2nodes.cfg is

nodenum hostname logical port netname resourcename

nodenum hostname logical port -- these are required

so db2nodes.cfg should be

0 netprod 0

try this out and check if there are issues .