Error in assigning string literal.......

Hi,
Below is a normal stub that i am executing
DECLARE
PI_PACKAGE_CLOB CLOB;
BEGIN
PI_PACKAGE_CLOB := '<ROWSET><ROW><SITE_NO Key="Yes">1</SITE_NO><PACKAGE_NO Key="Yes">832</PACKAGE_NO><PARENT_PACKAGE_NO>0</PARENT_PACKAGE_NO><NAME>Testing - 1</NAME><USER_ID Key="Yes">A427907</USER_ID><PACKAGE_TYPE_NO>47</PACKAGE_TYPE_NO><PACKAGE_UI_TYPE_NO>2</PACKAGE_UI_TYPE_NO><STATUS>PRIVATE</STATUS><CONTENT_HEADER><HEAD><LINK </TABLE_CONTENT><DEFAULT_PACKAGE>1</DEFAULT_PACKAGE><LAYOUT_TYPE>CELL</LAYOUT_TYPE><CREATED_ON>2007-11-29T01:08:18</CREATED_ON><MODIFIED_ON>2007-11-29T02:06:14</MODIFIED_ON></ROW></ROWSET>';
PKS_PACKAGE.PRC_UPDATE_PACKAGE ( PI_PACKAGE_CLOB );
COMMIT;
END; In the above shown procedure i am running it through TOAD as shown above.
But it says string literal too long... The size of the PI_PACKAGE_CLOB is more than 32767............Is there any way that i can assign data to variable which are more than the size 32767...
Help needed plz................
Thanks,
The database version is 10.2
Message was edited by:
SHILPFID
Message was edited by:
SHILPFID

a) Turn off your CAPS LOCK as it's considered rude to shout.
b) format your code using [code][/code] or [pre][/pre] tags so that people can actually read it.
I assume this relates to your other query: I am struggling...........plzzzzz help
You can assign data larger than 32767 bytes by using CLOBs, so what exactly is the problem?

Similar Messages

SQL Error: ORA-01704: string literal too long

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

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

How to handle the SQL Error: ORA-01704: string literal too long

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Java (vers. 26 Sep 2004), see www.w3.org">
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta content="MSHTML 6.00.2900.2963" name="GENERATOR">
</head>
<body class="BodyContent">
HI please chek the query getting error like string literal too long update PRVDR_ENRLMNT_AGREEMENT B set b.terms=q'#
<div class="widget-title">
<h5>Medical Assistance Provider Enrollment & Trading Partner Agreement - Conditions:</h5>
<a href="# class="btn-minimize pull-right"></a></div>
<div class="widget-content">
<table width="100%" border="0">
<tbody>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32">In applying for enrollment as a provider or trading partner in the Medical Assistance Program (and programs for which the Michigan Department of Community Health (MDCH) is the fiscal intermediary), I represent and certify as follows:</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">1.</td>
<td class="LabelValue" valign="top" align="left" height="32">The applicant, and the employer (if applicable), certify that the undersigned has/have the authority to execute this Agreement.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">2.</td>
<td class="LabelValue" valign="top" align="left" height="32">Enrollment in the Medical Assistance Program does not guarantee participation in MDCH managed care programs nor does it replace or negate the contract process between a managed care entity and its providers or subcontractors.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">3.</td>
<td class="LabelValue" valign="top" align="left" height="32">All information furnished on this Medical Assistance Provider Enrollment & Trading Partner Agreement form is true and complete.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">4.</td>
<td class="LabelValue" valign="top" align="left" height="32">The providers and fiscal agents of ownership and control information agree to provide proper disclosure of provider's owners and other persons criminal related to Medicare, Medicaid or Title XX involvement. [42 CFR 455.100]</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">5.</td>
<td class="LabelValue" align="left" height="32">The applicant and the employer agree to provide proper disclosure of any criminal convictions related to Medicare (Title XVIII), Medicaid (Title XIX), and other State Health Care Programs (Title V, Title XX, and Title XXI) involvement. [42 CFR 455.106 and 42 U.S.C. ? 1320a-7]</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">6.</td>
<td class="LabelValue" align="left" height="32">I agree to read the Medicaid Provider Manual from the Michigan Department of Community Health (MDCH). I also agree to comply with 1) the terms and conditions of participation noted in the manual, and 2) MDCH's policies and procedures for the Medical Assistance Program contained in the manual, provider bulletins and other program notifications.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">7.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the provisions of 42 CFR 455.104, 42 CFR 455.105, 42 CFR 431.107 and Act No. 280 of the Public Acts of 1939, as amended, which state the conditions and requirements under which participation in the Medical Assistance Program is allowed.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">8.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the requirements of Section 6032 of the Deficit Reduction Act of 2005, codified at section 1902 (a)(68) of the Social Security Act which relates to the conditions and requirements of "Employee Education About False Claims Recovery."</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">9.</td>
<td class="LabelValue" align="left" height="32">I agree that, upon request and at a reasonable time and place, I will allow authorized state or federal government agents to inspect, copy, and/or take any records I maintain pertaining to the delivery of goods and services to, or on behalf of, a Medical Assistance Program beneficiary. These records also include any service contract(s) I have with any billing agent/service or service bureau, billing consultant, or other healthcare provider.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">10.</td>
<td class="LabelValue" align="left" height="32">I agree to include a clause in any contract I enter into which allows authorized state or federal government agents access to the subcontractor's accounting records and other documents needed to verify the nature and extent of costs and services furnished under the contract.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">11.</td>
<td class="LabelValue" align="left" height="32">I understand that the incentive payment requested using my National Provider Identifier (NPI) number will be made directly to the Tax ID Number (TIN) that was indicated during the registration process.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">12.</td>
<td class="LabelValue" align="left" height="32">I am not currently suspended, terminated, or excluded from the Medical Assistance Program by any state or by the U.S. Department of Health and Human Services.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">13.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with all policies and procedures of the Medical Assistance Program. I also agree that all disputes, including overpayments, may be adjudicated in administrative proceedings convened under Act No. 280 of the Public Acts of 1939, as amended, or in a court of competent jurisdiction. I further agree to reimburse the Medical Assistance Program for all overpayments, and I acknowledge that the Medicaid Audit System, which uses random sampling, is a reliable and acceptable method for determining such overpayments.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">14.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the privacy and confidentiality provisions of any applicable laws governing the use and disclosure of protected health information, including the privacy regulations adopted by the U.S. Department of Health and Human Services under the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and Public Acts 104-191 (45 CFR Parts 160 and 164, Subparts A and E). I also agree to comply with the HIPAA security regulations, as applicable, for electronic protected health information by the compliance date, which is currently April 21, 2005 (45 CFR Parts 160 and 164, Subparts A and C).</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">15.</td>
<td class="LabelValue" align="left" height="32">This Agreement shall be governed by the laws of the State of Michigan and applicable federal law including, but not limited to, the Health Insurance Portability and Accountability Act of 1996 (HIPAA).</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">16.</td>
<td class="LabelValue" align="left" height="32">The provisions of this Agreement are severable. If any provision is held or declared to be illegal, invalid or unenforceable, the remainder of the Agreement will continue in full force and effect as though the illegal, invalid or unenforceable provision had not been contained in this Agreement.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">17.</td>
<td class="LabelValue" align="left" height="32">Failure or delay on the part of either party to exercise any right, power, privilege, or remedy in this Agreement will not constitute a waiver. No provision of this Agreement may be waived by either party except in writing and signed by an authorized representative of the party requesting the waiver.</td>
</tr>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32"></td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">18.</td>
<td class="LabelValue" align="left" height="32">If the nursing facility named on the Medical Assistance Provider Enrollment & Trading Partner Agreement is sold, the seller will notify MDCH of the sale at least ninety (90) days prior to the expected sale date. Further, it is understood that the sale will not be recognized for reimbursement purposes under the Medical Assistance Program until ninety (90) days after such notification. Provisions of 42 CFR 413.135(f) will be retrospectively satisfied at that time. Any exception must be approved in writing by MDCH. The new owner/provider must receive Medicare certification for all Medicaid-only beds in the facility within one year from the date of purchase of an operating nursing facility or from the date of reopening a previously closed nursing facility.</td>
</tr>
<tr valign="center">
<td class="Label" align="middle" width="14%" colspan="2" height="32">Medical Assistance Provider - Employer/Employee Conditions</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">19.</td>
<td class="LabelValue" align="left" height="32">The applicant is employed by the business listed, now referred to as the "employer", to provide Medical Assistance Program services to eligible beneficiaries at the service address listed.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">20.</td>
<td class="LabelValue" valign="top" align="left" height="32">The employer and the applicant shall advise MDCH within thirty (30) days after any change(s) in the employment relationship.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">21.</td>
<td class="LabelValue" align="left" height="32">The employer and the applicant agree to be jointly and severally liable for any overpayments billed and paid under Act No. 280 of the Public Acts of 1939, as amended, for services provided by the applicant to eligible beneficiaries.</td>
</tr>
<tr valign="center">
<td class="Label" align="middle" width="14%" colspan="2" height="32">Trading Partner Provisions</td>
</tr>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32">The MDCH and its Trading Partner desire to facilitate the exchange of healthcare transactions ("Transactions") by electronically transmitting and receiving data in agreed formats in substitution for conventional paper-based documents.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">1.</td>
<td class="LabelValue" align="left" height="32">Companion Documents; Standards; Other Documentation. MDCH makes available certain inbound and outbound Electronic Data Interchange (EDI) transaction sets/formats and associated version. From time to time during the term of this Agreement, MDCH may modify supported transaction sets/formats. In submitting Transactions to MDCH, the Trading Partner agrees to conform to MDCH-issued provider publications and MDCH Companion Guides as amended from time to time. The MDCH Companion Guides, incorporated by reference herein, contain specific instructions for conducting each Transaction and as such supplement Implementation Guides issued under the Standards for Electronic Transactions mandated by the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as amended. The MDCH Companion Guides are not intended to be complete billing instructions and do not alter or replace applicable physician guides or other healthcare provider billing publications issued by MDCH or by other third party payers. The Trading Partner agrees to comply with the requirements set forth in the applicable MDCH Companion Guides. The Trading Partner, or its vendor, or other authorized technical representative responsible for EDI software will document Trading Partner Information, data formats and related versions, trading partner identifiers, and other information MDCH requires to receive and transmit specific Transactions supported by MDCH.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">2.</td>
<td class="LabelValue" align="left" height="32">Support. 
As to software, equipment, and services associated with each party's performance under this Agreement, the parties agree to provide support services sufficient for Transactions to be exchanged. Each party will assist the other in establishing and/or maintaining support procedures, and will complete appropriate problem determination procedures prior to contacting the other with a support related matter. The parties agree to use all commercially reasonable efforts to avoid and resolve performance and unavailability issues. Each party will perform remedial action, as requested by the other, to assist in problem resolution. Each party, at its own expense, shall provide and maintain the equipment, software, services, and testing necessary to effectively and reliably transmit and receive transactions.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">3.</td>
<td class="LabelValue" align="left" height="32">Data Retention. 
MDCH will log all Transactions for the purpose of problem investigation, resolution, and servicing. The Trading Partner is responsible for maintaining and retaining its own records of data submitted to MDCH. Trading Partners who are healthcare providers will ensure that electronic healthcare claims submitted to MDCH can be readily associated and identified with the correct patient medical and business office records, and that these records are maintained in a manner that permits review, and for the time period as may be required by MDCH or other third party payer responsible for claim payment.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">4.</td>
<td class="LabelValue" align="left" height="32">Proper Receipt and Verification for Transactions. 
Upon proper receipt of any ANSI ASC X12N Standard Transaction, the receiving party shall promptly and properly transmit a functional acknowledgement in return, unless otherwise specified. The functional and interchange acknowledgements must be accepted and reviewed, when applicable, to confirm the receipt of a Transaction. The ability to send or receive functional acknowledgements is applicable only to ANSI ASC X12N Standard Transactions. Additionally, MDCH originated outbound Transactions must be accepted and reviewed, when appropriate, to obtain MDCH's response to specific inbound Transactions. The acknowledging party does not attest to the accuracy of the data contained in the transmission; rather, it only confirms receipt of the transmission.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">5.</td>
<td class="LabelValue" align="left" height="32">Liability. 
MDCH shall not be responsible to the Trading Partner nor anyone else for any damages caused by loss, delay, rejection, or any misadventure affecting such electronic information. In addition, MDCH shall be excused from performing any EDI servi

You cannot use string literal of more than 4000 characters in an Oracle SQL statement. I'm not going to count that string you so rudely posted but I presume it is longer than that figure. You'll need to use a variable instead.
declare
 c clob := '<your vast XML doc here>';
begin
 update PRVDR_ENRLMNT_AGREEMENT B set b.terms= c
 where ....
{code}
Cheers, APC

String literal too long error while invoking a package with clob variable

I have a package.One of the input variables of the procedure in packae is clob.
I want to invoke this package with a huge clob as input.
when i invoke this package like that i am getting following error
PLS-00172 string literal too long
can't we pass clob(huge clob) as input .is there any solution for that ?
Thanks
Pramod Garre

842802 wrote:
If insert this data into a table , from sql prompt still i get the same error.Do you mean SQL*Plus? Then there is buffer limitation and it is better to split literal into, let say 1000 character chunks:
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Mar 29 16:17:26 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
from dual
ERROR at line 6:
ORA-01489: result of string concatenation is too long
SQL> select to_clob('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA') ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
TO_CLOB('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
SQL> SY.

Unterminated string literal error every time firefox opens a page.

Every time firefox opens a new page, the error pops up. It says Javascript error at the top of the error window - and the error is "unterminated string literal. It very annoying, some pages have multiple instances of the error window popping up on top of each other. I reloaded the program, no changes. I am ready to give up and go to Chrome (which does not have the error)

This issue can be caused by an extension that isn't working properly.
Start Firefox in [[Safe Mode|Safe Mode]] to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe Mode start window.
If it works in Safe Mode and in normal mode with all extensions (Firefox/Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.
Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: Firefox > Quit Firefox; Linux: Firefox/File > Quit)
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

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

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

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

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

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

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

ORA-01704: string literal too long (URGENT)

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

Check this cool-bi.com

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

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

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

Unterminated String Literal..?

I am receiving an error message "unterminated string literal" in my custom calculation script and not sure why or how to fix it.
There error seems to occur on one of the last two lines on the code below...my code is about 4 times this length, but I can only make it to this point when the error occurs...the problem is not with the particular code, because if I remove some code before it, it works fine....maybe it has to do with the legth of the code? Are there any limits or restrictions that may be affecting this?
if (this.getField("TICKET1").value =="-") {event.value = 0.00}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket)" && this.getField("TYPE1").value == "ADULT") {event.value = 814.00;}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket)" && this.getField("TYPE1").value == "STU/SEN") {event.value = 740.00;}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket)" && this.getField("TYPE1").value == "CHILD") {event.value = 555.00;}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket Early Bird)" && this.getField("TYPE1").value == "ADULT") {event.value = 580.00;}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket Early Bird)" && this.getField("TYPE1").value == "STU/SEN") {event.value = 515.00;}
if (this.getField("TICKET1").value =="GENERAL (2011-2012 Season TIcket Early Bird)" && this.getField("TYPE1").value == "CHILD") {event.value = 366.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - 16 game pack)" && this.getField("TYPE1").value == "ADULT") {event.value = 384.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - 16 game pack)" && this.getField("TYPE1").value == "STU/SEN") {event.value = 352.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - 16 game pack)" && this.getField("TYPE1").value == "CHILD") {event.value = 272.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 1)" && this.getField("TYPE1").value == "ADULT") {event.value = 88.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 1)" && this.getField("TYPE1").value == "STU/SEN") {event.value = 80.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 1)" && this.getField("TYPE1").value == "CHILD") {event.value = 60.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 2)" && this.getField("TYPE1").value == "ADULT") {event.value = 96.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 2)" && this.getField("TYPE1").value == "STU/SEN") {event.value = 88.00;}
if (this.getField("TICKET1").value =="GENERAL (2010-2011 Playoffs - Round 2)" && this.getField("TYPE1").value == "CHILD") {event.value = 68.00;}

Just to mention I'm having a similar problem in Acrobat X on Mac of mysterious errors which alternate seemingly randomly between "unterminated string literal", or "missing ) in parenthetical", or "missing } in compound statement", or "missing : after property id".There seems to be some kind of bug here, or at the very least, non-standard behaviour.
They always occur at the end of the code and seem unrelated to what the code actually says.
Here's one example, giving "unterminated string literal" on the this.extractPages... line:
if(isInt(pagesPerRecord)) {
 for( var i = 0; i < this.numPages; i+pagesPerRecord ) {
 var filename = csvData.getRowAndColumn(i, 'filename') + '.pdf';
 var end = i+pagesPerRecord-1;
 app.alert(filename);
 filename = filename ? filename : 'file-'+((i+pagesPerRecord)/pagesPerRecord)+'.pdf';
 this.extractPages({ nStart: i, nEnd: end, icPath: filename });
If I make a minor, cosmetic change so the code reads like this (not defining end as a variable), the error changes to "missing ) in parenthetical":
if(isInt(pagesPerRecord)) {
 for( var i = 0; i < this.numPages; i+pagesPerRecord ) {
 var filename = csvData.getRowAndColumn(i, 'filename') + '.pdf';
 app.alert(filename);
 filename = filename ? filename : 'file-'+((i+pagesPerRecord)/pagesPerRecord)+'.pdf';
 this.extractPages({ nStart: i, nEnd: i+pagesPerRecord-1, icPath: filename });
If I make a minor, cosmetic change so the code reads like this (using a different form of if logic on the check for a filename), the error changes to "missing } in compound statement":
if(isInt(pagesPerRecord)) {
 for( var i = 0; i < this.numPages; i+pagesPerRecord ) {
 var filename = csvData.getRowAndColumn(i, 'filename') + '.pdf';
 app.alert(filename);
 filename = filename || 'file-'+((i+pagesPerRecord)/pagesPerRecord)+'.pdf';
 this.extractPages({ nStart: i, nEnd: i+pagesPerRecord-1, icPath: filename });
There have been times where I've had errors like this for valid code, and I've deleted and re-typed all the + signs, and it's worked again. Really don't understand this, as the error messages seem unrelated to the code. The rest of the code that ends with this hasn't changed since an earlier version that worked.
There are definitely definitely no unclosed brackets, parenthesies or quotes. I've checked manually and with text editor tools (and by copying and pasting directly from an earlier version that worked).
I'm sure there's a bug in error reporting or syntax checking that explains the original problem and mine.
Edit: Weirder and weirder, I changed an unrelated line earlier in the code, in the section that is unchanged from an earlier version that worked fine, from:
app.alert("5 - "+pagesPerRecord+" pages per record (isInt=="+isInt(pagesPerRecord)+")");
...to...
app.alert("5 - "+pagesPerRecord+" pages per record");
...on the basis that another time I had this problem, just deleting lines that involved string concaternation seemed to fix it, and the error message changed yet again to "missing : after property id", while still pointing at the same line (the penultimate } ). Odd, very odd.

String literal not termintate, line1

Hi All,
We added a new parameter in the BAPI's output table. After that we redefined the model in VC and then tested it, it was working fine. All of a sudden after few hours when we tried to test that model from VC we got an error saying that "String literal not terminated, line 1". We tried restarting the server, clearing the server cache and drag and drop new model after the structure change ( also the compiler option for data service retrieval is set to get latest). What could be the reason for this?
Expecting quick help from sdn.
Regards,
Murtuza

You may need to escape the default slash "\\".
I'd suggest importing the xsd into the jcaps xml schema editor and verifying that way and then creating the otd by node export.
Regards,
Rupert

Access Migration Error Creating Migration Project - string literal too long

I get this error when attempting to create an MS Access Migration Project:
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 8, column 8: PLS-00172: string literal too long &lt;pre&gt;begin &amp;lt;br&amp;gt;declare &amp;lt;br&amp;gt; p varchar(32767) := null; &amp;lt;br&amp;gt; l_clob clob; &amp;lt;br&amp;gt;begin &amp;lt;br&amp;gt; dbms_lob.createtemporary(l_clob,FALSE, dbms_lob.session); &amp;lt;br&amp;gt; dbms_lob.open(l_clob,dbms_lob.lob_
I suspected the 'string literal too long' was due to a very long code section in the Exporter .sql file -
So I edited out that code except - essentially by cutting the macro code within the quotes, cutting down that code module.
Same error.
Any suggestions on what else may be causing this?
Thanks - Karen

I found it - two other big long ugly macros that I had to cut out as well. Then the migration project created just fine. Thanks for the moral support :)

How to Update a clob column..it gives error string literal too long

I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too long

Peeyush wrote:
I am trying to update a clob column of a table but it gives error string literal too long plz tell me what's the issue
ORA-01704: string literal too longThere's a problem with my car. It won't start. Why won't it start? Please tell me!
Oh wait, you can't, because I haven't given you nearly enough information...
In other words, if you would like help in trying to work out where you've gone wrong, you should provide a small enough example of your code that demonstrates the error. We might then actually stand a chance of being able to help you!

String Literal Too Long - error?

I'm using a CLOB datatype but via an ODBC connection I'm given an error when I insert a value larger than 4000 chars:
ODBC Error Code = S1000 (General error)
[Oracle][ODBC][Ora]ORA-01704: string literal too long.
SQL:
insert into TEST2
(ARTICLE,UUID)
values ('Very long string I wont repeat here!','1234')
DESCRIBE confirms that the datatype is CLOB and not VARCHAR2. Am I doing something wrong or is it a restriction in the ODBC driver? The version installed is 8.1.5.6. I can't install the very latest version because it comaplains that it needs a newer version of the Oracle Installer. Thanks.

Hi Justin,
Thanks for pointing me back to the other topic where I asked the question. I lost it under all of the new topics that had been posted! Andrew's reply is very helpful but assumes I have the data stored in a file, which I don't. I've replied hoping Andrew still has the patience to help! :-)

Target="_blank Error unterminated string literal

Hello,
I have used a example from Patrick Wolf and it won't work.
http://www.inside-oracle-apex.com/opening-url-in-new-window/
I need a pop_up window after pushing the button:
Target is a: URL
1- URL Target: http://www.google.nl/" target="_blank -- Don't work (Error unterminated string literal)
2- URL Target: http://www.google.nl/ -- Works
What is wrong(see number 1)?
Thanks at advance.
Walter

Jari,
It didn't work.
On the rightside from my button I have now the next text : Google')">
With Error- pointer on ' before <a:
Fout: unterminated string literal
Bronbestand: http://apex-o/pls/apex/f?p=160:190:8048856061349970::::FSESSION,FORMID:10752014578,
Regel: 1, Kolom: 20
Broncode:
javascript:redirect('<a href=
when I change 'Optional URL Redirect' field 'URL Target' to
<a href=http://www.google.nl/ target=_blank'></a>
I have the next Error:
Fout: syntax error
Bronbestand: http://apex-o/pls/apex/f?p=160:190:8048856061349970::::FSESSION,FORMID:10752014578,
Regel: 1, Kolom: 66
Broncode:
javascript:redirect('<a href=http://www.google.nl/ target=_blank'></a>')
It still not work. Do you have a solution.
Walter

Error in assigning string literal.......

Similar Messages

Maybe you are looking for