This is caused by having a mix of Ignite-UX fileset revisions on your server. In most cases it happens when you UPDATE only one release (like Ignite-UX-11-23) even though you install other releases from that server.

An easy way to check for this case is to look at the output from the command swlist Ignite-UX. All the filesets should have the same REVISION; if not, then you need to install all consistent VERSIONS. If you have "boot helper" systems, they also need to have the Ignite-UX PRODUCT UPDATED to match the same revision as the server that they reference.

This is caused by having a mix of Ignite-UX fileset revisions on your server. In most cases it happens when you update only one release (like Ignite-UX-11-23) even though you install other releases from that server.

An easy way to check for this case is to look at the output from the command swlist Ignite-UX. All the filesets should have the same revision; if not, then you need to install all consistent versions. If you have "boot helper" systems, they also need to have the Ignite-UX product updated to match the same revision as the server that they reference.