SQL Developer v4 is now production :)

Because the announcements are easy to overlook, just a quick note - version 4.0 is no longer available as an Early Adopter. It's officially released as of this morning.
Thanks everyone - tens of thousands of downloads, hundreds of bug reports and enhancement requests - you truly did help make version 4.0 a much stronger release.
We'll be monitoring the forums, support, etc. for issues per usual.

Hi Rich,
I got the same problem after trying to install SQLDev 4.0.0.13 under OL 5.10 64-bit via the RPM.
As a workaound I used the sqldevloper-4.0.0.13-no-jre.zip which is downloadable here http://download.oracle.com/otn/java/sqldeveloper/sqldeveloper-4.0.0.13.80-no-jre.zip
It's actually the "other platform" package but works for me in most cases.
First, make sure you have the newest Oracle Java JDK 7 installed. The RPM http://download.oracle.com/otn-pub/java/jdk/7u45-b18/jdk-7u45-linux-x64.rpm works pretty fine.
1. rpm -ihv jdk-7u45-linux-x86.rpm
2. alternatives --install /usr/bin/java java /usr/java/latest/bin/java 10 --slave /usr/bin/keytool keytool /usr/java/latest/bin/keytool --slave /usr/bin/rmiregistry rmiregistry /usr/java/latest/bin/rmiregistry
3. alternatives --set java /usr/java/latest/bin/java
4. alternatives --config java -> Choose the 2nd selection which points to /usr/java/latest/bin/java
5. Check if Java 7 is working with java -version
Secondly unpack the SQLDev-Zip-File in the $HOME directory of a choosen user (e.g oracle) and give executable rights to the sqldeveloper.sh
1. unzip sqldeveloper-4.0.0.13.80-no-jre.zip
2. chmod +x ~/sqldeveloper/sqldeveloper.sh
Now, start SQLDEV
3. ~/sqldeveloper/sqldeveloper.sh

Similar Messages

Error opening Oracle SQL Developer 1.2.1

In my IDE, I saw extensions pane with title "Entensions - Log" which has
the following contents:
oracle.ide.db
Warning: Classpath entry \DISTAPPS$\ORACLE\v10\Oracle10g\jdbc\lib\ojdbc14.jar not found
Warning: Classpath entry \DISTAPPS$\ORACLE\v10\Oracle10g\jlib\orai18n.jar not found
oracle.jdeveloper.db.connection
Warning: Classpath entry \DISTAPPS$\ORACLE\v10\Oracle10g\jdbc\lib\ojdbc14.jar not found
Warning: Classpath entry \DISTAPPS$\ORACLE\v10\Oracle10g\jlib\orai18n.jar not found
(I am runing it on windows XP, the problem happened after I killed a running Oracle SQL Developer session. Now I cannot connect to anything even I tried to reinstall Oracle SQL Developer again) Anybody had the same issue, is there any way to fix it.
Thanks,
-caoy

Oracle SQL Developer 1.2.0 is working correctly at Argonne National Lab with Oracle 10g Client Version 10.2.1 and Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - 64bit. The correct UNC and java class path is:
\\Canary\DISTAPPS$\ORACLE\V10\Ora10g\jdbc\lib.
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Nov 17 16:23:58 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> exit
Successfully tested Oracle SQL Developer to this same database and retrieved data correctly.
Please see me in my office.
H. Johnstad
CIS 2-5069
[email protected]

SQL Developer 3.0 error message on Data mining feature

Hello,
I have installed the 3.0 Oracle SQL Developer and am now getting the following error when I attempt to connect to an existing database connection:
Connection Error - Oracle XMLDB and Text Features are not installed.
Please install the Oracle XMLDB adn Text features, or see your database administrator for assistance.
We are on Oracle 11.2.0.1 with windows env.
I have installed this new released SQL dev 3.0 for data mining purpose, but I am not sure whether we need a licence for this or it is free.
Does anyone have any idea please share with me.
Thanks for your assistance.
Regards.

This post can help you:
Connection Error - Oracle XMLDB and Text Features are not installed.
sql developer is free, not licence needed.

View a function in PL/SQL developer

I'm a sql developer, quite new to oracle.
I'm using PL/SQL developer tool. Now I would like to view how a function is defined.
But don't know how to open it.
I can see the function, when right click it I have the option of the following: Refresh, copy comma separated, Test, and describe.
How can I view the function contents?
Thanks

Hi,
You can double click on that function name, you can watch one window in left side.
If you want the bebug the fuction(first you should have the debug rights) just click on test and select ok for debug result, you watch the result step by step.
Regards
Sree

Oracle SQL Developer 3.1 Migration Third Party Databases Issues

Hi,
i had following issues with migrating from db2 v8 to oracle 11.2.
Online:
Due to missing privileges and roles for user db user migrations some steps have failed (CREATE USER -> ORA-01031 ...).
After correcting this like described in "Creating a Database User for the Migration Repository" in sqldev online help this has worked.
The problems are:
a) on the overview page at the end of the migration assistent all steps (CAPTURE, CONVERT, GENERATE, DATAMOVE) are shown as complete, even if nothing has done
b) on page 6/9 into migration assistant all changes for datatype convertion are ignored, for example CHAR to VARCHAR2
c) generated files are not visible, even if you mark refresh on file view
d) after restarting sqldev, generarted files are visible in file view, but when you add generated files to svn error message "svn: File: xxx has inconsitent newlines" is shown
e) after sucessful migration on opened migration project pane "data quality" sourcenumrows are NULL, even if they always NOT NULL and count(*) on any table on both sites are equal
Offline:
Generated skripts contains errors:
./startDump.sh: line 157: syntax error near unexpected token `done'
'/startDump.sh: line 157: `done < "schemas.dat"
Can anybody help?
Thanks in advance
André

Hi kgronau,
thanks for your fast answer.
Today i have found 2 new issue.
When you have opened a migration project from repository, on pane "data quality" sourcenumrows are always null
and
sourcename and targetname shows always databse object names from the database on the first migration project in repository independently of extra section in drop down box model and source.
kgronau wrote:
André,
I used SQL Dev 3.1 and I captured a DB2 database. Then I've changed the rule to map char to varchar2 and started the migration.
When I now check out my custom tables all all of them that had in the source model a char column are now using varchar2.I have tried to changed dataype for target database in place over the drop down box, not the edit rule button. It's a little bit confusing to have this option, when it doesn't works.
After using the edit rule button, all works fine. Just the summary page 9/9 doesn't report changed datatype assignment.
>
Could you please explain what you mean with your option c and d?c)
Yes i'm meaning View -> Files. Sorry but on german windows i have just german menu items. That is sometimes tricky to retranslate for support questions and also not helpful when using the online help where all menu items referenced in english :-(
(Do you have an ideo how can i configure sqldev with english menu aon german windows?)
I think, this problemn is special for output folders under subversion control.
d)
Generated Files after the end of the migration are just visible in output folders under subversion control after restarting sqldev
>
Edited by: kgronau on Mar 7, 2012 12:30 PM
Are you talking about Opening a File viewer window (View -> Files)? In my case I have chosen d:\temp\DB2 as output and monitored it during the migration. It isn't refreshed until I manually click on the refresh button - but once the migration has finished and written the output and when I then click on the refresh button I'll see all the directories and the files included.
Edited by: kgronau on Mar 7, 2012 12:39 PM
When a migration has finished then SQL Developer 3.1 now creates in the top directory an unload_script.sh file which calls the other unload scripts.That's right, all scripts are generated.
Also the data unload scripts were created - I need to find a DB2 on Unix to check the script - a quick check of the windows scripts worked correctly.
Edited by: kgronau on Mar 7, 2012 1:22 PM
These unload shell scripts to unload the data out of a DB2 database are also working.
Unfortunately I'm not able to test the shell script used for a source model unload as my UDB is running on Windows.
Didn't the online source model collection work? For me it looks like it did as you mentioned you changed the char data types to varchar2 and this requires already a connection to the source database - except you used the scripts that were generated using the startDump.sh which has failed. Yes, online source model collection did work. Just the unix shell script produces an error on the source unix system with db2. Please see below th generated script.
So please provide here some more details../startDump.sh was startet for testing purposes without any arguments
./startDump.sh: line 157: syntax error near unexpected token `done'
'/startDump.sh: line 157: `done < "
if [[ $# != 3 ]]; then
echo "Usage: startDump <database> <user> <password>";
exit 1;
fi
ROWTAG="'<row>'";
ENDROWTAG="'</row>'";
COLTAG="'<col><![CDATA['";
ENDCOLTAG="']]></col>'";
# Clear any other dat files
echo "Clearing older data files"
rm -f *.dat
echo "Connnecting to $1 as $2";
db2 -r connect.dat "connect to $1 user $2 using $3";
if [[ $? != 0 ]]; then
echo "Connection failed.";
exit 20;
fi
# GET SCHEMA QUERY.
echo "Get all schemas";
db2 +o -x -r schemas.dat "select SCHEMANAME SCHEMA_NAME from SYSCAT.SCHEMATA WHERE DEFINER <> 'SYSIBM' AND
SCHEMANAME <> 'NULLID' AND SCHEMANAME <> 'SQLJ'
AND SCHEMANAME <> 'SYSTOOLS'";
if [[ $? != 0 ]]; then
echo "Get schemas failed.";
exit 30;
fi
# Loop through file containing schema names and extract db objects for each of them
while read SCHEMA_NAME
do
# Create schema directory
rm -rf "${SCHEMA_NAME}";
mkdir "${SCHEMA_NAME}";
if [[ $? != 0 ]]; then
echo "Could not create schema directory ${SCHEMA_NAME}.";
exit 40;
fi
echo "Get all tables for schema $SCHEMA_NAME";
tablesFile="${SCHEMA_NAME}/""tables.dat";
# GET TABLES QUERY. */
db2 -x +o -r $tablesFile "select "$ROWTAG", "$COLTAG"||COLUMNS.TABSCHEMA||"$ENDCOLTAG", "$COLTAG"||COLUMNS.TABNAME||"$ENDCOLTAG",
"$COLTAG"||COLUMNS.COLNAME||"$ENDCOLTAG", "$COLTAG"||(CASE WHEN (COLUMNS.CODEPAGE = 0 and (COLUMNS.TYPENAME = 'VARCHAR' OR COLUMNS.TYPENAME = 'CHAR'
OR COLUMNS.TYPENAME = 'LONG VARCHAR' OR COLUMNS.TYPENAME = 'CHARACTER')) THEN COLUMNS.TYPENAME || ' FOR BIT DATA'
ELSE COLUMNS.TYPENAME END)||"$ENDCOLTAG", "$COLTAG"||CHAR(COLUMNS.LENGTH)||"$ENDCOLTAG",
"$COLTAG"||CHAR(COLUMNS.SCALE)||"$ENDCOLTAG", "$COLTAG"||COLUMNS.NULLS||"$ENDCOLTAG",
"$COLTAG"||COALESCE(COLUMNS.DEFAULT, '')||"$ENDCOLTAG", "$ENDROWTAG" from
SYSCAT.COLUMNS COLUMNS, SYSCAT.TABLES TABLES WHERE
COLUMNS.TABSCHEMA = '${SCHEMA_NAME}' AND
COLUMNS.TABNAME = TABLES.TABNAME AND
COLUMNS.TABSCHEMA = TABLES.TABSCHEMA AND
TABLES.TYPE = 'T'
ORDER BY COLUMNS.TABNAME, COLUMNS.COLNO";
if [[ $? != 0 ]]; then
echo "No tables found.";
fi
# GET SYNONYMS QUERY. */
echo "Get all synonyms for schema $SCHEMA_NAME";
synonymsFile="${SCHEMA_NAME}/""synonyms.dat";
db2 -x +o -r $synonymsFile "select "$ROWTAG", "$COLTAG"||TABNAME||"$ENDCOLTAG", "$COLTAG"||BASE_TABSCHEMA||"$ENDCOLTAG",
"$COLTAG"||BASE_TABNAME||"$ENDCOLTAG", "$ENDROWTAG" from syscat.tables
where tabschema = '${SCHEMA_NAME}' and type = 'A'";
if [[ $? != 0 ]]; then
echo "No synonyms found.";
fi
# GET VIEW QUERY. */
echo "Get all views for schema $SCHEMA_NAME";
viewsFile="${SCHEMA_NAME}/""views.dat";
db2 -x +o -r $viewsFile "select "$ROWTAG", "$COLTAG"||VIEWSCHEMA||"$ENDCOLTAG", "$COLTAG"||VIEWNAME||"$ENDCOLTAG",
"$COLTAG"||COALESCE(TEXT, '')||"$ENDCOLTAG",
"$COLTAG"||DEFINER||"$ENDCOLTAG", "$COLTAG"||READONLY||"$ENDCOLTAG", "$COLTAG"||VALID||"$ENDCOLTAG", "$ENDROWTAG"
from syscat.views
WHERE VIEWSCHEMA = '${SCHEMA_NAME}'
ORDER BY VIEWNAME";
if [[ $? != 0 ]]; then
echo "No views found.";
fi
# GET INDEXES QUERY. */
echo "Get all indexes for schema $SCHEMA_NAME";
indexesFile="${SCHEMA_NAME}/""indexes.dat";
db2 -x +o -r $indexesFile "select "$ROWTAG", "$COLTAG"||INDSCHEMA||"$ENDCOLTAG", "$COLTAG"||INDNAME||"$ENDCOLTAG",
"$COLTAG"||TABSCHEMA||"$ENDCOLTAG", "$COLTAG"||TABNAME||"$ENDCOLTAG", "$COLTAG"||INDEXTYPE||"$ENDCOLTAG",
"$COLTAG"||UNIQUERULE||"$ENDCOLTAG", "$ENDROWTAG" from SYSCAT.INDEXES
WHERE INDSCHEMA = '${SCHEMA_NAME}' AND UNIQUERULE <> 'P'
ORDER BY TABNAME, INDNAME";
if [[ $? != 0 ]]; then
echo "No indexes found.";
fi
# GET INDEX DETAILS QUERY. */
echo "Get all index details for schema $SCHEMA_NAME";
indexeDetailsFile="${SCHEMA_NAME}/""indexDetails.dat";
db2 -x +o -r $indexeDetailsFile "select "$ROWTAG", "$COLTAG"||INDSCHEMA||"$ENDCOLTAG", "$COLTAG"||INDNAME||"$ENDCOLTAG",
"$COLTAG"||COLNAME||"$ENDCOLTAG", "$COLTAG"||CHAR(COLSEQ)||"$ENDCOLTAG", "$ENDROWTAG" from SYSCAT.INDEXCOLUSE
WHERE INDSCHEMA = '${SCHEMA_NAME}'";
if [[ $? != 0 ]]; then
echo "No index details found.";
fi
# GET TRIGGERS QUERY. */
echo "Get all triggers for schema $SCHEMA_NAME";
triggersFile="${SCHEMA_NAME}/""triggers.dat";
db2 -x +o -r $triggersFile "select "$ROWTAG", "$COLTAG"||TRIGSCHEMA||"$ENDCOLTAG",
"$COLTAG"||TRIGNAME||"$ENDCOLTAG", "$COLTAG"||DEFINER||"$ENDCOLTAG", "$COLTAG"||TABSCHEMA||"$ENDCOLTAG",
"$COLTAG"||TABNAME||"$ENDCOLTAG", "$COLTAG"||TRIGEVENT||"$ENDCOLTAG", "$COLTAG"||VALID||"$ENDCOLTAG",
"$COLTAG"||COALESCE(TEXT, '')||"$ENDCOLTAG",
"$COLTAG"||COALESCE(REMARKS, '')||"$ENDCOLTAG", "$ENDROWTAG"
from SYSCAT.TRIGGERS
WHERE TRIGSCHEMA = '${SCHEMA_NAME}'";
if [[ $? != 0 ]]; then
echo "No triggers found.";
fi
# The for GET Promary Key CONSTRAINT QUERY. */
echo "Get all primary keys for schema $SCHEMA_NAME";
primarykeysFile="${SCHEMA_NAME}/""primarykeys.dat";
db2 -x +o -r $primarykeysFile "select "$ROWTAG", "$COLTAG"||X.CONSTNAME||"$ENDCOLTAG", "$COLTAG"||X.TYPE||"$ENDCOLTAG",
"$COLTAG"||X.TABSCHEMA||"$ENDCOLTAG", "$COLTAG"||X.TABNAME||"$ENDCOLTAG", "$COLTAG"||Z.COLNAME||"$ENDCOLTAG",
"$COLTAG"||CHAR(Z.COLSEQ)||"$ENDCOLTAG", "$COLTAG"||COALESCE(X.REMARKS, '')||"$ENDCOLTAG", "$ENDROWTAG" from
(select CONSTNAME, TYPE, TABSCHEMA, TABNAME, REMARKS from SYSCAT.TABCONST where (type = 'P' OR type = 'U')) X
FULL OUTER JOIN
(select COLNAME, COLSEQ, CONSTNAME, TABSCHEMA, TABNAME from SYSCAT.KEYCOLUSE) Z
on
(X.CONSTNAME = Z.CONSTNAME and X.TABSCHEMA = Z.TABSCHEMA and X.TABNAME = Z.TABNAME)
WHERE X.TABSCHEMA='${SCHEMA_NAME}'
ORDER BY X.CONSTNAME";
if [[ $? != 0 ]]; then
echo "No primary keys found.";
fi
# The for GET Check constraints QUERY. */
echo "Get all Check constraints for schema $SCHEMA_NAME";
constraintsFile="${SCHEMA_NAME}/""checkConstraints.dat";
db2 -x +o -r $constraintsFile "SELECT "$ROWTAG", "$COLTAG"||A.CONSTNAME||"$ENDCOLTAG", "$COLTAG"|| COALESCE(TEXT, '') ||"$ENDCOLTAG", "$COLTAG"|| A.TABSCHEMA||"$ENDCOLTAG", "$COLTAG"|| A.TABNAME ||"$ENDCOLTAG", "$COLTAG"|| COLNAME ||"$ENDCOLTAG", "$ENDROWTAG" FROM SYSCAT.CHECKS A , SYSCAT.COLCHECKS B
WHERE A.CONSTNAME = B.CONSTNAME AND A.TABSCHEMA = B.TABSCHEMA AND A.TABNAME=B.TABNAME AND A.TABSCHEMA = '${SCHEMA_NAME}'";
if [[ $? != 0 ]]; then
echo "No check constraints found.";
fi
done < "schemas.dat"
# GET PROCEDURES QUERY. */
. getProcedures.sh schemas.dat
# The for GET Foreign Key CONSTRAINT QUERY. */
. getForeignKeys.sh schemas.dat

Viewing table relations inside Oracle SQL Developer

Hi,
I'm a PL/SQL beginner and I need to control the table relations for an Oracle database. I'm using the Oracle SQL developer tool.
Now, how can I see the table relation inside Oracle SQL developer tool?
Thanks

itshak wrote:
When working with tables based on user defined types, the FK relations between the tables are not displayed at the data modeler (and also at the worksheet query builder)
I don't think that applies here 1041141 mentioned he is a beginner and did not mention any usage of object types.
If you want to report an issue or possible bug, then please open an extra thread for that. In such a case it helps tremendously if you provide a working test case as well.

SQL Developer Edition.

Hi,
I was wondering if anyone could tell me whether it's possible to install SAP onto Microsoft's SQL Developer Edition in Pre-Production platforms. Microsoft state publicly that Developer Edition has all the functionalilty of Enterprise and is essentially a rebadged Enterprise Edition with a development-centric Licensing model.
Furthermore, I understand that Microsoft's licensing documents cite a three tiered environment approach - Dev, Test and Prod - using Enterprise in production and Developer Edition in Dev and Test, as per pretty much any other SQL based environment.
I understand that the SAP system installation can be carried out manually (as opposed to the VBS scripted method), allowing the use of non-SAP provided media for the SQL installation but I'm unsure as to whether it will accept the Developer Edition installation at this point.
Thanks
W

Hi,
SQL Server 2000 and SQL Server 2005 are only tested in the Enterprise Edition by SAP. Therefore, only the Enterprise Edition is supported. The SAP support may not be able to solve problems that occur with other editions
if you want to try to use Developer Edition you need to install it manually check the installation document to install SQL server manually but do it as your own risk as SAP support is concern
regards,
kaushal

SQl Developer 3.1 / Data Miner Production Release is now available

Hi,
The SQL Developer 3.1/Data Miner Production Release is now available.
For more details see the OTN Forum announcement:
https://forums.oracle.com/forums/ann.jspa?annID=1747
Thanks, Mark

It will be there when the Oracle Cloud is released.
-kris

SQl Developer 3.2 Product Release Now Available

Hi,
See Data Miner forum announcement: https://forums.oracle.com/forums/ann.jspa?annID=1854
For more information about SQL Dev 3.2 in general: http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html
Thanks, Mark

You can use the 32 or the 64 bit versions.
But if you want to use the OCI/thick stuff, the bit level will have to match, 32 bit SQLDev with 32 bit Oracle Client with 32 bit JDK. Same goes with 64.
When you download the 64 bit dist of SQLDev for windows, you'll need to get a 64bit JDK, and make sure you have a 64 bit Oracle Client if you want to use that.
If you need more info, I wrote up more detailed instructions here
http://www.thatjeffsmith.com/archive/2012/05/getting-started-with-sql-developer-less-than-5-minutes/

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

SQL Developer 1.5.3 - Why is "Find and Replace" now a model dialog?

In SQL Developer 1.5.3 the find and replace dialog is now a modal dialog.
This prevent you from copying content from below it.
Basically only option is to type instead of copy and paste
Very frustrating!

This has been modal since 1.0. Do you mean the Edit -> Replace... ctrl R (Replace Text) dialog? As you have been able to copy and paste before, please direct me to the dialog you are referring to.
Sue

Oracle SQL Developer 1.2 Patch 1 (1.2.1.32.00) is Now available

Hi,
I have just posted the announcement that the latest patch release for SQL Developer is now available. The updated Check for Updates should be available from 1pm PST (16 Aug). So if you are ahead of the game, please give this another hour.
The Check for Updates does an automatic restart of SQL Developer, but you still need to do a second restart or you will not see the SQL Worksheet.
Finally we have updated the Statement of Direction with the main themes we plan to address in the next release.
For all document and download links, please see the main SQL Developer page on OTN.
Regards
Sue

Hi,
I have just posted the announcement that the latest patch release for SQL Developer is now available. The updated Check for Updates should be available from 1pm PST (16 Aug). So if you are ahead of the game, please give this another hour.
The Check for Updates does an automatic restart of SQL Developer, but you still need to do a second restart or you will not see the SQL Worksheet.
Finally we have updated the Statement of Direction with the main themes we plan to address in the next release.
For all document and download links, please see the main SQL Developer page on OTN.
Regards
Sue

Can SQL Developer 3.1 Early adopter be used on production ?

Can SQL Developer 3.1 Early adopter be used on production ?

Can , sure. Advisable , not officially.
Your call...
Regards,
K.

[4.0] Production SQL Developer hangs when attempting to expand Java in the Connection Navigator

Folks,
I'm running production SQL Developer on Oracle Linux 5.8 and whenever I click the Java link in the Connections Navigator with a SYS AS SYSDBA connection SQL Developer hangs.
Oracle Enterprise Edition 11.2.0.1.0
SQLDeveloper 4.0.0.13.80
Oracle Linux 6
JDK Version 1.7.0_45
Doing the same thing with user SCOTT (no SYSDBA) works fine (although there are not any Java objects).
Thanks,
Rich

This has been logged as a bug.
The bad plan/performance has been logged as a bug. SQL Developer didn't hang for me - I was able to cancel the query using the Task Progress panel.

SQL Developer 1.1 Patch 1 is Now Available for Download

You can now download
SQL Developer 1.1 Patch 1. This release is 1.1.1.25.14. Please
use the release number when posting queries on the forum. 
We have published a list of Bugs
Fixed since SQL Developer 1.1 (1.1.0.23.64). At this stage Check for Updates
is not yet available. It should be available by the end of the week. Until Check
for Updates is available, you should install the full release. You can migrate
your settings from release 1.1 (1.1.0.23.64)
Have Fun! 
SQL Developer Team 
Message was edited by:
Kris Rice
Fixed the download link

Sue,
I get the following error when unzipping the archive:
Extracting oracle.javacore.jar
bad CRC bb93c0d4 (should be 1f5b6bb6)
Warning: the size of the extracted file (7484702) does not match the uncompressed size (7484661) recorded in the zip file
It's the Windows version including the JRE.
Although probably my download went wrong I'd suggest to double check the ZIP-file on your server.
Best regards,
--==/ Uwe \==--

SQL Developer v4 is now production :)

Similar Messages

Maybe you are looking for