ETL job missing
Copied the rqm-etl.zip file from the RQM server to the RCR server & ran the import job. The job reports that 10 objects were successfully impotyed.
However, there are no tasks in Cognos > Public Folders > dataMovementTasks or in the IBM Cognos Administration \Status tab there are no dataMovementTasks. Is there another location where I can source a alternative rqm-etl.zip file or am I missing something during the setup. Thanks Mike |
2 answers
Hi Mike,
This forum is for questions/issues related to Rational Insight. For questions related to RQM/RCR you're better off posting to the RQM forum: http://jazz.net/forums/viewforum.php?f=7 Lawrence |
ok
thanks log file content: Data Manager v8.4.29.13 -- Copyright (C) 2008 Cognos ULC, an IBM Company. All rights reserved. COGNOS INTERNAL USE ONLY jobstream -- start run on KFLONT (18-Jun-2010 15:34:06) Run context: JobStream 'RQMAll' JobStream 'RQM_ODS2.0' JobStream 'RQM_ODS2.0' - run id 1, audit id 2 DS_JOBSTREAM_NAME = 'RQMAll' . DS_LOB_MAXMEM_SIZE = '65536' . DS_LOB_BUF_SIZE = '8000' . DS_DBMS_TRIM = 'SPACE' . DS_UDA_FETCH_ROWS = '50' . DS_UDA_BULKWRITE_ROWS = '50' . DS_RUN_TIMESTAMP = 2010-06-18 15:34:16 . DS_JOBSTREAM_NAME = 'RQM_ODS2.0' . DS_JOBSTREAM_FNAME = 'RQM_ODS2_0' . DS_AUDIT_ID = 2 . DS_JOB_AUDIT_ID = 2 . DS_RUN_ID = 1 . DS_LOG_DIR = 'C:\Program Files\IBM\RCPR\cognos\datamanager\log' . DS_LOG_NAME = 'C:\Program Files\IBM\RCPR\cognos\datamanager\log\Job_RQM_ODS2_0_0001_000011dc129213416574050000.log' . DS_MAX_RECURSION = '100' .. TRACE_VALUES = 'PROGRESS' .. ODS = 'RIODS' .. DW = 'RIDW' .. ETL_STARTTIME = 2010-06-18 15:34:02 .. ETL_DATEID = 6013 ... TRACE_VALUES = 'PROGRESS,DETAIL,INTERNAL,SQL,EXECUTEDSQL,USER,VARIABLE' ... AUDIT_VALUES = 'TIMING,ALERT,USER' ... ODS = 'RIODS' ... DW = 'RIDW' ... RESOURCEGROUP = '' ... RESOURCEGROUP_ID = '' ... ETL_START_TIME = ... resourcegroups = ... resourcegroup_ids = ... index = 0 ... Connection = 'Rational Quality Manager' ... ResourceCategory = 'RationalQualityManager' JobStream 'RQM_ODS2.0' 'RQM_ODS'; starting Start Node 1 'Start'; Idle -> Succeeded Procedure Node 35 'init'; Pending -> Executing Procedure Node 35 'init'; executing (inline) Procedure Node 35 'init'; Executing -> Succeeded Procedure Node 35 'init'; succeeded RESULT = TRUE Condition Node 37 'hasMore'; Pending -> Executing Condition Node 37 'hasMore'; executing (inline) Condition Node 37 'hasMore'; Executing -> Succeeded Condition Node 37 'hasMore'; succeeded (TRUE) RESULT = TRUE Procedure Node 36 'preparevar'; Idle -> Executing Procedure Node 36 'preparevar'; executing (inline) Procedure Node 36 'preparevar'; Executing -> Succeeded Procedure Node 36 'preparevar'; succeeded RESULT = TRUE Build Node 43 'RQMProjects'; Pending -> Executing Build Node 43 'RQMProjects'; initializing Build Node 43 'RQMProjects'; executing (pid 4112) Build Node 43 'RQMProjects'; component 'RQMProjects', RunId 1, AuditId 3 Build Node 43 'RQMProjects'; Executing -> Succeeded Build Node 43 'RQMProjects'; succeeded RESULT = TRUE DM_COMPONENT_AUDIT_ID = 3 Build Node 32 'Category_stg'; Pending -> Executing Build Node 32 'Category_stg'; initializing Build Node 32 'Category_stg'; executing (pid 4348) Build Node 32 'Category_stg'; component 'Category_stg', RunId 1, AuditId 4 pid 4348 Build Node 32 'Category_stg'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_Category_stg_0001_000010fc129213417033410000.log) Build Node 32 'Category_stg'; Executing -> Failed Build Node 32 'Category_stg'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 4 Build Node 33 'Category'; Pending -> Executing Build Node 33 'Category'; initializing Build Node 33 'Category'; executing (pid 4788) Build Node 33 'Category'; component 'Category', RunId 1, AuditId 5 Build Node 33 'Category'; Executing -> Succeeded Build Node 33 'Category'; succeeded RESULT = TRUE DM_COMPONENT_AUDIT_ID = 5 Build Node 2 'Contributor'; Pending -> Executing Build Node 2 'Contributor'; initializing Build Node 2 'Contributor'; executing (pid 3852) Build Node 2 'Contributor'; component 'Contributor', RunId 1, AuditId 6 pid 3852 Build Node 2 'Contributor'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_Contributor_0001_00000f0c129213417277770000.log) Build Node 2 'Contributor'; Executing -> Failed Build Node 2 'Contributor'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 6 Build Node 3 'Configuration'; Pending -> Executing Build Node 3 'Configuration'; initializing Build Node 3 'Configuration'; executing (pid 5744) Build Node 3 'Configuration'; component 'Configuration', RunId 1, AuditId 7 pid 5744 Build Node 3 'Configuration'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_Configuration_0001_00001670129213417364190000.log) Build Node 3 'Configuration'; Executing -> Failed Build Node 3 'Configuration'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 7 Build Node 4 'Requirement'; Pending -> Executing Build Node 4 'Requirement'; initializing Build Node 4 'Requirement'; executing (pid 4376) Build Node 4 'Requirement'; component 'Requirement', RunId 1, AuditId 8 pid 4376 Build Node 4 'Requirement'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_Requirement_0001_00001118129213417504390000.log) Build Node 4 'Requirement'; Executing -> Failed Build Node 4 'Requirement'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 8 Build Node 5 'WorkItem'; Pending -> Executing Build Node 5 'WorkItem'; initializing Build Node 5 'WorkItem'; executing (pid 6052) Build Node 5 'WorkItem'; component 'WorkItem', RunId 1, AuditId 9 pid 6052 Build Node 5 'WorkItem'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_WorkItem_0001_000017a4129213417581700000.log) Build Node 5 'WorkItem'; Executing -> Failed Build Node 5 'WorkItem'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 9 Build Node 28 'TestPlan'; Pending -> Executing Build Node 28 'TestPlan'; initializing Build Node 28 'TestPlan'; executing (pid 4448) Build Node 28 'TestPlan'; component 'TestPlan', RunId 1, AuditId 10 pid 4448 Build Node 28 'TestPlan'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_TestPlan_0001_00001160129213417681550000.log) Build Node 28 'TestPlan'; Executing -> Failed Build Node 28 'TestPlan'; failed but continuing RESULT = FALSE DM_COMPONENT_AUDIT_ID = 10 Build Node 34 'TestPhase'; Pending -> Executing Build Node 34 'TestPhase'; initializing Build Node 34 'TestPhase'; executing (pid 4112) Build Node 34 'TestPhase'; component 'TestPhase', RunId 1, AuditId 11 pid 4112 Build Node 34 'TestPhase'; reported the following: DM-DBM-0400 UDA driver reported the following on connection Rational Quality Manager: UDA-SQL-0107 A general exception has occurred during the operation "open result". CRREE9000E: Wewnętrzny błąd Java. Szczegłowe informacje zawiera dziennik ri_jdbc.log. (for details, see Build_TestPhase_0001_00001010129213417766070000.log) Build Node 34 'TestPhase'; Executing -> Failed Build Node 6 'TestSuiteLog'; Idle -> Terminate Build Node 8 'TestSuite'; Idle -> Terminate Build Node 44 'TestScript'; Idle -> Terminate Build Node 9 'TestCase'; Idle -> Terminate Build Node 48 'BuildRecord'; Idle -> Terminate Build Node 11 'ExecutionResult2'; Idle -> Terminate Build Node 12 'ExecutionWorkItem'; Idle -> Terminate Build Node 38 'EWI_Iteration_Lookup'; Idle -> Terminate Build Node 14 'ExecutionRes_ExecWkItem_Lookup'; Idle -> Terminate Build Node 15 'ExecutionRes_WorkItem_Lookup'; Idle -> Terminate Build Node 16 'ExecutionWorkItem_Config_Lookup'; Idle -> Terminate Build Node 17 'TestCase_Category_Lookup'; Idle -> Terminate Build Node 19 'TestCase_Requirement_Lookup'; Idle -> Terminate Build Node 20 'TestPlan_Iteration_Lookup'; Idle -> Terminate Build Node 21 'TestPlan_Category_Lookup'; Idle -> Terminate Build Node 22 'TestPlan_Requirement_Lookup'; Idle -> Terminate Build Node 23 'TestPlan_TestCase_Lookup'; Idle -> Terminate Build Node 25 'TestSuite_EWI_Lookup'; Idle -> Terminate Build Node 26 'TestSuite_TestSuLog_Lookup'; Idle -> Terminate Build Node 27 'TestSuLog_ExecRes_Lookup'; Idle -> Terminate Build Node 29 'ResourceGroup'; Idle -> Terminate Build Node 30 'LabResource'; Idle -> Terminate Build Node 31 'Reservation'; Idle -> Terminate Build Node 45 'TestCase_TestScript_Lookup'; Idle -> Terminate Build Node 42 'WorkItemHistory_Stg'; Idle -> Terminate Build Node 39 'WorkItemHistory'; Idle -> Terminate Build Node 40 'Job'; Idle -> Terminate Build Node 41 'JobResult'; Idle -> Terminate Condition Node 37 'hasMore'; Succeeded -> Terminate Procedure Node 36 'preparevar'; Succeeded -> Terminate Build Node 43 'RQMProjects'; Succeeded -> Terminate Build Node 32 'Category_stg'; Failed -> Terminate Build Node 33 'Category'; Succeeded -> Terminate Build Node 2 'Contributor'; Failed -> Terminate Build Node 3 'Configuration'; Failed -> Terminate Build Node 4 'Requirement'; Failed -> Terminate Build Node 5 'WorkItem'; Failed -> Terminate Build Node 28 'TestPlan'; Failed -> Terminate Build Node 34 'TestPhase'; failed RESULT = FALSE DM_COMPONENT_AUDIT_ID = 11 Done - 0 00:02:17 elapsed JobStream 'RQM_ODS2.0' Failed jobstream -- failed (18-Jun-2010 15:36:23) i try too find some information on RQM forum In ri_jdbc.log i found: 06/16/2010 05:46:31,526 INFO com.ibm.rational.drivers.jdbc.xml.RDSStatement : CRREE1229I: Wykonywanie zapytania => select "TestSuite"."Owner", "TestSuite"."DATASOURCE_ID" from "catalog"."RQM"."TestSuite" "TestSuite" 06/16/2010 05:46:31,536 INFO com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : CRREE1231I: Żądanie początkowego adresu URL => https://10.5.35.2:9444/jazz/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/testsuite?metadata=UUID&abbreviate=false 06/16/2010 05:46:32,808 ERROR com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd 06/16/2010 05:46:32,808 ERROR com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : http error dump END 06/16/2010 05:46:32,808 ERROR com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : com.ibm.rational.etl.common.exception.ETLException: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/strict.dtd 06/16/2010 05:46:32,808 INFO com.ibm.rational.drivers.jdbc.xml.RDSStatement : Zamknij tę instrukcję 06/16/2010 05:51:16,405 INFO com.ibm.rational.drivers.jdbc.xml.RDSStatement : Zamknij tę instrukcję 06/16/2010 05:51:16,405 INFO com.ibm.rational.drivers.jdbc.xml.RDSStatement : Zamknij tę instrukcję but i can open this URL in my browser |
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.