¿Qué podrá estar causando el error Oracle.DataAccess.Client.OracleException ORA-06550 al generar planilla?

Se ingresó como Issue (#1075) para revisión y se encontró que se podía modificar el fuente para que Oracle no se confundiera con los "line breaks" (CR/LF para Windows) (CR para Unix/Linux).

La corrección está disponible en la versión 1.7.2.0

La investigación que hizo Carlos Reyes concluyó que el manejo de los "line breaks" era el problema. Y nos proporcionó esta documentación:

Surprisingly, Oracle can be quite picky about what characters it accepts as legitimate line breaks. In Windows, a line break is typically a carriage return (CR), line-feed pair (LF) pair; while on Unix and Linux platforms, line breaks are represented just by a carriage return. Unfortunately, depending on where your script content originates, you may inadvertently have CR/LF pairs in it. Most often, this would be the case if you read your SQL script from a file or an embedded resource – where the normal encoding would use CR/LF. Unfortunately, the error message you get from Oracle isn’t very helpful if you run into this situation:

Initialization method Tests.AnonymousBlock.TestScript threw exception: Oracle.DataAccess.Client.OracleException: Oracle.DataAccess.Client.OracleException: ORA-06550: line 1, column 6: PLS-00103: Encountered the symbol "" when expecting one of the following: begin case declare exit for goto if loop mod null pragma raise return select update while with [an identifier] [a double-quoted delimited-identifier] [a bind variable] close current delete fetch lock insert open rollback savepoint set sql execute commit forall merge pipe.

While I haven’t been able to find any definitive documentation, empirical testing shows that Oracle will accept a CR as line break but not necessarily a CR/LF pair. To be safe, I replace CR/LF pairs with CRs before using them:

command.CommandText = sql.Replace("rn", "n");