You cannot force an inconsistent chunk to go online. Only the IBM technical support can do this with their support tools. Even if they manage to make it online, chances are the server will placed if in inconsistent mode.
The only way to make sure all chunks are consistent is to perform a full restore or drive south as fast as possible.
Problem is my friend my IDS instance is full of dbspaces that are NOT critcal and increase the backup time by 3 hours. I am now convinced I need to create a new instance where I can move my non critical dbspace and therfor reduce the critical backup to 2 hours.