Hi,

We have Baan IV C4 on Digital Unix, with Informix at the back-end

Currently, Baan Application and Baan Database are on the same Digital Unix server.
Over the years, Baan Database has grown and very soon, it would occupy all the disks on the server. We cannot add more disks on the server also.

We have another Digital Unix server.

So can we have configuration like this - Baan Application will continue to reside on the original server, whereas Baan Database will be on the new server or vice-versa.

If possible, what will be the steps involved ?

Thanks

Yes, It is possible...

First of all, update ur profile to give u a better answer..

Safer method is to move the application part to new server and let the database reside on existing server. Do user interface and logic installation on new server and then move appliation from existing server to new server. Then depending upon RDBMS being used there are different method available for connectivity from application server to database server.

Hi,

Here are some updates on the splitting of Application Server and Database Server.

These two servers are basically additional servers and we are testing splitting of Application and Database.
Production Server is only one.
But the configuration of the two new servers - Memory, Kernel Parameters, Number of CPUs etc. is identical to Production
Server.

1. 1st we tried using iconnect utility of Informix for connecting the two databases and did not use Remote Connectivity setup
as mentioned in Baan Help.
Application Server did not have Informix, while Database Server did not have $BSE environment.
A Service was created on Database Server to take request from Application Server and connect to the database.
Evenif Informix was not present on APplication Server, we set up, with INFORMIXDIR and INFORMIXSERVER environment variables
and created a $INFORMIXDIR/etc/sqlhosts file, which would point to the database server and database service running on
Database Server.
/etc/services files on Application Server and Database Server both have the same service name, with the same port numbers.
(I believe, /etc/services and $INFORMIXDIR etc. on Application Server are irrelevant).
In Baan Application, we created a new database defintion in session "Maintain Database Defintions" (ttaad4110m000), with
proper parameters of Informix environment. System Name was left blank. Companies were attached to this database and
everything was converted to Runtime DD. Toolc Company 000 too was pointed to this new database.

When we started Baan APplication and tried testing, some weird problems started occuring.
Problems are occuring for many tables - tdsls041, tdsls045, tfgld106 etc., which have records in millions. I am just
elaborating here one table here.
Our Informix DBAs and Baan DBAs all have given up.

a. When some simple Export Exchange Schemes, which does not have any join, any reference, any where condition, say on table
tdsls011, which had just 150,000 records, it used to process smoothly upto some 24000 records in around 15 minutes and then, it used to throw out of Baan Application with message "lost connection with bshell" and generated a Core Dump in the home
directory of the user.
No logs were generated at Informix Level (online.log) as well as Baan Level (log.informix, log.bshell etc.).

b. But, we were able to maintain data in this table without any problem in Baan session itself as well as ttaad4100. Insert,
Update, Delete was also possible.
Further, we ran an Import Exchange Scheme on this table (without bdbpost, bdbpre), it was going through smoothly, without any problem.
We were able to create seq. dump of this table, drop it and re-create it using seq. dump.
This we tried in Baan sessions as well as using bdbpre and bdbpost.
Import and Export Exchange Schemes using bdbpre and bdbpost too were working successfully.

c. When we built and ran SQL Query in Baan using Easy SQL in Maintain SQL Queries, then also it was failing.
When SQL Query was built and ran using the same syntax as in Exchange Scheme script, at that time also, it failed, giving the
same message and core dump.

d. A simple report session when generated on this table, went through without any problem.

e. qptool6.1 utility too did not give any problem.

f. When we run the query at Informix Level directly, then too there is no problem.

g. When the core dump was occurring, we observed that memory utilization was static - 10%, 20% etc., but CPU utilization on

Application Server was growing - intially 10%, then 30%, 40%, 70%, 90%, 100% and then the core dump.
CPU Utilization on Database Server remained static - some 30%.

h. We tried all above steps using different user IDs, then also the same result.

i. There is no problem of free space on both the servers - $BSE_TMP, /tmp etc. as well as temp dbspace on Database Server.

Free Space in all these is in GBs.

2. We then copied the entire $BSE environment from Application Server to Database Server. We were able to start Baan in
stand-alone mode on Database Server, with all companies pointing to Informix database on Database Server itself.
Still, the same problem for all the steps mentioned in step (1).

3. On Database Server itself, we created another database in tbase and assigned table tdsls011 to this tbase. Still, the same
problem for all the steps mentioned in step (1).

4. Then, we tried sharing, as per Baan Help. Maintain Remote Systems, Maintain Remote User Data to point to the remote system, Maintain a new database, which would reside on the new system, assign table tdsls011 to this database etc. Still the same problem for all the steps mentioned in step (1).

Is there anything else, that needs to be tried ?
We have tried everything as per iconnect help and Baan help.

(Hope, moderators will not object to such a long post).

Thanks

Hi,

On Database Server, we copied tools company 000 from Informix to tbase (using bdbpre, bdbpost) and also our target table tdsls011 in tbase.

Still, the same result. Core dump after processing sometime.

There is no sharing with Application Server. Baan is running in stand-alone mode on Database Server.

Is this a problem with some Baan settings or is it a problem with some Kernel related settings on Database Server ?

Thanks

what about if the operating system is windows 2003 and the database server is sql server 2005? can someone detail the step for splitting the database and the application server into different machine ?