dbms port

[grant]

Originally Posted by koli1980

File aaaaaaaa.cnf is corrupted allso in the backup server. The backup of imadb is never done before so we cannot replace that file. Is thet any other way to solve this problem?

Koli,

You have one, perhap two options. The first option is to recreate imadb. Assuming you have not added any new tables this is quite simple to do, although it will require you bring down the Ingres installation for part of it. The second option depends on whether you make use of VisualDBA, the GUI DBA tool. If you do then there is no second option. If you don't you can kill the "rmcmd.exe" process and prevent it from starting up. Start up is controlled in (V)CBF under "Remote Command", set it to 0 so the next time Ingres starts the "rmcmd.exe" process does not start. Admittedly option 2 is only a temporary measure. But it will stop rmcmd from being a problem process.

Rebuilding imadb requires you bring down Ingres. It also requires you have a current backup of your installation as we might need to manually delete some files from the data area. If something goes wrong you will need to make use of that backup to get to the last known good point before you tried to delete/recreate imadb.

1. Try to execute the following command, with the rmcmd process stopped:

   destroydb -u$ingres imadb

2. If that works then go to step 8
3. If it failed or hangs you will need to shut down Ingres
4. With Ingres shutdown issue the following command:

   del /s PATH_TO_INGRES\ingres\data\default\imadb

   where PATH_TO_INGRES is the Installation directory for ingres, also referred to as II_SYSTEM.
5. In CBF make sure the start-up count for "Remote Command" is 0
6. Start Ingres
7. Execute:

   destroydb -u$ingres imadb

8. Recreate the database::

   createdb -u$ingres imadb -fnofeclients

9. Put the IMA tables back:

   sql imadb -u$ingres < %II_SYSTEM%\ingres\vdba\makiman.sql

10. Backup the ima database using

    ckpdb +j imadb

11. In CBF set the startup count for "Remote Command" to 1
12. Manually start rmcmd using:

    ingstart -rmcmd

That list above should recreate and backup the imadb database. However I must stress that you should have a good system backup (with Ingres shut-down) before you attempt the above.

regards

grant

[koli1980]

This is also what the error is showing whem we try to connect to the server:

E_LQ0001 Failed to connect to DBMS session.
E_LC0001 GCA protocol service (GCA_REQUEST) failure.
Internal service status E_GC280d -- Network connection lost: See
errlog.log for detail..

Regards,
Koli

[grant]

Originally Posted by koli1980

This is also what the error is showing whem we try to connect to the server:

E_LQ0001 Failed to connect to DBMS session.
E_LC0001 GCA protocol service (GCA_REQUEST) failure.
Internal service status E_GC280d -- Network connection lost: See
errlog.log for detail..

Regards,
Koli

Where is this from, the server itself or from a PC running Ingres/NET?

g

[grant]

Originally Posted by koli1980

From 300 users only 20 can connect and the server respond to their request is very slow. We didn't add more users. The server used to work fine before with only one GCC for the users to connect. I don't know what changed in the system. We din't have connections problems before. By the way the connection limit of dbms is 400 connections and the connection limit for each GCC is 256 inbound connections and outbound connectins = 64 connections.

I shold have given this information to you before i think.

Thanks Grant

How responsive is the server when you are logged in at the console? Is it slow there too? Using the Windows performance manager can you see what the utilization is like? From an Ingres perspective there are several things you can do to get more information; DM420 trace point, look at the logging / locking activity, using IPM see if there are any queries which are taking longer than "normal". Support will be able to give you some more suggestions but I believe your best bet is to get someone onsite who can review your setup.

g

[koli1980]

Thanks grant.

[koli1980]

Dear Grant,

There were some good days with Ingress however we do have some problems still.

The application based on Ingres DB, recently we have found huge numbers of TCP checksum error messages on sniffer.

There is also other traffic on that server but only TCP traffic from the service of ingress (iigcc ) is giving a Checksum error and the traffic from the server to client, the packet seems not to be delivered on the wire.

Could this be related to wrong configurations on the network driver? Something wrong on OS ? or DB netutil? or somewhere else......?

Kind Regards

Koli

[bilgihan]

To imadb:

No need to backup imadb. You can recreate it at any time.
If case this is WIndows installation:
stop remote command server: rmcmdstp, or just kill rmcmd
destroydb -u$ingres imadb
run %II_SYSTEM%\ingres\bin\makimadb.bat