Was this page helpful?



    nmc_DataTransferDay_ORA Step ID 3

    Review details problem

    " Date 03/07/2012 07:30:01
    Log Job History (nmc_DataTransferDay_ORA) Step ID 3 Server NEP-NMC-211\NEWTEST
    Job Name nmc_DataTransferDay_ORA Step Name Run Oracle Data Transfer Day SSIS Package
    Duration 00:00:26 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0 Message
    Executed as user: NEP-NMC-211\SYSTEM. ...9.00.5292.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
    Started: 07:30:01 Progress: 2012-07-03 07:30:02.47
    Source: Check the State of DataTransferNight Executing query "SET NOCOUNT ON DECLARE @LOCK INT SET @LOCK = (S".: 100% complete End Progress Progress: 2012-07-03 07:30:02.58
    Source: NEPRight Executing query "--------------------------------------------------".: 100% complete End Progress
    Progress: 2012-07-03 07:30:02.67 Source: ADRules Executing query "DELETE dtw_oracle...ADRules FROM dtw_oracle...ADRu".: 100% complete End Progress
    Progress: 2012-07-03 07:30:02.83 Source: Company Executing query "DELETE dtw_oracle...Company FROM dtw_oracle...Comp".: 100% complete End Progress
    Progress: 2012-07-03 07:30:02.95 Source: Users Executing query "
    DELETE dtw_oracle...UserNewtest FROM dtw_oracl".: 100% complete End Progress Prog... Process Exit Code 1. The step failed.

    Failures of job DataTransferDay_Oracle noticed are due to a lack of space in the tablespace ' UNDOTBS2 ' .

    reference to undefined name 'syntax' Une exception de type 'MindTouch.Deki.Script.Runtime.DekiScriptUndefinedNameException' a été levée. (click for details)

    OLE DB provider "OraOLEDB.Oracle" for linked server "dtw_oracle" returned message
    "ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'".


    An application must temporarily overeat in this common space ( tablespace 28Go ) which causes the failure of the job that can not insert its data ( Result , Message, Statusrange ) in temporary tables.
    However, this is nothing to worry about because datas are reinserted as soon as job run again. So there was no loss of data.

    To solve this sporadic incident, we invite you to have your DBA analysis peak space consumption of this tablespace.
    Thus, the maximum size can be set by your DBA (auto -extend ) to resolve this incident.


    See also

    Was this page helpful?
    Tag page (Edit tags)
    • No tags
    Page statistics
    4648 view(s), 6 edit(s) and 5932 character(s)


    You must login to post a comment.

    Attach file