Handling Exceptions in Column-Mapping Methods
Parameters in the JADE initialization file enable you to control the handling of exceptions in column-mapping methods.
You should handle any "expected" exceptions that may occur in a column-mapping method by your JADE user code in an exception handler set from within the column-mapping method.
Global exception handlers are not called for column mapping methods have exceptions being handled.
If the default value of none is specified for the NullColumnOnException parameter in the [JadeRps] section of the JADE initialization file, any exceptions raised in column-mapping methods are passed back to the Datapump application exception handler, which terminates the Datapump application. The default exception information is logged, and you can then perform one of the following actions.
-
Set the NullColumnOnException parameter value to all or selected to set the column value to null for the method or virtual property, and then restart the Datapump application.
-
Fix the problem that caused the exception and recreate the RPS database.
Set the parameter to:
-
all, if you want any exceptions raised by column-mapping methods to be handled in the Datapump application and the value of the column in the RDBMS database set to Null.
-
selected, if you want exception handling and the setting of the column in the RDBMS database to a Null value to apply only to column mapping methods and virtual properties specified in the [RpsIgnoreMethodExceptions] section of the JADE initialization file.
When the value of the NullColumnOnException parameter is set to selected, column-mapping method and virtual property exceptions are handled only for the specified class and method or virtual property name values listed in the [RpsIgnoreMethodExceptions] section of the JADE initialization file.
The [RpsIgnoreMethodExceptions] section of the JADE initialization file can contain one or more Method<n> parameters, which have a class-name::method-name or class-name::virtual-property-name value. The <n> value of the parameter syntax indicates a unique number (1, 2, 3, and so on) in ascending order; for example:
Method1 = MyRpsClass::firstMethod
Method2 = AnotherRpsClass::secondMethod
Method3 = Client::deleteClient
