I was working through a bug the other day and using SQL*Plus, which for the most part doesn't annoy me too much. However, one of the things that does, is having to retype lots of stuff. (We dont have that problem in SQL Developer).
Having hunted around for a few minutes, I found rlwrap which is a GNU readline wrapper. All this means is that when we use it on SQL*Plus, it give us keyboard history and user defined completion. I've found a few posts about it too, which are referred to below, but I wanted to do this for our (more...)
For those of you who end up using the Oracle Developers Day VM for more that just demo's but playing with other things too, will find that at some point, you'll need more space. (Like I did) Today's post is about just that. We're going to add a new VMDK drive to our virtual machine and configure it so its available to you in the machine.
First thing we want to do is to have a list of the devices in your linux box. This will save you searching for it once you add it later.
[oracle@localhost ~]$ cd (more...)
The DBMS_SQLTUNE package is the interface for tuning SQL on demand. Its Doc pages are here
. Have a look. There is a lot of stuff to do to set a tuning task, run it, report on it and then get it to do something useful. We've wrapped all that into our SQL Tuning Advisor function which means you dont need to start writing plsql API calls to make this work. Stick in your dodgy query, click the advisor button and visualize the results.
Here's a look at how to do this. Firstly, we need to grant a few permissions to our user. I'm doing (more...)
One of the features exposed since SQL Developer 1.5 is the hierarchical profiler. There have been several blogs and things about this but none I think that really get into the detail of what you are seeing and how to do it.
The hierarchical profiler allows you to see what happens when your piece of PL/SQL is running. More specifically, it allows you to see where it is spending most of its time, which means you can concentrate on hammering that down, rather than wondering where to start.
For today, I'm using a really basic reference table with a few rows (more...)
As part of the development process, we all have to work out the bugs in our code. For all of us who use SQLDeveloper , we know how to debug with SQL Developer. Compile for Debug, breakpoint and go. However, People still get confused by what remote debugging is and how it works. At its most basic, it allows us to run a procedure in a session and debug if from another.
So, Lets say we have a simple procedure on employees table like this.
create or replace
ID IN NUMBER
) RETURN VARCHAR2 AS