Expected Date of Next Release of Sql Developer

Hi Dev Team,
Not sure whether this has been asked before; but wanted to check to see if you have decided on the next Release data of SQL Developer if so is there a sitefor beta checking a nightly build or so ?
-Thanks
A

Well, sometimes I resist coming to the forum in the morning, it's not always a good way to start a day with grumbles, but this morning this thread made me laugh. K is correct, Oracle does not provide dates of releases+. Typically we provide a 6 month window for a next release, but sometimes we are required, legally only to provide a year span. This protects you as the customer and us, as a development organization. Case in point last were our releases last year, when we effectively rolled our SQL Developer 2.0 and 2.1 release together and only released SQL Developer 2.1 at the end of the year.
What made me laugh today was the specific date provided. Nowhere in our internal plans for the year are there any specific dates noted. There are ranges and targets and these may change.
The date provided is neither accurate nor useful. Please disregard.
What is true is that we typically follow a major release with a full patch and we plan to do the same this time. You can expect a patch to SQL Developer 2.1 within the next few months. We are gathering and fixing bugs that we have found since production, bugs that were identified and did not make production and bugs noted on the forum. Not all will make the patch, but it's worth putting in as many fixes as we can before releasing the patch. So no date for SQL Developer 2.1.1 (the patch release) and definitely no known dates for SQL Developer 2.2, regardless of what you hear on the forum, from an "internal source" or on the wires.
Regards
Sue Harper
Product Manager

Similar Messages

Re: GeoRaptor 3.2.1 Released for SQL Developer 3.x

Hey,
Referencing this that was posted in early September 2012:
GeoRaptor 3.2.1 Released for SQL Developer 3.x
I am supporting GRE's and the like at UC Berkeley and I really want to hook them up with this plug because it will make their life MUCH easier. But I have some pretty basic problems:
1. A VERY simply table that has an 8307 linestring. The query that GR defaults when the table is added :
SELECT rowid,"ID","NETWORK_ID","BEG_NODE_ID","END_NODE_ID","LENGTH","SPEED_LIMIT","DETAIL_LEVEL",
"IN_SYNCH","CREATED","MODIFIED","CREATED_BY","MODIFIED_BY","MODSTAMP","NET_GEN_ID",t.GEOM as GEOM
FROM VIA.LINKS_HOLD t
WHERE SDO_FILTER(t.GEOM,?,?) = 'TRUE'This seems to do something but nothing is ever displayed. The table definition is as follows:
CREATE TABLE LINKS_HOLD (
ID NUMBER,
NETWORK_ID NUMBER,
BEG_NODE_ID NUMBER,
END_NODE_ID NUMBER,
GEOM MDSYS.SDO_GEOMETRY ,
LENGTH NUMBER(9,3),
SPEED_LIMIT NUMBER(3,0),
DETAIL_LEVEL NUMBER(3,0),
IN_SYNCH NUMBER(1,0),
CREATED DATE,
MODIFIED DATE,
CREATED_BY VARCHAR2(30 BYTE),
MODIFIED_BY VARCHAR2(30 BYTE),
MODSTAMP TIMESTAMP (6),
NET_GEN_ID NUMBER
)And some sample data. I am only including the geometry
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18477, 34.02929, -118.18156, 34.02932))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18268, 34.02393, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18268, 34.02393))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18387, 34.0273))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18387, 34.0273, -118.18257, 34.02731))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18131, 34.02632, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18131, 34.02632))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18256, 34.02631))Since the query I tried to substitute for the system generated one was:
select geom from links_hold ;When I tried to run that the system responded with and error and pasted the following into the clipboard:
SELECT rowid, GEOM as GEOM FROM (
select
rowid,geom
from
via.links_hold
? MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(-180.0,-165.78279266572636, 180.0,165.78279266572636))
? Please keep in mind that very same query will display all the links where I run in the generic map view (GMV) of SQLD and
since GMV has little in the way of additional features it is rather frustrating to see your tool not really working, or what
is more likely is that I have a lack of understanding because I cannot find documentation that will allow me to
move forward w/o bugging you.
So Any light you can throw on this would be of great assistance. Thanks much!

Flying Guy,
The non-display is a major bug that was discovered after GeoRaptor 3.2 was released. I knew it was there a few days after
the release - it got past our testers as well. I hoped to have a release out very soon after but a bunch of things conspired to
stop this from happening. Anyway, no one complained so I figured no one was using it enough to find the bug.
The bug is fixed which you can test if you download the Early Access release from our SourceForge website.
There are some other new functions in this EA that you might discover. The main one being the ability to have a feature count
(those drawn within the map window) displayed on the view / layer tree. See GeoRaptor preferences. Another is the restoration
of right mouse click menus on the sdo_geometry columns of table/mv/view connection nodes. Also, if a table has more than one
sdo_geometry column, the first is no longer selected if you right mouse click/map etc on table node. It will display a pick list
of sdo_geometry columns for you to chose from. (There has also been a major revamp of connection management as I noted
problems since SQL Developer 3.2.)
Please download and try it. Consider joining the GeoRaptor lists to help with testing and documenting. If you find bugs in
the EA please email the right georaptor list, or use the GeoRaptor SourceForge site to register the bug. Or email me
directly simon at spatialdbadvisor dot come.
I hope to have a release ready by the end of the week but I have not heard back from the small group of testers
that we have something that is ready to go.
Wrt documentation we have added some where users have created some for me with my input. Please volunteer to
create documentation.
The simple fact of life is that:
1. GeoRaptor is downloaded by lots and lots of people (a good thing).
But:
<complain>
2. Very few responses ever occur to postings made about GeoRaptor on this forum or on our sourceforge forum: disheartening;
3. Very few bug reports or enhancement requests ever get created at sourceforge: disheartening;
4. I have become the only developer which is a bad thing. I known of some Java developers who have used GeoRaptor but
most/all expect someone else to fix bugs or develop the tool. I have spend thousands of hours on a tool that I find useful because SQL Developer
is my main Oracle access tool. But I have never, ever heard from more than 10 people over the past 3 years that they too find it useful: disheartening;
5. Attempts to contact downloaders routinely fall on deaf ears or fail: disheartening;
6. Requests for documenters, developers, testers are ignored or fail because we can't contact anyone who downloads GeoRaptor: disheartening.
</complain>
Like a lot of open source projects I do not get paid for anything I do. But what annoys me is that no one - other than a tiny brace of people - will help with anything
even when we ask.
I have also decided that major new functionality added to GeoRaptor eg GeoRasters; WMS; WFS; etc will only be done when sufficient funding, via a fundraising website
makes a set amount. This is something that the PostGIS have started doing and I think it only fair considering how many months each year I spend on development "in
the dark" for no income.
regards
Simon

GeoRaptor 3.2.1 Released for SQL Developer 3.x

Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
     Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
     If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
     Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
     If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
   This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
     1. Metadata entries which have no underlying oracle object (orphan)
     2. Metadata entries for existing underlying objects (existing case)
     3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
     Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
     as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PM

Simon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan

How export datas with special characters from SQL Developer?

Hi.
I'm doing an import of datas of a table, but this table have special characteres in specific accents (á,é,í,ó,ú), my source table have for example "QRCN Querétaro, Candiles" but when I done an export from opcion Tool --> Export DLL (and Datas) from SQL Developer generate the next script
Insert into tablexxx(CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20280','QRCN Quer?ro, Candiles');
How can I do for export my datas and generate the script correct?
Insert into tablexxx(CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20280','QRCN Querétaro, Candiles');
thanks.

Hi sybrand_b,
1. In my SQL Developer I select Tool-->Export DDL (and Data).
2. I Select name file, connection (this is a remote DB), objects to export in this case I select 'Tables and data' and table name to export
3. Run the procedure and generate the script following:
-- File created - jueves-julio-01-2010
-- DDL for Table TABLEXXX
CREATE TABLE "BOLINF"."TABLEXXX"
(     "CADENA" VARCHAR2(50 BYTE),
     "NUMERO_FARMACIA" VARCHAR2(50 BYTE),
     "SUCURSAL_REFERENCIA" VARCHAR2(200 BYTE)
-- DATA FOR TABLE TABLEXXX
-- FILTER = none used
REM INSERTING into TABLEXXX
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20280','QRCN Quer?ro, Candiles');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20281','QRCG Quer?ro, Corregidora');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20282','QRFU');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20283','QRFU');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20284','SAUN San Lu?P, Universidad');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20285','SAEV San Lu?P, Eje Vial');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20286','SALB San Lu?P, Los Bravo');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20287','SAAL San Lu?P, Alvaro Obreg?');
Insert into TABLEXXX (CADENA,NUMERO_FARMACIA,SUCURSAL_REFERENCIA) values ('C002','20288','SACA San Lu? Callej?n de Cod');
4. But my source table have the next datas.
Select * from TABLEXXX.
CADENA     NUMERO_FARMACIA     SUCURSAL_REFERENCIA
C002     20280     QRCN Querétaro, Candiles
C002     20281     QRCG Querétaro, Corregidora
C002     20282     QRFU
C002     20283     QRFU
C002     20284     SAUN San Luís P, Universidad
C002     20285     SAEV San Luís P, Eje Vial
C002     20286     SALB San Luís P, Los Bravo
C002     20287     SAAL San Luís P, Alvaro Obregó
C002     20288     SACA San Luís, Callejón de Cod
5. I have done a query to table nls_database_parameters.
NLS_LANGUAGE     AMERICAN
NLS_TERRITORY     AMERICA
NLS_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_NUMERIC_CHARACTERS     .,
NLS_CHARACTERSET     UTF8
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD-MON-RR
NLS_DATE_LANGUAGE     AMERICAN
NLS_SORT     BINARY
NLS_TIME_FORMAT     HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZH:TZM
NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZH:TZM
NLS_DUAL_CURRENCY     $
NLS_COMP     BINARY
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CONV_EXCP     FALSE
NLS_RDBMS_VERSION     10.2.0.4.0
6. I have revised in Regedit-->HKEY_LOCAL_MACHINE-->SOFTWARE-->ORACLE-->ORACLE HOME and value for NLS_LANG=AMERICAN_AMERICA.UTF8
where should I change for export my datas correct?
or exist any form for export my datas?
thanks a lot.
regards

Import data using Excel and Oracle SQL Developer - I need some help

Dear friends,
I'm using Oracle SQL Developer 1.5.1 and I need to import an Excel file into a database table. If I try to import this file in XLS format, fields and headers are correctly being shown and separated, but if I press "Next" button, it simply doesn't do anything - it stays stopped.
I did some search here in this forum and it seems to me that, when you try to import a file via XLS format, SQL Developer has bugs. Is this correct?
If I save the same file in CSV format and try to import the same file, it goes ahead, but SQL Developer is not separating fields and headers correctly. It combines all CSV fields into one - let's say Column0 and fields 1;TEST;01/01/2000 below the same Column0.
Saving the file in CSV format is not a problem, taking a very little time. But I don't know how to make SQL Developer import it correctly. Could somebody please help me? Thanks in advance.
Best regards,
Franklin

Hello K,
yes, you're right. I found the following topic after posting this question here.
Re: After update to 1.5.1, import from Excel fails
I downloaded version 1.5.0 and I'll use it whenever I import data from Excel.
Thanks,
Franklin

Urgent Help !!! Export data into insert format (Oracle Sql developer)

Hi all,
Please help , when i try to export ms access table which have 400,000 over rows to insert format using oracle sql developer 1.5.5. After the export have done the exported file xxx.sql is empty.
Is it because of too many rows? or what tool or function should i use for exporting table with many rows.
It used to have exported successfully with
Insert into table( ) values ();
Insert into table( ) values ();
Insert into table( ) values ();
Insert into table( ) values ();
----- when i try to export table with over 10,000 row.
Regard,
Tun

Another option is to export your file as Formatted text (space delimited). This will create a fixed format file. You can either create an external table to access the file or use sqlloader to load it. In your control file or access parameters you will specify the positions of the fields you are interested in. Your control file will look something like this:
OPTIONS (BINDSIZE=50000,ERRORS=50,ROWS=200,READSIZE=65536)
LOAD DATA
CHARACTERSET US7ASCII
INFILE '/home/FIXED_FORMAT.dat' "FIX 58"
CONCATENATE 1
INTO TABLE "EMP2"
APPEND
REENABLE DISABLED_CONSTRAINTS
"ID" POSITION(1:2) INTEGER(2) ,
"REGION" POSITION(3:3) INTEGER EXTERNAL(1) ,
"DEPT" POSITION(4:6) INTEGER EXTERNAL(3) ,
"HIRE_DATE" POSITION(7:14) DATE(8) "mmddyyyy" ,
"SALARY" POSITION(15:19) DECIMAL(9,2) ,
"NAME" POSITION(20:34) CHAR(15)
SQLDeveloper does not currently provide an option to import fixed format files.

SQL Developer Data Modeler, Repository or file based?

As announced, in a next release of SQL Developer Data Modeler it wil be repository based. Ok that is nice. But what does it mean for the current possibility to store your work in files. Will the possibility to store in files be supported in new releases when also a Repository is available?

Will the possibility to store in files be supported in new releases we are not going to remove that run and use aspect of the tool.
Philip

Customization of Connection Drop Down/View in SQL Developer

I know this may not be that import feature that i think SQL Developer should have but will be very helpful.
In my scenario there are many databases and schemas exists in Development/Staging/Production environments, there is a possibility when selecting a connection from drop down some other connection is selected, its human error. What if there is Group by option in the drop down so that we can customize or group lower environment connections in one place and others in different group, even color coding of critical connections settings could be much helpful.
So in short i think it would be great if the following feature is included in next release of SQL Developer
- Connections to display as in groups
- Each group and connection of that group can be color coded(say production connections are displayed in Red color, Testing/Staging are displayed in Yellow, Development in Blue etc)

JeffSmithSQLDevPM wrote:
I think the poster means this actually
You'll need to be more specific. The developer comment for the feature request you linked says this:
Folders in the navigator are currently not persisted. Implementing this is not trivial.
I have created 'prod' and 'test' folders and put connections in each of them in 3.0.02 Build MAIN-02.37 and the folders and connections persist just fine.
So the connections themselves can certainly be 'grouped' which is what OP specifically asked about.
What if there is Group by option in the drop down so that we can customize or group lower environment connections in one place and others in different group, even color coding of critical connections settings could be much helpful.
Everything else in the tree (e.g. schemas) is specific to a connection which can be specific to a user created folder such as 'prod' or 'test'.
So if OP means something else they will need to clarify what they really mean and provide an example.

Data Miner Extension in SQL Developer 4.0 EA3 Release: EA3 Repository Migration Failure

The Data Miner extension in the SQL Developer 4.0 EA3 release fails when attempting to migrate the repository to EA3. This posting contains instructions on how to recover from this failure as well as to successful migrate the repository from EA2 to EA3. There are no problems when just installing a fresh Data Miner repository.
Sorry about the difficulty if this has caused you any problems.
Mark
Failure message displayed in log when migrating to EA3:
Error report -
ORA-06550: line 96, column 40:
PLS-00382: expression is of wrong type
ORA-06550: line 96, column 7:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:
Instructions on how to recover from failure and continue using original version of SQL Developer:
1) Execute the following sql as SYS in order to allow the Data Miner repository to be open for use again:
UPDATE ODMRSYS.ODMR$REPOSITORY_PROPERTIES
SET PROPERTY_STR_VALUE = 'LOADED'
WHERE PROPERTY_NAME = 'REPOSITORY_STATUS';
COMMIT;
2) During attempted migrationto EA3 failed, access priviliges to the Data Miner repository are revoked from users. In order to use Data Miner again, these grants must be reapplied. You can either use the UI guided process to accomplish this, which requires the SYS password, or you can run the usergrants.sql script, again as the SYS user. For instructions on how to run the usergrants.sql script, or any adminstrative script, review the instructions contained in the install_scripts_readme.html file. You can find this file in the SQL Developer directories created when you unzipped SQL Developer. It is located in the following relative directory: \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts.
Instructions on how to successfully migrate to EA3.
If you have already attempted to migrate to EA3 and failed, then you need to perform the recovery instructions noted above, after which you can continue with the instructions below.
If you have not yet attempted to migrate to EA3, then just following the instructions below.
1) Replace all contents the script file createxmlworkflowsbackup.sql with specification contained at the end of this posting. The file to edit can be found in the \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts directory.
2) After completing the edit to createxmlworkflowsbackup.sql, you can proceed with the UI guided migration or perform the migration using the appropriate migration script. Review the install_scripts_readme.html file in the /dataminer/scripts directory for instructions on how to perform the migration using the script. For the UI migration, simply open any user connection in your Data Miner navigator, and you will be prompted to perform the migration.
WHENEVER SQLERROR EXIT SQL.SQLCODE;
DEFINE MAX_VERSIONS = 30
EXECUTE dbms_output.put_line('Start Backup Data Miner Workflows ' || systimestamp);
DECLARE
table_cnt NUMBER;
BEGIN
SELECT count(*) INTO table_cnt FROM all_tables WHERE owner='ODMRSYS' AND table_name='ODMR$WORKFLOWS_BACKUP';
IF (table_cnt = 0) THEN
    EXECUTE IMMEDIATE '
      CREATE TABLE ODMRSYS.ODMR$WORKFLOWS_BACKUP
        USER_NAME VARCHAR2(30 CHAR) NOT NULL
      , PROJECT_ID NUMBER NOT NULL
      , PROJECT_NAME VARCHAR2(30 CHAR) NOT NULL
      , PJ_CREATION_TIME TIMESTAMP(6) NOT NULL
      , PJ_LAST_UPDATED_TIME TIMESTAMP(6)
      , PJ_COMMENTS VARCHAR2(4000 CHAR)
      , WORKFLOW_ID NUMBER NOT NULL
      , WORKFLOW_NAME VARCHAR2(30 CHAR) NOT NULL
      , WORKFLOW_DATA SYS.XMLTYPE
      , CHAIN_NAME VARCHAR2(30 CHAR)
      , RUN_MODE VARCHAR2(30 CHAR)
      , STATUS VARCHAR2(30 CHAR) NOT NULL
      , WF_CREATION_TIME TIMESTAMP(6) NOT NULL
      , WF_LAST_UPDATED_TIME TIMESTAMP(6)
      , BACKUP_TIME TIMESTAMP(6) NOT NULL
      , VERSION NUMBER NOT NULL
      , WF_COMMENTS VARCHAR2(4000 CHAR)
      , CONSTRAINT ODMR$WORKFLOWS_BACKUP_PK PRIMARY KEY
          PROJECT_ID
        , WORKFLOW_ID
        , VERSION
        ENABLE
      LOGGING
      PCTFREE 10
      INITRANS 1
      XMLTYPE COLUMN "WORKFLOW_DATA" STORE AS BASICFILE CLOB';
END IF;
END;
DECLARE
schema_old_ver VARCHAR2(30);
schema_ver   VARCHAR2(30);
patch        VARCHAR2(30);
db_ver       VARCHAR2(30);
v_storage    VARCHAR2(30);
schema_data CLOB;
v_db_11_2_0_2 NUMBER; -- db is <= 11.2.0.2?
row_cnt      NUMBER;
ver_num      NUMBER := 1;
maintaindom NUMBER;
workflow_rec ODMRSYS.ODMR$WORKFLOWS_BACKUP%ROWTYPE;
BEGIN
SELECT STORAGE_TYPE INTO v_storage FROM ALL_XML_TAB_COLS WHERE OWNER='ODMRSYS' AND TABLE_NAME='ODMR$WORKFLOWS' AND COLUMN_NAME='WORKFLOW_DATA';
if (db is >= 11.2.0.3 AND SQL Dev > 3.0) OR (db is <= 11.2.0.2 AND MAINTAIN_DOM_PATCH_INSTALLED)
    back up all workflows
end if
IF (v_storage != 'BINARY') THEN
    -- determine xml schema version
    SELECT XMLSerialize(CONTENT SCHEMA AS CLOB) INTO schema_data
    FROM DBA_XML_SCHEMAS WHERE schema_url = 'http://xmlns.oracle.com/odmr11/odmr.xsd' AND owner = 'ODMRSYS';
    maintaindom := INSTR(schema_data, 'xdb:maintainDOM="false"', 1, 1);
    -- determine database version
    SELECT version INTO db_ver FROM product_component_version WHERE product LIKE 'Oracle Database%';
    --- Check schema compatibility
    schema_old_ver := '11.2.0.1.9'; -- default value
    BEGIN
      SELECT property_str_value INTO schema_ver
      FROM "ODMRSYS"."ODMR$REPOSITORY_PROPERTIES" WHERE property_name = 'WF_VERSION';
      IF schema_old_ver = schema_ver THEN
        IF NOT (db_ver = '11.2.0.1' OR db_ver = '11.2.0.2') THEN
          dbms_output.put_line('WARNING: The backup process can not be done, The workflows need to be migrated first');
        RETURN;
        END IF;
      END IF;
    EXCEPTION WHEN NO_DATA_FOUND THEN
      schema_ver := schema_old_ver;
      dbms_output.put_line('No WF_VERSION found. Defaults to: ' || schema_old_ver);
    END;
    -- determine if MAINTAIN_DOM_PATCH_INSTALLED
    IF (INSTR(db_ver, '11.2.0.2') > 0 OR INSTR(db_ver, '11.2.0.1') > 0 OR INSTR(db_ver, '11.2.0.0') > 0) THEN
      v_db_11_2_0_2 := 1;
      BEGIN
        SELECT PROPERTY_STR_VALUE INTO patch FROM ODMRSYS.ODMR$REPOSITORY_PROPERTIES WHERE PROPERTY_NAME = 'MAINTAIN_DOM_PATCH_INSTALLED';
        patch := UPPER(patch);
      EXCEPTION WHEN NO_DATA_FOUND THEN
        patch := 'FALSE';
      END;
    ELSE
      v_db_11_2_0_2 := 0;
    END IF;
END IF;
IF (   v_storage = 'BINARY'
      OR (v_db_11_2_0_2 = 0) -- db is >= 11.2.0.3
      OR ((v_db_11_2_0_2 > 0) AND ((patch = 'TRUE') OR (maintaindom = 0))) ) THEN -- db is <= 11.2.0.2 AND (MAINTAIN_DOM_PATCH_INSTALLED OR maintaindom="true")
    SELECT count(*) INTO row_cnt FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    IF (row_cnt > 0) THEN
      SELECT NVL(MAX(VERSION)+1,1) INTO ver_num FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    END IF;
    FOR wf IN (
      SELECT
        p.USER_NAME "USER_NAME",
        p.PROJECT_ID "PROJECT_ID",
        p.PROJECT_NAME "PROJECT_NAME",
        p.CREATION_TIME "PJ_CREATION_TIME",
        p.LAST_UPDATED_TIME "PJ_LAST_UPDATED_TIME",
        p.COMMENTS "PJ_COMMENTS",
        x.WORKFLOW_ID "WORKFLOW_ID",
        x.WORKFLOW_NAME "WORKFLOW_NAME",
        xmlserialize(DOCUMENT x.WORKFLOW_DATA as CLOB indent size = 2) "WORKFLOW_DATA",
        x.CHAIN_NAME "CHAIN_NAME",
        x.RUN_MODE "RUN_MODE",
        x.STATUS "STATUS",
        x.CREATION_TIME "WF_CREATION_TIME",
        x.LAST_UPDATED_TIME "WF_LAST_UPDATED_TIME",
        x.COMMENTS "WF_COMMENTS"
      FROM ODMRSYS.ODMR$PROJECTS p, ODMRSYS.ODMR$WORKFLOWS x
      WHERE p.PROJECT_ID = x.PROJECT_ID
    LOOP
      workflow_rec.USER_NAME := wf.USER_NAME;
      workflow_rec.PROJECT_ID := wf.PROJECT_ID;
      workflow_rec.PROJECT_NAME := wf.PROJECT_NAME;
      workflow_rec.PJ_CREATION_TIME := wf.PJ_CREATION_TIME;
      workflow_rec.PJ_LAST_UPDATED_TIME := wf.PJ_LAST_UPDATED_TIME;
      workflow_rec.PJ_COMMENTS := wf.PJ_COMMENTS;
      workflow_rec.WORKFLOW_ID := wf.WORKFLOW_ID;
      workflow_rec.WORKFLOW_NAME := wf.WORKFLOW_NAME;
      workflow_rec.WORKFLOW_DATA := SYS.XMLTYPE(wf.WORKFLOW_DATA);
      workflow_rec.CHAIN_NAME := wf.CHAIN_NAME;
      workflow_rec.RUN_MODE := wf.RUN_MODE;
      workflow_rec.STATUS := wf.STATUS;
      workflow_rec.WF_CREATION_TIME := wf.WF_CREATION_TIME;
      workflow_rec.WF_LAST_UPDATED_TIME := wf.WF_LAST_UPDATED_TIME;
      workflow_rec.BACKUP_TIME := SYSTIMESTAMP;
      workflow_rec.VERSION := ver_num;
      workflow_rec.WF_COMMENTS := wf.WF_COMMENTS;
      BEGIN
        -- Output the ids (proj name, workflow name, proj id, workflow id)
        dbms_output.put_line('Backup workflow: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
        INSERT INTO ODMRSYS.ODMR$WORKFLOWS_BACKUP VALUES workflow_rec;
        COMMIT;
      EXCEPTION WHEN OTHERS THEN
        dbms_output.put_line('Backup workflow failed: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
      END;
    END LOOP;
END IF;
-- keep the latest 30 versions
EXECUTE IMMEDIATE 'DELETE FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP WHERE VERSION <= :1' USING (ver_num - &MAX_VERSIONS);
COMMIT;
EXCEPTION WHEN OTHERS THEN
ROLLBACK;
RAISE_APPLICATION_ERROR(-20000, 'Workflow backup failed. Review install log.');
END;
EXECUTE dbms_output.put_line('End Backup Data Miner Workflows. ' || systimestamp);

823006 wrote:
5.a. XLS export of big number columns looses precision, for example a number(38) column with all digits used.
I believe excel only holds 15 digits of precision.
Edited by: 823006 on Jan 18, 2011 8:14 AMThen it would be nice if you can define the "excel type" of each column. So you can make this number a "string" in the XLS.
Edited by: user9361780 on Jan 18, 2011 9:12 AM

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
   NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
   to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
   a. Sorting (click on column header) and
   b. Filtering.
   c. Copying to Clipboard via right mouse click sub menu of:
      - Geometry's SDO_ELEM_INFO array constructor.
      - SDO_GEOMETRY constructor
      - Error + validation string.
   d. Access to Draw/Zoom functions which were previously buttons.
   e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
      it can process - along with the ring / element that is host to the error (if it can) - and displays
      them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
      The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
   f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
   g. Table now has only one primary key column, and has a separate error column holding the actual error code.
   h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
   i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
   Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
   - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
     option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
     could be shown as: <25> or {x,y} or <25> {x,y}
   - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
   - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
     edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
   - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
   rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
   * NONE
   * START    - All segments of a line have the arrow positioned at the start
   * MIDDLE   - All segments of a line have the arrow positioning in the middle.
   * END      - All segments of a line have the arrow positioning in the END.
   * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
   For geographic/geodetic SRIDs distances are currently shown in meters;
   For all SRIDs an attempt is made to "adapt" the scaleBar units depending
   on the zoom level. So, if you zoom right in you might get the distance shown
   as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
   to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
   click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
   executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
   adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
   added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
   automatically adds a field that holds a unique row number.
3. When exporting to KML:
   * one can optionally export attributes.
   * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
   * If a column in the SELECTION or table/view/Mview equals "name" then its value is
     written to the KML tag <name> and not to the list of associated attributes.
     - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
   in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
   Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
   Example:
   SELECT a.geom.sdo_point as point
     FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
             FROM DUAL) a;
   SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
     FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
   than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
   the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
    However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
    Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
    to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
    Please read the Oracle documentation on how to project your data is this is necessary. An example is:
    SELECT OBJECTID,
           CODIGO as name,
           NOME as description,
           MI_STYLE,
           SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
      FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
    circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
    to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
   types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
   Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
   and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
   in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
   a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
   has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
   what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
   and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
   In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
   right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
    has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
    index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
    which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

Oracle SQL Developer Data Modeler start up error

Hi All,
I just downloaded Oracle SQL Developer Data Modeler (2.0.0.57.0) [Released 1 July 2009] by selecting the option "Oracle SQL Developer Data Modeler for Windows (This zip file includes the JRE)"
After I installed the same and tried to run it by clicking datamodeler.exe, I get the following error message
"unable to create an instance of the Java virtual machine located at path:..\jdk\jre\bin\client\jvm.dll"
On the same machine I can successfuly run the Oracle SQL Develper with no errors. My machine is having Windows XP Professional SP3.
Any ideas? If there was a problem with Java, than the Oracle SQL Developer should also not run. But as stated it runs with out any error but the Oracle SQL Developer Data Modeler gives the above error.
Regards,
JAA149

1 - The above problem has nothing to do with the memmory. I tried on a 400 MB RAM, 900 MB RAM, 1.5 MB RAM & 2 MB RAM with the same arror.
"unable to create an instance of the Java virtual machine located at path:..\jdk\jre\bin\client\jvm.dll"
http://i30.tinypic.com/9vkwf6.jpg
2 - There are two "datamodeler.exe: files
One is at D:\datamodeler\datamodeler.exe
2nd is at D:\datamodeler\bin\datamodeler.exe
The same error occurs with both the files.
3 - The Oracle SQL Developer Data Modeler version is "Oracle SQL Developer Data Modeler (2.0.0.57.0) [Released 1 July 2009]" and the file I downloaded is "Oracle SQL Developer Data Modeler for Windows (This zip file includes the JRE) - (57M)"
If I look in "D:\datamodeler\jdk\jre\README.txt" I find
"Java(TM) Platform, Standard Edition Runtime Environment Version 6"
If I run "D:\datamodeler\jdk\jre\bin\javacpl.exe" I get
http://i30.tinypic.com/mt8ocn.jpg
If I run "D:\datamodeler\jdk\jre\bin\jureg.exe" I get
http://i28.tinypic.com/30boiyo.jpg
If i check at the control panle add/remove program
http://i30.tinypic.com/1428tba.jpg
If I go to "http://www.java.com/en/download/manual.jsp" and download "jre-6u16-windows-i586-s.exe" and run it.
If I go to "C:\Program Files\Java\jre6" I find the same files as in "D:\datamodeler\jdk\jre"
I am able to run Oracle SQL Developer with out any kind of error let alone the above one. But with Oracle SQL Developer Data Modeler I get the above mentioned error no matter what I try.
As the error states "unable to create an instance of the Java virtual machine located at path:..\jdk\jre\bin\client\jvm.dll". The file "jvm.dll" is located at two places. One at "D:\datamodeler\jdk\jre\bin\client\jvm.dll" and the second at "D:\datamodeler\jdk\jre\bin\server\jvm.dll"
A similiar problem occurs with JDeveloper with the fllowing solution
http://forums.oracle.com/forums/thread.jspa?threadID=506339&start=0&tstart=0
Which states the following
"hello!
in the problem with JDeveloper i have a solution. The jdk have a file jvm.dll in the path: jdk/jre/bin/client/jvm.dll this is the problem ... now in the path:jdk/jre/bin/client/ojvm has a file with the same name if you copy and paste this file to the another path, now its works fine your Jdeveloper.
Jdeveloper use two files to jvm.dll to work one in the folder /client and other in /server copy the same file to the two locations for precaution
for me work fine thanks..."
I tried to do the same (Copy from client folder to server folder)
D:\datamodeler\jdk\jre\bin\client\jvm.dll
COPIED THIS FILE TO
D:\datamodeler\jdk\jre\bin\server\jvm.dll
Nada. So I reversed it (copied from server folder to client folder)
D:\datamodeler\jdk\jre\bin\server\jvm.dll
COPIED THIS FILE TO
D:\datamodeler\jdk\jre\bin\client\jvm.dll
Does not work. So I tried another solution stated at the same forum entry
"Well,
i solved the problem by this way :
<SQLDEVELOPER>/jdev/bin/ide.conf
In this file, change this line :
AddVMOption -Xmx512M
by
AddVMOption -Xmx256M
Now, the executable is lauching correctly. No more errors with Java Virtual Machine.
But is it a good thing to solve it like that ?"
But the ide.conf file is only at "D:\sqldeveloper\ide\bin\ide.conf" which is for the SQL Developer and not the SQl Developer Data Modeler
Correct me if I am wrong but
JRE = Java Run Time Envoirment
JDK = Java Development Kit
And Oracle SQL Developer Data Modeler needs JRE and not JDK. In any case I download JDK
jdk-6u14-javafx-1_2-windows-i586.exe (121,306 KB) and installed it but no succcess.
I tried every thing except completely re-install my whole PC.
Any help will be much appreciated.
Cordially,
Jawad

SQL Developer - Data Modeler - Trigger for FK arc constraints

In the preferences there is an option "Data Modeler > DDL > Create Triggers for FK arc constraints". I think Oracle recomments to use constraints instead of triggers where it is possible. Can anyone from the Development team tell me why here is just the option to create triggers and not also the option to create table level constraints for FK arc constraints? If it is possible I'd like to have this option. My suggetion is to use the following check constraint construction for creation: nvl2(FK_IDx,1,0)+nvl2(FK_IDy,1,0)+...+nvl2(FK_IDz,1,0)=1 or with not only single FK columns: nvl2(FK_IDx1,1,0)+nvl2(FK_IDx2,1,0)+nvl2(FK_IDy,2,0)+...+nvl2(FK_IDz,2,0)=2. Please tell me if that would be possible (and maybe available in next Version) or why it is better to user triggers instead.
Thanks
/c

The Data Modeler forum is at:
SQL Developer Data Modeler

SQL Developer - Data Modeler

The Data Modeler is a great Tool within SQL Developer. Will there be a possibility to work with it, without installing Subversion extension in the next Version of SQL Developer?

In our company we have one SVN Repository for all Projects and also one Version of a SVN Client (TortoiseSVN),
which fits to the companys SVN-Repository Version.
There is no guarantee, that the SVN-Version of the SQLDEV-Extension and our companys SVN-Repository-Version always fits together.
This is a disadvantage in our strategy to use SQLDEV Data Modeler as a tool for our projects.

SQL Developer Data Modeler - integration with subversion

I just discovered the release of SQL Developer Data modeler, and found this to be very interesting.
We are still using Oracle Designer for database design, but we are looking for a replacement (for several reasons).
My question is quite simple:
Given that the modeler uses a filebased repository, and also given that we have several developers potentially working on a data-model at the same time, how does Data Modeler integrate with subversion for source control etc.?
Can the repository itself be under source control, and checked in/out directly from Data Modeler?
Or will only the output files be candidates for version/source control?
Let me admit right away that I have not read much of the data modeler docs, and I have also not downloaded/installed it (yet), but does anyone have pointers to docs on this , or general input/knowledge around it.
On a side note, I must say that it puzzles me that a company like Oracle, that delivers one of the best databases doesn't use its database engine to host the repository, but instead chooses to go for files (I assume xml) "scattered all over the place"....
Well, I guess they a have a reason for it..
Anyway:
Sql Developer Data Modeler and Subversion anyone?
Jens

Hi Jens,
It's early days and the initial implementation is indeed file based. Though I'd say not xml files "all over the place", but in ordered folders. Yes, as a database company it does make sense that we'd have a repository for managing and versioning metadata. However the tool supports Oracle and other databases and many companies use open source version control tools, such as Subversion and so anyone using the Data Modeler today can use it with Subversion regardless of the database they are designing for.
We do plan to have a repository, but in the 6+ months of the early adopter program found that many of the early adopters were happy to place the files under source code control using Subversion and in so doing also managed the multi-user development.
Integrated Subversion support is planned for a future release.
Sue

SQL Developer Data Modeling pricing

I just downloaded the EA version of SQL Developer Data Modeling. I read in the release notes that the production release won't be free - any idea about the pricing ?
Matthias

Once the pricing for SQL Developer Data Modeling has been confirmed, we will release the full licensing detail. This will not affect the SQL Developer licensing that exists today. We plan to release SQL Developer Data Modeling as a stand alone product and then as an extension to SQL Developer, for those who want to work in an integrated environment. You can download the second early adopter release of SQL Developer Data Modeling and test and use the product. Once we have a production release, we will not answer queries on the early adopter releases and the feedback application we are currently offering for this will be shut down. As such you can continue to work with the early adopter release, but it is incomplete and would be unsupported.
Sue

Expected Date of Next Release of Sql Developer

Similar Messages

Maybe you are looking for