Ora-1445 rowid on subselect statement

Does anybody know what oracle component is missing if I get this error?
Here is the statement that's giving an error:
update GTT_CHART_TNX gtt
set (gtt.meter_name, gtt.entry_sequence_number) =
(SELECT new_name,entry_sequence_number
FROM (SELECT (w.field_location || '/' || gtt2.meter_name) new_name,
w.entry_sequence_number entry_sequence_number,
gtt2.rowid
FROM TWELL w,GTT_CHART_TNX gtt2
WHERE w.company_id = gtt2.company_id
AND w.battery_id = gtt2.battery_id
AND w.well_id = gtt2.well_id
AND gtt2.well_id IS NOT NULL
AND gtt2.meter_type IN ('GI')) b
WHERE b.rowid = gtt.rowid)
where gtt.meter_type in ('GI')
and gtt.well_id IS NOT NULL
and gtt.updt_mode IS NULL;

Just letting you know that this is now resolved. Primary key on one of the tables was missing.
Thought I'd post this, just canse other people are having the same problem.
thanks.
Mary Ann

Similar Messages

ORA-1445 and maximum width for field selection.

Hello,
We had the ORA-01445 error in the database recently.
A friend of mine directed me to the following address:
http://www.errorhelp.com/search/details/65019/ora-01445
And explained me that Oracle takes every field of every table in the inner and outer joins to build a HUGE table before selecting what fields are really required for the query.
I can't believe that Oracle makes such stupid thing so I ran here to ask the experts.
An example:
Two tables:
TABLE1
Field1
Field2
Field100
TABLE2
Field1
Field2
Field500
Select table1.field1, table2.field1
FROM table1
INNER JOIN table2 on table1.Field2 = table2.Field2
WHERE table1.field3 = '1'
->
Question is:
How the join is built on detail?
Does it build an intermediate table with 100+500 = 600 fields to get only the 5 that are used in the query (table1.field1, table2.field1, table1.Field2, table2.Field2,table1.field3)?
Thank you.
Kindest regards,

864737 wrote:
Hi John,
Maybe it's a complete nonsense but even if has no sense proceeding that way solved the issue here.
I have a query that suddenly failed to execute with the error described, version 10.2.0.3 but it does not happens in 10.2.0.4. As a workaround we did it using subselects and joining as described in the post and the query worked again.
So ORA-01445 is triggered even if it's not the cause of the error. You have there a circumstance where it fits...
So, it is clearly a bug introduced (possibly in 10.2.0.3), and fixed in 10.2.0.4.
I cannot post the query because license restrictions but believe it or not this happens with Oracle. It's great to know that the number fields of the tables does not matter. I was suprised to hear it. But your clarification was good. :D Tnx.
It seems that our DBA found that this behaviour can be corrected with an official patch.
Which clearly indicates a bug, just be sure that the patch is truly the right one.
Thank you again for your response.There are a number of bugs in MOS around ansi joins getting this error, bug
4369235.8 ORA-1445 can occur for ANSI join queries with large views/subqueries
seems possiblefor your case. However the workaround for that was to not use ansi style joins, so again, the number of columns is not directly the cause of the error.
John

ORA-04044 Error in SQL statement

Hi All,
I faced ORA-04044 in a SQL statement being written inside a shell script. I really don't know what is wrong with the script. Without shell variables is working ...
Here is the excerpt:
line=`sar -u 2 5 |tail -1`
var_io=`echo "$line" | awk '{print $6}'`
var_sys=`echo "$line" | awk '{print $5}'`
var_user=`echo "$line" | awk '{print $3}'`
var_idle=`echo "$line" | awk '{print $7}'`
sqlplus $ora_access <<EOF
select sysdate, a.hostid, a.inst_num, b.count1, c.count2, $var_user,$var_sys,$var_idle,$var_io
from dual ,
(select HOST_NAME hostid, INSTANCE_NUMBER inst_num from v$instance ) a,
(select count(sid) count1 from v$session where username is not null) b,
(select count(*) count2 from apps.fnd_concurrent_requests where phase_code ='R') c;
EOF
[b]Error Message:
SQL*Plus: Release 10.2.0.2.0 - Production on Thu Apr 10 02:20:53 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> 2 3 4 5 (select count(sid) count1 from v where username is not null) b,
ERROR at line 4:
ORA-04044: procedure, function, package, or type is not allowed here

Thanks a lot for instant reply. It worked!!
I forgot to use the escape character, but the error
message was not revealing anything :-(If you look carefully you could have spotted it:
SQL> 2 3 4 5 (select count(sid) count1 from[b] v where username is not null) b,

ORA-01555 caused by SQL statement below on production

Hi
i got ORA-01555 caused by SQL statement below on my prodution adn database undo_retention = 18000 what can i do my database performance is going down pls tail me what i do .
Regards
Digvijay

1) I don't see a SQL statement here
3) How did you determine that UNDO_RETENTION of 18000 was appropriate?
4) How much UNDO is your system generating?
6) Do you believe this is related to your performance problems? If so, why do you believe that?
At the risk of stating the obvious... You've told Oracle to try to maintain UNDO for 18,000 seconds (5 hours). You have a query that runs for roughly 6.25 hours. If, after running for 6.25 hours, that query needs a block that was modified, say, 6 hours ago, it may not find it because you've told Oracle you don't need it any longer.
Your UNDO_RETENTION needs to be greater than the longest-running query you expect to run. You can bump up UNDO_RETENTION if you'd like. However, I tend to believe that a query that died after 6.25 hours is probably a query that is in desparate need of tuning. If you reduce the query runtime to something less than 5 hours, you could keep UNDO_RETENTION at the current setting.
Justin

ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuc

Hi All,
I have exported a application and after that imported and tried to install it then i am getting this error:
ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 5, column 1: PLS-00306: wrong number or types of arguments in call to 'CREATE_REPORT_COLUMNS' ORA-06550: line 5, column 1: PL/SQL: Statement ignored <pre>declare s varchar2(32767) := null; begin s := null; wwv_flow_api.create_report_columns ( p_id=> 29524721731534348 + wwv_flow_api.g_id_offset, p_region_id=> 29524015959534345 + wwv_flow_api.g_id_offset, p_flow_id=> wwv_fl
History which happen:
everything was working fine in my workspace but 2 days back one of team member created customer demo application in the same work space so login was also failing and after struggling oneday i got that my authentication function was get overwritten by the demo user authentication so again i chaned by my bakup function now authentication is working but when i export my new developed application and tried to replace the existing application then i am getting the erroe which i have mention before.
1: I tried to replace by existing one
2: i tried to assign new application id
nothing is working so is it problem occues due to new demo application creation which i have deleted or other problem if other then how to solve if by demo then what i need to do .
But all applications are working well not able to install which i need to do with new developed application.
Please help me i am in tough situation.
Thanks in advance,
Amit

Amit,
The next useful test would be to run the file in SQL*Plus, connected as the application parsing schema. If it works, you will have imported the application. After that, please send me the file ([email protected]) and I'll figure out where the trouble is. If it fails in SQL*Plus, try to isolate the failing block. You'll get a pretty good idea by the prompts echoed to the output indicating the import progress.
Scott

ORA-00904:ROWID "Unknown Identifier"... trying to create a MV...

Hi,
I have created successfully a test mv which contains aggregates....
create materialized view log on dept with sequence, rowid (deptno,dname) including new values;
create materialized view log on emp with sequence, rowid(deptno,job,hiredate,sal) including new values;
create materialized view mv_dept_emp_
build immediate
refresh fast on commit
enable query rewrite
as
select a.dname, count(*) cnt, sum(b.sal) sal,count(b.sal) cnt_sal, b.job, b.hiredate
from dept a , emp b
where a.deptno=b.deptno
group by a.dname, b.job, b.hiredate
Now, I'm trying to create a mv which includes only a join... but the error ORA-00904:ROWID "Unknown Identifier" appears.... The sql stmt , i issue is as follows:
create materialized view mv_dept_emp
build immediate
refresh fast
enable query rewrite
as
select a.rowid, b.rowid, a.dname, b.ename, b.job, b.hiredate
from dept a , emp b
where a.deptno=b.deptno
Does anybody have any idea how to overcome this problem...???
Note: I use DB 10g v.2
Thank you,
Sim

Sim,
The error message is rather self explaining: you cannot create a (materialized) view with a column named "rowid". If you give it an alias, it will work:
SQL> create materialized view log on dept with sequence, rowid (deptno,dname) including new values;
Materialized view log created.
SQL>
SQL> create materialized view log on emp with sequence, rowid(deptno,job,hiredate,sal) including new values;
Materialized view log created.
SQL>
SQL> create materialized view mv_dept_emp
2 build immediate
3 refresh fast on commit
4 enable query rewrite
5 as
6 select a.dname, count(*) cnt, sum(b.sal) sal,count(b.sal) cnt_sal, b.job, b.hiredate
7 from dept a , emp b
8 where a.deptno=b.deptno
9 group by a.dname, b.job, b.hiredate
10 /
Materialized view created.
SQL> drop materialized view mv_dept_emp
2 /
Materialized view dropped.
SQL> create materialized view mv_dept_emp
2 build immediate
3 refresh fast
4 enable query rewrite
5 as
6 select a.rowid, b.rowid, a.dname, b.ename, b.job, b.hiredate
7 from dept a , emp b
8 where a.deptno=b.deptno
9 /
from dept a , emp b
ERROR at line 7:
ORA-00904: "ROWID": invalid identifier
SQL> create materialized view mv_dept_emp
2 build immediate
3 refresh fast
4 enable query rewrite
5 as
6 select a.rowid dept_rowid, b.rowid emp_rowid, a.dname, b.ename, b.job, b.hiredate
7 from dept a , emp b
8 where a.deptno=b.deptno
9 /
Materialized view created.Regards,
Rob.

ORA-01555 caused by SQL statement below - Kindly assist

Hi,
Version 9.2.0.7
I have been getting lots of ORA-01555 error logged into my alert log since 10 hours ago, happening every second till now.
The ORA-01555 is strange compared to those that have occured in my database before. From the error logged into the alert log, the statement is reflected as "table_4_200_c432_0_0_0". Any experts can advise what's exactly happening? The duration stated below seems really long.
ORA-01555 caused by SQL statement below (Query Duration=1225798260 sec, SCN: 0x077a.e8ab9ae8):
Tue Nov 4 19:31:00 2008
table_4_200_c432_0_0_0
thanks

That event trace is helpful only when you are getting ORA-01555 in trace files without a query.
Of course, you cannot get the diagnostic information for something that occurred in past (when diagnostics were not in place); so you have to wait till the next occurrence (if any) of ORA-01555 under similar conditions.

ORA-01555 caused by SQL statement below

Dear all,
How can I treat this error ?
ORA-01555 caused by SQL statement below (SQL ID: 9kh4f608ty7un, Query Duration=88767 sec, SCN: 0x0000.db7b3cef): : Category 1
Any ideas ? I did not touch the DB, so I am not sure why it came.
Thanks in advance,
Daniel.

hi Daniel,
You have to mentioned step by step solution (SQL statement) which you perform to resolve this issue.I am saying this for those sdn new users who have no S-user or access of SAP note.
Thanks and Regards,
majamil
Danke???

Oracle is adding "RowId" to select statement = ORA-00918 follows

Hi,
i've a problem with a strange case:
Oracle adds a rowId column to the select - and this select has joins to 2 other tables and a ora-00918 is the result!
But my application don't throw a java-excpetion - this appears only in the database log files - in the application, no problem is determined!
Database is suffering under this statement because in an hour, 1800 statements are failing... so what could this be and how i can prevent it to add this column!?
select rowid, t1.name, .......... from t1, t2, t3 etc....
I use the following statement:
Statement selStmt = stmt.getConnection().createStatement(
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
Thx for help!
lg
Manny

Tough to help if you don't provide you Java and OS infor and the Oracle JDBC driver version.
Post all of the relevant Java code that is used to setup and execute the prepared statement and handle the result set.
The Oracle JDBC driver uses ROWID to support scroll sensitive or updatable result sets so it is probably being added for this reason.
Remove the 'TYPE_SCROLL_SENSITIVE' setting and see if the problem goes away.
Seacrh for ROWID in the JDBC Dev guide (Chap 17) - http://www.stanford.edu/dept/itss/docs/oracle/10g/java.101/b10979/resltset.htm
>
17.1.2.2 Oracle JDBC Implementation for Result Set Updatability
To support updatability, Oracle JDBC uses ROWIDs to uniquely identify database rows that appear in a result set. For every query into an updatable result set, the Oracle JDBC driver automatically retrieves the ROWID along with the columns you select.
>
And since you are trying to produce a scroll sensitive result set you should do a test as described in this doc hint:
>
There is a simple way to determine if your query will probably produce a scroll-sensitive or updatable result set: If you can legally add a ROWID column to the query list, then the query is probably suitable for either a scroll-sensitive or an updatable result set. (You can try this out using SQL*Plus, for example.)
>
and:
>
The Oracle JDBC drivers use the ROWID to uniquely identify a row in a database table. As long as the ROWID is still valid when a driver tries to send an UPDATE or DELETE operation to the database, the operation will be executed.
>
Hope that helps.

Ora-1445 in an interactive report

I'm running into an issue adding an outer join to a SQL statement in an interactive report. When I add (+) to the where clause the I get the following error.
1 error has occurred
* The report query needs a unique key to identify each row. The supplied key cannot be used for this query. Please edit the report attributes to define a unique key column. ORA-01445: cannot select ROWID from, or sample, a join view without a key-preserved table
When I run the sql in the SQL workshop and it works fine and returns the results I expect. As soon as I add the (+) to the report, it fails. I have duplicated this issue on the apex.oracle.com site and can provide the details on how to reproduce the error.
Thanks,
Bruce

I tried to convert this where clause to the left outer join but it give me a table does not exist error. Perhaps you can see what I've done wrong. Here's the where clause.
from ni_requests a,
(select chain_num, chain_name, chain_seq_num from apex_so.cs_chain) b,
APEX_SO.ASSOCIATE ASSOCIATE,
(select NEW_ITEM_SEQ_NUM, assignor_comments, ASSIGNEE_ASSOC_SEQ_NUM from NI_ASSIGNEE where DATE_UNASSIGNED is null) ni_assignee
where a.NEW_ITEM_SEQ_NUM = NI_ASSIGNEE.NEW_ITEM_SEQ_NUM(+)
and NI_ASSIGNEE.ASSIGNEE_ASSOC_SEQ_NUM = ASSOCIATE.ASSOC_SEQ_NUM(+)
and a.chain_seq_num = b.chain_seq_num and NI_PROC_PHASE_SEQ_NUM = 14
The issue is on the outer from the ni_assignee to the associate table. This (+) spec causes the error in the interactive report but not in the workshop.
I tried this, maybe I did it incorrectly...
from ni_requests a,
(select chain_num, chain_name, chain_seq_num from apex_so.cs_chain) b,
left outer join APEX_SO.ASSOCIATE on NI_ASSIGNEE.ASSIGNEE_ASSOC_SEQ_NUM = ASSOCIATE.ASSOC_SEQ_NUM,
(select NEW_ITEM_SEQ_NUM, assignor_comments, ASSIGNEE_ASSOC_SEQ_NUM from NI_ASSIGNEE where DATE_UNASSIGNED is null) ni_assignee
where a.NEW_ITEM_SEQ_NUM = NI_ASSIGNEE.NEW_ITEM_SEQ_NUM(+)
and a.chain_seq_num = b.chain_seq_num and NI_PROC_PHASE_SEQ_NUM = 14
The above here give the table not found.
Thanks,
Bruce

Ora-907 during create table statement

Customer is receiving an ora-907 error running this sql statement and I cannot determine where the problem is, if there is extra spaces or if it's truly missing the right parenthesis.
SQL> set timing on
SQL> set echo on
SQL> set autotrace on
SQL> @sr.sql
SQL> create table tables_for_change_set (
2 change_set_name varchar2(30),
3 table_owner varchar2(30),
4 table_name varchar2(30),
5 column_names_0nf varchar2(4000),
6 constraint tfcs_pk primary key (change_set_name, table_owner, table_name)
7 )
8 ;
Table created.
Elapsed: 00:00:00.13
SQL>
SQL>
SQL> create table columns_for_change_set (
2 change_set_name varchar2(30),
3 table_owner varchar2(30),
4 table_name varchar2(30),
5 column_name varchar2(30),
6 data_type varchar2(30),
7 constraint cfcs_pk primary key (change_set_name, table_owner, table_name, column_name),
8 constraint cfcs_tfcs_fk foreign key (change_set_name, table_owner, table_name) references tables_for_change_set (ch
ange_set_name, table_owner, table_name)
9 using index (create index cfcs_tfcs_fk on columns_for_change_set (change_set_name, table_owner, table_name))
10 );
using index (create index cfcs_tfcs_fk on columns_for_change_set (change_set_name, table_owner, table_name))
ERROR at line 9:
ORA-00907: missing right parenthesis
Thanks,
Lisa

Welcome to the forum!
So why did you use your second post to the forum to resurrect a thread that is over a year old?
Hemant already provided the correct answer to the question and your reply to him that 'This contradicts the constraint documentation' doesn't specify what you mean by "this" but is wrong on any account.
You certainly can't be referring to Hemant's statement
>
The syntax "constraint cfcs_tfcs_fk foreign key ...", using the key words "foreign key" is for an out-of-line constraint definition.
>
Since the diagram clearly shows his statement is correct.
And you can't be referring to his statement
>
Furthermore, the "using index" clause is for Primary Key constraint , not for a Foreign Key. You should manually create the index separately.
>
Since the documentation states exactly what Hemant said.
See 'Using Indexes to Enforce Constraints' in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/clauses002.htm
>
Restrictions on the using_index_clause The following restrictions apply to the using_index_clause:
You cannot specify this clause for a view constraint.
You cannot specify this clause for a NOT NULL, foreign key, or check constraint.
>
Please check the dates in the threads before posting.

Getting ORA-00904 from various SPARQL statements

Hi,
I am currently working on a couple of Java services which offer access to semantic information using Jena. I have implemented two possible adapters so far, one "feeds" from an owl-file directly, one from an Oracle 11g (semantic technologies).
In both cases, I use SPARQL SELECT and CONSTRUCT statements for my queries. Querying the owl-file-based adapter with these statements, everything works fine. querying the Oracle adapter, I often get the following stacktrace:
Caused by: java.sql.SQLException: ORA-00904: "TYPE": ungültiger Bezeichner
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
     at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3431)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1203)
     at oracle.spatial.rdf.client.jena.Oracle.executeQuery(Oracle.java:352)
     at oracle.spatial.rdf.client.jena.Oracle.executeQuery(Oracle.java:315)
     at oracle.spatial.rdf.client.jena.OracleSemQueryPlan.executeBindings(OracleSemQueryPlan.java:431)
     ... 65 more
The SELECT statement used is:
==============
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT DISTINCT ?type ?label ?comment
WHERE { <http://www.demo-uri.com/test.owl#demoInstance> rdf:type ?type .
OPTIONAL { <http://www.demo-uri.com/test.owl#demoInstance> rdfs:label ?label .
FILTER(langMatches(lang(?label),'de') || (!langMatches(lang(?label),'*'))) . }
OPTIONAL { <http://www.demo-uri.com/test.owl#demoInstance> rdfs:comment ?comment .
FILTER(langMatches(lang(?comment),'de') || (!langMatches(lang(?comment),'*'))) }
==============
The generated SELECT clause is:
SELECT type$RDFVTYP, type$RDFLTYP, type$RDFLANG, type$RDFCLOB, decode(type$RDFVTYP, 'BLN', ('_:'||substr(type,instr(type,'m',4)+1)), type) type
FROM table(sdo_rdf_match('(<http://www.demo-uri.com/test.owl#demoInstance> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ?type) ', sdo_rdf_models('DEMO_MODEL'), sdo_rdf_rulebases('OWLPRIME'), null, null, NULL,' '))
I am really grateful for any advise! A simple statement like
[...]WHERE { <http://www.demo-uri.com/test.owl#demoInstance> rdf:type ?type }
works fine.
Best,
Damian

Thanks for the reply.
I have changed the statement according to your advice:
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT DISTINCT ?typ ?lbl ?cmnt
WHERE { <http://www.demo-uri.com/test.owl#demoInstance> rdf:type ?typ .
OPTIONAL { <http://www.demo-uri.com/test.owl#demoInstance> rdfs:label ?lbl .
FILTER(langMatches(lang(?lbl),"de") || (!langMatches(lang(?lbl),"*"))) . }
OPTIONAL { <http://www.demo-uri.com/test.owl#demoInstance> rdfs:comment ?cmnt .
FILTER(langMatches(lang(?cmnt),"de") || (!langMatches(lang(?cmnt),"*"))) }}
but still the same stacktrace :(
Caused by: java.sql.SQLException: ORA-00904: "TYP": ungültiger Bezeichner
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
     at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3431)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1203)
     at oracle.spatial.rdf.client.jena.Oracle.executeQuery(Oracle.java:352)
     at oracle.spatial.rdf.client.jena.Oracle.executeQuery(Oracle.java:315)
     at oracle.spatial.rdf.client.jena.OracleSemQueryPlan.executeBindings(OracleSemQueryPlan.java:431)
     ... 65 more
Edited by: user13170651 on 22.09.2010 02:32

Ora-02287 error in insert statement

Hello. I'm trying an insert query like that:
insert into table(a,b,c)
values
((select seq.nextval from dual),
'b-value',
'c-value'
And I get that error. How can I solve it?

Try..
insert into table(a,b,c)
values
(seq.nextval,
'b-value',
'c-value'
)

ORA-24338 Database connector error: statement handle not executed

I have written a procedure in PL/SQL Developer v 9.0.6.1665 that produces a ref cursor based on the criteria selected. It also produces a ref cursor if no data is selected.
I can run this procedure in pl/sql with no errors. The problem comes when I'm trying to run the report in Crystal (Crystal 2008 v 12.4.0.966). When I verify the database in Crystal I receive this error.
Is there a bug or something I'm overlooking? I've made sure the ref cursor for all outputs are exactly the same with the same name.

Welcome to the forums.
Crystal requires that all REF CURSORS be IN OUT parameters.
Not posting code makes it very possible for people to help you beyond very generic advice such as I have provided.
But Oracle 9.0.6? There is no value in working with something so old it belongs in a museum. Move your company into the current century.

Snapshot too old ORA-01555 from select statement (discoverer)??

Hi All
Am I loosing the plot .. but we have a select statement run from discoverer which is causing the famous snapshot too old error.
My understanding is that undo is generated from select/insert/update.
So why is the following discoverer Select statement causing the error?
from alert
ORA-01555 caused by SQL statement below (SQL ID: gk0wxgqmx66sh, Query Duration=3866 sec, SCN: 0x001e.089cf3f9):
SELECT ( ROUND(( TO_DATE(SYSDATE)-o101038.HIRE_DATE )/365,2) ) as
" bla bla
ORDER BY o101020.SUB_ORGANIZATION_NAME ASC
Thanks in Advance

simon.9999 wrote:
Hi All
Am I loosing the plot .. but we have a select statement run from discoverer which is causing the famous snapshot too old error.
My understanding is that undo is generated from select/insert/update.
So why is the following discoverer Select statement causing the error?
from alert
ORA-01555 caused by SQL statement below (SQL ID: gk0wxgqmx66sh, Query Duration=3866 sec, SCN: 0x001e.089cf3f9):
SELECT ( ROUND(( TO_DATE(SYSDATE)-o101038.HIRE_DATE )/365,2) ) as
" bla bla
ORDER BY o101020.SUB_ORGANIZATION_NAME ASC
Thanks in Advance
The SELECT statement is the victim.
Some session is doing DML against the same table against which the SELECT occurs & is likely doing COMMIT inside a LOOP.

Ora-1445 rowid on subselect statement

Similar Messages

Maybe you are looking for