Skip to content

Commit cd6b9f7

Browse files
gvasquezvargasgvasquezvargas
committed
added overview page information, and streamlined sample pages with same format
1 parent dedf46b commit cd6b9f7

File tree

9 files changed

+129
-53
lines changed

9 files changed

+129
-53
lines changed

‎advocacy_docs/migrating/oracle/workaround_overview.mdx

Lines changed: 31 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -4,44 +4,53 @@ description: "Workaround overview"
44
indexCards: none
55
---
66

7-
EDB provides a version of Postgres that is compatible with most of the built-in Oracle features. This greatly simplifies migrations from Oracle by allowing many objects and application queries to work in Postgres without having to modify them.
7+
EDB provides a version of Postgres that is compatible with most Oracle features. This greatly simplifies migrations from Oracle by allowing many objects and application queries to work in Postgres without having to modify them.
88
Additionally, EBD offers several migration tools (Migration Portal, AI Copilot, Migration Toolkit, Replication Server) that facilitate the migration of complex Oracle databases to EDB Postgres.
99

10-
For the remaining incompatibilities, EDB offers this workaround guide with practical aids for features and issues that could not be resolved automatically. It presents a collection of manual solutions to convert features and queries accompanied by examples on how to address them.
10+
For the remaining incompatibilities, EDB offers this workaround guide with practical aids for features and issues that you can't resolve automatically. It presents a collection of manual solutions to convert feature and query issues, accompanied by examples on how to address them.
1111

12-
Each workaround displays a table that contains a summary of the solution's most important things to consider.
12+
Each workaround displays a summary table with the solution's key data:
1313

14-
## Solution complexity
14+
- Complexity
15+
- Availability
16+
- Type
1517

16-
Specifies the complexity and level of effort to address the issue.
18+
## Complexity
1719

18-
- **Easy:**
19-
These workarounds require minimal effort and are easy to implement. The compatibility with EDB Postgres is very high and the solution involves simple modifications. Performing tests to validate the solution is recommended.
20+
Specifies the complexity of the solution and the level of effort required to address the issue.
2021

21-
- **Moderate:**
22-
These issues are still easily manageable and don't require a lot of backgroung knowledge. The compatibility with EDB Postgres is high and the solution involves modifications. Performing tests to validate the solution is recommended.
22+
- **1 - Easy:**
23+
Easy workarounds require minimal effort and are easy to implement. The compatibility with EDB Postgres is very high and the solution involves simple modifications. Performing tests to validate the solution is recommended.
2324

24-
- **Intermediate:**
25-
The solution may require an understanding of the Oracle database. You may need to perform troubleshooting efforts and performing comprehensive tests to validate the solution is recommended.
25+
- **2 - Moderate:**
26+
These issues are still easily manageable and don't require a lot of background knowledge. The compatibility with EDB Postgres is high and the solution involves some modifications. Performing tests to validate the solution is recommended.
2627

27-
- **Significant:**
28-
Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution may involve extensive modifications like using a combination of functions to reflect the original function. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the equivalent.
28+
- **3 - Intermediate:**
29+
The solution may require an understanding of the source Oracle database. You may need to perform troubleshooting efforts and perform comprehensive tests to validate the solution.
2930

30-
- **Difficult:**
31-
Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution will involve extensive modifications like using a combination of functions to reflect the original function. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the equivalent.
32-
31+
- **4 - Significant:**
32+
Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution involves extensive modifications like using a combination of functions to reflect the original function. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the solution.
33+
34+
- **5 - Difficult:**
35+
Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution involves extensive rewrites, using a combination of multi-level functions and the original function may not be entirely equivalent, but very similar. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the solution.
3336

3437
## Availability
3538

36-
Specifies the EDB Postgres distributions where the solution is available.
39+
Specifies the EDB Postgres distributions for which the solution is available.
3740

38-
- Yes, fully convertible to EDB Postgres and EDB Postgres Advanced Server
41+
- Yes, fully convertible to EDB Postgres and EDB Postgres Advanced Server.
3942
- No, partially convertible or no available equivalent.
4043

41-
[Are there possibly solutions that will only apply to EPAS and not to PG? Do we need a category for that?]#
44+
[Are there possibly solutions that will only apply to EPAS and not to PG? Do we need a category for that?]: #
4245

4346
## Type
4447

45-
- In Database
46-
- MP Repair Handler
47-
- Other
48+
- **In Database:**
49+
These workarounds are implemented directly in the database environment. They often involve modifying database objects such as tables, views, stored procedures, and triggers to ensure compatibility between Oracle and Postgres. This type of workaround handles differences in SQL syntax, data types, and database functions.
50+
51+
- **MP Repair Handler:**
52+
MP (Migration Portal) Repair Handlers are tools or scripts developed by EDB that automate solving compatibility issues during database migrations. These handlers can detect discrepancies between Oracle and Postgres environments and apply necessary fixes or adjustments.
53+
54+
- **Other:**
55+
This category encompasses all other types of workarounds that do not fit into the In Database or MP Repair Handler classifications.
56+

‎advocacy_docs/migrating/oracle/workarounds/BULK_COLLECT_INTO.mdx

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: 'BULK COLLECT INTO'
3+
description: "Workarounds to migrate BULK COLLECT INTO functions to Postgres"
4+
deepToC: true
5+
---
6+
7+
## Solution Summary
8+
9+
| | |
10+
|------------------|------------------------------------------------------------------|
11+
| **Complexity** | 3 - Intermediate |
12+
| **Availability** | Yes, fully convertible to PostgreSQL and EDB Postgres Advanced Server |
13+
| **Type** | In Database |
14+
15+
## BULK COLLECT INTO in Oracle
16+
17+
Description of the function in Oracle.
18+
19+
## PostgreSQL solution
20+
21+
Description of the solution in PostgreSQL.
22+
23+
## EDB Postgres Advanced Server solution
24+
25+
Description of the solution in EPAS.
26+
27+
## Migration considerations
28+
29+
Further helpful information.

‎advocacy_docs/migrating/oracle/workarounds/BULK_COLLECT_INTOB.mdx

Lines changed: 0 additions & 7 deletions
This file was deleted.

‎advocacy_docs/migrating/oracle/workarounds/NLS_SESSION_PARAMETERS.mdx

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: 'NLS_SESSION_PARAMETERS'
3+
description: "Workarounds to migrate NLS_SESSION_PARAMETERS functions to Postgres"
4+
deepToC: true
5+
---
6+
7+
## Solution summary
8+
9+
| | |
10+
|------------------|-----------------------------------------------------------------------|
11+
| **Complexity** | 2 - Moderate |
12+
| **Availability** | Yes, fully convertible to PostgreSQL and EDB Postgres Advanced Server |
13+
| **Type** | In Database |
14+
15+
16+
## NLS_SESSION_PARAMETERS in Oracle
17+
18+
Description of the function in Oracle.
19+
20+
## PostgreSQL solution
21+
22+
Description of the solution in PostgreSQL.
23+
24+
## EDB Postgres Advanced Server solution
25+
26+
Description of the solution in EPAS.
27+
28+
## Migration considerations
29+
30+
Further helpful information.

‎advocacy_docs/migrating/oracle/workarounds/NLS_SESSION_PARAMETERSB.mdx

Lines changed: 0 additions & 7 deletions
This file was deleted.

‎advocacy_docs/migrating/oracle/workarounds/V$INSTANCEB.mdx renamed to ‎advocacy_docs/migrating/oracle/workarounds/V$INSTANCE.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ deepToC: true
66

77
## Solution summary
88

9-
| | |
10-
|------------------|------------------------------------------------------------------|
11-
| **Complexity** | Easy |
12-
| **Availability** | Fully convertible to PostgreSQL and EDB Postgres Advanced Server |
13-
| **Type** | In Database |
9+
| | |
10+
|------------------|-----------------------------------------------------------------------|
11+
| **Complexity** | 1 - Easy |
12+
| **Availability** | Yes, fully convertible to PostgreSQL and EDB Postgres Advanced Server |
13+
| **Type** | In Database |
1414

1515
## V$INSTANCE in Oracle
1616

‎advocacy_docs/migrating/oracle/workarounds/index.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
title: 'Workaround list'
2+
title: 'Workaround catalogue'
33
description: "Workarounds to migrate functions and syntax from Oracle to Postgres"
44
indexCards: none
55
---
66

77
| Feature in Oracle | Description |
88
|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
9-
| [BULK COLLECT INTO](BULK_COLLECT_INTOB) | Fetches multiple rows from an SQL query into a collection (associative array, nested table, varray, etc.) in a single context switch between the SQL and PL/SQL engines. |
10-
| [NLS_SESSION_PARAMETER](NLS_SESSION_PARAMETERSB) | Provides information about the National Language Support (NLS) parameters for the current user session. |
11-
| [Pinelined function](pipelined_functionsB) | Allows a PL/SQL function to return a set of rows as a table, which can be queried like a regular table. |
12-
| [V$INSTANCE](V$INSTANCEB) | Provides information about the instance name, status, version, startup time, and host details. |
9+
| [BULK COLLECT INTO](BULK_COLLECT_INTO) | Fetches multiple rows from an SQL query into a collection (associative array, nested table, varray, etc.) in a single context switch between the SQL and PL/SQL engines. |
10+
| [NLS_SESSION_PARAMETER](NLS_SESSION_PARAMETERS) | Provides information about the National Language Support (NLS) parameters for the current user session. |
11+
| [Pinelined function](pipelined_functions) | Allows a PL/SQL function to return a set of rows as a table, which can be queried like a regular table. |
12+
| [V$INSTANCE](V$INSTANCE) | Provides information about the instance name, status, version, startup time, and host details. |
1313
| [...] | description |
1414
| [...] | description |

‎advocacy_docs/migrating/oracle/workarounds/pipelined_functions.mdx

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: 'Pipelined function'
3+
description: "Workarounds to migrate pipelined functions to Postgres"
4+
deepToC: true
5+
---
6+
7+
## Solution summary
8+
9+
| | |
10+
|------------------|-----------------------------------------------------------------------|
11+
| **Complexity** | 3 - Intermediate |
12+
| **Availability** | Yes, fully convertible to PostgreSQL and EDB Postgres Advanced Server |
13+
| **Type** | In Database |
14+
15+
## Pipelined function in Oracle
16+
17+
Description of the function in Oracle.
18+
19+
## PostgreSQL solution
20+
21+
Description of the solution in PostgreSQL.
22+
23+
## EDB Postgres Advanced Server solution
24+
25+
Description of the solution in EPAS.
26+
27+
## Migration considerations
28+
29+
Further helpful information.

‎advocacy_docs/migrating/oracle/workarounds/pipelined_functionsB.mdx

Lines changed: 0 additions & 7 deletions
This file was deleted.

0 commit comments

Comments
 (0)