'column ambiguously defined' due to automatic addition of rowid to every JDBC calls

We are using Weblogic 6.0 spf 1 and Oracle as back end.
When ever we fire an SQL using JDBC, Weblogic automatically adds 'rowid' to the
select clause and fires the SQL. If Oralce returns the error 'ORA-00918: column
ambiguously defined', the rowid is removed and the SQL is run as requested.
For example, when we say -
SELECT *
FROM SOME_TABLE
Rowid is added blindly and executed query will be
SELECT rowid, *
FROM SOME_TABLE
Oracle throws 'Column Ambigiously defined'. Upon this error weblogic fires originally
requested query
SELECT *
FROM SOME_TABLE
Another condition where it always fails is in case of SQL joins.
Is there any way to avoid adding rowid to the SQL statments?
Thanks
Satish

I would appreciate an answer to this same question: "Can the automatic addition of rowid after the select be prevented"? as it is causing several index hints to be rejected.

Similar Messages

How to get rid of ROWID in Join query -- ORA-00918: column ambiguously defined

Hi, All
the source of my data block is from two tables Emp and Title. My select statements is:
select a.name, b.title, b.start_date, b.end_date from Emp a, Title b where a.id = b.emp_id
But at run time, I got "ORA-00918: column ambiguously defined"
the wrapped statement becomes:
SELECT ROWID,a.name, b.title, b.start_date, b.end_date from Emp a, Title b where a.id = b.emp_id
I run the query in SQL*PLUS, found out it was ROWID caused problem.
Can anybody tell me how to get rid of ROWID? or I missed something in datablock defination?
Thanks in adance.
Deborah

I guess you are using oracle 7.x. In Oracle 8 and onwards, database lets you select ROWID from the views based on multiple views as long as view definition does not contain any aggregated functions or DISTINCT in it. Now coming back to forms ..Forms runtime engine uses ROWID to identify rows uniquely unless specified otherwise. If you are using forms 4.5/5.0 against Oracle 7.x , then change these properties and you should be able to run the form.
BLOCK PROPERTY
Key Mode : can be either updateable OR Non-updateable
( Certainly not 'Unique' .. That forces forms runtime engine to use ROWID to identify unique rows. )
ITEM PROPERTY
Identify one of the block items as unique. And then set the following property
Primary Key : True.
This should take care of rowid problem.
Regards,
Murali.
Hi, All
the source of my data block is from two tables Emp and Title. My select statements is:
select a.name, b.title, b.start_date, b.end_date from Emp a, Title b where a.id = b.emp_id
But at run time, I got "ORA-00918: column ambiguously defined"
the wrapped statement becomes:
SELECT ROWID,a.name, b.title, b.start_date, b.end_date from Emp a, Title b where a.id = b.emp_id
I run the query in SQL*PLUS, found out it was ROWID caused problem.
Can anybody tell me how to get rid of ROWID? or I missed something in datablock defination?
Thanks in adance.
Deborah

Strange behaviuor (bug?) with view (ora-918 column ambiguously defined)

Hallo everybody,
the following code works as expected;
select substr(fire_id,-4,2) as ct,zone_id, count(fire_id),sum(a_total) from
(select *
from fire right join fire_zone using (fire_id)
where definition_id = 1
and checked = 1
and substr(fire_id,-4,2) in (21,23)
and fire_id between 190400000000 and 200900000000)
group by substr(fire_id,-4,2),zone_id
order by ct, zone_id
but when a define a view for the subquery:
create or replace view tempfire as
select *
from fire right join fire_zone using (fire_id)
where definition_id = 1
and checked = 1
and substr(fire_id,-4,2) in (21,23)
and fire_id between 190400000000 and 200900000000
and then run
select substr(fire_id,-4,2) as ct,zone_id, count(fire_id),sum(a_total) from tempfire
group by substr(fire_id,-4,2),zone_id
order by ct, zone_id
I got the error ora-00918 column ambiguously defined for zone_id.
Is this a bug or is there a reason?
Thank you in advance,
Cheers,
Boris
Edited by: boris on Nov 19, 2009 6:49 AM
Edited by: boris on Nov 19, 2009 6:52 AM

user503699
I followed your suggestion and now it works. Thank you !
But something is strange ... this is the result of the desc tempfire ... and all the column names are different ...
desc tempfire
Name Null Type
FIRE_ID NOT NULL NUMBER(12)
START_DATE DATE
END_DATE DATE
LOCALITY VARCHAR2(56)
X_COORD NUMBER(6)
Y_COORD NUMBER(6)
COORD_RELIABILITY_ID NUMBER(1)
ALTITUDE NUMBER(4)
SITE_ID NUMBER(1)
EXPO_ID NUMBER(1)
SLOPE NUMBER(3)
X_BUSH NUMBER(1)
X_COPPICE NUMBER(1)
X_COPPICE_MIXED NUMBER(1)
X_SELVA NUMBER(1)
X_HIGH_FOREST_HARDWOOD NUMBER(1)
X_HIGH_FOREST_SOFTWOOD NUMBER(1)
X_HIGH_FOREST_MIXED NUMBER(1)
X_PIONEER NUMBER(1)
X_FORESTATION NUMBER(1)
S_BUSH NUMBER(8,2)
S_COPPICE NUMBER(8,2)
S_COPPICE_MIXED NUMBER(8,2)
S_SELVA NUMBER(8,2)
S_HIGH_FOREST_HARDWOOD NUMBER(8,2)
S_HIGH_FOREST_SOFTWOOD NUMBER(8,2)
S_HIGH_FOREST_MIXED NUMBER(8,2)
S_PIONEER NUMBER(8,2)
S_FORESTATION NUMBER(8,2)
A_FOREST NUMBER(8,2)
A_GRASSLAND NUMBER(8,2)
A_NONPRODUCTIVE NUMBER(8,2)
A_TOTAL NUMBER(8,2)
D_CASTANEA NUMBER(1)
D_QUERCUS NUMBER(1)
D_FAGUS NUMBER(1)
D_BETULA NUMBER(1)
D_OTHER_HARDWOOD NUMBER(1)
D_PINUS NUMBER(1)
D_PICEA NUMBER(1)
D_LARIX NUMBER(1)
D_OTHER_SOFTWOOD NUMBER(1)
DIAMETER NUMBER(3)
LITTER_ID NUMBER(1)
HERB_LAYER_ID NUMBER(1)
BUSH_LAYER_ID NUMBER(1)
FIRE_SURFACE NUMBER(1)
FIRE_CROWN NUMBER(1)
FIRE_SINGLE_TREE NUMBER(1)
FIRE_SUBSURFACE NUMBER(1)
DAMAGE_FOREST_ID NUMBER(1)
DAMAGE_SOIL_ID NUMBER(1)
HEIGHT_DAMAGE NUMBER(4,2)
F_PROTECTION NUMBER(1)
F_ECONOMIC NUMBER(1)
F_RECREATION NUMBER(1)
CAUSE_ID NUMBER(2)
OTHER_CAUSE VARCHAR2(200)
CAUSE_RELIABILITY_ID NUMBER(1)
ALARM_FORESTDEP DATE
CHECKED NUMBER(1)
DATA_FROM_FORESTDEP NUMBER(1)
DATA_FROM_FIREMANDEP NUMBER(1)
DATA_FROM_HISTORY NUMBER(1)
INSERT_DATE DATE
INSERT_BY VARCHAR2(16)
UPDATE_DATE DATE
UPDATE_BY VARCHAR2(16)
OLD_TI_AFFDFO VARCHAR2(1)
OLD_TI_S_SPES NUMBER(8,2)
OLD_TI_PICFOR VARCHAR2(1)
OLD_TI_FIRE_TYPE VARCHAR2(1)
OLD_TI_DOMINANT_SPECIES VARCHAR2(1)
OLD_TI_CAUSE VARCHAR2(2)
OLD_TI_FOREST_TYPE VARCHAR2(1)
START_DATE_RELIABILITY_ID NUMBER(1)
END_DATE_RELIABILITY_ID NUMBER(1)
DEFINITION_ID NUMBER(1)
ZONE_ID NOT NULL NUMBER(8)
79 rows selected
I'm still interested hoe to use hints. Can anybody tell me?
Thank you
Boris

ORA-00918: column ambiguously defined : while using inner Select

Hi
could you please help me to solve the following from.
I have a query like this
SELECT * FROM (SELECT ZMV.VENDOR_NAME,FR.PO_NUM,ZMV.PART_NUMBER,FR.ZAC_ITEM_DESCRIPTION,ZMV.QUANTITY_ORDERED,FR.QUANTITY_RECEIVED,ZMV.PO_UOM_CODE,FR.VENDOR_INV,FR.FORWARDER_REF,FR.PCS,TY.DESCRIPTION,FR.GROSS_WGT,FR.NET_WGT,FR.CFT,TR.DESCRIPTION,FR.PRO,FR.FORWARDER_REMARK,FR.RECAP_ID,FR.ZAC_REMARK,FR.SHIPMENT_BY FROM FWD_RECAP FR,ZAC_METRO_VIEW ZMV,FWD_MASTER_TYPE TY,FWD_MASTER_TRUCK TR WHERE FR.TYPE_ID=TY.TYPE_ID AND FR.TRUCK_ID=TR.TRUCK_ID AND FR.PO_LINE_ID=ZMV.PO_LINE_ID AND FR.PACKAGE_ID=0 AND FR.OPERATIONING_UINT_ID=511 AND FR.FORWARDER='METRO,ITALY' ORDER BY FR.PO_LINE_ID DESC) WHERE ROWNUM <=10
But while executing the following error showing,
SELECT * FROM (SELECT ZMV.VENDOR_NAME,FR.PO_NUM,ZMV.PART_NUMBER,FR.ZAC_ITEM_DESCRIPTION,ZMV.QUANTIT
ERROR at line 1:
ORA-00918: column ambiguously defined
For this problem i got some answers from web sites, they saying as follows, but i am using like that only.
(ORA-00918: COLUMN AMBIGUOUSLY DEFINED)
Use table aliases and prefix all column names by their aliases when more than one table is involved in a query. This reduces parse time AND prevents future syntax errors if someone adds a column to one of the tables with the same name as a column in another table.
awaiting your immediate reply
Thankyou
Jobin [[email protected]]

In your inline view you have fields
TY.DESCRIPTION and TR.DESCRIPTION which are the same
name DESCRIPTION for covered SQL.
place TY.DESCRIPTION TY_DESCRIPTION and
TR.DESCRIPTION TR_DESCRIPTION in your code:
SELECT * FROM (SELECT ZMV.VENDOR_NAME,FR.PO_NUM,ZMV.PART_NUMBER,FR.ZAC_ITEM_DESCRIPTION,ZMV.QUANTITY_ORDERED,FR.QUANTITY_RECEIVED,ZMV.PO_UOM_CODE,FR.VENDOR_INV,FR.FORWARDER_REF,FR.PCS,TY.DESCRIPTION TY_DESCRIPTION ,FR.GROSS_WGT,FR.NET_WGT,FR.CFT,TR.DESCRIPTION TR_DESCRIPTION,FR.PRO,FR.FORWARDER_REMARK,FR.RECAP_ID,FR.ZAC_REMARK,FR.SHIPMENT_BY FROM FWD_RECAP FR,ZAC_METRO_VIEW ZMV,FWD_MASTER_TYPE TY,FWD_MASTER_TRUCK TR WHERE FR.TYPE_ID=TY.TYPE_ID AND FR.TRUCK_ID=TR.TRUCK_ID AND FR.PO_LINE_ID=ZMV.PO_LINE_ID AND FR.PACKAGE_ID=0 AND FR.OPERATIONING_UINT_ID=511 AND FR.FORWARDER='METRO,ITALY' ORDER BY FR.PO_LINE_ID DESC) WHERE ROWNUM <=10
Rgds

Version Change from 10.2.0.3.0 to 11.2.0.4.0 - Column ambiguously defined

Hi,
Our oracle version has been upgraded from 10g to 11g.
After upgrade we face serious problem in compiling several packages, procedures and views and that throws an error "Column Ambiguously Defined", which was running perfectly in 10g version.
I have come through several blogs like, this problem occurs for many ppl as part of upgrade from 10g to 11g and the only solution is to change the code.
But in our case we have many numbers of objects like procedures, packages and views where this error occurs, do we have any common solution for overcome this problem (without changing the code)?
Regards,
Ananth

e7a47215-0e59-4d88-a082-7ad5e83ce5b0 wrote:
Hi,
Our oracle version has been upgraded from 10g to 11g.
After upgrade we face serious problem in compiling several packages, procedures and views and that throws an error "Column Ambiguously Defined", which was running perfectly in 10g version.
I have come through several blogs like, this problem occurs for many ppl as part of upgrade from 10g to 11g and the only solution is to change the code.
But in our case we have many numbers of objects like procedures, packages and views where this error occurs, do we have any common solution for overcome this problem (without changing the code)?
Regards,
Ananth
You will need to bite the bullet & change the code

Column ambiguously defined

select distinct hp.SYER_PEMBILANG||'/'||hp.SYER_PEMBILANG semua, kp.NAMA kod_pihak_nama,
kb.nama kod_bpm_nama,
kd.NAMA kod_daerah_nama,
kl.NAMA kod_lot_nama,
mo.ID_MOHON ,
ha.NO_LOT,
ha.KOD_HAKMILIK,
ha.NO_HAKMILIK
kd.NAMA kod_daerah_nama
from
mohon mo,
mohon_pihak mp join kod_pihak kp on (mp.kod_pihak=kp.kod),
hakmilik ha join kod_bpm kb on(ha.kod_bpm=kb.kod)
join kod_daerah kd on(ha.kod_daerah=kd.kod)
join kod_lot kl on (ha.KOD_LOT=kl.kod),
mohon mo join kod_caw kc on(mo.kod_caw=kc.kod),
kod_caw kc join kod_daerah kd on(kc.kod_daerah=kd.kod),
mohon_hakmilik mh,
hakmilik_pihak hp
where
mp.KOD_PIHAK ='PG'
and mo.KOD_CAW=kc.KOD
and kc.KOD_DAERAH=kd.kod
and mo.id_mohon=:p_id_mohon
and ha.KOD_BPM=kb.KOD
and ha.KOD_DAERAH=kd.KOD
and ha.KOD_LOT=kl.KOD
and mo.ID_MOHON=mh.ID_MOHON
and mh.id_hakmilik=ha.ID_HAKMILIK
and mo.ID_MOHON=mp.ID_MOHON
and mp.KOD_PIHAK=kp.KOD
and hp.ID_HAKMILIK=ha.ID_HAKMILIKcolumn ambiguously defined
Edited by: user9093689 on Nov 8, 2010 12:55 AM

Is nobody going for the "new" syntax?
I belive this makes the relationship between tables so much more visible (and a LEFT to mohon would be not possible with "old" JOIN.
SELECT
DISTINCT hp.SYER_PEMBILANG||'/'||hp.SYER_PEMBILANG semua, kp.NAMA kod_pihak_nama,
kb.nama        kod_bpm_nama,
kd.nama        kod_daerah_nama,
kl.nama        kod_lot_nama,
mo.id_mohon ,
ha.no_lot,
ha.kod_hakmilik,
ha.no_hakmilik
kd.nama kod_daerah_nama
FROM mohon_pihak mp
INNER JOIN kod_pihak kp
ON (mp.kod_pihak=kp.kod)
INNER JOIN kod_bpm kb
ON(ha.kod_bpm=kb.kod)
INNER JOIN kod_lot kl
ON (ha.KOD_LOT=kl.kod)
-- twice INNER join kod_daerah kd
INNER JOIN hakmilik ha
on (   ha.KOD_BPM=kb.KOD
   AND ha.kod_daerah=kd.kod
   AND ha.KOD_DAERAH=kd.KOD
   AND ha.KOD_LOT=kl.KOD)
-- twice INNER JOIN mohon mo
INNER join kod_caw kc
ON(mo.kod_caw=kc.kod)
-- twice INNER JOIN kod_caw kc
INNER join kod_daerah kd
ON(kc.kod_daerah=kd.kod)
INNER JOIN mohon_hakmilik mh
ON (mh.id_hakmilik=ha.id_hakmilik)
INNER JOIN hakmilik_pihak hp
ON hp.id_hakmilik=ha.id_hakmilik
INNER JOIN mohon mo
ON ( mo.ID_MOHON= mh.ID_MOHON
    AND mo.KOD_CAW = kc.KOD
    AND mo.ID_MOHON=mp.ID_MOHON)
WHERE
     mp.KOD_PIHAK ='PG'
AND mo.id_mohon=:p_id_mohon
;--andy

Automatic Passing of parameters with every RMI Call

We need the ability to automatically pass a couple of objects, both Strings in this case, with every RMI call we make from our clients (multiple clients) to the servers (multiple servers). Currently I'm using some code that Rickard �berg wrote a while ago that uses UnicastRef.marshalCustomCallData() and UnicastServerRef.unmarshalCustomCallData() so do this. I extended these 2 classes and rolled my own UnicastRemoteObject. This has worked out great but now I need to also use Custom Socket Factories, to get through the firewalls that our customer has. So I thought I could just extend UnicastRef2 and UnicastServerRef2 but when I do the servers never get
bound to the RmiRegistry.
We don't want to explicitly add these arguments to all our remote interfaces because we have a bunch of remote object classes and don't want to rely on the programmer sending the correct values or when writing new remote methods making sure that they these arguments are included.
We're using 1.4.1, but this also fails with 1.3.1.
The only thing I see in the logs is:
Oct 2, 2002 1:53:39 PM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(1)-216.100.254.188: [216.100.254.188: sun.rmi.registry
.RegistryImpl[0:0:0, 0]: void rebind(java.lang.String, java.rmi.Remote)]
Oct 2, 2002 1:53:50 PM sun.rmi.server.UnicastServerRef logCall
FINER: RMI TCP Connection(2)-216.100.254.188: [216.100.254.188: sun.rmi.registry
.RegistryImpl[0:0:0, 0]: java.rmi.Remote lookup(java.lang.String)]
Oct 2, 2002 1:53:50 PM sun.rmi.server.UnicastServerRef logCallException
FINE: RMI TCP Connection(2)-216.100.254.188: [216.100.254.188] exception:
java.rmi.NotBoundException: FileManager
at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:106)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:342
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:207)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:536)
So anyone know why this doesn't work when I supply the SocketFactories?
Is there a better way to accomplish this than extending sun.rmi.server classes (which was really easy)? I can supply the source for my classes if it helps, though my UnicastServerRef2 and UnicastRef2 classes are pretty simple.
Mark.

First, did you really bind the servers?
Second, does it work with the socket factories but without your custom Ref classes? I would suspect the socket factories here. Do they have a reasonable override for the Object.equals() method?
EJP

Eclipselink producing incorrect sql - ORA-00918: column ambiguously defined

We have a table with many columns .A1 .A2 .A3.... .A125 .N1 .N2 .N3... .N95 and with a simple jpql join it comes up with 2 columns that are ...AS N1150 and causing an ambiguous column error ...
Does any one know of a valid workround or if this is a known bug. No problems were present in toplink, just eclipselink....
it appears to be doing a count and suffixing the count to the column name to make sure the columns have unique id's - but failing:
K1 -> K1 _1_
N41 -> N41 _2_
N11 -> N11 _50_
... then 100 columns later
N1 -> N1 _150_
the jpql is :
@NamedQuery(name=NamedQueryNames.XREF_IMPORT_SELECT,
               query="SELECT t FROM Tran t, Xref x "+
               " WHERE t.key = x.a1 "+
               " AND x.key.k1 = :partial "+
               " AND x.key.k2 LIKE :partialX " +
               " ORDER BY x.key.k2")
Tran has fields k1,k2, a1, a2...a125, n1, n2...n95
xref has k1,k2,a1,a2..a5, n1,n2,n3
the sql eclipse link produces for the query is :
SELECT *
FROM
(SELECT
/*+ FIRSTROWS */
a.*,
ROWNUM rnum
FROM
(SELECT t1.K1 AS K11,
t1.N41 AS N412,
t1.N40 AS N403,
t1.N45 AS N454,
t1.N44 AS N445,
t1.A120 AS A1206,
t1.N43 AS N437,
t1.A121 AS A1218,
t1.N42 AS N429,
etc
t1.N25 AS N2547,
t1.N10 AS N1048,
t1.N12 AS N1249,
t1.N11 AS N1150,
t1.N17 AS N1751,
a load more columns
t1.A65 AS A65147,
t1.A68 AS A68148,
t1.A67 AS A67149,
t1.N1 AS N1150,
t1.A41 AS A41151,
t1.N5 AS N5152,
etc
FROM COREXFA t0,
CORETRA t1
WHERE (((t1.K1 = t0.A1)
AND (t0.K1 = ?))
AND (t0.K2 LIKE ?))
ORDER BY t0.K2 ASC
) a
WHERE ROWNUM <= ?
WHERE rnum > ?

This issue is cause by the aliasing done because you are using firstResult/maxResult. I think there is already a bug logged for this issue, please vote for the bug.
See,
http://old.nabble.com/Duplicate-aliases-generated-for-columns-%281.1.3%29-td28039552.html
Some workarounds would be,
- avoid using firstResult/maxResult
- rename the columns
- use native SQL
- use a cursor query instead of firstResult/maxResult
James : http://www.eclipselink.org

Oracle 11g bug for column ambigously defined error

I have below format query running on Oracle 10g without any issues
select col1
from (select col1
from (select 'A' col1
from dual)
) v1
inner join (select col1 as col2
from (select 'A' col1
from dual)
) v2
on (v1.col1=v2.col2);
When I run the exact same query on Oracle 11g I get column ambiguously defined error. But when I change the query to as below it works fine on 11g
select v1.col1
from (select col1
from (select 'A' col1
from dual)
) v1
inner join (select col1 as col2
from (select 'A' col1
from dual)
) v2
on (v1.col1=v2.col2);
Is it because 11g ignores column alias in my inner queries.

I'd tend to agree that this seems to be a bug in 11.1.0.7 (at least, that's the version I'm running it in)
It's not even that Oracle doesn't know about the column aliases, you can remove the aliases in the ON without a problem, i.e.
SELECT v1.col1
   FROM
(SELECT col1 FROM
    (SELECT 'A' col1 FROM dual
) v1
INNER JOIN
(SELECT col1 AS col2 FROM
    (SELECT 'A' col1 FROM dual
) v2
     ON (col1=col2);works fine. Using the old join syntax also seems to work fine
SELECT col1
   FROM
(SELECT col1 FROM
    (SELECT 'A' col1 FROM dual
) v1,
(SELECT col1 AS col2 FROM
    (SELECT 'A' col1 FROM dual
) v2
WHERE (col1=col2);So it appears that something in the SQL 99 parser is broken. Have you logged a bug in Metalink?
Justin

Defining Accounts for Automatic Offsetting Entry

Dear all,
From IMG: I Access the activity using the following navigation option:
Financial Accounting (New) ->Accounts Receivable and Accounts Payable ->Business Transactions -> Postings with Alternative Reconciliation Account -> Other Special G/L Transactions -> Define Accounts for Automatic Offsetting Entry
I'd like to ask a question: If I can define more items in column Account type/sp.GL ind? where I can do it?
Thank in advance
Minhtb

Hi
Based on Business Transactions u can assign the Alt Gl MRecords. Like Down Payments, Payment Requests etc.,
Shammi
assign points if it is helpful

"column ambigously defined" error

ORA-00918: column ambigously defined
00918.00000 - "column ambigously defined"
*Cause:
*Action
Vendor code 918
I've gotten this error on a few of the queries I've ran in SQL Developer 1.5 and tried to export to xls, but when I run and try to export the same query in 1.2.1 it's fine. There is another popup box that provides this detail (below). What causes this error and how can it be fixed?
java.lang.NullPointerException
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.addColumnsToTree(ColumnPanel.java:85)
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.showPanel(ColumnPanel.java:61)
     at oracle.dbtools.raptor.dialogs.export.ColumnPanel.<init>(ColumnPanel.java:50)
     at oracle.dbtools.raptor.dialogs.actions.TableExportAction.showPanels(TableExportAction.java:291)
     at oracle.dbtools.raptor.dialogs.actions.TableExportAction.launchDlg(TableExportAction.java:189)
     at oracle.dbtools.raptor.format.ui.ExportContextMenuListener$1.actionPerformed(ExportContextMenuListener.java:137)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1774)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

The problem is that SQL Developer 1.5.0/1 generates and executes a query that is not quite your original query to assist with the export dialog (presumably to populate the Columns tab). Note that it also does a single bulk fetch against this query, which can cause performance issues when trying to export the results of long running queries.
For the example query of:
select t.id, t2.id from t,t2;
this generated query is:
select * from ( select "ID","ID" from ( select t.id, t2.id from t,t2 ) )
The export works in 1.2.1 simply because they did not generate this additional query, but re-executed the original query.
theFurryOne

KMTL - How to add Column for OVER DUE DAYS in report

Dear Concern,
We are Microsoft Dynamics NAV 2013 users, We want a little change on Reminder Report (In report there is due date we inserted column for OVER DUE DAYS right side to Due Date column in we required Expression of which type of formula that
shows us the Over Due Days for particular.
Please every one confirm or suggest for this error.
Thanks & regards,
Laxman Sonar

Hi Laxman Sonar,
Per my understanding that you have an date field(Due Date) in the report and now you want to get the over due days based on this field and display at right of the date field in the report, right?
I have tested on my local environment that we have two method to do this, one is to add the datediff functon in the query to get the overdue days and another method is to using expression in the report.
Details information below for your reference:
Method one:
Modify the query as below to get the new field(OverDue Days):
SELECT DueDate, DATEDIFF(day, DueDate, GETDATE()) AS OverDueDays
FROM tableName
Method Two:
Add an calculated fields and then add the expression below to get the value for this field or just add expression directly in the new field:
=Datediff("d",Fields!DueDate.Value,Today())
If your problem still exists, please try to provide us some sample date and more details information about your requirements.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

"Add a column to show each of these additional fields: " doesn't support person feild

"Add a column to show each of these additional fields: " doesn't support person feild
I've seen that its not supported in 2010 version of sharepoint but I was hoping in the last 3 years its been fixed for the 2013
Any idea if this will be fixed or not?

Given that it hasn't been fixed so far, i doubt it.
The reason it doesn't work for some columns is that they themselves are a form of lookup column. I suspect MS have disallowed it to prevent looping, where a lookup column eventually starts trying to look up on itself. There may be other technical challenges
to making a double hop lookup column.

Table names and column names defined by other languages, not English.

Hi, everyone.
I am wondering if there are any possible problems or any inconvenience
when I define table names and column names by Japanese, not English.
Currently, we are using SQL server 2000 as a db and windows as a operating
system. In the near future, we have the plan to change the database software
and operating system to "Oracle 10g" and "Linux O/S".
I have not experienced the oracle database, which has table names and column
names defined by other languages, not English.
Personally, I would like to use English as table names and column names.
In this case, I might have to provide appropriate reasons.
Are there any possible problems or any "inconvenience" in terms of
system maintenance, development, or something else ?
What could be pros and cons in this case?
Thanks in advance.
Have a nice day.
Best Regards.
Ho.

First you need to make sure your database has character set that support Japanese.
Choosing a Character Set
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#i1007681
The main "inconvenience" you will have is if the client doesn't support Japanese or unicode, it will have trouble to access the table.
And say in future after the application been developed, you want to implement the schema in some English environment, you will have hard time to do it.
My point is English tablename and column names doesn't prevent you use it in Japanese environment and save Japanese data but not vice-versa. Hope you understand.

With the automatic addition of an update on both home & work computers, attachments went from being identified & opened as appropriate files, even when identified as .doc or .pdf, etc., all become .ashx

With the automatic addition of an update on both home & work computers, attachments went from being identified & opened as appropriate files, even when identified as .doc or .pdf, etc., all become .ashx (see details below)

With the automatic addition of an update on both home & work computers, attachments went from being identified & opened as appropriate files, even when identified as .doc or .pdf, etc., all become .ashx (see details below)

'column ambiguously defined' due to automatic addition of rowid to every JDBC calls

Similar Messages

Maybe you are looking for