Skip to main content
Skip table of contents

Source Details

The Source Details page shows informational items about the current source, regardless of the target.

The details listed are grouped into three areas:

Identity

Lists information helping identify the scanned source/instance being analyzed on this page.

Resources

Lists information helping to understand the computing resources used by the source.

Metrics

Lists key dimensional details that help understand the scale or operational characteristics of the source.

The content of each area varies by the source database engine type:

DB2 LUW

The Details section for DB2 LUW sources

The parameters shown for DB2 LUW are:

Area

Parameter

Description

Identity

Hostname

The name or IP address of the server that hosts the source database.

Instance Name

Name of the database instance.

Database Name

Name of the source database.

Database Version

Version of the source database.

Architecture

The OS architecture of the host on which the database is running.

Tags

Any custom tags assigned to this source during scan.

Resources

Number of Cores

Number of CPU cores.

Retrieved using the CPU_TOTAL column in the ENV_GET_SYSTEM_RESOURCES table.

Server RAM

Server memory available on the host where the DB is running.

Specified in GB using the MEMORY_TOTAL column in the ENV_GET_SYSTEM_RESOURCES() table function.

Allocated Instance Memory

Server memory allocated for the database.

Specified in GB using the MAX_MEMBER_MEM column in the ADMIN_GET_MEM_USAGE table function.

Allocated Database Memory

The amount of memory that is currently being used by a database.

Specified in GB using the SUM of rows under the MEMORY_SET_SIZE column in the MON_GET_MEMORY_SET table function.

Allocated Application Memory

The maximum amount of memory that can be allocated to service application requests.

Specified in GB using the SUM of rows under the MEMORY_SET_SIZE column where MEMORY_SET_TYPE is application from the MON_GET_MEMORY_SET table function.

Allocated Database Storage

Disk space used by the database data files.

Specified in GB using the SUM of rows using the TBSP_TOTAL_PAGES and TBSP_PAGE_SIZE columns in the MON_GET_TABLESPACE table function.

Utilized Database Storage

The amount of storage space that is currently being used by a database.

Specified in GB using the SUM of rows using the TBSP_USED_PAGES and TBSP_PAGE_SIZE columns in the MON_GET_TABLESPACE table function.

Metrics

Instance Uptime Prior to Analysis

Number of days the database was running since it was last restarted.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

HBase

The Details section for HBase sources

The parameters shown for HBase are:

Area

Parameter

Description

Identity

HBase Cluster ID

The HBase cluster unique id as reported by the HBase ClusterId metric.

HBase Version

HBase version as reported by the HBaseVersion metric.

ZooKeeper Quorum

ZooKeeper quorum address, as detected in configuration entry hbase.zookeeper.quorum.

Cluster Key

Key that can be used to add this current cluster as a replication peer by another HBase cluster using the add_peer() command.

Tags

Any custom tags assigned to this source during scan.

Resources

ZooKeeper Base Path

Root node of this cluster in ZooKeeper, as detected in configuration entry zookeeper.znode.parent.

Load Balancer

The LoadBalancer class used by the HMaster, as detected in configuration entry hbase.master.loadbalancer.class.

Access Control

Whether authorization is enabled in configuration.

HBase Root Directory

Path to the HBase root directory on the underlying Hadoop cluster.

HDFS Space Consumed

Bytes used across HDFS, accounting for replication. This includes all HDFS data stored under the HBase root folder in Hadoop, counting all replicated blocks. Copies / replicas of files are included in this value.

HDFS Space Remaining

Remaining potentially free space across HDFS.

Metrics

Number of Regions

Number of regions across the cluster.

Balancer Enabled

Whether the balancer is currently enabled or not.

Load Average

Average number of regions per RegionServer. Naïve computation as reported by the AverageLoad metric.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

MongoDB

MongoDB may be deployed in three different topologies: Replica Set, Sharded Cluster, and Standalone.

The parameters available under each of these detected topologies differ based on the characteristics and availability of information for each topology.

Replica Set

Databases Single Details MongoDB Replica (tags).png

MongoDB parameters for the Replica Set deployment topology

The parameters shown for a MongoDB Replica Set are:

Area

Parameter

Description

Identity

Cluster ID

The cluster unique identifier.

Topology

The deployment topology. “Replica Set” for Replica Sets.

Cluster Name

The user-defined cluster name provided during the scan.

Binary Versions

The mongod version(s). If mongod versions vary, then the earliest and latest ones are shown.

Replica Set Id

The Id of this Replica Set.

Tags

Any custom tags assigned to this source during scan.

Resources

Host Count

The number of unique hosts on which the Replica Set is deployed.

Instance Count

The number of mongod processes participating in this Replica Set.

Shard Count

Not applicable for Replica Sets.

Data Size

The sum total size of data stored by MongoDB.

Size on Disk

The sum total size of (compressed) data in files stored on disk by MongoDB.

Database Count

The number of user-defined databases.

Collection Count

The number of user-defined collections.

Index Count

The number of indexes across all user-defined collections.

Metrics

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

Oplog Size

The size (bytes) of the oplog.

Oplog Windows

The current oplog window in terms of time. This measures the difference between the oldest and the newest oplog entry.

Sharded Cluster

MongoDB parameters for the Sharded deployment topology

The parameters shown for a MongoDB Sharded Cluster are:

Area

Parameter

Description

Identity

Cluster ID

The cluster unique identifier.

Topology

The deployment topology. “Sharded” for sharded clusters.

Cluster Name

The user-defined cluster name provided during the scan.

Balancer Enabled

Whether the balancer is currently enabled or not.

Binary Versions

The mongod version(s). If mongod versions vary, then the earliest and latest ones are shown.

Tag/Region Aware Sharding

Whether the use of tag aware sharding or region aware configuration was detected or not.

Tags

Any custom tags assigned to this source during scan.

Resources

Host Count

The number of unique hosts on which mongod processes are deployed.

Instance Count

The number of mongod processes participating in this sharded cluster. Does not include mongos processes.

Shard Count

The number of shards in this cluster.

Data Size

The sum total size of data stored by MongoDB across all primary members. This effectively is the size of data stored in all user-defined collections and of non-user-defined collections that are located in user-defined databases.

Size on Disk

The sum total size of (compressed) data in files stored on disk by MongoDB across all primary members.

Database Count

The number of user-defined databases.

Collection Count

The number of user-defined collections.

Index Count

The number of indexes across all user-defined collections.

Metrics

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

Oplog Size

The size (bytes) of the oplog.

Oplog Windows

The current oplog window in terms of time. This measures the difference between the oldest and the newest oplog entry.

Standalone

In the standalone topology, there is only one mongod process.

If there is a single instance is configured as a single-member Replica Set, then it will show up as a Replica Set, not a Standalone.

MongoDB parameters for the Standalone deployment topology

The parameters shown for a MongoDB Standalone server are:

Area

Parameter

Description

Identity

Cluster ID

The cluster unique identifier.

Topology

The deployment topology. “Standalone” for stand-alone clusters.

Cluster Name

The user-defined cluster name provided during the scan.

Binary Versions

The mongod version.

Tags

Any custom tags assigned to this source during scan.

Resources

Data Size

The sum total size of data stored by MongoDB.

Size on Disk

The sum total size of (compressed) data in files stored on disk by MongoDB.

Database Count

The number of user-defined databases.

Collection Count

The number of user-defined collections.

Index Count

The number of indexes across all user-defined collections.

Metrics

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

MySQL

The Details section for MySQL sources

The parameters shown for MySQL are:

Area

Parameter

Description

Identity

Hostname

The name or IP address of the server that hosts the source database.

Instance Name

Name of the database instance.

Database Name

Name of the source database.

Database Version

Version of the source database.

Architecture

The OS architecture of the host on which the database is running.

Tags

Any custom tags assigned to this source during scan.

Resources

Number of Cores

Number of virtual CPU cores.

This number is based on various parameters gathered from system views, such as innodb_purge_threads, innodb_read_io_threads, and innodb_write_io_threads.

Prior to MySQL 5.6, innodb_purge_threads, innodb_read_io_threads, and innodb_write_io_threads were not available. migVisor also considers innodb_thread_concurrency if it has a non-zero value. Otherwise, an assumed CPU Core Count of 8 Cores is used.

Server RAM

Server memory available on the host where the DB is running.

Our calculations take into account different parameters, derived from system views, such as key_buffer_size, query_cache_size, innodb_buffer_pool_size, innodb_log_buffer_size, max_connections, read_buffer_size, read_rnd_buffer_size, sort_buffer_size, join_buffer_size, binlog_cache_size, thread_stack, and tmp_table_size.

Once we get an estimation based on these parameters, 30% is added as a buffer.

Allocated Instance Memory

Server memoryallocated for the database.

This number is based on various parameters gathered from system views, such as key_buffer_size, query_cache_size, innodb_buffer_pool_size, innodb_log_buffer_size, max_connections, read_buffer_size, read_rnd_buffer_size, sort_buffer_size, join_buffer_size, binlog_cache_size, thread_stack, and tmp_table_size.

Allocated Database Storage

Disk space used by the database data files.

Metrics

Database Uptime Prior to Analysis

Number of days the database was running since it was last restarted.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

Oracle

The parameters shown for Oracle are:

Area

Parameter

Description

Identity

Hostname

The name or IP address of the server that hosts the source database.

Instance Name

Name of the database instance.

Database Name

Name of the source database.

Database Version

Version of the source database.

Architecture

The OS architecture of the host on which the database is running.

Tags

Any custom tags assigned to this source during scan.

Resources

Number of Cores

Count of virtual CPU cores.

Specifies the number of CPU threads available for the instance. Derived from the CPU_COUNT setting in the V$PARAMETER view. 

Server RAM

Server memory available on the host where the database is running.

Specifies the physical memory in GB available on the server. Derived from the PHYSICAL_MEMORY_BYTES statistic metric in the V$OSSTAT view.

PGA size

Amount of server memory allocated for the database in addition to SGA. This memory contains session-dependent variables required by a dedicated or shared server process.

Allocated Memory (SGA)

Server memory allocated for the database. This read/write memory area along with the background processes form a database instance.

Allocated Database Storage

Disk space used by the database data files.

Metrics

Database Uptime Prior to Analysis

Number of days the database was running since it was last restarted.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

PostgreSQL

The Details section for PostgreSQL sources

The parameters shown for PostgreSQL are:

Area

Parameter

Description

Identity

Hostname

The name or IP address of the server that hosts the source database.

Instance Name

Name of the database instance.

Database Name

Name of the source database.

Database Version

Version of the source database.

Architecture

The OS architecture of the host on which the database is running.

Tags

Any custom tags assigned to this source during scan.

Resources

Number of Cores

Number of virtual CPU cores.

This number is based on various parameters gathered from system views, such as max_worker_processes and max_parallel_workers .
Prior to PostgreSQL 9.4, max_worker_processes and max_parallel_workers were not available. An assumed CPU Core Count of 8 Cores is shown for those earlier versions.

Server RAM

Server memory available on the host on which the database is running.

This number is based on various parameters gathered from system views, such as shared_buffers, work_mem , max_connections, maintenance_work_mem, effective_cache_size, and block_size.

This calculated size is padded 30% as a buffer, in order to support sizing for real-world requirements.

Prior to PostgreSQL 8.1, block_size was not available. An assumed block size of 8K is used to compute this metric for earlier versions.

Allocated Instance memory

Server memory allocated for the database.

This number is based on various parameters gathered from system views, such as shared_buffers, work_mem , max_connections, maintenance_work_mem, effective_cache_size, and block_size.

Prior to PostgreSQL 8.1, block_size was not available. An assumed block size of 8K is used to compute this metric for earlier versions.

Allocated Database Storage

Disk space used by the database data files.

Metrics

Database Uptime Prior to Analysis

Number of days the database was running since it was last restarted.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

SQL Server

The Details section for SQL Server sources

The parameters shown for SQL Server are:

Area

Parameter

Description

Identity

Hostname

The name or IP address of the server that hosts the source database.

Instance Name

Name of the database instance.

Database Name

Name of the source database.

Database Version

Version of the source database.

Architecture

The OS architecture of the host on which the database is running.

Edition

SQL Server edition name.

Product Major Version

The major version portion of the ‘ProductVersion’ property.

Product Minor Version

The minor version portion of the ‘ProductVersion’ property.

Always On availability groups

Indicates whether Always On (high availability) is enabled or disabled.

Always On availability groups status

Indicates Always On's current runtime status, whether it is running, not started, or failed.

Tags

Any custom tags assigned to this source during scan.

Resources

Number of Cores

Number of virtual CPU cores.

Specifies the number of CPU threads available for the database. Derived from the CPU_COUNT setting in the dm_os_sys_info view. 

Server RAM

Server memory available on the host where the database is running.

Specifies the physical memory in GB available on the server. Derived from the total_physical_memory_kb statistic metric in the dm_os_sys_memory view.

Allocated Instance Memory

Server memory allocated for the instance.

Allocated Database Memory

Server memory allocated for the database.

Allocated Database Storage

Disk space used by the database data files.

Metrics

Database Uptime Prior to Analysis

Number of days the database was running since it was last restarted.

Data Collection Date

The date on which the database scan was run.

mQE Version

The version of the Query Definitions file that was used by the mMC to collect the data.

mMC Version

The version of the migVisor Metadata Collector used to run the scan.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.