Avoiding PLW-07202 warning in SQL Developer

Hi All,
I am using EM Console to create package, now I have switched over to SQL Developer. When I was using EM Console, It was not showing any warning, but that same package when compiled in SQL Developer It show following warning:
PLW-07202: bind type would result in conversion away from column type
I want to avoid this warning to occur everytime when I compile.
How do I do it?
Help...

or issue an alter session/alter system yourself or :
http://www.oracle-base.com/articles/10g/PlsqlEnhancements10g.php#compile_time_warnings
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/errors.htm#sthref2096
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams166.htm#REFRN10249

Similar Messages

Stupid PLW-07202 warning

Hi,
I get a stupid bunch of warning when compiling this under 11.1.0.7:
create table test ( t varchar2(50) );
create or replace procedure test_warn as
    BEGIN
        INSERT INTO test (t)
             SELECT substr('blah', 1, 2)
                       FROM dual;
END;
SP2-0804: Procedure created with compilation warnings
show errors
Errors for PROCEDURE TEST_WARN:
LINE/COL ERROR
6/37     PLW-07202: bind type would result in conversion away from column type
6/40     PLW-07202: bind type would result in conversion away from column typeThe locations point to the "1" and "2" parameters in substr(). WTF???
Thanks,
Chris

What is the database trying to warn me from precisely?Looks like Bug 5983734: SPURIOUS PLW-07202, which still holds in 11gR2:
SQL> select * from v$version where rownum = 1
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
1 row selected.
SQL> alter session set plsql_warnings='enable:all'
Session altered.
SQL> create table t (a varchar2(40))
Table created.
SQL> alter system flush shared_pool
System altered.
SQL> create or replace procedure p as
begin
insert into t values (substr('abc',1,2));
end;
Procedure created.
SQL> show err
Errors for PROCEDURE P
LINE/COL ERROR
3/37     PLW-07202: bind type would result in conversion away from column
         type
3/39     PLW-07202: bind type would result in conversion away from column
         type
1/1      PLW-05018: unit P omitted optional AUTHID clause; default value D
         EFINER used
SQL> exec p
PL/SQL procedure successfully completed.
SQL> select sql_text from v$sql
where   lower(sql_text) not like '%v$sql$'
and     lower(sql_text) like 'insert into t values%'
SQL_TEXT
INSERT INTO T VALUES (SUBSTR('abc',1,2))
1 row selected.
/* no binding takes place at all, so a message about binding seems non-sensical. */
SQL> alter system flush shared_pool
System altered.
SQL> create or replace procedure p as
s varchar2(3) := 'abc';
s1 int := 1;
s2 int := 1;
begin
insert into t values (substr(s, s1, s2));
end;
Procedure created.
SQL> show err
Errors for PROCEDURE P
LINE/COL ERROR
6/34     PLW-07202: bind type would result in conversion away from column
         type
6/38     PLW-07202: bind type would result in conversion away from column
         type
1/1      PLW-05018: unit P omitted optional AUTHID clause; default value D
         EFINER used
SQL> exec p
PL/SQL procedure successfully completed.
SQL> select sql_text from v$sql
where   lower(sql_text) not like '%v$sql$'
and     lower(sql_text) like 'insert into t values%'
SQL_TEXT
INSERT INTO T VALUES (SUBSTR(:B3 , :B2 , :B1 ))
1 row selected.
But (1) the datatypes of the PL/SQL variables that are bound are exactly
right for Substr(). And (2), the binding occurs in an expression that's that
right-hand-side for "set <column> =" so there's possibility of an index
being in use.
*/

How to view warning in SQL developer

Dear experts,
After I executed a script, in the output I got the following message:
Warning: execution completed with warning
How can I view the warning?
Pardon my ignorance, regards,
Valerie

What are the contents of the script?
If you're compiling PL/SQL, you should work through the PL/SQL Editor for getting the best results ("Edit" in the context menu of the object in the navigator).
If you must work with scripts, you can always issue "SHOW ERRORS" at the end.
Have fun,
K.

SQL Developer 1.5.1 - warning messages generated by CREATE TABLE

Hi,
Have an issue with a CREATE TABLE statement - it works correctly, but generates a warning message when used in SQL Developer (1.2 or 1.5.1). Full test case below:
Setup:
drop table samplenames;
drop table customers;
drop table phones;
drop table customers_phone;
drop sequence primkey;
create table samplenames
(name VARCHAR2(10));
insert into samplenames values ('dan');
insert into samplenames values ('joe');
insert into samplenames values ('bob');
insert into samplenames values ('sam');
insert into samplenames values ('weslington');
insert into samplenames values ('sue');
insert into samplenames values ('ann');
insert into samplenames values ('mary');
insert into samplenames values ('pam');
insert into samplenames values ('lucy');
create sequence primkey
start with 1000000
increment by 1;
create table customers as
select primkey.nextval as cust_id,
tmp1.name || tmp2.name as first_name,
tmp3.name || tmp4.name || tmp5.name as last_name
from samplenames tmp1,
samplenames tmp2,
samplenames tmp3,
samplenames tmp4,
samplenames tmp5;
CREATE TABLE PHONES AS
SELECT cust_id, 'H' as phn_loc, trunc(dbms_random.value(100,999)) as area_cde,
trunc(dbms_random.value(1000000,9999999)) as phn_num
FROM customers;
INSERT INTO PHONES
SELECT cust_id, 'B' as phn_loc, trunc(dbms_random.value(100,999)) as area_cde,
trunc(dbms_random.value(1000000,9999999)) as phn_num
FROM customers;
--randomly delete ~10% of records to make sure nulls are handled correctly.
delete from phones
where MOD(area_cde + phn_num, 10) = 0;
create table statement (there are legacy reasons for why this is written the way it is):
CREATE TABLE customers_phone NOLOGGING AS
SELECT cst.*,
piv.HOME_PHONE,
piv.WORK_PHONE
FROM (SELECT cust_id,
MAX(decode(phn_loc, 'H', '(' || area_cde || ') ' ||
substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS HOME_PHONE,
MAX(decode(phn_loc, 'B', '(' || area_cde || ') ' ||
substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS WORK_PHONE
FROM phones phn
WHERE phn_loc IN ('H', 'B')
AND cust_id IS NOT NULL
AND EXISTS (SELECT NULL
FROM customers
WHERE cust_id = phn.cust_id)
GROUP BY cust_id) piv,
customers cst
WHERE cst.cust_id = piv.cust_id (+)
Warning message output:
"Error starting at line 1 in command:
CREATE TABLE customers_phone NOLOGGING AS
SELECT cst.*,
piv.HOME_PHONE,
piv.WORK_PHONE
FROM (SELECT cust_id,
MAX(decode(phn_loc, 'H', '(' || area_cde || ') ' || substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS HOME_PHONE,
MAX(decode(phn_loc, 'B', '(' || area_cde || ') ' || substr(phn_num,1,3) || '-' || substr(phn_num,4,4), NULL)) AS WORK_PHONE
FROM phones phn
WHERE phn_loc IN ('H', 'B')
AND cust_id IS NOT NULL
AND EXISTS (SELECT NULL
FROM customers
WHERE cust_id = phn.cust_id)
GROUP BY cust_id) piv,
customers cst
WHERE cst.cust_id = piv.cust_id (+)
Error report:
SQL Command: CREATE TABLE
Failed: Warning: execution completed with warning"
I am on 10.2.0.3. The CREATE TABLE always completes successfully, but the warning bugs me, and I have had no success tracking it down since there is no associated numberr.
Anyone have any ideas?

Hi ,
The Oracle JDBC driver is returning this warning so I will be logging an issue with them, but for the moment SQL Developer will continue to report the warning as is.
The reason for the warning is not clear or documented as far as I can tell,
but I have replicated the issue with a simpler testcase which makes it easier to have a guess about the issue :)
----START
DROP TABLE sourcetable ;
CREATE TABLE sourcetable(col1 char);
INSERT INTO sourcetable VALUES('M');
DROP TABLE customers_phone;
CREATE TABLE customers_phone AS
SELECT MAX(decode(col1, 'm','OK' , NULL)) COLALIAS
FROM sourcetable;
----END
The warning occurs in the above script in SQL Developer , but not in SQL*Plus.
The warning disappears when we change 'm' to 'M'.
The warning disappears when we change NULL to 'OK2'
In all cases the table creates successfully and the appropriate values inserted.
My gut feeling is ...
During the definition of customers_phone, Oracle has to work out what the COLALIAS datatype is.
When it sees NULL as the only alternative (as sourcetable.col1 = 'M' not 'm') it throws up a warning. It then has to rely on the 'OK' value to define the COLALIAS datatype, even though the 'OK' value wont be inserted as sourcetable.col1 = 'M' and not 'm'. So Oracle makes the correct decision to define the COLALIAS as VARCHAR2(2), but the warning is just to say it had to use the alternative value to define the column.
Why SQL*Plus does not report it and JDBC does, I'm not sure. Either way it doesn't look like a real issue.
Again, this is just a guess and not a fact.
Just though an update was in order.
Regards,
Dermot.

SQL developer starts and then disappears without any warning

Hi, guys:
I need to use SQL developer where there are existing connections. however, SQL developer 3.1 asked the java.exe location, and I chose java 6, now I can launch SQL developer but not able to continue running it. SQL developer starts and then disappears without any warning. Could anyone help me on this problem?
Thanks a lot!
Sam

Can you start the exe from the BIN subdirectory? That should open a command console, and maybe you can see any error messages there that explain what's happening. For step-by-step directions, here's some help:
http://www.thatjeffsmith.com/archive/2012/06/how-to-collect-debug-info-for-oracle-sql-developer/
OR
Install SQL Developer to a new directory and run it from there and see if that helps you get around your current install's issue.

SQL Developer 4.0 Early Adopter 2 - avoid "Please amend your code to something like this" message

When I edit PL/SQL packages or sql queries in SQL Developer 4.0 Early Adopter 2,
when i copy/paste SQL code, sometimes "Please amend your code to something like this: "select * from when", or "begin when; end;" appears.
Sometimes SQL Developer freezes.
Can I avoid that message (turn off some kind of checks in SQL Developer properties)?

This has been raised/documented fixed in future releases here:
EA42 - Ambiguous Context Pop-up

Sql developer 3.0: could be possible to avoid creating connections

Hi, when connecting from oracle forms, you don't have to create a connection, in the same way I don't know if could be possible to avoid creating connections when you are using a tnsnames.ora archive.
simple to choose the connection as in oracle forms, and the posibility to save the password.
thank you

As stated in the forum announcement, you can request this at the SQL Developer Exchange, so other users can vote and add weight for possible future implementation.
Regards,
K.

Top 10 Obstacles to Sql Developer Becoming a World-class Tool

I've been working with Sql Developer day and night for the last 6 months.
On a positive note, the SqlDeveloper team has been the most responsive Oracle product team I've worked with in the 19 years I've been working with Oracle tools. They pay attention to their customers. It's noticed and much appreciated!
I thought I would share the biggest problems that I face with the tool on a daily basis, the kind of problems that make me want to work with a different tool each and every day.
My intent isn't to gripe, it's to focus attention on the biggest productivity drains I face using the tool. Others may have a different list, based on their needs. Without further ado, here is my top 10 problems list:
1) Quality Control.
I cannot count on critical portions of the tool working correctly. This includes an oracle database development tool that is incapable of extracting oracle ddl correctly and which is incapable of correctly displaying information about SQL Server data and database objects. It also includes destroying connection files and losing keyboard settings. When the product was installed, it was incapable of properly displaying code in a worksheet when I scrolled thru the code. The details are listed in other postings of mine.
2) Quality Control.
See #1.
3) Quality Control.
See #1.
4) Very badly done threading.
The tool locks up on a constant basis when it does a many tasks. Rather than let me work on some other task, I have to wait for it to complete. My current work-around is to have two or three sql developer windows open. That sucks life out of my RAM supply, but at least I can get some work done. And, of course, it will often completely lock up and never return, which means I lose all unsaved worksheets. This forum is full of postings about these issues.
5) Memory Leaks / Internal memory corruption.
If I've had the tool open for a few days, or really worked it hard for a day, I will get bizarre compilation errors that make no sense. If I exit the tool, re-enter the tool, and compile the exact same code all will be well.
6) Awkward and slow data entry interface for frequently performed tasks.
Example: I create a new table and want to start defining columns for it. I remove my hands from the keyboard to press the + button, then I have to set focus on the column name field (it should do that for me!). Now that my hands are back on the keyboard, I have to backspace the dummy "column name" value in the column name field (it should ditch that dummy value for me). Only after all that can I actually enter a column name. When I want to add a new column, it's back to the mouse again, for the same drill. The down arrow key should take me to a new column record, as should pressing return at the end of the last field in the column row.
7) Destroys code
Changing a column datatype from varchar2 to nvarchar2 destroys the length of the column. Changing a field on a view destroys the instead of triggers. This is bad. There is no warning that this this is about to happen, which would at least give us a chance to avoid the problem. Better still, of course, would be not destroying that data.
8) Inaccurate checking for record locking.
When I try to edit records in a data grid for a table, I often get an error message telling me the data was modified in another session. It is simply not true. A hand-written update statement in a sql worksheet will work just fine. I've seen posts in the forum discussing this issue. An Oracle database development tool unable to reliably update oracle data tables is embarrassing. See Obstacle #1.
9) Unicode support
Sql Developer is heads above all the other tools I've tried out on this topic.
However, the configuration of the tool to provide unicode support needs to be simplified.
The tool needs to recognize the encoding of the files that are being opened up. On Windows Vista, Notepad seems to infallibly pick the right encoding for the file when I open it. Sql Developer should do the same. Files have specific encodings, the tool should have a default encoding (that I can override). Right now, the tool has a specific encoding and expects all files to match it. Extracting ddl to a worksheet does not respect the encoding choices of the tool, either. It only works with a limited set of tool encoding choices.
10) Resources
Does the sql developer team have the resources they need to compete with vendors like Microsoft? One really big reason for picking sqlserver over oracle is the ease of use of the Microsoft front-end tools. It's not until later that they may realize that Oracle has more capability, but that's still a lost sale.

We are acutely aware of quality and with each release work at improving this. Providing a polished, professional and ultimately user friendly and useful tool is our constant goal.
The broader our customer base grows, the more demands we have. This is a good and exciting position to be in, although it might mean that we need to slow down on our release cycles.
Release 2.0 should address more of the threading and memory leaks displayed as the team have rewritten some of the sections. As for resources, it's true we're a small team and we get on with the work that we do.It might be a little slower than some would like, but I'm not convinced that having large team is necessarily always the answer.
As ever, some of the points mentioned could be added to the Exchange. We'll be reviewing and updating the Exchange again in the New Year.
I think there is another point to add to your list. A lot of what the tool is and will become is from a positive customer interaction we have had to date. While we continue to grow this, I think the product will grow and improve. The forum and all the positive interactions that happen here are key to taking the product forward.
Regards
Sue

SQL developer not showing compiler warnings

I'm just testing out the new compiler warning contained in 11g related to the "when others" exception handler when it does not have a subsequent raise or raise_application_error.
in SQL plus, this works fine:
SQL> alter session set plsql_warnings='enable:all';
Session altered.
SQL>
SQL> create or replace function do_stuff
2 return number
3 as
4     v_return number;
5 begin
6
7     v_return := 3;
8     return v_return;
9
10 exception
11 when others then
12     return null;
13 end;
14 /
SP2-0806: Function created with compilation warnings
SQL> show errors;
Errors for FUNCTION DO_STUFF:
LINE/COL ERROR
1/1      PLW-05018: unit DO_STUFF omitted optional AUTHID clause; default
         value DEFINER used
11/6     PLW-06009: procedure "DO_STUFF" OTHERS handler does not end in
         RAISE or RAISE_APPLICATION_ERRORbut in SQL developer the output is:
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE     11.2.0.3.0     Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
session SET altered.
FUNCTION do_stuff compiled
No Errors.Anyone experience this issue? is there some setting that makes SQL developer behave differently?

it must be something I'm doing wrong, above, I was running under windows 7 pointing at the version above.
I just tried it under an Enterprise Linux pointing at
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
PL/SQL Release 11.2.0.2.0 - Production
CORE     11.2.0.2.0     Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production                                           and I get exactly the same script output and no compiler window....
actually...... if I go into a procedure window from the schema browser and compile it there, then I get the correct warning messages..... the problem is I mostly develop from .sql files extracted from source control rather than directly from the schema browser, I just want the sql worksheet to be able to show me the same compiler log window.....

Run package store procedure in sql developer

Night staff, I am using Oracle 11g, only that it gives the following error below, which can be wrong and how to rotate within the sql developer?
Warning(3,18): PLW-07203: o parâmetro 'CODCEP_EMP' pode se beneficiar do uso da hint do compilador NOCOPY
ror starting at line 1 in command:
exec buscadb.tabemp('09811370');
Error report:
ORA-06550: linha 1, coluna 7:
PLS-00306: número incorreto de tipos de argumentos na chamada para 'TABEMP'
ORA-06550: linha 1, coluna 7:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause: Usually a PL/SQL compilation error.
*Action:
create or replace PACKAGE BUSCADB AS
TYPE t_cursor IS REF CURSOR;
PROCEDURE TABEMP(CODCEP_EMP IN OUT empresas.cep_emp%TYPE,io_cursor OUT t_cursor);
END BUSCADB;
create or replace PACKAGE BODY BUSCADB AS
PROCEDURE TABEMP(CODCEP_EMP IN OUT empresas.cep_emp%TYPE,io_cursor OUT t_cursor) AS
v_cursor t_cursor;
begin
open v_cursor for
select cod_emp,nom_emp,end_emp,cep_emp
from empresas
where cep_emp = codcep_emp;
io_cursor := v_cursor;
END TABEMP;
END BUSCADB;

These questions should be posted in the SQL And PL/SQL forum.
But I can give you this: READ the error. The procedure takes 2 parameters, you only give 1.
Regards,
K.

Apex Listener 2.0.1 vs Sql Developer Administration 3.2.20.09 bugs

Apex Listener 2.0.1 / Sql Developer 3.2.20.09 / Apex 4.1.1
1. I'm using basic connection type with service name. Each time I connect to listener administration it is resetted to SID with default name as orcl.
2. Test Settings does not work in case hostname is localhost.
Database Settings apex:Cannot connect to APEX_PUBLIC_USER. Исключение ввода/вывода (input/output exception): The Network Adapter could not establish the connection>
At the same time it's working in defaults.xml:
<entry key="db.hostname">localhost</entry>I'm not sure why. Database and Apex Listener are installed on the same mashine. May be this can help:
<Warning> <Server> <x> <> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <> <BEA-002611> <Hostname "x", maps to multiple IP addresses: 10.110.x.x, 0:0:0:0:0:0:0:1> 3. I can see "Enable RESTful Services" action in (url http://docs.oracle.com/cd/E35137_01/appdev.32/e35117/intro.htm#autoId110)SQL Developer User's Guide. Still there is no such action in Sql Developer. Thus settings are always uploaded with enabled RESTful Services.
I see error
The pool named: apex_al does not existeach time I connect to Apex Listener Administration in case of RESTful Services is not configured during configuration of apex.war.
I can't find any restrictions for RESTful Services to be configured. So I think this error is unnecessary.
4. From sql developer User's Guide
Connect (context menu only): Connects to the Application Express Listener (see Connecting to Application Express Listener Server).Retrieve Settings, Upload Settings, and Launch URL are enabled when you connect to the Application Express Listener.>
administration settings are retrieved and displayed but still Retrieve Settings, Upload Settings, and Launch URL are disabled in context menu after connection.
I need to perform New Administration action to make them enabled.
Is this expected behavior ?
Is this all bugs or known features ?
Regards,
Igor

DB: V11.2
APEX V 4.2.3.00.08
APEX Listener: V2.0.5.287.04.27
SQLDeveloper: Version 3.2.20.09
OS WIndows 7 64 bit
I am trying to create a connection to a standalone Apex Listener installation via SQL Developer to manage the listener settings. I start a new connection and after entering the UN/PWD of the Listener Administrator I get the following error:
Authentication failed
"CANNOT CONNECT TO CONNECTION.
INVALID RESOURCE OWNER CREDENTIALS"
In the Standalone APEX Listener DOS window I'm getting the following error message:
SEVERE: The pool named: apex_al does not exist
So where do I even start to trouble shoot this???
I add a connection as follows:
Connection Name: Connection
Usename: adminlistener (pwd=adminlistener configured using command :java -jar apex.war user adminlistener "Listener Administrator")
HTTP radio button
Hostname: localhost
Port: 8080
Server Path: /apex
thanks in advance
Paul Platt

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

SPEEDING UP YOUR PL/SQL DEVELOPMENT

제품 : SQL*PLUS
작성날짜 : 1997-01-09
=================================
Speeding up your PL/SQL development
=================================
By Jeff Warner
If you're doing Oracle database or application development, then you're probably using PL/SQL. Every PL/SQL programmer is familiar with
using SQL*Plus to develop PL/SQL programs. Developer/2000 offers a better way: Procedure Builder. In this article we'll explore how
Procedure Builder can improve your PL/SQL development.
It has a GUI
==========
The first feature you'll notice in Procedure Builder is the graphical user interface (GUI). Procedure Builder provides separate windows for the
Object Navigator, the PL/SQL interpreter, and the program unit editor. By the way, if you think the program unit editor looks familiar, you're
probably right. Oracle uses it inside the other tools in Developer/2000 (Forms, Reports, and Graphics). Using the Object Navigator, you can
view the relationship between your code and the library and packages. Object Navigator also provides the references and referenced-by
information, as well as giving you the ability to examine the procedures and functions that make up packages and libraries. This makes it very
easy to take advantage of existing code.
The PL/SQL interpreter is just what you'd expect. You can use normal SQL and PL/SQL commands and see the results in the output
window. You create your PL/SQL in the program unit editor window. As with any text editor, you can cut, copy, and paste as well as search
and replace text. You can also use the editor to import and export source files. However, the editor's best feature is the Compile button. Click
the Compile button, and Procedure Builder will compile your code and display any errors in the bottom of the window. Click on the error,
and your cursor will move to the offending line. This will radically improve the compile-debug-run sequence. Speaking of debugging,
Procedure Builder has something that will really make life easier for you.
A PL/SQL debugger
================
Yes, Procedure Builder includes a real debugger for PL/SQL. Its features include breakpoints, triggers, variable inspection, variable
modification, step into, step over, and step out.
Having a graphical and easy-to-use debugger can dramatically improve code development. For example, to set a breakpoint in your code,
simply bring the PL/SQL interpreter window to the front and double-click on the line where a breakpoint is needed.
Once you've set a breakpoint and executed the code, the debugger will stop the program at the breakpoint. From here, you can use Object
Navigator to view and change the variables in the program. To resume execution, you can use Procedure Builder to step into, step over, or
step out of a routine. Procedure Builder also provides an option to simply continue execution.
A powerful feature of Procedure Builder's breakpoints is the capability of adding trigger code. Trigger code is a piece of PL/SQL that
executes when the breakpoint is hit. You can use this feature to log the value of a variable to the screen or a file.
If you need a conditional breakpoint, you can use a trigger. For example, let's say you want to stop execution only if the local variable i is
greater than zero. First, select the line where you want the check to occur and create a trigger by clicking the right mouse button on the line
and selecting Trigger. This will open the PL/SQL Trigger window. In the Trigger Body area, enter the following command to halt execution:
if debug.geti('i') > 0 then
raise debug.break;
end if;
Now the program will stop execution only when this condition is valid. You can also use the Trigger Body of a trigger to log information to a
file or a screen.
Debugging server-side programs
===========================
The version of Procedure Builder shipped with version 1.2 of Developer/2000 is V1.5.5.7.0. Unfortunately, it doesn't allow you to directly
debug programs on the server (this is planned for a future version). However, with the click-and-drag partition feature of Developer/2000,
you can use Object Navigator to drag the program unit from the server to the local program unit and debug it there.
Lots of help
=========
Procedure Builder includes extensive help under Windows. In addition to the normal help available on program features, Procedure Builder
provides help on the built-in packages as well as the PL/SQL commands to maintain libraries, program units, and packages. Also, version 1.2
or later of Developer/2000 provides the Cue Cards and Quick Tour.
Conclusion
=========
As you can see, Procedure Builder is a very powerful tool for development. The debugger is first-rate and the extensive help is a great
addition. One other nice feature of Procedure Builder is that Oracle will license it separately from Developer/2000 if you have users who don't indeed the other parts of Developer/2000. If you're doing PL/SQL programming, you should take advantage of what Procedure Builder has to
offer.

micwic --
I logged bug6508875 for this.
One suggestion in the meantime until we can get compile errors directed to the log window for offline objects...
You can open the Database Navigator to point to the same db connection. After generating the offline PL/SQL to the db, refresh the connection in the DB navigator. You will see any invalid objects flagged with an error icon. Then you can right-click on the PL/SQL with the error, and "Make" it. This will display the errors in the log window, similar to SQL Developer.
-- Brian

How can I use an existing local svn workspace with SQL Developer?

I have a couple directories of files on my local drive that hold my current working files from the svn repository. I use both TortoiseSVN and Cygwin to keep the local files in sync with the repository, depending on my mood. I have created a connection to the repository in SQL Developer, and I can browse the repository just fine. My goal is to have SQL Developer play nice with the local files, just like the other two Subversion clients do. Is there a way I can inform SQL Developer of my local files without re-importing them through the Versioning -> Import... wizard, without changing anything (or putting anything at risk) in the local workspace?
Thanks in advance for your help -
Wally

Then can her computer be authorized to both accounts?
Absolutely. You can authorize any given computer to up to five iTunes Store accounts.
If purchases are made on her account, to a computer authorized to my account, can I put those songs on my iPod?
If you connect your iPod to her computer, yes. Tracks download only to the computer from which they're purchased, regardless of which iTunes Store account is used for the purchase. Or you could copy the tracks from her computer to yours and then authorize your computer to her iTunes Store account. But that's sort of defeating the original purpose, it would seem to me.
is it better to buy music through Amazon downloads and/or actually purchasing CDs to avoid the security features iTunes puts on its music?
That's certainly an option. If it's an entire album I want, I buy CDs. That way I can import them at the quality I want and to whichever of my systems I want. Amazon or one of the other download stores that offer tracks as MP3 are also an option, though for me download stores are best when you just want a couple of tracks off a given CD.

Issue with migration DB from SQL Server 2005 to Oracle 11.2 using SQL Developer Migration workbench

Hi,
We face an issue while migrating an SQL Server 2005 DB to Oracle 11.2. It fails during the process. I hope someone on the forum has seen this before and can give us some advice.
I use the latest version of SQL Developer with JRE included (3.2.20.09). The JDBC driver to connect to SQL Server 2005 is 1.2.0
Here are the steps we take in the Migration Workbench wizard:
I made an online extract of the SQL Server database.
Using the workbench in SQL Developer I created a migration repository in schema PDM_MIGRATION.
Next I start the migration, it captures the tables fine, but immediately after the start of the conversion I get a failed message without further explanations.
This is the content of the error xml:
<?xml version="1.0" encoding="windows-1252" standalone="no"?>
<log>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@4c12ab</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>SEVERE</level>
<class>oracle.dbtools.migration.workbench.core.logging.MigrationLogUtil</class>
<message>Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
<param>oracle.dbtools.migration.convert.ConverterWorker.copyModel(ConverterWorker.java:1078)</param>
<param>oracle.dbtools.migration.convert.ConverterWorker.runConvert(ConverterWorker.java:316)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doConvert(FullMigrateTask.java:1002)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doMaskBasedActions(FullMigrateTask.java:303)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:205)</param>
<param>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask.doWork(FullMigrateTask.java:159)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:515)</param>
<param>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)</param>
<param>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)</param>
<param>java.util.concurrent.FutureTask.run(FutureTask.java:138)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)</param>
<param>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)</param>
<param>java.lang.Thread.run(Thread.java:662)</param>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@5dc1bc</param>
<exception>
    <message>oracle.dbtools.migration.convert.ConvertException: Ongeldig naampatroon.: PDM_MIGRATION .MIGR_FILTER</message>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>1078</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.convert.ConverterWorker</class>
      <line>316</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>1002</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>303</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>205</line>
    </frame>
    <frame>
      <class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
      <line>159</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTask</class>
      <line>193</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask</class>
      <line>515</line>
    </frame>
    <frame>
      <class>java.util.concurrent.Executors$RunnableAdapter</class>
      <line>441</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask$Sync</class>
      <line>303</line>
    </frame>
    <frame>
      <class>java.util.concurrent.FutureTask</class>
      <line>138</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>886</line>
    </frame>
    <frame>
      <class>java.util.concurrent.ThreadPoolExecutor$Worker</class>
      <line>908</line>
    </frame>
    <frame>
      <class>java.lang.Thread</class>
      <line>662</line>
    </frame>
</exception>
</record>
<record>
<date>2013-08-14T16:23:32</date>
<logger>oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle</logger>
<level>WARNING</level>
<class>oracle.dbtools.migration.workbench.core.ui.FullMigrateTask</class>
<message>Building converted model: FAILED : Database Migration : FAILED</message>
<param>oracle.dbtools.migration.workbench.core.logging.LogInfo@15a3779</param>
</record>
Does anybody know what this error means and what steps we should take to continue the migration?
I see the PDM_MIGRATION.MIGR_FILTER is a type.
Many thanks in advance,
Kris

Hi Wolfgang,
Thanks for your reply.
This is how the type MIGR_FILTER looks like:
create or replace
TYPE MIGR_FILTER IS OBJECT (
FILTER_TYPE INTEGER, -- Filter Types are 0-> ALL, 1->NAMELIST, 2->WHERE CLAUSE, 3->OBJECTID LIST
OBJTYPE VARCHAR2(40),
OBJECTIDS OBJECTIDLIST,
NAMES NAMELIST,
WHERECLAUSE VARCHAR2(1000));
I think the repository user has the correct privileges. This is the overview of privileges it has:
SQL> select * from dba_sys_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE PRIVILEGE ADM
PDM_MIGRATION ALTER SESSION NO
PDM_MIGRATION CREATE CLUSTER NO
PDM_MIGRATION CREATE DATABASE LINK NO
PDM_MIGRATION CREATE PROCEDURE NO
PDM_MIGRATION CREATE SEQUENCE NO
PDM_MIGRATION CREATE SESSION NO
PDM_MIGRATION CREATE SYNONYM NO
PDM_MIGRATION CREATE TABLE NO
PDM_MIGRATION CREATE TRIGGER NO
PDM_MIGRATION CREATE VIEW NO
PDM_MIGRATION UNLIMITED TABLESPACE NO
SQL> select * from dba_role_privs where GRANTEE in ('PDM_MIGRATION') order by GRANTEE;
GRANTEE GRANTED_ROLE ADM DEF
PDM_MIGRATION CONNECT NO YES
PDM_MIGRATION RESOURCE NO YES
Best regards,
Kris

Avoiding PLW-07202 warning in SQL Developer

Similar Messages

Maybe you are looking for