Data Collection failed on 6.0.3
Hello,
I have installed my ALM platform in version 6.0.3 on Linux and I use SQL Server 2012.
No problem during the installation.
When I execute a manuel data collection, some jobs are successfull and some jobs are failed ... I d'ont understand why ???
Note that the user dcc_uses has the licence ccm_user, rm_user and qm_user. I have modified the properties "com.ibm.team.datawarehouse.service.internal.MetaDataService" on the advanced properties of each application,
to change the value ADMIN to dcc_user.
For example, when I run the job Request Management Facts, I have an error.
The liberty logs are :
==> dcc_etl_Fact_Request_RIDW.log <==
01/11/2017 10:08:55,576 [dcc_etl_Fact_Request_RIDW] INFO CRRCD2700I The RIDW ETL task begins.
01/11/2017 10:08:55,641 [dcc_etl_Fact_Request_RIDW] INFO CRRCD2900I A JDBC connection is created based on the URL jdbc:sqlserver://bdd.formation.alm:1433;databaseName=dw;, and the total number of JDBC connections is 1.
01/11/2017 10:08:55,643 [dcc_etl_Fact_Request_RIDW] INFO CRRCD3100I The resource thread pool executor is shut down successfully.
01/11/2017 10:08:55,643 [dcc_etl_Fact_Request_RIDW] ERROR
java.lang.NullPointerException
at com.ibm.rational.datacollection.etl.utils.JDBCUtil.getEndDateID(JDBCUtil.java:1538)
at com.ibm.rational.datacollection.etl.utils.ETLExecutionUtil.getLocalTransformValue(ETLExecutionUtil.java:765)
at com.ibm.rational.datacollection.etl.utils.ETLExecutionUtil.getLocalTransformValue(ETLExecutionUtil.java:1118)
at com.ibm.rational.datacollection.etl.utils.ETLExecutionUtil.initializeParams(ETLExecutionUtil.java:1088)
at com.ibm.rational.datacollection.etl.utils.ETLExecutionUtil.initializeRGParams(ETLExecutionUtil.java:1059)
at com.ibm.rational.datacollection.etl.tasks.ETLBaseTask.initialize(ETLBaseTask.java:152)
at com.ibm.rational.datacollection.etl.tasks.ETLDBTask.call(ETLDBTask.java:60)
at com.ibm.rational.datacollection.etl.tasks.ETLDBTask.call(ETLDBTask.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
==> dcc_etl.log <==
01/11/2017 10:08:55,574 [dcc_Schedule_0] INFO Data Mart to execute soon
01/11/2017 10:08:55,575 [dcc_Schedule_0] INFO CRRCD2603I The ETL task is submitted for the Fact_Request map group of the RIDW resource group.
01/11/2017 10:08:55,575 [dcc_Schedule_0] INFO CRRCD2600I The Fact_Request map group begins the ETL task.
01/11/2017 10:08:55,825 [dcc_Schedule_0] ERROR CRRCD4200E An ETL task for the Fact_Request map group failed.
==> console.log <==
Executor [Schedule] is shutdown successfully
==> dcc_etl.log <==
01/11/2017 10:08:56,559 [dcc_Schedule_0] INFO CRRCD2602I The ETL task for the Fact_Request map group ends with the following details status:
[MapGroup]Name:Fact_Request | Status: Failed | Start Time: Wed Jan 11 10:08:55 CET 2017 | End Time: Wed Jan 11 10:08:55 CET 2017 | Duration Time (milliseconds):251 | Retreived Resources: 0 | Processed Resources:0 |
Failed Resources:0 | Inserted Rows:0 | Updated Rows:0
[ResourceGroup]Name:RIDW | Status: Failed | Start Time: Wed Jan 11 10:08:55 CET 2017 | End Time: Wed Jan 11 10:08:55 CET 2017 | Duration Time (milliseconds):68 | Retreived Resources: 0 |
Processed Resources:0 | Failed Resources:0 | Inserted Rows:0 | Updated Rows:0
01/11/2017 10:08:56,560 [dcc_Schedule_0] INFO CRRCD3100I The etl thread pool executor is shut down successfully.
==> dcc.log <==
01/11/2017 10:08:56,577 [Thread-17771] INFO com.ibm.rational.datacollection.service.internal.util.DataCollectionClient - Total ETL time:11009477735
==> messages.log <==
[1/11/17 10:08:56:575 CET] 00009c25 SystemOut O Executor [Schedule] is shutdown successfully
Thanks for your help
Regards
Mathieu DEFIANAS
One answer
Hi Mathieu,
From the code line that failed, it would seem that the RIDW.D_DATE table is empty, you may want to check that. For a more complete assessment, please contact IBM Support. They should be able to take a closer look at your environment and help you determine what the issue is.
Thank you,
Clara Forero