Upgrade the High-Performance Loader onpload Database

If onpload conversion failed during server conversion, you can manually convert the onpload database.

Starting with Version 9.40.xC3, Dynamic Server has a new version of the onpload database with longer column lengths. The onpload database now requires slightly more disk space than it did in previous versions.

The following table shows the relationship between the database server version and the onpload database schema version.

Database Server Version	onpload Database Version
Pre 7.3	0 or not available
7.31	1
9.2, 9.3, 9.40.xC1, 9.40.xC2	2
9.40.xC3 and later	3

When you upgrade to a new version of Dynamic Server, you must also upgrade the onpload database.

To upgrade the onpload database

If you are upgrading from a version of Dynamic Server that is prior to Version 9.40, run the conploadlegacy.sh script, as shown in this example:
```
conploadlegacy.sh 7.31 9.40
```
If are upgrading from a version of Dynamic Server that is prior to Version 9.40xC3 and, if necessary, have already run the conploadlegacy.sh script, you must also perform one of the following tasks:
- Run the conpload.sh script, as shown in this example:
```
conpload.sh 9.40 10.0
```
- Set the new environment variable IFX_ONPLOAD_AUTO_UPGRADE to 1 for the upgrade to happen automatically the first time you invoke 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.

If you invoke an HPL utility before upgrading the onpload database, then you receive an error stating that the onpload database must be converted.

Starting with Dynamic Server Version 9.40.xC3, the ipload utility does not operate properly if you are using object names that contain more than 18 characters. The utility will continue to operate properly if legacy applications do not use long object names.