Is a system copy to development a best practice?

("Refresh", as I use it here, refers to a system copy.)
We typically refresh our sandbox and pre-production test systems from production. Not often, since its a non-trivial amount of work (although our functional/business teams don't seem to realize that ), but we've got the process down. The production DBs also total around 8-9 TB, and its not practical to store too many copies of that. The full environment includes the core ERP 6 system (HR, PY, FI, CO, parts of PLM), SRM 5, BI 7, and two portals (employee and vendor), each with development, QA/test, pre-production, and production.
We have never refreshed our development environment, mainly since that version history and test data.
We recently had a project consultant request that we refresh development from production, and claim doing so was a "best practice". The project might significantly reconfigure FI, but everything else is out of scope.
Although refreshing the development system/environment can be done, should it be? What kind of circumstances might make it a good idea? Is it considered it a "best practice" by others? Why?
(Cross posted to the [ASUG Systems Management forum|http://hosted.jivesoftware.asug.com/community/sig_communities/business_integration__technology_%26_infrastructure/systems_management_sig].)
Thanks,
Dave

Well i cannot view the ASUG discussion but here is my 2 cents:
cons:
- versions history has to be saved prior to copy
- cost (additional disk space, backups, cpu/memory)
- the production data will age pretty fast, so the copy has to be done on a regular basis
- lots of interfaces to other systems will have to be corrected, risk of connecting to prod systems during the copy process
- the dev system will be unavailable for several days during the copy
pros:
- real data on the prod system, no need to manually generate data
- most performance issues can be discovered at design time, given the hardware is comparable to the prod system
In my opinion regularly copying the prod system to dev is not best practice. Personally i would never do it because of the cost and amount of work needed to do it.
Best regards, Michael

Similar Messages

System requirement tp install Utilities Best practices(utilities-V1.500)

Hello All,
We want to install SAP Best Practices for Utilities (UTILITIES - V1.500) in our landscape. I checked the system requirements proposed by SAP and observed that most of the s/w releases they are reffering to are ECC5 (500) and our system is at release ECC6 (600). I beleive that there will be a lot of changes in the config nodes of ECC6 from ECC5. So if we install it in our landscape then will it cause a conflict in configuration? So is it advisable to install Utilities Best Practices in our system? Please find below the system requirement proposed by SAP for installation of best practice and RTD system Configuration. Kindly let me know.
System Requirements proposed by SAP is as follows
Software Component     Release     Support Package     Highest Support     Short Description of Software Component
               Package
SAP_BASIS     640     13     SAPKB64013     SAP Basis Component
SAP_ABA     640     13     SAPKA64013     Cross-Application Component
ST-PI     2005_1_640     2     SAPKITLQH2     SAP Solution Tools Plug-In
PI_BASIS     2004_1_640     10     SAPKIPYI6A     Basis Plug-In (PI_BASIS) 2004_1_640
SAP_BW     350     13     SAPKW35013     SAP_BW 350
SAP_APPL     500     9     SAPKH50009     Logistics and Accounting
SAP_HR     500     11     SAPKE50011     Human Resources
EA-IPPE     300     7     SAPKGPIC07     SAP iPPE 300
EA-APPL     500     9     SAPKGPAC09     SAP R/3 Enterprise PLM, SCM, Financials
EA-DFPS     500     9     SAPKGPDC09     SAP R/3 ENTERPRISE DFPS
EA-FINSERV     500     9     SAPKGPFC09     SAP R/3 Enterprise Financial Services
EA-GLTRADE     500     9     SAPKGPGC09     SAP R/3 Enterprise Global Trade
EA-HR     500     11     SAPKGPHC11     SAP R/3 Enterprise HR Extension
EA-PS     500     9     SAPKGPPC09     SAP R/3 Enterprise Public Services
EA-RETAIL     500     9     SAPKGPRC09     SAP R/3 Enterprise Retail
FINBASIS     500     9     SAPK-30009INFINBASIS     FINBASIS 300 : Add-On Installation Request
SLL-LEG     300     9     SAPK-30009INSAPSLL     SLL-LEG 300_640 : Add-On Installation
CPROJECTS     300_640     8     SAPK-31408INCPROJECT     SAP cProject Suite 3.10 (based on 640)
BI_CONT     353     5     SAPKIBIFP5     BI_CONT 353 : Add-On Delta Upgrade
BP-INSTASS     500V3     0          -     Best Practices Installation Assistant
BP-BLERP     500V6     0          -     Best Practices All-in-One (based on ECC
Our RTD System
Software Component     Release     Support Package     Highest Support     Short Description of Software Component
               Package
SAP_BASIS     701     4     SAPKB70104     SAP Basis Component
SAP_ABA     701     4     SAPKA70104     Cross-Application Component
ST-PI     2005_1_700     6     SAPKITLQI6     SAP Solution Tools Plug-In
PI_BASIS     701     4     SAPK-70104INPIBASIS     Basis Plug-In
SAP_BW     701     4     SAPKW70104     SAP Business Warehouse
SAP_APPL     604     3     SAPKH60403     Logistics and Accounting
SAP_HR     604     11     SAPKE60411     Human Resources
EA-IPPE     400     15     SAPKGPID15     SAP iPPE
EA-APPL     604     3     SAPKH60403     Logistics and Accounting
EA-DFPS     600     13     SAPKGPDD13     SAP Enterprise Extension Defense Forces & Public Security
EA-FINSERV     600     3     SAPKGPFD03     SAP Enterprise Extension Financial Services
EA-GLTRADE     600     5     SAPKGPGD05     SAP Enterprise Extension Global Trade
EA-HR     604     11     SAPK-60411INEAHR     SAP Enterprise Extension HR
EA-PS     600     13     SAPKGPPD13     SAP Enterprise Extension Public Services
EA-RETAIL     600     5     SAPKGPRD05     SAP Enterprise Extension Retail
FINBASIS     600     13     SAPK-60013INFINBASIS     Fin.
Thanks a lot in Advance!
Boby Mathew

Hi ,
Please go with the sequence 4, 1, 2 ,3. This would give you solution manager key for the other systems also.
Rest of the stuff you can get it in the installation guides. http://service.sap.com/instguides
Regards,
Pavan

JDeveloper ADF development & CVS best practices?

Greetings all,
My team has chosen to use CVS for our ADF source control. Are there any best practices or advice on the source control lifecycle using CVS & JDev?

Shay Shmeltzer wrote:
We would recommend that if you are starting a new development project you'll use Subversion instead of CVS.
I'll echo that - if you're familar with CVS, you'll find most SVN commands are similar (if not identical!) and you'll find that branching/merging operations and atomic commits will make the problem areas with CVS a little easier.
Some good discussion here:
http://stackoverflow.com/questions/245290/subversion-vs-cvs

Operating system image build and management best practices?

how do we create gold images for servers/desktops,
Best practices image management,
How do we control changes?
How do we prevent unauthorized changes (installation of software)?
What tools we can use for above.

I use MDT 2013 Lite Touch to create my images
http://www.gerryhampsoncm.blogspot.ie/2014/03/create-customised-reference-image-with.html
You should use in-built ConfigMgr Role Based Access Control to manage images afterwards (look at the Operating System Deployment Manager role).
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

Re: Pre & Post activities for homogeneous system copy

Dear All,
can any body help with pre & post activities for homogeneous system copy
Thanks in advance
Best regards,
khan

Hi,
Use Oracle Database specific method to perform homogeneous system copy.
Along with this reference official [system copy guide|https://websmp209.sap-ag.de/~sapidb/011000358700000416402008E.PDF], You can also refer this [useful doc|http://www.basisconsultant.com/component/remository/Sytem-Copy-Guides/Homogeneous-System-Copy-using-OnlineandOffline-Backup/] for the same to have all required pre-post activities information with more details.
Regards,
Bhavik G. Shroff

Best practice for preparation of install of Leopard from Tiger

Hi all, I am about to upgrade my iMac with an Archive and Install of Leopard 10.5 from Tiger 10.4.11.
I've done this dozens of times on other machines, but I never really thought about the best way to prepare for an install, I have already backed up this machine using Carbon Copy Cloner, is there anything else I should do before hitting the button?

Run the Disk Utility Repair function (or at least Verify), and also the Repair Permissions, which takes many minutes. This will help assure Integrity of your directory before you begin.
I am not sure why you are choosing to Archive and Install. An Upgrade install will be offered, and is thought to be just as effective, and can be a little more convenient in that your non-Apple Applications are not moved into the "Previous System" folder.
The absolute BEST practice would be (after you make TWO backups) to erase your Hard Drive with the Write Zeroes/Zero All Data Option. This will take many hours, but will force the drive to substitute spares blocks for any found to be defective after the Zeroing. But I must say that in the absence of error messages indicating disk trouble developing, this is incredible overkill. You asked, so I am answering the question as you asked it.
Message was composed over a long period of time due to multiple interruptions.

Installing SAP Best Practices for HCM v2.60

Hi Gurus,
Has anyone installed SAP Best practices for HCM. I have to install the building blocks in the system. Can anyone guide me How to approach it? I have downloaded SAP BP v2.60 for HCM. How will I start transfering it to the client's SAP ECC 6.0 system. My Client needs Best Practices for HCM in their system.
Any kind of help is deeply appreciated. Please help.
Regards,
Sanchit

Hi Shaukat!
Please take a look at http://help.sap.com -> SAP Best Practices -> Cross-Industry Packages.
You can also try and take a look at http://service.sap.com/swdc -> Download -> Installations & Upgrades -> Entry by Application Group -> SAP Best Practices
Caution! You only can use the BP if this is suitable to your ERP version! Check if your HCM BP is for ERP2004. If so it will not work on an ERP2005 System.
I hope this helps!
Regards,
Zsolt

CRM - how to work with Best Practices

Hi All,
we will start with the implementation of mySAP CRM during the next weeks.
I'm a bit confused - how should I work with Best Practices, and what are the differences between the 3 ways for Best Practices
1) we have a 'Solution Manager' System where I can use Best Practices for CRM
2) Best Practices on help.sap.com: http://help.sap.com/bp_crmv250/CRM_DE/html/index_DE.htm (Buliding Blocks!)
3) Best Practices DVD to install on the CRM System
Are the 3 ways exchangeable? Is there some information provided by SAP?
We have already installed the Best Practices DVD, but now I don't know how to use this Add-On: Is there a special transaction-code to use them or a extension for the IMG?
regards
Stefan

Hi Stefan Kübler,
If the solution manager is in place, then the suggested (also the best) method is to use the best practices on it.
If you want to install and use the best practices with CRM system then the procedure is given in the best practice CD/DVD. Also you can download the installation procedure from the below link : http://help.sap.com/bp_crmv340/CRM_DE/index.htm. Click on Installation on left and then Quick Guide on right. Download the document.
Though the best practices give you a way to start with, but they cant replace your requirement. You have to configure the system as per your exact business requirement.
I never installed best practices before, but extensively used them as reference in all my projects.
Follow the below thread for additional information on best practices :
Also refer to my past thread :
Do not forget to reward if helps.
Regards,
Paul Kondaveeti

Best Practices - Transports

Hi there
In my brief Portal experience, I have only ever transported stuff (iviews, roles etc.) using the manual approach provided in the portal under System Admin >> Transports.
Now, one of the other portal implementations that our company has done has been scrutinized, and one of the suggestions that has come out of that investigation (outside contractors) was to implement a "Portal Transport System" as documented in the Best Practices document, which is then supposed to automate the content migration process.
So:
1. Can anybody tell me where documentation is available on this transport approach?
2. Can anybody confirm / deny that this is the best approach to use for transports.
Any information would be greatly appreciated.
Cheers,
Andrew

Hi,
You can find a best practice document in SDN.
Please check the below links.
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/ep/EP%206.0%20SP2.0/Best%20Practice%20for%20Transporting%20SAP%20NetWeaver%20Portal%20Content.pdf#search=%22How%20to%20transport%20portal%20packages%3F%20netweaver%22">Best Practice Transporting SAP NetWeaver Portal Content</a>
Also check..
http://www.sapportalseminar.com/agenda/index.cfm?usergroup=regular&confCode=POR6-PHI
Hope this helps you.
Thanks,
Ramakrishna

Hyperion Essbase Best Practices Document...

Hi All,
Is there any document out there that has the best practices for Hyperion Essbase development? I am looking for methodologies, naming conventions and such information. Wondering if there is any such doc with Hyperion Essbase Guru's that outlines the best approaches for Essbase-outline development with it . Searching this forum with the string "best practice" yields a lot of threads on specific issues, but couldn't find any document.
Any pointer is most appreciated.
Regards,
Upendra.

Various consulting organizations have different
guidelines, each with their own strengths and
weaknesses. To get them to cough it up without
bringing them in for a paid project might be
difficult, but not impossible.I agree with Doug here.. Many of these consulting companies have developed their best practices over a number of years and view them as a competitive advantage over the other consulting firms. I would be highly surprised if you managed to get ahold of such a document very easily.
That being said, those same consultants share information here in bits and pieces, so you can learn at least some of the best practices here (along with best practice tips from consultants/developers/customers who don't have an 'official' best practices guide)..
Tim Tow
Applied OLAP, Inc

Best Practices for Configuration Manager

What all links/ documents are available that summarize the best practices for Configuration Manager?
Applications and Packages
Software Updates
Operating System Deployment
Hardware/Software Inventory

Hi,
I think this may help you
system center 2012 configuration manager best practices
SCCM 2012 task-sequence best practices
SCCM 2012 best practices for deploying application
Configuration Manager 2012 Implementation and Administration
Regards, Ibrahim Hamdy

Best Practice of copying Production to Development

Hi everyone. My management would like some documentation on the Best Practice of copying Production systems to Development.
1. In the past, we've setup the clients and connections/interfaces and shrink the database by deleting unneeded production data. Now that there is note 130906, saving the ABAP versions may be easier.
2. Every two or three years we copy our BIW Production to Development. This is also labor intensive to set up the development system again with source systems.
3. We've copied our PI 70 system to a sandbox, and again this is labor intensive to reset the PI object names, since the system names are imbedded in the object names.
4. I've done java systems to, so I'm not to concerned about these.
5. There is talk of copying the following Production systems to Development systems - SLD, PI 7.1, Solution Manager, SAP R/3, BIW, MII...some of these make sense, others we question if it is worth it.
As a note, we copy our SAP R/3 Production instance to our QA environment about twice a year and to another QA system monthly. We also copy our CRM Production to our QA environment twice a year and BIW Production to QA environment once a year. We can leverage what we know about copying to PRD to QA, but we want to give them alternatives about copying PRD to DEV.
We'd like to use SAP's TDMS to move data from PRD to DEV. But unfortunately, that project has not gotten management attention as being a high priority (yet).
Rather than take my word for it, is there any SAP provided documentation that would give my management a set of alternatives on their desire to copy our Production systems to Development.
Thanks...Scott B.

From a E2E200 perspective SAP recommends the following landscape:
Maint = Dev -> QA -> Pre-Prod -> Prod
N+1 = Dev2 -> QA2 -> Pre-Prod -> Prod
Maint is all object versions to remain ideally the same versions, and only transports to fix a short dumping Prod system. N+1 is where you have implementation/upgrade projects worked on and allow you import the entire project of transports.
Another consideration, when you restore a Prod system to a Dev or new Dev system; you are destroying all of your version info which means your developers can't view or revert changes for the objects.

New Development system copy from Production

Hi All,
Hope you can help me out here with some ideas.
We are currently planning to implement a new SAP BW Development system, and for this we would like to make it a 1:1 copy of our current production system. Meaning all from customizing, ABAP, workbench objects etc.
But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
My question is then, is there any other ways to do this when system copy is a no go? I know we can do client copy but then we will not get all the workbench / ABAP programs which we need.
Any ideas on how to do this?
Thx. in Advance

Hi Rasmus,
But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
Options 1: As BI objects are cross client , copying client will not solve your purpose 100%.
You can perform system copy and then clean up data in DEV
Option 2: You can create a new Development and then create TRs for required configuration objects and move to new development system.
Option 3: Use SLO tools to perform container copy without any data.
Hope this helps.
Regards,
Deepak Kori

Development System Backup - Best Practice / Policy for offsite backups

Hi, I have not found any recommendations from SAP on best practices/recommendations on backing up Development systems offsite and so would appreciate some input on what policies other companies have for backing up Development systems. We continuously make enhancements to our SAP systems and perform daily backups; however, we do not send any Development system backups offsite which I feel is a risk (losing development work, losing transport & change logs...).
Does anyone know whether SAP have any recommendations on backuping up Development systems offsite? What policies does your company have?
Thanks,
Thomas

Thomas,
Your question does not mention consideration of both sides of the equation - you have mentioned the risk only. What about the incremental cost of frequent backups stored offsite? Shouldn't the question be how the 'frequent backup' cost matches up with the risk cost?
I have never worked on an SAP system where the developers had so much unique work in progress that they could not reproduce their efforts in an acceptable amount of time, at a acceptable cost. There is typically nothing in dev that is so valuable as to be irreplaceable (unlike production, where the loss of 'yesterday's' data is extremely costly). Given the frequency that an offsite dev backup is actually required for a restore (seldom), and given that the value of the daily backed-up data is already so low, the actual risk cost is virtually zero.
I have never seen SAP publish a 'best practice' in this area. Every business is different; and I don't see how SAP could possibly make a meaningful recommendation that would fit yours. In your business, the risk (the pro-rata cost of infrequently needing to use offsite storage to replace or rebuild 'lost' low cost development work) may in fact outweigh the ongoing incremental costs of creating and maintaining offsite daily recovery media. Your company will have to perform that calculation to make the business decision. I personally have never seen a situation where daily offsite backup storage of dev was even close to making any kind of economic sense.
Best Regards,
DB49

Is a system copy to development a best practice?

Similar Messages

Maybe you are looking for