5 Replies Latest reply on Sep 19, 2011 6:25 PM by Oscar Avila

    ETL Job Failing on UPDATE_COGNOS

    Kate Fell

      The ETL job was working fine but has now started failing.

       

      Tue Aug 2 16:53:01 2011:Starting run_etl.

      Tue Aug 2 16:53:01 2011:Checking for the existence of lock file.

      Tue Aug 2 16:53:01 2011:Creating lock file for this run.

      Tue Aug 2 16:53:01 2011: Properties File Name:  RunETL.properties

      Tue Aug 2 16:53:01 2011: Context Name:  CTX_SITE1

      Tue Aug 2 16:53:01 2011: Log Level:  3

      Tue Aug 2 16:53:02 2011: Level of Parallelism:  20

      Tue Aug 2 16:53:02 2011: Removing orphaned exstat files.

      Tue Aug 2 16:53:02 2011: Finished removing orphaned exstat files.

      Tue Aug 2 16:53:02 2011: Retrieving the scenario list of executable scenarios.

      Tue Aug 2 16:53:03 2011: Starting scenario execution

      Tue Aug 2 16:53:07 2011: Executing domain 0_BSARA_ETL

      Tue Aug 2 16:59:00 2011: Completed execution for domain 0_BSARA_ETL

      Tue Aug 2 16:59:00 2011: Call to Update Cognos scenario.

      Tue Aug 2 16:59:04 2011: Error: UPDATE_COGNOS scenario terminated with an error. Exit Code: 88

      Tue Aug 2 16:59:04 2011: Completed call.

      Tue Aug 2 16:59:05 2011: Completed succesful execution for domain 0_BSARA_ETL

      Tue Aug 2 16:59:05 2011: Error: 4_UPDATE_COGNOS  domain exited with status  88

      Tue Aug 2 16:59:05 2011:    Following are the possible causes for this failure:

      Tue Aug 2 16:59:05 2011:    1) Domain  4_UPDATE_COGNOS is already running in another instance.

      Tue Aug 2 16:59:06 2011:       Please navigate to the Metadata navigator and check if any other ETL runs are in progress for the same site.

      Tue Aug 2 16:59:06 2011:       If this is not so, please use the stop_etl.nsh script to stop and reset the ETL.

      Tue Aug 2 16:59:06 2011: Removing exstat files for this run.

      Tue Aug 2 16:59:06 2011: Finished removing exstat files.

      Tue Aug 2 16:59:06 2011: Removing lock file.

       

      The Stop_etl.nsh script has been run but this doesn't fix the issue.

       

      In the Update_Cognos_Model_Properties.log there are a bunch of errors:

       

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'IS_SCHEDULED' under the same parent. Please choose a unique name.

       

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'JOB_PART_TIMEOUT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'JOB_TIMEOUT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'ADMIN_ACCOUNT' under the same parent. Please choose a unique name.


      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'CUSTOMER' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'DEPLOYNAME' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'DEPLOYPATH' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'FQ_HOST' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'FUNCTION' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'HOST' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'HOSTIP_BITS' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'IS_DEPLOYABLE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'IS_ONLINE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'IS_SOLARIS_LIVE_UPGRADE*' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'IS_VIRTUAL*' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'LAST_UPDATED_DATE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'LIFECYCLE*' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'NETWORK_ADDRESS' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'ON_EDGE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'OS_PATCHLEVEL' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'OS_PLATFORM' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'OS_VENDOR' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'PUSH_ACL_NO_USERS_FLAG' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'REPEATER_NAME' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'REPEATER_STAGING_DIR' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'ROLLBACKPATH' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'RSCD_DIR' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'RSCD_VERSION' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'SOLARIS_ALTERNATIVE_BOOT_ENV*' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'STAGING_DIR' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'SUBNET_MASK' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'SYSTEMROOT' under the same parent. Please choose a unique name.

      Toiminto: Modify
      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'TRANSACTIONS_DIR' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'WINDIR' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'VIRTUALIZATION*' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'VM_HOST' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'VM_VIRTUAL_MACHINE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'TARGET' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'TEMPLATE' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'AUTO_GENERATED' under the same parent. Please choose a unique name.

      BMT-MD-0012 Another object of type 'Query Item' already exists with the name 'BROKEN_OBJECT' under the same parent. Please choose a unique name.

       

      Cognos error.png

        • 1. ETL Job Failing on UPDATE_COGNOS
          Kate Fell

          The results of the stop_etl

           

          tpitblrpt01% stop_etl.nsh -s 1 -v 80

          Stopping ETL.

          Parameter verification:

              Site Id:  1

              OM Version:  80

          Navigating to ETL path...

          Completed.

          Removing orphaned exstat files.

          Finished removing orphaned exstat files.

          Checking lock file for Site Id: 1

          Could not remove lock file for Site Id: 1

          Proceeding with Database Reset.

          Stop ETL is successful.

          tpitblrpt01%

          • 2. ETL Job Failing on UPDATE_COGNOS
            Kate Fell

            Once the lock was removed the ETL job ran successfully... see page 69 of the Administration guide.

            • 3. ETL Job Failing on UPDATE_COGNOS
              Oscar Avila

              Hi.

               

              I have the same problem but I did the steps indicated in the log file and the scenario 4_UPDATE_COGNOS is failing.

               

              When I stoped the etl job appears:

               

               

              SOFCBBDSA01% ./stop_etl.nsh -s 1 -v 81

              Stopping ETL.

              Parameter verification:

                  Site Id:  1

                  OM Version:  81

              Navigating to ETL path...

              Completed.

              Removing orphaned exstat files.

              Finished removing orphaned exstat files.

              Checking lock file for Site Id: 1

              Could not remove lock file for Site Id: 1

              Proceeding with Database Reset.

              Stop ETL is successful.

               

              but I couldn't see any lock file "props.look" like says the Administration Guide, I am runing the "run_etl.bat" on Windows Server 2008, The log file juts show:

               

              Mon Sep 19 16:30:42 2011:Starting run_etl.

              Mon Sep 19 16:30:43 2011:Checking for the existence of lock file.

              Mon Sep 19 16:30:43 2011:Creating lock file for this run.

              Mon Sep 19 16:30:43 2011: Properties File Name:  RunETL.properties

              Mon Sep 19 16:30:43 2011: Context Name:  CTX_SITE1

              Mon Sep 19 16:30:43 2011: Log Level:  3

              Mon Sep 19 16:30:44 2011: Level of Parallelism:  20

              Mon Sep 19 16:30:44 2011: Removing orphaned exstat files.

              Mon Sep 19 16:30:45 2011: Finished removing orphaned exstat files.

              Mon Sep 19 16:30:46 2011: Retrieving the scenario list of executable scenarios.

              Mon Sep 19 16:30:46 2011: Starting scenario execution

              Mon Sep 19 16:30:55 2011: Executing domain 0_BSARA_ETL

              Mon Sep 19 16:42:17 2011: Completed execution for domain 0_BSARA_ETL

              Mon Sep 19 16:42:17 2011: Call to Update Cognos scenario.

              Mon Sep 19 16:42:31 2011: Error: UPDATE_COGNOS scenario terminated with an error. Exit Code: 88

              Mon Sep 19 16:42:31 2011: Completed call.

              Mon Sep 19 16:42:31 2011: Completed succesful execution for domain 0_BSARA_ETL

              Mon Sep 19 16:42:32 2011: Error: 4_UPDATE_COGNOS  domain exited with status  88

              Mon Sep 19 16:42:32 2011:    Following are the possible causes for this failure:

              Mon Sep 19 16:42:33 2011:    1) Domain  4_UPDATE_COGNOS is already running in another instance.

              Mon Sep 19 16:42:33 2011:       Please navigate to the Metadata navigator and check if any other ETL runs are in progress for the same site.

              Mon Sep 19 16:42:33 2011:       If this is not so, please use the stop_etl.nsh script to stop and reset the ETL.

              Mon Sep 19 16:42:33 2011: Removing exstat files for this run.

              Mon Sep 19 16:42:34 2011: Finished removing exstat files.

              Mon Sep 19 16:42:34 2011: Removing lock file.

               

              I hope you can help me.

               

              Regards.

              • 4. ETL Job Failing on UPDATE_COGNOS
                Bill Robinson

                you should look in the metadata navigator (http://server:9300/oracledimn) and see what the actual error is.

                • 5. ETL Job Failing on UPDATE_COGNOS
                  Oscar Avila

                  Hi Bill, Thank you for respond.

                   

                  In the metadata navigator appears the "Return Code:7000" and the message shows:

                   

                  com.sunopsis.dwg.function.SnpsFunctionBaseException: OS command returned 1.

                     at com.sunopsis.dwg.tools.OSCommand.actionExecute(OSCommand.java)

                     at com.sunopsis.dwg.function.SnpsFunctionBase.execute(SnpsFunctionBase.java)

                     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java)

                     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)

                     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(SnpSessTaskSqlS.java)

                     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)

                     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)

                     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)

                     at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)

                     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)

                     at com.sunopsis.dwg.cmd.e.i(e.java)

                     at com.sunopsis.dwg.cmd.e.y(e.java)

                     at com.sunopsis.dwg.DwgJv.treatCmd(DwgJv.java)

                     at com.sunopsis.dwg.DwgJv.main(DwgJv.java)

                     at oracle.odi.Agent.main(Agent.java)

                   

                  In the Session Steps Table appears:

                   

                  error ETL.jpg

                   

                  Thank you.