A large RDU
database can be several gigabytes in size, and may take an extended length of
time to migrate. This depends largely on your hardware. Using faster disks
improves the time significantly.
automatically compacts your database that may be fragmented. However, this
Prime Cable Provisioning
release stores additional data for every device. You can expect the size of the
database to increase after migration by as much as 10 percent.
process is optimized for speed and database compactness. As a result, migration
requires a large amount of process heap size (memory). For example, migrating a
7-million device database requires approximately 1,024 MB of process heap size.
Since the migration process is limited to 4 GB of heap space, migration is
effectively limited to a database size of approximately 25-30 million devices.
parameter in the
migrateDb.sh script determines the maximum process heap size
for migration. The default setting of 3,072 MB for this parameter is sufficient
for migrating a 20-million device database. You may need to fine-tune this
setting to suit your environment. For example, to migrate smaller databases
running on low-end systems with less memory, you can reduce the value of the
maximum heap size setting. For databases that exceed the maximum supported
scale, you may need to increase this setting.
To change the
heap size parameter, in the
migrateDb.sh script edit the value for the