Ora 22992 -------- CLOB issue

Hi ,
I have a database in
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
I have table tableAAA in database1,which has a clob column.
I want to select the CLOB column to Another database (database2)
So I create a view
(create or replace view my_view_tableAAA as select * from tableAAA)
view created
select * from schema.my_view_tableAAA@mydblink
(ORA-22992: cannot use LOB locators selected from remote tables)
What mistake am i doing ?
Rgds
S

DBLink problem ORA-22992
Try the above, Google is really useful sometimes.

Similar Messages

Materialized view fast refresh ...getting ORA-22992: error

Hi All,
Oracle version 11.1.0.7
While creating a materialized view(Fast refresh) on remote tables ... i am getting the ORA-22992: cannot use LOB locators selected from remote tables ... error.
but the actual scenario is... i am not selecting any of the BLOB/LOB columns from the remote tables. I did n't include them in my materialized query.
I am able to refresh it complete but couldn't refresh it fast. Here i want to mention other thing... when ever i have records in Mat view log(Base table has a blob cloumns in it)
i am getting the above error. when no record in the Mat view log(i.e on BLOB base table) .. i can able to refresh it as FAST.
MV_CAPABILITIES table tells that ...My Mat view is able to refresh it FAST.I don't know howw to approach to solve this issue.could some one tell me the approach..to solve it?
Here is the sample code ....this is what i have done so fat
session 1 (REMOTE_ONE)
I have created synonyms for the remote tables on current schema. That's why i didn't include @DBLINK.
create table RT_A ( col1_A varchar2(20), col2_A BLOB,COL3_A NUMBER);
create a table RT_B (COl1_B varchar2(20), col2_B BLOB, COL3_B NUMBER);
create a table RT_C (COL1_C varchar2(20), col2_C VARCHAR2,COL3_C NUMBER);
create MATERIALIZED VIEW LOG ON RT_A
WITH ROWID EXCLUDING NEW VALUES;
create MATERIALIZED VIEW LOG ON RT_B
WITH ROWID EXCLUDING NEW VALUES;
create MATERIALIZED VIEW LOG ON RT_C
WITH ROWID EXCLUDING NEW VALUES;
grant select on RT_A to CUURRENT_ONE with grant option;
grant select on RT_B to CUURRENT_ONE with grant option;
grant select on RT_C to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_A to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_B to CUURRENT_ONE with grant option;
grant select on MLOG$_RT_C to CUURRENT_ONE with grant option;Session 2 (CUURRENT_ONE)
create materialized view ABC_MV
BUILD IMMEDIATE REFRESH FORCE ON DEMAND START WITH SYSDATE NEXT SYSDATE+1
AS
select A.ROWID AS A_ROWID,
B.ROWID as B_ROWID,
C.ROWID AS C_ROWID,
A.COL1_A,
B.col1_B,
c.col1_c
from RT_A, RT_B,RT_C
where COL3_A = COL3_B(+)
and COL3_B = COL3_C(+)Appreciate your help.
Thanks,
Mike

Thanks for the reply
In that he/she is selecting the LOB column from the remote database(master site).
I am just referencing the table which has BLOB column in it.I am not referencing any LOB column in my select(Mat view) query...
is there anything i need to check..?
Regards,
Mike

PL/SQL: ORA-22992: cannot use LOB locators selected from remote tables

Dear ALL,
My O/S is Redhatlinux 5.2 and i had Migrated my Oracle databse to 11g2. But after that while i am retrieving records through dblinks from one of my other Oracle 9.2.0.8 databse it's throwing the error : PL/SQL: ORA-22992: cannot use LOB locators selected from remote tables.* This error i am getting in TOAD as well as SQL Developer.
Can anybody tell me how to fix this error ? Because am not able to get the records.
Also am getting another error during retrieving data from some of my tables after migrating i.e the table which having CLOB data type while am accessing to retrieve the records using select query it's throwing the error :
+(The following error has occurred:+
A query with LOB's requires OCI8 mode, but OCI7 mode is used.)
If anyone having any idea kindly share.
Thanks and Regards
Biswa

Hi,
Ya what u sent that is fine. But already am using one procudure which is accessing LOB data from another databse through DBlink and working fine. But there Both the databse are 9.2.0.8.
But while am executing the same procedure in oracle 11g where the Dblink accessing the data from Oracle 9i , there am getting this error.
Kindly tell if u know any resolution.
Thanks

Creating view containing case statements received error ORA-22992

We have a create view referencing table through dblink. The select statement in the create view has case statements, when running the Select statement alone, results are return. However, when executing the create view, it returns:
SQL Error: ORA-22992: cannot use LOB locators selected from remote tables
22992. 00000 - "cannot use LOB locators selected from remote tables"
*Cause: A remote LOB column cannot be referenced.
*Action: Remove references to LOBs in remote tables.
One of the source table has LOB column but not in the select statement. The strange thing is when removing the case statement from the select, create view works fine. Can anybody tell me what caused the error and how to fix it?
Create View Snippet:
CREATE OR REPLACE VIEW "ABC"."XYZ" (....
AS SELECT
CASE
WHEN A.OUTAGE =1
THEN 'Y'
ELSE 'N'
END AS OUTAGE,
FROM
TABLEA@XXXX A
LEFT JOIN TABLEB@XXXX B
ON
A.LOC =B.LO
AND A.SITE =B.SITE
WHERE
A.CLASS ='CUSTOMER'
AND A.PLUSSISGIS =1;

What is your 4 digit Oracle version?
Try rewriting the query to not use ANSI SQL92 joins. I found a link where this solved a problem similar to yours.
DBLink problem ORA-22992
>
But, look at this curious thing: I re-write the query as follows:
SELECT A.ID, A.ID_REF, A.EVENDATE, B.DESCRIPTION
FROM A@ORCL A, B@ORCL B
WHERE A.ID_REF = B.ID_REF;
and it works fine... It seems like Oracle don't like the ANSI SQL92...
>
Several similar links by googling: 'SQL Error: ORA-22992'
http://www.dbuggr.com/smallwei/solution-error-ora-22992-lob-locators-selected-remote-tabl/
>
Fixing ORA-22992 “cannot use LOB locators selected from remote tables” error
You have migrated your Oracle 9i database to 10g and a distributed statement which worked fine in 9i now is getting error ORA-22992 “cannot use LOB locators selected from remote tables”. Even though the related remote table(s) does not contain any LOB column datatype.
FIX:
There is a bug on 9i,10g, and 11g that is related to this error. It is being fixed in 11.2. It can also be backported for previous 9i, 10g and 11g releases under the latest patchsets.
You may also do a workaround as follow:
Modify the affected SQL by adding the TO_CHAR function. For example:
-- Original SQL:
SELECT NVL2('a', 'b','c' ) FROM dual@remote_db;
-- Modified SQL:
SELECT TO_CHAR(NVL2('a','b','c')) FROM dual@remote_db;
>
See if that helps.

Error ORA-22992, what to do?

I created database link to another oracle db (same version: 9.2). Now I want to create view for a table with BLOB.
"create or replace view persons as select * from persons@serv2"
What can I do?

http://asktom.oracle.com/pls/ask/f?p=4950:8:9407757796067305436::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:5322964030684
ORA-22992 cannot use LOB locators selected from remote tables
Cause: A remote LOB column cannot be referenced.
Action: Remove references to LOBs in remote tables.

String Literal too long / CLOB Issue

I have a table with a "Clob" column called Message. This is where I store the message of an email. We have an internal email app. What is happening is I can't insert anything bigger then around 3990 or something around there. In my procedure I have the parameter coming in as clob and I use a TO_CHAR() around the table column and my parameter or my procedure gives me this error
PL/SQL: ORA-00932: inconsistent datatypes: expected - got CLOB
But when it runs and I put in a 9000 character message it says
Oracle.DataAccess.Client.OracleException was unhandled by user code
Message="ORA-01704: string literal too long
I'm using C# with
Oracle.DataAccess.Client.OracleConnection to create my oracle connection and Oracle 10g.
I'm calling this procedure from my app. By doing this am I causing it to only hold 4000 characters?
Here is a scaled down version of my code on just that column
CREATE OR REPLACE PROCEDURE EMAILINS (
P_MSG IN CLOB
AS
varT VARCHAR2(10000);
varSQL VARCHAR2(20000);
varTemp NUMBER;
BEGIN
-- SEE IF STRING EXISTS
SELECT 1 INTO varTemp
FROM tblEmail
WHERE TO_CHAR(MESSAGE) = P_MSG
EXCEPTION
WHEN TOO_MANY_ROWS THEN
varSQL := varT||CHR(10)||'***Multiple Rows Exist in Table tblEmail***';
DBMS_OUTPUT.PUT_LINE(varSQL);
WHEN NO_DATA_FOUND THEN
varT := P_MSG;
varSQL := 'INSERT INTO TBL_EMAIL( MESSAGE)'||CHR(10);
varSQL := varSQL || 'VALUES (tblEmail_SEQ.NEXTVAL,'||varT||')';
EXECUTE IMMEDIATE varSQL;
END EMAILINS;

In the first place, you don't need (and surely don't want) dynamic SQL to do the insert. Replace
varT := P_MSG;
varSQL := 'INSERT INTO TBL_EMAIL( MESSAGE)'||CHR(10);
varSQL := varSQL || 'VALUES (tblEmail_SEQ.NEXTVAL,'||varT||')';
EXECUTE IMMEDIATE varSQL;with the simpler
INSERT INTO tbl_email( <<primary key column>>, message )
VALUES( tblEmail_Seq.nextval, p_msg );Secondly, you want to use the DBMS_LOB.COMPARE function to determine whether the contents of the LOBs match. So replace
SELECT 1
INTO varTemp
FROM tblEmail
WHERE TO_CHAR(MESSAGE) = P_MSG with
SELECT 1
INTO varTemp
FROM tblEmail
WHERE dbms_lob.compare( message, p_msg ) = 0Of course, it is going to be relatively expensive to run this query every time you insert a new message unless the table is always going to be very small, which seems unlikely. It also doesn't prevent duplicate entries if there are multiple threads executing at the same time.
Justin

DBMS_LOB Package for CLOB Issues

I was wondering if any of you have worked with DBMS_LOB
packages. I wrote a procedure that will be invoked from a 'C'
program. I was first compiling the procedure as follows:
procedure <procedurename> (c_text out char, length in number)
declare c_lob CLOB;
begin
SELECT lob_locator_column into c_lob from <table>
WHERE
<table>.id = '1';
dbms_lob.read(c_lob,length,1,c_text)
end;
When I compile this program I am getting an error "length cannot
be used as a target". Have any of you seen this problem?
Right now I am getting around by declaring another variable and
assigning the input length to the variable and passing it into
DBMS_LOB.
Another issue I have is that the DBMS package is returning the
length of the clob to be an "INTEGER". What happens if the clob
length is greater than 32767?
null

I guess you are using a reserved word..
Bala Vanukuru (guest) wrote:
: I was wondering if any of you have worked with DBMS_LOB
: packages. I wrote a procedure that will be invoked from a 'C'
: program. I was first compiling the procedure as follows:
: procedure <procedurename> (c_text out char, length in number)
: declare c_lob CLOB;
: begin
: SELECT lob_locator_column into c_lob from <table>
: WHERE
: <table>.id = '1';
: dbms_lob.read(c_lob,length,1,c_text)
: end;
: When I compile this program I am getting an error "length
cannot
: be used as a target". Have any of you seen this problem?
: Right now I am getting around by declaring another variable
and
: assigning the input length to the variable and passing it into
: DBMS_LOB.
: Another issue I have is that the DBMS package is returning the
: length of the clob to be an "INTEGER". What happens if the
clob
: length is greater than 32767?
null

Receiving ORA-12537 TNS issue....what else can I do?

HPUX
10.2.0.3
I've started getting these errors on my database. However, nothing was being reported in my alert log. I did the research and found a bug that could cause this, with a patch. Also found that the same patch was in the 10.2.0.3 patch set.
So I updated to that patch last night. STILL getting the same errors...but now I'm getting new errors...
Wed Apr 1 09:00:14 2009
Process m000 died, see its trace file
Wed Apr 1 09:00:14 2009
ksvcreate: Process(m000) creation failed
Wed Apr 1 09:00:33 2009
Process J000 died, see its trace file
Wed Apr 1 09:00:33 2009
kkjcre1p: unable to spawn jobq slave process
Wed Apr 1 09:00:33 2009
Errors in file /opt/oracle/admin/peregrine/bdump/peregrine_cjq0_11720.trc:
So I open up the trace file...
only contents...
/opt/oracle/admin/peregrine/bdump/peregrine_cjq0_11720.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/oracle/product/10.2.0/db_1
System name: HP-UX
Node name: vscdsh01
Release: B.11.23
Version: U
Machine: ia64
Instance name: peregrine
Redo thread mounted by this instance: 1
Oracle process number: 10
Unix process pid: 11720, image: oracle@vscdsh01 (CJQ0)
*** SERVICE NAME:(SYS$BACKGROUND) 2009-04-01 09:00:01.694
*** SESSION ID:(382.1) 2009-04-01 09:00:01.694
*** 2009-04-01 09:00:01.694
Process J000 is dead (pid=1288, state=3):
*** 2009-04-01 09:00:07.844
Process J000 is dead (pid=1673, state=3):
*** 2009-04-01 09:00:33.940
Process J000 is dead (pid=2201, state=3):
I looked up that string of text...googled it...came back with nothing.
How else can I investigate this ORA-12537 error? This is my production db, and it's down.
I checked the memory that one article indicated could be of issue...memory is fine.
It also mentioned versions of listener, I'm looking into that right now on how to see what version and how to update it. I'm also going to open a SR with Oracle.
Thanks.

Ok...tried to log back in (no other actions taken) and it was a normal log in...that's really weird.
The db was never down...it's functional. Just some folks can't get to it. (not the same people all the time..)
show sga:
SQL> show sga
Total System Global Area 5083496448 bytes
Fixed Size 2052400 bytes
Variable Size 436211408 bytes
Database Buffers 4630511616 bytes
Redo Buffers 14721024 bytes
SQL> show parameter proces
NAME TYPE VALUE
aq_tm_processes integer 0
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 10
log_archive_max_processes integer 30
processes integer 350
SQL> show parameter transaction
NAME TYPE VALUE
transactions integer 429
transactions_per_rollback_segment integer 5
excerpt from print_manifest
Kernel Configuration
The following drivers or parameters are configured into your system's
kernel. After installing HP-UX, use the sam(1m) command to configure
the following items into the kernel:
dbc_max_pct 10
vps_ceiling 64
shmmni 512
semmnu 4096
semmns 8192
semmni 4096
ninode 34816
ncsize 34816
msgseg 32767
msgmni 4096
msgtql 5000
cmc_plat_poll 15
nstrpty 60
max_thread_proc 1200
maxssiz 134217728
maxssiz_64bit 1073741824
maxuprc 3687
msgmap 4098

Ora:countNodes coding issue

I try to get the node count by the ora:countNodes api, but it's just return 0. The following lines list the detail.
Namespace: xmlns:coaebmebo="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1"
Variable: curCOA
Type: coaebmebo:GLAccountValidation (the element name in the xsd file is GLAccountValidation)
Target Node: coaebmebo:GLElementValue (the element name in the xsd file is GLElementValue)
Code (both return 0) : ora:countNodes('curC0A','GLAccountValidation', '/coaebmebo:GLElementValue')
ora:countNodes('curC0A','GLAccountValidation', '/coaebmebo:GLAccountValidation/coaebmebo:GLElementValue')
SourceXML:
<curC0A>
<GLAccountValidation xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<corecom:GLAccountIdentification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
<corecom:BusinessComponentID schemeID="" schemeAgencyID="" schemeVersionID=""/>
<corecom:ID schemeID="" schemeAgencyID="" schemeVersionID="">631353532353231</corecom:ID>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="" schemeAgencyID="" schemeVersionID=""/>
</corecom:ApplicationObjectKey>
<corecom:Revision>
<corecom:Number schemeID="" schemeAgencyID="" schemeVersionID=""/>
<corecom:Code listID="" listAgencyID="" listVersionID=""/>
</corecom:Revision>
</corecom:GLAccountIdentification>
<coa:ValidityDate xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">2009-06-05T09:35:13-07:00</coa:ValidityDate>
<coa:GLElementValue xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<coa:SequenceNumber>1</coa:SequenceNumber>
<coa:GLElementCode listID="" listAgencyID="" listVersionID="">1101</coa:GLElementCode>
<coa:Value>01</coa:Value>
</coa:GLElementValue>
<coa:GLElementValue xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<coa:SequenceNumber>2</coa:SequenceNumber>
<coa:GLElementCode listID="" listAgencyID="" listVersionID="">1102</coa:GLElementCode>
<coa:Value>000</coa:Value>
</coa:GLElementValue>
<coa:GLElementValue xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<coa:SequenceNumber>3</coa:SequenceNumber>
<coa:GLElementCode listID="" listAgencyID="" listVersionID="">1103</coa:GLElementCode>
<coa:Value>1110</coa:Value>
</coa:GLElementValue>
<coa:GLElementValue xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<coa:SequenceNumber>4</coa:SequenceNumber>
<coa:GLElementCode listID="" listAgencyID="" listVersionID="">1104</coa:GLElementCode>
<coa:Value>1728</coa:Value>
</coa:GLElementValue>
<coa:GLElementValue xmlns:coa="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/ChartOfAccounts/V1">
<coa:SequenceNumber>5</coa:SequenceNumber>
<coa:GLElementCode listID="" listAgencyID="" listVersionID="">1105</coa:GLElementCode>
<coa:Value>000</coa:Value>
</coa:GLElementValue>
</GLAccountValidation>
</curC0A>
And another issue is, do you know that it's a convenient way to validate the code? It's really time costly by deploying the process.
Thanks in Advance
Edited by: TsinHua on Jun 7, 2009 12:03 AM

Hi James,
The following codes are the part of the xsd that related with the issue.
     <xsd:element name="ProcessGLAccountValidation" type="ProcessGLAccountValidationType"/>
     <xsd:complexType name="ProcessGLAccountValidationType">
          <xsd:sequence>
               <xsd:element ref="corecom:ChartOfAccountsIdentification" minOccurs="0"/>
               <xsd:element name="ValidityDate" type="corecom:DateType" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>Indicate the default date on which you want to check if GL Account is valid or not. This could be the date in the past, current or future.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element ref="GLAccountValidation" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
          <xsd:attribute name="actionCode" type="corecom:ActionCodeType"/>
     </xsd:complexType>
     <xsd:element name="GLAccountValidation" type="GLAccountValidationType"/>
     <xsd:complexType name="GLAccountValidationType">
          <xsd:sequence>
               <xsd:element ref="corecom:GLAccountIdentification" minOccurs="0"/>
               <xsd:element name="ValidityDate" type="corecom:DateType" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>Indicate the date on which you want to check if this GL Account is valid or not. This could be the date in the past, current or future.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element ref="GLElementValue" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="GLElementValue" type="GLElementValueType">
          <xsd:annotation>
               <xsd:documentation>
A sequenced set of account codes that form a GL Account which is used to record transaction.
</xsd:documentation>
          </xsd:annotation>
     </xsd:element>
     <xsd:complexType name="GLElementValueType">
          <xsd:sequence>
               <xsd:element name="SequenceNumber" type="corecom:PositiveIntegerType" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>
Sequence in which the GL Element appears in the Account Code Combination
</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="GLElementCode" type="corecom:CodeType" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>
Indicate the unique code for this GLElement. E.g. Department, Company, Cost Center.
</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Value" type="corecom:StringType" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>
The GL Element value - e.g. Account Number
</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Custom" type="corechartofaccountscust:CustomGLElementValueType" minOccurs="0"/>
          </xsd:sequence>
          <xsd:attribute name="actionCode" type="corecom:ActionCodeType" use="optional"/>
     </xsd:complexType>

Clob issue

Hi, I'm on the latest version of Apex on Oracle 11gr2
I have a function which returns a clob. Basically just a string which dynamically builds a load of html , divs etc in it.
In my page I call the function using ajax callback.
Depending upon the size of the clob returned by the function I get the following error message sqlerrm:ORA-06502: PL/SQL: numeric or value error
So a size based on length(clob) of 2861 works but one of 141486 gives the error. I appreciate there is a considerable difference in the 2 values but neither are anywhere near 4G for a clob.
I hav'nt a clue how to resolve this
Ed.

Hi, I'm on the latest version of Apex on Oracle 11gr2I have a function which returns a clob. Basically just a string which dynamically builds a load of html , divs etc in it.
In my page I call the function using ajax callback.
Depending upon the size of the clob returned by the function I get the following error message sqlerrm:ORA-06502: PL/SQL: numeric or value error
So a size based on length(clob) of 2861 works but one of 141486 gives the error. I appreciate there is a considerable difference in the 2 values but neither are anywhere near 4G for a clob.
I hav'nt a clue how to resolve this
>
If you are returning HTML fragment then you need to have a CRLF at least every 4000 character. That is the HTML Spec.
If you are trying to store the returned CLOB in a Page or Application Item then you are hitting the 32K limit. If that is the case then try return the CLOB (rather array of VARCHAR2) from an On Demand Process with HTP.P
Cheers,

AQ/MGW clob issue - strange message

Oracle version 9.2.0.4
Solaris 8
I am using AQ with the Message Gateway to write to MQ , I am getting the following error/warning (?) in the mgw.log file
2004-09-06 04:07:15 MGW AQD:MsgConsumer 3 TRACE worker0 non-temporary CLOB: size=1420 for class:
oracle.mgw.drivers.aq.AQMsgConsumer$MgwBasicMsg_Dequeuer@26f75b
The message writes to MQ, and I can receive confirmations back into AQ. However
nothing is removed from AQ when dequeued ... this is machine specific as it runs
just fine on a different machine. Does anybody have any idea what this message means ?
I have looked high and low but cannot find an explanation/documentation

The way I have this transformation setup, I'm assuming it's
being run during the dequeue. Would this cause the message to be moved
to the AQ exception queue on the 9i instance? Am I creating the
transformation as the correct user (the one adding the subscription and scheduling the propagation th MQ)?
Dennis..............

ORA-22992: cannot use LOB locators selected from remote tables

Has anyone had this error msg before?
Thx .

If you want, you could facilitate your process with a global temporary table as follows:
SQL> create global temporary table clob_temp (
2 id         number,
3 test_clob clob)
4 on commit delete rows;
Table created.
SQL> Create or Replace procedure run_clob (p_id in number, p_file_name in varchar2)
2    AS
3       l_clob          clob;
4       l_bfile         bfile := BFILENAME ('TEMP_DIR', p_file_name);
5 begin
6      insert into clob_temp values (p_id, empty_clob() )
7               returning test_clob into l_clob;
8      DBMS_LOB.OPEN(l_bfile, DBMS_LOB.LOB_READONLY);
9      DBMS_LOB.LOADFROMFILE(l_clob, l_bfile, DBMS_LOB.getlength(l_bfile));
10      DBMS_LOB.CLOSE(l_bfile);
11      insert into clob_table@dlog_link (id, test_clob)
12               select * from clob_temp;
13      commit;
14 end;
15 /
Procedure created.
SQL> select count(*) from clob_table@dlog_link;
COUNT(*)
         0
SQL> exec run_clob (1, 'clobtest.txt')
PL/SQL procedure successfully completed.
SQL> select count(*) from clob_table@dlog_link;
COUNT(*)
         1

ORA Error - 20010 Issue

Hi All,
I have a stored procedure to load data into a table from another table. When I execute it using the EXEC command, I am getting the expected result.
But when I try to invoke the same using a Unix shellscript by connecting to the DB thru the script, I am getting the exception:
ORA - 20010.
I have checked the shell script for any errors, and its fine. The same script is being to invoke other stored procs and they are working properly .
Please suggest a solution.
Thanks.

hi there
its nothing with the script the problem is in procedure
it is raising some user defined exception
ORA - 20010. is a user defined exception.its range starts from -20000 to -20999.
Regards
Hitesh

ORA 22992 -- silly

I realize that you cannot access LOB locators from remote DBs, so don't think I am reporting this as a bug.
But, your developer explanations to customers are very poor (just cut/paste from documentation and/or error desc). We (most developers/customers) have looked at the forums, the documentation, and we need a work-around.
It is ridiculous to think that Oracle has used (C)LOBs to replace LONG datatypes, but you can't access these fields through a remote DB link.
To say this is a limitation is a major understatement... perhaps an unforseen design flaw with the LOB datatypes?
How are shops supposed to scale to multiple locations (servers) if Oracle won't allow certain fields to be accessed remotely.
Any response would be appreciated...
Thanks,
Adam

Click on the link below for a couple of workarounds by Tom Kyte:
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:950029833940

Help in ORA-22992 erroe

hi .
i have two schama d1 and d2 i create database link between them to create some tables that contain some information about the data in the d1 tables sum,count .....
in d1 there is table that contain blob column i know that this column of blob type couse the error but i do not select it in the query :
select count(recm.RECOMMENDATIONID) count, sum(rp.COST) cost ,dg.DIA DIA ,
to_char(de.F_DATE,'mm-yyyy') F_Date
from decc@EMOH40LNK de inner join requests@EMOH40LNK rq on(rq.REQUESTID = de.REQUESTID)
inner join recomm@EMOH40LNK recm on(recm.RECOMMENDATIONID = de.RECOMMENDATIONID)
inner join RECOMMPro@EMOH40LNK rp on(recm.RECOMMENDATIONID = rp.RECOMMENDATIONID)
inner join DIA@EMOH40LNK dg on(dg.CODE = rq.REQUESTCODE)
where
de.F_DATE>=to_date('','');
so how can do it ........
thak you all.....

Implement the query as a view in database EMOH40LNK, like this:
CREATE OR REPLACE VIEW REMOTE_VIEW AS
select count(recm.RECOMMENDATIONID) count, sum(rp.COST) cost ,dg.DIA DIA ,
to_char(de.F_DATE,'mm-yyyy') F_Date
from decc de inner join requests rq on(rq.REQUESTID = de.REQUESTID)
inner join recomm recm on(recm.RECOMMENDATIONID = de.RECOMMENDATIONID)
inner join RECOMMPro rp on(recm.RECOMMENDATIONID = rp.RECOMMENDATIONID)
inner join DIA dg on(dg.CODE = rq.REQUESTCODE)
where
de.F_DATE>=to_date('','');(sorry, I was sloppy in my original - removed @EMOH40LNK references from query)
Then, in your local database,
SELECT * FROM REMOTE_VIEW@EMOH40LNK ;This should force the query to be resolved in the remote database, so that the LOBs will not be involved in the query over the link.
Edited by: mtefft on Jul 6, 2010 4:47 AM

Ora 22992 -------- CLOB issue

Similar Messages

Maybe you are looking for