Re: Oracle & SAP

Tip1: Prevent any non-SAP access to the database.

Tip2: SAP generates a humongous ammount of archived logs -- be sure your archive destination can handle several gigabytes per day.

Tip3: Some tables are verrrry large. It takes a large PSAPTEMP tablespace to sort your indexes.

Tip4: You need large rollback segments in a large rollback tablespace. The high rates of updating cause a high rate of rollback wraparound which causes the infamous:
 ORA-01555: snapshot too old (rollback segment too small)

Tip5: As mentioned in Tip2, SAP generates a humongous ammount of redo logs. We now use 4 groups of mirrored 200MB redo log files.

Tip6: Monitor table I/O activity and separate high activity tables to balance load.

Tip7: SAP data accumulates forever. This means your database will grow beyond all bounds, backups take longer and longer, recoveries take longer and longer, table scans take longer and longer. The answer is to implement SAP Data Archiving (not to be confused with Oracle redo log archiving (mandatory) ).

Tip8: SAP is an INTEGRATED system of 10,000 tables, 13,000 indexes, and 2,000 views. Oracle provides the capability to rollback the entire database to a prior point in time. But how can you employ this? Can your users re-enter all the transactions that are lost by a rollback? My point is that you need a way to do a LOGICAL recovery. I have BMC's DB Log Master For Oracle to examine the redo and/or archived logs for before and after row images.

sanjay_at_oseda.missouri.edu wrote:
>
> Hi all,
> I have taken over a SAP/Oracle system and while I am comfortable
> with administering Oracle, handling SAP data is new to me.
> Any DBAs out there who can warn me against gotchas or recommend
> some best practices ?
> TIA
> sanjay
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
  Received on Sat Mar 28 1998 - 00:00:00 CST