4 ms·

I would think that the way to do this would be to set up realtime replication from the origin oracle DB to a db with the same schema running on something much m

I would think that the way to do this would be to set up realtime replication from the origin oracle DB to a db with the same schema running on something much more 'normal' such as mariadb, and then set up client applications and libraries and queries to the newly replicated db in a read only mode. And then setting up test client application/libraries for write mode to a copy of the replicated db and verify everything is also working normally. After confirming everything is working okay, at some point in time, have a "rip off the band aid" moment of cutting off the oracle db and declaring the replicated one as the new primary.

shrubble 3y ago
Far easier said than done. And that you mentioned MySQL/MariaDB as a possible replacement means that you have never worked with Oracle's SQL dialect.
- icedchai 3y ago
  Oracle even has its own proprietary, alternate JOIN syntax. The devil is always in the details.
  - robocat 3y ago
    Empty strings "" being NULL was a hidden issue I remember causing problems.
- walrus01 3y ago
  Didn't say it would be easy - and indeed I'm well aware that Oracle is very different than MySQL. It's a painful transition process that more organizations will find necessary as the costs and hassle of oracle increase. If the end state goal is to have zero oracle in production use, people will have to figure out some kind of transition process to migrate away incrementally.
- Shorel 3y ago
  I have worked with Oracle and MySQL was the replacement. I rewrote the dozens of PL/SQL SP into the retarded language that MySQL has. It's not impossible in any way.
- evanelias 3y ago
  MariaDB has been improving Oracle compatibility in recent years, see https://mariadb.com/kb/en/sql_modeoracle/ https://mariadb.com/kb/en/sql_modeoracle/
le-mark 3y ago
> I would think that the way to do this would be to The devil as always Is in the details. The real problem comes With stored procedures. Maybe this is why I shy away from their used to this day. The last migration I did to Postgres wasn’t too bad; the app had only a few basic stored procedures.
- icedchai 3y ago
  Many legacy apps use tons of them. In the late 90's there was a style of application development where all DB access went through stored procedures. I find PL/SQL to be terrible.
  - marcosdumay 3y ago
    PL/SQL is terrible. But organizing your Oracle database in a way where you can do everything with only application-accessible statements is even worse. Oracle places still do a lot of stored procedures.
  - kamaal 3y ago
    There are still tons of PL/SQL developers, and a huge ecosystem that uses these things. Triggers were big at one time too. You will be surprised how H1B 'specialised talent' developers are just people who have worked on these ancient technologies all life, are near impossible to replace so you are left with no options but to hire them. Oracle is a whole different specialisation in itself and its tentacles go very deep and afar.

shrubble 3y ago

Far easier said than done. And that you mentioned MySQL/MariaDB as a possible replacement means that you have never worked with Oracle's SQL dialect.

icedchai 3y ago
Oracle even has its own proprietary, alternate JOIN syntax. The devil is always in the details.
- robocat 3y ago
  Empty strings "" being NULL was a hidden issue I remember causing problems.
walrus01 3y ago
Didn't say it would be easy - and indeed I'm well aware that Oracle is very different than MySQL. It's a painful transition process that more organizations will find necessary as the costs and hassle of oracle increase. If the end state goal is to have zero oracle in production use, people will have to figure out some kind of transition process to migrate away incrementally.
Shorel 3y ago
I have worked with Oracle and MySQL was the replacement. I rewrote the dozens of PL/SQL SP into the retarded language that MySQL has. It's not impossible in any way.
evanelias 3y ago
MariaDB has been improving Oracle compatibility in recent years, see https://mariadb.com/kb/en/sql_modeoracle/ https://mariadb.com/kb/en/sql_modeoracle/

le-mark 3y ago

> I would think that the way to do this would be to The devil as always Is in the details. The real problem comes With stored procedures. Maybe this is why I shy away from their used to this day. The last migration I did to Postgres wasn’t too bad; the app had only a few basic stored procedures.

icedchai 3y ago
Many legacy apps use tons of them. In the late 90's there was a style of application development where all DB access went through stored procedures. I find PL/SQL to be terrible.
- marcosdumay 3y ago
  PL/SQL is terrible. But organizing your Oracle database in a way where you can do everything with only application-accessible statements is even worse. Oracle places still do a lot of stored procedures.
- kamaal 3y ago
  There are still tons of PL/SQL developers, and a huge ecosystem that uses these things. Triggers were big at one time too. You will be surprised how H1B 'specialised talent' developers are just people who have worked on these ancient technologies all life, are near impossible to replace so you are left with no options but to hire them. Oracle is a whole different specialisation in itself and its tentacles go very deep and afar.