SQL*Loader-510 & SQL*Loader-2026 in the log file but no bad file. I need help underst
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: SQL*Loader-510 & SQL*Loader-2026 in the log file but no bad file. I need help underst

  1. #1
    Join Date
    Feb 2014
    Posts
    2

    SQL*Loader-510 & SQL*Loader-2026 in the log file but no bad file. I need help underst

    I am getting this error message in my log file and I am not sure what it means?

    value used for ROWS parameter changed from 64 to 1
    SQL*Loader-510: Physical record in data file (c:\DSR_LGCY_DATA\DSR.txt) is longer than the maximum(65536)
    SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
    Specify SKIP=972 when continuing the load.


    I received a file where some fields contain information greater than 4000 characters.
    I do not know the true size.

    As I run the file and get errors I change the ddl on the table to a CLOB and rerun.

    I have 1800 records but now I am able to load 972 before I get the error.

    I am not sure if it is a problem or if sql loader can only load 972 records of this size at time.

    Seeing Specify SKIP=972. I thought that this would skip the first 972 records and start from there.


    I added the following to my sql loader statement:
    C:\DSR_LGCY_DATA>sqlldr e406702/e406702@APEXD4 control=c:\DSR_LGCY_DATA\DSR.txt
    log=c:\DSR_LGCY_DATA\DSR.log bad=c:\DSR_LGCY_DATA\DSR.bad SKIP=972

    This produced this error:

    SQL*Loader-510: Physical record in data file (c:\DSR_LGCY_DATA\DSR.txt) is longe
    r than the maximum(65536)
    SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.



    I even tried to increase the physical record size limit by adding
    readsize=1048576


    My control file




    LOAD DATA


    INFILE *


    APPEND


    INTO TABLE DSR


    FIELDS TERMINATED BY "<:s:>"


    (RecordNo CHAR (8),


    DocumentUniversalID CHAR (32),


    CreationDate CHAR (30),


    ETL_STATUS CHAR (250),


    AccessLevel CHAR (4000),


    Author CHAR (4000),


    AuthorizedEditors CHAR (4000),


    ConditionName CHAR (4000),


    ConditionType CHAR (4000),


    CurrentAssignee CHAR (4000),


    CurrentAssigneeAssistant CHAR (4000),


    CurrentAssigneePosition CHAR (4000),


    CurrentStep CHAR (4000),


    CurrentStepStartDate CHAR (4000),


    DDNotify CHAR (4000),


    DDReassign CHAR (4000),


    Dis_AllowAssistantToEdit CHAR (4000),


    Dis_AllowGoBack CHAR (4000),


    Dis_AllowNotification CHAR (4000),


    Dis_AllowQuestion CHAR (4000),


    Dis_AllowReassign CHAR (4000),


    Dis_AllowSave CHAR (4000),


    Dis_CalendarDateField CHAR (4000),


    Dis_CompleteActionPrompt CHAR (4000),


    Dis_GoBackWhenComplete CHAR (4000),


    Dis_ResetStatus CHAR (4000),


    Dis_ShowDueDate CHAR (4000),


    Dis_SystemFields CHAR (4000),


    Dis_UsesReaderNames CHAR (4000),


    DSRAssignToSelf CHAR (4000),


    DSRBureau CHAR (4000),


    DSRContact CHAR (4000),


    DSRContactPhone CHAR (4000),


    DSRDescription CHAR (80000),


    DSRDistrict CHAR (4000),


    DSRDivision CHAR (4000),


    DSREstimate CHAR (4000),


    DSRFrequency CHAR (4000),


    DSRFunctionalArea CHAR (4000),


    DSRJustifyReport CHAR (4000),


    DSRPriorityDesc CHAR (4000),


    DSRPurpose CHAR (4000),


    DSRQuestionsAnswered CHAR (4000),


    DSRRequestDate CHAR (4000),


    DSRRequestNo CHAR (4000),


    DSRTitle CHAR (4000),


    DueDate CHAR (4000),


    ExecutionOrder CHAR (4000),


    FORM CHAR (4000),


    HAssignee CHAR (40000),


    HDate CHAR (4000),


    HNextAssignee CHAR (40000),


    HNextPosition CHAR (4000),


    HNextStep CHAR (4000),


    HPerformer CHAR (40000),


    HPosition CHAR (4000),


    HReason CHAR (4000),


    HStep CHAR (4000),


    NAction CHAR (4000),


    NAddedPerson CHAR (4000),


    NDate CHAR (4000),


    NDeletedPerson CHAR (4000),


    NPerformer CHAR (4000),


    PastAuthors CHAR (4000),


    PastEditDates CHAR (4000),


    PeopleInvolved CHAR (4000),


    PositionOfPeople CHAR (4000),


    RequestDate CHAR (4000),


    RequesterName CHAR (4000),


    RequestId CHAR (4000),


    RequestStatus CHAR (4000),


    RequestStatusChange CHAR (4000),


    RequestStatusDate CHAR (4000),


    ResponseTypeAction CHAR (4000),


    ResponseTypesAllowed CHAR (4000),


    SDate CHAR (4000),


    SortOrder CHAR (4000),


    SPerformer CHAR (4000),


    SStatus CHAR (4000),


    StepType CHAR (4000),


    TimesModified CHAR (4000),


    WorkflowObject CHAR (4000),


    FILE1 CHAR (4000),


    Revisions CHAR (4000),


    REFPARENT CHAR (4000),


    UpdatedBy CHAR (40000))


    BEGINDATA
    Last edited by hharda9791; 02-06-2014 at 12:52 PM.

  2. #2
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,003
    How many of the records are more than 65536 bytes wide? I bet you could write a perl script to
    read and insert the file into Oracle. Just look for code samples on writing scripts with an Oracle
    database on the net.
    this space intentionally left blank

  3. #3
    Join Date
    Feb 2014
    Posts
    2
    I have about 900 more records to load. I tried skipping record 973,974,975 all the way to 1800 andI got the same error.
    Is it just that tool sql loader cannot handle this. I counted the characters using word and it was 69000.

    How do I load records of this size?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width