# Using native Db2 tools to migrate data from Db2 to Amazon RDS for Db2
You can use several native Db2 tools, utilities, and commands to move data directly from a Db2 database to an Amazon RDS for Db2 database. To use these native Db2 tools, you must be able to connect your client machine to an RDS for Db2 DB instance. For more information, see [Connecting a client machine to an Amazon RDS for Db2 DB instance](db2-connecting-client-rds.md).
**Note**
Another way to move your data is to first save it to an Amazon S3 bucket, and then use the `LOAD` command to transfer that data into a table in your RDS for Db2 database. This method provides the best performance when migrating a large amount of data because of good network connectivity between RDS for Db2 and S3. For more information, see [Migrating Db2 data through Amazon S3 to Amazon RDS for Db2](db2-migration-load-from-s3.md).
| Tool name | Use case | Limitations |
| --- | --- | --- |
| [db2look](db2-native-db2-tools-db2look.md) | Copying metadata from a self-managed Db2 database to an RDS for Db2 database. | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-native-db2-tools.html) |
| [IMPORT command](db2-native-db2-tools-import.md) | Migrating small tables and tables with large objects (LOBs) from a client machine to the RDS for Db2 DB instance. | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-native-db2-tools.html) |
| [INGEST utility](db2-native-db2-tools-ingest.md) | Continually streaming data from files and pipes *without* large objects (LOBs) on the client machine to the RDS for Db2 DB instance. Supports `INSERT` and `MERGE` operations. | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-native-db2-tools.html) |
| [INSERT command](db2-native-db2-tools-insert.md) | Copying data in small tables from a self-managed Db2 database to an RDS for Db2 database. | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-native-db2-tools.html) |
| [LOAD CLIENT command](db2-native-db2-tools-load.md) | Migrating small tables *without *large objects (LOBs) from a client machine to the RDS for Db2 DB instance. | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/db2-native-db2-tools.html) |
# Connecting a client machine to an Amazon RDS for Db2 DB instance
To use any of the native Db2 tools to move data from a Db2 database to an Amazon RDS for Db2 database, you must first connect your client machine to an RDS for Db2 DB instance.
The client machine can be any of the following:
+ An Amazon Elastic Compute Cloud (Amazon EC2) instance on Linux, Windows, or macOS. This instance should be in the same virtual private cloud (VPC) as your RDS for Db2 DB instance, AWS Cloud9, or AWS CloudShell.
+ A self-managed Db2 instance in an Amazon EC2 instance. The instances should be in the same VPC.
+ A self-managed Db2 instance in an Amazon EC2 instance. The instances can be in different VPCs if you enabled VPC peering. For more information, see [Create a VPC peering connection](https://docs.aws.amazon.com/vpc/latest/peering/create-vpc-peering-connection.html) in the *Amazon Virtual Private Cloud VPC Peering Guide*.
+ A local machine running Linux, Windows, or macOS in a self-managed environment. You must either have public connectivity to RDS for Db2 or enable VPN connectivity between self-managed Db2 instances and AWS.
To connect your client machine to your RDS for Db2 DB instance, log in to your client machine with IBM Db2 Data Management Console. For more information, see [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md) and [IBM Db2 Data Management Console](db2-connecting-with-ibm-data-management-console.md).
You can use AWS Database Migration Service (AWS DMS) to run queries against the database, run an SQL execution plan, and monitor the database. For more information, see [What is AWS Database Migration Service?](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html) in the *AWS Database Migration Service User Guide*.
After you successfully connect your client machine to your RDS for Db2 DB instance, you are ready to use any native Db2 tool to copy data. For more information, see [Using native Db2 tools to migrate data from Db2 to Amazon RDS for Db2](db2-native-db2-tools.md).
# Copying database metadata from Db2 to Amazon RDS for Db2 with db2look
`db2look` is a native Db2 tool that extracts data definition language (DDL) files, objects, authorizations, configurations, WLM, and database layouts. You can use `db2look` to copy database metadata from a self-managed Db2 database to an Amazon RDS for Db2 database. For more information, see [Mimicking databases using db2look](https://www.ibm.com/docs/en/db2/11.5?topic=tools-db2look) in the IBM Db2 documentation.
**To copy the database metadata**
1. Run the `db2look` tool on your self-managed Db2 system to extract the DDL file. In the following example, replace *database\$1name* with the name of your Db2 database.
```
db2look -d database_name -e -l -a -f -wlm -cor -createdb -printdbcfg -o db2look.sql
```
1. If your client machine has access to the source (self-managed Db2) database and the RDS for Db2 DB instance, you can create the `db2look.sql` file on the client machine by directly attaching to the remote instance. Then catalog the remote self-managed Db2 instance.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the self-managed Db2 database.
```
db2 catalog tcpip node srcnode REMOTE dns_ip_address server port
```
1. Catalog the database. In the following example, replace *source\$1database\$1name* and *source\$1database\$1alias* with the name of the self-managed Db2 database and the alias that you want to use for this database.
```
db2 catalog database source_database_name as source_database_alias at node srcnode \
authentication server_encrypt
```
1. Attach to the source database. In the following example, replace *source\$1database\$1alias*, *user\$1id*, and *user\$1password* with the alias that you created in the previous step and the user ID and password for the self-managed Db2 database.
```
db2look -d source_database_alias -i user_id -w user_password -e -l -a -f -wlm \
-cor -createdb -printdbcfg -o db2look.sql
```
1. If you can't access the remote self-managed Db2 database from the client machine, copy the `db2look.sql` file to the client machine. Then catalog the RDS for Db2 DB instance.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the RDS for Db2 DB instance.
```
db2 catalog tcpip node remnode REMOTE dns_ip_address server port
```
1. Catalog the database. In the following example, replace *rds\$1database\$1name* and *rds\$1database\$1alias* with the name of the RDS for Db2 database and the alias that you want to use for this database.
```
db2 catalog database rds_database_name as rds_database_alias at node remnode \
authentication server_encrypt
```
1. Catalog the admin database that manages RDS for Db2. You can't use this database to store any data.
```
db2 catalog database rdsadmin as rdsadmin at node remnode authentication server_encrypt
```
1. Create buffer pools and tablespaces. The administrator doesn't have privileges to create buffer pools or tablespaces. However, you can use Amazon RDS stored procedures to create them.
1. Find the names and definitions of the buffer pools and tablespaces in the `db2look.sql` file.
1. Connect to Amazon RDS using the master username and master password for your RDS for Db2 DB instance. In the following example, replace *master\$1username* and *master\$1password* with your own information.
```
db2 connect to rdsadmin user master_username using master_password
```
1. Create a buffer pool by calling `rdsadmin.create_bufferpool`. For more information, see [rdsadmin.create\$1bufferpool](db2-sp-managing-buffer-pools.md#db2-sp-create-buffer-pool).
```
db2 "call rdsadmin.create_bufferpool(
'database_name',
'buffer_pool_name',
buffer_pool_size,
'immediate',
'automatic',
page_size,
number_block_pages,
block_size)"
```
1. Create a tablespace by calling `rdsadmin.create_tablespace`. For more information, see [rdsadmin.create\$1tablespace](db2-sp-managing-tablespaces.md#db2-sp-create-tablespace).
```
db2 "call rdsadmin.create_tablespace(
'database_name',
'tablespace_name',
'buffer_pool_name',
tablespace_initial_size,
tablespace_increase_size,
'tablespace_type')"
```
1. Repeat steps c or d for each additional buffer pool or tablespace that you want to add.
1. Terminate your connection.
```
db2 terminate
```
1. Create tables and objects.
1. Connect to your RDS for Db2 database using the master username and master password for your RDS for Db2 DB instance. In the following example, replace *rds\$1database\$1name*, *master\$1username*, and *master\$1password* with your own information.
```
db2 connect to rds_database_name user master_username using master_password
```
1. Run the `db2look.sql` file.
```
db2 -tvf db2look.sql
```
1. Terminate your connection.
```
db2 terminate
```
# Importing data from a client machine to Amazon RDS for Db2 with the IMPORT command
You can use the `IMPORT` command from a client machine to import your data into the Amazon RDS for Db2 server.
**Important**
The `IMPORT` command method is useful for migrating small tables and tables that include large objects (LOBs). The `IMPORT` command is slower than the `LOAD` utility because of the `INSERT` and `DELETE` logging operations. If your network bandwidth between the client machine and RDS for Db2 is limited, we recommend that you use a different migration approach. For more information, see [Using native Db2 tools to migrate data from Db2 to Amazon RDS for Db2](db2-native-db2-tools.md).
**To import data into the RDS for Db2 server**
1. Log in to your client machine with IBM Db2 Data Management Console. For more information, see [Connecting to your Amazon RDS for Db2 DB instance with IBM Db2 Data Management Console](db2-connecting-with-ibm-data-management-console.md).
1. Catalog the RDS for Db2 database on the client machine.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the self-managed Db2 database.
```
db2 catalog tcpip node srcnode REMOTE dns_ip_address server port
```
1. Catalog the database. In the following example, replace *source\$1database\$1name* and *source\$1database\$1alias* with the name of the self-managed Db2 database and the alias that you want to use for this database.
```
db2 catalog database source_database_name as source_database_alias at node srcnode \
authentication server_encrypt
```
1. Attach to the source database. In the following example, replace *source\$1database\$1alias*, *user\$1id*, and *user\$1password* with the alias you created in the previous step and the user ID and password for the self-managed Db2 database.
```
db2look -d source_database_alias -i user_id -w user_password -e -l -a -f -wlm \
-cor -createdb -printdbcfg -o db2look.sql
```
1. Generate the data file by using the` EXPORT` command on your self-managed Db2 system. In the following example, replace *directory* with the directory on your client machine where your data file exists. Replace *file\$1name* and *table\$1name* with the name of the data file and the name of the table.
```
db2 "export to /directory/file_name.txt of del lobs to /directory/lobs/ \
modified by coldel\| select * from table_name"
```
1. Connect to your RDS for Db2 database using the master username and master password for your RDS for Db2 DB instance. In the following example, replace **rds\$1database\$1alias**, *master\$1username,* and *master\$1password* with your own information.
```
db2 connect to rds_database_alias user master_username using master_password
```
1. Use the `IMPORT` command to import data from a file on the client machine into the remote RDS for Db2 database. For more information, see [IMPORT command](https://www.ibm.com/docs/en/db2/11.5?topic=commands-import) in the IBM Db2 documentation. In the following example, replace *directory* and *file\$1name* with the directory on your client machine where your data file exists and the name of the data file. Replace *SCHEMA\$1NAME* and *TABLE\$1NAME* with the name of your schema and table.
```
db2 "IMPORT from /directory/file_name.tbl OF DEL LOBS FROM /directory/lobs/ \
modified by coldel\| replace into SCHEMA_NAME.TABLE_NAME"
```
1. Terminate your connection.
```
db2 terminate
```
# Importing data from a client machine to Amazon RDS for Db2 with the LOAD command
You can use the `LOAD CLIENT` command to load data from a file on a client machine to the RDS for Db2 server. Because no SSH connectivity exists to the RDS for Db2 server, you can use the `LOAD CLIENT` command on either your self-managed Db2 server or your Db2 client machine.
**Important**
The `LOAD CLIENT` command method is useful for migrating small tables. If your network bandwidth between the client and RDS for Db2 is limited, we recommend that you use a different migration approach. For more information, see the [Using native Db2 tools to migrate data from Db2 to Amazon RDS for Db2](db2-native-db2-tools.md).
If your data file includes references to large object file names, then the `LOAD` command won't work because large objects (LOBs) need to reside on the Db2 server. If you try to load LOBs from the client machine to the RDS for Db2 server, you will receive an SQL3025N error. Use the [IMPORT command](db2-native-db2-tools-import.md) instead.
**To load data to the RDS for Db2 server**
1. Log in to your client machine with IBM Db2 Data Management Console. For more information, see [Connecting to your Amazon RDS for Db2 DB instance with IBM Db2 Data Management Console](db2-connecting-with-ibm-data-management-console.md).
1. Catalog the RDS for Db2 database on the client machine.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the self-managed Db2 database.
```
db2 catalog tcpip node srcnode REMOTE dns_ip_address server port
```
1. Catalog the database. In the following example, replace *source\$1database\$1name* and *source\$1database\$1alias* with the name of the self-managed Db2 database and the alias that you want to use for this database.
```
db2 catalog database source_database_name as source_database_alias at node srcnode \
authentication server_encrypt
```
1. Attach to the source database. In the following example, replace *source\$1database\$1alias*, *user\$1id*, and *user\$1password* with the alias you that created in the previous step and the user ID and password for the self-managed Db2 database.
```
db2look -d source_database_alias -i user_id -w user_password -e -l -a -f -wlm \
-cor -createdb -printdbcfg -o db2look.sql
```
1. Generate the data file by using the `EXPORT` command on your self-managed Db2 system. In the following example, replace *directory* with the directory on your client machine where your data file exists. Replace *file\$1name* and *TABLE\$1NAME* with the name of the data file and the name of the table.
```
db2 "export to /directory/file_name.txt of del modified by coldel\| \
select * from TPCH.TABLE_NAME"
```
1. Connect to your RDS for Db2 database using the master username and master password for your RDS for Db2 DB instance. In the following example, replace **rds\$1database\$1alias**, *master\$1username*, and *master\$1password* with your own information.
```
db2 connect to rds_database_alias user master_username using master_password
```
1. Use the `LOAD` command to load data from a file on the client machine to the remote RDS for Db2 database. For more information, see [LOAD command](https://www.ibm.com/docs/en/db2/11.5?topic=commands-load) in the IBM Db2 documentation. In the following example, replace *directory* with the directory on your client machine where your data file exists. Replace *file\$1name* and *TABLE\$1NAME* with the name of the data file and the name of the table.
```
db2 "LOAD CLIENT from /directory/file_name.txt \
modified by coldel\| replace into TPCH.TABLE_NAME \
nonrecoverable without prompting"
```
1. Terminate your connection.
```
db2 terminate
```
# Importing data from Db2 to Amazon RDS for Db2 with the INSERT command
You can use the `INSERT` command from a self-managed Db2 server to insert your data into an Amazon RDS for Db2 database. With this migration approach, you use a nickname for the remote RDS for Db2 DB instance. Your self-managed Db2 database (source) must be able to connect to the RDS for Db2 database (target).
**Important**
The `INSERT` command method is useful for migrating small tables. If your network bandwidth between your self-managed Db2 database and RDS for Db2 database is limited, we recommend that you use a different migration approach. For more information, see [Using native Db2 tools to migrate data from Db2 to Amazon RDS for Db2](db2-native-db2-tools.md).
**To copy data from a self-managed Db2 database to an RDS for Db2 database**
1. Catalog the RDS for Db2 DB instance on the self-managed Db2 instance.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the self-managed Db2 database.
```
db2 catalog tcpip node remnode REMOTE dns_ip_address SERVER port
```
1. Catalog the database. In the following example, replace *rds\$1database\$1name* with the name of the database on your RDS for Db2 DB instance.
```
db2 catalog database rds_database_name as remdb at node remnode \
authentication server_encrypt
```
1. Enable federation on the self-managed Db2 instance. In the following example, replace *source\$1database\$1name* with the name of your database on the self-managed Db2 instance.
```
db2 update dbm cfg using FEDERATED YES source_database_name
```
1. Create tables on the RDS for Db2 DB instance.
1. Catalog the node. In the following example, replace *dns\$1ip\$1address* and *port* with the DNS name or the IP address and the port number of the self-managed Db2 database.
```
db2 catalog tcpip node srcnode REMOTE dns_ip_address server port
```
1. Catalog the database. In the following example, replace *source\$1database\$1name* and *source\$1database\$1alias* with the name of the self-managed Db2 database and the alias that you want to use for this database.
```
db2 catalog database source_database_name as source_database_alias at node srcnode \
authentication server_encrypt
```
1. Attach to the source database. In the following example, replace *source\$1database\$1alias*, *user\$1id*, and *user\$1password* with the alias that you created in the previous step and the user ID and password for the self-managed Db2 database.
```
db2look -d source_database_alias -i user_id -w user_password -e -l -a -f -wlm \
-cor -createdb -printdbcfg -o db2look.sql
```
1. Set up federation, and create a nickname for the RDS for Db2 database table on the self-managed Db2 instance.
1. Connect to your local database. In the following example, replace *source\$1database\$1name* with the name of the database on your self-managed Db2 instance.
```
db2 connect to source_database_name
```
1. Create a wrapper to access Db2 data sources.
```
db2 create wrapper drda
```
1. Define a data source on a federated database. In the following example, replace *admin* and *admin\$1password* with your credentials for your self-managed Db2 instance. Replace *rds\$1database\$1name* with the name of the database on your RDS for Db2 DB instance.
```
db2 "create server rdsdb2 type DB2/LUW version '11.5.9.0' \
wrapper drda authorization "admin" password "admin_password" \
options( dbname 'rds_database_name', node 'remnode')"
```
1. Map the users on the two databases. In the following example, replace *master\$1username* and *master\$1password* with your credentials for your RDS for Db2 DB instance.
```
db2 "create user mapping for user server rdsdb2 \
options (REMOTE_AUTHID 'master_username', REMOTE_PASSWORD 'master_password')"
```
1. Verify the connection to the RDS for Db2 server.
```
db2 set passthru rdsdb2
```
1. Create a nickname for the table in the remote RDS for Db2 database. In the following example, replace *NICKNAME* and *TABLE\$1NAME* with a nickname for the table and the name of the table.
```
db2 create nickname REMOTE.NICKNAME for RDSDB2.TABLE_NAME.NICKNAME
```
1. Insert data into the table in the remote RDS for Db2 database. Use the nickname in a `select` statement on the local table in the self-managed Db2 instance. In the following example, replace *NICKNAME* and *TABLE\$1NAME* with a nickname for the table and the name of the table.
```
db2 "INSERT into REMOTE.NICKNAME select * from RDS2DB2.TABLE_NAME.NICKNAME"
```
# Importing data from Db2 to Amazon RDS for Db2 with the INGEST utility
You can use the `INGEST` utility to continually stream data from files and pipes on a client machine to a target Amazon RDS for Db2 DB instance. The `INGEST` utility supports `INSERT` and `MERGE` operations. For more information, see [Ingest utility](https://www.ibm.com/docs/en/db2/11.1?topic=reference-ingest-utility) in the IBM Db2 documentation.
Because the `INGEST` utility supports nicknames, you can use the utility to transfer data from your self-managed Db2 database to an RDS for Db2 database. This approach works as long as network connectivity exists between the two databases.
**Important**
The `INGEST` utility doesn't support large objects (LOBs). Use the [`IMPORT` command](db2-native-db2-tools-import.md) instead.
To use the `RESTARTABLE` feature of the `INGEST` utility, run the following command on the RDS for Db2 database.
```
db2 "call sysproc.sysinstallobjects(‘INGEST’,‘C’,NULL,NULL)"
```