It's all about the answers!

Ask a question

How to overcome resolve this exception in RRDI ?

Kevin Ramer (4.4k6160179) | asked Jun 20 '13, 4:22 p.m.
Installing RRDI (I've done successfully several times) and after running the RRDI setup I connect to the report server and launch Cognos Configuration.   Since our warehouse are on AIX 6.1 (64bit) I have cataloged the actual database through TCP/IP to a local alias.   In Cognos Config I go to the Configuration / Data Source Connections and open the RIDW, go onto the connection and change the connection to use the local database alias.  Then I test the connection. Instead of the "Success" I get "Failed" and this:

Handler trace back:
[the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler
[the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler
[service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler
[load_balancer] com.cognos.pogo.handlers.logic.ChainHandler
[lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler
[mdaChainHandler] com.cognos.pogo.handlers.logic.ChainHandler
[asyncMetadataServiceHandler] com.cognos.pogo.async.impl.AsyncHandler
[metadataServiceHandler] com.cognos.metadataService.bibusHandler.MDSRVHandler
Exception trace back:
Can't find resource for bundle java.util.PropertyResourceBundle, key MDSRVRequestInvoker.noResponse
java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key MDSRVRequestInvoker.noResponse
    at java.util.ResourceBundle.getObject(
    at java.util.ResourceBundle.getString(

From the description, it seems that somewhere there is a properties file missing -- but from where ? 

I have re-installed RRDI 3x today to try to resolve this ( into a new empty folder, thanks for asking ... )


2 answers

permanent link
Ali Manji (59147) | answered Jun 20 '13, 4:37 p.m.
hi Kevin - can you confirm the exact version of RRDI?  RRDI does noth have v3x (at least not yet)?  The most currently available release of RRDI is 2.0.3 (which corresponds to Jazz CLM 4.0.3).

Also what database are you using and is the db client 32-bit (and not 64-bit).

Check out this forum posting for users reporting a similar error in case their are commonalities with your env:


Kevin Ramer commented Jun 20 '13, 4:44 p.m.

RRDI is 2.0.1
DB2 v9.7 --- copied libdb2.a into RRDI_DIR/cognos/bin (bounced WAS). I did this for the 3 previous successful RRDI install.

$ find /opt/IBM -name libdb2.a -ls
532250 70020 -r--r--r--  1 root      system    71700367 May 31 11:23 /opt/IBM/RRDI_jts02/cognos/bin/libdb2.a
697256 70020 -r--r--r--  1 root      system    71700367 May 30 15:58 /opt/IBM/RRDI_jts03/cognos/bin/libdb2.a
790633 70020 -r--r--r--  1 root      system    71700367 Jun 20 15:02 /opt/IBM/RRDI_jts05/cognos/bin/libdb2.a
13993    1 lrwxrwxrwx  1 root      system          17 May  9 16:08 /opt/IBM/db2/V9.7/lib32/libdb2.a -> ../lib64/libdb2.a
14026 70020 -r--r--r--  1 bin       bin       71700367 May  9 16:14 /opt/IBM/db2/V9.7/lib64/libdb2.a

DB2 instances are 64 bit since DB2 9 (no choice)

permanent link
Kevin Ramer (4.4k6160179) | answered Jun 20 '13, 4:57 p.m.
Ha!  This is a goose chase ...   I loaded the report configuration files and I am able to run reports successfully.   The exception doesn't really give the actual result of the connection test only that some exception occurred....

Jackie Albert commented Jun 20 '13, 5:22 p.m.

Funny timing - I'm trying to set up a new ODBC connection today in Insight and I'm seeing the same error message.Will be interesting to see what resolution you get.

Your answer

Register or to post your answer.