Enhancement Req: Logging of actions within SQL Developer

I've always felt that was a deficiency of OEM - there was no way that I knew of to log what you did, especially DDL commands.
I wish that SQL Developer would add that capability, for several reasons not the least of which is to be able to extract an ad-hoc commands to put in a script if you ever had to rebuild your schema.
Another reason is to record your actions to validate what you had done.

If you edit the sqldeveloper.conf file. and uncomment this line
#AddVMOption -Daudit.trace=db_api
You'll should see just about every sql we issue either on a message log or on the console.
-kris

Similar Messages

How to create save actions in SQL Developer 1.5?

Hi,
I am trying to create a save action in SQL Developer, which shall execute "an external tool" I already added.
I choose "Code-Editor" -> "save actions". I want to add an action, but there are 3 predefined actions and there is no possibility for me to add another. Is there a way for me to add a save action, as it is possible in eclipse?
What I am trying to do is, I want to trigger an external sql formatter. The sql formatter, which is built in, doesn't fit my needs and the way I can configure it, is very sparse. Therefore I want to use an external tool do to this - and I want it to be executed after saving the document.
Greetings,
Daniel

Right click on the table and select "Export Data": default format is INSERT statement.
Example of generated SQL:
-- Fichier créé - mardi-septembre-13-2011
-- DDL for Table HELP
CREATE TABLE "SYSTEM"."HELP"
   (     "TOPIC" VARCHAR2(50 BYTE),
     "SEQ" NUMBER,
     "INFO" VARCHAR2(80 BYTE)
   ) PCTFREE 0 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 49152 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "SYSTEM" ;
REM INSERTING into SYSTEM.HELP
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',1,null);
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',2,' @ ("at" sign)');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',3,' -------------');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',4,' Runs the SQL*Plus statements in the specified script. The script can be');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',5,' called from the local file system or a web server.');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',6,null);
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',7,' @ {url|file_name[.ext]} [arg ...]');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',8,null);
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',9,' where url supports HTTP and FTP protocols in the form:');
Insert into SYSTEM.HELP (TOPIC,SEQ,INFO) values ('@',10,null);
(...)SQL Developer documentation: http://download.oracle.com/docs/cd/E18464_01/index.htm.
Edited by: P. Forstmann on 13 sept. 2011 21:27

Changing password within SQL Developer

Hi, Thanks for the great product. I'm beginning to migrate from TOAD to SQL Developer and have run into one minor snafu. The one minor feature missing within SQL Developer (unless I missed it) is to easily change a password like TOAD in the UI (This is a common complaint among other devlopers trying it out). I work on a lot of seperate databases occasionally and have to reset the passwords every 60 days.
I would like to request this minor feature.
How can I change my password without using SQL Plus, but within SQL Developer? Is there a way?
Thank you!

Sounds like a good enhancement and I will record it. In the meanwhile, just open a SQL Worksheet and issue your command.
-- Sharon

Query Builder within SQL Developer 2.1 versus Query Builder Version 6.0.7.1

Dear all,
dear Sue Harper,
we use Oracle 10g (upgrade to 11g is planed) and used the Oracle Query Builder Version 6.0.7.1 by now unless we got to know about the SQL Developer 2.1 including the Query Builder a few weeks ago to produce our SQL statements an efficient way.
Even tho the SQL Developer 2.1 Query Builder already has some nice features, like sorting the data fields ascending, export to excel, etc, that the Oracle Query Builder Version 6.0.7.1 did not have had, we miss some essential features, like the in-statement, define column, etc while on the other side tables are not included in SQL-code unless fields are selected or i.e. date fields cannot be queried in the where conditions.
I read the release notes and know that the SQL Developer 2.1 Query Builder is scheduled for rewrite in the next release.
Does it make any sense to summarized all things we noticed and get in touch with whomever it may concern?
Btw, if it would be possible to define a location for the stored connections within the SQL Developer 2.1 it would be very helpful... When starting SQL Developer 2.1 in our Windows Vista network environment it never finds the connection settings (file) automatically and we have to re-import the connections from a pre-defined directory.
Nevertheless, the SQL Developer 2.1 is a pretty user-friendly and most times reliable tool we are thankful for.
Kind regards,
Stefan Wagner
[email protected]

@user12092220
Yep, I saw your post; sorry for not replying, but i thought it's pretty the same problem i have. ;)
The missing possibility to query date-fields in the where clause is really one of a many things i miss in the SQL Dev Query Builder, i am sure you use an "in" statement as well as we do. I think going back to the manual creation of the where condition like we had in Version 6.0.7.1.0 should be okay with most users, at least additional to the current solution as long as the rest of the query can be built within the graphic user interface. Further to save and open a query in gui mode is really, really important for us. Not to mention that the boxes for the tables cannot be stretched over a certain extend and i cant separate the columns any longer :/
Other than that, SQL Developer is a pretty nice tool in my eyes, it's free and hopefully Version 3.0 will be closer to what we would like the SQL Developer to be like.
Stefan

Default path for scripts within SQL Developer version 3.2.20.09.87

I have SQL Developer version 3.2.20.09.87 and needed to know if the 'Set default path to look for scripts' be a UNC path?
Thanks

I hadn't tried it but now I did and it worked.
I also tried setting the Utilities Export default file location to a UNC path and I was able to set it but when I try to go to it via the 'browse' button, it doesnt go to it. It does, however, use it when I export.
Also when I do File > Open, I'm not able to navigate to UNC paths via the 'Home' or 'Desktop' buttons on the left hand side of the window and am not able to navigate to a network location from the 'Locations' box.
Any ideas? I am on Windows 7.
Thanks

Oracle SQL Developer (Not seeing object names within the interface)

Hello,
I was finally able to perform an export/import from our production environment to our training environment. Anyway, this was done using the SYS account and for some reason, I have an issue where in Oracle SQL Developer, there are no object names being displayed, but the objects do exist within SQLPLUS if I should query the table.
The following error message displays when I refresh any of the objects folders within SQL Developer:
ORA-00942: table or view does not exist
Any ideas would be greatly appreciated.
Thank you.

825084 wrote:
I'm pretty new to the Oracle DBA space but not to SQL Server Ah. The first thing you need to do is check everything you think you know about rdbms at the door. The similarity between SQL Server and Oracle ends right after SELECT * FROM EMP.
Even the term "database" has different meanings.
First thing I see, in your original post, is that you did the export/import as SYS. Was this "as sysdba"?
From Oracle® Database Utilities
10g Release 2 (10.2):
Invoking Export and Import As SYSDBA
SYSDBA is used internally and has specialized functions; its behavior is not the same as for generalized users. Therefore, you should not typically need to invoke Export or Import as SYSDBA, except in the following situations:
* At the request of Oracle technical support
* When importing a transportable tablespace set
so it's quite possible that I missed something during the import/export of the environments.
Are there any system tables that get invoked when you click on any of the objects within the connection?

SQLPLUS commands in SQL Developer

We are using 11g with Sql Developer. We have some script such as healthcheck etc provided by oracle support, which has SQLPLUS commands in it.
We are not able to run those in SQL Developer. We are getting errors.
Are there any way, we could invoke SQLPLUS shell within SQL Developer?
Thanks in helping.

Hi qwe16235
SQLPLUS command failed - not enough arguments
line 36: SQLPLUS Command Skipped: set lines 300
line 37: SQLPLUS Command Skipped: set pages 999
These are formatting commands we do not do yet.
The other command seems like an error in the middle of a PL/SQL block which we should have covered, just the start of it is not enough to know what the error is.
An example of bad pl/sql error reporting:
input:
show parameter error <-------------- Dummy command so the plsql block does not begin at 1
begin <----------------starting at line 3
broken plsql; <------------- bad plsql at line (start)3+(from ora error)2 = 5 (should be 4 - must be one off)
end;
output:
NAME TYPE VALUE
sec_protocol_error_further_action string CONTINUE
sec_protocol_error_trace_action string TRACE
Error starting at line 3 in command:
begin
broken plsql;
end;
Error report:
ORA-06550: line 2, column 8:
PLS-00103: Encountered the symbol "PLSQL" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "PLSQL" to continue.
06550. 00000 - "line %s, column %s:\n%s"
*Cause: Usually a PL/SQL compilation error.
*Action:
-Turloch
SQLDeveloper team

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

How can I find out what is causing this error in SQL Developer Data Modeler

Friends,
I am trying to import entities into into SQL Developer Data Modeler from Oracle Designer 10.1.2.3.
In case of need I perform these steps to perform the import:
File --> Import --> Oracle Designer Model --> Select database connection --> Select work area --> select application system --> select one entity --> Click finish --> Import starts
During the import process I see an alert dialog box with the message:
There are errors in import - check Log file Clicking Ok dismisses the alert box and I see the following summary screen:
Oracle SQL Developer Data Modeler Version: 2.0.0 Build: 584
Oracle SQL Developer Data Modeler Import Log
Date and Time: 2010-08-09 14:27:26
Design Name: erdtest
RDBMS: Oracle Database 10g
          All Statements:           32
          Imported Statements:      32
          Failed Statements:           0
          Not Recognized Statements:      0The Entity is then displayed in the Logical View within SQL Developer Data Modeler.
Upon checking the log file I see the following entry:
2010-08-09 13:50:34,025 [Thread-11] ERROR ODExtractionHandler - Error during import from Designer Repository
java.lang.NullPointerException
     at oracle.dbtools.crest.imports.oracledesigner.logical.ODORelation.createArcs(Unknown Source)
     at oracle.dbtools.crest.imports.oracledesigner.logical.ODORelation.generate(Unknown Source)
     at oracle.dbtools.crest.imports.oracledesigner.ODExtractionHandler.generateDesign(Unknown Source)
     at oracle.dbtools.crest.imports.oracledesigner.ODExtractionController$Runner.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:619)Can anyone shed any light on this error?
Thanks in advance for any help you may be able to provide.

No this helps a lot. It's not strange. Firstly, in a versioned repository you should see Private Workareas and Shared workareas, so your workarea may be in either of these. It won't be in the Global Shared Workarea, as this only for non-versioned repositories. (I like to open the RON by selecting the full Repository, that way I can see the private and shared worlareas and the configuration and containers all in the same tree.
Now your workarea is defined by a set of rules, so when you expand the workarea in the RON, and select the object, then that's the workarea and object you'll see in the import dialog in the Data Modeler. So if you check it out and check it back in, and can't see it in the RON, then the rule is not seeing this object. (Did you refresh the workarea in the RON?) If you can't see it in the RON, you can't see it in the Data Modeler. If you're working in a versioned repository, you need to work in the specific work area, i.e V27 and this is what you need to select in the Data Modeler.
It looks like you are selecting the wrong workarea in the Data Modeler.
Sue

(( SQL DEVELOPER UserName Password??? --- To Access APEX TABLES ))

How do I access APEX tables from SQL DEVELOPER?
What do I use as a USERNAME and PASSWORD--
inside SQL DEVELOPER?
Hello,
I have APEX installed on my machine.
WINDOWS 7 PROFESSIONAL 64 BIT.
I also have installed:
ORACLE XE
and
SQL DEVELOPER.
I have applications I have created in APEX
with various tables.
Question:
How can I access my APEX tables from
within SQL DEVELOPER?
What USERNAME and PASSWORD do I use?
I can do this with
HR
SQL DEVELOPER USERNAME = HR
PASSWORD = HR
This works fine.
But what about for my own APEX TABLES
I created inside my own workspace
inside APEX?
For example:
LOGIN TO APEX:
http://127.0.0.1:8080/apex/
If my
APEX WORKSPACE = DAVID_WS
SCHEMA = DAVID_SC
APEX USERNAME = DAVIDAPEX_UN
APEX PASSWORD = DAVIDAPEX_PW
LOGIN TO APEX ADMIN:
http://localhost:8080/apex/apex_admin
APEXADMIN USERNAME = DAVIDADMIN_UN
APEXADMIN PASSWORD = DAVIDADMIN_PW
So, given the above 6
NAMES and PASSWORDS above:
SQL DEVELOPER USERNAME = ????
SQL DEVELOPER PASSWORD = ????
Thanks a lot for your help!
David
Edited by: DAVID888 on Feb 3, 2011 11:53 PM

Hello david,
When you created your workspace with the below details, if the schema "DAVID_SC" was created through APEX, then you should have also specified the password as well.
APEX WORKSPACE = DAVID_WS
SCHEMA = DAVID_SC
APEX USERNAME = DAVIDAPEX_UN
APEX PASSWORD = DAVIDAPEX_PWIf you dont remember the password for "DAVID_SC", you can log on to your Oracle XE database as a "SYSTEM" user and reset the password of "DAVID_SC".
Once that is done, you can log on to SQL developer with :
username : david_sc
password : <your_new_password>
Hope it is clear and plz refer to the APEX documentation to get a better understanding of it.

Viewing the database version in SQL Developer

Hello there,
I am using SQL Developer version 1.5.0.53, and I was wondering if there is a way that I can view the database version within SQL Developer?
I know when you log on in SQL *Plus it shows it, is there anywhere in SQL Developer that it can be viewed?
Thanks,
ivalum21

There is a report.
Data Dictionary Reports -> About Your database -> Version Banner
but it is probably just quicker to select * from v$version;

Add Email Job Notification via SQL Developer

Hello,
I'm a novice in the Oracle Scheduler space and I have what is likely a novice question. However, I'm thoroughly turned around after searching and would gladly welcome some help.
I'm using SQLdeveloper to utilize Oracle Scheduler within my schema.
A procedure has been successfully created. The job which executes the procedure is also successfully configured.
Next I'd like to configure email notification for certain events.
I've found a number of posts regarding the ADD_JOB_EMAIL_NOTIFICATION procedure.
I.e., http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_sched.htm#ARPLS72277
However, I'm having trouble identifying how to get started implementing this within SQL Developer.
Can someone please help with how the ADD_JOB_EMAIL_NOTIFICATION can be implemented within SQL developer?
Another point I want to mention: in a previous prototype, I found a wizard to configure the email notification. I'm not seeing that now. Is there a wizard with SQL Developer in which this information can be configured?
Extremely grateful for any help you can provide.
Thanks - Fritz

Thank you for your response.
I'm entering that block into a SQL worksheet and it has now been accepted. I was mis-interpreting an error message which was thrown in my earlier attempts. Looks like the name of my job was problematic. I've renamed that and the add job email notification block is now being completed.
Thanks much for your help.
Also I've tried using the get_scheduler_attribute to see if an email server is already configured. However, I'm not using this correctly either. Only these attributes can be viewed through get scheduler attribute.
Scheduler Attribute
Description
default_timezone
Default time zone used by the Scheduler for repeat intervals and windows
log_history
Retention period in days for job and window logs
max_job_slave_processes
Maximum number of job slave processes that the Scheduler can start. May be NULL.
current_open_window
Name of the currently open window
event_expiry_time
Time in seconds before an event generated by the Scheduler and enqueued onto the Scheduler event queue expires. May be NULL.
Any suggestions of how to view which notifications are configured for a job?
Thanks again! Fritz

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

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

PL/SQL development with JDeveloper

We are using Toad and JDeveloper to maintain our legacy IS that count thousands of PL/SQL code object (Packages, Package Bodies, Triggers).
I'm using JDeveloper and SQL Developer in the perspective to verify if it is possible and effective to use only Oracle tools in the project.
I like to work with JDeveloper to edit pl/sql code and i like to have my code in database offline object maintained into subversion.
I'm able to compile these sources in my different platform (development system, test alpha, test beta and final testing instance directly from JDeveloper.
That's fine except JDeveloper didn't return a compile status or a list of compile errrors like in SqlDeveloper. So I need to use SqlDeveloper in parallel of JDeveloper.
This is the beginning of my problems.
SqlDeveloper may have some editor open with source code into I updated into JDeveloper (depends on the change to do, some changes a done in SqlDeveloper to correct some errors and the code is refreshed from the instance into JDeveloper, and more important changes are done in JDeveloper and compiled (loaded) in the instance) and loaded (compiled) into my instance.
When the packages tree is already displayed in SqlDeveloper, the status of the package (valid, invalid) didn't change immediately. That is normal because SqlDeveloper don't know i change it from JDeveloper. I think it check it when i click on the package or the body node. The problem is that the code is not reloaded into the editor if it is opened and i you recompile your package without refreshing all the packages list you will recompile the older version and search sometimes a long time why your package didn't compile after the changes you done in JDeveloper (mainly after 6pm and a day of developing and compiling ) !!!!
The only reason to use both JDeveloper and SqlDeveloper in this phase is the fact that JDeveloper didn't return compile status and a compile error list.
With theses features I will no more use SqlDeveloper for such developing purposes (still using it to debug, obtain object definition, customize database object for some physical properties, etc) and avoid those bad manipulations.

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

Enhancement Req: Logging of actions within SQL Developer

Similar Messages

Maybe you are looking for