OBIA 11.1.1.10.1 - Load Plan 'Domain-only Extract and Load (SDE and SIL)' fails at Generate Failed T — Oracle Analytics

Oracle Business Intelligence Applications

Home› Oracle Analytics› Oracle Analytics Forums› More Solutions› Oracle Business Intelligence Applications

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIA 11.1.1.10.1 - Load Plan 'Domain-only Extract and Load (SDE and SIL)' fails at Generate Failed T

Received Response
41
Views
6
Comments
user1631962
user1631962 Rank 1 - Community Starter
in Oracle Business Intelligence Applications

Hello,

I have installed and configured OBI Apps 11.1.1.10.1 as per the documentation.

Source System is Siebel CRM 8.2.2

When I am trying to run the Domain-only Extract and Load' , its failing with the following error message.

ODI-1217: Session GENERATE_FAILED_TASKS_REPORT (230500) fails with return code 7000.
ODI-1226: Step Generate Failed Tasks Report fails after 1 attempt(s).
ODI-1232: Procedure Generate Failed Tasks Report execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
  File "<string>", line 11, in <module>
  File "<string>", line 11, in <module>
  File "__pyclasspath__/codecs.py", line 817, in open
IOError: [Errno 13] EACCES: 'C:\\oracle\\Middleware\\instances\\instance1\x08iapps/logs/etl/BIA_DW_ETL_LPI_Summary_1500_1_230500.html'

at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2473)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2925)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2637)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1898)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:583)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:514)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1074)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:133)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:84)
at java.lang.Thread.run(Thread.java:745)

I am not understanding from where its picking the path (mentioned in red). Can anybody help me with this regards ?

Let me know if any more information is required.

Thanks,

Answers

  • 841717
    841717 Rank 2 - Community Beginner

    It is picking the path from Physical schema mapped to the logical schema DW_BIAPPS11G_LOG_FILES.

    Physical schema will most likely have value like this - C:\\oracle\\Middleware\\instances\\instance1\biapps/log

    Change this log location path in ODI topology to use forward slash /biapps instead of back slash \biapps. Issue seems to be because \b is a special character and only applicable to windows platform.


    This should solve the issue: C:\\oracle\\Middleware\\instances\\instance1/biapps/log


  • user1631962
    user1631962 Rank 1 - Community Starter

    Hello,

    Thanks for your response.

    My installation platform is Windows 2008 Server.

    The path mentioned in the logical Schema DW_BIAPPS11G_LOG_FILES is " BIAPPS_DW_LOG_FILE.C:\oracle\Middleware\instances\instance1\biapps\logs "


    I tried changing the path in the topology to C:\\oracle\\Middleware\\instances\\instance1/biapps/log. Still same issue.


    I also tried to change the path to another place not having biapps at al. Still the same issue.


    Do I need to again generate the load plan ?


    Regards,

  • 1045001
    1045001 Rank 2 - Community Beginner

    Hi,

    Issue is C:\\oracle\\Middleware\\instances\\instance1\x08iapps/logs/etl/...................'

    It should be C:\\oracle\\Middleware\\instances\\instance1\biapps/logs/etl/......................'

    So, Change \ to /.

    For example : change it [C:\oracle\Middleware\instances\instance1\biapps/log] like [C:/oracle/Middleware/instances/instance1/biapps/log].

    MOS confirm it's a bug. Thanks~

    Best regards,

  • 841717
    841717 Rank 2 - Community Beginner

    You don't need to generate LP again. However, it will not work if you restart the same failed session again either. During next LP when new session for this task gets created, it should work fine.

  • user1631962
    user1631962 Rank 1 - Community Starter

    Thanks a lot !

    The load plan execution worked now after I changed the path separator from \ to /

    However one question to confirm my understanding - Since its a bug, do I change the other paths as well ? ie BIAPPS_DW_FILE and BIAPPS_DW_SHARED_FILE.

    Regards,

  • user1631962
    user1631962 Rank 1 - Community Starter

    Thanks for the clarification ! I created a new Load Plan and then executed it. It worked fine with the new variables values.

    Regards,