Does your cup of Java get null point exception ?

I’m sure that the DB2 UDB users have once came across the famous java.lang.NullPointerException error when using one of IBM’s tools. The most common fix is to install any fixpacks, update java and ensure db2updv** command has been run. At least thats been the answer for me in the past.
I had a strange error when using Replication Center against one of my DB2 Replication server V9.5.   My replication scenario  involved replication from a particular subsystem in DB2 Z/OS table to a SQL Server via a Websphere Federation Server (used to be called DB2 Replication Server with relational wrapper).   While trying to list all the registered table or when I try to list all the tables to be added to a particular apply qualifier using Replication Center, I kept getting the java.lang.NullPointerException error.   After troubleshooting it for a while, I noticed that the error happens only when the list involved a particular registered table. To my surprise (or not !) I saw the CCD_OWNER column for one of the capture registered table in ASN.IBMSNAP_REGISTER table was not null.  I don’t have a CCD table in my replication scenario, so the rest of the CCD column for the registered table were  all null except for the CCD_OWNER column for the one of the table.  Apparently when the capture table was registered, the CCD_OWNER column was populated with spaces instead of null.  This threw Replication Center off.  Once I nulled that column for that particular row, replication center started listing all the registered table for that subsystem.
Replication Center throws this error if there is any data related issue on any one of the replication configuration or control tables, so next time go through the configuration tables and ensure that the data is setup right.