mysqlbackup | Mysql backup script for Debian | Continuous Backup library

You are showing a link to the documentation for the very old MySQL 5.6. The documentation for the current MySQL 8 says the only allowed value now is ansi. If ansi format is not good enough for you, you could install the mariadb client tools (which I believe can connect to a MySQL 8 server) and use mariadb-dump which still has the oracle option (but note that it does not actually produce oracle data types or comment syntax).

Short answer: no, not in the way you want; the type's identity (in IL) is defined by the assembly and the full type name - you can't just say "this type name, but I don't care where from"

You could perhaps just depend on DbCommand (or more generally: the APIs in System.Data.Common), rather than any provider-specific types; this is usually enough for most ADO.NET work unless you desperately need to touch provider-specific APIs, in which case: you might need to use some form of runtime reflection code (as an example: Dapper uses optimized reflection to tweak Oracle's BindByName behaviour, when it finds it). Note that ADO.NET also has a provider factory model, although it isn't much fun to work with.

Another approach is to have a core library that contains the common/shared logic, and 3 satellite libraries that all depend on that core library, and contain the provider-specific facets (obviously each satellite library would also take a package reference against one of the provider-specific APIs). Due to how transient dependencies work, your average consumer would then just need a single package-reference to their appropriate provider-specific package, for example MySqlBackup.Devart (naming is hard!).

I fixed this code by adding more lines. while executing.

After all workaround, the only solution I got is to export the schema using MySqlbackup.Net or Navicat then arranging the tables in order of their creation. First created, first to be exported. Then the import now works amazing.

Without specifying the absolute path you are making the assumption that the systemd timer is running your script from the same directory you tested it from. To remedy this, you can either use the absolute path or change directories before accessing your file.