The Java class definitions on the local and remote servers must be compatible to facilitate passing objects between servers.
For this reason, Component Integration Services assumes that compatibility exists, and any errors in object definition are detected during deserialization efforts. Objects are considered compatible if the serialized form of the object on the remote server can be used to successfully instantiate an object on the local server, or vise versa. Also, any Java method referenced in the local server in conjunction with a remotely mapped object must be defined on the remote object as well.
It is the responsibility of the database administrator to ensure that class definitions on local and remote servers are compatible. Incompatible objects and invalid method references result in deserialization errors or Java exceptions that cancel the requesting query.
To improve overall performance, increase the cis packet size configuration variable to better facilitate passing serialized objects between servers. Serialized objects are passed between servers with an image datatype, and can vary in size from a few bytes to 2GB.