Who's On?

	Membership:
	Latest: Chris Radcliffe
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5187

	People Online:
	Visitors: 379
	Members: 0
	Total: 379

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

copy PROD data AND patches to TEST

Sort:

You are not authorized to post a reply.

Author

Messages

bgodwin

Veteran Member

Posts: 143

10/24/2007 6:52 PM

Is there a way to make a copy of our LIVE system to copyover what is currently in our test system WHILE including the program files? We had some patches put into TEST that we chose not to put into LIVE and now our LIVE and TEST systems are out of synch...do we just BACKOUT the patches in TEST...or can we do a fresh copy of LIVE to TEST which will include the data and the patches (program file versions).

Any guidance is appreciated. Our Admin folks have the process of copying the data from Live to Test down to a science...just not how to get the file versions in synch.

Also is there a way that I can look at TEST to see if it is like LIVE in regards to all of the program files w/o having to look at individual file verisons such as pa100pd, pr140pd, etc?

Thanks

Greg Moeller

Veteran Member

Posts: 1498

10/24/2007 7:00 PM

Beverly:
The quickest way that I know of is to run the following:
perl $GENDIR/bin/patches_installed_report -c

This will give you a list of all CTP's applied to the product line which I then quickly import into Excel for easier manipulation.
Run it without the -c and it will give you the start and stop times of the installation of the particular CTP's.

Run it for both live and test, and import both lists into Excel and do your compare there.

Good luck,
-Greg

Greg Moeller

Veteran Member

Posts: 1498

10/24/2007 7:01 PM

Whoops... that should be
perl $GENDIR/bin/patches_installed_report -c product-line

John Henley

Senior Member

Posts: 3348

10/25/2007 12:18 AM

Beverly, there are number of step-by-step articles on Lawson's support site, e.g. 551210. The process is fairly easy: delete the existing TEST product line, dump from the LIVE product line, load to TEST, copy the source code and metadata and some other directories, and recompile. It only takes a couple of hours or so, plus compile time. You'll also need to use secdump/secload to migrate security classes.

As for backing out patches, that can be tricky, as they have to be backed out in the reverse of the order in which they were installed. So, if you installed 1, 2, 3, 4, and 5 and then wanted to back out 3, you'd need to uninstall 5, 4, and 3, then re-install 4 and 5. It's much quicker to just copy the product line.

bgodwin

Veteran Member

Posts: 143

10/25/2007 2:41 PM

Thanks so much to all - you are truly LIFE SAVERS

bgodwin

Veteran Member

Posts: 143

10/29/2007 1:02 PM

We did the copy and it seemed to work, I checked a few file versions and they now match live (i.e. patches backed out), but the install log for test still shows that these patches were installed. Did we do something wrong, were we supposed to replace the install log with the one from LIVE also? Is there a command to certify that all program files are the same versions between the live and test (I only checked a few).

??

John Henley

Senior Member

Posts: 3348

10/29/2007 2:10 PM

Beverly, As part of your copy, you should be cleaning out the old / target folders, then copying over the Admin, backup and metadata folders as part of the source code copy procedure...

You are not authorized to post a reply.