Skip to content

Commit e151fa4

Browse files
committed
Minor
1 parent afaf8c1 commit e151fa4

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

docs/Change Logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ This page contains all of Logger's Change Logs. Starting in version 3.0.0 onward
33
<a name="change-log-3.1.0"></a>
44
##Change Log 3.1.0
55
[Download](TODO_URL)<br/>
6-
[Release Page](https://github.com/OraOpenSource/Logger/milestones/Release%203.1.0)<br/>
6+
[Release Page](https://github.com/OraOpenSource/Logger/issues?utf8=%E2%9C%93&q=milestone%3A%22Release+3.1.0%22+)<br/>
77
Release Articles
88
- [TODO_NAME](TOOD_URL)
99

docs/Installation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ To uninstall Logger simple run the following script in the schema that Logger wa
9393
You may want to [install Logger into it's own schema](#install-into-new-schema) for various reasons. Some of the most common ones are:
9494

9595
- DBA does not want to give `CREATE ANY CONTEXT` access to your user.
96-
- If this is the case, the DBA can then lock the Logger schema after running the grant scripts (below) to prevent any access to the privileged user.
96+
- If this is the case, the DBA can then lock the Logger schema after running the grant scripts (below) to prevent any access to the privileged user.
9797
- Restrict Logger to never be able to access your data. *Note: Logger does not try to reference any of your data. Some security policies require that 3rd party solutions can not reside in the same schema as your data. This follows the concept that Logger doesn't need to see your data, your schema just needs access to Logger.*
9898

9999
Once you have installed Logger into it's own schema they're two additional scripts that need to be run. The first grants the appropriate privileges to your schema and the second will create synonyms in your schema.
@@ -104,7 +104,7 @@ Run as the user with Logger installed:
104104
@scripts/grant_logger_to_user.sql <grant_to_username>
105105
```
106106

107-
If you want to restrict access to the "Logger Schema" (since it has `CREATE ANY CONTEXT privilege) you can simple lock it as `SYSTEM`:
107+
If you want to restrict access to the "Logger Schema" (since it has `CREATE ANY CONTEXT` privilege) you can simple lock it as `SYSTEM`:
108108

109109
```sql
110110
alter user <username> account lock;

0 commit comments

Comments
 (0)