Upgrading the High-Performance Loader onpload database
If onpload conversion failed during database server migration, you can manually upgrade the onpload database.
Starting with Version 9.40.xC3, HCL OneDB™ has a new version of the onpload database with longer column lengths. The onpload database now requires slightly more disk space than it did before Version 9.40.xC3.
When you migrate to a new version of HCL OneDB, you must also upgrade the onpload database.
To upgrade the onpload database:
- If you are upgrading from a version of HCL
OneDB that
is prior to Version 9.40, run the conploadlegacy.sh script,
as shown in this example:
conploadlegacy.sh 7.31 9.40 - If you are upgrading from a version of the database server that
is prior to Version 9.40.xC3, you must also perform one of the following
tasks:
- Run the conpload.sh script, as shown in this example:
conpload.sh 9.40 11.50 - Set the new environment variable IFX_ONPLOAD_AUTO_UPGRADE to
1for the upgrade to happen automatically the first time you start an HPL utility using the ipload or onpladm command, after you migrate to a new database server version. You cannot use the IFX_ONPLOAD_AUTO_UPGRADE environment variable with the onpload utility.
- Run the conpload.sh script, as shown in this example:
If you start an HPL utility before upgrading the onpload database, then you receive an error stating that the onpload database must be converted.
Starting with Version 9.40.xC3, the ipload utility does not support object names that contain more than 18 characters. The utility will continue to operate properly if legacy applications do not use long object names.