Copy PROD to DEV

Hello,
We are running B733.2 Sp10 on AS400 plateform.
I need to transfert everything from PRoduction to Dev including ESUs and customizations (no datas).
Is there any UBEs that I can run?
Thanks
Kham

See JDE Doc OTI-01-0026 'Creating a mirror image of the CRP Environment for
the Production Environment'.

All you need to do is change the names.

If you want to speed things up then you can just do a database copy. Where
are your Central Objects? Are they on the AS400 or on the Deployment server
in SQL or Oracle?


Colin

Re: RE: Copy PROD to DEV

Hi Collin,
Thanks for helping.
Our Central Object is on SQl deployment server

On the data copy, do a restore library rather than a copy. I've done both
and the RSTLIB is alot faster even taking into account the time it takes for
the Backup. We have have over 93Gb in PROD that took 16+ hours using copy
commands. The restore took about half that. This was for both PRODDTA and
PRODCTL.

Darrell Allison
Systems Programmer
AS/400 V4R4 9406-730 8-Way / OneWorld B7332 SP11.3

Make sure you save access path on the backup!

How do you go about copying Central Objects (on a SQL 7.0 database) from one pathcode to another? We are probably going to do this and the document from JDE does not say anything about this. Help!
Thanks!

Re: RE: Copy PROD to DEV

There are 3 ways I have used to accomplish this when Central Objects are on the SQL Server.

1) Use R98403. There is a version set to copy Central Objects from one path code to another.
Pro: JDE supported
Con: This takes forever. R98403 uses the JDE copy table, which goes record-by-record. When you've got F98741 tables running over 2 million records, you're talking about an all day affair.

2) Empty all Central Object tables in the target path code. Use SQL Query Ananlyzer to Insert into (target) select * from (source) for each table.
Pro: Much faster than #1, usually taking about 4 hours, depending on your database server and how many records you've got.
Con: There is a better way to accomplish the same thing.

3) Use a SQL Server tool like BCP (bulk copy) to accomplish the same taks as #2. You still have to empty the tables first, but then you can use BCP to do the rest.
Pro: Fastest method of the 3, should take no more than 2 hours unless your database server is low on resources.
Con: You need to know SQL Server command line tools. You need space to hold the database dump files that BCP will generate.

There is an additional consideration. If you use #1, you don't have to worry about any path code specific data in any of the Central Object tables. If you use #2 or #3, and F983051 is in your SQL database, then you have to worry about changing all the references from PRODB733 to DEVB733.

Besides speed, the other thing in #3's favor is that JDE even supplies some of the tools to do the job. If you look at the DATABASE directory under B7332 of your Deployment Server, you will see the batch files you used when you loaded Central Objects in the first place. All it takes is a little rewrite to accomplish the task. I have attached a small zip file with something I've used in the past. Unzip the files into the same place where JDEBCPIN.BAT is located on your Deployment Server. Then make sure your Deployment Server has the space to hold the results. You might also want to move the existing .DTA files out of the way in anticipation of the creation of the new ones. Lastly, check the batch files to make sure you are only doing this for the tables that exist in your database.

Your mileage may vary ...

Re: RE: Copy PROD to DEV

There is an option #4, use DTS within SQL server. The speed of #3 with the ease of use of a GUI interface.

Paul

Re: RE: Copy PROD to DEV

We do regular refreshes between environments and found completing backup and restores to be the quickest. Here is the procedure we follow:

1. Backup up pd7333
2. Restore to dv7333
3. Update to new table owner.
The script to run is as follows: (modify for your environment specifics)
use jde_dv7333 (Your database that you restored)
a.) select uid from sysusers where name = 'pd7333' (Uid for production table owner)
b.) select uid from sysusers where name = 'dv7333' (Uid for development table owner)

Update sysobjects set uid = "dv7333 uid" where uid "pd7333 uid" and xtype = 'U'

4. Update your versions table
use jde_dv7333
update dv7333.f983051 set vrenhv = 'dv7333' where vrenhv = 'pd7333'

NOTES:
1. Make a backup of sysobjects and f983051 tables
2. Use caution when updating systables



Good Luck!!

Re: RE: Copy PROD to DEV

I have found (when using DTS) that you have to be careful or you won't have the proper indices and/or table owners.

Have you found a way around this?

Re: RE: Copy PROD to DEV

You can have SQL Server create a script for all of the existing indices before you copy the data using DTS. Then just run the script after the data has transferred.

For table owners just update the sysusers table.

DeRay Scholz
dj Orthopedics, LLC - 2985 Scott Street, Vista, CA 92083-8339

Re: RE: Copy PROD to DEV

Yeah, we used to have the same problem but have found a way around it.
If you use the DTS wizard, on the third screen "Specify Table Copy or Query" there is three options. We used to use the first one and this does not copy indexes/primary keys. If you use the third one "Copy Objects and Data between SQL server databases" then these are copied.

Paul

IN ONEWORLD UBE R98403 WHICH ALLOWS U TO TRANSFER FROM ONE ENV TO ANOTHER ENV.
IT HAS DIFFERENT VERSIONS - FOR DATA, CENTRAL OBJECTS, CONTROL TABLES.
CHECK ON THAT