Element name too long when using ROWTYPE

I've come across an issue with xml element names longer than 30 characters. Seems it has something to do with ROWTYPE. Creation of this function is successful:
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL.dummy%TYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
However, specifying the variable as ROWTYPE gives ORA-00972 error (unless I shorten the element name...):
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL%ROWTYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy.dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
Has anyone come across this before, or have any ideas for a solution? I could specify all my variables as TYPE but as there are many within the tables it would be easier to use ROWTYPE.
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
Thanks.

it works if you add "AS" after l_dummy.dummy
SQL> CREATE OR REPLACE FUNCTION test_fnc
  2     RETURN XMLTYPE
  3  AS
  4     var_return   XMLTYPE;
  5     l_dummy      DUAL%ROWTYPE;
  6  BEGIN
  7     SELECT   dummy INTO l_dummy FROM DUAL;
  8
  9     SELECT   XMLCONCAT(XMLELEMENT (
10                           "TEST",
11                           XMLFOREST (
12                              l_dummy.dummy AS "THIS_IS_OVER_30_CHARACTERS_LONG"
13                           )
14                        ))
15                 data_set
16       INTO   var_return
17       FROM   DUAL;
18  RETURN var_return;
19  END test_fnc;
20  /
Function created.Ants

Similar Messages

  • Compile error "input line is too long" when using useLegacyAOT

    I'm using FlashBuilder 4.7 and the release of AIR 4 on Windows 7 to package for iOS...As soon as I include 3 or more ANEs I can no longer compile to iOS (and also use the new "useLegacyAOT no" command).  When I try I get an error "The input line is too long.   Compilation failed while executing : compile-abc"
    I found a couple other similar issues.  One post suggested instead of pointing to individual ANEs (in Package Contents) to point to a folder instead--but this doesn't fix the
    Another post for a slightly different problem said it was fixed in the release of AIR 4.
    Any ideas?  I wonder if I move my AIR SDK to a simple path (like "c:\air\adt.jar" instead of "C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\adt.jar") if it'd help. 
    Thanks in advance!

    Awesome!  I got used to the new useLegacyAOT thing very fast.  In the meantime, I have to decide whether to remove all my ANEs and test or sit through an interminable build sequence.
    What's the current plan for a new release?  Is there any way I could get a beta copy just to use during development?
    Thanks!

  • Query taking too long when using bind variable

    Hi All,
    There is a query in our prod DB which runs very slow (approx 2 hours) when it uses Bind Variables (using JDBC thin client), and when i try passing the variable using TOAD/SQL developer it runs fine.
    Explain Plan for running Query
    SELECT STATEMENT ALL_ROWSCost: 146 Bytes: 379 Cardinality: 1                                                   
         21 SORT ORDER BY Cost: 146 Bytes: 379 Cardinality: 1                                              
              20 NESTED LOOPS Cost: 145 Bytes: 379 Cardinality: 1                                         
                   17 HASH JOIN Cost: 22 Bytes: 42,558 Cardinality: 123                                    
                        15 MERGE JOIN CARTESIAN Cost: 15 Bytes: 8,910 Cardinality: 27                               
                             12 FILTER                          
                                  11 NESTED LOOPS OUTER Cost: 9 Bytes: 316 Cardinality: 1                     
                                       8 NESTED LOOPS OUTER Cost: 8 Bytes: 290 Cardinality: 1                
                                            5 NESTED LOOPS Cost: 6 Bytes: 256 Cardinality: 1           
                                                 2 TABLE ACCESS BY GLOBAL INDEX ROWID TABLE GDP.GDP_FX_DEALS_INCREMENTOR Cost: 4 Bytes: 28 Cardinality: 1 Partition #: 9 Partition access computed by row location     
                                                      1 INDEX RANGE SCAN INDEX GDP.GDP_FX_DEALS_INC_IDX_01 Cost: 3 Cardinality: 1
                                                 4 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_FX_DEALS Cost: 2 Bytes: 228 Cardinality: 1      
                                                      3 INDEX UNIQUE SCAN INDEX (UNIQUE) GDP.GDP_FX_DEALS_KEY Cost: 1 Cardinality: 1
                                            7 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_FX_DEALS Cost: 2 Bytes: 34 Cardinality: 1           
                                                 6 INDEX UNIQUE SCAN INDEX (UNIQUE) GDP.GDP_FX_DEALS_KEY Cost: 1 Cardinality: 1      
                                       10 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_COUNTERPARTIES Cost: 1 Bytes: 26 Cardinality: 1                
                                            9 INDEX UNIQUE SCAN INDEX (UNIQUE) GDP.PK_CPTY Cost: 0 Cardinality: 1           
                             14 BUFFER SORT Cost: 14 Bytes: 448 Cardinality: 32                          
                                  13 TABLE ACCESS FULL TABLE GDP.GDP_CITIES Cost: 6 Bytes: 448 Cardinality: 32                     
                        16 TABLE ACCESS FULL TABLE GDP.GDP_AREAS Cost: 6 Bytes: 2,304 Cardinality: 144                               
                   19 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_PORTFOLIOS Cost: 1 Bytes: 33 Cardinality: 1                                    
                        18 INDEX UNIQUE SCAN INDEX (UNIQUE) GDP.PORTFOLIOS_KEY Cost: 0 Cardinality: 1                               
    Explain Plan for Slow Query
    Plan
    SELECT STATEMENT ALL_ROWSCost: 11,526,226 Bytes: 119,281,912 Cardinality: 314,728                                                   
         21 SORT ORDER BY Cost: 11,526,226 Bytes: 119,281,912 Cardinality: 314,728                                              
              20 HASH JOIN Cost: 11,510,350 Bytes: 119,281,912 Cardinality: 314,728                                         
                   2 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_PORTFOLIOS Cost: 1,741 Bytes: 177,540 Cardinality: 5,380                                    
                        1 INDEX FULL SCAN INDEX (UNIQUE) GDP.PORTFOLIOS_KEY Cost: 14 Cardinality: 5,380                               
                   19 HASH JOIN Cost: 11,507,479 Bytes: 87,932,495,360 Cardinality: 254,140,160                                    
                        3 TABLE ACCESS FULL TABLE GDP.GDP_AREAS Cost: 6 Bytes: 2,304 Cardinality: 144                               
                        18 MERGE JOIN CARTESIAN Cost: 11,506,343 Bytes: 18,602,733,930 Cardinality: 56,371,921                               
                             15 FILTER                          
                                  14 HASH JOIN RIGHT OUTER Cost: 3,930,405 Bytes: 556,672,868 Cardinality: 1,761,623                     
                                       5 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_COUNTERPARTIES Cost: 6,763 Bytes: 892,580 Cardinality: 34,330                
                                            4 INDEX FULL SCAN INDEX (UNIQUE) GDP.PK_CPTY Cost: 63 Cardinality: 34,330           
                                       13 HASH JOIN OUTER Cost: 3,923,634 Bytes: 510,870,670 Cardinality: 1,761,623                
                                            10 HASH JOIN Cost: 2,096,894 Bytes: 450,975,488 Cardinality: 1,761,623           
                                                 7 TABLE ACCESS BY GLOBAL INDEX ROWID TABLE GDP.GDP_FX_DEALS_INCREMENTOR Cost: 2,763 Bytes: 52,083,248 Cardinality: 1,860,116 Partition #: 14 Partition access computed by row location     
                                                      6 INDEX RANGE SCAN INDEX GDP.GDP_FX_DEALS_INC_IDX_01 Cost: 480 Cardinality: 334,821
                                                 9 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_FX_DEALS Cost: 1,734,205 Bytes: 8,320,076,820 Cardinality: 36,491,565      
                                                      8 INDEX FULL SCAN INDEX (UNIQUE) GDP.GDP_FX_DEALS_KEY Cost: 104,335 Cardinality: 39,200,838
                                            12 TABLE ACCESS BY INDEX ROWID TABLE GDP.GDP_FX_DEALS Cost: 1,733,836 Bytes: 1,331,145,696 Cardinality: 39,151,344           
                                                 11 INDEX FULL SCAN INDEX (UNIQUE) GDP.GDP_FX_DEALS_KEY Cost: 104,335 Cardinality: 39,200,838      
                             17 BUFFER SORT Cost: 11,499,580 Bytes: 448 Cardinality: 32                          
                                  16 TABLE ACCESS FULL TABLE GDP.GDP_CITIES Cost: 4 Bytes: 448 Cardinality: 32                     
    How can I avoid that.
    Thanks

    Hello
    Could you reformat your execution plans because they aren't particularly readable. The forums allow you to preserve the formatting of code or output by putting the symbol {noformat}{noformat} before and after the section of text you want to preserve formatting for. 
    If you write
    {noformat}select * from v$version
    {noformat}
    it will be displayed asselect * from v$version
    So can you run this above statement and post the output here so we know the full oracle version you are working with?  And finally, it would be really helpful to see the query you are running.  When you say it runs fine in Toad, is that when you replace the bind variables with the values or are you also using bind variables in Toad?
    Cheers
    David                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • JAXB: Error compiling classes generated by xjc (file name too long)

    Hi friends,
    I am trying to compile classes that are generated by using XJC tool on xsd file. The compilation fails with following message.
    buildxsdmodel:
        [javac] Compiling 794 source files to /home/uchamad/working/teleworker/ejb/build/classes
        [javac] /home/uchamad/working/teleworker/ejb/build/tmpsrc/uk/co/novatel/teleworker/model/wlr/bulksearch
    results/impl/ApplicationInformationTypeImpl.java:58372: error while writing
    uk.co.novatel.teleworker.model.wlr.bulksearchresults.impl.ApplicationInformationTypeImpl.XMLRequestID
    TypeImpl.SearchOrderResultsTypeImpl.SearchTypeDetailTypeImpl.OrderTypeImpl.OrderDetailsTypeImpl.
    OrderLinesTypeImpl.NumberPortingTypeImpl.OLODetailsTypeImpl.NumberLocationTypeImpl.OLOMainP
    STN1AddressTypeImpl.Unmarshaller: /home/uchamad/working/teleworker/ejb/build/classes/uk/co/novatel
    /teleworker/model/wlr/bulksearchresults/impl/ApplicationInformationTypeImpl$XMLRequestIDTypeImpl$S
    earchOrderResultsTypeImpl$SearchTypeDetailTypeImpl$OrderTypeImpl$OrderDetailsTypeImpl$OrderLin
    esTypeImpl$NumberPortingTypeImpl$OLODetailsTypeImpl$NumberLocationTypeImpl$OLOMainPSTN1A
    ddressTypeImpl$Unmarshaller.class (File name too long)
        [javac]                                             public class Unmarshaller
        [javac]                                                    ^
        [javac] 1 error
    The compiler is complaining about the file name being too long. This is happening because the java classes when generated from XSD contains deep nesting of inner classes. So when it comes to compile the .class name file is too long for the operating system.
    I am trying this on unix box.
    I wonder if there is a way to configure XJC so that it does not produce inner classes but instead keep them out.
    Any help would be appreciated.
    many thanks
    Usmangani

    Flattening your schema definition will flatten the output files, too -- that will probably be nice for coding as well since you wont have to use class names such as SomeTypeNestedInAnotherTypeThatHasYetAnotherType. Instead of having all of the elements defined directly within the enclosing root element, define logical chunks at the top level and incorporate them in the definition of real root element of your documents by reference.

  • File name too long cannot copy (cont'd)

    This is a continuation of the post started September 01, 2009, with the last post on
    October 17, 2011 named File name too long cannot copy
    Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
    It is ever so easy to create a long file/path using explorer.exe as will be shown below.
    What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
    too long to copy, (and then perhaps even copying those over either intact or renamed)?
    Maflagulator said:
    I'm running the 7100 build...enjoying it except for one big thing:
    While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
    It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
    I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
    titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
    Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
    It made it through 400gb out of the 402gb transfer.
    I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
    causing the transfer process to halt.
    Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
    In Windows Vista, we learnt from:
    File names and file name extensions: frequently asked questions that:
    Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
    In Windows 7, we are told here:
    File names and file name extensions: frequently asked questions that:
    It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
    that has a longer path than the file's original location.
    From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
    Naming Files, Paths, and Namespaces
    This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
    260 minus C:\ (3) minus <NUL> (1) = 256
    256 minus 8.3 file name (12) = 244
    We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
    And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
    There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
    255 characters in length. This information is now gone.
    So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
    But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
    For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
    Let's create a long path/file.
    Create a folder called A at the root of a Drive.
    Create a sub-folder of A called: B
    Create a sub-folder of B called: C
    Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
    123456789U123456789V123456789W123456789X123456.txt
    Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
    123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
    Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
    Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
    You now have the lovely file placed at (the breaks are just so it fits into the screen):
    C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
    123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
    123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
    You have a folder length of over 700 and a file length of over 250 for a total of over 950
    However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
    This only applies backwards, that is up the path. It did not matter what was further down the path.
    Now, you can't easily access or rename the file, but you can rename the folders easily.
    For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
    So how might knowing this help us?
    Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
    Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
    Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
    Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
    Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
    Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
    Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
    Rename D:\A to D:\Original_top_Folder_name
    Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
    Note: If using Explorer, at some points you might have to press the F5 refresh key.
    This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
    sharing a sub-folder
    using the commandline to assign a drive letter by means of SUBST
    using AddConnectionunder VB to assign a drive letter to a path
    using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
    and so on.
    See how simple Windows can be for Dummies!
    But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
    them, or by copying them intact as they are?
    There have been suggestions to use
    LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
    where exactly they are located.
    Neither does the free
    Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
    So, as shown above, it is ever so easy to create a long file/path using explorer.exe
    So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
    (and then perhaps even copying those over either intact or renamed)?

    This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
    1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
    limit, the error appears).  The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
    2.  How do you know which combined file names + path names are too long if  you are in the  middle of a copy operation and this error pops up?  Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
    files are the "too long" ones.  If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
    3.   Here's how you sort out the "bad" from the "good":
    4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
      C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong 
           There are five levels root "1 football" with subfolders  2, 3, 4 and lastly "5 injuries"
    5.    Use "cut" and "paste"  (for example to backup all five levels to a new backup folder):
           select "1 football" ....cut....select target folder....paste 
           ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
          Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
    character limit"...instead "paste" to a C:/ root directory.
           Suppose in the middle of this operation...error pops up: "5 files have file names that are too long"  Skip or cancel?
           select "skip"  ...and let operation finish
    6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
    in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
    7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
          C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
    8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
    9.  hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
           like this:   5 injuriessidelineplayers  ....you should delete 'toolong'....from the folder name
    10.  then go into folder 5....and do the same operation ...with the too long file name:
            hit F2 rename file....file name hightlighted...delete some of the letters
               like this:  injuriessidelineplayers.....you should delete 'toolong' from the file name
    11.  Now..."cut and paste"  the renamed file to the target backup folder.  
    The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
    12.     Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty) 
    Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

  • Disk Utility (10.5.6) error: File name too long

    Hello, here is one for you all...
    I am in the midst of creating a new "build image" so I can start deploying Leopard.
    Before I upgraded the build to 10.5.6 I was able to create a disk image of this build machine.
    After updating it to 10.5.6 and all of the current Apple updates I am no long able to create a disk image.
    I keep getting an error several minutes into the imaging process that says +"*File name too long".*+
    I've run permission repair on the disk and Disk Warrior with still no luck. I've also used different machines and a boot FireWire drive to make he image and still have had no luck. I can use CCC to clone my Master build to another machine but I need to be able to make an image of it.
    Thanks in advance for any help.

    Bear in mind that in Unix, a file name includes the path, so if you have a very deep file or perhaps some kind of infinite recursive link, that might cause the problem, since that would make the file name very long indeed.
    This may not be the problem you are having, but it just came to my mind when I read your post

  • Literal too long when 4000 chars

    I get an error that literal too long when trying to insert a record to a clob or varchar2 field when the string is over 4000 chars.
    How to resolve this problem. I'd like to be able to treat this insert the same as all other inserts rather than make a special case out of it so no special processing would be needed.
    The application reads from an html form textarea and inserts the value of the text area along with the other fields of the form to a database.

    Hi,
    The maximum length of VARCHAR2 data is 4000 bytes.
    You can't store more than 4000 bytes in varchar2 column.
    CLOB can store upto 4GB of data.
    You can check the LOB Datatype sample for details on how to insert data into CLOB.
    The sample is located at
    [url http://otn.oracle.com/sample_code/tech/java/sqlj_jdbc/files/advanced/LOBSample/LOBSample.java.html] LOB Datatype source
    Check the loadSamples method which shows how to insert data into CLOB using empty_clob() method.
    Hope this helps.
    For furthur clarifications please post your question at
    [url http://forums.oracle.com/forums/forum.jsp?forum=75]SQL and PL/SQL Forum
    Regards,
    Anupama
    [url http://otn.oracle.com/sample_code/content.html]OTN Sample Code[url ]

  • File communication channel issue : object name too long

    Hi Experts,
    My requirement is to place the successful files in folder and un-successful files in one folder after processing.
    we used parameterized mapping to achieve this requirement.
    I'm facing below issues, please help me to resolve.
    " An error occurred while connecting to the FTP server. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unexpected reply codeSpecified object name too long, limit is 10 characters: $Filepath_Su.'. For details, contact your FTP server vendor.
    As per my understanding it is not taking the path specified,because of length issue.
    Please send me your valuable inputs and help me.
    Thanks in advance for your help.
    Regards
    Bhargava Krishna

    Hello,
    By loking ur error description, it's quite evident that it's a FTP sever issue?
    Sometime on FTP server, there is a check which is enabled to limit the length of file names, and i think the same has been recently implemented on ur FTP server. So instead of changing ur config, check with ur FTP admin.
    Tested the same after tweaking existing FTP server settings.
    Thanks
    Amit Srivastava

  • "Maximum number of application files exceeded or file names too long"...help!!!

    Hi there…
    I am trying to create a game for my mobile.
    The “problem” is that I have more than 500 swfs that I want to pack using the Adobe Mobile Packager. And I am getting this error:
    “Maximum number of application files exceeded or file names too long”
    How could I solve this problem?
    Thanks everyone!
    Cheers.
    Leo.

    500??  What are there so many files?
    The problem is that the CAB format only allows for 300 files maximum, so there's nothing that we can do about that I'm afraid.
    Mark
    www.flashmobileblog.com

  • Error: "client-error-request-value-too-long" when trying to add printer

    After installing the 10.4.9 Combo update, my HP 1350 All-in-One printer was not recognized. I reinstalled the driver, but now I can't add the printer. I get the error message "client-error-request-value-too-long" when trying to add the printer. Has anyone else experienced a similar problem.
    Thanks in advance

    Well, I tried all of that and I'm still getting the error message. I've also repaired disk permissions and run Disk Warrior. When I repaired disk permissions, many HP printer items showed up in the list.

  • I don't know why my iphone4 usually too hot when use about 15 minutes.

    I don't know why my iphone4 usually too hot when use about 15 minutes.
    can you get the another.
    thank you

    You're not addressing Apple here, this is a user to user support forum.
    Basic troubleshooting from the User's Guide is reset, restart, restore (first from backup then as new).  Has any of this been tried?

  • Receiving ERROR meassage when trying to copy..file name too long.

    Hello.
    There is an error code number, but didn't write it down...will do so, if no-one can answer this question at the minute. I am not at the Mac at the moment, so this post is pre-emptive.
    Problem:
    If I try to copy over a folder with photoshop images onto another drive, the copy is incomplete due to the name/s of the files being too long, apparently.
    The error message says something to the effect: 'the names are too long can't complete copy'.
    The file names are about 10-12 [at most]characters in length.
    Please advise
    Chris

    If the drive is formatted HFS then you are limited to 32 characters on a file name. If it is formatted HFS + then you can have file names as long as 255 characters. I am not familiar withi the format you say the drive is formatted in so I can't speak to it.
    If you are receiving -50 errors that can indicate a file name that is too long OR an illegal character in the filename regardless of its length.
    If you are actually using 10.3.8 as your profile states then that may be part of the problem. Many of these problems existed in 10.3.X but were fixed in 10.4
    I remember that 10.3.8 had issues copying to external drives when there were more than a certain number of characters in a filename. I don't remember the number but for some reason 10 or 12 is what comes to mind. It caused me many problems when I would try and copy files to a Zip disk that I used to have. Since I updated to 10.4 those issues have never occured again.
    Since you know what folder the problematic files are in why not just open the folder and try to copy files one at a time. When you get to the one(s) that is a problem, change the file name to something shorter.
    A better solution would be to update to 10.4 but with 10.5 coming out sometime in the Spring of 2007 this may not be the time.

  • Consolidating Library Error: File Name Too Long, But What File?

    I am trying to consolidate my library to put all my music (very unorganized) in one spot so I can back it all up. When I try to consolidate, it takes a second to prepare, then immediately brings up an error window saying "Copying Music Failed. The file name was invalid or too long."
    How do I fix this? I really would like to back up my music!

    Hi, ZeroGravity107.
    This can be a tricky problem to figure out since iTunes doesn't specify what file name is "invalid or too long" and there's no documentation on what determines if a file name is "invalid or too long".
    We had one user report that he was able to use his/her keen eyesight to note the last file that appeared before the error message appeared and it turned out that file was the cause of his/her trouble.
    If your eyesight isn't that keen, I'd suggest concentrating on the file name being too long possibility.
    The entire directory path leading to the file is considered part of the file name so, as an example, iTunes' default settings might place a particular file at C:\Documents and Settings\ user name \My Documents\My Music\iTunes\iTunes Music\artist folder\album folder\whatever.m4a.
    Is the directory path leading to your consolidated location much longer than that?
    polydorus has suggested a way to look over your file names: Assuming your music is currently in the default location, make your way there with Windows Explorer and select List in the View menu menu and see if anything stands out as being unusual.

  • Path tool long when using arrays

    Hey Powershell people. I'm running into an array issue in powershell where the error "Copy-Item : The specified path, file name, or both are too long" is thrown back at me. However, the odd thing is if I type the copy path in manually the script it works
    fine, so the error only occurs when the script directly references the item in the array by its numbered location. Eventually, I want to create a for loop for this that will reference each file name in the array, so i'm hoping I can directly reference
    the array pointer.
    $DTS = get-date -format "dd-MM-yyy_hh-mm-ss"
    New-Item c:\$DTS -type directory
    $get = Get-Content C:\array.txt
    Start-Sleep -s 1 
    $testdata=@"
    $get            
    ($testdata | Select-String -Pattern '(?<=t.s.\\.).+?(?=\. u s p)' -AllMatches).Matches | %{$_.Value} | Out-File c:\test.txt
    Start-Sleep -s 1
    $get2 = Get-Content C:\test.txt
    $get2 = $get2 -replace " ", "" | Out-File c:\test.txt
    $get = Get-Content C:\test.txt
    Copy-Item "\\server\C$\Program Files\Projects\$get[0].usp" \\server2\C$\$DTS
    Note, if I do something like $get4 = $get[0] the script will properly reference $get[0] if $get4 is inserted into the copy path . 

    Sorry, let me try to explain a little better. The script is suppose to create a folder using the date/time on root C:, read from array.txt file (has the file
    information in it), parse out all files names from array.txt into text.txt, parse out all spaces from text.txt, use the file names in text.txt array as a variable to copy the files from one location to another.
    Pseudo Example
    Parsed file names in text.txt
    1234567890
    0987654321
    6789054321
    Loop Pseudo
    $filename[] = ReadFrom text.txt
    Loop through all file names in text.txt
    CopyFrom C:\FilePath\$filename[].usp to C:\FolderWithDateAndTime

  • XML Tag Name too long, won't run from a procedure

    I have a select statement that creates an xml file using the xmlelement syntax. When I run the select statement on its own it runs fine and the xml file is generated with no errors. I'm building a procedure that does a bunch of stuff, with the end product being the generated xml file. Everything in the procedure works great, until I add the xmlelement select statement. When I try to compile it I get an error message that one of the identifiers is too long (it is 40 characters). Is there something special I need to do to get this to run within a procedure with the given tag names? I can't change the names as they are set by another department.
    Thanks.

    Sorry about that, Mondays are painful...
    I'm not sure if you want the whole procedure, it is quite long, but here is the xml part. I am using TOAD, and when I right click and Compile I receive this error: PLS-00114: identifier 'PostalCodeOfPatientsCurrentResidenceKnownFlag FROM Admissions' too long
    The part that confuses me is why does it run fine when I run it on it's own, I get the expected XML file, but when I try to run it from a procedure it fails.
    SELECT sys_xmlgen(XMLELEMENT("MHR", XMLELEMENT("Control",      XMLELEMENT("DeliverySiteInstitutionNumber",a.institution_number),
                                                           XMLELEMENT("CreationTimestamp",sysdate),
                                                                               XMLELEMENT("DSSVersion",'NotSure'),
                                                                               XMLELEMENT("ResubmissionFlag",'1'),
                                                                               XMLELEMENT("SubmissionYear",a.REPORT_YR_AND_MNTH),
                                                                               XMLELEMENT("SubmissionPeriod",a.SUBMISSION_PERIOD)),
         XMLELEMENT("Stakeholders",XMLELEMENT("Stakeholder", XMLELEMENT("SubmissionType",'A'),
                                                                                                                  XMLELEMENT("ULI", a.ULI),
                                                                                              XMLELEMENT("Gender",'Male/Female/Unknown'),
                                                                     XMLELEMENT("BirthDate", XMLATTRIBUTES(a.BIRTH_DATE_TYPE,a.BIRTH_DATE)),
                                                                                                                  XMLELEMENT("ResidenceInformation",XMLELEMENT("ProvinceOfPatientsResidence",a.PROVINCE_OF_RESIDENCE),
                                                                                                                                      XMLELEMENT("PostalCodeOfPatientsCurrentResidenceKnownFlag",a.POSTALCODE_KNOWN_FLAG),
                                                                                                                                                          XMLELEMENT("PostalCodeOfPatientsCurrentResidence",a.POSTALCODE))
                        )).getClobVal() AS "result"
    FROM Admissions a
    Edited by: user11293056 on Jun 22, 2009 12:54 PM

Maybe you are looking for