Who's On?

	Membership:
	Latest: TJA
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5242

	People Online:
	Visitors: 276
	Members: 0
	Total: 276

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

Moving Oracle Database to Remote Server

3 Replies

0 Subscribed to this topic

27 Subscribed to this forum

Sort:

Author

Messages

Robert Newman

Basic Member

Posts: 6

2/1/2012 5:09 PM

Lawson S3 9.0.1.8, AIX 6.1, Oracle 11.2 - We currently have S3 Back Office, WebSphere, and Oracle DB all residing on one server. We are testing moving Oracle DB off to its own dedicated server. So far testing is showing severely decreased performance. We are seeing an average 50% increase in runtimes on long-running batch jobs. Has anyone else seen this same issue when mocing their DB to a separate server? Any suggestions on where to look for the problem causing the performance issue?

Thanks,
Robert

John Henley

Posts: 3362

2/1/2012 5:59 PM

Yes indeed. It's a bad idea. I wrote a paper for a client about 10 years ago, and the same holds true: Lawson accesses the database often on a record-by-record basis. If your DB server is a different server, that's one round trip across the network per record.

Greg Moeller

Veteran Member

Posts: 1498

2/1/2012 6:23 PM

You can (and we did) configure a separate network for your database traffic to go across. Actually, when we had the same type of configuration that you have, we had the two servers in the same room, so we just ran a cross-over cable between them and configured the database to use that. Now the 2 servers are 2.5 miles away from each other and a cross-over is not possible. So therefore the separate network/subnet.

Joel

Basic Member

Posts: 12

2/3/2012 3:01 PM

We are doing it ( due to company policy to use oracle clusters to reduce licensing costs). We upgraded the hardware at the same time we moved the db off the server so we seemed to essentially keep our old performance. The hardware improvement was negated by the database response issue. Lawson makes lots of little queries and its slow even when the servers are in the same room.

Now where we really have a problem is our dev system. It's in a building thats over ten miles away from the database cluster. Test jobs take 3-4 times as long as Q or P and its generally a huge pia to test any large jobs in dev now. Luckily our user testing takes place in Q or the users would have rioted by now.