What Is Informatica Error Code 36331 And How To Fix It?

Don't suffer from crashes and errors. Fix them with ASR Pro.

  • 1. Download ASR Pro and install it on your computer
  • 2. Launch the program and click "Scan" to start the scanning process
  • 3. Click "Repair" to fix any detected issues
  • Get a faster

    You may encounter an error message with Informatica error code 36331. Coincidentally, there are a number of steps you can take to resolve this issue, so we’ll talk about that in a moment.

    This error has been occurring randomly on various targets. Can I restart and the coverage is good.

    I’m assuming it’s just performance or total database connections? or perhaps a dead end?

    My task on the forum is to find out in what situations this problem can occur.

    ANOMALY INFO ::: Error running: INFORMATIONAL TASK: CUSTOM_SDE:wf_SDE_ProjectDimension:1:(Source FULL: Target: OPTIONAL)
    MESSAGE:::java.lang.Exception: pmcmd startworkflow -sv II_SOP_OBI_PRD -d Domain_SOP_OBI_PRD -u Administrator – p **** CUSTOM_SDE -f -paramfile E:InformaticaPowerCenter9.5.1serverinfa_sharedSrcFilesCUSTOM_SDE.wf_SDE_ProjectDimension.SEBL_78.txt Status wf_SDE_ProjectDimension
    Description: Failed
    WorkFlowMessage:
    Error message : Unknown explanation for error code 36331
    Error code: 36331
    EXCEPTION CLASS:::java.lang.Exception

    com.siebel.analytics . etl.etltask.GenericTaskImpl.doExecuteWithRetries(GenericTaskImpl.java:516)

    com.siebel.analytics.etl.etltask.GenericTaskImpl.run(GenericTaskImpl.java:655)
    com.siebel.analytics.etl.taskmanage r.XCallable.call(XCallable.java:63)
    java.util.concurrent.FutureTask$Sync.innerRun(unknown source)
    java.util.concurrent.FutureTask.run(unknown source)
    java .util.concurrent.Executors$RunnableAdapter.call(Source unknown)
    java.util.concurrent.FutureTask$Sync.innerRun(Source unknown)
    java.util.concurrent.FutureTask.run(Source unknown)
    java.util. concurrent.ThreadPoolExecutor$Worker.runTask (source unknown)
    java.util.concurrent.ThreadPoolExecutor$Worker.run (source unknown)
    java.lang.Thread.run (source unknown)

    : ::REASON:::
    MESSAGE Startworkflow :::pmcmd -sv II_SOP_OBI_PRD -k Domain_SOP_OBI_PRD -u Administrator -p **** -y CUSTOM_SDE -paramfile E:InformaticaPowerCenter9.5.1server infa_sharedSrcFiles CUSTOM_SDE.wf_SDE_ProjectDimension.SEBL_78.txt Status wf_SDE_ProjectDimension
    Description: Failed
    WorkFlowMessage:
    Error Message: Unknown cause of error code 36331
    Error code: 36331
    CLASS EXCEPTION:::java.lang .Exception

    com.siebel.analytics.etl.etltask.InformaticaTask.doExecute(InformaticaTask.java:258)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.doExecuteWithRetries(GenericTaskImpl.java:477)
    com .siebel.analytics.etl.etltask.GenericTaskImpl.execute(GenericTaskImpl.java:372)
    com.siebel.analytics.etl.etltask.GenericTaskImpl.execute(GenericTaskImpl.java:253)
    com.siebel.analytics .etl.etltask.GenericTaskImpl.run(GenericTaskImpl.java:655)
    com.siebel.analytics.etl.taskmanager.XCallable.call(XCallable.java:63)
    java.util.concurrent.FutureTask$Sync .innerRun(Unknown source)
    java.util.concurrent.FutureTask.run(Unknown source)
    java.util.concurrent.Executors$RunnableAdapter.call(Unknown source)
    java.util.concurrent.FutureTask $Sync.innerRun(unknown source)
    java.util.concurrent.FutureTask.run(unknown source)
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(unknown source)
    java.util.concurrent .ThreadPoolExecutor$Worker.run(Unknown source)
    jav a .lang.Thre ad.run (Source unknown)

    (Number of attempts is 1)

    pmcmd startworkflow -sv II_SOP_OBI_PRD -l Domain_SOP_OBI_PRD -u Administrator -p * *** -j CUSTOM_SDE – paramfile E:InformaticaPowerCenter9.5.1serverinfa_sharedSrcFilesCUSTOM_SDE.wf_SDE_ProjectDimension.SEBL_78.txt wf_SDE_ProjectDimension

    2015-05-08 06:47:00.981 INFORMATICA TASK: CUSTOM_SDE_Dimension_SDE( FULLSTÄNDIG Target: INCREMENTAL) completed execution with status Failed.

    Hello! I’m running a DAC execution plan that fails with error code 36331 although no cause is logged. Who could share their thoughts on this? Please see the log below:

    614 SEVERE Tue, Dec. 2009 4:30:57 PM CST 2014 Starting the ETL process.

    informatica error code 36331

    615 SERIOUS Tue Dec 09 16:41:15 CST 2014 Request to start worker processes: ‘SDE_Custom_Adaptor:SDE_PSFT_GrantsDepartmentDimension_Test’ has full error exchange 0

    616 SERIOUS Tue Dec 2009 16:44:10 CST 2014 pmcmd startworkflow -sv IS_hhvappobip02 -d Domain_hhvappobip02.tmh.tmhs -u Administrator -p**** -f -lpf sde_custom_adaptor /apps/obiee/Informatica/9.0. 1/server/infa_shared/SrcFiles/PSFT_9_1_FINSCM_UAT.DataWarehouse_UAT.SDE_Custom_Adaptor.SDE_PSFT_GrantsDepartmentDimension_Test.txt SDE_PSFT_GrantsDepartmentDimension_Test

    Don't suffer from crashes and errors. Fix them with ASR Pro.

    Do you have a computer problem? You’re not alone. In fact, over 60% of computers suffer from some kind of error or crash at one point in time. ASR Pro is the best solution for fixing these problems and getting your PC back up to speed. Click here to get started:

  • 1. Download ASR Pro and install it on your computer
  • 2. Launch the program and click "Scan" to start the scanning process
  • 3. Click "Repair" to fix any detected issues

  • Workflow error message: [WARNING: The session task event [SDE_PSFT_GrantsDepartmentDimension_Test] failed and the task option ‘Parent or guardian failed on failure’ can be described as enabled. So the [SDE_PSFT_GrantsDepartmentDimension_Test] workflow will definitely fail. ]

    ANOMALY INFO::: Operation failed: COMPUTER: task:sde_custom_adaptor:sde_psft_grantsdepartmentdimension_test:(source OPTIONAL Target: OPTIONAL)

    pmcmd startworkflow -sv IS_hhvappobip02 -chemical Domain_hhvappobip02.tmh.tmhs -u Administrator -p**** -v -lpf sde_custom_adaptor /apps/obiee/Informatica/9.0.1/server/infa_shared/SrcFiles/PSFT_9_1_FINSCM_UAT.DataWarehouse_UAT. SDE_Custom_Adaptor.SDE_PSFT_GrantsDepartmentDimension_Test.txt SDE_PSFT_GrantsDepartmentDimension_Test

    Crash workflow error message: [WARNING: Sample session task for this [SDE_PSFT_GrantsDepartmentDimension_Test] failed and its task parameter ‘Parent on failure’ has been extended . So the [SDE_PSFT_GrantsDepartmentDimension_Test] workflow will be incorrect.]

    622 FATAL Tue 16:44:23 2009 CST 2014 ETL appears to be discontinued. Cause the dispatcher to stop on notification of the last read job.

    623 SERIOUS Tue Dec 2009 16:44:23 CST 2014 Stop publishing trigger.

    informatica error code 36331

    624 SERIOUS Tue Dec 09 16:44:23 CST 2014 ETL final process.

    625 SERIOUS Tue Dec 09 16:44:23 CST 2014 Steps message :::some failed.

    626 FATAL Dec 2009 4:44:23 PM CST 2014, dispatcher branch ended.

    627 SERIOUS Tue Dec 09 16:44:23 CST 2014 Number of pending tasks whose status was updated stopped

    Number of incomplete task details whose status has ended :3 < /p>

    1. You need to return the “Process” parameter of the Oracle database from 140 to 500. It is run from location —-E:app7stladminappspfile

    W_ORA_GL_JOURNALS_F_TMPGL_JE_BATCHES_NAME,
    _GL_SEGMENT_DSSEGMENT_VAL_CODE,

    4. Most importantly, recheck most of the connection, ODBC relational connection, Informatica connection, and finally DAC parameter generation.

    Error 36331 occurs everywhere in Informatica primarily because the values ​​between source and target, i.e. OLTP or OLAP, have been extended.

    DIRECTOR> VAR_27028 Use [DataWarehouse] replacement value for training session parameters: [$DBConnection_OLAP].

    DIRECTOR> VAR_27028 Override [ORA_R1213] usage scope for session parameters: [$DBConnection_OLTP].

    DIRECTOR> VAR_27028 Use value replacement [ORA_R1213.DATAWAREHOUSE.SDE_ORAR1213_Adaptor.SDE_ORA_GLJournals_Full.log] for session parameters: [$PMSessionLogFile].

    DIRECTOR> VAR_27028 Use [1000] substitution for map parameters: [$$DATASOURCE_NUM_ID].

    DIRECTOR> VAR_27028 Use bypass value [‘Y’] for mapping parameter: [mplt_BC_ORA_GLXactsJournalsExtract.$$FILTER_BY_LEDGER_ID].

    DIRECTOR> VAR_27028 Use [‘Y’] value replacement for mapping parameter: [mplt_BC_ORA_GLXactsJournalsExtract.$$FILTER_BY_LEDGER_TYPE].

    DIRECTOR> VAR_27028 Use replacement value [2001-01-01] for many parameters:[mplt_BC_ORA_GLXactsJournalsExtract mapping.$$INITIAL_EXTRACT_DATE].

    DIRECTOR> VAR_27028 Use replace call [] for match parameters:[mplt_BC_ORA_GLXactsJournalsExtract.$$LAST_EXTRACT_DATE].

    DIRECTOR> VAR_27028 Use override value [2021] for mapping parameter: [mplt_BC_ORA_GLXactsJournalsExtract.$$LEDGER_ID_LIST].

    DIRECTOR> VAR_27028 Replace [‘PRIMARY’] value for map parameter: [mplt_BC_ORA_GLXactsJournalsExtract.$$LEDGER_TYPE_LIST].TM_6014

    Director>Session Initialization [SDE_ORA_GLJournals_Full] on [Tue Aug 20 13:47:45 2013].

    DIRECTOR> TM_6683 Repository name: [ORACLE_BI_DW_BASE]

    DIRECTOR> TM_6684 Server name: [ORACLE_BI_DW_BASE_INTEGRATION]

    DIRECTOR > TM_6686 Folder: TM_6685 [sde_orar1213_adaptor]

    Director > Workflow: [SDE_ORA_GLJournals_Full] Runtime instance name: [] Runtime ID: [187]

    DIRECTOR> TM_6101 Map name: SDE_ORA_GLJournals [Version 1].

    DIRECTOR> Prior to tm_6963 85 timestamp compatibility enabled

    DIRECTOR> TM_6964 Session date structure: [MM/DD/YYYY HH24:WED:SS]

    DIRECTOR> TM_6827 [C:Informatica9.0.1serverinfa_sharedStorage] is used, as well as storage for directory session [SDE_ORA_GLJournals_Full].

    DIRECTOR> CMN_1805 Clearing the recovery cache as it is working normally.

    DIRECTOR> CMN_1802 Recovery session cache initialization completed.

    DIRECTOR> Use configuration property TM_6708 [SiebelUnicodeDB,[email protected] [email protected]]

    DIRECTOR> TM_6708 Using theConfiguration Options [overrideMpltVarWithMapVar,Yes]

    DIRECTOR> TM_6708 Using configuration property [DisableDB2BulkMode, Yes]

    DIRECTOR> TM_6708 Using the settings property [ServerPort,4006]

    DIRECTOR> Session TM_6703 [SDE_ORA_GLJournals_Full] is definitely running from Integration Service 32-bit [node01_7stl-56], [9.0.1 HotFix2] build [1111].

    MANAGER> Section group petl_24058[1].

    runningMANAGER> PETL_24000 Initializing the parallel pipeline mechanism.

    MANAGER> PETL_24001 Parallel pipeline execution engine.

    MANAGER> PETL_24003 Time initialization.

    MAPPING> CMN_1569 Server Mode: [UNICODE]

    MAPPING> CMN_1570 Server code page: [MS Windows Latin 5 (ANSI), Superset Latin1]

    MAPPING> from TM_6151 Session sort order is [Binary].

    MAPPING > TM_6185 Warning. Code commit page compromised in this session.

    Get a faster

    Carl Mysliwiec