Occasionally I'll want some form of report noting file sizes of blobs in a database.
The solution is relatively simple, and I thought I'd write it up here for a place to copy syntax each time.
APEX users also have a handy table to verify this against (apex_application_files). Well, a synonym/view that ultimately maps to the core table wwv_flow_file_objects$.
It contains a doc_size
column, which is no doubt evaluated at some point during upload of (more...)
Unshared worksheets are created to have a private connection to the database. When that unshared worksheet is closed, the connection and session for it should disappear as well.
This graphic shows what should happen!
In this post I’m going to show to synchronize the remote and local repositories after an existing file in local gets modified. What I’ll do is modify the sp_test_git.pls file in our local repository and then push those changes to the remote repository (GitHub).
First, I proceed to open the sp_test_git.pls file using SQL Developer, add another dbms_output line to it and save it. The moment I save the file, the Pending Changes (more...)
In my previous post, I showed how to clone a GitHub repository using SQL Developer. In this post I’m going to show to synchronize the remote and local repositories after remote gets modified.
Here I use GitHub to commit a file called sp_test_git.pls. You can create files by clicking on the icon the red arrow is pointing to.
The content of the file is a PL/SQL procedure that prints a message.
At this (more...)
SQL Developer 4 provides an interface that allows us to interact with Git repositories. In this post, I’m going to show how to clone a GitHub (A web based hosting service for software development projects that uses the Git revision control system) repository.
First you need to sign up for a GitHub account. You can skip this step if you already have one.
Your account will give you access to public repositories that could be cloned (more...)
The PL/SQL Debugger works pretty much out of the box when used with a previous Oracle version. These are the things we needed in place before we could start debugging PL/SQL:
- A grant of the DEBUG CONNECT SESSION privilege.
- EXECUTE privilege on DBMS_DEBUG_JDWP.
- EXECUTE privilege on the stored procedure you want to debug.
- Make sure the stored procedure is “Compiled for Debug”.
Jeff Smith talks about it in this post.
But what happens when you (more...)
This, the last part of a four part tutorial goes over the movement of data using files generated by Oracle SQL Developer.
Looking at the data move scripts that we generated in an earlier part. We need to zip up the files and copy them to the SQL Server machine (more...)
In part 1
we generated the offline capture scripts to take to the SQL Server machine, unloaded the metadata, zipped it up and copied it back to out local machine. In part 2
we used SQL Developer to create a migration project and load the capture files into SQL Developer. (more...)
Ok, Now we have the files as generated and moved in part 1
, we can now start SQL Developer to load the files. Start up SQL Developer and create a connection with the following privileges: CONNECT, RESOURCE and CREATE VIEW.
When the connection is opened, right click on it (more...)
Apparently, being able to use Oracle’s SQL Developer to connect to SQL Server databases has been around for a while (via third party drivers), but I only started using it today for the first time, with SQL Developer 4 EA2 after my colleague mentioned it to me this afternoon First (more...)
I find myself installing and running mysql of different versions in different places for different reasons all the time (well often enough to do it and not remember the little things that cost time when setting up) Its with that in mind, I'm making notes for myself and you (more...)
To reverse engineer an existing database into a relational model, I used SQL Developer Data Modeler, a free data modeling and database design tool from Oracle.
I had a problem with the tool. I could not save the model. It appeared to be saved but when I reopened the . (more...)
Running lots of scripts in SQL*Plus is nice when they are working correctly. But what about when they fail? Its a pain to figure out what went wrong, unless you have a log file and even then, you have to hunt the errors down.
Well, I've had enough of that. (more...)
When you have a load of SQL*Plus scripts, they can be a pain to manage and just simply get around.
In the next version of SQL Developer, you'll be able to hold the ctrl key down and click on the file name and have it open up. This also works (more...)
decided to save a script that cleans out a couple of tables for me.
Now I have a script, how do I run it in SQL Dev? In SQL*Plus, I would run it like @clean_tables
. Two things to note there, 1, I didn't have to put the extension on the file and b, I assumed SQL*Plus was running from the directory where my file was located. If I was running the script from a different directory, I would have to use either a relative path...or something, but I digress.
I wanted to be able to run my (more...)
(First off, sorry Mike, I'm hoping this will break my writer's block...)
On Friday I was asked to look at a report that wasn't returning all of the data. Sample:
Year/Month Total Sales Total Sales (YAGO)
01/31/2013 $1,000,000 $900,000
For reference, YAGO is "Year Ago."
Notice anything funny there?
Yeah, February is missing. The (OBIEE) report has a filter on Jan, Feb and Mar of 2013. But it wasn't showing up. I confirmed via manual SQL (hah!) that there was (YAGO) data in there for February. Any ideas?
I immediately suspected one of two (more...)
This one is a quick hint for SQL Developer and the COLLECT function.
In case you're not familiar with it, COLLECT
is an aggregate function that was introduced in 10gR2 and simply gathers all the items up into a VARRAY/TABLE style collection type. If you use it in PL/SQL programs, you can handle the collection programmatically.
But sometimes it can be handy to see the elements in a quick ad-hoc query.
In SQL*Plus, you'll get an output that is ugly, but usable:SQL> l 1 select country_id, collect(city) 2 from hr.locations 3* group by country_idSQL> (more...)
Ok, Finally, we have got to part 3 of Application Migration. In Part 1
, we outlined a program which runs in Sybase through iSQL. We then followed this, in part 2
with 2 important pieces.
- Recognizers to identify the file types of the source we post
- Rules to identify items within the files and report on the them
In this part, We will take the rules we used for the previous part, and add some replacement rules. So, lets recap. Our recogniser is set for shell files as below.
<?xml version="1.0" encoding="UTF-8"?>
<rulesfile version="1.0" name="Shell (more...)