Hi,

We can not connect to Baan on GUI mode to our server but can connect using ASCII.

The following are the server configuration:

Baan version: BaanIVc4
OS: Solaris 8
Database: DB2 v5
Porting set: 6.1c.06.02
BW: B40.065
Service Pack: SP6

Please help
regards,

Lidia

What is the error message?

Message
"Detected database server termination"

I would try re-installing the porting set, probably get the latest one and install. Make sure you select the correct environment.

Maybe is possible to solve this problem with settings some parameters in $BSE/lib/defaults/db_resource file. Unfortunately I have no experience in DB2 database.

any messages in log-files ?

Did the GUI work before for you guys or is this a new installation?

the database server disconnect message shows up if any of the links

BW Client <------> bshell <----> DB2 driver <------> DB2

fail to communicate (in a timely fashion) with each other.

Since it works with the ASCII interface, but not with BW, I would look at the connection between your PC(s) and the server.
After all, BA is running on the server itself and doesn't seem to have a problem, right?

If it is only your BW client giving you problems, you might want to experiment with different versions of the program. If there are other programs that are 'acting up', you should investigate your hardware and cables.

You say 'we' cannot connect to Baan. Am I assuming correctly that this indicates that nobody there can use the BW client?

Hi Francesco,

We cannot connect to Baan GUI after changing database
from bisam to DB2v5.
I think that problem is with file tabledef6.1 , but
I don't know what I should change in it.

Below is some first lines from this file.

pcom000:*:db2v5(DB2INSTANCE=db2inst1):Y
cprpd000:*:db2v5(DB2INSTANCE=db2inst1):Y
pspmg000:*:db2v5(DB2INSTANCE=db2inst1):Y
tccom000:*:db2v5(DB2INSTANCE=db2inst1):Y
tccom999:*:db2v5(DB2INSTANCE=db2inst1):Y
tcedi000:*:db2v5(DB2INSTANCE=db2inst1):Y
tcmcs000:*:db2v5(DB2INSTANCE=db2inst1):Y
tcmcs002:*:db2v5(DB2INSTANCE=db2inst1):Y
tcmcs095:*:db2v5(DB2INSTANCE=db2inst1):Y
tdcms000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdilc000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdinv000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdltc000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdpst000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdpur000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdrpl000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdsls000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdsls600:*:db2v5(DB2INSTANCE=db2inst1):Y
tdsmi000:*:db2v5(DB2INSTANCE=db2inst1):Y
tdsst000:*:db2v5(DB2INSTANCE=db2in

Lidia

tabledef6.1 is probably OK if you can connect to Baan using ba6.1

If you manage to get a database server termination, then it seems that BW is able to reach the server, but not the DB server (be local or remote).

Make sure that the needed environment variables are setup in maintain DB definitions (ttaad4100m000, also used in the tabledef6.1 file). Check if something that is set at UX level must also be set in that session parameter field (and tabledef6.1).

Here's another possibility.

When using BA, you will pick up your environment variables from your user .profile file.
When using BW, your environment variables (including the location of your database), are not set, unless you specifically set them in your log-in script (the one that ipc_info points to).

we just had the same problem about two weeks ago. The only solution that Baan could give us was to reboot our servers.

Also do a sar -v on your server and check to see if your end_files are close to the limit. We increased these while we had the software shutdown.

We have had no other occurance since.

Telgar,

You can find a lengthy thread on my struggles with 'database server terminations' on this board under this thread (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=5760).

In this case, the error was caused by corrupted shared memory, in which case the problem would be solved by rebooting the server (and consequently rebuilding shared memory).

I suspect Lidia's problem is of a different nature, because
A. She is unable to connect period.
B. She _only_ receives the error using BW, not using BA.

For the same reason it doesn't seem logical that the time-out would occur through lack of system resources.

Of course it never hurts to try a reboot. Logic and reason sometimes seem to stand in the way of finding the right solution in Baan :D

Hi,

thanks you very much for all your response!
by the way, we can now use Baan GUI.
The problem regarded environement variables.
I set the variables via ipc_info files.

regards,

Lidia

Theses are the enviornment variables needed..

• Ipc_info
Bshell s 0 0 p ${BSE}/bin/bshell2
• Bshell2
#!/bin/ksh
export LIBPATH=/home/db2_v7/sqllib/lib:/usr/lpp/db2_07_01/lib
${BSE}/bin/bshell6.2 $*