Who's On?

	Membership:
	Latest: Brady
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5274

	People Online:
	Visitors: 462
	Members: 0
	Total: 462

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

eRecruit Upgrade

3 Replies

0 Subscribed to this topic

68 Subscribed to this forum

Sort:

Author

Messages

John Costa

Veteran Member Send Private Message

Posts: 154

9/18/2006 6:14 PM

We are on version 5.8.0 of eRecruit (way behind.....). We want to go to version 5.8.4. Can I get away with doing a complete new install of eRecruit version 5.8.4 and simply run the database upgrade scripts to bring our database up to date? Since we are so far behind in our applications, we are having a great deal of difficulty finding all of the components to upgrade to each release in succession from 5.8.0, to 5.8.1, to 5.8.2, etc.

John Henley

Posts: 3351

9/19/2006 11:05 PM

My understanding is that you would have to install each patch release, since each release contains the database changes scripts for that version, and that you can't skip from 5.8.0 to 5.8.4. See KB article 969658 for the releases you need to install. They should all be available on the support site, and if not, you should contact your Account Manager.

Deleted User

New Member Send Private Message

Posts: 0

9/25/2006 11:33 AM

You may want to hold off on that upgrade. We had a number of issues with 5.8.4. In particular when sending emails out some of the fields would not populate.

John Costa

Veteran Member Send Private Message

Posts: 154

9/25/2006 4:36 PM

Well, it turns out that you *can* go directly to a newer version of eRecruit. You need only do a fresh install of the application itself and then you update your Oracle database by running all of the database upgrade scripts provided in the application download.

Unfortunately in our case, there are problems with the database and the upgrade scripts won't run without them being 'doctored' by Lawson. Strange, since the database has not been 'touched' since it was orginally installed by Lawson back when we went live.

We've chosen not to upgrade at this time until we can determine how the database needs to be fixed and who is going to do it.