Troubleshooting actual CI mappings

Use the following information to troubleshoot actual CI mappings.

If your target database is IBM® DB2®, you must run a command from a Db2 command window, before you run the actual CI mapping for the first time. You do not have to repeat the command on subsequent mappings. On Microsoft Windows, enter this command:

db2jdbcbind -url jdbc:db2://mysystem.mylab.mytown.mycompany.com:50005/maxdb75 
-user maximo -password XXXXX -size 15

On other platforms, enter this command:

./db2jdbcbind -url jdbc:db2://mysystem.mylab.mytown.mycompany.com:50005/maxdb75 
-user maximo -password XXXXX -size 15

If there are many discovered CIs, running the actual CI mapping can take a long time to import all the data. By default, even if you upgraded from a previous release and already have actual CI data, all of the discovered data is imported. If you upgraded from version 7.1.1.4 or later and have a large amount of actual CI data in your target database, you can avoid reimporting this data.

The FSNLASTSCAN table is used by the actual CI mapping to determine which top-level CIs were imported from TADDM. The table also indicates the last time a scan was done. You can modify the mapping name associated with the last scan that was performed. In this way, the next actual CI mapping imports only the data that changed since that time. To change the mapping name, run this command against your target database:

update fsnlastscan set mappingname='NewMappingName' 
where mappingname='OldMappingName'

Substitute the name of your new actual CI mapping and the name of the mapping you were using in the previous release.