ORA-31044: Top-level prefix length exceeds maximum

Hi,
I am trying to migrate the cube and associated view created by view generator from one environment to another environment.
The cube is migraed through XML and it is working.
But when we compile the view created in one environment in the target environemn after cube migration we get and error as - "ORA-31044: Top-level prefix length exceeds maximum".
What is the resolution for this?
Regards,
Gurudatta

Not sure what is happening between production and development environments, if it worked in dev it should work in production assuming no other changes were made to the data model. Data volumes should not be an issue. When you are testing the view are you using a WHERE clause to limit the number of rows returned? Try just returning the top level for each dimension, the 'All' dimension member as this will return just one row (or one row for each year if you have a time dimension with year as the top level).
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Similar Messages

Column name length exceeds maximum allowed

Hello,
I get this error when am trying to create a table. ERROR: Column name length exceeds maximum allowed length(30).
Is it able to extend this length to be more than 30 ? By the way I am using Oracle 11g
Regards,
Moussa El Tayeb
about.me/MoussaEltayeb

Hello,
also Oracle has some limits. For more Information see the logical limits
http://docs.oracle.com/cd/E14072_01/server.112/e10820/limits.htm
regards
Peter

"ORA-01144: File size (7680000 blocks) exceeds maximum of 4194303 blocks.

Hi Team,
While increasing the tablespace i am getting below error. How to handle this any one please suggest.
SQL> set lin 300
SQL> col TABLESPACE_NAME for a25
SQL> col FILE_NAME for a65
SQL> select TABLESPACE_NAME,FILE_ID,FILE_NAME,AUTOEXTENSIBLE,sum(BYTES/1024/1024) MB
2 from dba_data_files where TABLESPACE_NAME='SYSAUX' group by TABLESPACE_NAME,FILE_ID,FILE_NAME,AUTOEXTENSIBLE order by sum(BYTES/1024/1024) DESC,file_name;
TABLESPACE_NAME FILE_ID FILE_NAME AUT MB
SYSAUX 3 /ora2/oradata/dbname/sysaux_01.dbf NO 300
SQL> Alter database datafile 3 RESIZE 60000M;
Alter database datafile 3 RESIZE 60000M
ERROR at line 1:
ORA-01144: File size (7680000 blocks) exceeds maximum of 4194303 blocks
Regards,

941829 wrote:
Hi Team,
While increasing the tablespace i am getting below error. How to handle this any one please suggest.
SQL> set lin 300
SQL> col TABLESPACE_NAME for a25
SQL> col FILE_NAME for a65
SQL> select TABLESPACE_NAME,FILE_ID,FILE_NAME,AUTOEXTENSIBLE,sum(BYTES/1024/1024) MB
2 from dba_data_files where TABLESPACE_NAME='SYSAUX' group by TABLESPACE_NAME,FILE_ID,FILE_NAME,AUTOEXTENSIBLE order by sum(BYTES/1024/1024) DESC,file_name;
TABLESPACE_NAME FILE_ID FILE_NAME AUT MB
SYSAUX 3 /ora2/oradata/dbname/sysaux_01.dbf NO 300
SQL> Alter database datafile 3 RESIZE 60000M;
Alter database datafile 3 RESIZE 60000M
ERROR at line 1:
ORA-01144: File size (7680000 blocks) exceeds maximum of 4194303 blocks
Regards,You must know that its really important to mention your db version and other details so that we can answer in a more proper manner. Since you haven't mentioned your db size and block size so here is a generic reply. If you are using 8kb Blocksize,you should be able to go till 32gb of one file(8192*4194303/1024/1024=>32G). So your solution would be to either go for a different file or use Big File(if you are on 10g and above) .
HTH
Aman....

ORA-01144: File size (4194304 blocks) exceeds maximum of 4194303 blocks

Hello all,
Wen i try to add new datafile(32GB) to tablespace i found the below error. I have space available in my disk, why i am not able to add new datafile to tablespace?
ERROR at line 1:
ORA-01144: File size (4194304 blocks) exceeds maximum of 4194303 blocks
here is my db_block_size information:
NAME TYPE VALUE
db_block_size integer 8192
How can i add new datafile with out any issues.
Regards,
RHK

Thanks,
I minimise the size, now i am able to add new datafile.
From long time back i am getting below error,
ORA-1653: unable to extend table PQB_ADMIN.RPT_TR by 128 in tablespace USERS
ORA-1653: unable to extend table PQB_ADMIN.RPT_TR by 8192 in tablespace USERS
to avoid this error i added new datafile. Now the data will sync automatically? (it may be nearly 2 months data)
Regards,
RHK

Error : Summary String length exceeds maximum

I just got an error while trying to Update a User on my IDM instance.
com.waveset.util.InternalError : Summary String length (3003) exceeds maximum (2048)
I already checked this forum for similar issues, and I found a couple of threads. However, for some reason, I was unable to VIEW those threads (something about not having the rights/access to read those threads)
So, I am posting my issue here.
Any help will be greatly appreciated

Roman,
if you are using NETBEANS, this is what you do :
(a) right-click on the name of your instance (in the Projects Tab)
(b) select IDM
(c) then select "Download Objects"
(d) From the list that appears, choose "Common Configuration Object Types"
(e) Next, choose "*Repository Configuration"*
Somewhere in this file, there is a clause which states : *"Maximum Summary = '2048'*
Change this value to something higher (but, *NOT* too high !)
This should solve your problem

ORA-30951: Element or attribute at Xpath /AC//Doc[@] exceeds maximum length

Hi All,
I am trying to load the XML Files into a Table using the SQL Loader and i am getting the Error
Record 1: Rejected - Error on table COMMONASSETCATALOG.
ORA-30951: Element or attribute at Xpath /AC/T[1]/T[1]/T[1]/T[1]/T[1]/Doc[@] exceeds maximum length
The <Doc> Element which is child of the <T> contains an XML Schema inside it..
The Doc Element is declared in Schema as
<xs:complexType name="AsDocType">
          <xs:annotation>
               <xs:documentation>A (Doc)ument, a container for any type of file</xs:documentation>
          </xs:annotation>
          <xs:sequence minOccurs="0" maxOccurs="unbounded">
               <xs:any namespace="##any" processContents="lax"/>
          </xs:sequence>
          <xs:attributeGroup ref="AsDocAtts"/>
     </xs:complexType>
The Size of the XML Content that <Doc> Node has is around 34Kb.
Could you pls let me know how to resolve this..
Thanks
Sateesh

Hi All,
I am trying to load the XML Files into a Table using the SQL Loader and i am getting the Error
Record 1: Rejected - Error on table COMMONASSETCATALOG.
ORA-30951: Element or attribute at Xpath /AC/T[1]/T[1]/T[1]/T[1]/T[1]/Doc[@] exceeds maximum length
The <Doc> Element which is child of the <T> contains an XML Schema inside it..
The Doc Element is declared in Schema as
<xs:complexType name="AsDocType">
          <xs:annotation>
               <xs:documentation>A (Doc)ument, a container for any type of file</xs:documentation>
          </xs:annotation>
          <xs:sequence minOccurs="0" maxOccurs="unbounded">
               <xs:any namespace="##any" processContents="lax"/>
          </xs:sequence>
          <xs:attributeGroup ref="AsDocAtts"/>
     </xs:complexType>
The Size of the XML Content that <Doc> Node has is around 34Kb.
Could you pls let me know how to resolve this..
Thanks
Sateesh

XML data value exceeds maximum length - ORA-30951

Hello,
I am receiving ORA-30951: Element or attribute at Xpath /dataroot/Respondent[1]/Response[3]/Value exceeds maximum length error during the XML load.
I have registered the schema and it works fine when the Value is less than 64k but fails if its greater. I tried changing the type of Value to type="xsd:base64Binary" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="BLOB" but then I get ORA-00932: inconsistent datatypes error.
Can someone please let me know what I am doing wrong or is there a way I can load more than 64k length elements on 10g?
Thanks
Here is my schema.
var SCHEMAURL varchar2(256)
var XMLSCHEMA CLOB
set define off
begin
:SCHEMAURL := 'http://xmlns.example.com/Svy_Resp.xsd';
:XMLSCHEMA := '<?xml version="1.0"; encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0"; xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:storeVarrayAsTable="true">
<xsd:element name="dataroot" xdb:defaultTable="SVY_RESP_XML_SCHEMA" type="datarootType" />
<xsd:complexType name="datarootType" xdb:maintainDOM="false"
xdb:SQLType="Dataroot_T">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Respondent" type="RespondentType" />
</xsd:sequence>
<xsd:attribute name="generated" type="xsd:dateTime" />
</xsd:complexType>
<xsd:complexType name="RespondentType" xdb:maintainDOM="false" xdb:SQLType="Respondent_Type">
<xsd:sequence>
<xsd:element name="RespondentID" type="xsd:int" />
<xsd:element name="KsID" type="xsd:int" />
<xsd:element name="email" type="xsd:string" />
<xsd:element name="SyID" type="xsd:int" />
<xsd:element name="KSuID" type="xsd:int" />
<xsd:element name="Completed" type="xsd:int" />
<xsd:element name="SubmitDateTime" type="xsd:dateTime" />
<xsd:element maxOccurs="unbounded" name="Response" type="ResponseType" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ResponseType" xdb:maintainDOM="false" xdb:SQLType="Response_Type">
<xsd:sequence>
<xsd:element name="ResponseID" type="xsd:int" />
<xsd:element name="RespondentID" type="xsd:int" />
<xsd:element name="CID" type="xsd:int" />
<xsd:element name="AID" type="xsd:int" />
<xsd:element name="Value" type="xsd:string"/>
<xsd:element name="QID" type="xsd:int" />
<xsd:element name="SID" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>';
end;
/

Thanks for the quick response. I am not able to modify the source file, but will it be possible to set the value to NULL if it exceeds the max length instead of failure?
Thanks

ORA-30951: ...exceeds maximum length

Oracle Database 10g Release 10.2.0.1.0 - Production
I am new to XML and having a problem importing data using the XML Repository. I have annotated the schema and validated it using XML Spy. I am able to register the schema w/o errors. I am now working through the issues as they occur during the insertion of xml documents. Thes section below is giving me an error (bottom) that the data exceeds the maximum length. The "DATA" in the xml doc is a pdf file that has been converted to characters by some method. The size element has a data value of 5008. Seems to be too long for a varchar2. I tried RAW, CLOB, BLOB. I was pretty sure they wouldn't work and they didn't. I get an error that the xml/xdb types are incompatible.
How can I modify the schema to get this element to load?
Is it possible to tell oracle to ignore an element so I can eliminate those that are not critical? This would be very helpful.
Thanks!
Schema -
<xs:element name="NpdbReportList" minOccurs="0">
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:element name="NpdbReport" minOccurs="0">
<xs:complexType>
<xs:all minOccurs="0">
<xs:element name="DCN" minOccurs="0"/>
<xs:element name="DateReport" type="Date" minOccurs="0"/>
<xs:element name="ReportType" type="IdRef" minOccurs="0"/>
<xs:element ref="LOB" minOccurs="0"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="LOB" xdb:SQLType="LOB_T"xdb:maintainDOM="false">
<xs:all>
     <xs:element name="Type" type="IdRef"/>
     <xs:element name="Size"/>
     <xs:element name="Data" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="VARCHAR2"/>
</xs:all>
</xs:complexType>
ftp> mput *
mput Smyth_Steven_1386367.XML? y
227 Entering Passive Mode (127,0,0,1,83,221)
150 ASCII Data Connection
550- Error Response
ORA-30951: Element or attribute at Xpath /Provider/NpdbReportList/NpdbReport[1]/LOB/Data exceeds maximum length
550 End Error Response
28706 bytes sent in 0.014 seconds (1.9e+03 Kbytes/s)
ftp>

Thanks for your time Marco.
Here is the header:
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true" xdb:mapStringToNCHAR="true" xdb:mapUnboundedStringToLob="true">
I made the following change -
<xs:element name="Data" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="CLOB"/>
I received this error -
ORA-31094: incompatible SQL type "CLOB" for attribute or element "Data"
ORA-06512: at "XML_TEST.XML_TEST_SCHEMA_REGISTER", line 48
I did a little more testing after the first post. I used the same type as an element that is defining image data.
<xs:element name="Data" type="xs:base64Binary" xdb:maintainDOM="false" xdb:SQLName="LOB_DATA" xdb:SQLType="BLOB"/>
While this did register and I was able to load a record, I am guessing that this will render the data for this element usless but at least the record loads. I'll still need to resolve this issue as the .pdf data is important.
Thanks
Joe

Lax validation errors on schema import ('version' exceeds maximum length)

I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
Cheers,
Daniel
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
     <xs:element name="edit">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="edit_id" type="xs:string"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="derivation_id" type="xs:string"/>
                    <xs:element ref="br:derivation_type"/>
                    <xs:element ref="br:business_rule"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="derivation_type">
          <xs:simpleType>
               <xs:restriction base="xs:NMTOKENS">
                    <xs:enumeration value="complex"/>
                    <xs:enumeration value="format"/>
                    <xs:enumeration value="formula"/>
                    <xs:enumeration value="recode"/>
                    <xs:enumeration value="SAS code"/>
                    <xs:enumeration value="transfer"/>
                    <xs:enumeration value="count"/>
                    <xs:enumeration value="sum"/>
                    <xs:enumeration value="max"/>
                    <xs:enumeration value="min"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="business_rule"></xs:element>
</xs:schema>

Opps -- Sorry it's a decision we took when looking at Version
When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
SQL> desc xdb.xdb$schema_T
Name                                      Null?    Type
SCHEMA_URL                                         VARCHAR2(700)
TARGET_NAMESPACE                                   VARCHAR2(2000)
VERSION                                            VARCHAR2(12)
NUM_PROPS                                          NUMBER(38)
FINAL_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
BLOCK_DEFAULT                                      XDB.XDB$DERIVATIONCHOICE
ELEMENT_FORM_DFLT                                  XDB.XDB$FORMCHOICE
ATTRIBUTE_FORM_DFLT                                XDB.XDB$FORMCHOICE
ELEMENTS                                           XDB.XDB$XMLTYPE_REF_LIST_T
SIMPLE_TYPE                                        XDB.XDB$XMLTYPE_REF_LIST_T
COMPLEX_TYPES                                      XDB.XDB$XMLTYPE_REF_LIST_T
ATTRIBUTES                                         XDB.XDB$XMLTYPE_REF_LIST_T
IMPORTS                                            XDB.XDB$IMPORT_LIST_T
INCLUDES                                           XDB.XDB$INCLUDE_LIST_T
FLAGS                                              RAW(4)
SYS_XDBPD$                                         XDB.XDB$RAW_LIST_T
ANNOTATIONS                                        XDB.XDB$ANNOTATION_LIST_T
MAP_TO_NCHAR                                       RAW(1)
MAP_TO_LOB                                         RAW(1)
GROUPS                                             XDB.XDB$XMLTYPE_REF_LIST_T
ATTRGROUPS                                         XDB.XDB$XMLTYPE_REF_LIST_T
ID                                                 VARCHAR2(256)
VARRAY_AS_TAB                                      RAW(1)
SCHEMA_OWNER                                       VARCHAR2(30)
NOTATIONS                                          XDB.XDB$NOTATION_LIST_T
LANG                                               VARCHAR2(4000)
SQL>

SQL Loader - Field in data file exceeds maximum length

Dear All,
I have a file which has more than 4000 characters in a field and I wish to load the data in a table with field length = 4000. but I receive error as
Field in data file exceeds maximum lengthThe below given are the scripts and ctl file
Table creation script:
CREATE TABLE "TEST_TAB"
    "STR" VARCHAR2(4000 BYTE),
    "STR2" VARCHAR2(4000 BYTE),
    "STR3" VARCHAR2(4000 BYTE)
);Control file:
LOAD DATA
INFILE 'C:\table_export.txt'
APPEND INTO TABLE TEST_TAB
FIELDS TERMINATED BY '|'
TRAILING NULLCOLS
( STR CHAR(4000) "SUBSTR(:STR,1,4000)" ,
STR2 CHAR(4000) "SUBSTR(:STR2,1,4000)" ,
STR3 CHAR(4000) "SUBSTR(:STR3,1,4000)"
)Log:
SQL*Loader: Release 10.2.0.1.0 - Production on Mon Jul 26 16:06:25 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Control File:   C:\TEST_TAB.CTL
Data File:      C:\table_export.txt
Bad File:     C:\TEST_TAB.BAD
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 0
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional
Table TEST_TAB, loaded from every logical record.
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect
   Column Name                  Position   Len Term Encl Datatype
STR                                 FIRST 4000   |       CHARACTER
    SQL string for column : "SUBSTR(:STR,1,4000)"
STR2                                 NEXT 4000   |       CHARACTER
    SQL string for column : "SUBSTR(:STR2,1,4000)"
STR3                                 NEXT 4000   |       CHARACTER
    SQL string for column : "SUBSTR(:STR3,1,4000)"
value used for ROWS parameter changed from 64 to 21
Record 1: Rejected - Error on table TEST_TAB, column STR.
Field in data file exceeds maximum length
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table TEST_TAB:
0 Rows successfully loaded.
1 Row not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array:                 252126 bytes(21 rows)
Read   buffer bytes: 1048576
Total logical records skipped:          0
Total logical records read:             1
Total logical records rejected:         1
Total logical records discarded:        0
Run began on Mon Jul 26 16:06:25 2010
Run ended on Mon Jul 26 16:06:25 2010
Elapsed time was:     00:00:00.22
CPU time was:         00:00:00.15Please suggest a way to get it done.
Thanks for reading the post!
*009*

Hi Toni,
Thanks for the reply.
Do you mean this?
CREATE TABLE "TEST"."TEST_TAB"
    "STR" VARCHAR2(4001),
    "STR2" VARCHAR2(4001),
    "STR3" VARCHAR2(4001)
);However this does not work as the error would be:
Error at Command Line:8 Column:20
Error report:
SQL Error: ORA-00910: specified length too long for its datatype
00910. 00000 - "specified length too long for its datatype"
*Cause:    for datatypes CHAR and RAW, the length specified was > 2000;
           otherwise, the length specified was > 4000.
*Action:   use a shorter length or switch to a datatype permitting a
           longer length such as a VARCHAR2, LONG CHAR, or LONG RAW*009*
Edited by: 009 on Jul 28, 2010 6:15 AM

DRG-11112: length of CLOB query value exceeds maximum of 64000

Is there a CLOB length limitation when running an Oracle Text search? (v 11.1.0.7) I have checked the Reference Guide and Application Developer's Guide.
--create table
create table nk_1929(id number, vc_a clob);
--insert dummy data
declare
vc_clob clob;
begin
vc_clob := lpad(to_clob('a'), 222920, 'a');
insert into nk_1929 values(1, vc_clob);
end;
--create index
create index nk_1929_ndx on nk_1929(vc_a)
indextype is ctxsys.context parameters('
datastore ctxsys.default_datastore
stoplist ctxsys.empty_stoplist');
--run query with a search string longer than 64000
declare
str1 clob;
query_term clob;
begin
select vc_a into query_term from nk_1929 where id = 1;
str1 := 'select id from nk_1929 where contains(vc_a, :1) > 0';
execute immediate str1 using query_term;
end;
ORA-29902: error in executing ODCIIndexStart() routine
ORA-20000: Oracle Text error:
DRG-11112: length of CLOB Query Value exceeds maximum of 64000
Please let me know if I am missing something here?

Same 64000 CLOB query value limitation is also generated with a simple select:
--run query with a search string longer than 64000
declare
vn_id number;
query_term clob;
begin
select vc_a into query_term from nk_1929 where id = 1;
select max(id) into vn_id from nk_1929 where contains(vc_a, query_term) > 0;
end;
ORA-29902: error in executing ODCIIndexStart() routine
ORA-20000: Oracle Text error:
DRG-11112: length of CLOB Query Value exceeds maximum of 64000

Field in data file exceeds maximum length

Hi,
I am trying to run the following SQL*Loader control job on my Oracle 11gR2 . Running the SQL*Loader control job results in the ‘Field in data file exceeds maximum length’ error message. Below, I am listing the control file.Please Suggest. Thanks
It's giving me an error when I run SQL Loader on it,
Record 61: Rejected - Error on table RMS_TABLE, column GEOM.SDO_POINT.X.
Field in data file exceeds maximum length.
Here is my SQL Loader Control file,
LOAD DATA
INFILE *
TRUNCATE
CONTINUEIF NEXT(1:1) = '#'
INTO TABLE RMS_TABLE
FIELDS TERMINATED BY '|'
TRAILING NULLCOLS (
   Status NULLIF Status = BLANKS,
   Score,
   Match_type NULLIF Match_type = BLANKS,
   Match_addr NULLIF Match_addr = BLANKS,
   Side NULLIF Side = BLANKS,
   User_fld NULLIF User_fld = BLANKS,
   Addr_type NULLIF Addr_type = BLANKS,
   ARC_Street NULLIF ARC_Street = BLANKS,
   ARC_City NULLIF ARC_City = BLANKS,
   ARC_State NULLIF ARC_State = BLANKS,
   ARC_ZIP NULLIF ARC_ZIP = BLANKS,
   INCIDENT_N NULLIF INCIDENT_N = BLANKS,
   CDATE NULLIF CDATE = BLANKS,
   CTIME NULLIF CTIME = BLANKS,
   DISTRICT NULLIF DISTRICT = BLANKS,
LOCATION
NULLIF LOCATION = BLANKS,
   MAPLOCATIO
NULLIF MAPLOCATIO = BLANKS,
   LOCATION_T
NULLIF LOCATION_T = BLANKS,
   DAYCODE
NULLIF DAYCODE = BLANKS,
   CAUSE
NULLIF CAUSE = BLANKS,
   GEOM COLUMN OBJECT
     SDO_GTYPE       INTEGER EXTERNAL,
     SDO_POINT COLUMN OBJECT
       (X            FLOAT EXTERNAL,
        Y            FLOAT EXTERNAL)
CREATE TABLE RMS_TABLE (
Status VARCHAR2(1),
Score NUMBER,
Match_type VARCHAR2(2),
Match_addr VARCHAR2(120),
Side VARCHAR2(1),
User_fld VARCHAR2(120),
Addr_type VARCHAR2(20),
ARC_Street VARCHAR2(100),
ARC_City VARCHAR2(40),
ARC_State VARCHAR2(20),
ARC_ZIP VARCHAR2(10),
INCIDENT_N VARCHAR2(9),
CDATE VARCHAR2(10),
CTIME VARCHAR2(8),
DISTRICT VARCHAR2(4),
LOCATION VARCHAR2(128),
MAPLOCATIO VARCHAR2(100),
LOCATION_T VARCHAR2(42),
DAYCODE VARCHAR2(1),
CAUSE VARCHAR2(17),
GEOM MDSYS.SDO_GEOMETRY);

Hi,
Looks like you have a problem with record 61 in your data file. Can you please post it in reply.
Regards
Ivan

ORA-01044: size of buffer bound to variable exceeds maximum

Hello Oracle Gurus,
I have a tricky problem.
I have a stored procedure which has to retun more than 100,000 records. In my stored procedure, I have "TABLE OF VARCHAR2(512) INDEX BY BINARY_INTEGER". It fails when I try to get 80,000 records.
I get an error "ORA-01044: size 40960000 of buffer bound to variable exceeds maximum 33554432"
A simple calculation shows that 512*80000=40960000.
Oracle help suggests to reduce buffer size (i.e., number of records being returned or size of variable).
But, reducing the number of records returned or reducing the size of variable is not possible because of our product design constraints.
Are there any other options like changing some database startup parameters to solve this problem?
Thanks,
Sridhar

We are migrating an application running on Oracle 8i to 9i and found the same problem with some of the stored procedures.
Our setup:
+ Oracle 9.2.0.3.0
+ VB6 Application using OLEDB for Oracle ...
+ MDAC 2.8 msdaora.dll - 2.80.1022.0 (srv03_rtm.030324-2048)
I am calling a stored procedure from VB like this one:
{? = call trev.p_planung.GET_ALL_KONTEN(?,?,{resultset 3611, l_konto_id, l_name,l_ro_id, l_beschreibung, l_typ, l_plg_id})}
If setting the parameter "resultset" beyond a certain limit, I will eventually get this ORA-01044 error. This even happens, if the returned number of records is smaller than what supplied in the resultset parameter (I manually set the "resultset" param in the stored procedure string). E.g.:
resultset = 1000 -> ORA-06513: PL/SQL: Index der PL/SQL-Tabelle ungÃ¼ltig fÃ¼r Language-Array vom Host
resultset = 2000 -> OK (actual return: 1043 Recordsets)
resultset = 3000 -> ORA-01044: GrÃ¶Ãe 6000000 des Puffers fÃ¼r Variable Ã¼berschreitet HÃ¶chstwert von 4194304
resultset = 3500 -> ORA-01044: GrÃ¶Ãe 7000000 des Puffers fÃ¼r Variable Ã¼berschreitet HÃ¶chstwert von 4194304
... therefore one record is calculated here 7000000/3500=2000 bytes.
In Oracle 8i we never had this problem. As this is a huge application using a lot stored procedures, changing all "select" stored procedures to "get data by chunks" (suggestet in some forum threads in OTN) ist not an option.
Interesting: I can call the stored procedure above with the same parameters as given in VB from e.g. Quest SQL Navigator or sql plus successfully and retrieve all data!
Is there any other known solution to this problem in Oracle 9i? Is it possible to increase the maximum buffer size (Oracle documentation: ORA-01044 ... Action: Reduce the buffer size.)? What buffer size is meant here - which part in the communication chain supplies this buffer?
Any help highly appreciated!
Sincerely,
Sven Bombach

SQL Azure Reporting - There was an exception running the extensions specified in the config file. --- Maximum request length exceeded.

I am trying to deploy an RDL file (5MB) to SQL Azure Reporting server in South Central US using the deploy function in SQL Server Data Tools but facing the following error during deployment to Azure Reporting server.
"There was an exception running the extensions specified in the config file. ---> Maximum request length exceeded."
Is there any limit on the size of RDL files which can be deployed to Azure Reporting server? I have seen some online posts which talk about increasing the maxRequestLength in httpruntime of web.config in Reporting server. But in case of Azure Reporting server
how can be make modification to this configuration?
I have tried to upload it directly to SQL Azure Reporting server from the Management Portal --> Upload Report function which still resulted in error.
Thanks & Regards, Deep

Thanks for your question. Unfortunately we are in the process of deprecating SQL Reporting services. Full details are available at http://msdn.microsoft.com/en-us/library/gg430130.aspx
Thanks Guy

On load, getting error: Field in data file exceeds maximum length

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0    Production
TNS for Solaris: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
I'm trying to load a table, small in size (110 rows, 6 columns). One of the columns, called NOTES is erroring when I run the load. It is saying that the column size exceeds max limit. As you can see here, the table column is set to 4000 Bytes)
CREATE TABLE NRIS.NRN_REPORT_NOTES
NOTES_CN      VARCHAR2(40 BYTE)               DEFAULT sys_guid()            NOT NULL,
REPORT_GROUP VARCHAR2(100 BYTE)              NOT NULL,
AREACODE      VARCHAR2(50 BYTE)               NOT NULL,
ROUND         NUMBER(3)                       NOT NULL,
NOTES         VARCHAR2(4000 BYTE),
LAST_UPDATE   TIMESTAMP(6) WITH TIME ZONE     DEFAULT systimestamp          NOT NULL
TABLESPACE USERS
RESULT_CACHE (MODE DEFAULT)
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
            INITIAL          80K
            NEXT             1M
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
            FLASH_CACHE      DEFAULT
            CELL_FLASH_CACHE DEFAULT
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
I did a little investigating, and it doesn't add up.
when i run
select max(lengthb(notes)) from NRIS.NRN_REPORT_NOTES
I get a return of
643
That tells me that the largest size instance of that column is only 643 bytes. But EVERY insert is failing.
Here is the loader file header, and first couple of inserts:
LOAD DATA
INFILE *
BADFILE './NRIS.NRN_REPORT_NOTES.BAD'
DISCARDFILE './NRIS.NRN_REPORT_NOTES.DSC'
APPEND INTO TABLE NRIS.NRN_REPORT_NOTES
Fields terminated by ";" Optionally enclosed by '|'
NOTES_CN,
REPORT_GROUP,
AREACODE,
ROUND NULLIF (ROUND="NULL"),
NOTES,
LAST_UPDATE TIMESTAMP WITH TIME ZONE "MM/DD/YYYY HH24:MI:SS.FF9 TZR" NULLIF (LAST_UPDATE="NULL")
BEGINDATA
|E2ACF256F01F46A7E0440003BA0F14C2|;|DEMOGRAPHICS|;|A01003|;3;|Demographic results show that 46 percent of visits are made by females. Among racial and ethnic minorities, the most commonly encountered are Native American (4%) and Hispanic / Latino (2%). The age distribution shows that the Bitterroot has a relatively small proportion of children under age 16 (14%) in the visiting population. People over the age of 60 account for about 22% of visits.   Most of the visitation is from the local area. More than 85% of visits come from people who live within 50 miles.|;07/29/2013 16:09:27.000000000 -06:00
|E2ACF256F02046A7E0440003BA0F14C2|;|VISIT DESCRIPTION|;|A01003|;3;|Most visits to the Bitterroot are fairly short. Over half of the visits last less than 3 hours. The median length of visit to overnight sites is about 43 hours, or about 2 days. The average Wilderness visit lasts only about 6 hours, although more than half of those visits are shorter than 3 hours long.   Most visits come from people who are fairly frequent visitors. Over thirty percent are made by people who visit between 40 and 100 times per year. Another 8 percent of visits are from people who report visiting more than 100 times per year.|;07/29/2013 16:09:27.000000000 -06:00
|E2ACF256F02146A7E0440003BA0F14C2|;|ACTIVITIES|;|A01003|;3;|The most frequently reported primary activity is hiking/walking (42%), followed by downhill skiing (12%), and hunting (8%). Over half of the visits report participating in relaxing and viewing scenery.|;07/29/2013 16:09:27.000000000 -06:00
Here is the full beginning of the loader log, ending after the first row return. (They ALL say the same error)
SQL*Loader: Release 10.2.0.4.0 - Production on Thu Aug 22 12:09:07 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Control File:   NRIS.NRN_REPORT_NOTES.ctl
Data File:      NRIS.NRN_REPORT_NOTES.ctl
Bad File:     ./NRIS.NRN_REPORT_NOTES.BAD
Discard File: ./NRIS.NRN_REPORT_NOTES.DSC
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional
Table NRIS.NRN_REPORT_NOTES, loaded from every logical record.
Insert option in effect for this table: APPEND
   Column Name                  Position   Len Term Encl Datatype
NOTES_CN                            FIRST     *   ; O(|) CHARACTER
REPORT_GROUP                         NEXT     *   ; O(|) CHARACTER
AREACODE                             NEXT     *   ; O(|) CHARACTER
ROUND                                NEXT     *   ; O(|) CHARACTER
    NULL if ROUND = 0X4e554c4c(character 'NULL')
NOTES                                NEXT     *   ; O(|) CHARACTER
LAST_UPDATE                          NEXT     *   ; O(|) DATETIME MM/DD/YYYY HH24:MI:SS.FF9 TZR
    NULL if LAST_UPDATE = 0X4e554c4c(character 'NULL')
Record 1: Rejected - Error on table NRIS.NRN_REPORT_NOTES, column NOTES.
Field in data file exceeds maximum length...
I am not seeing why this would be failing.

HI,
the problem is delimited data defaults to char(255)..... Very helpful I know.....
what you need to two is tell sqlldr hat the data is longer than this.
so change notes to notes char(4000) in you control file and it should work.
cheers,
harry

ORA-31044: Top-level prefix length exceeds maximum

Similar Messages

Maybe you are looking for