New Oracle Infrastructure2

1,028 views

Published on

Using RAC with ASM on NetApp filers in combination with SnapManager for Oracle

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,028
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • New Oracle Infrastructure2

    1. 1. A new Oracle Infrastructure Mark Leeuw
    2. 2. Our Current Architecture
    3. 3. Single instance databases glued together with DataGuard <ul><li>Simple technology </li></ul>
    4. 4. Single instance databases glued together with DataGuard <ul><li>Simple technology
    5. 5. No infrastructure integration </li></ul>
    6. 6. Single instance databases glued together with DataGuard <ul><li>Simple technology
    7. 7. No infrastructure integration
    8. 8. Many SPOFs </li></ul>
    9. 9. Single instance databases glued together with DataGuard <ul><li>Simple technology
    10. 10. No infrastructure integration
    11. 11. Many SPOFs
    12. 12. Reduces recovery times </li></ul><ul>But it's not automated !!! </ul>
    13. 13. Single instance databases glued together with DataGuard <ul><li>Simple technology
    14. 14. No infrastructure integration
    15. 15. Many SPOFs
    16. 16. Reduces recovery times
    17. 17. Not High Available </li></ul>
    18. 18. A resilient new infrastructure
    19. 19. Seeing an Oracle cluster in Action
    20. 20. Oracle RAC & ASM <ul><li>Multiple instances (RAC) </li></ul>
    21. 21. Oracle RAC & ASM <ul><li>Multiple instances (RAC)
    22. 22. Automatic failover (TAF) </li></ul>
    23. 23. Oracle RAC & ASM <ul><li>Multiple instances (RAC)
    24. 24. Automatic failover (TAF)
    25. 25. Replicated and redundant storage (ASM) </li></ul>
    26. 26. The demo system
    27. 27. The Demo System
    28. 28. The Demo System
    29. 29. The Demo System
    30. 30. Components: Network
    31. 31. Network <ul><li>Client network: business as usual </li></ul>
    32. 32. Network <ul><li>Client network: business as usual
    33. 33. Cluster interconnect: low latency </li></ul>
    34. 34. Network <ul><li>Client network: business as usual
    35. 35. Cluster interconnect: low latency!
    36. 36. Storage network: huge blocksize huge bandwidth </li></ul>
    37. 37. Components: Systems
    38. 38. Systems <ul><li>NetApp filer (FAS) </li><ul><li>Snaprestore
    39. 39. Flexclone </li></ul></ul>
    40. 40. Systems <ul><li>NetApp filer (FAS) </li><ul><li>Snaprestore
    41. 41. Flexclone </li></ul><li>Solaris 5.10/Linux 2.6 </li><ul><li>Oracle clusterware 11
    42. 42. Oracle RDBMS 11.1.0.7
    43. 43. SnapDrive 4.0
    44. 44. SMO 3 </li></ul></ul>
    45. 45. Systems <ul><li>NetApp filer (FAS) </li><ul><li>Snaprestore
    46. 46. Flexclone </li></ul><li>Solaris 5.10/Linux 2.6 </li><ul><li>Oracle clusterware 11
    47. 47. Oracle RDBMS 11.1.0.7
    48. 48. SnapDrive 4.0
    49. 49. SMO 3 </li></ul><li>Client </li><ul><li>Oracle client 8i/9i/10g/11g
    50. 50. Or native Java </li></ul></ul>
    51. 51. Components: Software
    52. 52. Software – DB Maintenance <ul><li>GridControl is Cluster/ASM aware but needs redesign
    53. 53. GridControl 10.2.0.5 supports all 11g features
    54. 54. netmgr, svrctl, dbca are cluster aware
    55. 55. 11g can run DBConsole together with GridControl </li></ul>
    56. 56. Software – Applications <ul><li>All software using ODBC (Filemaker, IIS/ASP) is 11g/RAC compatible
    57. 57. Java/JSP works but may be improved
    58. 58. Client tools ( DBArtisan, TOAD): not problem
    59. 59. ActiveBatch: Setup needs redesign </li></ul>
    60. 60. Storage
    61. 61. Storage <ul><li>NetApp filer (FAS) provides NFS shares or iSCSI disk </li></ul>
    62. 62. Storage <ul><li>NetApp filer (FAS) provides NFS shares or iSCSI disk
    63. 63. Virtual Disks are created on the OS and managed by ASM </li></ul>
    64. 64. Storage <ul><li>NetApp filer (FAS) provides NFS shares or iSCSI disk
    65. 65. Virtual Disks are created on the OS and managed by ASM
    66. 66. Oracle DB uses virtual disks coordinated by ASM </li></ul>
    67. 67. <ul>Why ASM? <li>It's mandatory for Oracle SE and RAC
    68. 68. It's the most transparent solution
    69. 69. It provides better availability </li></ul>
    70. 70. <ul>Why ASM? <li>It's mandatory for Oracle SE and RAC
    71. 71. It's the most transparent solution
    72. 72. It provides better availability </li></ul>
    73. 73. <ul>How about dNFS? <li>No need to optimize NFS manually
    74. 74. Best possible NFS performance
    75. 75. No hard mounts </li></ul>Example 1: Sample oranfstab File server: MyNFSServer1 path: 192.168.1.1 path: 192.168.1.2 path: 192.168.1.3 path: 192.168.1.4 export: /vol/oradata1 mount: /mnt/oradata1 Example 2: Enabling the Direct NFS Client ODM Library prompt> cd $ORACLE_HOME/lib prompt> cp libodm11.so libodm11.so_stub prompt> ln –s libnfsodm11.so libodm11.so
    76. 76. <ul>Shared Oracle Homes <li>Multiple systems share their software and logs, stored on NFS
    77. 77. Reduces maintenance
    78. 78. Reduces disk space requirements
    79. 79. Can be a SPOF;
    80. 80. So let's have a shared home per site. </li></ul>Quest for the home of the Oracle The home of Oracle
    81. 81. Filer fun <ul><li>Filers can create snapshots </li></ul>
    82. 82. Filer fun
    83. 83. Filer fun <ul><li>Filers can create snapshots
    84. 84. SMO coordinates and maintains consistency </li></ul>
    85. 85. Filer fun <ul><li>Filers can create snapshots
    86. 86. SMO coordinates and maintains consistency
    87. 87. SMO creates working copies of running databases using FlexClones </li></ul>
    88. 88. Source control integration Applying project changes to the new (cloned) database > svn diff --summarize --old=http://svn/CJO/trunk/sql > --new=http://svn/cjo/branches/ProjectA/sql A oracjoc#table1.sql M oracjoc#function2.sql > cat oracjoc#table1.sql oracjoc#function2.sql > new_uat.sql > sqlplus oradba@cjouat @new_uat.sql

    ×