Value param too long - error

When I enter a PLSQL anonymous block in the page process region and try to apply the changes, I get the following error message -
" Your browser sent a request that this server could not understand.
mod_plsql: /pls/caps/wwv_flow.accept HTTP-400 Value param too long. Length is 44169. Upper limit is 32000"
Is it because the the size of the plsql block entered too big? If so what is the work around? I can not create a stored procedure for this because the block uses html form element collections (HTMLDB_APPLICATION.G_F01, etc).
My HTMLDB version is 1.5.1.00.12
Please help me solve this problem.
thanks,
Aravind R
Message was edited by:
user446863

I have a peculiar problem here. I have created the stored procedure and calling the stored proc from the anonymous block. Still I get the same error I mentioned above.
I get this error even when the process region contains a dummy block like -
declare
begin
null;
end;
Even more funnier - I am not able to delete or do any other changes in that after submit process. I have created a new process and added the block to that process. Now when I try delete the process that is giving me the problem, I get the same error message and nto able to do any operation on the process.
Message was edited by:
user446863

Similar Messages

Value param too long. Upper limit is 32000

Is there a character limit to An html portlet? Say some where around an Upper limit of 32000.

Taken a sentence from Hans Forbrich :
"Are you sure this is not related to a specific technology for which a separate forum exists? (Y/N)"
And :
Community Feedback and Suggestions
Use this forum for feedback about OTN programs, Web site content, and systems - product-related questions cannot be answered here.
Nicolas.

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

SagePay Gateway Response: 3145 : The BillingCountry value is too long.

I know that with SagePage the BillingState has to be just a two letter abbreviation for US states (eg FL rather than Florida). However, overnight we had new failure saying BillingCountry value is too long.
Anyone else come across this error before?

Okay got to the bottom of this. SagePay says the BillingCountry was "-- Select Country --"
So customer must have forgotten to choose one from the drop down list !
I guess we should make this drop down selection a required field!
Thanks
James

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

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

Sort key too long error depends on values supplied to query

Please have a look at this query (Just given for guessing complications).
This query works and gives output for pro_id=1 and other few values.
But it fails for value 2.
SELECT *
FROM common_list_view_test
WHERE che_id != 14
AND(use_id = 299 OR iss_rec = 299 OR che_id IN
(SELECT a.m_che_id
   FROM m_chk_pt a,    m_role_chk_pt b,    m_user c
   WHERE a.m_che_id = b.m_che_id
   AND b.m_rol_id = c.m_rol_id
   AND c.m_use_id = 299))
AND pro_id = 2
ORDER BY iss_dat,
issue_stringFor pro_id = 2 it gives error:
ORA-01467: sort key too long
What do we mean by sort key?
Is it depends on supplied information and the records to be fetched.
If the query is going to fetch a lot of records then do this error occur?
How to avoid this error and make the query to work got pro_id=2.
-Sameer

It is also not working for:
SELECT COUNT(*)
FROM common_list_view_test
WHERE pro_id = 2Please tell me what i have to do?
I can't rewrite common_list_view_test as i do not have enough priviledged to change its code, but this view is a lot complicated.
But then why it works for one value and not for another one?
Please help.
-Sameer

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! :-)

PLS-00114: identifier too long error (Oracle 10g)

Hi All,
Hi All,
I have created procedure called "p_procedure_for_cals_annual_sal_oracle_proprierty.lib".
It is must to give the procedure name as mentioned.(>30 Chars)
But while executing I am getting following error.
SQL> exec p_procedure_for_cals_annual_sal_oracle_proprierty.lib
BEGIN p_procedure_for_cals_annual_sal_oracle_proprierty; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00114: identifier 'p_procedure_for_cals_annual_sal_' too long.Please give me suggestion to execute this procedure.
Thank you.
Edited by: user636482 on Mar 22, 2009 9:57 PM

I think you've mistaken EXEC(UTE) with START or @
Execute
Executes a single PL/SQL statement. The EXECUTE command is often useful when you want to execute a PL/SQL statement that references a stored procedure.
Start
STA[RT] {url | file_name[.ext] } [arg...]
Runs the SQL*Plus statements in the specified script. The script can be called from the local file system or from a web server. Only the url form is supported in iSQL*Plus. You can pass values to script variables in the usual way.
Here's a copy/paste of a test:
the file (some_long_name_with_many_characters.sql)
set serverout on
Begin
dbms_output.put_line('A line of text...');
End;
/The SQL*Plus session:
SQL> exec some_long_name_with_many_characters.sql
BEGIN some_long_name_with_many_characters.sql; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00114: identifier 'SOME_LONG_NAME_WITH_MANY_CHARA' too long
ORA-06550: line 1, column 43:
PLS-00103: Encountered the symbol "SQL" when expecting one of the following:
<an identifier> <a double-quoted delimited-identifier> delete
exists prior <a single-quoted SQL string>
The symbol "<an identifier> was inserted before "S
SQL> @some_long_name_with_many_characters.sql
A line of text...
PL/SQL procedure successfully completed.
SQL> sta some_long_name_with_many_characters.sql
A line of text...
PL/SQL procedure successfully completed.
SQL>

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.

Create WorkInstruction Webservice call; Url is too long Error.

Hi,
I am trying to create a Work Instruction using workflow, the url is very long & the call is failing with error Url is too long (333 > 256)
If I create WI manually from Work Instruction Maintenance with the same url, its working fine.
Response Content:
- <ns2:StandardMessageFault xmlns="http://sap.com/xi/SAPGlobal/GDT" xmlns:ns2="http://sap.com/xi/ME">
<ns2:ErrorCode>12032</ns2:ErrorCode>
<ns2:ErrorMessage>Url is too long (333 > 256)</ns2:ErrorMessage>
</ns2:StandardMessageFault>
Has any one seen this? please advise.
ME Version: 6.0.4.1 Counter 10
Br,
Shridhar..

Hello Sergiy,
I tried it on ME 6.1.4.9 Counter 201403061828 and still get the same message Url is too long (328 > 256) (Message 12032)
I understand that MEINT to ME 6.1 integration is through Java API calls, What should be set in 'Partner Service Transaction' for Z_DOCMAS04.?
I could not find the value of it so i referred ME 6.0 and set Visiprise/ERPShopFloorIntegration/frame/workflow/MEWebService/ serviceUrl=manufacturing-services/WorkInstructionService;timeOutInSec=60 and tested.
Let me know if this is correct or we should be using java class, like java:com.sap.me.integration.ERPItemHandler.
Whats the name?. I tried with ERPWorkInstructionHandler and it failed.
Please advise.
Thanks,

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

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.

Value param too long - error

Similar Messages

Maybe you are looking for