ORA-22813: operand value exceeds system limits

hi all,
ORA-22813: operand value exceeds system limits
the above error occurs while calling a function. in 10g its working fine. after moving it to 11g v r facing the error. Plz help

KRIS wrote:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE 11.1.0.7.0 Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - ProductionIt seems that is a bug,refer
*Bug 8861467 - ORA-22813 / ORA-600 [12761] can occur in 11g [ID 8861467.8]*
To fixing problem you need apply 11.2.0.2 (Server Patch Set)

Similar Messages

ORA-22813: operand value exceeds system limits when generation XML

Hi All,
We are using Oracle 11GR2 database and I am trying to generate XML Files using SQL/XML Functions.
I am in the end of development and while testing I am facing this freaking issue. ORA-22813: operand value exceeds system limits.
SELECT XMLSERIALIZE(DOCUMENT DATA AS CLOB) AS DATA FROM (
          SELECT
          XMLELEMENT (
"Region_Data",
XMLAGG (
XMLFOREST (
R.region as "Region_Name",
R.first_name||R.last_name as "EmployeeFullName",
R.ntlogin as "EmployeeAlias",
R.job_title as "EmployeeRole",
R.sap_number as "SAPNumber",
R.sales_transaction_dt AS "Day",
R.region AS "RegionName",
R.postpaid_totalqty AS "PostpaidCount",
R.postpaid_totaldollars AS "PostpaidAmount",
R.postpaidfeature_totalqty AS "PostpaidFeatureCount",
R.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
R.prepaid_totalqty AS "PrepaidCount",
R.prepaid_totaldollars AS "PrepaidAmount" ,
R.prepaidfeature_totalqty AS "PrepaidFeatureCount",
R.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
R.accessory_totalqty AS "AccessoriesCount",
R.accessory_totaldollars AS "AccessoriesAmount",
R.handset_totalqty AS "HandsetsCount",
R.handset_totaldollars AS "HandsetsAmount",
(SELECT XMLAGG (
XMLELEMENT (
"Division",
XMLFOREST (
di.division AS "DivisonName",
di.postpaid_totalqty AS "PostpaidCount",
di.postpaid_totaldollars AS "PostpaidAmount",
di.postpaidfeature_totalqty AS "PostpaidFeatureCount",
di.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
di.prepaid_totalqty AS "PrepaidCount",
di.prepaid_totaldollars AS "PrepaidAmount" ,
di.prepaidfeature_totalqty AS "PrepaidFeatureCount",
di.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
di.accessory_totalqty AS "AccessoriesCount",
di.accessory_totaldollars AS "AccessoriesAmount",
di.handset_totalqty AS "HandsetsCount",
di.handset_totaldollars AS "HandsetsAmount",
(SELECT XMLAGG (
XMLELEMENT (
"District",
XMLFOREST (
dis.district AS "DistrictName",
dis.postpaid_totalqty AS "PostpaidCount",
dis.postpaid_totaldollars AS "PostpaidAmount",
dis.postpaidfeature_totalqty AS "PostpaidFeatureCount",
dis.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
dis.prepaid_totalqty AS "PrepaidCount",
dis.prepaid_totaldollars AS "PrepaidAmount" ,
dis.prepaidfeature_totalqty AS "PrepaidFeatureCount",
dis.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
dis.accessory_totalqty AS "AccessoriesCount",
dis.accessory_totaldollars AS "AccessoriesAmount",
dis.handset_totalqty AS "HandsetsCount",
dis.handset_totaldollars AS "HandsetsAmount",
(SELECT XMLAGG (
XMLELEMENT (
"Store",
XMLFOREST (
mst.store_id AS "StoreNumber",
mst.store_name AS "StoreLocation",
mst.postpaid_totaldollars AS "PostpaidAmount",
mst.postpaidfeature_totalqty AS "PostpaidFeatureCount",
mst.postpaidfeature_totaldollar AS "PostpaidFeatureAmount",
mst.prepaid_totalqty AS "PrepaidCount",
mst.prepaid_totaldollars AS "PrepaidAmount" ,
mst.prepaidfeature_totalqty AS "PrepaidFeatureCount",
mst.prepaidfeature_totaldollars AS "PrepaidFeatureAmount",
mst.accessory_totalqty AS "AccessoriesCount",
mst.accessory_totaldollars AS "AccessoriesAmount",
mst.handset_totalqty AS "HandsetsCount",
mst.handset_totaldollars AS "HandsetsAmount"
FROM stores_comm_mobility_info_vw mst
WHERE mst.district = dis.district
) "Store_Data")))
FROM diST_comm_mobility_info_vw dis
WHERE dis.division = di.division
) "District_Data")))
FROM div_comm_mobility_info_vw di
WHERE di.region = r.region
) AS "Division_Data"))) AS DATA
FROM reg_comm_mobility_info_vw R GROUP BY region)
This is working fine for conditions where there is less amount of data, but when there is more data this query is failing.
I do not know what to do now. Is there any way of this limit or do I need someother mechanisms to generate XML Files.
The challenge is we need to generate XML Files and send the XML Data to an Interface which will use this data to display in a cell phone.
I am really frustated now as I am getting this error when I am testing for huge amount of data.
Appreciate if anyone can help me out ASAP.
(tHE BELOW XML I am trying to generate)
<REGION>
     <Region_Data>
          <Region_Name>Southwest</Region_Name>
          <EmployeeFullName>AllisonAndersen</EmployeeFullName>
          <EmployeeAlias>AANDERS60</EmployeeAlias>
          <EmployeeRole>District Manager, Retail Sales</EmployeeRole>
          <SAPNumber>P12466658</SAPNumber>
          <Day>JAN</Day>
          <RegionName>Southwest</RegionName>
          <PostpaidCount>52</PostpaidCount>
          <PostpaidAmount>1579.58</PostpaidAmount>
          <PostpaidFeatureCount>296</PostpaidFeatureCount>
          <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
          <AccessoriesCount>394</AccessoriesCount>
          <AccessoriesAmount>45213.87</AccessoriesAmount>
          <Division_Data>
               <Division>
                    <DivisonName>Southern California</DivisonName>
                    <PostpaidCount>52</PostpaidCount>
                    <PostpaidAmount>1579.58</PostpaidAmount>
                    <PostpaidFeatureCount>296</PostpaidFeatureCount>
                    <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
                    <AccessoriesCount>394</AccessoriesCount>
                    <AccessoriesAmount>45213.87</AccessoriesAmount>
                    <District_Data>
                         <District>
                              <DistrictName>Orange County West</DistrictName>
                              <PostpaidCount>52</PostpaidCount>
                              <PostpaidAmount>1579.58</PostpaidAmount>
                              <PostpaidFeatureCount>296</PostpaidFeatureCount>
                              <PostpaidFeatureAmount>4174.19</PostpaidFeatureAmount>
                              <AccessoriesCount>394</AccessoriesCount>
                              <AccessoriesAmount>45213.87</AccessoriesAmount>
                              <Store_Data>
                                   <Store>
                                        <StoreNumber>9551</StoreNumber>
                                        <StoreLocation>TM - BROOKHURST & WARNER</StoreLocation>
                                        <PostpaidAmount>10</PostpaidAmount>
                                        <PostpaidFeatureCount>22</PostpaidFeatureCount>
                                        <PostpaidFeatureAmount>319.89</PostpaidFeatureAmount>
                                        <AccessoriesCount>27</AccessoriesCount>
                                        <AccessoriesAmount>4330</AccessoriesAmount>
                                   </Store>
                              </Store_Data>
                         </District>
                    </District_Data>
               </Division>
          </Division_Data>
     </Region_Data>
</REGION>
Thanks,
Madhu K.

You didn't give any feedback in your previous thread.
Did you try the approach suggested here in {message:id=10998557}, instead of using nested inline subqueries ?

Operand value exceeds system limits in sdo_aggr_mbr

Hi-- i'm trying to get the MBR of a fairly large geometry (1429 vertices) and run into a strange problem:
when i:
select sdo_aggr_mbr(shape)
from FEEDER_LINES_SDO
where subname = 'OCEANO';
i get what i expect:
SDO_GEOMETRY(2003, 82212, NULL, SDO_ELEM_INFO_ARRAY(1,1003, 3),SDO_ORDINATE_ARRAY(712103.736,3876977.34, 733591.744, 3896557.18))
however when i try to get the subname in my query as well:
select subname ,sdo_aggr_mbr(shape)
from FEEDER_LINES_SDO
where subname = 'OCEANO'
group by subname;
i get
ERROR at line 1:
ORA-22813: operand value exceeds system limits
The query fails with "ORA-00937: not a single-group group function" when i leave out the group by clause
i can get around it with a kludge, but would like to know why the group by fails
the kludge:
select subname,min(t.x) minx, min(t.y) miny, max(t.x) maxx, max(t.y) maxy from
FEEDER_LINES_SDO c,
TABLE(SDO_UTIL.GETVERTICES(c.shape)) t
where subname = 'OCEANO'
group by subname;
SUBNAME MINX MINY MAXX MAXY
OCEANO     712103.736 3876977.34 733591.744 3896557.18
where minx(), miny() etc are variations on:
function minx (geom_in mdsys.sdo_geometry)
return number DETERMINISTIC IS
begin
return sdo_geom.sdo_min_mbr_ordinate(geom_in,1);
end;
the group by expression seems to work fine on geometries with less than 1200 vertices. Is there a system parameter i can change?
elvis{44}% oerr ora 22813
22813, 00000, "operand value exceeds system limits"
// *Cause: Object or Collection value was too large. The size of the value
// might have exceeded 30k in a SORT context, or the size might be
// too big for available memory.
// *Action: Choose another value and retry the operation.
i am running oracle 9.2.0.1 on solaris8
any insight on this will be greatly appreciated
cheers
--kassim

Hi Kassim,
At KMS I recently ran into the same ORA-22813, when running this cursor SQL
     CURSOR lcur_montage IS
     select m.mont_id, m.sys_PK, m.krtp_id, m.mont_geom, m.til_dato_id , m.forloeb
     from MTK_montage m
     where m.fra_dato_id = in_dato_id
     and m.krtp_id = 1
     order by m.mont_id;
Omitting the order by clause makes it work fine. If I alternatively omit the SDO_geometry m.mont_geom as a select item, the query also works.
Our problem seems to arise when trying to sort selected rows, which contain large objects such as SDO_geometry.
Yesterday we played around with SORT_AREA_SIZE, but to no avail. It turns out to be a known bug.
When I today search for ORA-22813 in MetaLink, the first list item is
1.
9.2.0.X Patch Sets - List of Bug Fixes by Problem Type
Type: Note
Doc ID: 217194.1
Score: 63%
Modified Date: 18-FEB-2003
Status: PUBLISHED
Platform: Generic issue
Product: Oracle Server - Enterprise Edition
which unfortunately will not open and reveal its content.
On the other hand trying MetaLink -> Bugs -> search for 'ORA-22813' gives amongst others Bug 2656107, which looks a lot like my problem.
For Oracle eyes: - when will this bug be fixed? Does it solve the problem at hand?
- regards
Jens Ole Jensen
Kort & MatrikelStyrelsen (WWW: http://www.kms.dk)
Danmark
version: (32 bit) Oracle9i Enterprise Edition Release 9.2.0.2.0 - Production on Sun/SunOS 5.8 (64 bit)

ORA 22813 in merge statement

hi gems..good afternoon...
My database version is 11.2.0.1.0 64 bit Solaris OS.
I am facing an "ORA-22813: operand value exceeds system limits" while running a procedure.
I have used loggers and found that it is getting failed in a MERGE statement.
That merge statement is used to merge a table with a collection. the code is like below:
MERGE /*+ INDEX(P BALANCE_HISTORIC_INDEX) */
    INTO BALANCE_HOLD_HISTORIC P
    USING TABLE(GET_BALANCE_HIST(V_MERGE_REC)) M
    ON (P.CUSTOMER_ID = M.CUSTOMER_ID AND P.BOOK_ID = M.BOOK_ID AND P.PRODUCT_ID = M.PRODUCT_ID AND P.SUB_BOOK_ID = M.SUB_BOOK_ID AND)
    WHEN MATCHED THEN
      UPDATE
         <set .....>
    WHEN NOT MATCHED THEN
      INSERT<.....>The parameter of the function GET_BALANCE_HIST(V_MERGE_REC) is a table type.
Now the function GET_BALANCE_HIST(V_MERGE_REC) is a pipelined function and we have used that because the collection V_MERGE_REC may get huge with data.
This proc was running fine from the beginning but from day before yesterday it was continously throwing ORA 22813 error in that line.
please help..thanks in advance..

hi paul..thanks for your reply...
the function GET_BALANCE_HIST is not selecting data from any tables.
What this pipeline function is doing is, it is taking the huge collection V_MERGE_REC as parameter and releasing its datas in pipelined form. The code for the functions is :
CREATE OR REPLACE FUNCTION GET_BALANCE_HIST(P_MERGE IN TAB_TYPE_BALANCE_HISTORIC)
RETURN TAB_TYPE_BALANCE_HISTORIC
PIPELINED AS
V_MERGE TAB_TYPE_BALANCE_HISTORIC := TAB_TYPE_BALANCE_HISTORIC();
BEGIN
FOR I IN 1 .. P_MERGE.COUNT LOOP
    V_MERGE.EXTEND;
    V_MERGE(V_MERGE.LAST) := OBJ_TYPE_BALANCE_HISTORIC(P_MERGE(I).CUSTOMER_ID,
                                             P_MERGE(I).BOOK_ID,
                                             P_MERGE(I).PRODUCT_ID,
                                             P_MERGE(I).SUB_BOOK_ID,
                                             P_MERGE(I).EARNINGS,
                                             P_MERGE(I).EARNINGS_HOUSE,
                                             P_MERGE(I).QUANTITY,
                                             P_MERGE(I).ACCOUNT_INTEGER);
END LOOP;
FOR J IN 1 .. V_MERGE.COUNT LOOP
    PIPE ROW(OBJ_TYPE_BALANCE_HISTORIC(V_MERGE(I).CUSTOMER_ID,
                                             V_MERGE(I).BOOK_ID,
                                             V_MERGE(I).PRODUCT_ID,
                                             V_MERGE(I).SUB_BOOK_ID,
                                             V_MERGE(I).EARNINGS,
                                             V_MERGE(I).EARNINGS_HOUSE,
                                             V_MERGE(I).QUANTITY,
                                             V_MERGE(I).ACCOUNT_INTEGER));
END LOOP;
RETURN;
END;I think the error is comming because of the parameter value of V_MERGE_REC. Since it is huge, so loading that into memory is causing problem. But in this case, how can I resolve it?? Can I use a global temporary table for this??
Please suggest...

ORA-22813 on SELECT with ORDER BY

Hi all,
I have on a server Windows 2003 (3Gb RAM) an Oracle Database 9.2.0.1
Until last week all seems right, but now when i submit this SQL:
Select a,b,c,d,e... from mytable order by a,b
I have this error:
ORA-22813 "operand value exceeds system limits"
-If i remove a first or second column from order by clause
-If i remove a geometry column or some columns from the select
It works.
To fix this problem I have tried to:
Recreate any indexes (data and spatial), no result
Enable/Disable all costraints, no result
Set parameter hash_join_tables to true and false, no result
Enlarge the PGA, no result
Copy only 10 record in another blank table, no result
Export the table and import it in another database in another server (Windows 2003 / Oracle 9.2.0.1). The Export and Import are ok but the error is the same.
Can you help me? Have you any suggest?
Thanks

Error:     ORA-22813
Text:     operand value exceeds system limits
Cause:     Object or Collection value was too large. The size of the value might
     have exceeded 30k in a SORT context, or the size might be too big for
     available memory.
Action:     Choose another value and retry the operation.Has your data changed such that one of the recent values is hitting this limit.
Note also Metalink bug 5959987 Spatial aggregations fail with ORA-22813 which is only confirmed as being in 10.2.0.3 but says
ORA-22813 can occur when performing Spatial aggregations
(SDO_AGGR_UNION or SDO_AGGR_CONCAT_LINES)
when used with a GROUP BY clause and the input contains
geometries that occupy more than 32K."

ORA-22813 ?

Hi,
I've run into an interesting ORA-22813 error. I ran the following SQL aginst an xmltype table.
SQL> select
2 extractValue(value(a), '/GTP/TransmissionSource@ID') TransmissionSourceID,
3 extractValue(value(a), '/GTP/TransmissionSource@Name') TransmissionSourceName,
4 extractValue(value(b), '/Study@ID') StudyID,
5 extractValue(value(b), '/Study@Name') StudyName,
6 extractValue(value(b), '/Study@TransmissionType') StudyTransmissionType,
7 extractValue(value(c), '/Site@ID') SiteID,
8 extractValue(value(d), '/Investigator@ID') InvestigatorID,
9 extractValue(value(d), '/Investigator@Name') InvestigatorName
10 from gtp x,
11 table(xmlsequence(extract(value(x),'/GTP'))) a,
12 table(xmlsequence(extract(value(x),'/GTP/Study'))) b,
13 table(xmlsequence(extract(value(x),'/GTP/Study/Site'))) c,
14 table(xmlsequence(extract(value(x),'/GTP/Study/Site/Investigator'))) d
15 /
select
extractValue(value(a), '/GTP/TransmissionSource@ID') TransmissionSourceID,
extractValue(value(a), '/GTP/TransmissionSource@Name') TransmissionSourceName,
extractValue(value(b), '/Study@ID') StudyID,
extractValue(value(b), '/Study@Name') StudyName,
extractValue(value(b), '/Study@TransmissionType') StudyTransmissionType,
extractValue(value(c), '/Site@ID') SiteID,
extractValue(value(d), '/Investigator@ID') InvestigatorID,
extractValue(value(d), '/Investigator@Name') InvestigatorName
from gtp x,
table(xmlsequence(extract(value(x),'/GTP'))) a,
table(xmlsequence(extract(value(x),'/GTP/Study'))) b,
table(xmlsequence(extract(value(x),'/GTP/Study/Site'))) c,
table(xmlsequence(extract(value(x),'/GTP/Study/Site/Investigator'))) d
ORA-22813: operand value exceeds system limits
SQL>
Not sure how to get around this one? The query was correctly a number of times without any issue.
Also, I've got over ~90 SYS_IOT_OVER_39#### and ~70 SYS_NT+qzhFuERTRio9lfg061upw== bla, bal table objects.
Not sure what these are?
Thanks.

OK
A number of questions. I assume GTP only occurs once per document (eg is the root node), in which case there is no point to 'sequencing' GTP.
I'm assuming that Study can occur more than once with GTP, and Site more than once within Study and Investigator more than once with Site.
If the above is true the problem may be caused by the way you are constructing your sequences. XMLSequence relies on a correlated join. Hence each level of nesting should be obtained as a subset of the previous level. In your case you are creating a cartesian product which may explain the error...
Try the following
select
extractValue(value(x), '/GTP/TransmissionSource@ID') TransmissionSourceID,
extractValue(value(x), '/GTP/TransmissionSource@Name') TransmissionSourceName,
extractValue(value(study), '/Study@ID') StudyID,
extractValue(value(study), '/Study@Name') StudyName,
extractValue(value(study), '/Study@TransmissionType') StudyTransmissionType,
extractValue(value(site), '/Site@ID') SiteID,
extractValue(value(investigator), '/Investigator@ID') InvestigatorID,
extractValue(value(d), '/Investigator@Name') InvestigatorName
from gtp x,
table(xmlsequence(extract(value(x),'/GTP/Study'))) study,
table(xmlsequence(extract(value(study),'/Study/Site'))) site,
table(xmlsequence(extract(value(site),'Site/Investigator'))) investigator
The tables you see imply that you have 70 different collections within your XML Schema.

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-01536: space quota exceeded for tablespace 'SYSTEM'

Hi All,
Please help me to understand the below issue. I am trying to create a table as below. Connected as APPS user.
SQL>create table test_ts(id number) tablespace APPS_TS_TX_DATA
ORA-00604: error occurred at recursive SQL level 1
ORA-01536: space quota exceeded for tablespace 'SYSTEM'
ORA-06512: at line 2
Below are the details of the user
SQL>select * from user_ts_quotas
        where tablespace_name = 'APPS_TS_TX_DATA'
TABLESPACE_NAME     BYTES     MAX_BYTES     BLOCKS     MAX_BLOCKS
APPS_TS_TX_DATA     929038336     -1     113408     -1
SQL>select * from user_ts_quotas
        where tablespace_name = 'SYSTEM'
No Rows Returned.

Hi,
Thanks for the response. There is no QUOTA defined for SYSTEM user, so it is UNLIMITED, No?
Below are the details of "SYSTEM" tablespace. Is there any issue with this?
TABLESPACE_NAME           BLOCK_SIZE INITIAL_EXTENT       NEXT_EXTENT           MIN_EXTENTS            MAX_EXTENTS
SYSTEM                  8192               16384         16384                1                     505

SERVICE PO VALUE EXCEEDING IN SERVICE ENTRY SHEET

Hi all
How to restrict the Service Entry sheet value which is exceeding PO value (In Service PO Unlimited & Price change option are selected)
Here scenario is user will place order for say 1 set with value of 50 Lakh with only one service line item & will select the unlimited & price change option.
Now he will receive invoice in parts & will post accordingly with quantity 1 set each time & value as per each invoice. in this case value of invoice raises can be more than po Value so how to restrict the same.
OR How to map this type of scenario otherwise to avoid above
Kindly suggest
Thanks & regards,
Rajesh

Dear,
Please check with S.-Based IV check box selected in Invoice tab of Item details. This option useful for
Indicator for Service-Based Invoice Verification
Indicates that service-based invoice verification is defined for a purchase order item.
In service-based invoice verification, the quantities and values of services performed and ordered to date are available for checking purposes. As in the case of invoice verification for materials, you are able to change quantities and values within the permitted tolerances.
In addition, if service-based invoice verification is active, the acceptance posting is carried out at the level of the services in the entry sheet, and the quantities and values of the accepted and invoiced services are shown in the PO history.
And I suggest to enter Limitations for Servce to limit the :
Overall Limit
Maximum value that the total of all unplanned services (or the value of the material) covered by this document item may not exceed.
Limits can be used in service lines and the items of blanket purchase orders.
When services actually performed are entered in service entry sheets (or at the time of goods receipt in the case of materials), the system checks the entered values with regard to adherence to this maximum value. If the overall limit is exceeded, it issues an appropriate message.
If you have also fixed sub-limits within the overall limit for an item, each time services are entered or goods receipts are recorded the system checks whether the individual sub-limits and the overall limit have/has been adhered to.
By entering in Limits tab of item details.
Hope this will solve your issue.
Regards,
Syed Hussain.

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

Contract value exceeding in Release order

Hi All,
The target value of the value contract is 200,000 INR. After reaching to the 190,000 INR ( Making different Release order ) the user has made one more purchase order for this value contract with the value 50,000. The system hasnt given any warning /error message that the contract value exceeding...
In general system should have to give the error message that the contract value is exceeding???
The message 06-042 & 06-155 set as error message.
also if your trying to make release order of more than 200,000 INR then it is giving error message 06-42 the value is exceeding
Please suggest
Thanks & Regards
Rajesh

Please check your release order qty set in contract item / header details

Important--Bug(ORA-22813) fixes in Oracle Database 10g Release 10.2.0.4

Hi,
I found that in SELECT STATEMENTs where we use "xmlagg() functions with a GROUP BY/ORDER BY,it fails with ORA-22813 if the result is too large.
This happens as there is a hard coded limit on the result size. (max 30k)
Next,i confirmed that and when i removed a portion of the XML agg() values and executed it---Wonders,it runs perfectly fine.
This means that ""xmlagg() functions with a GROUP BY/ORDER BY,fails with ORA-22813 since the result is too large.
I have come to know that patch "Release 10.2.0.4" has the fix for Bug-22813 for "xmlagg() functions with a GROUP BY/ORDER BY".
Could you all please confirm that "Oracle Database 10g Release 10.2.0.4" (patch 10.2.04) fixes the issue?
Based on your confirmation,i can go ahead to get the patch installed.
Current Version:-Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
Thanks
Mainak

Your query should be written something like this..
select d.*
from fbnk_customer,
       XMLTABLE
          '//c3'
          passing XMLRECORD
          columns
          C3_VALUE varchar2(60) path 'text()'
       ) d
where recid='1001400'; Although it would be better to use an extact path expression rather than '//c3'

Free Goods to be issues if Sales value exceed target Value

HI,
User wanted us to configure the sales order such that when the total sales order vlaue exceed a certain amount, the system will automatic include a certain free items to the order as FOC item.
How do I go about configuring it?
Thanks

Hi Colin,
1: With standard SAP your requirement will not be fulfilled.
2: To do this you need some ABAP development.
Ask your ABAPER to write a code in user exit MV45AFZZ
where check the Value of the Sales order. If the Sales order value exceeds a specific value then add the FOC items in the Sales order where the item category should be TANN (or equivalent).
You might need a custom Z-table where you can store what Materials are to be added as FOC items in sales order & at what value.
regards
Edited by: Innovation is key on Mar 4, 2011 9:22 AM

ORA-22290: operation would exceed the maximum number of opened files or LOB

i am getting this error in a procedure.
ORA-22290: operation would exceed the maximum number of opened files or LOBs
22290, 00000, "operation would exceed the maximum number of opened files or LOBs"
// *Cause: The number of open files or LOBs has reached the maximum limit.
// *Action: Close some of the opened files or LOBs and retry the operation.
NAME TYPE VALUE
session_max_open_files integer 10
Procuedure:
CREATE OR REPLACE PROCEDURE WMSOWN."PROC_WMS_XML_READ"
P_EVENT_KEY IN VARCHAR2,
X_STATUS_MSG OUT VARCHAR2,
X_STATUS OUT NUMBER
)AS
l_parser dbms_xmlparser.Parser;
domdoc xmldom.DOMDocument;
nodelist XMLDOM.DOMNODELIST;
node XMLDOM.DOMNODE;
n_child XMLDOM.DOMNODE;
elements XMLDOM.DOMELEMENT;
name_node_map XMLDOM.DOMNAMEDNODEMAP;
parent_seg varchar2(4000);
tag_name_bkp varchar2(4000); -- LOOK OUT BRAD IS CODING AGAIN
chile_seg VARCHAR2(4000);
p_seg VARCHAR2(4000);
p_seg1 VARCHAR2(4000);
p_seg2 VARCHAR2(30);
p_int_name VARCHAR2(50);
col_value VARCHAR2(100):=NULL;
len1 NUMBER;
cnt NUMBER;
seg_id_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
sequence_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_sequence NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_seq_set VARCHAR2(3); --brad coding
parent_id number; ---brad coding
valid_seg NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
data_status VARCHAR2(10);
v_main_seg VARCHAR2(50);
v_seq_no NUMBER;
V_CLOBLOCATOR CLOB;
V_FILELOCATOR BFILE;
v_amount_to_load NUMBER;
dest_offset NUMBER := 1;
src_offset NUMBER := 1;
lang_context NUMBER := DBMS_LOB.DEFAULT_LANG_CTX;
warning NUMBER;
v_event_name USR_OUB_FILE_PROCESS_DETAILS.EVENT_NAME%TYPE;
v_file_name USR_OUB_FILE_PROCESS_DETAILS.FILE_NAME%TYPE;
DIRECTORY_PATH_INVALID EXCEPTION;
PRAGMA EXCEPTION_INIT(DIRECTORY_PATH_INVALID,-22285);
NO_PRIVILEGES EXCEPTION;
PRAGMA EXCEPTION_INIT(NO_PRIVILEGES,-22286);
INVALID_DIRECTORY EXCEPTION;
PRAGMA EXCEPTION_INIT(INVALID_DIRECTORY,-22287);
FILE_NOT_FOUND EXCEPTION;
PRAGMA EXCEPTION_INIT(FILE_NOT_FOUND,-22289);
P_DIRECTORY VARCHAR2(50) :='WMS_XML_DIR_OUB';
v_whid poldat_view.wh_id%type;
BEGIN
--NAME : PROC_WMS_XML_READ.PLS
--DESCRIPTION :
-- Procedure PROC_WMS_XML_READ search XML files from remote location.
-- Open,Parse and Read XML files. Store all XML values into tables.
-- Developed by Dharmesh Patidar(jw782)
-- History: New condition is added i.e. p_seg:=parent_seg to maintain PARENT and CHILD relationship
-- by Vishwanath Dubey(jl246) on 17-June-2011
-- BRAD_XML_DEBUG table removed for CLEANING Activity by DHARMESH PATIDAR(JW782) ON 29-JUNE-2011.
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID START*/
BEGIN
SELECT event_name,file_name,WAREHOUSE_ID
INTO v_event_name, v_file_name,v_whid
FROM usr_oub_file_process_details
WHERE event_id=p_event_key
AND process_flag='U';
EXCEPTION
WHEN NO_DATA_FOUND THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Record is not available in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN TOO_MANY_ROWS THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : More than one Records found in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN VALUE_ERROR THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Varibale length is small or data type mismatch while selecting event id and event name in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting event name and event id ';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID END*/
/*LOGIC TO READ XML FROM REMOTE LOCATION START*/
DBMS_LOB.CREATETEMPORARY(V_CLOBLOCATOR, TRUE);
V_FILELOCATOR := BFILENAME(P_DIRECTORY,V_FILE_NAME);
DBMS_LOB.OPEN(V_FILELOCATOR,DBMS_LOB.FILE_READONLY);
V_AMOUNT_TO_LOAD := DBMS_LOB.GETLENGTH(V_FILELOCATOR);
DBMS_LOB.LOADCLOBFROMFILE(V_CLOBLOCATOR,
V_FILELOCATOR ,
V_AMOUNT_TO_LOAD,
DEST_OFFSET,
SRC_OFFSET,
0,
LANG_CONTEXT,
WARNING);
dbms_lob.close(V_FILELOCATOR);
/*LOGIC TO READ XML FROM REMOTE LOCATION END*/
/*Temporary Code to help with debug Clear the table before populating it with new data*/
--delete table BRAD_XML_DEBUG;
cnt:=1;
seg_id_bkp:=0;
data_status:='N';
v_seq_no:=0;
prev_seq_set:='NO';
/*create new parser.*/
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, replace(V_CLOBLOCATOR,'&','1x2x3x4x5'));
/*Parse the document and create a new DOM document.*/
domdoc :=dbms_xmlparser.getDocument(l_parser);
/* get all elements in the DOM*/
nodelist := XMLDOM.getElementsByTagName(DOMDoc, '*');
len1 := XMLDOM.getLength(nodelist);
/* loop through elements of the DOM */
FOR j in 1..len1-1 LOOP --MAIN LOOP START
BEGIN
/*below sql will fetch Node from table to travel xml data*/
BEGIN
SELECT int_name,tag_name
INTO p_int_name, p_seg1
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND seq_no =cnt;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN OTHERS THEN
NULL;
END;
IF cnt=1 THEN
v_main_seg:=p_seg1;
END IF;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN no_data_found THEN
null;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting interface name and tag name'||sqlerrm;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*LOGICS TO READ XML START*/
node:=XMLDOM.item(nodelist, j);
elements:=XMLDOM.makeElement(node);
parent_seg:=(xmldom.getTagName(elements));
tag_name_bkp:=(xmldom.getTagName(elements));
name_node_map:=xmldom.getAttributes(node);
n_child:=xmldom.getFirstChild(node);
col_value:=xmldom.getNodeValue(n_child);
/*get the sequence number from the interface hierarchy table */
SELECT count(1)
INTO valid_seg
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
if valid_seg>0 then
begin
SELECT seq_no
INTO sequence_bkp
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
seg_id_bkp:=seg_id_bkp+1;
p_seg:=parent_seg;--Modified by Vishwanath Dubey dated 16-jun-2011
end;
end if;
if prev_seq_set = 'NO' then
begin
prev_sequence := sequence_bkp;
prev_seq_set := 'YES';
end;
end if;
if sequence_bkp < prev_sequence then --you just moved up level(s) in the message structure
begin
select max(seg_id)
into parent_id
from usr_wms_global_xml_det
where seg_sequence = sequence_bkp-1;
prev_sequence := sequence_bkp;
end;
end if;
if sequence_bkp > prev_sequence then --you just moved down a level in the message structure
parent_id := seg_id_bkp-1;
prev_sequence := sequence_bkp;
end if;
/*end getting the hierarchy table sequence */
/*LOGICS TO READ XML END */
IF (parent_seg =p_seg1) or (parent_seg=p_seg2) THEN
if parent_seg=v_main_seg then
v_seq_no:=v_seq_no+1;
end if;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,parent_seg,seg_id_bkp,sequence_bkp,parent_id,'','','',J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END ;
p_seg:=parent_seg;
p_seg2:=P_SEG1;
cnt:=cnt+1;
ELSE
chile_seg:=parent_seg;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,p_seg,seg_id_bkp,sequence_bkp,parent_id,'',chile_seg,replace(TRIM(Col_Value),'1x2x3x4x5','&'),J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
END IF;
END LOOP; --MAIN LOOP END
dbms_xmldom.freeDocument(DOMDoc);
x_status:=0;
EXCEPTION
WHEN DIRECTORY_PATH_INVALID THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ DIRECTORY PATH IS INVALID';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN FILE_NOT_FOUND THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ INVALID XML FILE NAME OR FILE DOES NOT EXISTS';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN NO_PRIVILEGES THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ Insufficient privileges on file or directory NAME- '||p_directory||' to perform FILEOPEN operation.';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ '|| SQLERRM;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
dbms_xmlparser.freeParser(l_parser);
dbms_xmldom.freeDocument(DOMDoc);
RETURN;
END PROC_WMS_XML_READ;
Edited by: user13427480 on Feb 8, 2013 7:08 PM

when you post sql statement use also similar threads :
ORA-22290: operation would exceed the maximum number of opened files or LOB
https://kr.forums.oracle.com/forums/thread.jspa?messageID=10842417

ORA-48108: invalid value given for the diagnostic_dest init.ora parameter

Hi All,
I am trying to start my oracle 11g database on windows 7 PC and i am getting below exception
SQL> startup mount
ORA-48108: invalid value given for the diagnostic_dest init.ora parameter
ORA-48140: the specified ADR Base directory does not exist [d:\oracle\app\product\11.2.0\dbhome_1\database\<oracle_base>]
ORA-48187: specified directory does not exist
OSD-00002: additional error information
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is incorrect.
SQL>
Earlier it was working fine. For learning purpose, i have created spfile using pfile and after that i got this issue.
Please help.
Regards,
Sunil

sunil907 wrote:
Hi,
I have provided diagnostic_dest folder location (physical path). Now i am getting some different kind of error on startup.
SQL> startup
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size                  2182592 bytes
Variable Size             616563264 bytes
Database Buffers          444596224 bytes
Redo Buffers                5595136 bytes
ORA-00205: error in identifying control file, check alert log for more info
Please help
What does your own research of 'ORA-00205' indicate?
the text of the error message is pretty self explanatory .. it couldn't find the control file.
The control files are specified by the "control_files" initialilzation paramter. When you get this error, the instance has started but was unable to mount the control file. since the init file (spfile) was processed and the instance started you can easily see what it thinks are the control files.
oracle:fubar$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 16 12:51:37 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 835104768 bytes
Fixed Size                  2217952 bytes
Variable Size             490735648 bytes
Database Buffers          339738624 bytes
Redo Buffers                2412544 bytes
ORA-00205: error in identifying control file, check alert log for more info
SQL> show parameter control
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
control_files                        string      /u01/app/oracle/oradata/FUBAR/
                                                 controlfile/o1_mf_8ybx4t7w_.ct
                                                 x, /u01/app/oracle/flash_recov
                                                 ery_area/FUBAR/controlfile/o1_
                                                 mf_8ybx4tom_.ctl
control_management_pack_access       string      NONE
SQL>
So what did you do in fixing your original problem that caused your control_files parameter to go south?

ORA-22813: operand value exceeds system limits

Similar Messages

Maybe you are looking for