ERP Enterprise Administration

Originally posted by  Ashok Thiyagarajan 8/9/2009

SAP ECC 6 and MSCS configuration (Active/Standby)- HA

Sample Picture – Single SAP system in the MSCS Cluster

6 Node cluster configuration – Windows 2003 Enterprise edition.
————————————————————–

This is one of the SAP’s recommended HA configuration.

Node1 – Oracle 10G installed – 6GB RAM,Dual Xeon 16 cores – Oracle Binaries in F Local Drive and Datafiles/logfiles/controlfiles in O Shared drive for Oracle Datafiles – Called O Drives 300GB
Node2 – Oracle 10G installed – 6GB RAM,Dual Xeon 16 cores – Oracle Binaries in F Local Drive and Datafiles/logfiles/controlfiles in O Shared drive for Oracle Datafiles – Called O Drives 300GB
Node1 – First MSCS node – Running SCS – 4GB RAM – Shared Drive for SAP mount point – Called S Drive – 100GB
Node2 – Second MSCS node – Standby SCS – 4GB RAM – Shared Drive for SAP mount point -
Called S Drive
Node3 – MS Active Directory – Primary server – 2GB RAM – Local Drive
Node4 – SAP First DI instance – Local Drive F
Node5 – SAP Second DI instance – Local Drive F

You can further enhance this HA architecture more protection.

Enqueue replication server for HA.
LBR to Load balance between available DI instances.
Oracle RAC for HA and scalling purpose.

SAP Services running on the First Node (SUBSCRIBE) and MSCS running on Second Node (ECC6)

Sample Picture – Multiple SAP systems in the MSCS Cluster

Minimum Requirments

1.Shared Drives for Oracle and SAP mount point
2.MSCS installed and fully functional.
3.MS AD installed and fully functional.
4.DNS configured for all hosts
5.Linkd installed and configured if Multiple SAP to be suppored in the MS Cluster.
SAP NetWeaver 2004s SR2 and higher ABAP+Java (kernel 7.00)used.
6.Oracle Fail safe – Optional

SAP services moving to the second Node

SAP services completely moved to the second Node

Steps

All nodes are already configured with Linkd shared mount points.
1.Install Oracle binaries on node1
2.Install SAP SCS on the First node- node2 – instance # 00.S Drive
3.Install ASCS on the First node – node2 – instance # 01. S Drive
3.SAP configuration prepare on the first SCS node – node2
4.Configure the second node for the MSCS – node3
5.Install Database instance – O Drive

Test the Fail over by moving MSCS groups from node2 to node 3. All the services SCS,ASCS and Oracle will be move to the second stand by node2.

6.Install the first DI instance on node5
7.Install the second DI instance on node6
8.Check the SAP connectivity using the two DI with SAP system on Primary (active) cluster.
9.Switch over the SAP system from node2 to node3.repeat the step 8.Since the Network name (say sapcluster) and IP also switches to node3 , there should not be any problem in connecting.
10.Configure the SAP logon group for the two DI instances
11.For more HA you can configure enqueue replication server.
12.Complete the TMS and other initial configurations
13.Backup the SAP instance using BRTOOLS tools

This completes the basic overview about the SAP Active/Passive cluster implementation.

Oracle Data Warehouse Tuning – 25 Tips

Originally Posted by: Ashok Thiyagarajan 8/16/2009

Things to know about Tuning Oracle Data Warehouse Databases - 

———————————————————–

1.Dimensions and Fact Tables
2.De-Normalization
3.RAID Levels (Design) – specific to DW applications
4.Big Tablespaces – Where single datafile can grow up to 128TB
5.Block size – 16K or 32K – Depends on the Operating system
6.Partitioning Options – which needs License from Oracle
Range,Hash,List and Composite partitions
7.Partition Operations – DDL specific
8.Bitmap Indexes – Helps a lot
9.Functional base indexes
10.Data Compresssion
11.Direct Data load operations
12.Oracle Joins – Nested , Merge and Hash joins
13.SQL Tuning – Need Good understanding of SQL Tuning
14.Parallel Operations
15.Materilaized Views
16.Dimensions
17.Query Rewrite option
18.AWR reports
19.ADDM
20.SQL Tuning Advisor
21.Reoranization
22.CBO Statistics
23.SQL Hints – This helps a lot in real-time
24.Ofcourse some init.ora parameters like CBO related , MTS etc
25.IOT

RAC Features for Data Warehouse Databases
—————————————

1.Automatic Workload Management
2.Parallel Query Options
3.Parallel Instance Groups
4.DOP
5.Be aware of the Inter connect traffic
6.Services
7.Partitions specific to RAC applications
8.SQL tuning
9.Dedicated Temp tablespaces
10.TAF

Advans Distributed Networking

With the Advans Transparent Networking Appliance, (“netPulz”) a proprietary hardware/software platform, two or more disparate networks are made to appear as one, yielding a more flexible and less expensive alternative to routers and traditional WAN’s. A single “Virtual Datacenter” can be created from multiple, geographically separated ones, decreasing IT infrastructure costs while increasing network and application performance and maintaining security.

netPulz Transparent Networking Appliance

New Product!

We are very excited to announce the launch of AdvansDRM, a Donor Relationship Management System designed specifically for nonprofits and universities.

Check it out at AdvansDRM.com

Win Golf Balls for Summer!

Take our 5 Question Survey on SaaS Applications & Enter to win 2 Sleeves of Top Flite Long & Strong Golf Balls for Summer!

Take Survey!

Good Luck!!!

Facebook Privacy’s Issue is still not over…

Happy Happy Friday Bloggers! Hope everyone is super excited about the three day weekend..I sure am!!! I figured i’d make this post short since i’m sure a lot of you can’t wait to kick off their memorial day weekend asap and fire up that grill!

So i was browsing CNN.com today and noticed an article on Facebook’s privacy policy which caught my attention. If you are on FACEBOOK im sure this will take your interest. Check it out!

Have a grrrrrreat weekend! Happy Memorial Day

New Product Launch Coming Soon!

Greetings Bloggers!

Its time to get excited!!! :-) Advans is launching its newest product in the matter of weeks and is very eager to share the news with the world! The product, AdvansDRM, stands for Donor Relationship Management. Similar to a Customer Relationship Management (CRM) system, however the DRM will be targeted for non-profits and universities to use in order to track their donors efficiently. This product is very exciting since it will be launched from the Advans SaaS Cloud, therefore making the product very cost-effective and less burden on managing an in-house infrastructure yourself.

More news will come shortly on this! Get Pumped!

Signing off,

Michelle