how to collect database data using online collection or a collector - Data Transmission Service

Advanced Database & Application Migration (ADAM) provides two methods for collecting database information: online collection and collector-based collection. You can choose a method based on whether the source database is accessible from the cloud.

Introduction to collection methods

Online collection: For online collection, you must ensure that the source database is network-accessible and add the ADAM server IP addresses to the database whitelist. This configuration allows ADAM to collect information directly. For more information, see Online collection.
- With a public IP address: The source database has a public IP address and can be accessed over the Internet.
- Without a public IP address: You can connect through Database Gateway (DG). DG is a database connection service that supports remote access to databases in a private network. DG lets you access and manage databases in your on-premises data center or on other cloud platforms without a public IP address. For more information, see What is Database Gateway?.
  Note
  ADAM currently supports DG instances in the China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Hangzhou), and China (Shanghai) regions.
Collector-based collection: If the source database cannot be accessed over the Internet or from the cloud, you can use the ADAM Database Collector. For more information, see Collector-based collection.

Online collection

Log on to the Data Management (DMS) 5.0 console.
In the top menu bar, choose Data + AI > Heterogeneous Database Migration (ADAM) > Database Evaluation.
On the Database Information Collection tab, click Online Database Collection.
Click Create Collection Task to create a collection task.

Log on to the source database to configure a collection account and grant the required permissions.

Oracle 10g, 11g, or 12c (non-CDB mode, create a LOCAL USER)
1. Create a user named eoa_user and set the password to eoaPASSW0RD.
```
create user eoa_user identified by eoaPASSW0RD default tablespace users; 
```
2. Grant query permissions.
```
grant connect,select_catalog_role to eoa_user;
```

Oracle 12c (CDB mode, connect to the CDB to create a COMMON USER)

create user c##eoa_user identified by "eoaPASSW0RD" default tablespace users; 
 grant connect,select_catalog_role to c##eoa_user container=all; 
 alter user c##eoa_user set container_data=all container=current;

After you configure the source database account, click Next. On the Create Collection Task panel, configure the following parameters.

Configuration Item	Description
Collection Task Name	Enter a custom name for the collection task.
Source Database Type	Only ORACLE is supported.
Source Database Profile	Select the profile of the source database based on its type. For more information about how to create a database profile, see Manage database profiles.
List Of Schemas To Include	Specify the list of schemas. Separate multiple schema names with commas (`,`).
List Of Schemas To Exclude	Specify the list of schemas to exclude. Separate multiple schema names with commas (`,`).
Collect SQL Statements	Select whether to collect SQL statements.

After you complete the configuration, click Test Connectivity. If the connection is successful, click Start Collection.
After the collection task is complete, select the task and click Next: Create Profile to generate a database profile.

Collector-based collection

Log on to the Data Management (DMS) 5.0 console.
In the top menu bar, choose Data + AI > Heterogeneous Database Migration (ADAM) > Database Evaluation.
On the Database Information Collection tab, click Download Collector.
Download the ADAM client version that corresponds to the operating system of the device where you will run the client, and then decompress the package.
Note
Do not run the collector on the same device as the source database. The device where you run the ADAM client must meet the following minimum requirements:
- Network: Must be able to connect to the source database.
- CPU: 2 cores.
- Memory: 8 GB.
- Disk: 100 GB of free space.
Log on to the source database to configure a collection account and grant the required permissions.
Use an account with SYSDBA permissions to create a temporary account and configure the following permissions.
Note
If you already have an account with the required permissions, you can skip this step and use that account.
- Oracle 10g, 11g, or 12c (non-CDB mode, create a LOCAL USER)
  1. Create a user named eoa_user and set the password to eoaPASSW0RD.
```
create user eoa_user identified by eoaPASSW0RD default tablespace users; 
```
  2. Grant query permissions.
```
grant connect,select_catalog_role to eoa_user;
```
- Oracle 12c (CDB mode, connect to the CDB to create a COMMON USER)
```
create user c##eoa_user identified by "eoaPASSW0RD" default tablespace users; 
 grant connect,select_catalog_role to c##eoa_user container=all; 
 alter user c##eoa_user set container_data=all container=current;
```
Collect the structural data of the database. This data is used to generate feasibility and compatibility reports.
1. Execute the collection command.
  Note
  The .bat command is for Windows environments, and the .sh command is for Linux environments.
  - Oracle 10g
```
collect_10g[.sh|.bat] -h -u -p -d <service_name>
```
  - Oracle 11g
    - Oracle 11g R1
```
collect_11gR1[.sh|.bat] -h -u -p -d <service_name>
```
    - Oracle 11g R2
```
collect_11gR2[.sh|.bat] -h -u -p -d <service_name>
```
  - Oracle 12c, 18c, or 19c
    Note
    To collect information from a specific pluggable database (PDB) in Oracle 12c, use the collect_12c script. The operation is similar to collecting from Oracle 11g. collect_12c[.sh|.bat] –h <host> -u <username> -p <password> -P <port> -d <service_name> -s <sid>
  -h: The IP address of the source database. -u: The username for the collection account. For example, eoa_user. -p: The password for the collection account. For example, eoaPASSW0RD. -P: The port of the source database, such as 1521. -d: The service name of the source database. For Oracle 12c, this is the service name of a specific PDB. -s: The instance name of the source database.
2. Export the collection results.
  After the collection is complete, the system indicates that a data packet was generated and provides the path to the packet. The log file output is similar to the following:
```
[***] ******************************************************************
                                    [***] * Collect Successfully!
                                    [***] *
                                    [***] * Complete the file packaging, the package result path is:
                                    [***] * ~rainmeter/out/data.zip ******************************************************************
```
Optional: After the migration, purge the temporary account.
Use an account with SYSDBA permissions to connect to the database from a terminal and execute the following SQL statement.
1. Oracle 10g, 11g, 12c, 18c, or 19c (non-CDB mode)
```
drop user eoa_user cascade;
```
2. Oracle 12c, 18c, or 19c (CDB mode)
```
drop user c##eoa_user cascade;
```

Note

For best performance, collect database information during off-peak hours.
The collector has minimal impact on CPU. If the collection involves getddl operations on database objects, the CPU load might increase slightly at the beginning of the task. The degree of the increase depends on the specifications and current load of the source database.
The collector uses a negligible amount of memory from the source database.