Introduction Recently, I had a project to migrate data from an Oracle 10g EE database to an Oracle 9i EE database.

The data to bemigrated was real-time and required fairly large data transformation. The basic use of the migration was to keep an older production 9i database in sync with the newer 10g database for several months while applications dependant on this datawere remediated to use the new database. This paper and the accompanying presentation are based on the proof of concept(POC) we performed to prove this functionality.The POC would use Oracle streams, Change Data Capture (CDC) specifically, to capture the data. That data was thenavailable to other 10g databases but not to 9i databases. To enable us to send the data to 9i, we enqueued the captured datainto an AQ queue that was then propagated to a 9i database. Once the data was in 9i, it was a simple process to dequeue thedata and apply it.Below is the short list for setting up Change Data Capture using Oracle Streams. These steps are mostly from the docs with afew tweaks I have added. Following the setup of CDC is a discussion of using AQ to move the data from 10g to 9i. The paper concludes with a detailed discussion of creating your own manual Logical Change Record (LCR). Change Data Capture First the set up: we will use the HR account's Employee table. We'll capture all changes to the Employee table and insert theminto an audit table. I'm not necessarily saying this is the way you should audit your database but it makes a nice example.I'll also add a monitoring piece to capture process. I want to be able to see exactly what is being captured when it is beingcaptured.You will need to have sysdba access to follow along with me. Your database must also be in archivelog mode. The changesare picked up from the redo log.So, away we go!The first step is to create our streams administrator. I will follow the guidelines from the oracle docs exactly for this:Connect as sysdba: sqlplus / as sysdba Create the streams tablespace (change the name and/or location to suit): create tablespace streams_tbs datafile 'c:\temp\stream_tbs.dbf' size 25M reuse autoextend on maxsize unlimited; Create our streams administrator: create user strmadmin identified by strmadmindefault tablespace streams_tbsquota unlimited on streams_tbs; I haven't quite figured out why, but we need to grant our administrator DBA privs. I think this is a bad thing. There is probably a work around where I could do some direct grants instead but I haven't had time to track those down. grant dba to strmadmin; We also want to grant streams admin privs to the user.

BEGIN DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(grantee => 'strmadmin', grant_privileges => true); END;/ The next steps we'll run as the HR user. conn hr/hr Grant all access to the employee table to the streams admin: grant all on hr.employees to strmadmin; We also need to create the employee_audit table. Note that I am adding three columns in this table that do not exist in theemployee table. CREATE TABLE employee_audit(employee_id NUMBER(6),first_name VARCHAR2(20),last_name VARCHAR2(25),email VARCHAR2(25), phone_number VARCHAR2(20),hire_date DATE,job_id VARCHAR2(10),salary NUMBER(8,2),commission_pct NUMBER(2,2), manager_id NUMBER(6),department_id NUMBER(4),upd_date DATE,user_name VARCHAR2(30),action VARCHAR2(30)); Grant all access to the audit table to the streams admin user: grant all on hr.employee_audit to strmadmin; We connect as the streams admin user: conn strmadmin/strmadmin We can create a logging table. You would NOT want to do this in a highvolume production system. I am doing this to illustrate user defined monitoring and show how you can get inside the capture process. CREATE TABLE streams_monitor (date_and_time TIMESTAMP(6) DEFAULT systimestamp,txt_msg CLOB ); Here we create the queue. Unlike AQ, where you have to create a separate table, this step creates the queue and theunderlying ANYDATA table. BEGIN DBMS_STREAMS_ADM.SET_UP_QUEUE(queue_table => 'strmadmin.streams_queue_table',queue_name => 'strmadmin.streams_queue'); END;/ This just defines that we want to capture DML and not DDL. BEGIN DBMS_STREAMS_ADM.ADD_TABLE_RULES(table_name => 'hr.employees',streams_type => 'capture',streams_name => 'capture_emp',queue_name => 'strmadmin.streams_queue',include_dml => true,include_ddl => false,inclusion_rule => true);

END;/ Tell the capture process that we want to know who made the change: BEGINDBMS_CAPTURE_ADM.INCLUDE_EXTRA_ATTRIBUTE(capture_name => 'capture_emp',attribute_name => 'username',include => true);END;/ We also need to tell Oracle where to start our capture. Change the source_database_name to match your database. DECLAREiscn NUMBER;BEGINiscn := DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();DBMS_APPLY_ADM.S ET_TABLE_INSTANTIATION_SCN(source_object_name => 'hr.employees',source_database_name => 'ORCL',instantiation_scn => iscn);END;/ And the fun part! This is where we define our capture procedure. I'm taking this right from the docs but I'm adding a couplesteps. CREATE OR REPLACE PROCEDURE emp_dml_handler(in_any IN ANYDATA) ISlcr SYS.LCR$_ROW_RECORD;rc PLS_INTEGER;command VARCHAR2(30);old_values SYS.LCR$_ROW_LIST;BEGIN-- Access the LCR rc := in_any.GETOBJECT(lcr);-- Get the object command typecommand := lcr.GET_COMMAND_TYPE();-- I am inserting the XML equivalent of the LCR into the monitoring table.insert into streams_monitor (txt_msg) values (command ||DBMS_STREAMS.CONVERT_LCR_TO_XML(in_any) );-Set the command_type in the row LCR to INSERTlcr.SET_COMMAND_TYPE('INSERT');- Set the object_name in the row LCR to EMP_DELlcr.SET_OBJECT_NAME('EMPLOYEE_AUDIT');-- Set the new values to the old values for update and deleteIF command IN ('DELETE', 'UPDATE') THEN-- Get the old values in the row LCR old_values := lcr.GET_VALUES('old');-- Set the old values in the row LCR to the new values in the row LCR lcr.SET_VALUES('new', old_values);-- Set the old values in the row LCR to NULLlcr.SET_VALUES('old', NULL);END IF;-- Add a SYSDATE for upd_datelcr.ADD_COLUMN('new', 'UPD_DATE', ANYDATA.ConvertDate(SYSDATE));-- Add a user columnlcr.ADD_COLUMN('new', 'user_name',lcr.GET_EXTRA_ATTRIBUTE('USERNAME') );-- Add an action columnlcr.ADD_COLUMN('new', 'ACTION', ANYDATA.ConvertVarChar2(command));

-- Make the changeslcr.EXECUTE(true);commit;END;/ Create the DML handlers:

BEGINDBMS_APPLY_ADM.SET_DML_HANDLER(object_name => 'hr.employees',object_type => 'TABLE',operation_name => 'INSERT',error_handler => false,user_procedure => 'strmadmin.emp_dml_handler',apply_database_link => NULL,apply_name => NULL);END;/BEGINDBMS_APPLY_ADM.SET_DML_HANDLER(object_name => 'hr.employees',object_type => 'TABLE',operation_name => 'UPDATE',error_handler => false,user_procedure => 'strmadmin.emp_dml_handler',apply_database_link => NULL,apply_name => NULL);END;/BEGINDBMS_APPLY_ADM.SET_DML_HANDLER(object_name => 'hr.employees',object_type => 'TABLE',operation_name => 'DELETE',error_handler => false,user_procedure => 'strmadmin.emp_dml_handler',apply_database_link => NULL,apply_name => NULL);END;/ Create the apply rule. This tells streams, yet again, that we in fact do want to capture changes. The second calls tells streamswhere to put the info. Change the source_database_name to match your database. DECLAREemp_rule_name_dml VARCHAR2(30);emp_rule_name_ddl VARCHAR2(30);BEGINDBMS_STREAMS_ADM.ADD_TABLE_RULES(table_name => 'hr.employees',streams_type => 'apply',streams_name => 'apply_emp',queue_name => 'strmadmin.streams_queue',include_dml => true,include_ddl => false,source_database => 'ORCL',dml_rule_name => emp_rule_name_dml,ddl_rule_name => emp_rule_name_ddl);DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION(rule_nam e => emp_rule_name_dml,destination_queue_name => 'strmadmin.streams_queue');END;/ We don't want to stop applying changes when there is an error, so:

BEGINDBMS_APPLY_ADM.SET_PARAMETER(apply_name => 'apply_emp', parameter => 'disable_on_error', value => 'n');END;/ Turn on the apply process: BEGINDBMS_APPLY_ADM.START_APPLY(apply_name => 'apply_emp');END;/ Turn on the capture process: BEGINDBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'capture_emp');END;/ Connect as HR and make some changes to Employees. sqlplus hr/hrINSERT INTO hr.employees VALUES(207, 'JOHN', 'SMITH','JSMITH@MYCOMPANY.COM', NULL, '07-JUN-94', 'AC_ACCOUNT', 777, NULL, NULL, 110);COMMIT;UPDATE hr.employees SET salary=5999 WHERE

employee_id=206;COMMIT;DELETE FROM hr.employees WHERE employee_id=207;COMMIT; It takes a few seconds for the data to make it to the logs and then back into the system to be applied. Run this query until yousee data (remembering that it is not instantaneous): SELECT employee_id, first_name, last_name, upd_Date, actionFROM hr.employee_auditORDER BY employee_id; Then you can log back into the streams admin account: sqlplus strmadmin/strmadmin View the XML LCR that we inserted during the capture process: set long 9999set pagesize 0select * from streams_monitor; That's it! It's really not that much work to capture and apply changes using Oracle 10g. Of course, it's a little bit more work tocross database instances, but it's not that much.One of the things that amazes me is how little code is required to accomplish this. The less code I have to write, the less code I have to maintain.

BEGINDBMS_APPLY_ADM.SET_PARAMETER(apply_name => 'apply_emp', parameter => 'disable_on_error', value => 'n');END;/ Turn on the apply process: BEGINDBMS_APPLY_ADM.START_APPLY(apply_name => 'apply_emp');END;/ Turn on the capture process: BEGINDBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'capture_emp');END;/ Connect as HR and make some changes to Employees. sqlplus hr/hrINSERT INTO hr.employees VALUES(207, 'JOHN', 'SMITH','JSMITH@MYCOMPANY.COM', NULL, '07-JUN-94', 'AC_ACCOUNT', 777, NULL, NULL, 110);COMMIT;UPDATE hr.employees SET salary=5999 WHERE employee_id=206;COMMIT;DELETE FROM hr.employees WHERE employee_id=207;COMMIT; It takes a few seconds for the data to make it to the logs and then back into the system to be applied. Run this query until yousee data (remembering that it is not instantaneous): SELECT employee_id, first_name, last_name, upd_Date, actionFROM hr.employee_auditORDER BY employee_id; Then you can log back into the streams admin account:

sqlplus strmadmin/strmadmin View the XML LCR that we inserted during the capture process: set long 9999set pagesize 0select * from streams_monitor; That's it! It's really not that much work to capture and apply changes using Oracle 10g. Of course, it's a little bit more work tocross database instances, but it's not that much.One of the things that amazes me is how little code is required to accomplish this. The less code I have to write, the less code I have to maintain.

AQ 10g to 9i NOTE: Streams is not available with Oracle 10g XE. Download and install EE. If you have 1 GB or more of RAM on your PC, you can download EE and use the DBCA to run two database instances. You do not physically need two machines to getthis to work.You need two Oracle instances for this. I used a 10g instance as my source (required) and a 9i database as my target (youcould also use a 10g instance here). I called my first instance ORCL (how creative!) and I called my second instanceSECOND. It works for me!As I said, ORCL will be my source instance and SECOND will be my target instance. You should already have the CDC codefrom the last article running in ORCL. If you are not using the same names for your databases and you are not sure of theexact name of your databases (including domain), use global_name, i.e. select * from global_name;ORCL must be in archivelog mode to run CDC. SECOND does not need archivelog mode. Having two databases running ona single PC in archivelog mode can really beat up a poor IDE drive.You already created your streams admin user in ORCL so now do the same thing in SECOND. The code below is mostly thesame code that you ran on ORCL. I made a few minor changes in case you are running both instances on a single PC: sqlplus / as sysdbacreate tablespace streams_second_tbs datafile 'c:\temp\stream_2_tbs.dbf' size 25M reuse autoextend on maxsize unlimited;create user strmadmin identified by strmadmindefault tablespace streams_second_tbsquota unlimited on streams_second_tbs;grant dba to strmadmin; Connect as strmadmin. You need to create an AQ table, AQ queue and then start the queue. That's what the code below does. BEGINDBMS_AQADM.CREATE_QUEUE_TABLE(queue_table => 'lrc_emp_t',queue_payload_type => 'sys.anydata',multiple_consumers => TRUE,compatible

=> '8.1');DBMS_AQADM.CREATE_QUEUE(queue_name => 'lrc_emp_q',queue_table => 'lrc_emp_t');DBMS_AQADM.START_QUEUE (queue_name => 'lrc_emp_q');END;/ You also need to create a database link. You have to have one from ORCL to SECOND but for debugging, I like a link in both. So, while you're in SECOND, create a link: CREATE DATABASE LINK orcl.world CONNECT TO strmadminIDENTIFIED BY strmadminUSING 'orcl.world'; Log into ORCL as strmadmin and run the exact same command there. Most of the setup for this is exactly the same betweenthe two instances.

Create your link on this side also. CREATE DATABASE LINK second.world CONNECT TO strmadminIDENTIFIED BY strmadminUSING 'second.world'; Ok, now we have running queues in ORCL and SECOND. While you are logged into ORCL, you will create a propagationschedule. You DO NOT need to run this in SECOND. BEGINDBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES(table_name => 'hr.employees',streams_name => 'orcl_2_second',source_queue_name => 'strmadmin.lrc_emp_q',destination_queue_name => 'strmadmin.lrc_emp_q@second.world',include_dml => true,include_ddl => FALSE,source_database => 'orcl.world');END;/ This tells the database to take the data in the local lrc_emp_q and send it to the named destination queue.We're almost done with the propagation now. We are going to modify the EMP_DML_HANDLER (from above) so that weget an enqueue block just above the execute statement: CREATE OR REPLACE PROCEDURE emp_dml_handler(in_any IN ANYDATA) ISlcr SYS.LCR$_ROW_RECORD;rc PLS_INTEGER;command VARCHAR2(30);old_values SYS.LCR$_ROW_LIST;BEGIN-- Access the LCR rc := in_any.GETOBJECT(lcr);-- Get the object command typecommand := lcr.GET_COMMAND_TYPE();-- I am inserting the XML equivalent of the LCR into the monitoring table.insert into streams_monitor (txt_msg) values (command ||DBMS_STREAMS.CONVERT_LCR_TO_XML(in_any) );--

Set the command_type in the row LCR to INSERTlcr.SET_COMMAND_TYPE('INSERT');- Set the object_name in the row LCR to EMP_DELlcr.SET_OBJECT_NAME('EMPLOYEE_AUDIT');-- Set the new values to the old values for update and deleteIF command IN ('DELETE', 'UPDATE') THEN-- Get the old values in the row LCR old_values := lcr.GET_VALUES('old');-- Set the old values in the row LCR to the new values in the row LCR lcr.SET_VALUES('new', old_values);-- Set the old values in the row LCR to NULLlcr.SET_VALUES('old', NULL);END IF;-- Add a SYSDATE value for the timestamp columnlcr.ADD_COLUMN('new', 'UPD_DATE', ANYDATA.ConvertDate(SYSDATE));-- Add a user value for the timestamp columnlcr.ADD_COLUMN('new', 'user_name',lcr.GET_EXTRA_ATTRIBUTE('USERNAME') );-- Add an action columnlcr.ADD_COLUMN('new', 'ACTION', ANYDATA.ConvertVarChar2(command)); DECLARE enqueue_options DBMS_AQ.enqueue_options_t;message_properties DBMS_AQ.message_properties_t;message_handle RAW(16);

recipients DBMS_AQ.aq$_recipient_list_t;BEGIN recipients(1) := sys.aq$_agent( 'anydata_subscriber','strmadmin.lrc_emp_q@second.world',NULL);message_p roperties.recipient_list := recipients;DBMS_AQ.ENQUEUE( queue_name => 'strmadmin.lrc_emp_q',enqueue_options => enqueue_options,message_properties => message_properties,payload => anydata.convertObject(lcr),msgid => message_handle);EXCEPTION WHEN OTHERS THEN insert into streams_monitor (txt_msg)values ('Anydata: ' || DBMS_UTILITY.FORMAT_ERROR_STACK );END; -- Make the changeslcr.EXECUTE(true);commit;END;/ The declaration section above created some variables required for an enqueue. We created a subscriber (that's the name of theconsumer). We will use that name to dequeue the record in the SECOND instance.We then enqueued our LCR as an ANYDATA datatype.I put the exception handler there in case there are any problems with our enqueue.That's all it takes. Insert some records into the HR.employees table and commit them. Then log into strmadmin@second andselect * from the lrc_emp_t table. You should have as many records there as you inserted.There are not a lot of moving parts so there aren't many things that will go wrong. Propagation is where I have the mosttroubles. You can query DBA_PROPAGATION to see if you have any propagation errors.That's it for moving the data from 10g to 9i.

Manual Creation of an LCR This part of the paper is not required to move data from 10g to 9i. It is very handy if you need to manually create test datathough. I recently had the need to create some test datain LCR format. If you have manual control of your LCR, you can test specific data issues a lot easier.Anyway, I (and a coworker) searched the web and looked through various documentation but was not able to find a concisedescription of how to go about creating an LCR manually. So I decided to write one. NOTE: Everything below is specifically for a ROW type LCR as opposed to a DDL type LCR. The concepts would be thesame but the specificcode would change. First a little definition. An LCR format is the format of data that Oracle uses in the redo logs and is used for Oracle Streams(and probably data guard although I am guessing about that). The LCR has information about what the object is as well as theold and new values. The old and new values are exactly the same as :old and :new in a trigger.You can see the definition of the LCR format by viewingthe LCR XML Schema. http://downloadeast.oracle.com/docs/cd/B14117_01/server.101/b10727/ap_xmlsc.htmAn LCR is an object type. Actually, it is two table collections of an object type embedded within another object type. You canget the details of that from the documentation in thesupplied PL/SQL Packages and Types documentation.http://www.oracle.com/pls/db102/to_toc?pathname=appdev.102%2 Fb14258%2Ftoc.htm&remark=portal+%28Application+development%29The short story is that an LCR stored object level information (database, object_name, owner, and command type) at the toplevel. Beneath that is column and data information in a name/value pair collection.I tend to think of things like this in a relational format. If I put it in database terms, it might look something like: Figure 1 - LCR Structure Excuse the poor diagram. An artiste I am not.You can do a describe to see the methods as well as view the documentation. The important thing to note is the constructor. Normally, a constructor has the same name as the object type. In this case, they chose to name it CONSTRUCT. SQL> desc sys.lcr$_row_record METHOD------STATIC FUNCTION CONSTRUCT RETURNS LCR$_ROW_RECORDArgument Name Type In/Out Default?----------------------------- ----------------------- ------ --------SOURCE_DATABASE_NAME VARCHAR2 IN

www.odtug.com9 K a l 2 0 0

O e 7 i

D d

T o

U s

G c

Excuse the poor diagram. An artiste I am not.You can do a describe to see the methods as well as view the documentation. The important thing to note is the constructor. Normally, a constructor has the same name as the object type. In this case, they chose to name it CONSTRUCT. SQL> desc sys.lcr$_row_record METHOD------STATIC FUNCTION CONSTRUCT RETURNS LCR$_ROW_RECORDArgument Name Type In/Out Default?----------------------------- ----------------------- ------ --------SOURCE_DATABASE_NAME VARCHAR2 IN

COMMAND_TYPE VARCHAR2 INOBJECT_OWNER VARCHAR2 INOBJECT_NAME VARCHAR2 INTAG RAW IN DEFAULTTRANSACTION_ID VARCHAR2 IN DEFAULTSCN NUMBER IN DEFAULTOLD_VALUES LCR$_ROW_LIST IN DEFAULTNEW_VALUES LCR$_ROW_LIST IN DEFAULT Based on that info, populating the test LCR is relatively straight-forward.Just for your info, the type LCR$_ROW_LIST is a collection of LCR$_ROW_UNIT.

Those types are also documented in thereference guide I mentioned above. You will not want to access those directly though. You can use the builtinLCR$_ROW_RECORD methods to populate those fields.One thing to remember is that the data values that you are dealing with are sys.AnyData data types. That type has it's ownrules and deserves a blog entry all to itself.Here is a function that will create an empty LCR for you automatically for any table. Once you have the LCR you can modifythe values to suit. CREATE OR REPLACE FUNCTION create_lcr( p_table_owner IN all_tables.owner%TYPE,p_table_name IN all_tables.table_name%TYPE,p_command IN VARCHAR2 )RETURN sys.lcr$_row_record ASv_lcr sys.lcr$_row_record;v_database global_name.global_name%TYPE;BEGIN-- verify the command typeIF p_command NOT IN ('INSERT', 'UPDATE', 'DELETE')THENRETURN v_lcr;END IF;-- Get the database name-- This could be parameterized SELECT global_nameINTO v_databaseFROM global_name;-- Construct the LCR v_lcr := sys.lcr$_row_record.construct(source_database_name => v_database,command_type => p_command,object_owner => p_table_owner,object_name => p_table_name );-- You can override the values in the constructor by calling these methods v_lcr.set_command_type(p_command);v_lcr.set_object_name(p_table_name);v_lcr.s et_object_owner(p_table_owner);v_lcr.set_source_database_name(v_database);-- Loop through the columns and add new and old valuesFOR c1 IN (SELECT column_name, data_typeFROM all_tab_columnsWHERE owner = p_table_ownerAND table_name = p_table_nameORDER BY column_id )LOOP-- Create an anydata based on column data type- You would expand this for all data types

-- I'm going to keep this example fairly simpleCASE c1.data_typeWHEN 'VARCHAR2'THENv_lcr.add_column('new', c1.column_name, sys.AnyData.convertVarChar2(TO_CHAR(NULL)));v_lcr.add_column('old', c1.column_name, sys.AnyData.convertVarChar2(TO_CHAR(NULL)));WHEN 'DATE'THENv_lcr.add_column('new', c1.column_name, sys.AnyData.convertDate(TO_DATE(NULL)));v_lcr.add_column('old', c1.column_name,

sys.AnyData.convertDate(TO_DATE(NULL)));WHEN 'NUMBER'THENv_lcr.add_column('new', c1.column_name, sys.AnyData.convertNumber(TO_NUMBER(NULL)));v_lcr.add_column('old', c1.column_name, sys.AnyData.convertNumber(TO_NUMBER(NULL)));END CASE;END LOOP;RETURN v_lcr;END; To call this function and manipulate it, you might write something like the following: DECLAREv_lcr sys.lcr$_row_record;BEGIN v_lcr := create_lcr( 'HR', 'EMPLOYEES', 'INSERT' );-- Set some valuesv_lcr.set_value('new', 'first_name', sys.anyData.convertVarchar2('Lewis'));v_lcr.set_value('old', 'first_name', sys.anyData.convertVarchar2('George'));-- Display Some ValuesDBMS_OUTPUT.PUT_LINE('Database: ' || v_lcr.get_source_database_name() ||', Object Owner: ' || v_lcr.get_object_owner() ||', Object Name: ' || v_lcr.get_object_name() ||', Command: ' || v_lcr.get_command_type() );DBMS_OUTPUT.PUT_LINE('New First Name: ' || sys.anyData.accessVarchar2(v_lcr.get_value('new', 'first_name')) ||', Old First Name: ' || sys.anyData.accessVarchar2(v_lcr.get_value('old', 'first_name')) );END; The output from this is: Database: XE, Object Owner: HR, Object Name: EMPLOYEES, Command: INSERT New First Name: Lewis, Old First Name: George And that's all there is to it.Thank you for taking the time to read this paper. You can contact me in the future at lewisc@rocketmail.com or come by andread my blog, An Expert's Guide to Oracle Technology, http://blogs.ittoolbox.com/oracle/guide.