PureEngage On-Premises

 View Only

Sign Up

  • 1.  Infomart reporting issue

    Posted 10-08-2018 13:22
    Hello Guys, 

    I am facing a problem while installing and configuring  Infomart reporting.

    In GIM_ETL logs, job "update_idm_for_gim" is failing as while trying to query icon db , schema is being taken as "auto" which actually is the username.

    2018-10-05 11:04:36,977 WARN  ecp-0        20049 Job step 'UPDATE_IDB_FOR_GIM' failed. com.genesyslab.gim.etl.exceptions.UncategorizedSQLException: queryAndScan; Uncategorized SQLException for SQL [SELECT G_DB_PARAMETERS.VAL FROM (select 1 as dummy) DUAL LEFT OUTER JOIN auto.G_DB_PARAMETERS ON G_DB_PARAMETERS.SECT = 'schema' AND G_DB_PARAMETERS.OPT = 'version']; SQLSTATE=S0002; error code=208; DBError=UNCATEGORIZED; Invalid object name 'auto.G_DB_PARAMETERS'..2018-10-05 11:04:36,977 WARN  ecp-0        20049 Job step 'UPDATE_IDB_FOR_GIM' failed. com.genesyslab.gim.etl.exceptions.UncategorizedSQLException: queryAndScan; Uncategorized SQLException for SQL [SELECT G_DB_PARAMETERS.VAL FROM (select 1 as dummy) DUAL LEFT OUTER JOIN auto.G_DB_PARAMETERS ON G_DB_PARAMETERS.SECT = 'schema' AND G_DB_PARAMETERS.OPT = 'version']; SQLSTATE=S0002; error code=208; DBError=UNCATEGORIZED; Invalid object name 'auto.G_DB_PARAMETERS'..com.genesyslab.gim.etl.exceptions.TaskExecutionException: com.genesyslab.gim.etl.exceptions.UncategorizedSQLException: queryAndScan; Uncategorized SQLException for SQL [SELECT G_DB_PARAMETERS.VAL FROM (select 1 as dummy) DUAL LEFT OUTER JOIN auto.G_DB_PARAMETERS ON G_DB_PARAMETERS.SECT = 'schema' AND G_DB_PARAMETERS.OPT = 'version']; SQLSTATE=S0002; error code=208; DBError=UNCATEGORIZED; Invalid object name 'auto.G_DB_PARAMETERS'. at com.genesyslab.gim.etl.exceptions.ExceptionHandlers.wrap(ExceptionHandlers.java:28) at com.genesyslab.gim.etl.exceptions.ExceptionHandlers.wrap(ExceptionHandlers.java:16) at com.genesyslab.gim.etl.util.BunchExecutorService$Invoker.invoke(BunchExecutorService.java:128) at com.genesyslab.gim.etl.util.BunchExecutorService.invokeAll(BunchExecutorService.java:160) at com.genesyslab.gim.etl.server.GenericJobStepContext.invokeAll(GenericJobStepContext.java:75) at com.genesyslab.gim.etl.jobs.migrate.UpdateIdbForGim.runStep(UpdateIdbForGim.java:38) at com.genesyslab.gim.etl.server.GenericJobTask.execute(GenericJobTask.java:67) at com.genesyslab.gim.etl.server.CallableTransactionStep.runTransaction(CallableTransactionStep.java:56) at com.genesyslab.gim.etl.server.CallableTransactionStep.runContext(CallableTransactionStep.java:72) at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:86) at com.genesyslab.gim.etl.server.CallableTransactionStep.call(CallableTransactionStep.java:20) at com.genesyslab.gim.etl.util.StopWatchCallable.call(StopWatchCallable.java:32) at com.genesyslab.gim.etl.server.JobStepRunner.callTask(JobStepRunner.java:288) at com.genesyslab.gim.etl.server.JobStepRunner.runTask(JobStepRunner.java:279) at com.genesyslab.gim.etl.server.JobStepRunner.runTasks(JobStepRunner.java:236) at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:190) at com.genesyslab.gim.etl.server.JobStepRunner.initAndRun(JobStepRunner.java:141) at com.genesyslab.gim.etl.server.JobStepRunner.run(JobStepRunner.java:120) at com.genesyslab.gim.etl.constants.JobInfo$11.call(JobInfo.java:244) at com.genesyslab.gim.etl.constants.JobInfo$11.call(JobInfo.java:237) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:435) at com.genesyslab.gim.etl.server.JobController$4.call(JobController.java:1171) at com.genesyslab.gim.etl.server.JobController$4.call(JobController.java:1168) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: com.genesyslab.gim.etl.exceptions.UncategorizedSQLException: queryAndScan; Uncategorized SQLException for SQL [SELECT G_DB_PARAMETERS.VAL FROM (select 1 as dummy) DUAL LEFT OUTER JOIN auto.G_DB_PARAMETERS ON G_DB_PARAMETERS.SECT = 'schema' AND G_DB_PARAMETERS.OPT = 'version']; SQLSTATE=S0002; error code=208; DBError=UNCATEGORIZED;

    Here auto is the username and not schema name

    Any suggestions please?




    ------------------------------
    [Ankush] [Khare]
    ------------------------------


  • 2.  RE: Infomart reporting issue

    Posted 10-09-2018 09:28
    Hello.

    Could you please share the following:

    Complete set of GIM_ETL Logs
    GIM_ETL Options
    GIM_ETL Connections
    GIM DAP Configuration options
    ICON Configuration Options (All ICONs)
    ICON DAP Configuration options (print of the tab where ou specify the db details and the annex tab options as well)

    Could you please also tell us the sequence of scripts that you ran in the database, preferably the script name and the database name.

    Cheers.

    ------------------------------
    Amauri de Oliveira
    Alctel Telecom
    http://amaurioliveira.com
    ------------------------------



  • 3.  RE: Infomart reporting issue

    Posted 10-09-2018 09:38
    By reading quickly the piece of logs that you shared, seems its complaining about the IDB. Could you please confirm:

    1. That you ran the script to update your IDB for GIM
    2. That your GIM_ETL database user has permissions on the ICON(s) Schemas ?


    Let us know if it works for you.

    Cheers.

    ------------------------------
    Amauri de Oliveira
    Alctel Telecom
    http://amaurioliveira.com
    ------------------------------



  • 4.  RE: Infomart reporting issue

    Posted 10-10-2018 04:12
    ​HI All,

    Thank you for the replies. But it worked after recreating a DAP :)

    ------------------------------
    [Ankush] [Khare]
    ------------------------------



Related Content