Update some details

Author: msjuergent

articles/sap/workloads/dbms-guide-oracle.md

@@ -35,7 +35,7 @@ General information about running SAP Business Suite on Oracle can be found at 
 | 2799920 | [Patches for 19c: Database SAP ONE Support Launchpad](https://launchpad.support.sap.com/#/notes/0002799920) |
 | 974876 |  [Oracle Transparent Data Encryption (TDE) SAP ONE Support Launchpad](https://launchpad.support.sap.com/#/notes/0000974876) |
 | 2936683 | [Oracle Linux 8: SAP Installation and Upgrade SAP ONE Support Launchpad](https://launchpad.support.sap.com/#/notes/2936683) |
-| 1672954 | [Oracle 11g, 12c, 18c and 19c: Usage of hugepages on Linux](https://launchpad.support.sap.com/#/notes/1672954) |
+| 1672954 | [Oracle 11g, 12c, 18c, and 19c: Usage of hugepages on Linux](https://launchpad.support.sap.com/#/notes/1672954) |
 | 1171650 | [Automated Oracle DB parameter check](https://launchpad.support.sap.com/#/notes/1171650) |
 | 2936683 | [Oracle Linux 8: SAP Installation and Upgrade](https://launchpad.support.sap.com/#/notes/2936683) |
 | 3399081 | [Oracle Linux 9: SAP Installation and Upgrade](https://launchpad.support.sap.com/#/notes/3399081) |
@@ -56,12 +56,12 @@ Installing or migrating existing SAP on Oracle systems to Azure, the following d
 4.  Azure Premium Storage SSD should be used. Don't use Standard or other storage types.
 5.  ASM removes the requirement for Mirror Log. Follow the guidance from Oracle in Note [888626 - Redo log layout for high-end systems](https://launchpad.support.sap.com/#/notes/888626).
 6.  Use ASMLib and don't use udev.
-7.  Azure NetApp Files deployments should use Oracle dNFS (Oracle’s own high performance Direct NFS solution).
+7.  Azure NetApp Files deployments should use Oracle dNFS which is Oracle’s own high performance Direct NFS (Network File System) driver solution.
 8.  Large Oracle databases benefit greatly from large System Global Area (SGA) sizes. Large customers should deploy on Azure M-series with 4 TB or more RAM size
     - Set Linux Huge Pages to 75% of Physical RAM size
     - Set System Global Area (SGA) to 90% of Huge Page size
     - Set the Oracle parameter USE_LARGE_PAGES = **ONLY** - The value ONLY is preferred over the value TRUE as the value ONLY is supposed to deliver more consistent and predictable performance. The value TRUE may allocate both large 2MB and standard 4K pages. The value ONLY is going to always force large 2MB pages. If the number of available huge pages isn't sufficient or not correctly configured, the database instance is going to fail to start with error code: *ora-27102 :  out of memory Linux_x86_64 Error 12 : can't allocate memory*. If there's insufficient contiguous memory, Oracle Linux may need to be restarted and/or the Operating System Huge Page parameters reconfigured.
-9.  Oracle Home should be located outside of the "root" volume or disk. Use a separate disk or ANF volume. The disk holding the Oracle Home should be 64 Gigabyte in size or larger.
+9.  Oracle Home should be located outside of the "root" volume or disk. Use a separate disk or ANF volume. The disk holding the Oracle Home should be 64 Gigabytes in size or larger.
 10. The size of the boot disk for large high performance Oracle database servers is important. As a minimum a P10 disk should be used for M-series or E-series. Don't use small disks such as P4 or P6. A small disk can cause performance issues.
 11. Accelerated Networking must be enabled on all Virtual Machines. Upgrade to the latest Oracle Linux release if there are any problems enabling Accelerated Networking.
 12. Check for updates in this documentation and SAP note [2039619 - SAP Applications on Microsoft Azure using the Oracle Database: Supported Products and Versions - SAP ONE Support Launchpad](https://launchpad.support.sap.com/#/notes/2039619).
@@ -98,7 +98,7 @@ The table below details the support status
 | Azure Files NFS | Not supported | | |
 | Azure files SMB | Not supported | | |
 
-<sup>1</sup> Azure Premium SSD v2 does not have predefined storage sizes.  There is no need to allocate multiple disks within an ASM Disk Group or LVM VG.  It is recommended to allocate a single Premium SSD v2 disk with the required size, throughput and IOPS per ASM Disk Group
+<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
 <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)
 
 Other considerations that apply list like:
@@ -108,9 +108,9 @@ Other considerations that apply list like:
 2. Oracle 19c and higher fully supports 4K Native sector size with both ASM and LVM
 3. Oracle 19c and higher on Linux – when moving from 512e storage to 4K Native storage Log sector sizes must be changed  
 4. To migrate from 512/512e sector size to 4K Native Review (Doc ID 1133713.1) – see section "Offline Migration to 4KB Sector Disks"
-5.	SAPInst writes to the pfile during installation.  If the $ORACLE_HOME/dbs is on a 4K disk set filesystemio_options=asynch and see the Section "Datafile Support of 4kB Sector Disks" in MOS Supporting 4K Sector Disks (Doc ID 1133713.1)
+5.	SAPInst writes to the pfile during installation.  If the $ORACLE_HOME/dbs is on a 4K disk, set filesystemio_options=asynch and see the Section "Datafile Support of 4kB Sector Disks" in MOS Supporting 4K Sector Disks (Doc ID 1133713.1)
 5. No support for ASM on Windows platforms
-6. No support for 4K Native sector size for Log volume on Windows platforms.  SSDv2 and Ultra Disk must be changed to 512e via the "Edit Disk" pencil icon in the Azure Portal
+6. No support for 4K Native sector size for Log volume on Windows platforms.  SSDv2 and Ultra Disk must be changed to 512e via the "Edit Disk" pencil icon in the Azure portal
 7. 4K Native sector size is supported only on Data volumes for Windows platforms.  4K isn't supported for Log volumes on Windows
 8. We recommend reviewing these MOS articles:
     - Oracle Linux: File System's Buffer Cache versus Direct I/O (Doc ID 462072.1)
@@ -131,7 +131,7 @@ Checklist for Oracle Automatic Storage Management:
 3.  ASM should be configured for **External Redundancy**. Azure Premium SSD storage provides triple redundancy. Azure Premium SSD matches the reliability and integrity of any other storage solution. For optional safety, customers can consider **Normal Redundancy** for the Log Disk Group
 4.  Mirroring Redo Log files is optional for ASM [888626 - Redo log layout for high-end systems](https://launchpad.support.sap.com/#/notes/888626)
 5.  ASM Disk Groups configured as per Variant 1, 2 or 3 below
-6.  ASM Allocation Unit size = 4MB (default). Very Large Databases (VLDB) OLAP systems such as BW may benefit from larger ASM Allocation Unit size. Change only after confirming with Oracle support
+6.  ASM Allocation Unit size = 4MB (default). Very Large Databases (VLDB) OLAP systems such as SAP BW may benefit from larger ASM Allocation Unit size. Change only after confirming with Oracle support
 7.  ASM Sector Size and Logical Sector Size = default (UDEV isn't recommended but requires 4k)
 8.	If the COMPATIBLE.ASM disk group attribute is set to 11.2 or greater for a disk group, you can create, copy, or move an Oracle ASM SPFILE into ACFS file system. Review the Oracle documentation on moving pfile into ACFS. SAPInst isn't creating the pfile in ACFS by default
 8.  Appropriate ASM Variant is used. Production systems should use Variant 2 or 3
@@ -242,7 +242,7 @@ Documentation is available with:
 
 ### Monitoring SAP on Oracle ASM Systems on Azure
 
-Run an Oracle AWR report as the first step when troubleshooting a performance problem. Disk performance metrics are detailed in the AWR report.
+Run an Oracle AWR (Automatic Workload Repository) report as the first step when troubleshooting a performance problem. Disk performance metrics are detailed in the AWR report.
 
 Disk performance can be monitored from inside Oracle Enterprise Manager and via external tools. Documentation, which might help is available here:
 - [Using Views to Display Oracle ASM Information](https://docs.oracle.com/en/database/oracle/oracle-database/19/ostmg/views-asm-info.html#GUID-23E1F0D8-ECF5-4A5A-8C9C-11230D2B4AD4)
@@ -345,7 +345,7 @@ The disk selection for hosting Oracle's online redo logs is driven by IOPS requi
 
 ### Current recommendations for Oracle Storage
 
-1.  Azure Premium Storage – The majority of customers are deploying on ASM with Premium Storage
+1.  Azure Premium Storage – Most customers are deploying on ASM with Premium Storage
 2.  Azure NetApp Files - VLDB customers, often with single Oracle databases larger than 50TB are typically using ANF and leveraging Storage Snapshot capabilities of Azure NetApp Files for Backup and Restore
 3.  Managed Disk Bursting - [Managed disk bursting - Azure Virtual Machines \| Microsoft  Docs](/azure/virtual-machines/disk-bursting)
 4.  Azure Write Accelerator - used for the case that the Oracle redo log is based on Premium SSD v1 disks