The Data Mart is the same old data warehouse that we shipped in 1.0, 2.0 and 3.0.
In 3.0.1, we created a new data warehouse that can be shared by all CLM apps. Using the new data warehouse is the recommended path. Notice that moving to the new data warehouse will require a full ETL which could take several days to re-extract the historical data and metrics from the jazz repository.

Notice that moving to the new data warehouse will require a full ETL which could take several days to re-extract the historical data and metrics from the jazz repository.

Hi Rafiq,,


We started the DW job for the first time after the upgrade from 2.0.0.2 to 3.0.1.2.It went on for about 8 days and on the 9th day the process almost crashed. We tried it twice later, but couldnt suceed it even once.

Our DB is about 350GB and have more than 380,000 workitems and use Tomcat.

We see the below error quite often in the jazzlogs and the connection to RTC keeps dropping now and then when the DW job runs for more than 4 days. The connection regains by itself. We do not do anything. But this doesn't let us to even load a workspace in the foreground.

WARN .team.repository.servlet.AbstractTeamServerServlet - CRJAZ1413E A connection to the database could not be acquired in 3000 ms. This can happen if your server is under very high load, or if your DB server is not powerful enough to quickly process the requests from this server. The primary resolution to this problem is to use a more powerful DB server. If this problem is intermittent, increasing the JDBC Connection Pool Size or JDBC Connection Pool Wait Time properties in the Advanced Properties page might help you avoid the problem in those rare cases. CRJAZ1170I The request was made by user "{UnknownUserid}" from "xx.xx.xx.xx". CRJAZ1167I The stack trace hash is BE6944ED85A86109D575C475399FECFA98952EC4, use it to locate the previously logged stack trace at Tue Apr 17 09:21:57 GMT+05:30 2012.

So, we had no option other than stopping the job and restarting RTC once.

Our JTS JDBC pool size was 128 and Jazz - JDBC pool size was 200
We have about 160 connections to the DB at any point of time.

Do you have any recommendation for the JDBC poolsize or the waiting size ?

Do you have any comments on the setting given in https://jazz.net/library/article/790 (Is the setting recommended for Tomcat as well? )

Hi,

two months ago we migrated from 3.0.1 to 4.0.1, when im trying to create some BIRT reports the information is not complete, if i run the DW Job it takes like 2 min.

Is there any steps to "run" correctly the jobs?