Rep-0530 file too long

hi,
i have a query 78617 characters and 1754 lines. in a file it is about 80-84 kb.
if i paste this query on report builder wizard then only a part of this query is pasted..
if i select the option import query then it displays error as rep-0530 file too long. it will be truncated to fit.
is there any limit for query size in reports.. same query runs fine in sqlplus,toad.
regards,
Avinash

Hello,
http://www.oracle.com/webapps/online-help/reports/10.1.2/topics/htmlhelp_rwbuild_hs/rwcontxt/props/pi_sql_query_statement.htm
Value
A valid SELECT statement not to exceed 64K.
Regards

Similar Messages

IMovie file too long for iDVD

I created an iMovie (4 1/2 hours long of Hawaii vacation) that is too large to transfer to one DVD in iDVD. I know this must be simple but, please would someone tell me how to break up my completed movie into two more easily digestible movies that would become DVD part 1 and DVD part 2?
Thank you!!!

Hi c
Catspaw - are exelent.
My way are more tedious but.
If You have a very larg hard disk. Copy Your project.
(Will need about 70Gb free space)
Edit project 1 to less than 2 hours of the beginning
Edit project 2 to the following 2 h
Yes it is tedious and hard disk demanding.
If You by any chance doesn't have any editing to Your movie the You could
make it very easy.
Move the first 2 h to Your time line from Shelf
Close iMovie and Save
Locate the QT ref mov in the project icon and make a copy of it on the desktop. Drop this into a folder named part 1
Start iMovie and replace the clips with what follows - and re do but put
the QT copy in a folder - part 2
Keep on till all clips are used.
Now burn Your DVD's with the new QT ref movie copies.
One DVD per QT mov.
It really works.
Yours Bengt W

XML file too long

Hi all,
I have the following problem regarding XML file.
I generate an XML file with following steps:
1) Populate an internal table;
2) Transform the internal table into an xml xstring variable, using CALL TRANSFORMATION command;
3) Write a file in binary mode (Open/Tansfer/Close).
The file produced is ok but if I open it with notepad, all the xml is written in one line.
Is there a way to write the file in more than one line?
Best Regards,
Raffaele

Hi,
You have to use a carriage return statement(^M) at the end of each line in ABAP to produce the file correctly this will help you to split the file in multiple lines rather than a single line in the Notepad. Also when you will open this in the notepad you can visualize the same format in comparision when youopen it in IE/Wordpad.
Hope this carifies you queries.
Cheers,
Jay

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...

Destination file characters too long (File names) , while copying from one external to another

I have a external my book fat32 formated and a new mybook ntfs formated external as well. Now when I copy my files from the fat32 to the ntfs external all files copy fine but some give that destination location file characters are too long, meaning that the file names are too long. Now I could change the file names but that would conflict with programs that need that file name. I am using vista ultimate and would like to copy all the files over from the fat32 to ntfs so I can reformat the fat32 to ntfs. The files got on the ntfs from a simple drag and drop from my IDE NTFS internal hard drive.
I hope you guys to tell me what to do.
Thank you :)

Here's the 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)

ITunes v10.6.1.7 "Copying files failed. The File name was invalid or too long."

I'm trying to organize my music files using iTunes 10.6.1.7 and I keep getting the error message "Copying files failed. The File name was invalid or too long."
I've got music folders by artist in both the iTunes Music folder and the iTunes Media/Music folder. When I add certain files by drag/drop they sometimes get lost and I don't want that to happen anymore. I used to just consolidate my music files using the File/Library/Organize Library option and that worked, however now when I do that, I get the error message.
I'm a novice and the only online stuff I see is both confusing and refers to earlier versions of iTunes.
My concern is that I have heard that people lose entire libraries of their music when they trry to fix things like this and I don't want that. If this is of any importance, I have several files called iTunes library and temp library. I have no idea what that all means but I'm scared to death of it.
Also, I can't get to the "re-organize library" link at all. It won't let me.
One thing that be of some interest is that when I pull up the properties of the music and media/music files they are marked "read only" I'm also afraid to touch that!
Please help and please know that I am a dummy. Be kind and be clear. Step by step would be great, with images even better. Thanks.

Perhaps nobody knows the answer? We're fellow users here answering questions in our free time when we think we've something useful to contribute.
You can choose to *Consolidate selected tracks* with a right-click menu. Perhaps if you can identify a specific track that won't consolidate and examine the full path to the file & the path that iTunes would create when it consolidates the problem might become apparent. For example iTunes may not be able to move files if the source or destination path length exceeds 255 characters.
tt2

Source path too long :-Unable to delete mutiple number of folder and files from windows 2008 R2 file server

Hi Team,
we have a file server on windows server 2008 R2, I have copied some data from one server to another server using robocopy . I have checked access permission it seems okay no issues with access permission. but when i am trying to delete these folder i am
getting below error message
Error message:-
The source file name are larger than is supported by the file system.try moving to a location which has a shorter path name or try renaming to shortcut names before attempting this operations
Regards,
Triyambak
Regards, Triyambak

I have tried everything , but nothing help , getting same error
could any one help me regarding this.
Regards, Triyambak
I have not looked at the other thread mentioned, but usually when this ends up happening, There are several ways to go about it. One is to map a drive to the UNC path deeper into the folder structure.
So instead of C:\long\path\that\we\dont\want\files\in
You map a drive.. lets say M:\ to \\computer\c$\long\path\that\we\dont\want
Now, when you open Explorer to M:\ you've elimintated the length of the path down to M:\files\in which is completely usable.
The other way, is to shorten the names of everything. For example...
Folder structure like this:
Root
-----Folder1
-----Folder2
--------------Folder2A
-----Folder3
--------------Folder3A
Rename all the folders to shorten up the path. Rename Folder1 to '1' Rename Folder2 to '2', Rename folder3 to '3. Then try to delete. If it's still too long, go one folder deeper. Rename Folder2A to '1' and
Rename Folder3A to '1' and so on. Basically keep renaming everything to a single digit character and eventually you'll shrink the path down to where you can shift-delete everything remaining.
Hope that helps.
Brian / ChevyNovaLN

Cannot delete file: filename too long

Sometime ago, I made a copy of a hierarchy of folders under my "Users" folder to another drive as a quick backup. I no longer need this copy of folders and files. So when I tried to delete these files I got a message that some filenames are too long. When
I look at these files they mostly seem to be part of Internet Explorer temp directory, and also some files used by Mozilla Thunderbird, so they were likely created by these utilities on purpose. I cannot rename them to shorter names, or even move them to lower
folders. I can't even copy their filenames to show you what these filenames are! When I use the DOS prompt's "dir /x" command these files do not even have any 8.3 short filenames either, which I could've used to delete them with. There are over 400 of these
files!
I know what the problem is, the Windows OS has a limit of somewhere around 250 characters for filenames and complete pathnames. I've seen some utilities advertised saying that they can delete these files, but they all require money. Anything that's free?
Yousuf Khan

Hi,
It is just for testing. It is good since the files can be deleted in Linux.
However, if you don't have Linux, it needs to find the way to delete the files under Windows.
Since the files are located in Internet Explorer temp directory, you could use Disk Cleanup to clear the Temporary Internet Files.
Also, check if the following KB is helpful. It has several methods. Go to check if 8.3 name creation is disabled.
http://support.microsoft.com/default.aspx?scid=kb;en-us;320081
Best Regards,
L.S
Regarding it being in the Internet Explorer temp directory, it actually wasn't. Remember I said in the original posting that this was in a backup directory of these directories, so Disk Cleanup has no way of knowing that this belongs to Internet Explorer
or anything else. Also there was a Thunderbird directory having the same issues as well, which Disk Cleanup wouldn't have touched no matter what.
Okay, I checked out the state of the filesystem registry. The "NtfsDisable8dot3NameCreation" entry in the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem" is set to non-zero, meaning the feature is in effect. Interestingly it was set to 2
rather than 1, but I doubt that makes a difference.
Even if I disable this feature right now, all previously created files still won't be assigned the 8.3 filenames, just only those files that are newly created will have the 8.3 filenames available.
Yousuf Khan

"PLS-00172: string literal too long" When Writing XML file into a Table

Hi.
I'm using DBMS_XMLStore to get a XML file into a db table. See the example below, I'm using that for my PL/SQL format. Problem is that because there're too many XML elements that I use in "xmldoc CLOB:= ...", I get "PLS-00172: string literal too long" error.
Can someone suggest a workaround?
THANKS!!!
DECLARE
insCtx DBMS_XMLStore.ctxType;
rows NUMBER;
xmldoc CLOB :=
'<ROWSET>
<ROW num="1">
<EMPNO>7369</EMPNO>
<SAL>1800</SAL>
<HIREDATE>27-AUG-1996</HIREDATE>
</ROW>
<ROW>
<EMPNO>2290</EMPNO>
<SAL>2000</SAL>
<HIREDATE>31-DEC-1992</HIREDATE>
</ROW>
</ROWSET>';
BEGIN
insCtx := DBMS_XMLStore.newContext('scott.emp'); -- get saved context
DBMS_XMLStore.clearUpdateColumnList(insCtx); -- clear the update settings
-- set the columns to be updated as a list of values
DBMS_XMLStore.setUpdateColumn(insCtx,'EMPNO');
DBMS_XMLStore.setUpdateColumn(insCtx,'SAL');
DBMS_XMLStore.setUpdatecolumn(insCtx,'HIREDATE');
-- Now insert the doc.
-- This will only insert into EMPNO, SAL and HIREDATE columns
rows := DBMS_XMLStore.insertXML(insCtx, xmlDoc);
-- Close the context
DBMS_XMLStore.closeContext(insCtx);
END;
/

You ask where am getting the XML doc. Well, am not
getting the doc itself.I either don't understand or I disagree. In your sample code, you're certainly creating an XML document-- your local variable "xmldoc" is an XML document.
DBMS_XMLSTORE package needs
to know the canonical format and that's what I
hardcoded. Again, I either don't understand or I disagree... DBMS_XMLStore more or less assumes the format of the XML document itself-- there's a ROWSET tag, a ROW tag, and a then whatever column tags you'd like. You can override what tag identifies a row, but the rest is pretty much assumed. Your calls to setUpdateColumn identifies what subset of column tags in the XML document you're interested in.
Later in code I use
DBMS_XMLStore.setUpdateColumn to specify which
columns are to be inserted.Agreed.
xmldoc CLOB :=
'<ROWSET>
<ROW num="1">
<KEY_OLD> Smoker </KEY_OLD>
<KEY_NEW> 3 </KEY_NEW>
<TRANSFORM> Specified </TRANSFORM>
<KEY_OLD> Smoker </KEY_OLD>
<VALUEOLD> -1 </VALUEOLD>
EW> -1 </VALUENEW>
<DESCRIPTION> NA </DESCRIPTION>
</ROW>
ROWSET>';This is your XML document. You almost certainly want to be reading this from the file system and/or have it passed in from another procedure. If you hard-code the XML document, you're limited to a 32k string literal, which is almost certainly causing the error you were reporting initially.
As am writing this I'm realizing that I'm doing this
wrong, because I do need to read the XML file from
the filesystem (but insert the columns
selectively)...What I need to come up with is a proc
that would grab the XML file and do inserts into a
relational table. The XML file will change in the
future and that means that all my 'canonical format'
code will be broken. How do I deal with anticipated
change? Do I need to define/create an XML schema in
10g if am just inserting into one relat. table from
one XML file?What does "The XML file will change in the future" mean? Are you saying that the structure of the XML document will change? Or that the data in the XML document would change? Your code should only need to change if the structure of the document changes, which should be exceptionally uncommon and would only be an issue if you're adding another column that you want to work with, which would necessitate code changes.
I found an article where the issue of changing XML
file is dealt by using a XSL file (that's where I'd
define the 'canonical format'), but am having a
problem with creating one, because the source XML is
screwed up in terms of the format:
it's not <x> blah </x>
<x2> blah </x2>
x2="blah" x3="blah> ...etc
Can you point me in the right direction, please?You can certainly use something like the DBMS_XSLProcessor package to transform whatever XML document you have into an XML document in an appropriate format for the XMLStore package and pass that transformed XML document into something like your sample procedure rather than defining the xmldoc local variable with a hard-coded document. Of course, you'd need to write appropriate XSL code to do the actual transform.
Justin

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.

SharePoint 2010, Visual Studio 2010, Packaging a solution - The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Hi,
I have a solution that used to contain one SharePoint 2010 project. The project is named along the following lines:
<Company>.<Product>.SharePoint - let's call it Project1 for future reference. It contains a number of features which have been named according
to their purpose, some are reasonably long and the paths fairly deep. As far as I am concerned we are using sensible namespaces and these reflect our company policy of "doing things properly".
I first encountered the following error message when packaging the aforementioned SharePoint project into a wsp:
"The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
I went through a great deal of pain in trying to rename the project, shorten feature names and namespaces etc... until I got it working. I then went about gradually
renaming everything until eventually I had what I started with, and it all worked. So I was none the wiser...not ideal, but I needed to get on and had tight delivery timelines.
Recently we wanted to add another SharePoint project so that we could move some of our core functinality out into a separate SharePoint solution - e.g. custom workflow
error logging. So we created another project in Visual Studio called:
<Company>.<Product>.SharePoint.<Subsystem> - let's call it Project2 for future reference
And this is when the error has come back and bitten me! The scenario is now as follows:
1. project1 packages and deploys successfully with long feature names and deep paths.
2. project2 does not package and has no features in it at all. The project2 name is 13 characters longer than project1
I am convinced this is a bug with Visual Studio and/or the Package MSBuild target. Why? Let me explain my findings so far:
1. By doing the following I can get project2 to package
In Visual Studio 2010 show all files of project2, delete the obj, bin, pkg, pkgobj folders.
Clean the solution
Shut down Visual Studio 2010
Open Visual Studio 2010
Rebuild the solution
Package the project2
et voila the package is generated!
This demonstrates that the package error message is in fact inaccurate and that it can create the package, it just needs a little help, since Visual Studio seems to
no longer be hanging onto something.
Clearly this is fine for a small time project, but try doing this in an environment where we use Continuous Integration, Unit Testing and automatic deployment of SharePoint
solutions on a Build Server using automated builds.
2. I have created another project3 which has a ludicrously long name, this packages fine and also has no features contained within it.
3. I have looked at the length of the path under the pkg folder for project1 and it is large in comparison to the one that is generated for project2, that is when it
does successfully package using the method outlined in 1. above. This is strange since project1 packages and project2 does not.
4. If I attempt to add project2 to my command line build using MSBuild then it fails to package and when I then open up Visual Studio and attempt to package project2
from the Visual Studio UI then it fails with the path too long error message, until I go through the steps outlined in 1. above to get it to package.
5. DebugView shows nothing useful during the build and packaging of the project.
6. The error seems to occur in
CreateSharePointProjectService target called at line 365 of
Microsoft.VisualStudio.SharePoint.targetsCurrently I am at a loss to work out why this is happening? My next task is to delete
project2 completely and recreate it and introduce it into my Visual Studio solution.
Microsoft, can you confirm whether this is a known issue and whether others have encountered this issue? Is it resolved in a hotfix?
Anybody else, can you confirm whether you have come up with a solution to this issue? When I mean a solution I mean one that does not mean that I have to rename my namespaces,
project etc... and is actually workable in a meaningful Visual Studio solution.

Hi
Yes, I thought I had fixed this my moving my solution from the usual documents to
c:\v2010\projectsOverflow\DetailedProjectTimeline
This builds ok, but when I come to package I get the lovely error:
Error 2 The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\VS2010\ProjectsOverflow\DetailedProjectTimeline\VisualDetailedProjectTimelineWebPart\Features\Feature1\Feature1.feature VisualDetailedProjectTimeline
Now, the error seems to be related to
Can anyone suggest what might be causing this. Probably some path in an XML file somewhere. Here is my prime suspect!
<metaData>
<type name="VisualDetailedProjectTimelineWebPart.VisualProjectTimelineWebPart.VisualProjectTimeline, $SharePoint.Project.AssemblyFullName$" />
<importErrorMessage>$Resources:core,ImportErrorMessage;</importErrorMessage>
</metaData>
<data>
<properties>
<property name="Title" type="string">VisualProjectTimelineWebPart</property>
<property name="Description" type="string">My Visual WebPart</property>
</properties>
</data>
</webPart>
</webParts>
.... Unless I can solve this I will have to remove the project and recreate but with simple paths. Tho I will be none the wiser if I come across this again.
Daniel

Consolidating Music Files into Itunes - File Name Invalid/Too Long!

When trying to consolidate music files into my library, I get an error message stating "Failed, The file name was invalid or too long." ????
I have tons of songs and don't know which file name is invalid or too long???

hiya!
hmmmm. we're looking for filenames here where the path and the filename has more than 256 characters in it. (at least i believe that's what the path-filename length limit is.)
possibly the easiest way to check for that is to use a spreadsheet like excel.
right-click your library in your itunes sourcelist, and select "export songlist ...". save it as a .txt file.
open the .txt file with Excel (or whatever spreadsheet application you have on the PC). the column with the path-filename in it is the one to the extreme right (you can delete the other columns and resize them to make looking for things a bit easier).
scroll through that looking for extremely long path-filenames.
can you track down some that seem to be above the length limit?
love, b

File name invalid or too long

Hey all, pretty new to this so please give some leaway. Paha
I've just gone to organise my iTunes libary and have all the files in the same folder, (consolidate) and it's said that it's failed and the file name is invalid or too long?
What can I do to fix this so I can transfer all my data to my new computer with ease?

Anyone!?

"Copying Music Failed - File name invalid or too long." HELP!

I desperately need to consolidate my music before my computer says goodbye for all eternity. It seems I can't consolidate my music because apparently, the file name is too long or invalid. I even got this program that was supposed to help me seek out the ones with too long file names. So I deleted those songs and it still won't work. And after I got the new iTunes the other day, I set it to add all new songs automatically into the iTunes Music Folder. However, it seems my iTunes is a little screwed up, because whenever I add a song with a long file name, it automatically shortens it down. For example if I add a song with the named "20th Century Masters - The Millennium Collection: The Best of Smokey Robinson & The Miracles - Smokey Robinson & The Miracles - Ooo, Baby Baby", which is obviously a very long name, it will shorten it down to about the first 4 or 5 words. I naturally shorten it down to just "Ooo, Baby Baby" myself, but I'm thinkin this whole error may have something to do with the fact that the library won't consolidate.
I'm in desperate need of help here - come to my rescue, please!

Well, aren't you lucky I signed in tonight? Sometimes you just have to be patient and wait until a person who might know an answer shows up.
I have had problems with Consolidate too, and getting that stupid error message when the file name was not too long.
The consolidate function starts copying things over by Date Added, with the older ones getting copied first. First in, first out.
What I finally had to do was look in Windows Explorer for the target (new) drive and see the last file that was successfully copied. Let's call it Carole King.
Then I went into iTunes and sorted by Date Added to see the file just AFTER the Carole King file. In my case, it was La Bohème and iTunes had filed it in the Compilations folder. I selected all the tracks and unchecked the Compilations box. This made iTunes move it out of the Compilations folder
The Consolidate worked after I moved that file.

When trying to 'Consolidate Files' via iTunes I get the message "Copying files failed. The name was invalid or too long."

I am trying to copy my entire iTunes library and everything in it from my PC Desktop to my PC Laptop using the "External Drive" method as shown on the Apple website. On Part 1 (5) I am told to consolidate files. When attempting to do this I get the message "Copying files failed. The file name was invalid or too long."
How do I resolve this?

I have just been having this problem and it has been driving me mad. The error message doesn't tell you which file is causing the problem so you can't fix it and it leaves your libray in a state of limbo with some files copied into the new location and some in the old location. After many hours I found a surprisingly quick and simple solution.
1) in iTune create a smart play list that includes everything that was added before tomorrows date. This will include everything.
2) Right click this playlist and export it as a text file to produce a tab delimited file.
3) Import this into a spread sheet, or just view it in a text editor with line wrap turned off. What you are interested in is the last column (or end of the line in a text editor). This gives you the path of the file associated with each entry in the library.
The path of the files that have already been copied successfully will start with the new location for your media files you specified. Scroll thru the rows until you get a blank path. If you start getting paths starting with the old Media file location then you went to far and start scrolling back.
The row with the blank path was the file that failed. Move back to the start of the row to find out more about it. In my case it was a podcast with a very long name. I just deleted that podcast from iTunes.
4) Restart the consolidation by choosing File, Library as you did before and the process starts again where it left off.
5) If it fails again on another file just repeat the process

Rep-0530 file too long

Similar Messages

Maybe you are looking for