cancel
Showing results for 
Search instead for 
Did you mean: 

Connection errors?

Former Member
0 Kudos

AIX 7.1 DB2 v9.7.04 SRM MDM-CAT 3.0 7.1..07.247

I've upgraded my MDM-Cat from 7.1.03.52 and migrated my db from 9.5 to 9.7

Now I THINK I've got connection problems.

In the "Master Data Server_ncs.trc" (workdir of MDS) I see

M Wed Feb 29 09:43:07 2012

M NCS library version 2.3.0 (unicode) loaded

M NCS_ProcInit API invoked

M

M Wed Feb 29 09:43:11 2012

M ***LOG Q0I=> NiPConnect: 127.0.0.1:59818: connect (79: Connection refused) [nixxi.cpp 2777]

M *** ERROR => NiPConnect: SiConnect failed for hdl 1/sock 6

(SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:59818) [nixxi.cpp 2777]

M *** ERROR => NI raw handle failed to be initilized for the first time, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 140]

M

M Wed Feb 29 09:43:22 2012

M Performance or Resource Data Detected

M *** ERROR => NI raw handle failed to be initilized for the first time, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 140]

M

M Wed Feb 29 09:43:37 2012

The MDS_Log i logdir doesn't show any strange things, nothing strange in the db2diag.log

I've got an other system where I've migrated the db, but not installed the MDM-patches. I've checked the configfiles between the systems and the seems to be the same.

I've changed the paths to db-lib in the src and env files.

I've even tryied to drop and recreate my database. Anyone have a clue?

It is possible to connect to the repository via mdm-console, but when trying to "update indicies" the connection in the console is lost, the status becomes "Stopped". When unmount/mounting the server again the status is changed to "running". My guess is that this is due to the problems in the trace-log.

Edited by: cace on Feb 29, 2012 10:54 AM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Cace,

Please verify the repository and see if you have any fatal errors.

If yes do a repair after taking a backup.

Pls revert with findings.

Thanks,

Ravi

Former Member
0 Kudos

Hi!

I've allready tryied that. I had 4 non severe errors, two of them was possible to repair.

Thanks anyway!

Former Member
0 Kudos

Hi Cace,

Out of these errors were you able to remove the other 2?

If not did you try again as it requires few attempts sometimes to repair a repository.

Once you do a Verify you get a report,you can slect warnings/errors in that,try to isolate the non fatal errors you got.

Did you try a server restart?

Pls revert.

Thanks,

Ravi