Update attribute value in xml db in Oracle 10g

I have a table with XML blob data
The root element is invoice with an element billInfo and attribute type0
I'm trying to update the attribute value using the following sql but it is not working.
the sql goes to sucess but the value is not updated.
Looking for a solution and I appreciate your help
update sc.table_name
set xml_cb= updateXML(xml_cb,'/invoice/billInfo/@type0','A')
where id = 1 succeeded.
select id,
extractValue(xml_cb,'/invoice/billInfo/@type0') type_val
from sc.table_name
where id =1;
ID TYPE_VAL
1 K

What database version are you using?
could you show us the outcome of:
SQL> select dbms_metadata.get_ddl('TABLE','TABLE_NAME','SC') from dual;
and/or a
SQL> describe SC.TABLE_NAME

Similar Messages

How to update the value in xml file using transformer after setNodeValue

Hi,
This is my code
I want to set update the values in xml file using transformer..
Any one can help me
This is my Xml file
<?xml version="1.0" encoding="UTF-8"?>
<place>
<name>chennai</name>
</place>
Jsp Page
<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%@ page import="javax.xml.parsers.DocumentBuilderFactory,
javax.xml.parsers.DocumentBuilder,org.w3c.dom.*,org.w3c.dom.Element"
%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<% String str="";
String str1="";
try
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse("http://localhost:8084/XmlApplication1/sss.xml");
out.println("Before change");
NodeList n11 = doc.getElementsByTagName("name");
Node n22= n11.item(0).getFirstChild();
str1 = n22.getNodeValue();
out.println(str1);
out.println("After change");
String name = "Banglore";
NodeList nlst = doc.getElementsByTagName("name");
Node node= nlst.item(0).getFirstChild();
node.setNodeValue(name);
NodeList n1 = doc.getElementsByTagName("name");
Node n2= n1.item(0).getFirstChild();
str = n2.getNodeValue();
out.println(str);
catch(Exception e)
out.println(e) ;
%>
<h1><%=str%></h1>
<%--
This example uses JSTL, uncomment the taglib directive above.
To test, display the page like this: index.jsp?sayHello=true&name=Murphy
--%>
<%--
<c:if test="${param.sayHello}">

Hello ${param.name}!
</c:if>
--%>
</body>
</html>

hi check this exit...
IWO10012

Help In XML schema using oracle 10g

i want to give seminar in XML schema using oracle 10g. n i m very new in this topic. so help me out which topic i include & any document regarding this

XML Schema has various aspects.
1. Creating an XML Schema, which may be done in JDeveloper.
2. Initializing an XML document from an XML Schema, which may also be done in JDeveloper.
For creating and initializing an XML Schema please refer
http://www.regdeveloper.co.uk/2007/10/01/build_xml_schema_jdeveloper/
3. Validating an XML document with an XML Schema.
http://www.oracle.com/technology/pub/articles/vohra_xmlschema.html

Selcect/ update attribute value using xpath navigator/ linq to xml

Hi Folks,
below is my xml string and the highlighted bold attribute value needs to update. Since this element contains prefix im not able to select teh particular element. if i remove the prefixx im able to select but i need to keep prefix.
<IOP:MtvnSvcReq xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:IOP="mtvnCWExternInteropReq" xmlns:IOP1="mtvnExtInteropReqData" xmlns:PR1="mtvnPRInteropReqData">
<IOP:Svc>
<IOP1:PR1>
<PR1:PRExternSSOReqData>
<PR1:UserId>abcd</PR1:UserId>
</PR1:PRExternSSOReqData>
</IOP1:PR1>
</IOP:Svc>
</IOP:MtvnSvcReq>
Thanks

Hi Pulikk,
Do you mean you want to change the attribute value(abcd)? If so,
Please try the following code, i tested on my side, it changed successfully.
//Here is the variable with which you assign a new value
string newValue = string.Empty;
XDocument objDoc = XDocument.Load(@"yourdata.xml");
XNamespace IOP = "mtvnCWExternInteropReq";
XNamespace IOP1 = "mtvnExtInteropReqData";
XNamespace PR1 = "mtvnPRInteropReqData";
foreach (var node in objDoc.Descendants(PR1 + "UserId"))
node.Value = newValue;
objDoc.Save(@"yourdata.xml");
Have a nice day!
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Updating Attribute value

I have a simple XML document. file.
<result success="TRUE">
<plan>
<step number="0" name="SelectTransportA"/>
<step number="1" name="SelectFlight"/>
<step number="2" name="GetMedicalFlightAccountB"/>
<step number="3" name="SelectFlight"/>
</plan>
</result>What i want is to update any "name" attribute value at runtime. I receive "number" attribute value, so on the basis of the received number, i want my name attribute value to be updated.
Just like updating a value in hashtable or vector given an index.
Regards.

It depends what you want to do, Do you just want to update the file? Then XSLT is probably the easiest. Do you want to update this in memory? Then DOM's Node.setAttribute is probably best.

Update Attribute values of AR transaction.

Hi All,
We have a requirement to update the attribute of the AR transaction and have written the following code:
DECLARE
   l_msg_count               NUMBER;
   l_msg_data                VARCHAR2 (2000);
   l_return_status           VARCHAR2 (10);
   v_batch_rec               ra_batches_all%ROWTYPE;
   v_header_rec              ra_customer_trx%ROWTYPE;
   v_errors                  arp_trx_validate.message_tbl_type;
   v_lines_tbl               ar_transaction_pub.line_tbl_type;
   v_tax_lines_tbl           ar_transaction_pub.line_tbl_type;
   v_freight_lines_tbl       ar_transaction_pub.line_tbl_type;
   v_salescredit_lines_tbl   ar_transaction_pub.salescredit_tbl_type;
   v_dist_tbl                ar_transaction_pub.dist_tbl_type;
   v_commitment_rec          arp_process_commitment.commitment_rec_type;
   v_date                    DATE;
   out_message               VARCHAR2 (4000);
   l_msg_index_out           INTEGER;
   cursor c_trx is
   select * from ra_customer_trx_all
   where customer_trx_id = 272499;--234915;
BEGIN
   fnd_msg_pub.initialize;
   fnd_client_info.set_org_context ('328');
   fnd_global.apps_initialize (37850,50261,222, 0);
   v_date := SYSDATE - 30;--This must be a date in the open gl period
   for i in c_trx
   loop
    v_header_rec.interface_header_attribute8:= i.interface_header_attribute8;
    v_header_rec.interface_header_context:= i.interface_header_context;
    v_header_rec.default_ussgl_trx_code_context:= i.default_ussgl_trx_code_context;
    v_header_rec.interface_header_attribute10:= i.interface_header_attribute10;
    v_header_rec.interface_header_attribute11:= i.interface_header_attribute11;
    v_header_rec.interface_header_attribute12:= i.interface_header_attribute12;
    v_header_rec.interface_header_attribute13:= i.interface_header_attribute13;
    v_header_rec.interface_header_attribute14:= i.interface_header_attribute14;
    v_header_rec.interface_header_attribute15:= i.interface_header_attribute15;
    v_header_rec.interface_header_attribute9:= i.interface_header_attribute9;
    v_header_rec.default_ussgl_transaction_code:= i.default_ussgl_transaction_code;
    v_header_rec.recurred_from_trx_number:= i.recurred_from_trx_number;
    v_header_rec.attribute11:= i.attribute11;
    v_header_rec.attribute12:= i.attribute12;
    v_header_rec.attribute13:= i.attribute13;
    v_header_rec.attribute14:= i.attribute14;
    v_header_rec.attribute15:= i.attribute15;
    v_header_rec.interface_header_attribute1:= i.interface_header_attribute1;
    v_header_rec.interface_header_attribute2:= i.interface_header_attribute2;
    v_header_rec.interface_header_attribute3:= i.interface_header_attribute3;
    v_header_rec.interface_header_attribute4:= i.interface_header_attribute4;
    v_header_rec.interface_header_attribute5:= i.interface_header_attribute5;
    v_header_rec.interface_header_attribute6:= i.interface_header_attribute6;
    v_header_rec.attribute_category:= i.attribute_category;
    v_header_rec.attribute1:= i.attribute1;
    v_header_rec.attribute2:= 'NEW';
    v_header_rec.attribute3:= i.attribute3;
    v_header_rec.attribute4:= i.attribute4;
    v_header_rec.attribute5:= i.attribute5;
    v_header_rec.attribute6:= i.attribute6;
    v_header_rec.attribute7:= i.attribute7;
    v_header_rec.attribute8:= i.attribute8;
    v_header_rec.attribute9:= i.attribute9;
    v_header_rec.attribute10:= i.attribute10;
    v_header_rec.customer_trx_id:= i.customer_trx_id;
    v_header_rec.trx_number:= i.trx_number;
    v_header_rec.paying_site_use_id:= i.paying_site_use_id;
    v_header_rec.bill_to_customer_id:= i.bill_to_customer_id;
    v_header_rec.cust_trx_type_id:= i.cust_trx_type_id;
    v_header_rec.reversed_cash_receipt_id:= i.reversed_cash_receipt_id;
    v_header_rec.agreement_id:= i.agreement_id;
    v_header_rec.batch_id:= i.batch_id;
    v_header_rec.status_trx:= i.status_trx;
    v_header_rec.doc_sequence_id:= i.doc_sequence_id;
    v_header_rec.doc_sequence_value:= i.doc_sequence_value;
    v_header_rec.paying_customer_id:= i.paying_customer_id;
    v_header_rec.related_batch_source_id:= i.related_batch_source_id;
    v_header_rec.default_tax_exempt_flag:= i.default_tax_exempt_flag;
    v_header_rec.created_from:= i.created_from;
    v_header_rec.org_id:= i.org_id;
    v_header_rec.request_id:= i.request_id;
    v_header_rec.program_application_id:= i.program_application_id;
    v_header_rec.program_id:= i.program_id;
    v_header_rec.program_update_date:= i.program_update_date;
    v_header_rec.finance_charges:= i.finance_charges;
    v_header_rec.complete_flag:= i.complete_flag;
    v_header_rec.posting_control_id:= i.posting_control_id;
    v_header_rec.bill_to_address_id:= i.bill_to_address_id;
    v_header_rec.ra_post_loop_number:= i.ra_post_loop_number;
    v_header_rec.ship_to_address_id:= i.ship_to_address_id;
    v_header_rec.credit_method_for_rules:= i.credit_method_for_rules;
    v_header_rec.credit_method_for_installments:= i.credit_method_for_installments;
    v_header_rec.receipt_method_id:= i.receipt_method_id;
    v_header_rec.related_customer_trx_id:= i.related_customer_trx_id;
    v_header_rec.invoicing_rule_id:= i.invoicing_rule_id;
    v_header_rec.ship_via:= i.ship_via;
    v_header_rec.ship_date_actual:= i.ship_date_actual;
    v_header_rec.waybill_number:= i.waybill_number;
    v_header_rec.fob_point:= i.fob_point;
    v_header_rec.customer_bank_account_id:= i.customer_bank_account_id;
--    v_header_rec.printing_option:= i.printing_option;
    v_header_rec.printing_count:= i.printing_count;
    v_header_rec.printing_pending:= i.printing_pending;
    v_header_rec.purchase_order:= i.purchase_order;
    v_header_rec.purchase_order_revision:= i.purchase_order_revision;
    v_header_rec.purchase_order_date:= i.purchase_order_date;
    v_header_rec.customer_reference:= i.customer_reference;
    v_header_rec.customer_reference_date:= i.customer_reference_date;
    v_header_rec.comments:= i.comments;
    v_header_rec.internal_notes:= i.internal_notes;
    v_header_rec.exchange_rate_type:= i.exchange_rate_type;
    v_header_rec.exchange_date:= i.exchange_date;
    v_header_rec.exchange_rate:= i.exchange_rate;
    v_header_rec.territory_id:= i.territory_id;
    v_header_rec.invoice_currency_code:= i.invoice_currency_code;
    v_header_rec.initial_customer_trx_id:= i.initial_customer_trx_id;
    v_header_rec.end_date_commitment:= i.end_date_commitment;
    v_header_rec.start_date_commitment:= i.start_date_commitment;
    v_header_rec.last_printed_sequence_num:= i.last_printed_sequence_num;
    v_header_rec.orig_system_batch_name:= i.orig_system_batch_name;
    v_header_rec.post_request_id:= i.post_request_id;
    v_header_rec.last_update_date:= i.last_update_date;
    v_header_rec.last_updated_by:= i.last_updated_by;
    v_header_rec.creation_date:= i.creation_date;
    v_header_rec.created_by:= i.created_by;
    v_header_rec.last_update_login:= i.last_update_login;
    v_header_rec.trx_date:= i.trx_date;
    v_header_rec.set_of_books_id:= i.set_of_books_id;
    v_header_rec.bill_to_contact_id:= i.bill_to_contact_id;
    v_header_rec.batch_source_id:= i.batch_source_id;
    v_header_rec.reason_code:= i.reason_code;
    v_header_rec.sold_to_customer_id:= i.sold_to_customer_id;
    v_header_rec.sold_to_contact_id:= i.sold_to_contact_id;
    v_header_rec.sold_to_site_use_id:= i.sold_to_site_use_id;
    v_header_rec.bill_to_site_use_id:= i.bill_to_site_use_id;
    v_header_rec.ship_to_customer_id:= i.ship_to_customer_id;
    v_header_rec.ship_to_contact_id:= i.ship_to_contact_id;
    v_header_rec.ship_to_site_use_id:= i.ship_to_site_use_id;
    v_header_rec.shipment_id:= i.shipment_id;
    v_header_rec.remit_to_address_id:= i.remit_to_address_id;
    v_header_rec.term_id:= i.term_id;
    v_header_rec.term_due_date:= i.term_due_date;
    v_header_rec.previous_customer_trx_id:= i.previous_customer_trx_id;
    v_header_rec.primary_salesrep_id:= i.primary_salesrep_id;
    v_header_rec.printing_original_date:= i.printing_original_date;
    v_header_rec.printing_last_printed:= i.printing_last_printed;
    v_header_rec.global_attribute1:= i.global_attribute1;
    v_header_rec.global_attribute2:= i.global_attribute2;
    v_header_rec.global_attribute3:= i.global_attribute3;
    v_header_rec.global_attribute4:= i.global_attribute4;
    v_header_rec.global_attribute5:= i.global_attribute5;
    v_header_rec.global_attribute6:= i.global_attribute6;
    v_header_rec.global_attribute7:= i.global_attribute7;
    v_header_rec.global_attribute8:= i.global_attribute8;
    v_header_rec.global_attribute9:= i.global_attribute9;
    v_header_rec.global_attribute10:= i.global_attribute10;
    v_header_rec.global_attribute11:= i.global_attribute11;
    v_header_rec.global_attribute12:= i.global_attribute12;
    v_header_rec.global_attribute13:= i.global_attribute13;
    v_header_rec.global_attribute14:= i.global_attribute14;
    v_header_rec.global_attribute15:= i.global_attribute15;
    v_header_rec.global_attribute16:= i.global_attribute16;
    v_header_rec.global_attribute17:= i.global_attribute17;
    v_header_rec.global_attribute18:= i.global_attribute18;
    v_header_rec.global_attribute19:= i.global_attribute19;
    v_header_rec.global_attribute20:= i.global_attribute20;
    v_header_rec.global_attribute_category:= i.global_attribute_category;
    v_header_rec.wh_update_date:= i.wh_update_date;
    v_header_rec.edi_processed_flag:= i.edi_processed_flag;
    v_header_rec.edi_processed_status:= i.edi_processed_status;
    v_header_rec.global_attribute21:= i.global_attribute21;
    v_header_rec.global_attribute22:= i.global_attribute22;
    v_header_rec.global_attribute23:= i.global_attribute23;
    v_header_rec.global_attribute24:= i.global_attribute24;
    v_header_rec.global_attribute25:= i.global_attribute25;
    v_header_rec.global_attribute26:= i.global_attribute26;
    v_header_rec.global_attribute27:= i.global_attribute27;
    v_header_rec.global_attribute28:= i.global_attribute28;
    v_header_rec.global_attribute29:= i.global_attribute29;
    v_header_rec.global_attribute30:= i.global_attribute30;
    v_header_rec.payment_server_order_num:= i.payment_server_order_num;
    v_header_rec.approval_code:= i.approval_code;
    v_header_rec.address_verification_code:= i.address_verification_code;
    v_header_rec.old_trx_number:= i.old_trx_number;
    v_header_rec.br_amount:= i.br_amount;
    v_header_rec.br_unpaid_flag:= i.br_unpaid_flag;
    v_header_rec.br_on_hold_flag:= i.br_on_hold_flag;
    v_header_rec.drawee_id:= i.drawee_id;
    v_header_rec.drawee_contact_id:= i.drawee_contact_id;
    v_header_rec.drawee_site_use_id:= i.drawee_site_use_id;
    v_header_rec.drawee_bank_account_id:= i.drawee_bank_account_id;
    v_header_rec.remittance_bank_account_id:= i.remittance_bank_account_id;
    v_header_rec.override_remit_account_flag:= i.override_remit_account_flag;
    v_header_rec.special_instructions:= i.special_instructions;
    v_header_rec.remittance_batch_id:= i.remittance_batch_id;
    v_header_rec.prepayment_flag:= i.prepayment_flag;
    v_header_rec.ct_reference:= i.ct_reference;
    v_header_rec.contract_id:= i.contract_id;
    v_header_rec.bill_template_id:= i.bill_template_id;
    v_header_rec.cc_error_flag:= i.cc_error_flag;
    v_header_rec.cc_error_code:= i.cc_error_code;
    v_header_rec.cc_error_text:= i.cc_error_text;
   dbms_output.put_line(v_header_rec.term_id);
   end loop;
   ar_transaction_pub.update_transaction
                         (p_api_name                   => 'AR_TRANSACTION_PUB',
                          p_api_version                => 1.0,
                          p_init_msg_list              => fnd_api.g_true,
                          p_commit                     => fnd_api.g_true,
                          p_validation_level           => fnd_api.g_valid_level_full,
                          p_batch_rec                  => v_batch_rec,
                          p_header_rec                 => v_header_rec,
                          p_receivable_gl_date         => v_date,
                          p_commitment_rec             => v_commitment_rec,
                          p_lines_tbl                  => v_lines_tbl,
                          p_tax_lines_tbl              => v_tax_lines_tbl,
                          p_freight_lines_tbl          => v_freight_lines_tbl,
                          p_salescredit_lines_tbl      => v_salescredit_lines_tbl,
                          p_dist_tbl                   => v_dist_tbl,
                          p_return_status              => l_return_status,
                          p_msg_count                  => l_msg_count,
                          p_msg_data                   => l_msg_data,
                          p_errors                     => v_errors,
                          p_recalc_tax_flag            => fnd_api.g_true,
                          p_rerun_autoacc_flag         => fnd_api.g_true,
                          p_backout_sc_flag            => fnd_api.g_true,
                          p_backout_dist_flag          => fnd_api.g_true
   IF (fnd_msg_pub.count_msg > 0)
   THEN
      FOR i IN 1 .. fnd_msg_pub.count_msg
      LOOP
         fnd_msg_pub.get (p_msg_index          => i,
                          p_encoded            => 'F',
                          p_data               => out_message,
                          p_msg_index_out      => l_msg_index_out
         DBMS_OUTPUT.put_line ('l_msg_data :' || out_message);
      END LOOP;
   END IF;
END;However getting the below error:
l_msg_data :Invalid payment terms id. (TERM_ID: &INVALID_VALUE)
l_msg_data :Invalid Transaction Status &INVALID_VALUE .
l_msg_data :Validation error(s) occurred. Rolling back and setting status to ERROR
This was working fine sometimes back. Can anyone point the right direction. I am able to update the attribute value fron the front end.
Thanks,
Subhasish

Hi All,
Any thoughts on this ??
Regards,
Subhasish

How to Get and Update properties values from XML tag Using Xquery or PL Sql

Hi
I have this tag
<Solicitud Pais = "1">
How i can get Pais value?
How i can update Pais Value?
Y can use Xquery funtions or PL SQL for this?
Thak's
Angel

How i can get Pais value? ExtractValue
How i can update Pais Value?UpdateXML
Y can use Xquery funtions or PL SQL for this?Yes
Without knowing more about your requirements, where information resides, or even a version of Oracle, that is the best I'll do.

Reading XML File in Oracle 10g

Can anybody tell me How to Read an XML file into Oracle Table and update the Records.
Please guide me.

http://www.oracle.com/technology/sample_code/tech/java/codesnippet/xmldb/HowToLoadLargeXML.html
or else straighter way, go here:
XML DB
Edited by: Ora on Feb 16, 2011 1:32 AM

Load XML file to Oracle 10G XE

The load xml wizard in Oracle XE asks for a table in the HR schema to load into.
Well I create one using the 'Create Table' procedure with a script that runs and creates the table. Now I have a XML file that matches the table I created and try to load the file contents into the table. I get an error. Am I surprised? no, I am not. Nothing works the first time.
Is there a preferred format for the xml file that supports loading into a table?
There appears to be no help file, but then I may be mistaken.
Could someone show me where to find this help file?

The bug you are referencing occurs when an Enumerated Value also has min and max lengths specified..
Eg something like
<xsd:simpleType name="EnumType">
     <xsd:annotation>
         <xsd:documentation>ENUM_TYPE</xsd:documentation>
     </xsd:annotation>
     <xsd:restriction base="xsd:string">
         <xsd:enumeration value="AA"/>
         <xsd:enumeration value="AB"/>
         <xsd:enumeration value="AE"/>
         <xsd:enumeration value="AK"/>
         <xsd:enumeration value="AL"/>
     </xsd:restriction>
   </xsd:simpleType>
   <xsd:complexType name="TYPE1">
     <xsd:sequence>
         <xsd:element name="TYPE11">
           <xsd:simpleType>
               <xsd:restriction base="EnumType">
                 <xsd:minLength value="1"/>
                 <xsd:maxLength value="10"/>
               </xsd:restriction>
           </xsd:simpleType>
         </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
</xsd:schema> Do you have something like this in your XML Schema. If this is the case try removing the minLength, maxLength as they are redundant, which is probably why we didn't catch this one in internal testing, it sort of falls into the "if it hurts please don't do it" category :). Also the fix for this bug appears to have been backported on top of 9.2.0.6.0 so upgrading to 9.2.0.7.0 or 9.2.0.8.0 or the later releases of 10.1 or 10.2 should fix the problem.

XML SCHEMA registration for XML TYPE (storing XML files in Oracle 10g)

I have created the XML Schema for the XML file stored in Oracle 10g and also added this Schema into the database. I have related that schema with the column in the table which contains the XML file. When i execute the query to fetch the data from the stored file i am getting a blank resultset. Is registering the XML Schema is necessary, if yes then please let me know the process of doing it. I have tried following steps to register Schema, but it is not working
Step1:
DECLARE
v_return BOOLEAN;
BEGIN
v_return := dbms_xdb.createFolder('/home/');
v_return := dbms_xdb.createFolder('/home/DEV/');
v_return := dbms_xdb.createFolder('/home/DEV/xsd/');
v_return := dbms_xdb.createFolder('/home/DEV/messages/');
v_return := dbms_xdb.createFolder('/home/DEV/employees/');
COMMIT;
END;
STEP 2:
Connecting To XML DB
Step3:
Register XML schema
I am failing to execute step number 2 and hence not able to register the schema also.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by sudeepk:
If a java exception is thrown probably during ur install u might have forgotten
grant javauserpriv to scott;
grant javasyspriv to scott;
Thanks
[email protected]
<HR></BLOCKQUOTE>
Thank you!!!

Avoid Bug 7146375 ORA-4030 MEMORY LEAK IN (Xml generation) in oracle 10g

Hi All,
I have to generate an xml from database which contains around 4 lac records. I had written a query using XmlSerialize and XmlElement.
It does run properly for records less than 2 lacs.
But when the record count goes above 2 lacs..it is throwing the following error -
{ ORA-04030: out of process memory when trying to allocate 1032 bytes (qmxlu subheap,qmemNextBuf:alloc)
ORA-06512: at "SYS.XMLTYPE", line 111!}
For the above error - I have tried increasing pga from 480M to 800M, but still we are getting the same error.
After researching i found out -
Cause
This is caused by the following bug:
Bug 7146375 ORA-4030 AND MEMORY LEAK IN SESSION HEAP: "KOH DUR HEAP D"
Solution
Bug 7146375 is fixed in 11.2
So i tried out the query in another a db which has 11g installed and my query runs perfectly fine for records of upto 4 lacs.
But since we have oracle 10g on our clients machine, are there other ways to achieve this XML generation other than this?
Thanks.

913389 wrote:
After researching i found out -
Cause
This is caused by the following bug:
Bug 7146375 ORA-4030 AND MEMORY LEAK IN SESSION HEAP: "KOH DUR HEAP D"
Solution
Bug 7146375 is fixed in 11.2
So i tried out the query in another a db which has 11g installed and my query runs perfectly fine for records of upto 4 lacs.
But since we have oracle 10g on our clients machine, are there other ways to achieve this XML generation other than this?I doubt it. If Oracle have investigated and created a bug report that says the solution is to upgrade to 11.2, then that's the answer, otherwise they would indicate that a particular 10g patch set can also be used.

Required setting for Locale values for Arabic db in oracle 10g

I want to create a new db in Oracle 10g for storing the arabic data.
My client machine is Arabic Windows XP.
What are the steps that i will need to follow to make the db arabic supported.
What streps will be required if i choose to make it unicode supported?
Setting the following:-
1. Set Database Character Set to AL32UTF8 for the Oracle Server.
2. Set the NLS_LANG to ARABIC_LIBYA.UTF8 (on Arabic Windows xp)
Will do the work?

The database character set should be AL32UTF8 for Unicode support. This is a recommended setting.
As far as NLS_LANG is concerned, this strongly depends on how your client application is written (what technology, which Oracle access API). For example, for SQL*Plus, the NLS_LANG must be set to AR8MSWIN1256, as SQL*Plus does not support Unicode on Windows, only the ANSI code page. For SQL Developer, the NLS_LANG does not matter at all.
-- Sergiusz

Updated Attribute values in Z table not coming in Delta

Hi,
We have a generic master data datasource based on a view. View is based on two standanrd R3 tables. We also enhanced this datasource by adding few fields populated through user exit from a custom Z table.
The datasource was initialized (delta field being 'Change date field' i.e. AEDAT).
The issue is, if users update/modify few fields in Z table, then those records are not picked up as deltas because AEDAT field is not changed.
How should I pull such records? If I do a repair full, will it affect delta mechanism?
Regards,
Vikrant.

Hi AHP,
Thx for replying.
But is there any other way. At present I do not want to do any new development, its pretty urgent requirement.
Can't I do full-repair for such records?
Regards,
Vikrant.

Issue with Date Conversion when loading XML File into Oracle 10g Database

Hello all,
I have the interface shown in the screenshot below. In it, amongst other actions, I'm mapping an XML file element representing a date to an Oracle table column defined as DATE. The source and target columns are highlighted in the screenshot.
!http://img223.imageshack.us/img223/1565/odiscr275.jpg!
When I execute the interface, I get the following error message:
java.lang.IllegalArgumentException at java.sql.Date.valueOf(Date.java:103)
I'm assuming this refers to the date conversion!
I've already tried replacing SRC_TRADES.DEAL_DATE with TO_DATE( SRC_TRADES.DEAL_DATE, 'DD/MM/YYYY' ) in the Implementation tab. This function was not recognised when I executed the interface, so it didn't work! The date value in the XML file is in DD/MM/YYYY format.
I'm guessing that Oracle SQL Date functions don't work in the Implementation tab. Please could somebody let me know:
1. Which Date Conversion function I could use instead?
2. Where I can find a reference for the methods/functions I can use in the Implementation tab (if such a reference exists)?
Cheers.
James

Hi.
Try to change the execution area to staging area. After You change it, write in the mapping box just SRC_TRADERS.DEAL_DATE. When You use TO_DATE, the source field typu should be varchar2, not date (as it is in your source datastore)

ORA-06502: PL/SQL: numeric or value error While Exporting in Oracle 10g

Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in AR8MSWIN1256 character set and AL16UTF16 NCHAR character set
server uses AR8ISO8859P6 character set (possible charset conversion)
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. . exporting table DEF$_AQCALL 0 rows exported
. . exporting table SRC_RQST_SEQ 1 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table SRC_USERS 6 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table SRC_YEAR_LOOKUP 40 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table TENDER_DETAIL_TABLE 36 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table TENDER_MASTER_TABLE 34 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table TENDER_NEW_DETAIL_TABLE 4 rows exported
EXP-00091: Exporting questionable statistics.
. exporting synonyms
. exporting views
EXP-00056: ORACLE error 6502 encountered
ORA-06502: PL/SQL: numeric or value error
LPX-00210: expected '<' instead of 'n'
ORA-06512: at "SYS.UTL_XML", line 152
ORA-06512: at "SYS.DBMS_METADATA_INT", line 7195
ORA-06512: at "SYS.DBMS_METADATA_INT", line 9135
ORA-06512: at "SYS.DBMS_METADATA", line 1882
ORA-06512: at "SYS.DBMS_METADATA", line 3707
ORA-06512: at "SYS.DBMS_METADATA", line 3689
ORA-06512: at line 1
EXP-00056: ORACLE error 6502 encountered
ORA-06502: PL/SQL: numeric or value error
LPX-00210: expected '<' instead of 'n'
ORA-06512: at "SYS.UTL_XML", line 152
ORA-06512: at "SYS.DBMS_METADATA_INT", line 7195
ORA-06512: at "SYS.DBMS_METADATA_INT", line 9135
ORA-06512: at "SYS.DBMS_METADATA", line 1882
ORA-06512: at "SYS.DBMS_METADATA", line 3707
ORA-06512: at "SYS.DBMS_METADATA", line 3689
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
Plz reply me the appropriate Solution
Edited by: user8920919 on May 3, 2010 12:27 AM

hi,
EXP-00091: Exporting questionable statistics The client character set(NLS_LANG) does not match the server character;
select parameter,value from nls_database_parameters where parameter like '%CHARACTERSET%';
and check the client system character set
- Pavan Kumar N
- ORACLE OCP - 9i/10g
https://www.oracleinternals.blogspot.com

Update attribute value in xml db in Oracle 10g

Similar Messages

Maybe you are looking for