Well, I’ve been using SQL Developer for about three weeks now. When SQL Developer was first released a few years ago, I was not a big fan of this free tool. I’m still not a big fan at this point, but I will say that the tool is growing on me everytime I use it. What I’m finding interesting about it at this time is how it deals with RAW datatypes. When you select a RAW column from a table all you get in the column is (RAW) in the column.
select job_id, job_name, job_owner, job_description, job_type
where rownum < 4
JOB_ID JOB_NAME JOB_OWNER JOB_DESCRIPTION JOB_TYPE
(RAW) LOAD USER_QUEUE DATATEAM SQLScript
(RAW) LOAD SDA DSUMMS DATATEAM SQLScript
(RAW) UPDATE PROCESS_TIMESTAMP DATATEAM SQLScript
As you can see if you are trying to find a job_id for one of the listed jobs it is difficult from SQL Developer. Now, from TOAD this issue is not relative; however, I’ve decided to use SQL Developer recently since I cannot get the company to purchase new TOAD licenses. What can you do when you are pretty much told that the company doesn’t like Quest due to pricing issues.
So the solution to gettting around this issue is to covert the column to hex using the RAWTOHEX() function. To do this I modified the query to allow the job_id column to displace the relative information that I was looking for.
select rawtohex(job_id), job_name, job_owner, job_description, job_typefrom sysman.mgmt_job
where rownum < 4
(for simplicity reason only used the first two columns)
4883A26B1F5806A2E0400A0A4A020878 LOAD USER_QUEUE
4883A26B1F6306A2E0400A0A4A020878 LOAD SDA DSUMMS
4883A26B1F6A06A2E0400A0A4A020878 UPDATE PROCESS_TIMESTAMP
Hope this helps.
Another good post for issues with RAW datatypes and PL/SQL see http://thinkoracle.blogspot.com/2005/11/raw-datatype.html