String
None
Purpose
The NullColumnOnException parameter specifies what happens when an exception occurs in a column‑mapping method, the mapping method for a virtual property, or blob, slob, or slobutf8 mapping method and the exception is not handled by an exception handler armed from within the method.
The column is set to a null value and the Datapump application continues or the transaction is aborted and the Datapump application is stopped.
Arm a local exception handler in a column‑mapping method, the mapping method for a virtual property, or blob, slob, or slobutf8 mapping method for any exception that is expected to occur. Global exception handlers are not called for exceptions within such a method.
The values that you can specify for the NullColumnOnException parameter and the consequences of those settings are listed in the following table.
| Value | Column is Set to a Null Value and the Datapump Application Continues |
|---|---|
| all | Yes |
| selected | Yes (if the column-mapping method, the mapping method for a virtual property, or the blob, slob, or slobutf8 mapping method is listed in the [RpsIgnoreMethodExceptions] section) or No (if the method is not listed in the section) |
| none | No |
If the Datapump application is stopped, default exception information is logged. You can:
Change the JADE initialization file so that the column value is set to null for this method and restart the Datapump application
Fix the problem that caused the exception and recreate the RPS database
When an exception occurs and a column is set to a null value, the exception is logged to the file specified by the LogNullColumnOnException parameter.
If the LogNullColumnOnException parameter has a null value, no exception information is logged.
The NullColumnOnException parameter is not created or updated by the RPS Manager application.
Parameter is read when …
The Datapump application is started.
Applicable to database role or subrole…
RPS node only.