Meening of Geen Bug in SQL Developer 2.1.0.62

I know this should be obvious to me, but is not and 2 other people I asked did not know either. What is the meaning of the green bugs that sometimes appear when you expand nodes (for example expanding the packages node)?
I could not find the meaning in the documentation, but I have to say I did not know what to search for…
Thanks

Well, it's new and documentation isn't up to date yet, so don't worry if you don't know what it means.
It actually indicates "compiled with debug info". For a minute you thought your code was infected, didn't you ;)
Regards,
K.

Similar Messages

Bug report SQL DEVELOPER DATA MODELER

Hello,
I think i found a bug using Sql developer data modeler 2.0.0 build 584.
When importing a DDL file to create a relational model, foreign key constraints might not be created if foreign key uses multiple-field and the fields are not referenced in the same order as the primary key was.
ex:
Table FOO ..... PRIMARY KEY (id_1, id_2)
FOREIGN KEY (id_2, id_1) REFERENCES FOO (id_2, id_1)
Benjamin
P.S: Bellow is a portion of SQL code demonstrating the problem:
-- "_decompte"
CREATE TABLE "_decompte"(
numero_rang VARCHAR2(2),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
ALTER TABLE "_decompte"
add CONSTRAINT pk_decompte PRIMARY KEY (numero_rang, numero_contrat, id_decompte);
-- "_decompte_detail"
CREATE TABLE "_decompte_detail"(
numero_rang VARCHAR2(2),
id_ligne NUMBER(4),
numero_contrat VARCHAR2(13),
id_decompte VARCHAR2(19)
-- "_decompte_detail"
-- NOT Recognized by SQL DEVELOPER DATA MODELER (fields are not in the same order as primary key definition)
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_1 FOREIGN KEY (numero_contrat, numero_rang , id_decompte) REFERENCES "_decompte"(numero_contrat, numero_rang , id_decompte);
-- Recognized by SQL DEVELOPER DATA MODELER
ALTER TABLE "_decompte_detail"
add CONSTRAINT fk_decompte_detail_2 FOREIGN KEY (numero_rang, numero_contrat, id_decompte) REFERENCES "_decompte"(numero_rang, numero_contrat, id_decompte);

Hi,
Well, I was recently given some database scripts and asked to correct and improve them. These scripts were not generated but rather hand made. Having no access to a DBMS I was just curious about the result of this option in Data modeler and tried it for a better DB overview. I don't need it at all, but I was surprised to discover that the result was a failure. So I tried various scripts until I found the mistake.
regards.

Bug in SQL Developer relating to handling of XMLTYPE columns

Hi,
I have found a bug in SQL Developer relating to its handling of XMLTYPE columns.
Given a table with the following data:
ID, XML_DATA
1, <xml here>
2, <xml here>
3, <xml here>
And the following SQL to extract a value from the XML and also an XML fragment as an XMLTYPE:
SELECT
EXTRACTVALUE(t.column_value,'/*/USER_ID/text()')user_id
, t.column_value user_data
FROM dbuser.mytable m
, TABLE(XMLSEQUENCE(EXTRACT(m.xml_data, '/*/USER_LIST/USER'))) t
I get the following:
user_id, user_data
jsmith26, (XMLTYPE)
mjones45, (XMLTYPE)
sborga31, (XMLTYPE)
Note that the user_id is correctly extracted, however the XMLTYPE column (user_data) is empty in SQL Developer.
The same query returns the correct XML data in TOAD.
Edited by: 1008733 on May 29, 2013 5:07 PM

Steve,
So your example is slightly more complex than the one documented for a table in the standard OE schema here:
http://docs.oracle.com/cd/B19306_01/server.102/b14200/functions052.htm
That example works fine on an 11.2.0.1 database with SQL Developer 3.2.20.09.87. Please try the following with your case:
Tools -> Preferences -> Database -> Advanced -> Display Struct Value In Grid (check it off if not already)If that still does not work for Run Statement (query result displayed in the grid, not as script output using Run Script), then please provide a test case based on the Warehouse table in the OE schema (or your case with DDL and DML scripts including the xml data) and I will log a bug.
Thanks,
Gary
SQL Developer Team

PL/SQL Bug in SQL Developer?

SQL Developer v 1.1.1.25 running on Windows XP.
I have a PL/SQL procedure that does not compile with debug in SQL Developer. Compiling it with debug produces the following error:
an Error(1): PLS-00801: internal error [79110].The only way I was able to get the procedure to compile in SQL Developer was to add the 4th line. If I uncomment the 4th line it compiles with debug. Why??
Here is the procedure:
CREATE OR REPLACE
PROCEDURE BOGUS AS
CURSOR c1 IS
SELECT dummy FROM DUAL;
-- x c1%ROWTYPE;
PROCEDURE test ( rec IN OUT c1%ROWTYPE) IS
begin
null;
end;
BEGIN
NULL;
END BOGUS;Message was edited by:
marife
I played around some more with the procedure and discovered the problem. The key is the compiling with debug. I believe that compile with debug cannot build the debug information for a %ROWTYPE as a parameter. But if I define a local variable of that %ROWTYPE, then the compile with debug knows what debug information to track for the %ROWTYPE.
I discovered that in SQL*Plus it compiles, but when you issue the ALTER PROCEDURE bogus COMPILE DEBUG, it does not compile. This is a problem with the debug option for compiling and not a problem with SQL Developer.
Sorry for the posting. Hopefully this information will save other times and fustration.
Mike

Just for anyone else searching on this bug - I get the same error with certain procedures in TOAD when compiling with DEBUG.
Fortunately nobody here has the first clue how to use TOAD debug so it's only ever switched on by accident or after a reinstall (it's the default) - so turning debug off fixes the problem.

Bug report: SQL Developer 3.2.09 Crashes for some Replace Regexp

Hi,
SQL Developer 3.2.09 (tested on Win XP with SQL Developer built-in Java) crashes for some Replace Regexp.
Try the following:
New SQL-sheet
CTRL-R for Replace
Enter "||" (two chars) as search-expression
Enter "" (nothing) as replace-with-expression
Check Regular Expressions Check Box
Hit OK
-->100% CPU usage, no reaction.
Can you confirm the bug?
Edited by: blama on Sep 4, 2012 3:48 PM

I believe the pipe character is a regexp meta character and your regexp probaby matches everything repeatedly. If you want to replace the concatenation operator you don't need a regexp.
Having said that, I am using SQL Developer on Linux with Java 1.6.0_33 and I don't get the hang, just replacing the same thing again and again.
On windows with 1.6.0_24, I do get the hang. It may be a java issue.
Edited by: Jim Smith on Sep 4, 2012 5:39 PM

Bug report: sql developer/application express application import

I noticed some bugs on deploying an application using sql developer 1.5.1-5440.
Using a single file deployment generated by apex including install/upgrade/remove scripts: Here's what happens:
# I tried installing version 1.1 of my application already existing. Connected to the parsing schema of the version 1.0 I can clearly see my app "dashboard(101)"
# using sql dev I tried an application import. Using the following import options buildstatus =runonly, autoassign app_id and checked run install scripts
# The install runs, but instead of using the upgrade script it simply runs the install script causing a lot of errors of course since the objects already exist in the schema
# After this installation the application is visible in the workspace using a browser dashboard(102), however it remains invisible in sql developer where i can still only see dashboard(101)
After this failure I decided to go ahead and try once more doing the same thing but now just not check run install scripts.
To my amazement it still runs the install scripts???
Now I have 3 application showing in the browser and still only 1 in sql developer
Final problem with sql developer is that I choose to drop dashboard(101) it only deinstalls the application. It does not run the deinstall script for supporting objects included in dashboard(101).
All this makes an easy deployment a real hassle, since the browser interface can't handle a run only apllication with supporting object as all (it simply doesn't run the install script) I need to use sql developer, which is then fine for the first install, but then doen't upgrade properly. Finaly deinstalling a run only application again is impossible from a workspace and does work from sql developer, but then you still have to do the deinstall of the db objects manually.
I know as an apex admin I can work arround al this by switching the build status etc etc, but then again I can do anything if I'm apex admin and db sys.Point in having a single file deployment is allowing a novice user to easily install.
Geert

Hi Scott
Thanks for the reply
sspadafo wrote:
Run Only applications don't show up in the application list because they should not be editable. But perhaps it could display an icon indicating that.In my opinion they should and they do. The single app that is appearing in the list in sql developer is run only. Having it here allows me to select drop amongst other functionality the browser interface currently still lacks. Even when I drop all apps and than reinstall them again it seems like I can only see 1 version of an app with the same name.
sspadafo wrote:
The problem you described where you can't use the Application Install wizard to install supporting objects if the application is set to Run Only should be fixed in the upcoming 3.1.2 release/patch.I've installed the patch and I'm afraid the patch is no good either. Indeed is has improved. After the app installs it shows the supporting object dialogue. But if you then select yes and press Next it does absolutely nothing and redirects tot the application showing Application not available for edit.
So if you would be so kind to reopen bug 7286162
So while I'm on this section in my opinion the following bugs exist/features are missing
SQL Developer interface
# Not all application for parsing schema are shown in connection explorer. It seems like it can multiple show apps with different names only not when you install the same app twice with different app_id's. Then it only show the lowest app_id.
# Installing runonly app with supporting objects installs supporting object regardless of option selected
# Installing runonly app with upgrade scripts ignores update scripts and runs install scripts regardless of "install supporting objects" checkbox's state
# De installing app shows unpredictable behaviour for running deinstall scripts. It seemingly prompts random. Sometimes it does, sometimes it doesn't. When it does show I get behaviour like initially prompting for running deinstall script, failing to run deinstall script, causing neither app or objects to be dropped, on retry not showing prompt anymore and only dropping app.
Browser interface
# Installing a runonly app always finishes with a white page showing only Application not available for edit instead of showing a proper installation summary
# Installing a runonly app still prevents installation of supporting objects
# De installing a runonly application is not possible. Possible a button for de install could be included on page 4000:733
# Unable to perform important application level task from workspace like changing status, alias, global notification, proxy \\ (which are all available in the sql developer interface and imho could all be added to page 400:733 of the browser interface)
Hope this helps,
Geert

Fallo en SQL Developer , bugs in SQL Developer

He detectado que si hacemos clic con el botón derecho sobre una tabla y seleccionamos EXPORT ==> SQL INSERT. la exportación no se lleva a cabo.
¿Alguien ha detectado este problema?

Mucho mas tarde, doy confirmacion del problema en mi sistema Linux SuSE 10.0 con Oracle 10g release 2 y la ultima version de SQL Developer (Build 14.67). No tengo ningun dato en el fichero ni en el "clipboard". Pero si no selecciono todas las columnas, el fichero o el clipboard se rellenan normalement. Eso explica que algunos dicen que funciona y otros que no funciona.
Como solucion pratica, creo una vista (view) con una columno mas ( *, 1 as nada) y no la selecciono. Solo me queda cambiar el nombre de la tabula en el texto SQL que produce la exportacion.
A few weeks later, I certify there is a bug (en my Linux SuSE 10.0 system con Oracle 10 g release 2 and Build 14.67 of SQL Developer). I obtain an empty file or nothing in the clipboard. If I don't select all fields, the file or clipboard are full of data. This explains why some assert there is no problem and other say there is one. As a practical solution, I created a view with an extra field ( *, 1 as dummy) and didn't select it. I only have to rename the table in the exported SQL text.

Bug in SQl Developer + Ubuntu 64 bits and Open JDK 7

if i use de /usr/lib/jvm/java-1.6.0-openjdk
a have this errors.
SEVERE     283     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     282     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     281     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     280     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     279     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     278     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     277     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     276     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     275     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)

Welcome to the forum!
Please read the FAQ for how to post a question and the information that you need to provide.
The most important thing is that you actually need to post a question. Saying 'when I do this I have errors' is NOT a question. And it does not provide enough information for anyone to help you.
The subject mentions Open JDK 7 but your content uses '/usr/lib/jvm/java-1.6.0-openjdk'. Nothing in what you posted says anything at all about whether you are using sql developer, what version you are using, or how you are trying to launch it.
If you want help you have to provide detailed, specific information about each step you are taking and what results you get.
Have you ever installed or used ANY version of sql developer on ANY platform?
You are on a 64 bit system so are you using 64 bit versions of sql developer and the JDK?
Are you aware that JDK 7 is NOT recommended for use with sql developer at this time?

Bug in SQL Developer 1.5 SQL Worksheet

Hello,
did any of you already encounter the following effect in version 1.5's SQL Worksheet?
When I try to execute the following statement in version 1.5:
select (1 +
2 -
3 +
4)
from dual;
I get the error: ORA-00907 missing right parenthesis
With more complex statements I also get an 'unimplemented feature' error.
When I put the operators in front like this:
select (1
+ 2
- 3
+ 4)
from dual;
i get the correct answer '4' as result. Seems to be clearly a bug for me. In version 1.2 both versions work perfectly well.
Does anyone know whether there's already some bug filed for this or whether there's a patch around?
Regards Holger

Hi Dieter W.
It looks like the command does work in sqlplus , from what I can see only the first line (and continued first line) has continuation character facility. (I am working on an other related SQLDeveloper bug).
i.e. No continuation character (10.2XE)
SQL> select (1 +
2 -
3 +
4)
from dual;
2 3 4 5
(1+2-3+4)
4
Continuation character:
SQL> select (1 -
1 -
1 -
3)
from dual
2 3 select (1 1 1 3)*
ERROR at line 1:
ORA-00907: missing right parenthesis
I am on the lookout for more information...
-Turloch

Bug in SQL Developer Version 1.5.1

I have a problem with the Database Export :
The generated Insert-Command look's like:
INSERT INTO atable (Field1, Field2) VALUES (10.'test');
The Value-Separator is a point and not a comma.
Is it a bug or have I chance to change the separator-parameter?

Others have this problem as well... please check out this thread for more angles to attack this problem. Cheers.
1.5 - Export to INSERT statements doesn't work
-Tim

SQL Developer 3.1 Bug: Tabs get closed!!!

Hi!
There is a bug in SQL Developer 3.1 which closes previously opened object editors when the number of opened editors increases over a certain amount.
e.g.:
Open PL/SQL package editors by clicking on them.
After a certain amount of opened packages, the first openend packages begin to disapear.
When theses packages were edited, you are asked if you want to save, ignore or cancel the operation.
Best regards,
Matthias Schulz

Hi Matt,
This is not a bug. The behavior is controlled through preferences:
1. PL/SQL Editor: Tools|Preferences|Code Editor|Auto Pin (checkbox) + Max Open (input field) PL/SQL Editors.
2. ObjectViewer: Tools|Preferences|Database|ObjectViewer|Automatically Freeze Object Viewer Windows (checkbox).
3. Worksheet: Tools|Preferences|Database|Worksheet|Close all worksheets on disconnect (checkbox). Otherwise these inherently remain open.
So we have a minor terminology issue with regard to "Pin" versus "Freeze". Also, another issue with tab width shrinkage as tab number increases:
Please change the way window tabs are handled
Regards,
Gary
SQL Developer Team

Password change fails in SQL Developer with verify function...

A couple of months ago I enforced a password verify function on our 11.2.0.3 databases and also one legacy 10.2.0.4 database.
At the time I tested on my account (which had elevated privileges...doh!).   Now some users are hitting expiry, they can't change it via SQL Developer.
If I create a user with 'create session' privilege and set their profile to one that uses the verify function (see both below), I then log in to SQL Developer (we have tried with versions 3.1 (Windows) and 3.2 (Linux) with same failure results.
BTW,.. the password verify function enforces the following:
password must be minimum of 8 characters
password must not be the same as the user name, or user name (1-100)
password must contain at least a single digit
password must contain at least a single character
1. Works = I log into the local server and run command line SQLPlus, type 'password' and update.   I can successfully change my password.
2. Fails = I log into the local server and run command line SQLPlus, type 'alter user <me> identified by <newpwd>;' I get:
TEST: SUTEMP > alter user sutemp identified by carport9999;
alter user sutemp identified by carport9999
ERROR at line 1:
ORA-28221: REPLACE not specified
This error is because the account does not have the 'alter user' privilege.   I'm okay with this, as I don't want our users having this privilege.
3. I start SQL Developer 3.2, type 'alter user <me> identified by <newpwd>;' I get the same ORA-28221 error as above.   That is fine, and as expected.
4. Now in SQL Developer, I type 'password', set a valid password, but I get 'Failed to change password' in the Script Output tab.
I have a database 'after servererror on database' trigger set, and querying the database table it is logging into, I see a record with a date stamp matching my failure with a server_error=28221 (the same as above).
So I'm wondering if I'm doing something wrong here, or if this is a bug in SQL Developer.   I don't want standard users having 'alter user' privileges, but I do want to enforce password verification.
I get the same result on three 11.2.0.3 databases (haven't tried any more but suspect same results for others) and one legacy 10.2.0.4 database, and using SQL Developer 3.1 and 3.2.
DBA_PROFILE used:
PROFILE
RESOURCE_NAME
RESOURCE LIMIT
CTRU
COMPOSITE_LIMIT
KERNEL     DEFAULT
CTRU
SESSIONS_PER_USER
KERNEL     10
CTRU
CPU_PER_SESSION
KERNEL     DEFAULT
CTRU
CPU_PER_CALL
KERNEL     DEFAULT
CTRU
LOGICAL_READS_PER_SESSION    KERNEL     DEFAULT
CTRU
LOGICAL_READS_PER_CALL
KERNEL     DEFAULT
CTRU
IDLE_TIME
KERNEL     DEFAULT
CTRU
CONNECT_TIME
KERNEL     DEFAULT
CTRU
PRIVATE_SGA
KERNEL     DEFAULT
CTRU
FAILED_LOGIN_ATTEMPTS
PASSWORD 10
CTRU
PASSWORD_LIFE_TIME
PASSWORD 180
CTRU
PASSWORD_REUSE_TIME
PASSWORD DEFAULT
CTRU
PASSWORD_REUSE_MAX
PASSWORD 5
CTRU
PASSWORD_VERIFY_FUNCTION     PASSWORD VERIFY_FUNCTION_11G
CTRU
PASSWORD_LOCK_TIME
PASSWORD .002
CTRU
PASSWORD_GRACE_TIME
PASSWORD 21
16 rows selected.
Verify Function used:
$ cat utlpwdmg.sql
Rem
Rem $Header: utlpwdmg.sql 02-aug-2006.08:18:05 asurpur Exp $
Rem
Rem utlpwdmg.sql
Rem
Rem Copyright (c) 2006, Oracle. All rights reserved.
Rem
Rem    NAME
Rem      utlpwdmg.sql - script for Default Password Resource Limits
Rem
Rem    DESCRIPTION
Rem      This is a script for enabling the password management features
Rem      by setting the default password resource limits.
Rem
Rem    NOTES
Rem      This file contains a function for minimum checking of password
Rem      complexity. This is more of a sample function that the customer
Rem      can use to develop the function for actual complexity checks that the
Rem      customer wants to make on the new password.
Rem
Rem    MODIFIED   (MM/DD/YY)
Rem    suren       05/09/13 - customise for NIHI use
Rem    asurpur     05/30/06 - fix - 5246666 beef up password complexity check
Rem    nireland    08/31/00 - Improve check for username=password. #1390553
Rem    nireland    06/28/00 - Fix null old password test. #1341892
Rem    asurpur     04/17/97 - Fix for bug479763
Rem    asurpur     12/12/96 - Changing the name of password_verify_function
Rem    asurpur     05/30/96 - New script for default password management
Rem    asurpur     05/30/96 - Created
Rem
-- This script sets the default password resource parameters
-- This script needs to be run to enable the password features.
-- However the default resource parameters can be changed based
-- on the need.
-- A default password complexity function is also provided.
-- This function makes the minimum complexity checks like
-- the minimum length of the password, password not same as the
-- username, etc. The user may enhance this function according to
-- the need.
-- This function must be created in SYS schema.
-- connect sys/<password> as sysdba before running the script
CREATE OR REPLACE FUNCTION verify_function_11G
(username varchar2,
password varchar2,
old_password varchar2)
RETURN boolean IS
   n boolean;
   m integer;
   differ integer;
   isdigit boolean;
   ischar boolean;
   ispunct boolean;
   db_name varchar2(40);
   digitarray varchar2(20);
   punctarray varchar2(25);
   chararray varchar2(52);
   i_char varchar2(10);
   simple_password varchar2(10);
   reverse_user varchar2(32);
BEGIN
   digitarray:= '0123456789';
   chararray:= 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ';
   -- Check for the minimum length of the password
   IF length(password) < 8 THEN
      raise_application_error(-20001, 'Password length less than 8');
   END IF;
   -- Check if the password is same as the username or username(1-100)
   IF NLS_LOWER(password) = NLS_LOWER(username) THEN
     raise_application_error(-20002, 'Password same as or similar to user');
   END IF;
   FOR i IN 1..100 LOOP
      i_char := to_char(i);
      if NLS_LOWER(username)|| i_char = NLS_LOWER(password) THEN
        raise_application_error(-20005, 'Password same as or similar to user name ');
      END IF;
    END LOOP;
   -- Check if the password contains at least one letter, one digit
   -- 1. Check for the digit
   isdigit:=FALSE;
   m := length(password);
   FOR i IN 1..10 LOOP
      FOR j IN 1..m LOOP
         IF substr(password,j,1) = substr(digitarray,i,1) THEN
            isdigit:=TRUE;
             GOTO findchar;
         END IF;
      END LOOP;
   END LOOP;
   IF isdigit = FALSE THEN
      raise_application_error(-20008, 'Password must contain at least one digit, one character');
   END IF;
   -- 2. Check for the character
   <<findchar>>
   ischar:=FALSE;
   FOR i IN 1..length(chararray) LOOP
      FOR j IN 1..m LOOP
         IF substr(password,j,1) = substr(chararray,i,1) THEN
            ischar:=TRUE;
             GOTO endsearch;
         END IF;
      END LOOP;
   END LOOP;
   IF ischar = FALSE THEN
      raise_application_error(-20009, 'Password must contain at least one digit, and one character');
   END IF;
   <<endsearch>>
   -- Check if the password differs from the previous password by at least
   -- 3 letters
   IF old_password IS NOT NULL THEN
     differ := length(old_password) - length(password);
     differ := abs(differ);
     IF differ < 3 THEN
       IF length(password) < length(old_password) THEN
         m := length(password);
       ELSE
         m := length(old_password);
       END IF;
       FOR i IN 1..m LOOP
         IF substr(password,i,1) != substr(old_password,i,1) THEN
           differ := differ + 1;
         END IF;
       END LOOP;
       IF differ < 3 THEN
         raise_application_error(-20011, 'Password should differ from the old password by at least 3 characters');
       END IF;
     END IF;
   END IF;
   -- Everything is fine; return TRUE ;
   RETURN(TRUE);
END;
alter profile ctru limit password_verify_function verify_function_11g;
alter profile default limit password_verify_function verify_function_11g;
alter profile web_and_it limit password_verify_function verify_function_11g;

okay,... I just saw another website which shows I should put in the 'replace <oldpwd>' clause in.
This works in SQL Developer:     alter user sutemp identified by carport999 replace garage999;
So why does the 'password' command fail?     (Developers: it would also be helpful to have the ORA- error displayed as opposed to 'Failed to change password')

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

Statement terminator problems when exporting data with SQL Developer 3.2

I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
Thanks,
-Bill

>
So, it would appear that this is a bug, but I'm not sure.
>
That would be a bug. Thanks for reporting it and providing the detailed example.
>
Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
>
No.
Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

SQL Developer 3.0.04 deleted contents of many tables mystically!!!

I just upgraded SQL Developer 3.0.04 on Windows XP with dual core and SSD drive. Database is 10g. I was clicking on data content tab and looking at one table from database, but it suddenly reported an error like "no more data...".
I thought my connection was dropped (I am using port forwarding tunnel to connect to database). I disconnect and reconnect to database, but suddenly I found more than 10 tables have been emptied. All data in those tables were DELETED!!! Some tables were left untouched.
It must be a huge bug in SQL Developer. I have been using it for three years. It used to be just slow, but never did something like this.
William

Luckily, it's not happening to our prod database. It is still scary, so I investigated a little bit more. This is what I found from v$sql. At that time range, some weird delete statements were issued to our database as follows. We definitely don't have any tables or views with those names. Anyone has an idea what those sqls are about?
SQL_TEXT first_load_time
delete from dir$ where obj#=:1     2011-04-13/19:16:03
delete from dir$ where obj#=:1     2011-04-13/19:16:03
delete from opbinding$ where obj#=:1     2011-04-13/19:16:03
delete from opbinding$ where obj#=:1     2011-04-13/19:16:03
delete from oparg$ where obj# = :1     2011-04-13/19:16:03
delete from oparg$ where obj# = :1     2011-04-13/19:16:03
delete from triggercol$ where obj#=:1     2011-04-13/19:16:03
delete from triggercol$ where obj#=:1     2011-04-13/19:16:03
delete from triggercol$ where obj#=:1     2011-04-13/19:16:03
delete from cdef$ where con#=:1     2011-04-13/19:16:03
delete from cdef$ where con#=:1     2011-04-13/19:16:03
delete from javaobj$ where obj#=:1     2011-04-13/19:16:03
delete from javaobj$ where obj#=:1     2011-04-13/19:16:03
delete from procedure$ where obj#=:1     2011-04-13/19:16:03
delete from procedure$ where obj#=:1     2011-04-13/19:16:03
delete from procedure$ where obj#=:1     2011-04-13/19:16:03
delete from trigger$ where obj#=:1     2011-04-13/19:16:03
delete from ccol$ where con#=:1     2011-04-13/19:16:03
delete from ccol$ where con#=:1     2011-04-13/19:16:03
delete from com$ where obj#=:1     2011-04-13/19:16:03
delete from com$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavas$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavas$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavam$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavam$ where obj#=:1     2011-04-13/19:16:03
delete from type_misc$ where obj#=:1     2011-04-13/19:16:03
delete from type_misc$ where obj#=:1     2011-04-13/19:16:03
delete from error$ where obj#=:1     2011-04-13/19:16:03
delete from error$ where obj#=:1     2011-04-13/19:16:03
delete from context$ where obj#=:1     2011-04-13/19:16:03
delete from context$ where obj#=:1     2011-04-13/19:16:03
delete from settings$ where obj# = :1     2011-04-13/19:16:03
delete from settings$ where obj# = :1     2011-04-13/19:16:03
select name,owner# from con$ where con#=:1     2011-04-13/19:16:03
delete from triggerjavac$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavac$ where obj#=:1     2011-04-13/19:16:03
delete from opancillary$ where obj#=:1     2011-04-13/19:16:03
delete from opancillary$ where obj#=:1     2011-04-13/19:16:03
delete from library$ where obj#=:1     2011-04-13/19:16:03
delete from library$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavaf$ where obj#=:1     2011-04-13/19:16:03
delete from triggerjavaf$ where obj#=:1     2011-04-13/19:16:03
delete from viewcon$ where robj#=:1     2011-04-13/19:16:03
delete from operator$ where obj#=:1     2011-04-13/19:16:03
delete from operator$ where obj#=:1     2011-04-13/19:16:03
Thanks,
William

Meening of Geen Bug in SQL Developer 2.1.0.62

Similar Messages

Maybe you are looking for