Problem

When ISDN(Integrated Services Digital Network) is set up with other protocols, ISDN will be used as secondary or fallback if the connection with other protocol fails and a license check for ISDN will be performed.

An error may occur when there are ISDN residual settings in the OFTP config and no ISDN entry in the license file.

To avoid the error, the ISDN settings should be removed.

Using UI and then activation would be the best and recommended way, as it leaves no place for error. If using the UI is not possible then the following procedure can be used to clear residual ISDN config directly from the database.

!! Note however that the procedure comes with a risk so it should be tested first on a test environment.

The procedure would be to change the settings in amg table , export those changes in odette2.cfg using cfgdb tool and then activate the changes through UI so that the changes propagate to OFTP tables.

Resolution

Below query can be used to identify the records having ISDN :

SELECT * FROM P_F_PARAM_CONFIG_ODETTE2_CFG WHERE TLIB = 'isdnDB.tlib' OR TLIB LIKE 'isdnDB.tlib,%'OR TLIB LIKE '%,isdnDB.tlib,%' OR TLIB LIKE '%,isdnDB.tlib';

After identifying the rows, two columns need to be updated in these tables: TLIB and CONNECTION_TYPE. Remove “isdnDB.tlib” from TLIB column and “ISDN” from CONNECTION_TYPE column.

The update query will depend on what DB is used and what values will be used in connection type instead of ISDN and below is a sample query for derby database:

UPDATE P_F_PARAM_CONFIG_ODETTE2_CFG SET TLIB = 'tcpDB.tlib' WHERE TLIB = 'isdnDB.tlib' OR TLIB LIKE 'isdnDB.tlib,%'OR TLIB LIKE '%,isdnDB.tlib,%' OR TLIB LIKE '%,isdnDB.tlib';

UPDATE P_F_PARAM_CONFIG_ODETTE2_CFG SET CONNECTION_TYPES='TCP/IP-TLS, TCP/IP' where id in ( SELECT id FROM P_F_PARAM_CONFIG_ODETTE2_CFG WHERE TLIB = 'isdnDB.tlib' OR TLIB LIKE 'isdnDB.tlib,%'OR TLIB LIKE '%,isdnDB.tlib,%' OR TLIB LIKE '%,isdnDB.tlib');

The above query will set connection type 'TCP/IP-TLS, TCP/IP’. The query will change according to what values are needed to set and what DB is used.

After updating the data, export odette2.cfg from the CLI (using command "cfgDbTool.sh EXP_ONE /param/odette2.cfg") and activate OFTP2 from the GUI

Note: This should be tested thoroughly before applying to production.