Special Main Tan Ace

7/31/2019 Special Main Tan Ace

http://slidepdf.com/reader/full/special-main-tan-ace 1/58

System Administration Made Easy 23 –1

&KDSWHU 6SHFLDO 0DLQWHQDQFH

&RQWHQWV

Overview .................. .................. .................. .................. .................. ................... ...23 –2

Changing System Profile Parameters (Transaction RZ10) ...............................23–2

Support Packages...............................................................................................23–11

Kernel Upgrade ...................................................................................................23–40

Client Copy ..........................................................................................................23–42

Production Refresh Strategies ..........................................................................23–56



Chapter 23: Special Maintenance

Overview

Release 4.6A/B23 –2

2YHUYLHZ

In this chapter, the reader will learn about special maintena nce. This topic includes th efollowing:< Kernel upgrad e< Client copy< Prod uction refresh strategies

&KDQJLQJ 6\VWHP 3URILOH 3DUDPHWHUV 7UDQVDFWLRQ 5=

:KDW

The system profile param eters are wh at R/ 3 uses wh en it starts up. Param eters may definehow man y of each work p rocess to create, the minimu m length of the user passw ord , etc.

The system u ses the following thr ee param eters:< Start

This par ameter d efines wh ich R/ 3 services are started .< Default

This param eter d efines the p rofile for all instances in th e system.< Instance

This param eter d efines the profile for the specific instance, wh ich a llows individu alapp lication servers to be configured differently for specific tasks and users.

:K\

Change a value only for a specific pu rpose and only with pr oper know ledge of wh at isbeing changed and why it is being changed.

< If a par ameter is incorrectly changed, R/ 3 may not start.

Chang ing system p rofile parameters shou ld only be done u nd er the instruction of theSAP Hot line, SAP EarlyWatch , or an experienced consultant.

< Use RZ 10 to maintain your p rofile parameters.< Do not mod ify the files at the operating system level.

This process could lead to inconsistency an d confusion.

Before m aking changes to th e system p rofiles, make certain that you have a recent, usablecopy of the system pr ofile files. This backup is your last line of defense if a pro file change ismad e that results in R/ 3 not being able to start.




Changing System Profile Parameters (Transaction RZ10)

System Administration Made Easy23 –3

*XLGHG 7RXU

1. In the Command field, enter transaction RZ10 , and choose Enter

(or from th e SA P standard menu , choose Tools→

CCMS→

Configuration→

RZ 10 - Profile maintenance). 2. In the Profile field, choose .

3. Select the instance or defau ltprofile as ap prop riate (forexample, the instance profile, SA S

– DV EBM GS00 – PA 100767 ).

4. Choose .

The profiles used by th e system work in th e following ord er:< Start p rofile< Default p rofile (for all instan ces in the system)< Instance profile (specific to the instan ce you are on )

2

4

3






Use the instance p rofile to ma ke the par ameters of a specific app lication server “d ifferent”than the other servers for specific reasons (for examp le, a batch ap plication server).

Under Edit profiles , there are th ree selections:< Administration data

This selection is not a m aintenance mod e. It is used to chan ge the na me of the file wh erethe p rofile should be activated.

< Basic maintenance (maintenance m ode)

This mode a llows y ou to set the bu ffers, work p rocesses, and directories in the systempr ofiles. It also allows you to specify the SAP componen ts to be started (for examp le,message server, application server, SNA gateway, etc.) in start up profiles. This form of maintena nce protects most profile param eters from being chang ed by p otentiallyincorrect settings.

< Extend ed maintena nce (maintenance mode)

This mode allows you to access all system pr ofile param eters or start u p profile entries.

5. Note the Version numberof the instance pr ofile.Step 32 in this procedu reshows th e versionnum ber has changed.

6. Under Edit profile , select Extended maintenance.

7. Choose Change . 5

6

7






8. Click on the line abovewhich you want the entryto be inserted (forexample, abap/buffersize ).

9. Choose Parameter. .

The point wh ere you insert the new profile para meter ha s no effect on the p rocess.But, to make it easier to read, you m ay w ant to grou p or ord er the pa rameters (forexample, group the logon para meters together).

Once you en ter the p rofile param eter, it cannot be easily moved to another location.Therefore, be careful w here y ou choose to insert it.

10. Click in the Parameter name an dchoose .

8

9

10






11. The list that ap pea rs is long.

To find th e profile param eter you wan tto add , scroll down .

12. Select the para meter .

13. Choose .

14. A default value app ears in Unsubstituted standard value .

15. Enter the new v alue in Parameter val. (for example, enter 5 to increase theminimu m length to five).

16. In Comment , document your change byentering a description of wh y thechange was made.

The system attaches your u ser ID anddate to your comment.

17. Choose Copy .

14

15

16

17

12

13






18. This screen show s that the systeminserted your u ser ID and the date andtime of the change into the Comment .

In this wa y, you can determ ine who

mad e a pr ofile change, and when thischange was made.

19. Choose Back .

20. This screen show s the new p aram eterlogin/min_password_lng with a value of 5 inserted above abap/buffersize.

21. Choose Copy .

18

19

20

21






22. The message at the bottom of the screenindicates that th e profile was chan ged.

23. Choose Back .

24. In Version , note the p rofile’s versionnumber.

25. Choose Save .

26. Choose Yes.

23

24

25

26

22






27. Choose .

28. Choose .

Only if you hav e operation mod esconfigured , will this screen ap pear. If this screen d oes not app ear, skip to step

32.29. Double-click on Yes.

27

28

29






30. Review the check log.

31. Choose .

32. Note that the profile’s version nu mberhas changed.

Use tra nsaction RZ 11 to get the d etails of a specific profile pa ram eter.

32

31




Support Packages


6XSSRUW 3DFNDJHV

:KDW

1RWH < Hot Packages are now known as R/ 3 Sup port Packages< Legal Change Patches (LCP) are know n as R/ 3 HR Sup port Packages

A Supp ort Package is a collection of corrections tha t ad dr ess serious errors in the ABAPrepository. These corrections affect the Basis and functional areas. There are defined rulesabout w hat kind of fixes should be (and are) included in a Supp ort Package. Some ru les aretechnical w hile other ru les are policy.

A Supp ort Package is not a cumu lative fix for app lication m odu les. You mu st still get andapp ly the notes for the functional modu les. How ever, since Sup port P ackages containpatches for the various functional areas, some of the notes may be ap plied in the Supp ortPackage. The Sup port Package is not supp osed to contain functional enhan cements, but thisis not always th e case.

:K\

The pu rpose of a Supp ort Package is to fix problems before they become pr oblems.

:KHQ

There is a conflict about wh en H ot Packages should be (and are) app lied:< To prevent serious p roblems, SAP’s position is that customers sh ould a pp ly all Sup port

Packages as they are released..< The position of man y customers is that all system changes mu st be regression tested.

This stance, with the frequency of Sup port Package releases, results in the Sup portPackages not being ap plied.The reason is that the amou nt of testing required cannot be d one continu ouslyThis customer p osition is not u nique to SAP and h as been taken by m any customer ssince the early d ays of comp uting.

SAP d evelopm ent is working on w ays to make Supp ort Package application easier.

1RWH As of Release 4.5, Hot Packages have been separated from the HR Legal ChangePatch (HR LCP). This separa tion allows LCPs to be app lied qu ickly, to be in legalcompliance, and not app lying Supp ort Packages before they are sched uled to be app lied.

Before Release 4.5, the LCP contained the H ot Packages; app lying a LCP also mean tapp lying the Hot Package.




Support Packages


6WUDWHJ\Obtain the notes related to the Supp ort Package, and review w hat it fixes:< If there is nothing in the Supp ort Package that app lies to you, do not ap ply it.< If there is something in the Sup port Package that ap plies to you:

Determine if the entire Supp ort Package (or just th e note) mu st be installed.If the Sup port Package is to be installed, treat the installation as a “m ini-up grad e.”

+LJK /HYHO 3URFHVV RI $SSO\LQJ 6XSSRUW 3DFNDJHV

Applying Support Packages

1. Determine w hat Sup port Packages have been app lied to your system.

2. Get and review the notes for the Sup port Package(s).

3. Determine if the Sup port Package should be or needs to be app lied.

Steps 4 throu gh 9 assume that the Supp ort Package is to be app lied an d are rep eatedfor all Sup port Pa ckages that are to be ap plied at the curren t time.

4. Obtaining the Sup port Package

Depend ing on the size of the Supp ort Package, it can be obtained three w ays:< Down load it from th e SAPNet–R/ 3 (formerly OSS).

This option is size limited, so large Supp ort Packages cann ot be dow nloaded viaSAPNet–R/ 3.

< Down load it from SAPNet–Web.

< Upload it from the Sup port Package collection on CD.

The Support Package collection contains all Support Packages available at thatpoint in time.

Download from SAPNet – R/3(OSS)

Download from SAPNet –Web Support Package collection on CD

5. Request the Sup portPackage from th eSAPNet –R/ 3.

5. Down load theSup port Package.

5. Request the Hot Packagecollection.

6. Down load the Sup portPackage.

6. N/ A 6. Upload the Hot Package.

7. App ly the Sup port Package.

8. Execute the regression test.

9. When successful, confirm the Sup port Package.




Support Packages


'HWHUPLQLQJ :KDW 6XSSRUW 3DFNDJHV +DYH %HHQ $SSOLHG

*XLGHG 7RXU

0HWKRG

1. From the menu bar, choose System → Status .

2. On the right-hand side of thisscreen, und er SA P System data ,choose for add itionalcomponent information.

3. Choose the Patches tab .

2

3




Support Packages


4. In this examp le, the followingpatches have been applied: < SPAM update 17-Sept-99< Support Package 01 for 4.6A

Patch status values are: < N – The p atch has n ot yet been

applied. < I – Patch has been successfully

applied. < ? – Patch ap plication has been

aborted.

The Sup port P ackage name is interpreted as follows:< SAPKH<release><sequence_number>< SAPKH46A01, interpreted as SA PKH / 46A / 01 , is for Release 4.6A and is the first Sup por t Package.

0HWKRG

1. In the Command field, enter transaction SPAM and choose Enter (or from th e SA P standard menu , choose Tools → ABAP Workbench → Utilities → Maintenance → SPAM - Patches ).

2. Select Applied patches .

3. Choose Display .

3

2




Support Packages


This screen sh ows:

4. Under Applied Patches:

a. SPAM Update version level.

b. Hot Packages / Support Packages applied.

In this example, the followingpatches have been applied:

SPAM update 17-Sept-99Support Package 01 for 4.6A

*HWWLQJ ,QIRUPDWLRQ RQ WKH 6XSSRUW 3DFNDJH IURP 6$31HW²5

*XLGHG 7RXU

1. Choose Service .

2. Choose SA P Patch Service .

3. Choose R/3 support packages .

4

12

3




Support Packages


4. Search the extend ed list for you rrelease.

5. Click the nod e ( +) to the left of you r release to select it.

6. Choose .

From this screen, you can view the:

a. SPAM update

This is the SAP Sup por t PackageManager (formerly Pa tchManager). Download and applythe curren t version beforeapp lying any Supp ort Package.

b. Hot Packages

Ext ra Large indicates that the H ot

Package may not bedownloadable.

7. To d isplay the notes for a specificSup por t Package, select it, thenchoose Notes for patch.

a

b

10

5

6




Support Packages


8. To view all notes, click the nod e (-)to the left of Application areas .

9. Choose Expand .

From this screen, you m ay viewone of the following:< All notes< A sp ecific note

7R 9LHZ $OO 1RWHV

1. Right-click anywhere on thescreen.

2. Select Download list from thepopu p menu (not shown ).

8

9




Support Packages


3. Select unconverted .

4. Choose .

5. in the File name field , enter the<drive\path\filename>

where you want to save the notes.6. Choose Transfer .

This screen show s the saved n otelist as read by a text ed itor orword processor.

3

5

6

4




Support Packages


To create a file of all notes (in casethere are too man y notes to gothrou gh individu ally on the screen):

7. Choose Select all .

8. Choose List selection .

9. Choose Download to download thenotes to a file.

9

7 8




Support Packages


10. Choose N o related copy .

11. Choose N o.

Here you only w ant to review thenotes, not to register th e object forchange. After reviewing the notes,you m ay d ecide n ot to install theSup port Package.

1RWH The duration of the down load d epends on the nu mber of notes addressed by the Sup portPackage. It could take 20 minutes (or more) to dow nload th e notes for a large Sup port P ackage.

12. Enter the path to you r local PCand create a name for the file.

13. Choose Transfer .

10

13

12

11




Support Packages


7R 9LHZ D 6SHFLILF 1RWH

1. Double-click the nod e ( +) toexpand an individu al branch (forexample, BC ).

2. Double-click the nod e ( +) for BC-CCM, BC-CCM-PRN and BC-CCM-PRN-SPO .

3. Under BC-CCM-PRN -SPO , selectnote 0168529 .

4. Choose Choose .

This screen show s the SAP note.

1

2

3

4




Support Packages


5HTXHVWLQJ 63$0 RU D 6XSSRUW 3DFNDJH IURP 6$31HW²5

*XLGHG 7RXU

1. Choose Service .

2. Choose SA P Patch Service .

3. Choose R/3 support packages .

4. From the Support Packages screen,select one of the following :< SPAM update < R/3 Support Package

5. Choose Request patch.

4

5

1

2

3




Support Packages


6. Select the installation that the pa tch isfor.

7. Enter the <SID> for the system (forexample, SAS ).

8. Choose Continue .

9. The message in the status barindicates that the p atch request hasbeen generated.

10. The next step is to dow nload th epa tch (see the next section,

Downloading SPAM or a Support Package ).

6

7

9

8




Support Packages


'RZQORDGLQJ D 6XSSRUW 3DFNDJH +RW 3DFNDJH ² 6$31HW²5< Always p lan to first app ly the Sup port Pa ckage on a test server to assure it will not

create a problem.< Back up the test server before applying the Sup port Pa ckage.

3UHUHTXLVLWH

The Sup port Package(es) mu st have been requ ested for the system/<sid> to which you aredow nloading it.

*XLGHG 7RXU

1. Log on to client 000 , und er any u ser that has the SAP* equivalent auth orizations.

2. In the Command field, enter transaction SPAM and choose Enter

(or from th e SA P standard menu , choose Tools→

ABAP Workbench→

Utilities→

Maintenance→

SPAM-Patches ).

3. Choose .

From this wind ow you can specifywhich Hot Packages to download.

4. Select the Hot Package (if notalready selected).

5. Choose .

4

5

3






Support Packages


6XSSRUW 3DFNDJH &ROOHFWLRQ &'

1. Load the CD containing the patches.

2. Log on to the operating system as:

< NT: <SID>adm < UNIX: <sid>adm

3. Chang e to the transp ort directory.< NT: <drive>:\ usr\ sap\ trans < UNIX: /usr/sap/trans

4. Unp ack the patch archive.< NT: CAR –xvf <CD_drive>:\<PATH>\<ARCHIVE>.CAR

< UNIX: CAR –xvf /<CD_DRIVE>/<PATH>/<ARCHIVE>.CAR

6$31HW²:HE

1. Log on to the operating system as:< NT: <SID>adm < UNIX: <sid>adm

2. Copy the dow nloaded patch files (examp le kh46a02.car ) into an “u np ack” directory.

3. Unp ack the patch file by entering:car –xvf <patch-file>

4. Copy the un packed files from the EPS\ in directory to the directory to up load pa tches:< NT: <drive>:\ usr\ sap\ trans\ eps\ in

< UNIX: /usr/sap/trans/eps/in






Support Packages


7. Select All patches.

8. Choose Display.

9. The patch is un der New patches .

6

7

9






Support Packages


3. Choose .

4. Choose .

After app lying the SPAM up date,SPAM m ust restart to u se the latestversion.

5. Choose .

6. Restart tran saction SPAM .

7. Note the version nu mber change.

8. Select All patches.

9. Choose Disp .7

8

9

3

4

5




Support Packages


10. You w ill see the SPAM u pd ateunder Applied patches .

$SSO\LQJ WKH 6XSSRUW 3DFNDJH

3UHUHTXLVLWHV

< The R/ 3 System shou ld not be active, so no:Users are logged onJobs are run ning

< All app lication servers should be shu t dow n.< The current SPAM upd ate should have been dow nloaded from SAPNet and app lied.< The following p rogram s should be up dated to the latest version:

r3transtp

< The Hot Package should have been dow nloaded from SAPNet or up loaded from theCD.

10








Support Packages


$SSO\LQJ WKH +RW 3DFNDJH

1. The nam e of the first sup port packageappears in Patch queue .

2. Choose to app ly the patch queu e.

3. Choose .

4. Choose .

1RWH Depend ing on the size of the H ot Package, the patch ap plication process could r un for a long

time.

2

3

4

1




Support Packages


&KHFN WKH 3DWFK /RJ

1. Choose .

2. Review the return codes.

Values greater than 4 indicate afailure.

3. Choose Back .

At this p oint, regression testingshould be performed on the HotPackage.

If several H ot Packages are going in a sa grou p, the option is to confirm themafter app lying and then perform theregression testing.

2

3

1




Support Packages


&RQILUP WKH 3DWFK

1. Choose .

The next Hot Package cannot beapp lied u ntil the previous one isconfirmed.

2. Check the statu s bar to see if the patchqueue w as confirmed.

1

2








Support Packages


5HJUHVVLRQ 7HVWLQJ

Regression testing is necessary because m any objects in man y fun ctional areas may beaffected by changes from a H ot Package. All functional areas m ust p erform regression teststo verify that a Hot Pa ckage does not create new problems as it fixes old ones. A HotPackage is a “m ini-upgrad e,” especially if it is large (for examp le, Release 4.0B, Hot Package10).

All existing processes should continu e to function as they d id before the Hot Package wasapp lied. A review of the n otes related to a H ot Package indicates wh at specific tests need tobe performed by th e technical and functional team. As dur ing the implementation, thefunctional teams should have a script of test p rocedur es to test the system. This script couldalso be used in th e regression test.

8VHIXO 6$31HW ² 5 )URQWHQG 1RWHV

SAP Note # Description

19466 Dow nload ing a pa tch from SAPSERVx

33525 Imp ortan t informa tion abou t SAP pa tches < 3.1H

53902 Conflicts between Hot Packages/ LCPs and Add -ons

62119 Obtain ing extra large pa tches

73510 Problems du ring up grad e of patched source releases

82264 Imp ortan t information abou t SAP pa tches >= 3.1H

83458 OCS Info: Dow nload ing pa tches from SAPN et

84962 Info: SPAM upd ate

85820 Patch is not displayed in patch queu e

86241 HR Legal Change Patches for the HR comp onen t

87432 Conten ts of and applying LCPs

89089 Configu ration of R/ 3 Systems for LCPs

97620 OCS Info: Overview of Imp ortan t OCS Notes

97621 OCS Info: On line Correction Sup por t (OCS)

97623 Patch typ es97630 Known problems with patches >= 3.1H

104664 Applying pa tches from CD

119738 Problems du ring up grad e with too new Hot Packages

173814 Know n pr oblems with pa tches Release 4.6




Kernel Upgrade


.HUQHO 8SJUDGH

:KDWThe kernel upg rad e process is the replacing of opera ting system level files (the kernel files)with u pd ated v ersions of these files.< Special notes on the kernel version:

It is now ind epend ent of the R/ 3 release.The kernel is backward compatible, wh ich mean s that a user could be runn ing aRelease 3.0F with a 3.1I kernel.If you a re on a release before 3.1I, review d ocumentation to d etermine w hich kernelversion is app licable to you r release.

You mu st remember the R/ 3 release and kernel version you are run ning. After the kernelis upgrad ed, app ly kernel patches for the up grad ed version of the kernel. Do not app lykernel patches for the old version of the kernel.

When getting w hich patches, remem ber that your R/ 3 release stays the same, regardless of wh ich version you r kernel changes to. On ra re occasions, a SAP note instructs you to ap plya fix based on the R/ 3 release of the system; not the kernel version.

All servers in a system m ust be on the same v ersion of the kernel.

:K\

Kernel up grad es are norm ally d one to fix “bugs” or other p roblems in the kernel. Some

kernel upgrad es provid e enhanced functionality.

+RZ

To up grad e the kernel:

1. Review all app licable docum entation:< Kernel instructions< SAP notes< Upgrade manual

2. Always first perform the upgrad e on a test server.

3. Obtain the new kernel from:< SAPSERV4

This route is more current th an getting the k ernel via CD (see chapter 13, Retrieving files from SAP, SA PSERV4).

< Distribution CD (if provided )




Kernel Upgrade


< The kern el files are:dw1_nnn.CAR dw2_nnn.CAR

In this filename, nnn is the patch level (for example, dw1_114.CAR .)

4. Unp ack the kernel files (see chap ter 13, Retrieving files from SAP, SA PSERV4 for theunp acking p rocedure).

5. Back up th e system at the database and opera ting system levels.

6. Stop the R/ 3 System.

7. Stop the SAP services tha t are using the kernel files (NT).

8. Backup the kern el directory

NT: <drive>:\ usr\ sap\ <sid>\ sys\ exe\ run

UNIX: /usr/sap/<sid>/sys/exe/run

Copy the cur rent kernel files to a backup d irectory, to be prepared in the event that youneed to restore back to the old version if a pr oblem occur s with the n ew version.

9. Copy the new kernel files into the kernel directoryThis replaces the old program s with the new p rogram s.

10. Perform any special instructions contained in:< Kernel instructions< Online Service System n otes< Upgrade manual

11. Restart.

5HVWDUW 2SWLRQ

1. Restart the SAP services tha t are using the kernel files (NT).

2. Start the R/ 3 System

3. Check the R/ 3 logs.

4. Monitor the system and system logs for problems.

5HVWDUW 2SWLRQ

1. Restart the server.

2. Check all logs for:< Operating system< Database

3. Start the R/ 3 System

4. Check the R/ 3 logs

5. Monitor the system and system log for problems.








Client Copy


6HFXULW\

To perform a client copy, the user ID of the person d oing the copy mu st have the sam e auth orizations inthe source client and in the target client. A system ad ministrator with th e same au thorizations as user SAP*will have all the requ ired au thorizations.

&UHDWLQJ D &OLHQW

*XLGHG 7RXU

1. In the Command field, enter transaction SCC4 and choose Enter (or from th e SA P standard menu , choose Tools → Administration, then Administration → Client admin → Client maintenance).

2. Choose .

3. Choose .

2

3








Client Copy


&RS\LQJ D &OLHQW

*XLGHG 7RXU

&RS\LQJ RQ WKH 6DPH 6\VWHP 6,'

To copy a client on the sam e system/ <sid>, do a “local client copy.”

1. To log on to the “target client,” enter sap* for the user ID and pass for the p assword.

Be sure you are logged on to the correct target client. If you ar e on th e w rong client, youwill destroy th at client.

2. In the Command field, enter transaction SCCL and choose Enter (or from th e SA P standard menu , choose Tools → Administration, then Administration → Client admin →

Client copy → Local copy ).

3. In Selected profile , choose toselect a copy p rofile that m atchesyour requirements.

4. In Source client , enter the sourceclient nu mber (for examp le, 001 ).

5. If you r user master s w ill be copiedfrom a specific client, in th e Sourceclient user masters field, enter thisclient nu mber (for examp le, 001 ).

6. Choose Schedule as background job .

You w ill be taken to thebackground scheduling screen tocomplete the task.

7. In Background server , choose toselect the server on w hich to runthe client copy .

3

45

7

6








Client Copy


17. Choose .

18. The displayed message indicatesthe job was successfullyscheduled.

19. Choose .

&RS\LQJ WR D 'LIIHUHQW 6\VWHP 6,'

To copy a client to a d ifferent system/ <sid>, do a “r emote client copy.”

3UHUHTXLVLWH

In the target system, the:< Source system need s to be set up in transaction SM59 .< Client mu st have been created.

Copying from one system to another using rem ote client copy uses the RFC interface,therefore, there is no intermed iate storage on disk.

*XLGHG 7RXU

1. Log in to the target system and client.

Be sure you are logged in to the correct target client. If you are on th e wrong client, youwill destroy th at client.

2. In the Command field, enter transaction SCC9 and choose Enter (or from th e SA P standard menu , choose Tools → Administration → Administration → Client admin → Client copy → Remote copy).

17

18

19
















Production Refresh Strategies


+RZ

There are two w ays to refresh a system:< Database copy of the prod uction system< Client copy of the p rodu ction client

'DWDEDVH &RS\ RI 3URGXFWLRQ 6\VWHP

A databa se copy is done by copying the entire prod uction database.

%HQHILWV< The “refreshed” system will be a d up licate of the pr odu ction system.

Client-ind epend ent changes will also be captured and copied to the target system.< The copy can be mad e using standa rd ba ckup tap es, so there is no impact on the

production system.

Making a copy also tests your backup and restore process.

'LVDGYDQWDJHV< All revision history of the “refreshed” system is lost, wh ich is usua lly:

Acceptable for the test/ QA systemNot acceptable for the DEV system becau se version history is lost.

< The target database need s to be as large as the PRD database.< After the copy, the target system m ust be reconfigured .< The target system loses its client structur e and become a d up licate of the client structure

of the PRD system.

If the PRD system h as one client an d the QAS system ha s three clients, after the d atabase

copy, the QAS system w ill hav e one client. The other tw o clients are lost.

&OLHQW &RS\ RI WKH 3URGXFWLRQ 6\VWHP ZLWK 'DWD

A client copy is don e by per forming a client copy of the active client from the PRD system(instead of copying the entire d atabase, like a d atabase copy).

$GYDQWDJHV< Unlike a database copy, the target system does not hav e to be reconfigured.< The target system does not lose its client configuration.

'LVDGYDQWDJHV

< A client copy requ ires that the sou rce and targ et systems are n ot in use du ring the copy.Ha ving both systems out of use may not be a p ractical action for man y compan iesbecause the amou nt of time requ ired to d o the copy could be significantly greater thanthe amou nt of time that the prod uction system can be “dow n.”

< If there are an y client-ind epend ent objects (program s, table structures, etc.) that havebeen changed and are not th e same in th e two systems, these objects will not be copied(refer to the sections on Client Copy below).



Documents

Special Main Tan Ace