Skip to Content
avatar image
Former Member

10.2 Oracle sapdata layout - performance issues?

Can someone provide the pros cons of /oracle layout for ERP 6.0 production system?

Is it better to build several additional sapdatas.

Initially SAP loads data into sapdata 1 through sapdata4.....

Has anyone seen any possible performance issues only using sapdata1-4 especially with a 3 TB DB running 10.2.04?

Any advice is appriciated...

Thanks

Mikie B

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Sep 24, 2009 at 03:51 PM

    Hello Mikie,

    > Initially SAP loads data into sapdata 1 through sapdata4....

    What do you mean with this?

    > Is it better to build several additional sapdatas.

    This depends on your storage. Normally if you have a high-range SAN storage it shouldn't matter. I have seen special cases where some disk ranks were overloaded .. but normally you should not think about that. If you don't have SAN and your load needs to be spread .. this is something different.

    > Has anyone seen any possible performance issues only using sapdata1-4 especially with a 3 TB DB running 10.2.04?

    Our main logistic system is round about 3.6 TB and stored in eleven sapdata directories .. but this partitioning has nothing todo with performance issues ... the reason for that is some limitation on OS level.

    Regards

    Stefan

    P.S.:

    > Can someone provide the pros cons of /oracle layout for ERP 6.0 production system?

    If i extend or create a new tablespace i am wondering every time .. why sap is creating a sub directory for every data file by default .. absolutely freaky.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 24, 2009 at 05:21 PM

    During a typical SAP by default sapinst specifies sapdata1,2 3, 4 for loading tables etcetc.

    Add comment
    10|10000 characters needed characters exceeded

    • > During a typical SAP by default sapinst specifies sapdata1,2 3, 4 for loading tables

      True.

      I think the main reason for this is "historical" where databases directories were physically spread across different disks because RAID was either unavailable or too expensive or too slow.

      If all those sapdataX are on the same SAN it doesn't matter if you have one, two or ten of them (in regards to performance). OS imposed restrictions may limit that but from a performance perspective there's no difference.

      Markus