Categories
- Databases (12)
- MySQL (8)
- Oracle (4)
- PostgreSQL (3)
- SQL Server (3)
- SQLite (1)
- General Info (8)
- Hardware (7)
- Hosted 64-bit Software (22)
- Lightning Plug-In (3)
- Xine RPMs (20)
- Linux (22)
- Audio / Video (3)
- Internet Apps (11)
- Office Productivity (4)
- Printing (1)
- Red Hat / Fedora (3)
- Samba (1)
- White Box (3)
- Wine (5)
- Wireless Support (8)
- Programming (26)
- C# / .NET (4)
- Mono (2)
- C++ (1)
- JavaScript (1)
- PHP (9)
- SQL (3)
- PL/SQL (1)
- Web Services (1)
- WordPress (13)
- Plug-Ins (7)
- C# / .NET (4)
- Projects (1)
- Security (3)
- Web Servers (6)
- Windows Open Source (1)
- Databases (12)
Archives
- January 2012 (1)
- November 2011 (1)
- October 2011 (2)
- September 2011 (1)
- August 2011 (1)
- May 2011 (1)
- September 2010 (2)
- August 2010 (3)
- March 2010 (1)
- April 2009 (1)
- February 2009 (1)
- January 2009 (1)
- October 2008 (2)
- June 2008 (3)
- May 2008 (1)
- March 2008 (4)
- January 2008 (2)
- December 2007 (2)
- November 2007 (1)
- October 2007 (1)
- September 2007 (2)
- August 2007 (5)
- July 2007 (2)
- June 2007 (2)
- May 2007 (3)
- November 2005 (1)
- August 2005 (2)
- June 2005 (3)
- September 2004 (7)
- August 2004 (2)
- July 2004 (8)
- June 2004 (10)
Category Archive: Oracle
Subcategories: No categories
Oracle SQL Developer 2.1 Debian Package
It had been a while since I had updated SQL Developer. It turns out that version 2.1 was released March 1st of this year. I’ve downloaded it and created a Debian package. It can be downloaded from the DJS Consulting Linux Software Repository.
I’ve used it with Sun’s Java 6 Update 18; I have not tested it with OpenJDK. If you have problems getting it to work, you may want to check the previous post on this topic.
Tagged deb, oracle, sql developer
Oracle SQL Developer Debian Package
Oracle SQL Developer is a Java-based tool that provides a graphical interface to a database. While it’s main focus is Oracle (of course), it can be hooked up, via JDBC, to many other databases, such as MySQL, PostgreSQL, and SQL Server. It’s similar to Toad, but is provided by Oracle at no cost.
Oracle provides SQL Developer in either an RPM, or a generic binary install. I like the ability to manage packages, but I’ve never had much luck at getting RPM to run on Ubuntu. I downloaded the RPM file, and, using alien, I converted the package to a .deb package (Debian package format) and installed it. It worked like a charm!
I haven’t tested it with gcj, but using Sun’s Java 6 update 7 from the Ubuntu repositories, it ran just fine. After you install the package, do a directory list on /usr/lib/jvm. You’re looking for the Sun JDK – if it’s installed, you’ll have a symlink java-6-sun that points to java-6-sun-1.6.0.07. Once you’ve determined the location of the JDK, run “sqldeveloper” from the command line – the program will prompt you for the path to your JDK. Enter it (probably “/usr/lib/jvm/java-6-sun”) and you’re good to go. (You have to install the package as root – but, for the rest of these steps, use your normal user, not root, as this puts settings in a .sqldeveloper directory off your home directory.) The package installs an icon in the “Programming” or “Development” group. Once you’ve told it where the JDK is, you can use this to launch it.
Transferring Data Between Oracle and SQL Server
There are lots of “how to” articles on sharing data between Oracle and SQL Server. Most of these involve installing Oracle’s code base on the SQL Server machine, then using that instance to link tables within Oracle. This technique does not require that, thanks to a product from Oracle called Oracle Instant Client.
To set up the Oracle piece, download the packages for “Basic” and “ODBC Supplement”, and follow the instructions for installation, on the machine with SQL Server. (This is not an “install” per se – it’s basically an unzip.) Next, you’ll need to provide a TNSNAMES.ORA file – this can be any valid file, including a simple shell with an “ifile=” statement pointing to a common TNSNAMES.ORA file. Finally, set the environment variable TNS_ADMIN to point to the directory where this TNSNAMES.ORA file resides.
Now, you can easily create a DTS script through SQL Server to push or pull data however you’d like. Oracle Instant Client will appear in the drop-down list of providers, and you’ll be able to specify your connection the way you normally do (i.e., “DB01.WORLD”).
Happy migrating!
Tagged data, dts, instant client, oracle, sql server
Transferring CLOBs Across Linked Oracle Databases
Linking databases in Oracle make it easy to share data, and can be useful for replication. However, there is a limitation in Oracle that prevents Character Large Objects (CLOBs) from coming across these links. The following technique uses stored procedures and a temporary table to pull CLOBs across a database link.
First, you’ll need the temporary table, which will hold a sequence number, the primary key for the table where you’ll want to reconstruct the CLOB, and some text. This table can reside in the source or destination database, but must be linked from the other one. For our purposes, it looks like this…
1 2 3 4 5 6 7 8 9 10 11 | CREATE TABLE clob_xfer_area ( cxa_pk NUMBER(12), cxa_number NUMBER(12), cxa_text varchar2(4000 byte) ); ALTER TABLE clob_xfer_area ADD ( CONSTRAINT pk_cxa_id PRIMARY KEY (cxa_pk, cxa_number) ); |
Second, you’ll need the procedure in the source database that breaks the CLOB apart and populates the temporary table.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 | SET serveroutput ON SIZE 1000000 SET LINES 1000 SET pages 0 SET tab off SET feedback ON CREATE OR REPLACE PROCEDURE break_clobs_apart IS v_line_number NUMBER(3); v_text_piece varchar2(4000); v_total_length NUMBER(12); cursor clob_cur IS SELECT twc_pk, twc_clob_field FROM table_with_clob; BEGIN /* { */ FOR clob_rec IN clob_cur loop /* { */ v_total_length := 1; v_line_number := 0; while (v_total_length <= DBMS_LOB.GETLENGTH(clob_rec.twc_clob_field)) loop /* { */ v_line_number := v_line_number + 1; v_text_piece := DBMS_LOB.SUBSTR(clob_rec.twc_clob_field, 3999, v_total_length); v_total_length := v_total_length + 3999; INSERT INTO clob_xfer_area ( cxa_pk, cxa_number, cxa_text ) VALUES ( clob_rec.twc_pk, -- cxa_pk v_line_number, -- cxa_number v_text_piece -- cxa_text ); END loop; /* } of while */ END loop; /* } of clob_cur */ END; /* } of procedure break_clobs_apart */ |
Third, you’ll need a procedure in the destination database that puts the CLOB back together, and deletes the data from the temporary table.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 | SET serveroutput ON SIZE 1000000 SET LINES 1000 SET pages 0 SET feedback ON SET tab off CREATE OR REPLACE PROCEDURE put_clobs_together IS v_new_clob CLOB; cursor pk_cur IS SELECT DISTINCT cxa_pk FROM clob_xfer_area; cursor piece_cur(p_cxa_pk NUMBER) IS SELECT cxa_text FROM clob_xfer_area WHERE cxa_pk = p_cxa_pk ORDER BY cxa_number; BEGIN /* { */ FOR pk_rec IN pk_cur loop /* { */ DBMS_LOB.CREATETEMPORARY(v_new_clob, TRUE); DBMS_LOB.OPEN(v_new_clob, DBMS_LOB.LOB_READWRITE); FOR piece_rec IN piece_cur(pk_rec.cxa_pk) loop /* { */ DBMS_LOB.WRITEAPPEND(v_new_clob, LENGTH(piece_rec.cxa_text), piece_rec.cxa_text); END loop; /* } of piece_cur */ DBMS_LOB.CLOSE(v_new_clob); UPDATE dest_table_with_clob SET migrated_clob = v_new_clob WHERE dtwc_pk = pk_rec.cxa_pk; END loop; /* } of pk_cur */ DELETE FROM clob_xfer_area; END; /* } of procedure put_clobs_together */ |
Finally, you’ll need a procedure that controls the whole thing. We’ll assume that this procedure is loaded in the destination database, and the source database is linked with the name “source”.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | SET LINES 1000 SET pages 0 SET feedback ON SET tab off CREATE OR REPLACE PROCEDURE xfer_clobs IS BEGIN /* { */ break_clobs_apart@SOURCE; put_clobs_together; END; /* } */ |
(This does not include a commit – the changes will not be persistent unless they are committed.)
Of course, these processes could (and, to be useful, likely would) be integrated into other procedures and scripts. But, this framework will successfully transfer CLOBs across linked databases in Oracle.
Tagged algorithm, clob, data, linked database, oracle