Skip to Content
avatar image
Former Member

BASIS - R3trans question

Hello SAP colleagues, and thanks a lot for your replies.

I have a question about R3Trans functionality.

We have an ECC 6.0 Installation over a DB2 Database, and we were doing a client delete over R3trans at OS Level. Everything was doing smoothly and it was supposed to be "deleting" tables but at some point it stopped, telling us that there was not enough space for archive logs. The client delete stopped when it was going to erase tables starting by letter 'M'.

We had to move some parameters to correct this behaviour, until we concluded that we had to increase the FS space so it could take more rounds into circular logging, and then we backup.

But after the backup was done we launched the client delete with R3trans command supposing it was going to continue deleting where it finished last time (starting by tables with letter 'M' and so on) and we noticed that it started from scratch. Is there a reason why it started over again? Like for example, because it threw an NOT ENOUGH SPACE error a rollback happened so that is why it started again, or what could it be?

PS Is there any further documentation I could read about R3Trans program? I have read the basic documentation from SAP, but seems to be poor in detail.

Thanks a lot for your replies,

Regards.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Feb 16, 2012 at 02:20 AM

    Angel

    Just curious to know, instead of SCC5 , What advantages we will have if we delete @ OS level. We do have some client deletion requirement, i thought m i can grab some platform for thie activity form you.

    Rgds

    PR

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 17, 2012 at 11:26 AM

    Angle,

    What is the commend you used in OS level to delete client ?

    Mukul

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 18, 2012 at 02:52 PM

    compress or delete old archive log files or increase the archive log.u can delete client from transaction SCC5

    What cmd u used to delete client from OS level???

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 22, 2012 at 02:01 PM

    Angel,

    why don't you prefer scc5 to delete client rather R3trans

    and for others to delete client from OS level

    To delete a client with R3trans, a control file has to be created. This has to include the following instructions

    1. Create control file for R3trans

    vi delete<clnt number>
    clientremove
    client = <clnt number>
    select *

    2 . The command to start the deletion as

    <sid>adm@> R3trans <control-file>

    For the described example it is R3trans delete<clnt number>

    3 . If you take a look into Transaction ST04 you will read the following message: Delete from table xxx where MANDT= 'XXX'. So, there will be no selects to create small pieces and only one commit at the end of every table. This might cause into ORA-01555 if the operation takes too long. To prevent this you can increase the UNDO-RETENTION or delete with SCC5 before you delete with R3trans. So that several entries of the table will already be gone.

    Delete the client once again with transaction SCC5 after using R3trans.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 23, 2012 at 02:42 AM

    According to Naresh, exactly we do the client delete at OS via the CMD R3trans.exe plus your parameters (if Windows) or just R3trans and your parameters as well (if Unix or Linux)

    And yet we opted for SCC5, since it is recommended for SAP, and just for any other who want to know this information and I consider it to be useful: the reason why the client delete was performing slowly, it is because R3trans performs delete by deleting every single entry by every single table in a secuencial way. Making it to be so slow, and this affects performance.

    @Chandra. We had lot of space in our hard drive, so we concluded that the "NOT ENOUGH SPACE" was being thrown because of an SQL Error. But we are following your advice to compress our old archive logs if by chance again we might get into these problems again.

    Thanks to everyone for your replies.

    Best regards.

    Add comment
    10|10000 characters needed characters exceeded