Frequently asked questions about the enterprise database
There are several common questions concerning the deployment and configuration of the enterprise database.
If the initial High Availability (HA) configuration was performed using DDL, are there any other permissions required to perform the upgrade with DDL?
The answer is no, as long as you have applied the DDL migration scripts (
fixupxx.sql
) for that particular IBM Traveler release and theappGrants.sql
. It is recommended that you run theappGrants.sql
every time DDL migration scripts are executed, as this will configure permissions for new tables if any have been added in that release.What is the default value for the
NTS_AUTO_DBSCHEMA
parameter innotes.ini
?The default is
true
, which means IBM Traveler will perform automatic schema migration.Is it possible to switch from DDL to Automatic Schema migration when performing an IBM Traveler upgrade? If so, how?
Yes, you can switch to automatic schema migration by removing the configuration parameter
NTS_AUTO_DBSCHEMA=false
fromnotes.ini
.What permissions are required for switching from DDL to Automatic Schema migration during an upgrade?
If you are switching to automatic schema migration, you cannot use the LNTUSER as it is. This user was only granted specific permissions for IBM Traveler operations, and does not include permissions for modifying schema or altering the database. As a result, a schema upgrade will fail and the IBM Traveler server will not start. The DB administrator must configure LNTUSER with schema privileges to create/alter/drop tables, columns, primary keys, and indexes, as well as grant database alter permission. LNTUSER, by default, should have INSERT, UPDATE, SELECT and DELETE permissions for all database objects (tables).
For SQL Server the schema authorization must be altered:ALTER AUTHORIZATION ON SCHEMA :: LNT TO LNTUSER
For DB2, LNTUSER must have permission to create and drop schema:GRANT CREATEIN, ALTERIN, DROPIN ON SCHEMA LNT TO LNTUSER
Note: Please refer to the SQL server or DB2 documentation for more information on setting these permissions, as well as the Database permissions topic in the IBM Traveler documentation.What DDL migration script(s) are needed for upgrading IBM Traveler HA to the latest release?
Start with thefixup#.sql
listed below and run all remainingfixup#.sql
scripts. When this completes, you should also runappGrants.sql
to ensure any new schema elements have the appropriate access rights.Table 1. Migration scripts Migration from... Start with script... 9.0.1.21
fixup32.sql
9.0.1.3
fixup20.sql
9.0.1
fixup12.sql
9.0.0.1
fixup11.sql
9.0.0.0
fixup10.sql
8.5.3 Upgrade Pack 2
fixup8.sql
8.5.3 Upgrade Pack 1
fixup6.sql
Earlier than 8.5.3 Upgrade Pack 1
fixup5.sql
Note: There are no migration scripts required for IBM Traveler server Interim Fix pack(s) .What are the recommended settings for DB2 transaction logs?
By default, the size of the DB2 transaction log is small, and an IBM Traveler server under heavy load can easily exceed the default size. As a result, it is recommended to set the transaction log to a larger size during HA setup. To get an initial estimate of the log size, refer to the IBM Traveler performance measurement guide and compare it against your environment. You should also monitor the DB2 transaction log space and check the utilization percentage. If it is high, or if you see DB2 transaction related errors
SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null
, then adjust the following log settings to higher values:LOGFILESIZ, LOGPRIMARY, LOGSECOND
.For example, perform the following commands on the DB2 server (or, if DB2 is configured with standby mirrors, on each DB2 server in the cluster):db2 update db cfg for traveler using LOGFILSIZ 8192 LOGPRIMARY 40 LOGSECOND 120 db2stop force db2start db2 activate db traveler
When does a schema normally get changed?
Schema changes occur only during major releases, upgrades, and/or to resolve a critical issue. Documentation will be provided for any fix pack or major release.