Nobody can answer this type of question, except for the person who has actually ported it really: Even if it compiles, and you can install it, this doesn't mean that it will run fast (or fast enough).
It depends on the SQL features being used in the application, and how these map to the new database.
So your port could be very easy for 95% of your application, but if you have to find a quick replacement for Oracle's materialized views, it could be cumbersome on PostgreSql, for example.
So a port really starts at the design phase of an application, otherwise you might run in lots of problems, have a look at this.
In your case you have to identify all SQL features, and how easily these map on PostgreSql and MySQL.
You can see differences between PostgreSql and MySQL here, for example. I would opt for PostgreSql, because I haven't had major problems to develop applications which run on Oracle and PostgreSql: Features like window aggregates, recursive CTEs, stored procecedures in Java etc. are available in both systems.