The time it takes to upgrade from Release 8.2 to Release 8.5 varies, because of numerous factors. It is therefore recommended that you use the information in Table 2 as a rough estimate, and not as a guarantee. The following hardware configuration was used to arrive at these time estimates:
DB Version: 11.1.0.7
DB Server OS: RHEL 5.3
Class of the DB Server: PowerEdge R900
Number of CPUs on the DB Server: 2 Quad 2.4 GHz processors
RAM on Database Server: 16 GB
Disks Used for Database Files: EMC CLARiiON CX3-20 SANS
Disk Filesystem: ASM
Application Server (The server on which the migration was performed):
Database Server
Total Data Size premigration: ~ 269 GB
Total Data Size postmigration: ~ 272 GB
Table 1 provides row counts for key tables in the sample database for Release 8.5. These row counts are based on tables with > 500,000 records.
Data | Current Data Size | History Data Size |
---|---|---|
Number of Orders | 2020646 | 3646369 |
Number of Order Lines | 3407941 | 7207180 |
Number of Shipments | 2665353 | 5121472 |
Number of Items | 1201544 | N/A |
Number of Inventory Items | 286670 | N/A |
Number of Receipts | 177848 | N/A |
Table 2 provides time estimates pertaining to the migration process.
Time | Task |
---|---|
< 1 min | copyextensions |
~ 2 mins | initupgrade |
< 1 min | migration-validation |
< 1 min | alter-history-tables |
~ 43 mins | install-history-indexes |
< 1 min | upgrade-history-tables |
< 1 min | alter-transaction-tables |
~ 26 mins | install-transaction-indexes |
~ 4 mins | upgrade-transaction-tables |
< 1 min | migrate-doc-params |
< 1 min | validate-upgrade |
~ 16 mins | run-history-drop |
~ 13 mins | run-transaction-drop |
~ 310 mins | migrate-char-to-varchar-h |
~ 113 mins | migrate-char-to-varchar |