C.2 Upgrade Issues

This section discusses known issues and workarounds for upgrading.

Missing Parameter in the ArkSQL.cnf File after Upgrading from NetWare 6.5 SP1

Problem: The Transaction Isolation parameter in the sys:\arkManager\arkSQL.cnf file is missing or is set to the wrong value after you upgrade from NetWare 6.5 SP1 to any later versions of NetWare. Data corruption is possible.
Possible Cause: The Transaction Isolation parameter in the sys:\arkManager\arkSQL.cnf file is not set to READ_COMMITTED or is missing from the file.
Action: If you upgrade directly from NetWare 6.5 SP1 to any later version of NetWare, you must modify the sys:\arkManager\arkSQL.cnf file. To prevent possible data corruption, set the Transaction Isolation parameter to Read_Committed before restarting ArkManager after the upgrade.

  1. Stop ArkManager 2.0.

  2. Upgrade the server to OES NetWare.

  3. Verify that the server is operating as expected, but do not start ArkManager.

  4. Compare and modify values of non-system-specific information in sys:\arkManager\arkSQL.cnf with the ones defined in sys:\arkManager\arkSQL_sample.cnf.

    Most importantly, make sure to add the following variable setting to the end of the file:

    
set-variable = transaction_isolation=READ_COMMITTED

  5. Start ArkManager 2.0.

If you are configuring a new archive server after the upgrade, this setting is part of the updated sample arkSQL.cnf file, sys:\arkManager\arkSQL_sample.cnf. Use the updated sample file as a guide when setting up additional archive servers.

IMPORTANT:This defect exists for upgrades from NetWare SP1 to NetWare SP2 or later servers or OES NetWare servers. It was resolved in NetWare SP2 and is not a problem for upgrades from NetWare SP2.