ORA-12899: value too large for column 'FLOWS_FILES '. ' WWV_FLOW_FILE_OBJECTS$

Try to download a .docx, get the following:

ORA-12899: value too large for column 'FLOWS_FILES '. «WWV_FLOW_FILE_OBJECTS$ '.» "" Mime_type "(real: 71, maximum: 48)

Course description WWV_FLOW_FILE_OBJECTS$, MIME_TYPE is declared as varchar2 (48).

The problem is that the Content-Type for a .docx file is "application/vnd.openxmlformats-officedocument.wordprocessingml.document.

What is the best way to solve this problem?

Easy solution?

Change the Table of $ WWV_FLOW_FILE_OBJECT and widen the column.

Or change your dads.conf file (if you are using mod_plsql) and specify a different table to PlsqlDocumentTablename.

brgds,
Peter

-----
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
Work: http://www.click-click.at
Training: http://www.click-click.at/apex-4-0-workshops

Tags: Database

Similar Questions

  • ORA-02374: error loading conversion table / ORA-12899: value too large for column

    Hi all.

    Yesterday I got a dump of a database that I don't have access and Production is not under my administration. This release was delivered to me because it was necessary to update a database of development with some new records of the Production tables.

    The Production database has NLS_CHARACTERSET = WE8ISO8859P1 and development database a NLS_CHARACTERSET = AL32UTF8 and it must be in that CHARACTER set because of the Application requirements.

    During the import of this discharge, two tables you have a problem with ORA-02374 and ORA-12899. The results were that six records failed because of this conversion problem. I list the errors below in this thread.

    Read the note ID 1922020.1 (import and insert with ORA-12899 questions: value too large for column) I could see that Oracle gives an alternative and a workaround that is to create a file .sql with content metadata and then modifying the columns that you have the problem with the TANK, instead of BYTE value. So, as a result of the document, I done the workaround and generated a discharge .sql file. Read the contents of the file after completing the import that I saw that the columns were already in the CHAR value.

    Does anyone have an alternative workaround for these cases? Because I can't change the CHARACTER set of the database the database of development and Production, and is not a good idea to keep these missing documents.

    Errors received import the dump: (the two columns listed below are VARCHAR2 (4000))

    ORA-02374: error loading «PPM» conversion table "" KNTA_SAVED_SEARCH_FILTERS ".

    ORA-12899: value too large for column FILTER_HIDDEN_VALUE (real: 3929, maximum: 4000)

    "ORA-02372: row data: FILTER_HIDDEN_VALUE: 5.93.44667. (NET. (UNO) - NET BI. UNO - Ambiente tests '

    . . imported "PPM". "' KNTA_SAVED_SEARCH_FILTERS ' 5,492 MB 42221 42225-offline

    ORA-02374: error loading «PPM» conversion table "" KDSH_DATA_SOURCES_NLS ".

    ORA-12899: value too large for column BASE_FROM_CLAUSE (real: 3988, maximum: 4000)

    ORA-02372: row data: BASE_FROM_CLAUSE: 0 X '46524F4D20706D5F70726F6A6563747320700A494E4E455220 '.

    . . imported "PPM". "' KDSH_DATA_SOURCES_NLS ' lines 229 of the 230 308.4 KB

    Thank you very much

    Bruno Palma

    Even with the semantics of TANK, the bytes for a column VARCHAR2 max length is 4000 (pre 12 c)

    OLA Yehia makes reference to the support doc that explains your options - but essentially, in this case with a VARCHAR2 (4000), you need either to lose data or change your data type of VARCHAR2 (4000) to CLOB.

    Suggest you read the note.

  • ORA-12899: value too large for column (size: 30, maximum: 25)

    I try to insert values from one table to another using substr (column_x, 1, 25) (field target is of type varchar (25)) and I get an error: ORA-12899: value too large for column (size: 30, maximum: 25) how is this possible?

    SUBSTRB uses the same syntax:

    http://docs.Oracle.com/CD/E11882_01/server.112/e41084/functions181.htm#i87066

    If chopping byte characters does not mean that you could end up with a partial character at the end for example if each character 2 bytes, then the last character would not that it is the first byte, so wouldn't an entire character.

    Depends on what you actually try to reach by taking the partial strings.

    Keep in mind, with the UTF8, you could have up to 4 bytes of length characters each.

  • Addition of virtual column: ORA-12899: value too large for column

    I am using Oracle 11g, OS Win7, SQL Developer

    I'm trying to add the virtual column to my test table, but get ORA-12899: value too large for column error. Here are the details.
    Can someone help me in this?
    CREATE TABLE test_reg_exp
    (col1 VARCHAR2(100));
    
    INSERT INTO test_reg_exp (col1) VALUES ('ABCD_EFGH');
    INSERT INTO test_reg_exp (col1) VALUES ('ABCDE_ABC');
    INSERT INTO test_reg_exp (col1) VALUES ('WXYZ_ABCD');
    INSERT INTO test_reg_exp (col1) VALUES ('ABCDE_PQRS');
    INSERT INTO test_reg_exp (col1) VALUES ('ABCD_WXYZ');
    ALTER TABLE test_reg_exp
    ADD (col2 VARCHAR2(100) GENERATED ALWAYS AS (REGEXP_REPLACE (col1, '^ABCD[A-Z]*_')));
    
    SQL Error: ORA-12899: value too large for column "COL2" (actual: 100, maximum: 400)
    12899. 00000 -  "value too large for column %s (actual: %s, maximum: %s)"
    *Cause:    An attempt was made to insert or update a column with a value
               which is too wide for the width of the destination column.
               The name of the column is given, along with the actual width
               of the value, and the maximum allowed width of the column.
               Note that widths are reported in characters if character length
               semantics are in effect for the column, otherwise widths are
               reported in bytes.
    *Action:   Examine the SQL statement for correctness.  Check source
               and destination column data types.
               Either make the destination column wider, or use a subset
               of the source column (i.e. use substring).
    When I try to, I get the correct results:
    SELECT col1, (REGEXP_REPLACE (col1, '^ABCD[A-Z]*_'))
    FROM test_reg_exp;
    Thank you.

    Yes, RP, it works if you give col2 size > = 400.

    @Northwest - could you please test the same w/o having a clause of regex in col2?
    I have a doubt about using a REGULAR expression in this case Dynamics col.

    Refer to this (might help) - http://www.oracle-base.com/articles/11g/virtual-columns-11gr1.php
    Below excerpt from above link... see if that helps...
    >
    Notes and restrictions on the virtual columns include:

    The indexes defined on the virtual columns are equivalent to a function-based index.
    Virtual columns can be referenced in the updates and deletions WHERE clause, but they cannot be manipulated by DML.
    The tables containing virtual columns may still be eligible for result caching.
    Functions in expressions must be deterministic when the table is created, but can then be recompiled and non-deterministic without for as much invalidate the virtual column. In such cases, the following steps must be taken after the function is recompiled:
    Constraint on the virtual column must be disabled and re-enabled.
    On the virtual column indexes must be rebuilt.
    Materialized views that access the virtual column must be fully refreshed.
    The result cache must be flushed if the virtual column acceded to the request (s).
    Statistical table must be regathered.
    The virtual columns are not supported for the organized and external object in index, cluster or temporary tables.
    The expression used in the virtual column definition has the following restrictions:
    It cannot refer to another virtual column by name.
    It can refer to the columns defined in the same table.
    If it refers to a deterministic user-defined function, it cannot be used as a partitioning key column.
    The result of the expression must be a scalar value. It cannot return that an Oracle supplied the data type, a type defined by the user, LOB or LONG RAW.
    >

    Published by: Vanessa B on October 16, 2012 23:48

    Published by: Vanessa B on October 16, 2012 23:54

  • ORA-12899: value too large for column

    Hi Experts,

    I get data of erp in the form of feed systems, in particular a column length in animal feed is only 3.

    In the column of the target table was also length is VARCHAR2 (3)

    but when I try to load even in db it showing errors such as:

    ORA-12899: value too large for column
    emp_name (population: 4, maximum: 3)

    I use the version of database:
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production

    but it is solved when the time to increase the length of the column target for varchar2 (5) of VARCHAR2 (3)... but I checked the length of this column in the feed is only 3...


    My question is why we need to increase the length of target column?


    Thank you
    Surya

    Oracle Database 11 g Express Edition uses the UTF-8 character set.

  • ORA-01401: inserted value too large for column

    I have a table.the structure is as below.

    SQL > desc IDSSTG. FAC_CERT;

    Name                                      Null?    Type

    ----------------------------------------- -------- ----------------------------

    FAC_CERT_SK NOT NULL NUMBER (38)

    LOB_BYTE_CD_SK NUMBER (38)

    SRC_CRDTL_ID_STRNG VARCHAR2 (20)

    PROV_CRDTL_SK NOT NULL NUMBER (38)

    LAB_SPCL_TYP_CD_SK NUMBER (38)

    FAC_CERT_ID NOT NULL VARCHAR2 (20)

    DATE OF FAC_CERT_EFF_DT

    FAC_CERT_EFF_DT_TXT NOT NULL VARCHAR2 (10)

    DATE OF FAC_CERT_END_DT

    FAC_CERT_END_DT_TXT VARCHAR2 (10)

    UPDT_DT                                            DATE

    UPDT_DT_TXT VARCHAR2 (10)

    SS_CD NOT NULL VARCHAR2 (10)

    ODS_INSRT_DT NOT NULL DATE

    ODS_UPDT_DT NOT NULL DATE

    CREAT_RUN_CYC_EXEC_SK NOT NULL NUMBER (38)

    LST_UPDT_RUN_CYC_EXEC_SK NOT NULL NUMBER (38)

    LAB_SPCL_TYP_CD VARCHAR2 (10)

    LOB_BYTE_CD VARCHAR2 (10)

    BUS_PRDCT_CD VARCHAR2 (20)

    I need set the value of a column to a default value.

    SQL > alter table IDSSTG. FAC_CERT change (FAC_CERT_EFF_DT_TXT default, TO_DATE('01010001','MMDDYYYY'));

    ALTER table IDSSTG. FAC_CERT change (FAC_CERT_EFF_DT_TXT default, TO_DATE('01010001','MMDDYYYY'))

    *

    ERROR on line 1:

    ORA-01401: inserted value too large for column

    Please notify.

    Kind regards

    VN

    ALTER table IDSSTG. FAC_CERT change (default FAC_CERT_EFF_DT_TXT ' 01010001');

  • Value too large for column

    Hello

    I have a column with the varchar2 data type (500) next to oltp, I extract the data from this column and loading in another column of tables which has the same varchar2 data type (500)

    My problem: I get error with a value too large for column when I am trying to load data in certain folders. (I guess there is a problem of character format, if that's the case how to check characters for the data format)

    Help, please

    Do not forget that the 500 in varchar2 (500) specifies the size of the storage. This means that you have 500 bytes of storage.

    Which may depend on your default however nls_length_semantics: your statement is true semantics bytes but neither tank:

    SQL> select name, value  from sys.v_$parameter  where lower (name) like '%length%'
      2  /
    
    NAME                 VALUE
    -------------------- --------------------
    nls_length_semantics BYTE
    
    SQL>
    SQL> create table t (a varchar2 (500))
      2  /
    
    Table created.
    
    SQL>
    SQL> alter session set nls_length_semantics=char
      2  /
    
    Session altered.
    
    SQL>
    SQL> alter table t add b varchar2(500)
      2  /
    
    Table altered.
    
    SQL> desc t
     Name                                      Null?    Type
     ----------------------------------------- -------- ----------------------------
     A                                                  VARCHAR2(500 BYTE)
     B                                                  VARCHAR2(500)
    
    SQL>
    
  • Data truncation error ORA-12899 ODI File_To_RT: value too large for colum

    Hello
    Give me an idea so I can truncate the grater data source to length max before you insert into the target table.

    Prtoblem details: -.

    For my script read the data of the insert and the source .txt file the data in the length of the target table.suppose source file data exceeds the length of col max of the target table. So how I truncates the data so that the data migration will be successful and also can avoid the mistake of ODI "" ORA-12899: value too large for column '. "

    Thank you
    Sébastien

    I was referring to the source database. Because C$ table is created based pon the source data store. Increase the physical and logical length on a same value.
    If you see the code generated for C$ table create table step you can see the size of the column. This table is not able to store the incoming string value.

    Substr function will be used when the data will be loaded either I$ table or table target.

  • too big for column

    With the help of 11g...

    I am trying to insert data into a column in a table that contains postal codes with a varchar2 setting (5).

    When I try to run an insert, it keeps telling me:

    ORA-12899: value too large for column 'FY13_NRN_ADMIN '. "" POSTAL CODE "(real: 39, maximum: 9)

    So I ran a few tests...

    Select

    Max (length (zipcode)) zip_size

    of fy13_individual_data;

    ZIP_SIZE

    5

    Select distinct lengthb (zipcode) "length in bytes.

    of Fy13_individual_data;

    Length in bytes

    1

    5

    4

    So I tried to run the insert using a command of the substring.

    INSERT INTO FY13_NRN_ADMIN (ADMIN_CN,

    PURPOSE_SITE_WORKING,

    PURPOSE_SITE_RECREATE,

    PURPOSE_SITE_PASSTHRU,

    PURPOSE_SITE_OTHREASN,

    PURPOSE_SITE_BATHROOM,

    TIME_LEAVING_SITE,

    FROM_SAMERICA,

    FROM_OTH_COUNTRY,

    FROM_MEXICO,

    FROM_EUROPE,

    FROM_CANADA,

    FROM_ASIA,

    SERIALNUMBER,

    SCAN_HEADER,

    -DONT_KNOW_ZIP,

    Zip code

    WHY_ROUTE,

    REC_GFA,

    REGION_CODE,

    PURPOSE_GFA,

    PURPOSE_SITE,

    AGREE_TO_INTERVIEW,

    WHEN_LEAVE_GFA,

    WHEN_LEAVE_SITE,

    CLICK_START,

    AXLE_COUNT,

    DATAYEAR,

    FORM,

    ROUND,

    TYPESITE,

    AFOREST_CODE,

    INTERVIEW_DATE,

    -SITE_CN_FK,

    SUBUNIT,

    SITENUMBER,

    PURPOSE_GFA_WORKING,

    PURPOSE_GFA_RECREATE,

    PURPOSE_GFA_PASSTHRU,

    PURPOSE_GFA_OTHREASN,

    PURPOSE_GFA_BATHROOM,

    VPDUNIT_ID)

    SELECT ADMIN_CN,

    REGION_CODE,

    SUBSTR (PURPOSE_SITE_WORKING, 1, 1),

    SUBSTR (PURPOSE_SITE_RECREATE, 1, 1),

    SUBSTR (PURPOSE_SITE_PASSTHRU, 1, 1),

    SUBSTR (PURPOSE_SITE_OTHREASN, 1, 1),

    SUBSTR (PURPOSE_SITE_BATHROOM, 1, 1),

    TO_NUMBER (TO_CHAR (time_leaving_site, 'HH24MI')),

    SUBSTR (FROM_SAMERICA, 1, 1),

    SUBSTR (FROM_OTH_COUNTRY, 1, 1),

    SUBSTR (FROM_MEXICO, 1, 1),

    SUBSTR (FROM_EUROPE, 1, 1),

    SUBSTR (FROM_CANADA, 1, 1),

    SUBSTR (FROM_ASIA, 1, 1),

    SERIALNUMBER,

    SCAN_HEADER,

    -SUBSTR (DONT_KNOW_ZIP, 1, 1),

    SUBSTR (POSTAL CODE, 1, 5),

    WHY_ROUTE,

    SUBSTR (REC_GFA, 1, 1),

    PURPOSE_GFA,

    PURPOSE_SITE,

    SUBSTR (AGREE_TO_INTERVIEW, 1, 1),

    WHEN_LEAVE_GFA,

    WHEN_LEAVE_SITE,

    CLICK_START,

    AXLE_COUNT,

    DATAYEAR,

    FORM,

    ROUND,

    TYPESITE,

    AFOREST_CODE,

    INTERVIEW_DATE,

    -SITE_CN_FK,

    SUBUNIT,

    SITENUMBER,

    SUBSTR (PURPOSE_GFA_WORKING, 1, 1),

    SUBSTR (PURPOSE_GFA_RECREATE, 1, 1),

    SUBSTR (PURPOSE_GFA_PASSTHRU, 1, 1),

    SUBSTR (PURPOSE_GFA_OTHREASN, 1, 1),

    SUBSTR (PURPOSE_GFA_BATHROOM, 1, 1),

    VPDUNIT_ID

    OF fy13_individual_data;

    But it STILL says the same error of size max.

    I don't understand why would it be otherwise when even... the substr command must ignore the characters of tail.  Isn't it?

    Thoughts on the alternatives?  All the lines seem to be the right size for me.

    Hello

    It seems that the postal code is the 16th column in the list INSERT, but scan_header is the 16th column in the SELECT clause.  ('SUBSTR (POSTAL code, 1, 5)' is the 17th column in the SELECT clause).

    Perhaps you forgot REGION_CODE in the list INSERT, or didn't want to include it in the SELECT clause.  It is, he is very suspicious to say:

    INSERT INTO FY13_NRN_ADMIN (ADMIN_CN, - column 1

    PURPOSE_SITE_WORKING, - column 2

    PURPOSE_SITE_RECREATE, - column 3

    ...

    SELECT ADMIN_CN, - column 1

    REGION_CODE, - column 2

    SUBSTR (PURPOSE_SITE_WORKING, 1, 1),-column 3

    ...

    as you do.

  • 'Value too large' error discoverer

    Hi all

    I was stuck with a problem with the Oracle Discoverer Plus 10 g (10.1.2.55.26) since the last 2 days, tried all possible options mentioned on the Forums and elsewhere, but somehow, nothing seems to help. So I fire experts for help. Here is a description:

    We have a report on the discoverer who gives us the "ORA-12899 value too large for column', whenever we try to plan sound via the Scheduler. The report runs well if we run manually. To address the problem, I did the following:

    1 identify areas of activity associated with this report and map the column in question to its base table.

    2 could see that the column is a column varchar2, and so I changed length from 50 to 200.

    3. once the column has changed, I deleted all complex records of his business and he added again by copying in the simple folder (which maps directly to the column in the table).

    4 then I refreshed all the BA to make the new length of the column would be picked up all over the place, and the update went successfully.

    5. I deleted all regular existing workbooks with errors and tried to program again.

    Even in this case, the workbook raises always the same ' ORA-12899 value too large for column (real: 57, maximum: 50)'. Don't know what step is missing when updating of the EULS that causes this error.

    Please advise!

    Thank you.

    Hello

    I just wanted to report that we were able to locate and fix the problem last night. There is another complex issue that also had the same element, and we missed the first time to change that. The fact that change, the deletion and the rescheduling of the report, it started working perfectly

    Thank you.

  • ODI Datastore length differs with the length DB - IKM throws value too large

    ODI datastore when reverse engineering a different length than the datalength in actual db.

    The Datastore ODI column details: tank (44)
    Column db target: varchar2 (11 char)

    The I$ table inserts char44 in varchar2 (11char) in the target. As the value of the source column is empty ODI throws
    "ORA-12899: value too large for column (size: 44, maximum: 11)."

    You must always include the ODI version you are using.

    I assume that you are using the standard method or not an RKM of reverse engineering.
    Because of a bug in JDBC driver (ojdbc14.jar is), using reverse engineering standard will multiply the lengths of all varchar2 by 4.
    Upgrade the jdbc driver or use oracle RKM to reverse engineer the data store.

    PS. Please indicate as good/useful answers when you're done.

  • Getting ORA-22835: buffer too small for to CHAR CLOB or BLOB to RAW conversion in my ODI interface

    Hi all

    I am creating an interface ODI as explained below,

    I table A column 'Comments' and one other table with column B "No Comment." I create a view as shown below and use it as a source for my interface.

    SELECT * FROM WC_EQM_CSAP_FS_TMP WHERE to_char (QUESTION_COMMENT) IN (SELECT NO_COMMENTS FROM WC_EQM_NO_COMMENTS_LIST).

    But my interface fails with the error below

    ORA-22835: buffer too small for to CHAR CLOB or BLOB to RAW conversion (real: 4108, maximum: 4000)

    22835 00000 - "too small buffer tank CLOB or BLOB to RAW conversion (actual: %s, maximum: %s)) '

    * Cause: an attempt was made to convert CLOB to CHAR or BLOB to RAW, where

    LOB size was larger than the buffer for CHAR and RAW limit types.

    Note that the widths are reported in characters if characters length isadds are in effect for the column, other widths are

    in bytes.

    Here QUESTION_COMMENT is of type CLOB data. NO_COMMENTS is also CLOB data type. The maximum length of the data of QUESTION_COMMENT is also 11710

    Please tell us how to solve.

    Thank you

    Dany

    IMHO, it is not good to compare CLOB, can be that it is possible to use the primary key for the comments

    Is it QUESTION_COMMENT and NO_COMMENTS a PRIMARY INDEX,

    may be is the best solution to create vacabulary with comments (if it does not exist) and then compare it by id;

    You can simply use the left join and check for null in a CASE statement

    Try this, but I don't know... as I said before I have no Oracle DB

    SELECT INTEGRATION_ID, DATASOURCE_NUM_ID, QUESTIONNAIRE_ID, QUESTION_ID,

    CLIENT_ID, SITE_ID, CLIENT_REP, COMMITMENT, ENGAGEMENT_TYPE, TOP_CLIENT_FLG,

    INITIAL_PLANNED_DT, REVISED_PLANNED_DT, INTERVIEW_DT, RECEIVED_DT, QUESTION_SCORE,

    (

    CASE WHEN EXISTS (SOME T2.NO_COMMENTS OF WC_EQM_NO_COMMENTS_LIST T2 WHERE DBMS_LOB.COMPARE (TMP.) (QUESTION_COMMENT, T2.NO_COMMENTS) = 0)

    THEN NULL

    OF OTHER QUESTION_COMMENT

    END QUESTION_COMMENT),

    (CASE WHEN QUESTION_SCORE<=5 then="" 1="" else="" 0="" end)="">

    0 AS QWOCOMMENTS,

    CREATED_ON_DT, CHANGED_ON_DT OF WC_EQM_CSAP_FS_TMP as TMP

    P.S. does not use TO_CHAR (LOB) there are possible error

  • When I open a tab/icon on my computer is much too large for my screen and I can't use my computer; 3 boxes in the upper right corner.

    When I open a tab/icon on my computer is much too large for my screen and I can't use my computer; 3 boxes at the top right corner with the-, square and X are too far to the right to do anything. How can I fit on my screen, so I can use my computer?

    Hello

    Please contact Microsoft Community.

    This problem is limited to any icon or it happens with all?

    Did you change to the computer?

    I suggest to refer to the following methods and check to see if it helps:

    Method 1:

    Install the latest display driver and check

    Uninstall the driver from Device Manager display.

    a. close all programs. This will ensure that the programs do not interfere with the update of the driver.
    b. right-click on my computer, and then click Properties. This will bring you from the System Properties menu.

    c. click Device Manager
    d. expand the display column of cards by clicking on them. This will show the graphical current map that is using your computer.
    e. right click on the adapter, then select Properties.
    f. click on the driver tab. This tab displays information about the current driver, as well as options to update, delete, uninstall, and back the driver.
    g. click on uninstall
    h. restart the computer

    You can install the latest display driver for download on the site of computer manufacturing, same driver will reinstall automatically after the restart, if the computer is connected to the Internet.

    Method 2:

    I suggest you try the system restore. Restore the system to a restore point when your computer was working fine

    You can also check the Device Manager to see if the video card has a yellow exclamation on it with an error any:

    http://Windows.Microsoft.com/en-us/Windows7/products/features/device-management

    I hope this helps.

    Kind regards
    Anusha

  • When the scaling in the layout, 1st page prints correctly, but the following pages were not properly/too large for the paper, parts of text missing scale

    When you try to print in Firefox and when the scale to the size of the page in the page layout, the first page prints correctly, but the following pages do not scale correctly and are too large for the paper, with the parts of the text are cut off at top and right. It is not fixed by checking or unchecking the scaling / shrink to fit page width "ignore" in the print window, or by changing the scale percent.

    I am running Firefox 15.0.1, on Mac OS 10.5.8.

    The same problem happens in preview print and if I save the copy in a .pdf file

    I tried all the fixes in the how to and others in various forums with no improvement.

    This happens everytime I try to print a document from scaling upwards or downwards in Firefox.

    I note the bug has been fixed and should in Firefox 21 right now, it will mean the use night http://nightly.mozilla.org/

  • When you try to transfer a file of 8 GB on external hard drive 'file too large for the destination system message' to get there is that much space on disk

    When you try to transfer a file of 8 GB on external hard drive 'file too large for the destination system message' to get there is that much space on disk

    Hello

    Discs formatted with the FAT be limited to files with a maximum of 4 GB. You can format outside
    drive drive with NTFS, contact the manufacturer if necessary pilot or split the file into parts under
    at 4 GB.

    Overview of FAT, HPFS, and NTFS file systems
    http://support.Microsoft.com/kb/100108

    How to go beyond the limit of 4 GB on FAT32
    http://lazybit.com/index.php/2007/03/01/how_to_get_over_the_4gb_limit_fat32

    -------------------------------------------------------------------------------------------------------------------------

    The ZIP file and then divided the ZIP which helps maintain the integrity of sharing files and restoring.

    Zip and Split - free
    http://zipandsplit.toolazy.me.UK/

    Split and Zip - free
    http://www.jtoolgame.com/tools/splitzip.html

    Akhir Split Zip - free
    http://www.mydigitallife.info/2009/04/24/Akhir-split-zip-splits-files-into-smaller-zip-files/

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

Maybe you are looking for