Skip to content

Commit

Permalink
Edits to 3.0.2 release update #6225
Browse files Browse the repository at this point in the history
  • Loading branch information
ebgitelman authored and gvasquezvargas committed Dec 4, 2024
1 parent 61fca9d commit 9dc5049
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion product_docs/docs/livecompare/3/oracle_support.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ For example, you can define `technology = oracle` in a data connection. You can

All other data connections must be PostgreSQL.

The `user` you use to connect to Oracle must have the necessary privileges to read the data from the tables you want to compare. Specifically, `CONNECT`, `SELECT ANY TABLE` and `SELECT_CATALOG_ROLE`. These can be granted with the command:
The `user` you use to connect to Oracle must have the privileges needed to read the data from the tables you want to compare. Specifically, these privileges are `CONNECT`, `SELECT ANY TABLE`, and `SELECT_CATALOG_ROLE`. These can be granted with the command:

```sql
GRANT CONNECT, SELECT ANY TABLE, SELECT_CATALOG_ROLE TO username;
Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,5 +11,5 @@ LiveCompare 3.0.2 includes the following new features, enhancements, bug fixes,

| Type | Description | Addresses |
|:--------|:---------------------------------------------------------------------------------|:----------|
| Bug Fix | Fixed an issue which caused the application to crash when using replication sets | |
| Enhancement | Revised documentation to clarify what roles are required for Oracle | |
| Bug Fix | Fixed an issue that caused the application to crash when using replication sets. | |
| Enhancement | Revised documentation to clarify the roles that are required for Oracle. | |

0 comments on commit 9dc5049

Please sign in to comment.