Does data collection impose high pressure on a database?
No, the data collection process does not impose high pressure on a database. The process consists of only read operations. Only the getDDL operation consumes CPU resources. However, we recommend that you collect data during off-peak hours to increase the collection speed. Otherwise, a connection timeout error may occur. If such an error occurs, you must recollect the data.
What kind of data does Database Collector collect? Is the amount of collected data large?
Database Collector collects statistics from Oracle databases. The statistics include data definition language (DDL) statements and SQL statements. The amount of collected data depends on the number and size of your database objects and the size of SQL statements. In most cases, the amount of collected data is less than 1 GB.
What can I do if the "connection to database fail, please check connection parameters" error is reported?
If this error is reported, check whether the specified username (-u), password (-p), port number (-P), and service name (-d) of the database are valid.
What can I do if the "TNS:listener does not currently know of service requested in connect descriptor" error is reported?
If this error is reported, check whether the value of the -d parameter is the service name of the database.
What can I do if the Database Collector client fails to start because the JDK installed on the local machine is earlier than V1.8?
If the Database Collector client fails to start due to this cause, set JAVA_PATH in the collect_.sh script to the installation directory of the Java Development Kit (JDK). To do so, replace JAVA_PATH='which java' with JAVA_PATH=''.
How do I run Database Collector on macOS?
Install Java Runtime Environment (JRE) of JDK V1.8 or later on your on-premises server and download the Linux-based Database Collector.
Why is the number of index objects in the collection results inconsistent with the actual number?
The numbers are inconsistent because unique indexes and primary indexes in Oracle databases are merged into the DDL statements of table objects.
What can I do if a returned error message indicates that SQL text information is missing when I collect data from an Oracle Database Express Edition database?
If this error message is returned, run the alter system set control_management_pack_access="DIAGNOSTIC+TUNING";exec dbms_workload_repository.create_snapshot(); command on the database. Then, recollect data without restarting the database.
What can I do if the "insufficient account permission, please refer to user guide and re-configure account" error is reported?
Check whether you have granted the required permissions to the database account, or reauthorize the account by executing SQL statements.
What can I do if the "GC overhead limit exceeded" error is reported?
If this error is reported, expand the physical memory of Database Collector and expand the startup memory by adding the -Xmx16g suffix to the value of the JVM_OPTIONS parameter in the startup script.
How do I view a large file in the collection results on macOS or Linux?
Copy the large file to a temporary directory, run the split -b 10m eoa_tmp_objects_ext.csv command to split the file into small files, and then view the small files. These small files will be named (for example, xaa and xab) and saved in the same directory.
What can I do if the "transaction log is not configured, please refer to FAQ and modify log configuration" error is reported?
  1. If this error is reported, set a directory to store archive files based on the runtime environment of the Oracle database.
    alter system set log_archive_dest_1='location=<file_path>';
  2. If permitted, shut down the database, and then restart it in the mount state.
    shutdown immediate
    startup mount                     
  3. Configure the archiving mode for the database.
    alter database archivelog;               
  4. Open the database.
    alter database open;                     
  5. Execute the following SQL statement to check whether SUPPLEMENTAL_LOG_DATA is enabled:
    select t.SUPPLEMENTAL_LOG_DATA_MIN from v$database t;                       

    If the returned value is NO, SUPPLEMENTAL_LOG_DATA is disabled. Execute the following statement:

    alter database add supplemental log data;