You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/workloads/dbms-guide-oracle.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,8 +98,8 @@ The table below details the support status
98
98
| Azure Files NFS | Not supported |||
99
99
| Azure files SMB | Not supported |||
100
100
101
-
<sup>1</sup> Azure Premium SSD v2 doesn't have predefined storage sizes. There's no need to allocate multiple disks within an ASM Disk Group or LVM VG. It's recommended to allocate a single Premium SSD v2 disk with the required size, throughput, and IOPS per ASM Disk Group
102
-
<sup>2</sup> 512e is supported on Premium SSD v2 for Windows systems. 512e configurations are't recommended for Linux customers. Migrate to 4K Native using procedure in MOS 512/512e sector size to 4K Native Review (Doc ID 1133713.1)
101
+
1. Azure Premium SSD v2 doesn't have predefined storage sizes. There's no need to allocate multiple disks within an ASM Disk Group or LVM VG. It's recommended to allocate a single Premium SSD v2 disk with the required size, throughput, and IOPS per ASM Disk Group
102
+
2. 512e is supported on Premium SSD v2 for Windows systems. 512e configurations are't recommended for Linux customers. Migrate to 4K Native using procedure in MOS 512/512e sector size to 4K Native Review (Doc ID 1133713.1)
103
103
104
104
Other considerations that apply list like:
105
105
1. No support for DIRECTIO with 4K Native sector size. Recommended settings for FILESYSTEMIO_OPTIONS for LVM configurations:
@@ -441,13 +441,12 @@ At the time, of writing ASM for Windows customers on Azure isn't supported. The
2. During R3load migrations, the Host Cache option for SAPDATA should be set to None
450
-
3. oraarch: Windows Storage Spaces is optional
449
+
2. oraarch: Windows Storage Spaces is optional
451
450
452
451
The disk selection for hosting Oracle's online redo logs is driven by IOPS requirements. It's possible to store all sapdata1...n (tablespaces) on a single mounted disk as long as the volume, IOPS, and throughput satisfy the requirements.
453
452
@@ -459,13 +458,12 @@ The disk selection for hosting Oracle's online redo logs is driven by IOPS requi
459
458
| F:\oracle\\\<SID\>\origlogaB | Premium | None | Can be used |
460
459
| G:\oracle\\\<SID\>\mirrlogAB | Premium | None | Can be used |
461
460
| H:\oracle\\\<SID\>\mirrlogBA | Premium | None | Can be used |
2. During R3load migrations, the Host Cache option for SAPDATA should be set to None
468
-
3. oraarch: Windows Storage Spaces is optional
466
+
2. oraarch: Windows Storage Spaces is optional
469
467
470
468
### Links for Oracle on Windows
471
469
-[Overview of Windows Tuning (oracle.com)](https://docs.oracle.com/en/database/oracle/oracle-database/19/ntqrf/overview-of-windows-tuning.html#GUID-C0A0EC5D-65DD-4693-80B1-DA2AB6147AB9)
0 commit comments