Skip to Content
avatar image
Former Member

Any help expected : During removing ECC6.0 client, too long hours for VBFA

Hi exerts,

Can you provide any solutions or hints for poor performance during remoeving ERP6.0 SPS12 client?

Now, I am experiencing very long processing VBFA with very low IO.

The table contains 760K entries for each of the existing clients.

Meantime, one of them are to be removed.

6.5 hours after starting client deletion using transaction SCC5, VBFA is being removed.

Now, 10 hours later, VBFA is still subject for removal.

there are almost no I/O, except for small number of DirectRead/Sequential Read.

during this, once the client copy has been cancelled intentionally to have VBFA table updated is statistic.

and, restarted -- actually, it's rerun --

ERP6.0 SPS12

Oracle 10.2.0.4

Sun Solaris 10

Any advice should be gread helful.

thanks in advance,

Kohji

sorry for duplicate posting. thanks for the advice at ABAP General, I found this forum.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 20, 2009 at 01:23 PM

    Official answer:

    Check sap note [446485 - CC-ADMIN: Special copying options|https://service.sap.com/sap/support/notes/446485]:

    number 5. DWITH_CURS - Deleting with CURSOR WITH HOLD

    number 8. LARGEBLOCK - Using large block sizes

    number 9. LOCK_SYS - Deletion mode with system-wide exclusive locks

    Also have a look at [365304 - CC-ADMIN: Reports for deleting tables|https://service.sap.com/sap/support/notes/365304]

    Unofficial answer:

    manually delete the rows of the client. I won't give you the statement. If you don't know it, don't do it, stick to the official way.

    Best regards, Michael

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      I would alwys suggest you to delete client @ OS level as it is taking less time than SCC5

      I am not sure whether it will solve your issue for perticular talbe but you can try this for better performance

      Eg.

      To delete a client 200, you have to create a command file "del200" with following entries

      Clientremove

      Client = 200

      Select *

      Place the command file in /usr/sap/trans/bin

      $ cd /usr/sap/trans/bin

      $ R3trans u2013w <log file name> -u 1 <command file name >

      e.g $ R3trans -w del200.log -u 1 del200

      To check the progress...

      $ tail -f del200

      Regards,

      Nitin Salunkhe