Database Backup Conversion

Abstract

This hint and tip focuses on the technical considerations and methodology involved in performing Oracle to DB2 UDB database conversion. It provides information about the different data types and the implementation of features such as DML, DDL, stored procedures, and triggers. Application programming and conversion considerations are discussed along with the differences in features and functionality of the two products. We also discuss migration tools, addressing the areas tools can and cannot convert automatically, and we provide solution and workarounds for those areas that tools cannot.

Contents

Back up database to tape

In DB2 UDB, you can back up a database directly to tape. Oracle supports backing up database directly to Oracle using media manager in RMAN (Recovery Manager) to take backups directly in tapes. The media management libraries are installed on host machines and RMAN directly communicates with media management to perform the backup.

An example of a RMAN command to allocate the channel using media manager and for taking backup is:

RUN
{
ALLOCATE CHANNEL c1 DEVICE TYPE sbt
PARMS='ENV=(NSR_SERVER=tape_srv,NSR_GROUP=oracle_tapes)';
BACKUP DATAFILE 1;
}

The equivalent of using a TSM in DB2 is:
db2 backup database database_name uses TSM to open two sessions with four buffers.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Profile

Publish Date
14 December 2003


Rating: Not yet rated


Author(s)

IBM Form Number
TIPS0338