How to recovery a deleted client

[Former Member]

Hi,

can we recovery a CLIENT that's deleted?

if yes, please show me steps to do this

my email: longnv@cybersoft-vn.com

Thank you very much

Long

[Former Member]

Hi,

If you have backup :

1. Restore system "offsite" from backup (before deletion)

2. Preform client export

3. Copy files and perform client import on target system

If you do not havebackup :

If you need just client without previously deleted data - just perform client copy from most suitable client.

[Former Member]

Hi. How you delete the client? What your steps?

[Former Member]

Hi,

Thank you for your reply

We deleted with steps:

1. log into the client to delete

2. go into SCC5 and delete client

3. log into another client and delete entry with SCC4

note: we not backup database before

Thanks

Long

[antonio_voce]

Hi dear,

IT is NOT possible to recovery without a backup.

Please look carefully this oss note.

pls reward if this help you , thanks

Note 31496 - CC-INFO: Client deleted by mistake

Summary

Symptom

A client was deleted or overwritten by mistake. How can it be recovered.

Additional key words

SCC0, SCC5, SCC8, SCC9, SCCL

Cause and prerequisites

Handling error

Solution

There is no "Undo" for the client copy and an "Undo" cannot be available in view of the size of the dataset. You must therefore make use of a database backup. All described measures should be carried out by an experienced consultant.

You should avoid that such an accident occurs to a productive client by calling up Transaction SCC4 and setting the status of the client to 'Productive'. In addition, for 'Protection: Client Copier and comparison tool' choose the setting 'Protection level 1: No overwriting' (as of Release 4.0). For releases prior to 4.0 under 'Restrictions' choose the setting 'Protection against overwrite by copying'.

To recover a client, SAP provides the new copy profile SAP_RECO in the following Support Packages as of Release 4.5B:

SAPKH45B31 SAPKB46B17 SAPKB46C08 SAPKB46D03

To be able to schedule a copy with SAP_RECO in the background, the advance correction given below should additionally be implemented. Without this correction, the copy is an ordinary copy with SAP_ALL. This additional correction is delivered with the following Support Packages.

SAPKH45B35 SAPKB46B22 SAPKB46C12 SAPKB46D04

In Release 4.5B, you can also use Note 96732 (as of KDIK000202) as an alternative; it allows to use parallel processes in 4.5B as well. (It is true that the note was written for DB2/390, but you can use it nevertheless for other databases as well.) Before you implement Note 96732, you must read it, since it carries out considerable changes to the SAP standard programs. This may cause additional efforts e.g. after the import of Support Packages.

Local settings stored in the tables of delivery class 'L' are only copied with copy profile SAP_RECO. Otherwise, this data is deleted, since it only makes sense in identical environments (system configuration, client, etc.). This affects e.g. SPOOL data (printer administration) and personal settings of the users.

SAP recommends to check prior to the client copy using report RSCCEXPT whether important tables have been excluded manually from the copy.

Procedure:

Example: The client was deleted today at 10:30 o'clock. The last database backup was made yesterday at 22:00 o'clock.

If your database product supports 'Point-in-time recovery', there are - besides restoring today's status of 10:29 - two options:

1. Recovery of all current changes with the fallback system recommended by SAP

a) Import of the backups from yesterday evening into the fallback system

b) Only if the lost client was changed between yesterday evening and the deletion: import the log files to restore the database status of 10:29 (point in time recovery).

c) Copy the client into your main system using the Client Copy tool. (As of Release 4.5B with copy profile SAP_RECO or as of Release 3.0F with SAP_ALL).

o As of Release 4.0, you can use a remote copy (Transaction SCC9) to copy large clients as well.

o The second option is to export the client with transaction SCC8 (or up to and including Release 3.0F Transaction SCC2) into the main system. Please see Note 70547 for this. In particular, postprocessing is absolutely required.

d) If you use profile SAP_ALL instead of SA_RECO in the Releases 4.5A through 4.6B, tables CDPOS, PCDPOS (from cluster CDCLS) and tables CDHDR and PCDHDR should be copied in addition. They can be exported and imported e.g. with an R3trans script as described in Note 68896 under Solution 1.c).

• Advantage: all current changes are saved

• Disadvantages:

o A second system (the fallback system recommended by SAP) is required.

o Without copy profile SAP_RECO, localized data are missing from class 'L' tables.

o If the client is very large, the copy may take rather long.

2. Recovery of all current changes, if the fallback system recommended by SAP is not available.

a) Saving the entire database (e.g. tonight, if there is no further activity).

b) Import of last night's backup.

c) Only, if the lost client was changed in the time from last night and the deletion: Import the log files to bring the database to the status of 10:29 (point in time recovery).

d) Saving the client with the client copy tool. (As of Release 4.5B, with copy profile SAP_RECO or as of Release 3.0F with SAP_ALL.)

o As of Release 4.0, you can copy the client to an unused client of another system - with the same release and repository status and, if SAP_RECO is used, the same client number, too - using a remote copy (transaction SCC9).

o The second option is to export the client with transaction SCC8 (or up to and including Release 3.0F Transaction SCC2) into the file system. Please see Note 70547 for this.

e) If you use profile SAP_ALL instead of SA_RECO in the Releases 4.5A through 4.6B, tables CDPOS, PCDPOS (from cluster CDCLS) and tables CDHDR and PCDHDR should be copied in addition. They can be exported and imported e.g. with an R3trans script as described in Note 68896 under Solution 1.c).

f) Bring the database to the status of tonight (by importing the backup or the log files).

g) Copy client back or import it. In the case of an import, please see Note 70547. In particular postprocessing is absolutely required.

h) Import of tables CDPOS, PCDPOS, CDHDR and PCDHDR, if they were recovered acc. to 2.e).

• Advantage: All changes are saved.

• Disadvantages:

o The action is more complicated and takes longer.

o Without copy profile SA_RECO, localized data are missing from class 'L' tables.

o If the clients are rather large, the copy may take very long.