Restore-DfsrPreservedFiles "Path Too Long" Error

I'm attempting to run this on a file server where all replicated folders live in the D:\data drive. I am not sure why I would get a "Path Too Long" error and the exception does not provide any clues as to what it doesn't like -- or if it does,
I am reading it wrong. Ideas anyone?
PS C:\Users\Administrator> Restore-DFSRPreservedFiles -Path "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml" -Restor
eToPath "D:\backup\recovery\dfsrrecovery" -RestoreAlLVersions -CopyFiles -Force -verbose
VERBOSE: Loading preserved file manifest: "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml"
VERBOSE: Restoring preserved files from manifest: "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml"
Restore-DFSRPreservedFiles : 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.
At line:1 char:1
+ Restore-DFSRPreservedFiles -Path "D:\data\DfsrPrivate\ConflictandDeletedManifest ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Restore-DfsrPreservedFiles], PathTooLongException
+ FullyQualifiedErrorId : System.IO.PathTooLongException,Microsoft.DistributedFileSystemReplication.Commands.Resto
reDfsrPreservedFilesCommand

Hi Mark,
This has been already discussed here. Please refer the below thread.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/14fc8393-d616-408f-abad-49a3ccb15585/windows-server-2012-r2-running-restoredfsrpreservedfiles-getting-path-file-name-or-both-are-too?forum=winserverfiles
Devaraj G | Technical solution architect

Similar Messages

File path too long when collecting??...

Hi all,
REALLY hope someone has some wisdom on this! I've searched forums and the web and not yet found an answer....
I've got a MASSIVE project on an external drive that's on the way out, so I want to collect the project that's on it to another new healthy drive. The current file structure leaves alot to be desired (several years of updating the same project and splitting it into managable portions then importing them back together several times, files still on there that aren't in use in AE anymore but have been kept 'incase we need them again later', etc...you can imagine the mess!)
SO, I'm getting the 'file path too long' error when trying to collect it. Now, I could manually go through every folder and sub folder and tidy things up within AE - this would days about a week I reckon! - but I'll do it if that's the only way. What I'm wondering is this: -
A) is the problem AE is having with the deep structure *WITHIN* ae project, or with the actual folders/files on the disk itself?
B) if I tidy it up in AE only will that fix it?
C) is there an easier way to do this rather than manually going through everything and looking for the offenders???
Thanks guys,
Jim.

GULP....so I have to reorganise my assets OUTSIDE of AE and then relink it all WITHIN AE afterwards?? With 3 x 430GB projects and thousands of assets that is going to take a looooooooonng time.
What I don't understand (or like) is how AE will let you get this far without any warning and still operate/save, etc but then when you come to collect is goes 'urr urrrr, computer says no'.
Is there really no way of automating some of this then? I mean even a script that highlighted items in the project that are over the maximum path length would save a hell of a lot of manual searching and counting.
Thanks for your replies guys but.....AAAARRGGHH!!!!!

Destination Path Too Long having this problem on desk top computer

Destination Path Too Long
when I try to move files from my desk top screen to my external hard drive or my internal hard drive I get this error message:
Path Too Long: The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.
These are files that I have previously moved from my internal hard drive on to my desk top [screen] computer, this error seems to pop up on my desk top not my lap top, both running windows
7. These files do not have long names, and I can not "skip" these files these are files that I have created for business or fun.
I am not a computer tech so if some one could instruct me what to do I would appreciate this.

Hi,
the destination path is the full path you are copying to. In case of a library for example that would be (by default) c:\users\username\folder. The length of paths quickly adds up and may not exceed 255. Copying the file to a longer destination
path would render the file inaccesible in standard ways.
Consider to try copying the files to a shorter destination path (not to c:\folder\longfolder\subfolder\folder\ but to c:\x\for example). Please post back if that does not work either.
The foldername in your screenshot alone already has 40 about characters. Consider using shorter descriptive names for your folders. For example 'Bible scripts FB2010' only contains 22 characters and contains more or less the same info)
http://support.microsoft.com/kb/177665
If you still use large folderstructures to 'easily' track down your files, consider spending less time arranging files and using search more often. If I for example would need some file, I tap the windows key and start typing some part of the filename or
even it's contents or tags. Usually before I have typed afew characters, the startmenu shows exactly the document or picture I need. I' ve got about 4000 documents of all kinds stored in "my documents" only roughly spread over some folder like Letter,
Script, Work, House\*year*, Pay\*year*...Index your folders, use a bit of tagging and let the computer do the work!
Also, Windows does contain methods to access longer filepaths (see
http://social.technet.microsoft.com/Forums/en/winservergen/thread/cc7491ae-5039-4cf5-8347-d43f22389bb0) but these are not recommended for daily use as applications might fail handling files stored in such paths.
MCP/MCSA/MCTS/MCITP

ORA-01467: Sort key too long error.

Dear All,
I have a complex query having lot of joins. It is working fine.
I just added few functions to it i.e. now few fields are calculated using functions.
Now it start giving error: ORA-01467: Sort key too long error.
What may be the problem?
Please help.
-Sameer

ORA-01467 sort key too long
Cause: A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement.
Action: Reduce the number of columns or group functions involved in the operation.

Sort key too long error

Hi,
I have a query which is customizable by the user based on changes to a table. They recently added 12 more double-precision columns to the table, giving them a total of 353 number columns and 32 varchar2 columns.
The query needs to summarize these records into another table. Before adding the 12 new columns it worked fine. Now we get the oracle sort key too long error.
Basically, the query looks like this:
insert into MyTable(txtField1,txtField2,..,txtField32,numField1,numField2, ..,numField353)
select txtfield1,txtfield2,..,txtfield32, SUM(numfield1),SUM(numfield2), .., SUM(numfield353)
from MyOldTable
where txtField1='somevalue' and txtField2='some other value'
group by txtField1,txtField2,..,txtFieldn;
I have tried increasing the sort_area_size parameter and it doesn't make a difference. What else can/should I change in order to get this query working again? As I said, this worked when there were only 341 sum columns.
Thanks for any information you may provide.
Thanks,
Rob

The sort key in Oracle is retricted to a length of one database block less some overhead. The only way to get the query to work is to increase your db_block_size parameter. Unfortunately, this will require rebuilding your database from scratch.
In 9i, you can have different block sizes for different tablespaces. If you are running in 9i, you may be able to move the affected tables to a tablespace with a larger block size, and then do the query. I am not sure which block size would be used for the sort key in 9i, the "database" block size or the "tablespace" block size.
Alternatively, you could look at the design of the table to see if you could split it up into several narrower tables, and use views to get the reporting.
HTH
John

'sort key too long error' while trying to use dynamic sql

Hi All,
I have been trying to generate an interactive report using a dynamically generated SQL query.. for this I have
1) Created a application process that returns the dynamically generated SELECT statement
2) Create a process in the page which creates a collection based on the SELECT statement returned by the application process
3) An interactive report that selects ALL (SELECT * ....) from that particular collection.
On implementing I am getting the 'ORA-01467: sort key too long' error.
On checking this out online I realized that one has to change the Block size of the database to get past this error, but in order to do that I would have to re-create the database, create a backup of the data and then re enter them into the new database which would be a nightmare.
I would like to know if there is any work around to this....
CODE IN THE APPLICATION PROCESS
DECLARE
q VARCHAR2(1000);
BEGIN
IF :P124_COUNTRY - :P124_WORK_GROUP - :P124_PRODUCT - :P124_ROLE = 1 THEN
q:= 'SELECT VISA_COUNTRY AS "Country", ROUND(((COUNT(VISA_ID)/(SELECT COUNT(ROW_ID) FROM PSA_RESOURCE_MANAGER WHERE ACTIVE_FLAG = ''Y''))*100),2) || ''%'' AS "Travel Readiness %" FROM PSA_VISA_INFO WHERE ACTIVE_FLAG = ''Y'' AND VISA_ACTIVE_FLAG = ''Y'' GROUP BY VISA_COUNTRY';
END IF;
return q;
END;
CODE IN THE PROCESS THAT CREATES THE COLLECTION:
APEX_COLLECTION.CREATE_COLLECTION_FROM_QUERY_B(
p_collection_name => 'TRAVRED_TEST',
p_query => 'application_process=set_query' );
CODE IN THE INTERACTIVE REPORT:
Select *
From apex_collections
Where collection_name = 'TRAVRED_TEST';
I also tried selecting just 'c001, c002' etc which gave me a 'no data found' output. The query work fine when I ran it in the SQL Workshop
Please help!
Thanks in advance :)

Hey Ben,
I am getting the same error when I used the following code in the app process....
DECLARE
q VARCHAR2(32767);
BEGIN
IF :P124_COUNTRY - :P124_WORK_GROUP - :P124_PRODUCT - :P124_ROLE = 1 THEN
q:= 'SELECT visa_country,
COUNT(visa_id) visa_count
FROM psa_visa_info
WHERE active_flag = 'Y'
AND visa_active_flag = 'Y'
GROUP BY visa_country),
row_id_count AS
(SELECT /*+ MATERIALIZE */
COUNT(ROW_ID) row_count
FROM PSA_RESOURCE_MANAGER
WHERE ACTIVE_FLAG = 'Y')
SELECT visa_country,
ROUND(visa_count/(SELECT row_count FROM row_id_count)*100,2) travel_readiness FROM PSA_VISA_INFO WHERE ACTIVE_FLAG = ''Y'' AND VISA_ACTIVE_FLAG = ''Y'' GROUP BY VISA_COUNTRY';
END IF;
return q;
END;
Thanks

ITunes installation error - no C-drive, invalid C-drive, or specified path too long

This is an answer rather than a question as answer to a previous question seemed unresolved and I had similar problem which I have resolved. I thought posting it might help others...
My OS System disk wasn't set as the C-drive (how or why I'm not sure, but I have several OS installations and 2 hard-drives and must be a result of the way I installed these). And so I had no C-drive at all (except when I plugged in USB Pen's they would appear as C-drive).
iTunes wouldn't let me install unless I had a C-drive - probably said I had an invalid C-drive or something. So I tried creating a virtual C-drive by mapping the C: drive letter to a new empty folder on my system disk (G-drive) to "C:". See - http://ask-leo.com/i_have_no_c_drive_but_some_programs_insist_on_it_what_can_i_d o.html
This DIDN'T resolve the problem as it merely created a different error message - it said: "The specified path is too long C:\Program Files" NB This is despite me telling it to install iTunes to the G-drive.
Solution: I removed the virtual C-drive (ie. mapping of "C:" to the new folder) and instead in My Computer -> Manage -> Storage -> Disk Management, I assigned the C: drive letter to a drive partition I use for storing media (I plan to name it back else several programms will fail to store media correctly). I also moved the iTunes.exe installation file to that C: partition in case that helped. Installation (still told to be the G-drive) was now successful.
What I noticed is iTunes created the following path - C:\Program Files\JavaSoft\JRE\1.3.0_02\lib\ext - and dumped this file there: QTJava.zip Looks suspiciously like an install file for the bundled (and required) updated Quick Time, which it obviously requires to be dumped on a C-drive. Once installed I doubt that file will still be needed, so I'll delete it after I restart (it won't let me at the mo).
If you don't have extra partitions that you can assign C-drive to, then you could either try Adding (rather than changing) the C: drive letter to your current System disk. IN FACT I'M THINKING THAT'D BE THE BEST THING TO DO ANYWAY as then all programmes will use the correct system disk regardless of whether they think they should be using G: or C: (though I've not tried it, so can't be sure this works). Alternatively I reckon you could connect a USB stick and assign C-drive to that (if it isn't in fact automatically assigned it). Allow it to dump the QTJava.zip file on to it and once installed, you can remove the USB Stick - NB I'd suggest using the Safe Removal. (Well, might be worth restarting first in case it is referencing anything on it that isn't finished until restart.)
Hope this helps someone as was driving me potty coz I couldn't update my iTunes and thus couldn't sync my iPhone!

Hi AltafB,
For your situation, you can short the path for the source code. Or use a short path for build agent folder in your build definition. You can refer to the links below to solve your problem:
http://blogs.msdn.com/b/aaronhallberg/archive/2007/06/20/team-build-and-260-character-paths.aspx
https://social.msdn.microsoft.com/Forums/vstudio/en-US/1638a5f0-9321-4ff9-9ee7-6d347badb972/please-some-solution-to-the-specified-path-file-name-or-both-are-too-long?forum=tfsbuild
Besides, since you deploy Orchard to Azure, you can also publish it directly using publish profile in Visual Stduio or WebMatrix directly.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

MTU error (Path too long) with linux-3.6.2

I have a PC running 24/7, with an OpenVPN connection up all the time as well. I also have a (shared) ssh connection open, through said vpn. Every night an rsync job is ran, to backup some stuff over said VPN, through a shared ssh connection.
Starting a few days ago (Oct 17) I've had trouble with this, as in after rsync started, it would not be able to finish its job, getting "interrupted" (or, hanged) quite early on.
Looking in the journal, I can see error messages such as those (right after rsync starts, which happens at 02:23) :
Oct 17 02:23:05 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:06 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:06 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:06 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:06 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:07 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:09 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:13 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:22 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:23:39 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:24:13 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:25:20 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:27:21 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:29:21 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:31:21 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:33:22 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:35:22 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
Oct 17 02:37:22 arch.local openvpn@xxx[552]: read UDPv4 [EMSGSIZE Path-MTU=1460]: Message too long (code=90)
This eventually led to the ssh connection timing out, and the rsync job failing to complete.
Also, restarting OpenVPN seems to "fix" the issue, without the need to change any settings.
That's when I realized this started happening since upgrading the kernel to 3.6.2, so I then downgraded to 3.5.6 (Oct 19) and, since then, haven't had any issue.
So I'm thinking this is some kind of bug/regression in the 3.6 kernel, but I'm not really sure what to do now.
Note: I see 3.6.3 is out (and in testing), but only looked at the changelog so far (and didn't see anything that seem related to this issue?).

Thanks for your answers (and sorry about the delay).
I'm not sure how to read the error message actually, but I use default settings and `ip addr show` reports a MTU of 1500 indeed. Also, (on linux-3.6.2) I tried using OpenVPN's --mtu-test option to see what it would say (even though early on I never have a problem), and here it is:
NOTE: Empirical MTU test completed [Tried,Actual] local->remote=[1541,1541] remote->local=[1541,1541]
I'm nor really sure what it means, that I could (should?) use 1541 instead of 1500? And if so, how come it says I could go higher while I get errors with Path-MTU=1460 ? And actually, right before this result I do have a couple of those Path-MTU errors in the log, so I really don't know what to make of it, could it fail at 1460 but work higher? Does that even make sense?
I still don't know if it's really an MTU issue or not, since the kernel 3.5.6 isn't affected. Anyhow, I'll probably install 3.6.3 and see, hopefully it'll be back to normal.... if not I guess I'll have to try and set an MTU, though I'm not sure to what.
Also, would that require the OpenVPN server to have its MTU set that way as well (Since currently it also uses default settings, so MTU 1500) ?

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

Unexpected "result of the string concatenation is too long" error

Hello,
I am using Oracle Database 11.2.0.
When querying my database with a common table expression which concatenates VARCHAR2 strings, I receive an ORA-01489 error although I'm doubting that I am concatenating more than 4000 characters.
To be more precise, I have a table entity which basically stores XML elements including their parent element and their sibling position among its siblings. The CREATE statement for this table is listed below.
CREATE TABLE Entity (
ID NUMBER(10,0) NOT NULL PRIMARY KEY,
Name VARCHAR2(100) NOT NULL,
Parent NUMBER(10,0) REFERENCES Entity(ID),
Sibling_Pos NUMBER(2,0) DEFAULT 0
Now, I would like for all elements to be concatenated with their ancestor elements to a structure like this:
"/root_element(sibling_pos)/.../ancestor_element(sibling_pos)/parent_element(sibling_pos)/current_element(sibling_pos)"
(where root_element, ancestor_element, parent_element and current_element are just values from the name column of the entity table)
In order to achieve this, I use a common table expression which concatenates the name and sibling_pos values as shown below:
WITH entity_cte (lvl, id, path) AS (
SELECT 1 AS lvl, id, '/' || name || '(0' || sibling_pos || ')' AS path
FROM entity
WHERE parent IS NULL
UNION ALL (
SELECT lvl + 1 AS lvl, e.id, entity_cte.path || '/' || e.name || '(' || cast(e.sibling_pos AS VARCHAR2(2)) || ')' AS path
FROM entity_cte, entity e
WHERE entity_cte.id = e.parent
SELECT lvl, id, path
FROM entity_cte e
After inserting certain values, I get the ORA-01489 error, that the result of the string concatenation is too long. The maximum is referred to as being 4000 characters for VARCHAR2 in the oracle documentation and in various websites. Of course, it is clear to me by just using the common table expression like that, I could run into such an error. However, due to the structure of my XML documents, I doubted that the resulting strings would be more than 4000 characters long.
So, I rearranged my query in order to count the characters to be concatenated instead of actually concatenating them. The query is stated below as well, the changes are marked bold:
WITH entity_cte (lvl, id, path) AS (
SELECT 1 AS lvl, id, length('/' || name || '(0' || sibling_pos || ')') AS path
FROM entity
WHERE parent IS NULL
UNION ALL (
SELECT lvl + 1 AS lvl, e.id, entity_cte.path + length('/' || e.name || '(' || cast(e.sibling_pos AS VARCHAR2(2)) || ')') AS path
FROM entity_cte, entity e
WHERE entity_cte.id = e.parent
SELECT lvl, id, path
FROM entity_cte e
ORDER BY path DESC
The result of the query gives me a maximum length of 319 characters.
To be sure, I also checked the maximum level depth (indicated by the column named lvl in the common table expression), meaning the maximum number of elements in my path (the concatenated string). The result is 18. As I use VARCHAR2(100) for the name column and add 5 charcaters in each level, the maximum number of characters expected for 18 levels would be 1890.
So, now I wonder is the ORA-01489 maybe raised for another reason? Or is there something else I am missing?
Any help would be appreciated. Further suggestions to track down the error are more than welcome. Thanks in advance.

Thanks for the hint, BluShadow.
Still, I don't reach that limit of 1000 characters with my actual data (yet). I understand that if my data changes, I might run into that error with the given query. But I don't understand why this error is raised with the given data I have. The longest string in the column "name" is 32 characters long up to now. When I'm adding 5 characters on each level and I only have max 18 levels that should only result in max 2664 bytes.
@odie_63
The database characterset is: AL32UTF8. If I googled correctly, than it just confirms what BluShadow said, that one character is represented by max 4 byte.
Regarding the sample data, the XML document that I am inserting and which causes the error comprises 1058 nodes. That means I have 1058 entries in my entity table. I think it would be no sense posting all of it here, but is there a way that I can attach a text file containing an insert script to this post?
Some sample data from the entity table orderd by the length of the string in the name column are shown below.
"ID"     "NAME"     "TYPE"     "PARENT"     "SIBLING_POS"
90     "representedCustodianOrganization"     1     89     0
109     "serviceProviderOrganization"     1     108     0
58     "standardIndustryClassCode"     1     55     2
186     "standardIndustryClassCode"     1     173     7
150     "standardIndustryClassCode"     1     137     7
106     "dischargeDispositionCode"     1     99     4
35     "administrativeGenderCode"     1     29     3
932     "substanceAdministration"     1     931     0
950     "substanceAdministration"     1     949     0
1043     "representedOrganization"     1     1041     1
71     "representedOrganization"     1     61     6
137     "representedOrganization"     1     128     5
173     "representedOrganization"     1     163     6
504     "substanceAdministration"     1     503     0
223     "representedOrganization"     1     221     1
252     "representedOrganization"     1     250     1
272     "representedOrganization"     1     270     1
477     "substanceAdministration"     1     476     0
481     "manufacturedLabeledDrug"     1     480     0
207     "representedOrganization"     1     205     1
802     "specimenPlayingEntity"     1     801     0
830     "specimenPlayingEntity"     1     829     0
844     "specimenPlayingEntity"     1     843     0
858     "specimenPlayingEntity"     1     857     0
99     "encompassingEncounter"     1     98     0
788     "specimenPlayingEntity"     1     787     0
676     "specimenPlayingEntity"     1     675     0
704     "specimenPlayingEntity"     1     703     0
718     "specimenPlayingEntity"     1     717     0
746     "specimenPlayingEntity"     1     745     0
Any help or further suggestion are appreciated. Thank you.

Importing iTunes library from a Mac to PC--File name too long error.....

Hi...
Hope someone can help. Ive been forced to use a PC at work (Win7) and am trying to install my 84 gig library from my Macbook Pro to the PC. During the course of the import, i get an error stating that a file is too long, and then the whole process aborts....any suggestions?
thanks in advance!
yp

Log into the migrated account, find the content, choose Go to Folder from the Finder's Go menu, provide /Users/Shared/ as the path, drag it there, and access it from the new account.
(100256)

String literal too long error while invoking a package with clob variable

I have a package.One of the input variables of the procedure in packae is clob.
I want to invoke this package with a huge clob as input.
when i invoke this package like that i am getting following error
PLS-00172 string literal too long
can't we pass clob(huge clob) as input .is there any solution for that ?
Thanks
Pramod Garre

842802 wrote:
If insert this data into a table , from sql prompt still i get the same error.Do you mean SQL*Plus? Then there is buffer limitation and it is better to split literal into, let say 1000 character chunks:
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Mar 29 16:17:26 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
from dual
ERROR at line 6:
ORA-01489: result of string concatenation is too long
SQL> select to_clob('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA') ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
TO_CLOB('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
SQL> SY.

SP2-0027: Input is too long -error on pl/sql procedure

Hi,
We are on Oracle 11.2.0.2 on Solaris 10. I have a procedure call that errors out with this error:
SP2-0027: Input is too long (> 2499 characters) - line ignored
It is one single procedure but it takes too many long inputs in it. This giant procedure call -with some names changed - is as below - is there a way I can avoid this errro? I will be thankful for inputs on it.
SQL> exec func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF','co Reporting','NOT',func_j23k_TYPE_ACTION_ARRAY(func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Find in Report List'),LANG_TEXT_TYPE('en_CA', 'Find in Report List'),LANG_TEXT_TYPE('fr_CA', 'Chercher dans la liste des rapports'),LANG_TEXT_TYPE('es_US', 'Buscar en lista de informes')),'/Reporting/el/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open using Excel'),LANG_TEXT_TYPE('en_CA', 'Open using Excel'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format Excel'),LANG_TEXT_TYPE('es_US', 'Abrir usando Excel')),'/Reporting/el/xls/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in PDF'),LANG_TEXT_TYPE('en_CA', 'Open in PDF'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format PDF'),LANG_TEXT_TYPE('es_US', 'Abrir en PDF')),'/Reporting/el/pdf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in HTML'),LANG_TEXT_TYPE('en_CA', 'Open in HTML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format HTML'),LANG_TEXT_TYPE('es_US', 'Abrir en HTML')),'/Reporting/el/html/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in TXT'),LANG_TEXT_TYPE('en_CA', 'Open in TXT'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format TXT'),LANG_TEXT_TYPE('es_US', 'Abrir en TXT')),'/Reporting/el/txt/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in CSV'),LANG_TEXT_TYPE('en_CA', 'Open in CSV'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format CSV'),LANG_TEXT_TYPE('es_US', 'Abrir en CSV')),'/Reporting/el/csv/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in XML'),LANG_TEXT_TYPE('en_CA', 'Open in XML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format XML'),LANG_TEXT_TYPE('es_US', 'Abrir en XML')),'/Reporting/el/xml/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Download Data Extract File'),LANG_TEXT_TYPE('en_CA', 'Download Data Extract File'),LANG_TEXT_TYPE('fr_CA', 'TÃ©lÃ©charger le fichier d''extraction de donnÃ©es'),LANG_TEXT_TYPE('es_US', 'Descargar archivo de extracciÃ³n de datos')),'/Reporting/el/flf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL)), 'MC');
SP2-0027: Input is too long (> 2499 characters) - line ignoredThanks,
OrauserN

It is an sqlplus error..
Did you try this?
begin
func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF',
'co Reporting',
'NOT',
end;http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4789399600346029472

String Literal Too Long - error?

I'm using a CLOB datatype but via an ODBC connection I'm given an error when I insert a value larger than 4000 chars:
ODBC Error Code = S1000 (General error)
[Oracle][ODBC][Ora]ORA-01704: string literal too long.
SQL:
insert into TEST2
(ARTICLE,UUID)
values ('Very long string I wont repeat here!','1234')
DESCRIBE confirms that the datatype is CLOB and not VARCHAR2. Am I doing something wrong or is it a restriction in the ODBC driver? The version installed is 8.1.5.6. I can't install the very latest version because it comaplains that it needs a newer version of the Oracle Installer. Thanks.

Hi Justin,
Thanks for pointing me back to the other topic where I asked the question. I lost it under all of the new topics that had been posted! Andrew's reply is very helpful but assumes I have the data stored in a file, which I don't. I've replied hoping Andrew still has the patience to help! :-)

SP2-0027: Input is too long error during Apex 4.0 installation

I have come across an error while installing Apex 4.0.
The installation reached the point where it gave a SP2-0027 error
...PAGE 72: Workspace Schemas
...PAGE 73: &PRODUCT_NAME. Workspace Creation
...PAGE 74: Page Views By Day Report
...PAGE 75: Page Views by Application and Page
...PAGE 76: Hourly Usage
...PAGE 77: Usage by Application, for selected hour
...PAGE 78: Page Performance Dashboard
...PAGE 79: Database
SP2-0027: Input is too long (> 2499 characters) - line ignored
wwv_flow_api.create_report_region (
ERROR at line 16:
ORA-06550: line 16, column 1:
PLS-00703: multiple instances of named argument in list
ORA-06550: line 16, column 1:
PL/SQL: Statement ignored
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Following this, I looked up Apex help, and so checked dba_registry
C:\apex>C:\oraclexe\app\oracle\product\10.2.0\server\BIN\sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 13 15:40:05 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys as sysdba
Enter password:
Connected.
SQL> SELECT STATUS FROM DBA_REGISTRY
2 WHERE COMP_ID = 'APEX';
STATUS
LOADING
Please help
Edited by: user4477408 on Jul 19, 2010 3:35 PM
Edited by: user4477408 on Jul 26, 2010 11:29 AM

Did you keep any kind of external references to your pages/reports? From what it looks like, one of your report regions exceeds 2500 characters and APEX is having a hard time crunching it. See if you can find that page, then export that page, delete the region, and import the page on it's own later.
Not sure why it would be such a small area, though. I usually don't have any trouble until I hit 32K characters.

Restore-DfsrPreservedFiles "Path Too Long" Error

Similar Messages

Maybe you are looking for