3.0.0RC2 MappingTool producing bad SQL

It looks like <jdbc-field-map type="many-many" table="TestServiceKeyArray"
element-column
..pk="keyArray" ref-column.pk="parent" order-column="seqno"/> is producing
bad SQL through MappingTool. It gives the following exception when run as
"kodo.jdbc.meta.MappingTool -action buildSchema ..."
It looks like the "seqno" order-column is of type "OTHER", which is not
correct.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Syntax error or access
violation, message from server: "You have an error in your SQL syntax.
Check the manual that corresponds to your MySQL server version for the right
syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE TABLE
TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno OTHER)}
[code=1064, state=42000]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Syntax error or access
violation, message from server: "You have an error in your SQL syntax.
Check the manual that corresponds to your MySQL server version for the right
syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE TABLE
TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno OTHER)}
[code=1064, state=42000]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:832)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Caused by: com.solarmetric.jdbc.ReportingSQLException: Syntax error or
access violation, message from server: "You have an error in your SQL
syntax. Check the manual that corresponds to your MySQL server version for
the right syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE
TABLE TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno
OTHER)} [code=1064, state=42000]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecora
tor.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnection
Decorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingSta
tement.executeUpdate(LoggingConnectionDecorator.java:506)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
... 2 more

I'm using mysql 4.0.15 and mysql connector (jdbc driver) 3.0.9.
Ben
"Stephen Kim" <[email protected]> wrote in message
news:[email protected]...
What version of MySQL and driver are you using?
Ben Eng wrote:
It looks like <jdbc-field-map type="many-many"
table="TestServiceKeyArray"
element-column
.pk="keyArray" ref-column.pk="parent" order-column="seqno"/> isproducing
bad SQL through MappingTool. It gives the following exception when runas
"kodo.jdbc.meta.MappingTool -action buildSchema ..."
It looks like the "seqno" order-column is of type "OTHER", which is not
correct.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Syntax error or access
violation, message from server: "You have an error in your SQL syntax.
Check the manual that corresponds to your MySQL server version for theright
syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE TABLE
TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno OTHER)}
[code=1064, state=42000]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Syntax error or access
violation, message from server: "You have an error in your SQL syntax.
Check the manual that corresponds to your MySQL server version for theright
syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE TABLE
TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno OTHER)}
[code=1064, state=42000]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:832)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Caused by: com.solarmetric.jdbc.ReportingSQLException: Syntax error or
access violation, message from server: "You have an error in your SQL
syntax. Check the manual that corresponds to your MySQL server versionfor
the right syntax to use near 'OTHER)' at line 1" {stmnt 30301818: CREATE
TABLE TestServiceKeyArray (keyArray BIGINT, parent VARCHAR(255), seqno
OTHER)} [code=1064, state=42000]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecora
tor.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnection
Decorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingSta
tement.executeUpdate(LoggingConnectionDecorator.java:506)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
... 2 more
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Similar Messages

[1.1.1.25.14] BUG: Export to insert statement produces bad sql

I haven't seen anyone from oracle on the thread below and wanted to make sure it gets seen so that the bug can be logged.
See this thread:
Export to INSERT error

It has to do with data types. I think that the data appears in the correct order, but the quotes don't.
For example:
Using HR.COUNTRIES as an example:
Reorder REGION_ID to the first position and export to insert via file.
The file looks like this. Note the lack of quotes around COUNTRY_ID:
REM INSERTING into COUNTRIES
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('2',AR,'Argentina');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',AU,'Australia');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',BE,'Belgium');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('2',BR,'Brazil');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('2',CA,'Canada');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',CH,'Switzerland');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',CN,'China');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',DE,'Germany');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',DK,'Denmark');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',EG,'Egypt');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',FR,'France');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',HK,'HongKong');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',IL,'Israel');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',IN,'India');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',IT,'Italy');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',JP,'Japan');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',KW,'Kuwait');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('2',MX,'Mexico');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',NG,'Nigeria');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',NL,'Netherlands');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('3',SG,'Singapore');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('1',UK,'United Kingdom');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('2',US,'United States of America');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',ZM,'Zambia');
Insert into COUNTRIES ("REGION_ID","COUNTRY_ID","COUNTRY_NAME") values ('4',ZW,'Zimbabwe');
Thanks,
Eric

OBIEE consistently producing very very bad SQL

Hi,
We need some advice, or would like to know if people have had similar experiences. Here is our issue.
Users running reports and filtering data in presentation layer of OBIEE are seeing the OBIEE generate the SQL and sends it to the database.
This SQL which is auto generated by the OBIEE server is extremely costly. We are not whu OBIEE produces such bad sql - anyone have same problem?
When we look at explains, we see that most costly operations are when HASH operations are used. This is consistent throughout all OBIEE generated SQL.
As the SQL is of ad hock nature we do not use SPB's etc.
We are puzzled and are not sure where to start w.r.t troubleshooting.
Please help.

Dear guru.
Let me know what's may be wrong ?
My post is closely related to bad SQL thread.
Shortly speaking, I'd like to discuss multiple star problem.
So, Oracle Business Intelligence 11.1.1.6.0
I have three fact table A,B,C joined to common link table D ( look as dimension in Administrator )
A and B have inner join with D, while C has left outer join to D ( actually outer join defined only in BMM cause don't see how set outer join on physical layer for C ).
The matter is in generated SQL query which is broken, i.e. can't be compiled in Oracle DB.
Let me give broken piece of generated SQL.
As you can see, the subquery has reference to table T69242 in WHERE, but no such table in FROM section:
SACOMMON821644 AS
(SELECT
/*+ MATERIALIZE */
DISTINCT T68993.NAME AS c1,
T69266.DISTRICT2 AS c2,
CASE
WHEN T68993.DEPARTMENTID IN
(SELECT D1.c1 AS c1 FROM SASUBWITH820608 D1
THEN 1
ELSE 0
END AS c3,
CASE
WHEN T69266.OKATO_KOD IN
(SELECT D1.c1 AS c1
FROM SASUBWITH820633 D1
THEN 1
ELSE 0
END AS c4,
T68993.DEPARTMENTID AS c5,
T69266.OKATO_KOD AS c6,
T68993.PARENT AS c7,
T69266.PARENT_OKATO_KOD AS c8
FROM BI_MSK_DISTRICTS_STAT_HIER T69233
MOS_DISTRICTS_STAT T69266
BI_DEPARTMENTS_MFC T68993
BI_MFC_HIER T69068
DEP_OPERATORS_CNT T69220
INCIDENTS T69648
MOS_DISTRICT_POPULATION T69410
WHERE ( T69233.MEMBER_KEY = T69410.OKATO_KOD
AND T68993.DEPARTMENTID = T69068.ANCESTOR_KEY
AND T69068.MEMBER_KEY = T69220.DEPARTMENTID
AND T69220.DEPARTMENTID = T69242.DEPARTMENTID*
AND T69233.ANCESTOR_KEY = T69266.OKATO_KOD
AND T69242.OKATO_KOD* = T69410.OKATO_KOD
AND T68993.DEPARTMENTID IN
(SELECT D1.c1 AS c1 FROM SASUBWITH820658 D1
AND T69266.OKATO_KOD IN
(SELECT D1.c1 AS c1 FROM SASUBWITH820683 D1
Meanwhile in aggregation subquery of that generated SQL we have requred table
SACOMMON821667 AS
(SELECT
/*+ MATERIALIZE */
TRUNC(SUM( DISTINCT T69220.OPER_TOTAL)) AS c9,
T68993.DEPARTMENTID AS c10,
T68993.PARENT AS c11,
T69266.OKATO_KOD AS c12,
T69266.PARENT_OKATO_KOD AS c13,
SUM( DISTINCT T69410.POPUL_SIZE) AS c14,
SUM(T69648.TOTAL / NULLIF( T69242.OKATO_COUNT, 0)) AS c15
FROM BI_MSK_DISTRICTS_STAT_HIER T69233
MOS_DISTRICTS_STAT T69266
BI_DEPARTMENTS_MFC T68993
BI_MFC_HIER T69068
DEP_OPERATORS_CNT T69220
MFC_ADDRESSOKATO T69242*
LEFT OUTER JOIN INCIDENTS T69648
ON T69242.DEPARTMENTID = T69648.DEPARTMENTIDFROM,
MOS_DISTRICT_POPULATION T69410
WHERE ( T69242.OKATO_KOD = T69410.OKATO_KOD
AND T69233.ANCESTOR_KEY = T69266.OKATO_KOD
AND T69233.MEMBER_KEY = T69410.OKATO_KOD
AND T69220.DEPARTMENTID = T69242.DEPARTMENTID
AND T68993.DEPARTMENTID = T69068.ANCESTOR_KEY
AND T69068.MEMBER_KEY = T69220.DEPARTMENTID
AND T68993.DEPARTMENTID IN
(SELECT D1.c1 AS c1 FROM SASUBWITH820658 D1
AND T69266.OKATO_KOD IN
(SELECT D1.c1 AS c1 FROM SASUBWITH820683 D1
GROUP BY T68993.DEPARTMENTID,
T68993.PARENT,
T69266.OKATO_KOD,
T69266.PARENT_OKATO_KOD
And it's time to show Consistency Check results in Administrator.
There is no errors, but
WARNINGS:
Business Model Сводная таблица:
[39008] Logical dimension table A_MFC_ADDRESSOKATO has a source A_MFC_ADDRESSOKATO that does not join to any fact source.
[39020] Logical table source "Сводная таблица"."FCT Incidents"."A_Incidents": No path has been found to link all tables. There is no link between the set ( 'A_DEP_OPERATORS_CNT', 'A_MFC_ADDRESSOKATO', 'A_MOS_DISTRICT_POPULATION' ) and the set ( 'A_Incidents' ).
[39020] Logical table source "Сводная таблица"."A_DEP_OPERATORS_CNT"."A_DEP_OPERATORS_CNT ": No path has been found to link all tables. There is no link between the set ( ) and the set ( ).
[39020] Logical table source "Сводная таблица"."A_MOS_DISTRICT_POPULATION"."A_MOS_DISTRICT_POPULATION": No path has been found to link all tables. There is no link between the set ( ) and the set ( ).
I wonder, how that link can be realized, when fact tables already have joins to common dim A_MFC_ADDRESSOKATO.
Should I create Logical Dimmension for A_MFC_ADDRESSOKATO while it is actually bridge table in terms of 10G ?
Besides, as we can see from query, A B and C have its own dims.
So, finally as a result in Answers we have
ORA-00904: "T69242"."OKATO_KOD": invalid identifier at OCI call OCIStmtExecute
It should be mentioned that error is appeared only when I put measure from A_Incidents (C alias) on analys in Answers, till that all worked correctly, i.e. A,B joined successfully to D
and SQL query gave desired result.
Any suggestion on issue are greately appreciated.
Sorry for unformatted SQL, still don't know how to do it.
Sorry for the post as reply cause I don't see how create new thread.
Hope, my explanation was clear.

Bad SQL from 2.3.4 (and 2.3.2)

Hi guys,
In the Maine Lighthouse Rental app for my book, there are a total of 48 Rental records. To start
with, all rentals are available. Mary reserves one rental. Subsequently a search for all of Mary's
reservations and all available records, returns 95 rental references in the result collection
instead of 48. The problem arises from bad sql generated by Kodo 2.3.2 and 2.3.4.
This particular query can be fixed in two ways, but I'm not sure about the general mapping issues.
One, SELECT DISTINCT will fix it. Two, dropping the CUSTOMERX table from the query and changing the
first AND clause from:
WHERE (((t1.JDOIDX = 1351 AND t0.CUSTOMERX = t1.JDOIDX)
OR (t0.CUSTOMERX IS NULL))
to
WHERE (t0.CUSTOMERX = 1351
OR t0.CUSTOMERX IS NULL)
Code and generated SQL are below.
Hope this helps.
David Ezzio
---- query setup -------------
// set up query for customer's rentals and available rentals
Extent extent = pm.getExtent(Rental.class, false);
queryCustomerAndAvailableRentals = pm.newQuery(extent, "customer == c || customer == null");
queryCustomerAndAvailableRentals.declareParameters("Customer c");
queryCustomerAndAvailableRentals.setOrdering("week.startDate ascending, lighthouse.name ascending");
----- generated SQL -------
[ C:1923370; S:1238221; T:700575; D:10/22/02 3:48 PM ]
SELECT
t0.JDOIDX,
t0.JDOCLASSX,
t0.JDOLOCKX,
t0.CUSTOMERX,
t0.LIGHTHOUSEX,
t0.PRICEX,
t0.WEEKX,
t2.STARTDATEX,
t3.NAMEX
FROM
CUSTOMERX t1,
LIGHTHOUSEX t3,
RENTALX t0,
WEEKX t2
WHERE (((t1.JDOIDX = 1351 AND t0.CUSTOMERX = t1.JDOIDX)
OR (t0.CUSTOMERX IS NULL))
AND t0.LIGHTHOUSEX = t3.JDOIDX
AND t0.WEEKX = t2.JDOIDX)
ORDER BY
t2.STARTDATEX ASC,
t3.NAMEX ASC

SQL*Net 2.3.4 was shipped along 8.0 products:
* SQL*Plus
* ORACLE NET8 PRODUCTS
* ORACLE NETWORKING PRODUCTS (SQL*NET 2.3.4)
* ORACLE 8 JDBC DRIVERS
This is not supported to connect against a 10g database. The last valid combination was 8.0.6 vs 9.2.0
~ Madrid.

JDOQL Correlated Subquery - Bad SQL

Hi,
When I execute a JDOQL correlated subquery, the generated SQL is either
invalid or incorrect. Exactly what happens depends on the exact query, and
on the target database type, but I believe it all stems from the same
problem, which has to do with table aliasing.
If you need further details to reproduce this, please let me know. I'll be
glad to help in any way I can to get this situation remedied quickly, as I
am depending on this functionality. I have a test application to
demonstrate the problem.
I'm using Kodo 3.3.3 and application identity.
Paul Mogren
CommerceHub

For the record, this is in part due to a bug in Kodo's SQL92 joining.
See http://bugzilla.solarmetric.com/show_bug.cgi?id=1156
-Patrick
Paul Mogren wrote:
Certainly... Here's a simple example using Microsoft's JDBC Driver for SQL
Server 2000, and kodo.jdbc.sql.SQLServerDictionary, which produces invalid
SQL.
The query:
pm.newQuery(Container.class,
"(select from Entry entry where entries.contains(entry) &&
entry.containedId != 1).isEmpty()");
The classes:
class Contained {
private int id; //pk
class Container {
private int id; //pk
private Set entries = new HashSet(); //<Entry>
class Entry {
private int containerId; //pk
private int containedId; //pk
private Container container; //persistent-redundant
private Contained contained; //persistent-redundant
The result:
Incorrect syntax near the keyword 'WHERE'. {prepstmnt 31598780 SELECT
t0.container_id, t0.lock FROM WHERE (NOT EXISTS (SELECT DISTINCT
t2.contained_id, t2.container_id FROM dbo.entry t2 WHERE (t1.contained_id
= t2.contained_id AND t1.container_id = t2.container_id AND
t2.contained_id <> ?) AND t0.container_id = t1.container_id))
[params=(int) 1]} [code=156, state=HY000]
Patrick Linskey wrote:
Hi Paul,
Kodo's correlated subquery support does have some known limitations. Can
you post a sample JDOQL statement + corresponding SQL statement?
-Patrick
Paul Mogren wrote:
Hi,
When I execute a JDOQL correlated subquery, the generated SQL is either
invalid or incorrect. Exactly what happens depends on the exact query, and
on the target database type, but I believe it all stems from the same
problem, which has to do with table aliasing.
If you need further details to reproduce this, please let me know. I'll be
glad to help in any way I can to get this situation remedied quickly, as I
am depending on this functionality. I have a test application to
demonstrate the problem.
I'm using Kodo 3.3.3 and application identity.
Paul Mogren
CommerceHub

HashMap err --- Sql Exception - bad sql (pls see code)

Hi
//Query A
ResultSet resultSet = statement.executeQuery("select sno,rank from school");
BufferedWriter writeout = new BufferedWriter(new FileWriter(EDU, false));
while(resultSet.next()){
                    sno = resultSet.getString(1);
                    rank= resultSet.getString(2);
                    if("25".equals(rank)) {
// When the rank value is 25 , i want the hashA to have a key value pair in it , with value as 25 .
                        hashA.put(resultSet.getString(1),resultSet.getString(2));          /// ?? Sometimes the hashA contains key but for that key the value it contains is null
//Query B
resultSet = statement.executeQuery("select busno , driverno from License");
               BufferedWriter writeFlat = new BufferedWriter(new FileWriter(OUT, false));
               while(resultSet.next()){
                   busno = resultSet.getString(1);
               driverno = resultSet.getString(2);
               String rankOfB;
               rankOfB = hashA.get(resultSet.getString(1));                         // SO when i want to get the value it is giving an error SQL Exception - bad Sql . How to make this code work ,
               System.out.println("The value of Rank is : "+rankOfB);             // and when i get a value which is null from hashA , it is giving an error ... PLS HELP
               writeFlat.close();
               resultSet.close();
          }catch (ClassNotFoundException classNotFound) {
               System.out.println("Driver not Found"+classNotFound.getMessage());
          } catch (SQLException sqlException) {
               System.out.println("SQL Exception - bad sql");
               System.out.println(sqlException.getMessage());
          } catch (IOException e) {
               e.printStackTrace();
                    Thank U in advance ...

you cannot read a column twice within the same row
this is the part form javadoc
The ResultSet interface provides getter methods (getBoolean, getLong, and so on) for retrieving column values from the current row. Values can be retrieved using either the index number of the column or the name of the column. In general, using the column index will be more efficient. Columns are numbered from 1. For maximum portability, result set columns within each row should be read in left-to-right order, and each column should be read only once.
rankOfB = hashA.get(resultSet.getString(1));
use busno instead of resultSet.getString(1)
Edited by: whitenight541 on Dec 29, 2008 8:13 AM

EA2 - BUG: Export produces invalid SQL for BINARY_DOUBLE columns

Description:
When a table contains a BINARY_DOUBLE column, INSERTs for that column in SQL exported with Export Wizard are invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table containing a BINARY_DOUBLE column, e.g.:
CREATE TABLE "TESTTABLE" ("BINDBLCOL" BINARY_DOUBLE) ;
- add some data (floating-point numbers) to the table
- choose Tools -> Export Wizard (or Export DDL and Data in SQL Developer v1.2)
- check exporting of tables and data, on "Specify Objects/Data" choose your table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: floating-point numbers are enclosed in apostrophes (see below, relevant part is underlined).
-- DDL for Table TESTTABLE
CREATE TABLE "TESTTABLE"
( "BINDBLCOL" BINARY_DOUBLE
-- DATA FOR TABLE TESTTABLE
-- FILTER = none used
-- INSERTING into TESTTABLE
Insert into TESTTABLE (BINDBLCOL) values ('1.2345');
-- END DATA FOR TABLE TESTTABLE
The script, when run, produces following error on INSERT line:
SQL Error: ORA-01722: invalid number
When apostrophes are removed manually, script runs without problems.
Remarks:
SQL Developer: 1.5.0.52 MAIN-52.03; the same bug also on 1.2.1, build MAIN-32.13
Oracle DB: 10 Express
OS: Windows 2000 Professional
Java: 1.5.0.52: 1.5.0_15; 1.2.1: 1.6.0_03

Description:
When a table contains a BINARY_DOUBLE column, INSERTs for that column in SQL exported with Export Wizard are invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table containing a BINARY_DOUBLE column, e.g.:
CREATE TABLE "TESTTABLE" ("BINDBLCOL" BINARY_DOUBLE) ;
- add some data (floating-point numbers) to the table
- choose Tools -> Export Wizard (or Export DDL and Data in SQL Developer v1.2)
- check exporting of tables and data, on "Specify Objects/Data" choose your table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: floating-point numbers are enclosed in apostrophes (see below, relevant part is underlined).
-- DDL for Table TESTTABLE
CREATE TABLE "TESTTABLE"
( "BINDBLCOL" BINARY_DOUBLE
-- DATA FOR TABLE TESTTABLE
-- FILTER = none used
-- INSERTING into TESTTABLE
Insert into TESTTABLE (BINDBLCOL) values ('1.2345');
-- END DATA FOR TABLE TESTTABLE
The script, when run, produces following error on INSERT line:
SQL Error: ORA-01722: invalid number
When apostrophes are removed manually, script runs without problems.
Remarks:
SQL Developer: 1.5.0.52 MAIN-52.03; the same bug also on 1.2.1, build MAIN-32.13
Oracle DB: 10 Express
OS: Windows 2000 Professional
Java: 1.5.0.52: 1.5.0_15; 1.2.1: 1.6.0_03

ADDM Report is not produced by SQL DEV 4.0 if logged in user does not have SYSDBA privilege

Hello -
In SQLDEV 4.0 (Early Adapter), I logged in as user with no SYSDBA privilege granted. But ADVISOR granted and execute on DBMS_ADDM granted and "select any dictionary" granted, etc.
Then i go to the menu View --> DBA --> Performance --> Automatic Database Diagnostic Monitor
Select ADDM report from the available choices.
Out of 3 menu options: Summary, Findings and ADDM Report, I can see the first two, but I am getting a grey screen for ADDM Report.
^^^^^^^^^^^^^^^^^^^^^
If i do exactly the same but login as SYSDBA, then ADDM Report can be produced and can be seen. So the issue is in the missing grants and privileges.
^^^^^^^^^^^^^^^^^^^^^^
The goal that we are pursuing in our shop is to empower developers to work with ADDM reports by having them login as non-SYSDBA user.
^^^^^^^^^^^^^^^^^^^^^^^^
Please advise what privilege should be granted to get this working for non-SYSDBA login
The same user can successfully execute $ORACLE_HOME/rdbms/admin/addmrpt.sql and produce file with complete ADDM report. But not able to get the ADDM from SQL DEV 4.0
Thank you,
vr

Thank you, Phil.
This worked for me in my quick test case.
Great help, as DBA group wants to allow NON-privileged users (like Developers and QA) to execute ADDM on demand.
Here is my observation for RAC database with two instances.
I have followed your instructions:
"Performance / Automatic Database Diagnostic Monitor -> Run ADDM"
Then
- Uncheck box "By Creating New Snapshot" (this box was checked by default)
- Provide new "Task Name" (let's say "vr1")
- Select "Start Snapshot" (this is where my first confusion is: each screen shot # is shown twice, may be because i have two instances of RAC)
- Select "End Snapshot" (the same way: each SNAP_ID is shown twice)
- and finally APPLY button is pressed
This creates 3 reports:
vr1
vr1$1 (for instance_id=1)
vr1$2 (for instance_id=2_
So, my question is: this expected and normal behavior of the tool?
What if my RAC database has 8 instances? Then I would generate 9 separate ADDM reports?
Is this correct observation?
Thank you,
vr

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

CR produces modern SQL joining on one machine and old style on another

Hi.
I have a configuration related question that I hope someone here could help me with. The background is that we are two project members that have very similar setup, but where one crusial outcome differs between the environments and this difference is a real obstacle to the project. I assume that there is a way to fix it but I cannot find out how.
So, what actually differs is that when I use the Crystal Designer to build up a report query (using the Database expert, Data and Links), the SQL that is produced by the CR Designer uses the modern approach to table joining with the join conditions in the FROM clause (i.e. by jusing "INNER JOIN" and "OUTER JOIN" statements) wheras my collegue's CR Designer produces old style table joining with the join conditions in the where clause and using the join operator to achieve outer joins. Now, the problem arises when we both make changes in the same rpt file and when there is a need to use outer joins in a way that is not allowed with the old style joining.
So, my question is where (in what component) this behaviour is configured. We are both using CR2008 (different builds but I did not find this issue looking at the changelog) and Oracle db connection using the JDBC provider.
I am grateful for any help.
Kind regards,
Mikael

Thanks for your anwer Don.
I had hoped that there was a more "user friendly" approach to getting the configurations correct. Neither of us have experience in the tools you mentioned and the same goes for making registry changes etc in general. For now, it seems that we can live with the problem. Maybe we will dig into it again at a later stage.
Kind regards.
/Mikael

Mappingtool generates bad DDL for sybase (J2ee tutorial)

Running the mappingtool on the J2EE tutorial app (3.0.0RC1) generates bad
DDL for sybase. It's trying to create a table with a column of type
"IndexName":
C:\devtools\kodo\samples\j2ee>mappingtool -a refresh package.jdo
0 INFO [main] kodo.Tool - Mapping tool running on type "class
samples.j2ee.Car" with action "refresh".
0 INFO [main] kodo.Tool - The tool is now reading existing schema
information; this process may take some time. En
able the kodo.jdbc.Schema logging category to see messages about schema
data. Also see the -readSchema tool flag.
3716 INFO [main] kodo.Tool - Recording mapping and schema changes.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length
or scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
NestedThrowablesStackTrace:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnectionDecorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConne
ctionDecorator.java:506)
at
com.solarmetric.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:125)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Anyone else seen this? It works ok with Hypersonic (though i can't get the
tutorial app to run with hypersonic - see my earlier post).
Alex.

Some bugs in RCs sometimes don't make it into Bugzilla as it is a
release candidate and not production quality.
I would reocmmend upgrading as it fixes a number of major bug fixes and
you should be able to use the same eval key.
Alex Robbins wrote:
Abe White wrote:
I should also have asked: what JDBC driver are you using?Hi Abe,
I haven't tried with RC2 - has this been fixed in RC2? I didn't find this
bug on bugzilla.
I'm using Sybase JConnect JDBC driver (com.sybase.jdbc2.jdbc.SybDriver in
jconn2.jar) - looks like this is the version:
jConnect (TM) for JDBC(TM)/5.5(Build 25008)/P/JDK12/Tue May 29 14:37:46
2001
Should I upgrade from RC1 to RC2, and if so, can I continue to use the
same eval license key or can i download a new one?
thanks,
alex
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com

Bad SQL in 2.3.1 with n*m collection

Hi guys,
This bug comes from an example in my book. The Library example is one of the JDO Learning Tools
that I am providing that allows the user to enter queries interactively. The bug arises in an
example of its use presented in the book. Abe will receive the code with Chapter 8, coming soon.
Basically, Volunteer has a 1 to 1 relation with Borrower. A Borrower has a 1 to M relation with
Book. Book has a N to M relation with Category. Or in object terms, a Volunteer is always a
Borrower, but a Borrower is not always a Volunteer. A Book can be borrowed by one Borrower. A
Borrower can borrow from 0 to M books. A Book can be in the books collection of any number of
Category objects, and a Category can be in the categories collection of any number of Book objects.
Here is the JDO metadata:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jdo SYSTEM "jdo.dtd">
<jdo>
<package name="com.ysoft.jdo.book.library">
<class name="Borrower" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="books" >
<collection element-type="com.ysoft.jdo.book.library.Book" />
<extension vendor-name="kodo" key="inverse" value="borrower"/>
</field>
</class>
<class name="Book" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="borrower" />
<field name="categories" >
<collection element-type="com.ysoft.jdo.book.library.Category" />
<extension vendor-name="kodo" key="inverse" value="books"/>
</field>
</class>
<class name="Category" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="books" >
<collection element-type="com.ysoft.jdo.book.library.Book" />
<extension vendor-name="kodo" key="inverse" value="categories"/>
</field>
</class>
<class name="Volunteer" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
</class>
</package>
</jdo>
Here is the example as presented in the book, this is quoting output from the JDORI.
-- begin quote --
To find all the books that are in categories that interest Harry, use the Book extent, and define
the query variables:
Book b; Category c;
Then use the query string:
categories.contains(c) && (c.books.contains(b) && b.borrower.name == "Harry")
Your answer for the default object population should be:
Found 1 objects in the results
book [OID: 102-16] "Gone to Work" checked out: Mon Aug 26 08:23:10 EDT 2002
-- end quote --
Here is the SQL that KODO produces. It finds many (or all?) books instead of 1.
SELECT DISTINCT
t0.JDOIDX,
t0.JDOCLASSX,
t0.JDOLOCKX,
t0.BORROWERX,
t0.CHECKOUTX,
t0.TITLEX
FROM BOOKX t0, BOOKX t5, BOOKX t6,
BOOK_CATEGORIESX t1, BOOK_CATEGORIESX t4,
BORROWERX t7, CATEGORYX t2, CATEGORYX t3
WHERE (t7.NAMEX = 'Harry'
AND t0.JDOIDX = t1.JDOIDX
AND t1.CATEGORIESX = t2.JDOIDX
AND t3.JDOIDX = t4.CATEGORIESX
AND t4.JDOIDX = t5.JDOIDX
AND t6.BORROWERX = t7.JDOIDX)
Here is the modified version that gets the job done:
SELECT
t0.JDOIDX,
t0.JDOCLASSX,
t0.JDOLOCKX,
t0.BORROWERX,
t0.CHECKOUTX,
t0.TITLEX
FROM BOOKX t0,
BOOK_CATEGORIESX t1,
CATEGORYX t2,
BORROWERX t3
WHERE (t3.NAMEX = 'Harry'
AND t0.JDOIDX = t1.JDOIDX
AND t1.CATEGORIESX = t2.JDOIDX
AND t0.BORROWERX = t3.JDOIDX)
David Ezzio

David,
This has been fixed internally, and will be available in 2.3.3 (hopefully
along with a fix to your other issue).
-Patrick
In article <[email protected]>, David Ezzio wrote:
Hi guys,
This bug continues to exist in 2.3.2
David Ezzio
David Ezzio wrote:
Hi guys,
This bug comes from an example in my book. The Library example is one of the JDO Learning Tools
that I am providing that allows the user to enter queries interactively. The bug arises in an
example of its use presented in the book. Abe will receive the code with Chapter 8, coming soon.
Basically, Volunteer has a 1 to 1 relation with Borrower. A Borrower has a 1 to M relation with
Book. Book has a N to M relation with Category. Or in object terms, a Volunteer is always a
Borrower, but a Borrower is not always a Volunteer. A Book can be borrowed by one Borrower. A
Borrower can borrow from 0 to M books. A Book can be in the books collection of any number of
Category objects, and a Category can be in the categories collection of any number of Book objects.
Here is the JDO metadata:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jdo SYSTEM "jdo.dtd">
<jdo>
<package name="com.ysoft.jdo.book.library">
<class name="Borrower" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="books" >
<collection element-type="com.ysoft.jdo.book.library.Book" />
<extension vendor-name="kodo" key="inverse" value="borrower"/>
</field>
</class>
<class name="Book" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="borrower" />
<field name="categories" >
<collection element-type="com.ysoft.jdo.book.library.Category" />
<extension vendor-name="kodo" key="inverse" value="books"/>
</field>
</class>
<class name="Category" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
<field name="books" >
<collection element-type="com.ysoft.jdo.book.library.Book" />
<extension vendor-name="kodo" key="inverse" value="categories"/>
</field>
</class>
<class name="Volunteer" identity-type="datastore" >
<field name="oidString" persistence-modifier="none" />
</class>
</package>
</jdo>
Here is the example as presented in the book, this is quoting output from the JDORI.
-- begin quote --
To find all the books that are in categories that interest Harry, use the Book extent, and define
the query variables:
Book b; Category c;
Then use the query string:
categories.contains(c) && (c.books.contains(b) && b.borrower.name == "Harry")
Your answer for the default object population should be:
Found 1 objects in the results
book [OID: 102-16] "Gone to Work" checked out: Mon Aug 26 08:23:10 EDT 2002
-- end quote --
Here is the SQL that KODO produces. It finds many (or all?) books instead of 1.
SELECT DISTINCT
t0.JDOIDX,
t0.JDOCLASSX,
t0.JDOLOCKX,
t0.BORROWERX,
t0.CHECKOUTX,
t0.TITLEX
FROM BOOKX t0, BOOKX t5, BOOKX t6,
BOOK_CATEGORIESX t1, BOOK_CATEGORIESX t4,
BORROWERX t7, CATEGORYX t2, CATEGORYX t3
WHERE (t7.NAMEX = 'Harry'
AND t0.JDOIDX = t1.JDOIDX
AND t1.CATEGORIESX = t2.JDOIDX
AND t3.JDOIDX = t4.CATEGORIESX
AND t4.JDOIDX = t5.JDOIDX
AND t6.BORROWERX = t7.JDOIDX)
Here is the modified version that gets the job done:
SELECT
t0.JDOIDX,
t0.JDOCLASSX,
t0.JDOLOCKX,
t0.BORROWERX,
t0.CHECKOUTX,
t0.TITLEX
FROM BOOKX t0,
BOOK_CATEGORIESX t1,
CATEGORYX t2,
BORROWERX t3
WHERE (t3.NAMEX = 'Harry'
AND t0.JDOIDX = t1.JDOIDX
AND t1.CATEGORIESX = t2.JDOIDX
AND t0.BORROWERX = t3.JDOIDX)
David Ezzio
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

Refine edge tool (CS5) producing bad quality selections?

I am having troubles where whenever I use the refine edge tool, the selection it produces is horrible quality. What's weird is on my old computer, running the same software and using the same images, I could get much better results. I was runnign Vista on a laptop and now I'm running Windows 7 on a desktop, so It's confusing that I am getting bad quality selections with a much better computer adn the saem images in the same program Suite.
anyone know what's up?

Looking at the screenshot I assume you mean the artifiacts/blockiness? Have you checked disabling OpenGL to see if that's the culprit? From the help file:
1. Turn off OpenGL.
Choose Edit > Preferences (Windows) or Photoshop > Preferences (Mac OS).
In the Performance panel, deselect Enable OpenGL Drawing. Click OK.
Restart Photoshop, and perform the same function.

V2.1 - Exporting DATE columns produces invalid SQL

If you export a table with a column of type DATE, the SQL produced is invalid:
Left-click on table in tree view -> Click on "Data" tab -> Right click on data -> Export Data -> Insert -> Clipboard:
to_timestamp('01-SEP-09 17:49:21','DD-MON-RR HH.MI.SSXFF AM')
I have seen this work correctly, but I can't find the right combination now... but in this case the date format should be:
to_timestamp('01-SEP-09 17:49:21','DD-MON-RR HH24.MI.SSXFF')
Edited by: gclough on Jan 4, 2010 3:54 PM

Hi,
I encountered this problem since the EA and Vasan (one of the SQL Dev's team) gave the solution for this.
>
You can add the following in the sqldeveloper.conf to ensure that the driver doesn't report the column type of a DATE column as TIMESTAMP.
AddVMOption -Doracle.jdbc.mapDateToTimestamp=false
>
As you can see on
Re: 2.1 EA1: Problems on Date type columns
I wonder, why this isn't included on the default installation of the product, since it is absolutely wrong to use Timestamp for Date type column on the first place.
Regards,
Buntoro

V2.1 - Exporting CLOBS produces invalid SQL

When you export a table that has a CLOB via either of these methods, the SQL it produces is invalid (Quotes, Blank Lines, etc.) :
1. "Tools -> Database Export"
2. Right-click on the results page, then export as "Insert" to the clipboard
Insert into JAVASCRIPT (ID,FUNCTION_NAME,NAME,DESCRIPTION,VALID,FUNCTION,NUMBER_OF_ARGUMENTS,JAVASCRIPT,LAST_MODIFIED_DATE) values (26,'buildParameterizedUrl','Build Parameterized URL','Build Parameterized URL',1,1,3,'function buildParameterizedUrl(url, paramArray, valueArray)
url += '?';
var first = true;
for(var i in paramArray)
if(first)
first = false;
else
url += '&';
*url += paramArray[i] + '=' + valueArray;*
return url;
*',to_timestamp('16-JUL-09 09.52.30.000000000 AM','DD-MON-RR HH.MI.SS.FF AM'));*

Hi,
I encountered this problem since the EA and Vasan (one of the SQL Dev's team) gave the solution for this.
>
You can add the following in the sqldeveloper.conf to ensure that the driver doesn't report the column type of a DATE column as TIMESTAMP.
AddVMOption -Doracle.jdbc.mapDateToTimestamp=false
>
As you can see on
Re: 2.1 EA1: Problems on Date type columns
I wonder, why this isn't included on the default installation of the product, since it is absolutely wrong to use Timestamp for Date type column on the first place.
Regards,
Buntoro

3.0.0RC2 MappingTool producing bad SQL

Similar Messages

Maybe you are looking for