RRDI setup - Exception while logging onto report server
![]()
While trying to setup RRDI on the Reporting Server, I am getting errors with the following configuration:
Content DB - On Report Server (Oracle 11g Release 2)
DataWareHouse DB - On Database server (Oracle 11g). There is a single database with all the CLM products pointing to it and have separate Tablespaces for RQM, RTC, JTS and Datawarehouse.
WAS 8.5
CLM 4.0
RRDI 2.0
When I am trying to Validate the "Configure Data Warehouse" step, I get an error that says "The schema RIDW is not empty. No objects can exist under this schema. Drop all objects before continuing."
Is it mandatory to have separate database (instead of Tablespace) for separate CLM tools, in order to access the Datawarehouse from RRDI.
----------------------------------------------------------------------------------------------------------------------------------------------
I tried to create a DataWareHouse DB on the Report Server as a separate DB, then the setup goes through to the last step.
But while executing "Initialize and Set the Rational Reporting style" (in the Build and Deploy Reporting Components step), I get an error that says "No dw connection is found."
And the Report Server log in fails with a java.lang.NullPointerException.
![]()
I would greatly appreciate any help regarding this.
|
13 answers
![]()
I have the same problem when trying to install RRDI. Why the DW must be empty? The data warehouse that we're using has data from the last 3 months. Is there any way to install RRDI without dropping an existent DW?
I will appreciate any help you may give us.
Regards,
|
![]()
Leonardo,
For your case which is migrating from previous RRDI version, you need select to run the scenario "Upgrade to this version of Rational Reporting" in the first page of setup. Comments Jin, Do you have any suggestion for me, I'm stuck on the last step and unable to complete the setup. Thanks Jin, we didn't install previous versions of RRDI, so it is not an upgrade. We upgraded JTS, CCM and RQM from 3.0.1.3 to 4.0, and now we're trying to install RRDI. We set up DW in 3.0.1.3 and then DW worked properly in 4.0 |
![]()
Leonardo,
I am afraid it is not a supported scenario. For your case, you can skip the step of "Configure Data Warehouse", the way is change the URL from ".../steps/3" to "../steps/4" |
![]()
Thanks for your answer Jin. However, in the step "Configure Data Warehouse" it says "The data warehouse is a database used for reporting and analytics. You can point to an existing data warehouse or specify values to create a new data warehouse"
So, I think it is a supported scenario. If I skip the step, will I be able to point RRDI to the DW later?
Thanks,
|
![]()
Hi Prasun/All,
I am using WAS 8.0.0.3 (32 bit), DB2 , CLM 4.0.1 and RRDI 2.0.1 (32 bit). I am facing the similar issue when i reach to the last step while setting up the RRDI. From the RRDI log file, i am getting following error. 12/20/2012 22:32:58,044 INFO com.ibm.rational.rrdi.setup.resources.DWConnectionService : CRRRA0116I: No dw connection is found. 12/20/2012 22:32:58,077 INFO com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0137I: Loading the model 12/20/2012 22:32:58,080 INFO com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0139I: Loaded the model 12/20/2012 22:32:58,104 INFO com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2038I: Connect to the report server. 12/20/2012 22:32:58,600 ERROR com.ibm.rational.rrdi.setup.steps.DeployCognosToWASStepService : com.ibm.rational.rrdi.setup.biserver.common.RRDIBIServerException: CRRRA2083E: Cannot connect to the report server. Any Idea!!! Comments Hi Manoj,
For starters, Which version of DB2 you are using (32bit or 64 bit). Make sure you use 32 bit DB2 as rest of your configuration is 32 bit. Exactly same issue is reported for Oracle database, refer to the link Workaround : RRDI Setup exception. So you need to make sure that the DB2 database instance is created with the same name as the Service that represents the instance.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.