RDBMS providers: Oracle

When using JDBC to execute scripts, Oracle's JDBC driver usually requires that statements are not terminated with a semicolon, and that long commands (such as a CREATE TABLE script with many column descriptions) contain no internal newlines. This applies to preload and postload scripts in the RDBMS Output tool, as well as scripts in the RDBMS Execute and RDBMS In-Database Processor tools. Data Management enforces these rules programmatically.

However, there are cases where Oracle requires embedded newlines and a semicolon after the final command (especially if this command is END;).

If you are using Oracle's JDBC driver and must use an embedded newline, precede it with a single backslash, the standard escape character (\). Similarly, if you must use a semicolon at the end of a command, precede it with a single backslash (\ ), or double the semicolon (;;).