Scribd Logo
Upload

Welcome to Scribd!

  • ODI Load Plan Failed for Financial Analytics

    Uploaded by

    Asad Hussain
    18 views2 pages
    The load plan for the Financial analytics failed with an error indicating an IO error when reading from the database. The cause was that the number of processes configured for the database was too low. Increasing the number of processes parameter in the database initialization file resolved the issue and allowed the load plan to complete successfully.

    Original Description:

    Doc

    Original Title

    Document 1624800.1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The load plan for the Financial analytics failed with an error indicating an IO error when reading from the database. The cause was that the number of processes configured for the database was too low. Increasing the number of processes parameter in the database initialization file resolved the issue and allowed the load plan to complete successfully.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    18 views2 pages

    ODI Load Plan Failed for Financial Analytics

    Uploaded by

    Asad Hussain
    The load plan for the Financial analytics failed with an error indicating an IO error when reading from the database. The cause was that the number of processes configured for the database was too low. Increasing the number of processes parameter in the database initialization file resolved the issue and allowed the load plan to complete successfully.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    6/18/2015

    Document1624800.1

    OBIA11g:ODILoadPLanFailedForFinancialAnalytics.(BIAPPS11.1.1.7.1)withErrorODI
    1228:Task...failsCausedBy:java.sql.SQLException:IOError:Gotminusonefromaread
    call(DocID1624800.1)
    InthisDocument
    Symptoms
    Cause
    Solution

    APPLIESTO:
    BusinessIntelligenceSuiteEnterpriseEditionVersion11.1.1.7.1andlater
    Informationinthisdocumentappliestoanyplatform.

    SYMPTOMS
    RuntheLoadPlanforFinancialanalyticsaftercompletingalltheconfigurations.
    Theloadplanfailswith
    ODI1228:TaskSIL_DayDimension.W_DAY_D(Integration)failsonthetargetORACLE
    connectionBIAPPS_DW.
    CausedBy:java.sql.SQLException:IOError:Gotminusonefromareadcall
    Errormayshow:
    ODI1519
    ODI1519:Serialstep"StartLoadPlan(InternalID:6271500)"failedbecausechild
    step"GlobalVariableRefresh(InternalID:6272500)"isinerror.
    ODI1519:Serialstep"GlobalVariableRefresh(InternalID:6272500)"failed
    becausechildstep"SourceExtractPhase(InternalID:6275500)"isinerror.
    ODI1519:Serialstep"SourceExtractPhase(InternalID:6275500)"failedbecause
    childstep"1General(InternalID:6276500)"isinerror.
    ODI1519:Serialstep"1General(InternalID:6276500)"failedbecausechildstep
    "2GeneralPRESDE(InternalID:6277500)"isinerror.
    ODI1519:Serialstep"2GeneralPRESDE(InternalID:6277500)"failedbecause
    childstep"3PRESDEDay(InternalID:6285500)"isinerror.
    ODI1519:Serialstep"3PRESDEDay(InternalID:6285500)"failedbecausechild
    step"SerialwithDual_GandDAY_D(InternalID:6288500)"isinerror.
    ODI1519:Serialstep"SerialwithDual_GandDAY_D(InternalID:6288500)"failed
    becausechildstep"SIL_DAYDIMENSION(InternalID:6292500)"isinerror.
    ODI1217:SessionSILOS_SIL_DAYDIMENSION(326500)failswithreturncode8000.
    ODI1226:StepSIL_DayDimension.W_DAY_Dfailsafter1attempt(s).
    ODI1240:FlowSIL_DayDimension.W_DAY_DfailswhileperformingaIntegration
    operation.ThisflowloadstargettableDayDimension.
    ODI1228:TaskSIL_DayDimension.W_DAY_D(Integration)failsonthetargetORACLE
    connectionBIAPPS_DW.
    CausedBy:java.sql.SQLException:IOError:Gotminusonefromareadcall
    at
    oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutD
    at
    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1a75k0lmoi_65&id=1624800.1

    1/2

    6/18/2015

    Document1624800.1

    oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDat
    at
    oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.ge
    at
    org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.ja
    at
    com.sunopsis.sql.SnpsConnection.createConnection(SnpsConnection.java:390)
    at
    com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java:348)
    at
    com.sunopsis.dwg.dbobj.SnpSessTaskSql.getExecutor(SnpSessTaskSql.java:2962)
    ...

    CAUSE
    Databaseparameterforthenumberofprocessesistoolow.
    Canbeseenbyerrorsindatabasealertlog.

    SOLUTION
    Increasethenumberofprocessesforthedatabaseininit.oradatabaseparameterfileandreruntheloadplan.
    Inthiscase,processwereincreasedfrom150to400.
    Didn'tfindwhatyouarelookingfor?

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1a75k0lmoi_65&id=1624800.1

    2/2

    You might also like