diff --git a/filter-plugin/logstash-filter-oua-guardium/OuaOverPipeReadme.md b/filter-plugin/logstash-filter-oua-guardium/OuaOverPipeReadme.md
index cf3ee9023..1500a797b 100644
--- a/filter-plugin/logstash-filter-oua-guardium/OuaOverPipeReadme.md
+++ b/filter-plugin/logstash-filter-oua-guardium/OuaOverPipeReadme.md
@@ -44,10 +44,9 @@ Update the variables in Makefile for your environment's Java home and Logstash l
          CREATE USER guardium IDENTIFIED BY password;
          GRANT CONNECT to guardium;
          GRANT SELECT ANY DICTIONARY to guardium;
-         GRANT AUDIT_VIEWER to guardium;
-         GRANT SELECT ON v$INSTANCE to guardium;
-         GRANT SELECT ON v$DATABASE to guardium;
-         GRANT SELECT ON v$MYSTAT to guardium;
+         GRANT SELECT ON v_$INSTANCE to guardium;
+         GRANT SELECT ON v_$DATABASE to guardium;
+         GRANT SELECT ON v_$MYSTAT to guardium;
          ```
 
        - For other environments including RDS in AWS and Oracle Databases On-Premises run the following commands:
@@ -101,4 +100,4 @@ Update the variables in Makefile for your environment's Java home and Logstash l
 ## Limitation
 - Normally, the "statement type" attribute for the "FULL SQL" entity in Guardium reports shows us whether a full SQL statement is a prepared statement. However, because OUA doesn't give us information about whether a statement is a prepared statement or not, the "Statement type" attribute is not applicable for the OUA universal connector plug-in.
 - The "record affected" field is not supported when using Oracle with the universal connector.
-- If you restart the database, then any Universal Connector that uses the OUA plugin must also be restarted.
\ No newline at end of file
+- If you restart the database, then any Universal Connector that uses the OUA plugin must also be restarted.