Solution:
There are 3 resolutions to this issue. Both resolutions involve a modification to the stat.conf file followed by the bouncing of the Oracle agent(s).
The first is the preferred resolution.
1. Run SQL Plus in silent mode. Add this to the stat.conf file:
.sqlplus_options:-s
Note: If SQL Plus is run in silent mode, the log files on the OA console will not display every single line of the script. Only the SQLPlus errors will be displayed.
2. The following preprocessors are passed to SQLPlus by default in the stat.conf:
<ENV>.env.SQLPLUS_PREPROCESSORS:SET VERIFY OFF WHENEVER SQLERROR EXIT FAILURE ROLLBACK;
WHENEVER OSERROR EXIT FAILURE ROLLBACK;
Depending on the needs, the parameters can be added or removed in the stat.conf like the example below:
<env>.env.SQLPLUS_PREPROCESSORS:SET DEFINE OFF\n WHENEVER SQLERROR EXIT FAILURE ROLLBACK;\n WHENEVER OSERROR EXIT FAILURE ROLLBACK;\n SET LINESIZE 999\n
OR
<env>.env.SQLPLUS_PREPROCESSORS:WHENEVER SQLERROR CONTINUE
3. There is also the possibility to ignore passing any preprocessors by setting the value of this parameter to no value (blank value) like below:
<env>.env.SQLPLUS_PREPROCESSORS:
Note: If you drop the preprocessors there may be some SQL errors that SQLPlus does not return to Stat. Stat may think a migration was successful even though the compilation was not complete.
If the schema object is thoroughly tested before migration, this should not be an issue.
