Conectivity Problem

[qfan]

Hi,

I installed Ingres 2006 on Sun Solaris and get the following message at the end:
Building the password validation program 'ingvalidpw'.
Could not compile ingvalidpw: Using executable from the distribution instead.
Executable successfully installed.

I start the inges server using ingstart. The server seems to be started successfully.

-- Ingres 2006 Release 3/ingstart

-- Checking host "brogo" for system resources required to run Ingres 2006 Release 3...

-- Your system has sufficient resources to run Ingres 2006 Release 3.

-- Starting your Ingres 2006 Release 3 installation...

-- Starting the Name Server...

-- Allocating shared memory for Logging and Locking Systems...

-- Starting the Recovery Server...
-- II_DBMS_SERVER = 33432

-- Starting the Archiver Process...

-- Starting DBMS Server (default)...
-- II_DBMS_SERVER = 33435
-- WARNING!!! The recommended file descriptor hard limit for the NET Server to service 64 inbound, and 64 outbound connections is 261. The current file descriptor hard limit is set to 256.
-- Starting Net Server (default)...
-- GCC Server = 33438
-- TCP_IP port = II (21064)

-- Starting Data Access Server (default)...


Starting the Visual DBA Remote Command Server...

-- Ingres 2006 Release 3 installation successfully started.

And then, I setup vnode using netutil in the windows and tried to use ingres account to connect to the database. But I got the following error messsage:
E_GC2809_NTWK_CONNECTION_FAIL Network connection failed for protocol WINTCP, to node 203.0.128.2, port DA; status follows.
DT-xxx ::[II\COMSVR\1034 , 4148 , 00000000]: Thu Nov 13 16:10:47 2008 E_CL2781_GC_CONNECT_FAIL An attempted network connection failed
DT-xxx ::[II\COMSVR\1034 , 4148 , 00000000]: socket() failed with operating system error 10061 (No connection could be made because the target machine actively refused it.)

Could the ingres account be used to connect to the server? How can I manually execute the ingvalidpw (I tried the script in II_SYSTEM/ingres/bin. But the system just hanging there)?

Thanks a lot.

[stephenb]

Your problem looks identical the the one in this thread:

Connectivtity between Ingres 2006 and Ingres II 2.0

I think your installation code in the netutil entry on the client is wrong...the error message talks about "failed to connect to port DA", yet your ingstart output says "TCP_ip Port II".

Try re-creating the netutil entry on the client and use listen port=II

You might also want to follow the progress in the other thread.

[qfan]

I set the port to be II. Another error comes:

E_GC2462_NO_CHARSET Character set negotiation failed: no common character set found.

The ingres instance uses UTF8. Is that the reason for this problem? If I want to change the charset, do I need to re-install ingres?

Thanks

[denjo02]

If your server installation has a CHARSET of UTF8, you should be able to set that on the client too. Open a DOS window on the client, and enter the command:
ingsetenv II_CHARSETII UTF8

[qfan]

I set the windows client's charset to be utf8 too. Now both server and client have the same variable:
II_CHARSETII=UTF8

But the problem remains. When I test the connection using netutil, it gives me the same error message.

[denjo02]

Did you restart the client after resetting II_CHARSETII? If not, try it.

If the problem persists I think we need to see the output of an "ingprenv" command on each of the server and client. It might also be useful to know the full version of each - can you also provide the content of the version.rel file from each installation. That's in $II_SYSTEM/ingres (or %II_SYSTEM%\ingres for the Windows client)

[qfan]

Great. The test is successful. But my old server with ISO88591 cannot be connected. Can I just change the env variable of the new server to be ISO88591 to make it work or I need to re-install the server? Thanks.

[denjo02]

Restarting the client worked? Sorry, I should have advised that earlier.

You need to have the client and the server with CHARSETs which can coexist, can map to one another. I have the same problem with one of our internal applications, where the database server used UTF8. I simply installed a second client on my windows PC to connect to that server.

I guess one question which remains unasked is why the DBMS was set to UTF8? If you have no specific reason to use this charset then perhaps a reinstall of your new server installation, specifying the default charset of ISO88591 might be the best approach. You will need to deinstall and reinstall though, to change the charset of a DBMS installation.

[qfan]

Thanks a lot for your help. I think I will keep UTF8 as we might have some unicode data. ISO88591 is single byte. It might not handle some special character properly.

[qfan]

I need to merge the old Ingres2.5 server with IOS88591 to the new server with UTF8. Could that happen anyway? Or I need to make the charset to be the same before I can merge?