Ora-06502: variable length too long on report query xml schema download

on shared components/report queries/edit report query/
and downloading my queries in xml schema format (radio button).
Get
ORA-06502: PL/SQL: numeric or value error: raw variable length too long
when i click the download button.
EDIT:
i want to add that i recently changed several columns in the database from 150 to 3000 chars long.
Edited by: Manny Rodriguez on Oct 11, 2011 7:19 AM

"4000 bytes is the ultimate maximum. you can say 4000 *characters* , but it'll always be limited to 4000 *bytes* . "
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:1224836384599#201073000346459201\
"The maximum length of the column is determined by the national character set definition. Width specifications of character data type NVARCHAR2 refer to the number of characters. The maximum column size allowed is 4000 bytes."
http://docs.oracle.com/cd/E11882_01/server.112/e26088/sql_elements001.htm#SQLRF50976
By the way, you're treating your numbers as STRINGS, remove the quotes around your zero's.

Similar Messages

ORA-06502: PL/SQL: numeric or value error: raw variable length too long

Hi All,
Oracle 9.2.0.1.0 and Oracle 10g.
I the following procedure:
CREATE OR REPLACE TYPE Resource_TT AS TABLE OF RAW(16)
CREATE OR REPLACE PROCEDURE GET_ROLEMAPPING_Temp
RoleIds IN NVARCHAR2 DEFAULT NULL ,
Application IN NVARCHAR2 DEFAULT NULL ,
MappingExixts OUT NVARCHAR2
AS
     v_Application NVARCHAR2(150) := Application;
     resource_list CONSTANT Resource_TT := Resource_TT(RoleIds);
     v_temp NUMBER(1, 0) := 0;
BEGIN
     SELECT 1 INTO v_temp
FROM DUAL
WHERE EXISTS ( SELECT SecurityGroupId
FROM SKESGResourceMapping
WHERE APPLICATION = v_Application
AND RoleId IN
                                                  select column_value
                                                  from table(resource_list)
EXCEPTION
WHEN NO_DATA_FOUND THEN
MappingExixts := 'NO';
END;
IF v_temp = 1 THEN
MappingExixts := 'YES';
     END IF;
END;
while calling the procedure from sql*plus, the calling block is :
variable MappingExixts nvarchar2(100);
execute Get_RoleMapping_Temp('2f90e7969e0a9045aeb5b5ed7b3da9d6,363aef470e10094281e5040627e3b6f8', 'repo1', :MappingExixts);
print MappingExixts;
It is throwing an error saying:
ORA-06502: PL/SQL: numeric or value error: raw variable length too long
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8
Thanks for your valuable time and suggestions

Hi Binoy,
Thanks for your quick response, I increased its size to 200, but I am getting the following error
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8

ORA-09100 specified length too long for its datatype with Usage Tracking.

Hello Everyone,
I'm getting an (ORA-09100 specified length too long for its datatype) (a sample error is provided below) when viewing the "Long-Running Queries" from the default Usage Tracking Dashboard. I've isolated the problem to the logical column "Logical SQL" corresponding to the physical column "QUERY_TEXT" in the table S_NQ_ACCT. Everything else is working correctly. The logical column "Logical SQL" is configured as a VARCHAR of length 1024 and the physical column "QUERY_TEXT" is configured as a VARCHAR2 of length 1024 bytes in an Oracle 11g database. Both are the default configurations and were not changed.
In the the table S_NQ_ACCT we do have record entries in the field "QUERY_TEXT" that are of length 1024 characters. I've tried various configuration such as increasing the the number of bytes or removing any special character but without any sucess. Currently, my only possible workaround is reducing the "Query_Text" data entries to roughly 700 characters. This makes the error go away. Additional point my character set to WE8ISO8859P15.
- Any suggestions?
- Has anyone else ever had this problem?
- Is this potentially an issue with the ODBC drive? If so, why would ODBC not truncate the field length?
- What is the maximum length supported by BI, ODBC?
Thanks in advance for everyones help.
Regards,
FBELL
*******************************Error Message**************************************************
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 910, message: ORA-00910: specified length too long for its datatype at OCI call OCIStmtExecute: select distinct T38187.QUERY_TEXT as c1 from S_NQ_ACCT T38187 order by c1. [nQSError: 17011] SQL statement execution failed. (HY000)
SQL Issued: SELECT Topic."Logical SQL" saw_0 FROM "Usage Tracking" ORDER BY saw_0
*******************************************************************************************

I beleieve I have found the issue for at least one report.
We have views in our production environment that call materialized views on another database via db link. They are generated nightly to reduce load for day-old reporting purposes on the Production server.
I have found that the report in question uses a view with PRODUCT_DESCRIPTION. In the remote database, this is a VARCHAR2(1995 Bytes) column. However, when we create a view in our Production environment that simply calls this materialized view, it moves the length to VARCHAR2(4000).
The oddest thing is that the longest string stored in the MV for that column is 71 characters long.
I may be missing something here.... But the view that Discoverer created on the APPS side also has a column length for the PRODUCT_DESCRIPTION column of VARCHAR2(4000) and running the report manually returns results less than that - is this a possible bug?

Report query XML schema error - Apex Listener 2

I built a simple query: select * from emp in (Shared components > Report Query)
When I try to download XML schema for this query (Source Query section) resulting xsd file contains this text: String index out of range: -1
Shared Apex hosting: 4.2.2.0.0.11
Print server: Apex Listener 2.0.1

Hey Saymonc, we're you ever able to find the cause of this issue? I'm having this happen to me as well. When I begin using the Report Query functionality, the schema downloaded just fine. I made an update to a query and began receiving this error. Now I get the error for ALL of my report queries. I tried removing them and recreating them, and I continue to receive this error in my schema file, no matter how simple the query. The data will download just fine, and using the Test Report button works as well.
Thanks,
Chris

Using clobs and ORA-01704: string literal too long

Hi,
I am attempting to add oracle support to an existing J2ee application. The issue I am facing is the use of CLOB datatypes and the 4k string literal limitation that Oracle has.
I have dowloaded the 10.2.0.3 thin driver and am connected to a 9i release 2 database. When I execute a statement such as the following (say the table has one varchar2 field and two clob fields
Insert into my_table VALUES ('hi','something','pretend this string is 5000 characters')
I still receive the error
java.sql.SQLException: ORA-01704: string literal too long
I have read that the version 10 drivers were supposed to address this limitation. Is there something I am missing or must I change my home grown database layer to use bind variables or clob manipulation in a separate update/insert statement.? I am trying to avoid this situation since the database layer works fine for the situation of MSSQL and text fields which have no such limitation.
Any advice you have here is greatly appreciated.
Thanks,
Joe

Hi,
I am attempting to add oracle support to an existing J2ee application. The issue I am facing is the use of CLOB datatypes and the 4k string literal limitation that Oracle has.
I have dowloaded the 10.2.0.3 thin driver and am connected to a 9i release 2 database. When I execute a statement such as the following (say the table has one varchar2 field and two clob fields
Insert into my_table VALUES ('hi','something','pretend this string is 5000 characters')
I still receive the error
java.sql.SQLException: ORA-01704: string literal too long
I have read that the version 10 drivers were supposed to address this limitation. Is there something I am missing or must I change my home grown database layer to use bind variables or clob manipulation in a separate update/insert statement.? I am trying to avoid this situation since the database layer works fine for the situation of MSSQL and text fields which have no such limitation.
Any advice you have here is greatly appreciated.
Thanks,
Joe

PL-SQL-ORA-01704 - String literal too long

Hello guyz;
I am trying to store a value of over 4000 character long in a CLOB column and I got the error message that says "PL-SQL-ORA-01704 - String literal too long".
What can I do to overcome this challenge?
Thanking you for your usual support.

sb92075 wrote:
Problem Exists Between Keyboard And Chair
We can't say what you are doing wrong since we don't know specifically what you actually do.Okay let me put it down this way.
I have an application using SQL Server as d backend engine & now, the user wants to migrate to Oracle. I now wrote a mini-program to create a schema/user in oracle with the schema/database (being used by the app) from SQL server. I verified the structure very well & every is just fine. Now, data migration (from SQL Server to Oracle).
I was able to move most tables data successfully without issue until I attempted to load a table which has a column (in SQL defined as text with over 4000 (var)chars/CLOB in Oracle). On moving a particular row to oracle db (after few rows have already been INSERTed into this particular table x), I got that err msg.
After battling with that for a while, I concluded to make d (DataMigrator) app take just d first 4000 string - only if the value in that field value length > 4000. This worked perfectly without issue but you know the implication - Data lost.
Do I need to switch something on/off in Oracle that expands the CLOB default maximum field size? Because I foresee this happening as soon as the application (that would now sit on Oracle) is now in use.
If you still don't understand this, I don't know how beta 2 explain this!
Edited by: aweklin on Mar 17, 2013 8:25 AM
Edited by: aweklin on Mar 17, 2013 8:25 AM
Edited by: aweklin on Mar 17, 2013 8:27 AM
Edited by: aweklin on Mar 17, 2013 8:27 AM

"ORA-01704: string literal too long" in Oracle 10g

I would like to explain my problem with an example, let's create the following table:
CREATE TABLE longtest
(text LONG);
I have to insert lots of data into this table and when I run this command:
INSERT INTO LONGTEST VALUES ('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
..................more than 4000 characters..................
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa');
I get the following error:
ORA-01704: string literal too long
To workaround this, I used bind variables, like this:
BEGIN
EXECUTE IMMEDIATE 'INSERT INTO LONGTEST VALUES (:a) '
using
'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
..............(repeat more than 32768 characters)..............
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa';
COMMIT;
END;
This worked fine with Oracle 9.2.0.4 but when I do the same thing
in Oracle 10.2.0.2 there is a 32768 characters limit.
I am planning to upgrade the database but I need a workaround for
this, anyone knows why Oracle behaves differently in 10g??

So, I wonder if anyone can explain why the following code works fine in Oracle 9.2.0.4 but not in Oracle 10.2.0.2:
CREATE TABLE longtest
(text LONG);
BEGIN
EXECUTE IMMEDIATE 'INSERT INTO LONGTEST VALUES (:a) '
using
'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
..............(repeat more than 32768 characters)..............
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa';
COMMIT;
END;
Regards,
Cassiano

Limitation for CLOB columns? - ORA-01704: string literal too long

Hello!
I'm trying to update a CLOB column with more than 35000 characteres, but I get "ORA-01704: string literal too long".
The code:
declare
l_clob clob;
begin
update test set test = empty_clob()
WHERE ID = 1
returning test into l_clob;
dbms_lob.write( l_clob, length('A...here 35000xA...A'), 1,'A...here 35000xA...A');
end;
Is there any limitation for CLOB columns?
Thanks for help.
Daniel

user605489 wrote:
32768 characteres :)Actually it's 1 character less than 32K...
*32767*
SQL> declare
2 v_vc varchar2(32768);
3 begin
4 null;
5 end;
6 /
v_vc varchar2(32768);
ERROR at line 2:
ORA-06550: line 2, column 17:
PLS-00215: String length constraints must be in range (1 .. 32767)
SQL>I guess it comes from a legacy thing where signed words (2 bytes) are/were used to represent a value. As the most significant bit of the word is used to represent the sign of the number the range goes from -32768 to 32767.

SQL Error: ORA-01704: string literal too long

select * from table(fn_split('some 10000 characters with comma separation .........................'))
Error report:
SQL Error: ORA-01704: string literal too long
01704. 00000 - "string literal too long"
*Cause: The string literal is longer than 4000 characters.
*Action: Use a string literal of at most 4000 characters.
how to pass my 10k record string

933663 wrote:
The string is through a user interface.So, that interface is using what datatype for the string? What language is the interface written in?
insert into table
select * from table(fn_split('2,4,2,5,7'));Do you understand what a string literal is? You cannot provide a varchar2 string that exceeds 4000 bytes from within SQL. Fact. It just cannot be done.
If you are passing the string from a user interface using a datatype that supports more than 4000 bytes, and you pass it directly to PL/SQL code by calling the function or procedure directly (not using SQL) then you can use up to 32767 bytes for your VARCHAR2.
The code you've posted (which happens to be some of my own code posted years ago on these forums) takes a VARCHAR2 as an input. You would have to change that to accept a CLOB datatype and work on the CLOB instead. However, you still wouldn't be able to pass in a string literal of more than 4000 bytes from SQL for it.
Looking at your other thread: Seperate the string value
... it looks like the 'user' is trying to pass in a table definition. What is it your application is trying to do? Surely you are not trying to create a table at run time?
So explain, what is the business issue you are trying to solve? We may be able to provide a better way of doing it.

[ORA-01704: string literal too long] in a long xquery

I get an error when using queries with xmlquery.
If the quoted string part is longest than 4000 chr then I get
ORA-01704: string literal too long.
Example...
select xmlquery(
' <Root >
{for $xxx in ora:view("ttttttt")
let $nnn := $xxx/ROW/nnn/number()
[total chr>4000] '
RETURNING CONTENT)
from dual
Is it really not possible to write Oracle xmlqueries longest than 4000chr or there's a workaround for it?

I got similary problem using the OCCI to insert record in my table.
I have a BLOB field in my table and whenever I quote an HEX string that is bigger than 4000 chars I get the error: ORA-01704: string literal too long
To sort that problem I have to pass to the prepared SQL statement, but now I got a new problem for which I do not have solution.
I write here the piece of C++ code to insert and the error I get hoping somebody can help me.
I have problem to write into a Blob object.
I get the error: ORA-22275: Invalid LOB Locator Specified.
The error occurs when I try to write into the blob variable:
blobField.writeChunk(....
Routine:
void insert2 (void) throw (SQLException)
cout << "=== Prepare Statement ===" << endl;
Statement* stmtIns = occiConn->createStatement("insert into test_tab values (:1,:2,:3,:4,:5)");
cout << "=== Prepare the Blob data ===" << endl;
// Prepare all Blobs in an array of char.
char* data[5];
ub2 dataLen[5];
int i;
for (i = 0; i < 5; i++)
data[i] = new char[16364];
memset(data, 65+i, 16364);
dataLen[i] = 16364;
cout << "=== Assign the other fields ===" << endl;
stmtIns->setInt(1, i + 10);
stmtIns->setInt(2, i + 1000);
stmtIns->setInt(3, i + 10000);
stmtIns->setInt(4, i + 20);
// Assign the blob field
Blob blobField(occiConn);
blobField.setEmpty();
cout << "=== Opening the blob field in read/write mode ===" << endl;
blobField.open(OCCI_LOB_READWRITE);
cout << "=== Writing data into the blob ===" << endl;
blobField.writeChunk(dataLen[0], reinterpret_cast<unsigned char*>(data[0]), dataLen[0], 1);
blobField.close();
cout << "=== Done ===" << endl;
stmtIns->setBlob(5, blobField);
cout << "=== Execute the iteration ===" << endl;
stmtIns->executeUpdate();
for (i = 0; i < 5; i++)
delete [] data[i];
stmtIns->executeUpdate("COMMIT");
occiConn->terminateStatement(stmtIns);

ORA-01704: string literal too long (URGENT)

Folks,
I get error - ORA-01704: string literal too long,
when trying to insert a value >4k into the SDIDOC column of the table below:
CREATE TABLE "B1"."SDI_XML_TAB"
( "SDIID" VARCHAR2(60 BYTE) NOT NULL ENABLE,
"SDIDOC" "SYS"."XMLTYPE" ,
CONSTRAINT "SDI_XML_TAB_PK" PRIMARY KEY ("SDIID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "B1SYSTEM" ENABLE
) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "B1SYSTEM"
XMLTYPE COLUMN "SDIDOC" STORE AS CLOB (
TABLESPACE "B1SYSTEM" ENABLE STORAGE IN ROW CHUNK 16384 PCTVERSION 10
NOCACHE LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)) ;
The SQL I used using OCI was:
"INSERT INTO SDI_XML_TAB(SDIID,SDIDOC) VALUES('ABC','clobVal')"
What am I doing wrong?
P.S. I also used the following and it gives the same error:
"INSERT INTO SDI_XML_TAB(SDIID,SDIDOC) VALUES('ABC',XMLType('clobVal'))"
Thanks,
Arthur
Message was edited by:
ArthurJohnson

Check this cool-bi.com

ORA-01704:String literal too long with update of more than 4000 chars

Hi,
I want to update a table column in Oracle Database(version 10) with more than 4000 chars.
The datatype of the table column is NCLOB.
I want to achieve this with one single line of update query as below,
update mytable set MY_DESCRIPTION = 'longdesc' where ID = '111' ;
But there's a problem, if the 'longdesc' is more than 4000 chars, it gives the error , "ORA-01704:String literal too long"
How can I achieve this in sql developer ?
I dont want to do this using stored procedures, I want to do this update using only sql statement.
Please help.
thanks,
sudhakar

Hello Sudhakar,
I am afraid, this will never work by SQL.
Just because an SQL-Statement must not contain a string literal over 4,000 characters (or did that change lately?).
Maybe you can bypass the limit with PL/SQL ... but you will certainly run into the 32K limit sooner or later
regards
Peter

ORA-00972: identifier is too long

Hi All,
I get the error ORA-00972: identifier is too long during installation of NW2004s SR2 Java system with DI. This error is seen on the step Perform post load activites. i have made the changes as suggested by SAP note: 314671. But the error still persists. Can anyone suggest what further more should be done here?
Oracle is unable to delete : OPS$<14 letter host name>\SAPSERVICESR3 and hence the error.
the output from ora_sql_results.log
=============================================================
2008-04-28, 19:04:56 SAPINST ORACLE start logging for
@@SAPDBA_ADDITIONAL.SQL
exit;
Output of SQL executing program:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Apr 28 19:04:56 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Connected.
old   3:   :sSchemaUser := upper('&&1');
new   3:   :sSchemaUser := upper('SAPSR3DB');
old 19:   if upper('&&2') = 'NT' then
new 19:   if upper('NT') = 'NT' then
old 21:     :sDomain := upper('&&3');
new 21:     :sDomain := upper('[14 letter Host Name]\SIDadm');
old 32:   elsif upper('&&2') = 'UNIX' then
new 32:   elsif upper('NT') = 'UNIX' then
old 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('&&2'));
new 37:     RAISE_APPLICATION_ERROR(-20004,'Invalid OS, must be "NT" or "UNIX": ' || upper('NT'));
using following Parameters:
. Schema User:                  SAPSR3DB
. Parametervalue os_authent_prefix:   OPS$
. OPS$SIDADM:                      OPS$[14 letter Host Name]\SIDADM
. SAP SID:                      SR3
. DB SID:                      SID
. R/3 Service User:                 OPS$[14 letter Host Name]\SAPSERVICESR3
. Computer or Domain:                 [14 letter Host Name]\SIDADM
old 119:   if upper('&&4') = 'SYN' then
new 119:   if upper('SYN') = 'SYN' then
old 137:   if upper('&&4') = 'SYN' then
new 137:   if upper('SYN') = 'SYN' then
create synonym: SAP_SDBAH SAPSR3DB.SDBAH
create synonym: SAP_SDBAH SAPSR3DB.SDBAD
unable to delete user: OPS$[14 letter Host Name]\SAPSERVICESR3
begin
ERROR at line 1:
ORA-00972: identifier is too long
ORA-06512: at line 46
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SAPINST: End of output of SQL executing program C:\oracle\product\10.2.0\db_1/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2008-04-28, 19:04:56 SAPINST ORACLE stop logging
Thanks in advance,
Arun E V

Hi Markus/Stefan,
Thanks for the quick answer. I know i am using a unsupported version, but that should not be a problem here. Though i have not run the installer from the script, still the DB is a successful installation and i have used it like this a few times.
Stefan, I have seen the note and made the required modification but still the issue persists. Is there anything more that i need to do apart from what is mentioned in the note?
The trouble is we are not in a position to change the host name as suggested and would prefer to continue with the same name.
Thanks,
Arun E V

Error ORA-01467: sort key too long

Hi. I have just come across the error ORA-01467: sort key too long .
In the Oracle documentation, the 2 line
description of this error basically says that there may be too many columns
or group functions in the query, so I need to reduce the number of columns
in the query.
Here's the problem. The documentation does not say how many the limit is.
The query is quite complex, I suppose, but I don't see why it should be a
problem. In a nutshell, the main table has 3 text fields (which are the
index) and 154 floats. The query joins one of the text fields to another
table to get a lookup value and selects this out, along with the other two
text fields and the SUM of the numeric fields. The query groups by the two
text fields and the lookup.
I guess I saw this when I was using MS SQL Server 6.5 and tried to sum more
than 125 columns, but that went away in SQL Server 7. I am using Oracle 8
at this point but need to support Oracle 7, too.
I guess what I am looking for (at least) is the maximum number of columns
that can be in a grouping/summing query. I'd also like to know if this can
be worked around by changing a setting on the server, something to set the
maximum number of sums to 1000, perhaps? I am fine with working around this
in my software if I need to, as I have done previously (I took the first 125
sums into a temp table, then the next 125, etc. and joined the resulting
tables to get my results), but would really like to get a workaround that
was server-based, if possible.
Thanks for your help!
null

Hi. I have just come across the error ORA-01467: sort key too long .
In the Oracle documentation, the 2 line
description of this error basically says that there may be too many columns
or group functions in the query, so I need to reduce the number of columns
in the query.
Here's the problem. The documentation does not say how many the limit is.
The query is quite complex, I suppose, but I don't see why it should be a
problem. In a nutshell, the main table has 3 text fields (which are the
index) and 154 floats. The query joins one of the text fields to another
table to get a lookup value and selects this out, along with the other two
text fields and the SUM of the numeric fields. The query groups by the two
text fields and the lookup.
I guess I saw this when I was using MS SQL Server 6.5 and tried to sum more
than 125 columns, but that went away in SQL Server 7. I am using Oracle 8
at this point but need to support Oracle 7, too.
I guess what I am looking for (at least) is the maximum number of columns
that can be in a grouping/summing query. I'd also like to know if this can
be worked around by changing a setting on the server, something to set the
maximum number of sums to 1000, perhaps? I am fine with working around this
in my software if I need to, as I have done previously (I took the first 125
sums into a temp table, then the next 125, etc. and joined the resulting
tables to get my results), but would really like to get a workaround that
was server-based, if possible.
Thanks for your help!
null

ORA-20001: FLEX-VALUE TOO LONG

I am getting ORA-20001: FLEX-VALUE TOO LONG error message while updating
payroll_id using hr_assignment_api.update_emp_asg_criteria package.
Please let me know if you have any Idea.
thank you,
Ravi kanth

I am getting ORA-20001: FLEX-VALUE TOO LONG error message while updating
payroll_id using hr_assignment_api.update_emp_asg_criteria package.
Please let me know if you have any Idea.
thank you,
Ravi kanth

Ora-06502: variable length too long on report query xml schema download

Similar Messages

Maybe you are looking for