This edition applies to version 8, release 2 of IBM DB2 Everyplace and to all subsequent releases and modifications until otherwise indicated in new editions.
Welcome to the DB2 Everyplace Express Edition installation notes for version 8.2. These notes provide information about:
If you are migrating from an earlier version of DB2 Everyplace, refer to the migration instructions in the DB2 Everyplace installation and user's guide for version 8.2, available for download at the following location:
http://www.ibm.com/software/data/db2/everyplace/library.html
In order for DB2 Everyplace to operate with the highest degree of efficiency, system parameters need to be adjusted. Failure to do so can result in the inability to create a new connection to the database on Linux. It is recommended that the kernel parameters are adjusted.
Modify the login profile to include the following: export DISPLAY=hostname:0.0
Where hostname is the workstation where you want to use the Mobile Devices Administration Center.
You need to install the DB2 Everyplace Sync Server on a server, and install the DB2 Everyplace mobile database and Sync Client software on each mobile device or emulator that connects to the server. Requirements vary depending on the hardware, software, and operating system of the target server, device, or emulator.
After you install and configure DB2 Everyplace, you can start the First Steps launchpad, which provides links to sample applications and other resources that will help you get started using DB2 Everyplace.
The exact configuration you need to support your environment with satisfactory response time will vary depending on the size of the objects you are working with and other factors. Individual display response times vary depending on workstation speed, memory, size of objects, and network and server workload. Minimum recommended configurations must be evaluated and adjusted according to your unique requirements. Disk space recommendations below are for the product installation and working space only. The actual hard disk space required varies, depending upon your installation.
To use DB2 Everyplace Express, your system must meet or exceed the following hardware requirements:
| Configuration type | (Windows) Disk space required on the target hard drive | (Linux ) Disk space required in the user's home directory for each DB2 Everyplace Sync Server instance |
|---|---|---|
| Express |
400 MB (if using Database message store) 350 MB (if using File system message store) |
520 MB (if using Database message store) 470 MB (if using File system message store) |
The DB2 Everyplace Sync Server requires the following software:
DB2 Everyplace Express runs on the following operating systems:
Operating system requirements vary depending on the target device's processor. See Table 4 for more information.
Prerequisites:
Replace hostname with the name of the workstation where you want to use the Mobile Devices Administration Center.
For all supported operating systems, the server must meet or exceed the requirements specified in DB2 Everyplace Express Edition installation requirements.
To install DB2 Everyplace Express Edition on a server:
Choose one of the following methods:
If you need to change the configuration after installing files, you can use the Configuration wizard to specify parameters interactively, or use the command line configuration tool to configure DB2 Everyplace Express by using that is data specified in a file.
The DB2 Everyplace Express Edition Installation wizard copies files from a source (such as a CD or compressed archive) to a server and configures the installation. You can choose one of the following installation types:
Copies a predefined set of files to default locations relative to a directory you specify, then configures the installation.
In addition to the target directory, the wizard prompts you for the following information:
You specify the files to copy (for example, to support specific mobile devices), and you can specify additional configuration information. A custom installation also allows you to save your specifications in a response file that you can use to automate the installation process on other computers at a later time.
In addition to the information required for a typical installation, the wizard prompts you for the following parameters:
To install DB2 Everyplace Express Edition by using the Installation wizard:
The procedure for starting the Launchpad varies depending on your operating system and whether you are installing from a CD or an archive (for example, a compressed file downloaded from ibm.com).
| Operating system | Procedure |
|---|---|
| Windows | The Launchpad starts automatically when you insert the CD. |
| Linux |
|
| Linux for iSeries |
|
| Operating system | Procedure |
|---|---|
| Windows |
|
| Linux |
|
| Linux for iSeries |
|
After it copies the files to the server, the Installation wizard configures DB2 Everyplace Express Edition. If you need to change the configuration, you can start the Configuration wizard manually. You can also configure the installation by using the command line configuration tool.
The command line installer can read input from a file called a response file, which can automatically install DB2 Everyplace on multiple systems. A response file is an ASCII text file that contains setup data. The response file can be generated either by performing a custom installation with the DB2 Everyplace Installation wizard or by manual editing.
To install DB2 Everyplace Express Edition by using a response file and the command line installation tool:
The command line installer, installSilent, is in the top level directory of the CD or archive.
A sample response file is provided in the lib directory of the CD or archive.
The following example starts the command line installation tool on Windows and specifies C:\db2eSilent.rsp as the response file.
installSilent.bat C:\db2eSilent.rsp
Use the Uninstall wizard to remove DB2 Everyplace Express Edition from a server.
Prerequisites:
To remove DB2 Everyplace Express Edition:
In the following table, supported combinations of mobile device processors and operating systems are marked with an X. Availability of devices and the level of device support may change over time based on device manufacturer's actions. Some devices may go out of support; new devices may be added.
| Processor / OS | ARM | ARM v4T | Strong ARM | x86 | XScale | WINS | MIPS |
|---|---|---|---|---|---|---|---|
| Palm OS 4.1 | X | ||||||
| Palm OS 5.0 | X | ||||||
| Palm OS 5.2.1 | X | X | |||||
| Windows(R) CE v3 | X | X | |||||
| Windows CE v4 | X | X | X | X | X | ||
| Symbian OS 7 | X | X | |||||
| Linux(TM) | X | X | X | ||||
| QNX Neutrino | X | X | |||||
| Windows 2000 / XP / 2003 Server | X |
The design of some devices may limit the DB2(R) Everyplace(R) capabilities that can be used by the device. Not all devices can support all of the functions offered by DB2 Everyplace. IBM(R) cannot guarantee that all devices will work correctly due to differences in manufacturing, configuration and preloaded device software. Some DB2 Everyplace clients for the supported devices are available as downloads rather than being included on the DB2 Everyplace media.
Prerequisites:
Prerequisites for installing DB2 Everyplace files on a Linux mobile device vary depending on the device.
Linux mobile devices take various forms. Depending on the type of mobile device that you have, there are several installation options. For example, you could transfer files to your mobile device by using one of the following methods, depending on the type of mobile device and how that mobile device is configured:
The following table lists required run-time libraries for various processors.
| Processor | Library |
|---|---|
| x86 | glibc-2.2.4-13 |
| StrongARM | glibc-2.2.5 |
| XScale | glibc-2.2.5 |
To install DB2 Everyplace files on a Linux mobile device:
DB2 Everyplace mobile database files for Linux mobile devices are in the %DSYINSTDIR%\Clients\linux\database\ directory, where proc is a processor type, for example, strongarm or x86, and lang represents the language.
The file names are:
The files are located in %DSYINSTDIR%\clients\linux\sync\proc, where proc is a processor type, for example, strongarm or x86.
Copy the following library files for the appropriate processor into usr/lib/DB2e/:
DB2 Sync console is located at %DSYINSTDIR%\Clients\linux\sync\lang\proc\db2sync_console where proc represents a processor type and lang represents the language.
For example, if the DB2 Everyplace CLI shared library is in the %DSYINSTDIR%\database\x86 directory, append %DSYINSTDIR%\database\x86 to the existing LD_LIBRARY_PATH by using the following statement:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/DB2e/database/x86
DB2 Everyplace also includes a development database library for Linux devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for Linux devices with x86 processors are located in %DSYINSTDIR%\Clients\linux\database\x86Dev. To install this library, follow the procedure described in this topic, but copy the file from the appropriate Dev directory.
Prerequisites:
Install DB2 Everyplace by transferring files onto your device using one of the following methods, depending on whether you are using a mobile device or an emulator.
To install DB2 Everyplace files on a Palm OS device:
These files are in the %DSYINSTDIR%\Clients directory.
In the following table, lang is a language code, for example, en_US.
| File name | Description |
|---|---|
| palmos\database\ CryptoPlugin.prc | Encryption library |
| palmos\database\ DB2eCat.prc | DB2 Everyplace database engine |
| palmos\database\ DB2eCLI.prc | DB2 Everyplace database engine |
| palmos\database\ DB2eComp.prc | DB2 Everyplace database engine |
| palmos\database\ DB2eDMS.prc | DB2 Everyplace database engine |
| palmos\database\ DB2eRunTime.prc | DB2 Everyplace database engine |
| palmos\database\ PBSPkcs11.prc | Encryption library. Encryption support is available only on Palm OS 4.1 devices or later. The PBSPkcs11.prc file must be installed to use encryption between a Palm OS mobile device and the DB2 Everyplace Sync Server. |
| palmos\database\ lang \DB2eCLP\DB2eCLP.prc | DB2 Everyplace command line processor |
| utilities\ lang \DB2eImport | DB2 Everyplace Import tool |
These files are required if you plan to use the DB2 Everyplace sync server. They are in the %DSYINSTDIR%\Clients\palmos\sync\ directory.
In the following table, lang is a language code, for example, en_US.
| File name | Description |
|---|---|
| imsaconfig.prc | IBM Sync Configuration adapter |
| imsadb2e.prc | IBM Sync DB2 Everyplace adapter |
| imsafile.prc | IBM Sync File adapter |
| isyncconf.prc | IBM Sync engine |
| isyncore.prc | IBM Sync engine |
| isyncstat.prc | IBM Sync statistics |
| isyncxpt.prc | IBM Sync transport library |
| SSLlib.prc | IBM Sync SSL library |
| wbxmllib.prc | IBM Sync WBXML library |
| \lang\ db2sync.prc | DB2 Sync client GUI |
| \lang\ dsyagent.prc | IBM Sync Remote Stored Procedure adapter |
| \lang\ upgrade\ iUpgrade.prc | IBM Sync Auto Deploy |
Prerequisites:
Installation procedures for QNX Neutrino mobile devices vary depending on the device. Options include:
For additional information on transferring files to your device, see the documentation provided with that device. You can also consult the QNX Neutrino Software Developer's Kit (SDK).
DB2 Everyplace database files for QNX Neutrino mobile devices are located in the %DSYINSTDIR%\Clients\neutrino\database\ directory.
In the following list, proc represents a processor type, for example, strongarm or x86. :
The files are located in %DSYINSTDIR%\clients\neutrino\sync\proc, where proc represents a processor type, for example, strongarm or x86.
Copy the following library files for the appropriate processor into usr/lib/DB2e/:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/DB2e/database/x86
DB2 Everyplace also includes a development database library for QNX Neutrino devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for QNX Neutrino devices with x86 processors are located in %DSYINSTDIR%\Clients\neutrino\database\x86Dev. To install this library, follow the procedure described in this topic, but copy the file from the appropriate Dev directory.
Prerequisites:
To install DB2 Everyplace files on a Symbian OS Version 7 device:
In the following table, lang is a language code, for example, en_US.
| File name | Description |
|---|---|
| armi\DB2e.sis | DB2 Everyplace database engine |
| armi\db2ejdbc.sis | DB2 Everyplace JDBC driver |
| lang\DB2eCLP\UIQ\DB2eCLP.sis | DB2 Everyplace Command Line Processor |
| lang\install\UIQ\DB2e_Symbian7.sis | DB2 Everyplace package (all the above in a single package) |
| File name | Description |
|---|---|
| DB2Sync.sis | DB2 Sync Client |
| upgrade\IUpgrade.app | IBM Update Tool |
| upgrade\IUpgrade.rsc | IBM Update Tool |
Prerequisites:
To install the DB2 Everyplace files on a Windows CE device:
In the following table, ver is the Windows CE version, for example, v3 for version 3, or v4 for version 4; and proc is the processor type, for example, ARMRel or X86Rel.
| File Name | Description |
|---|---|
| jdbc\db2ejdbc.jar | DB2 Everyplace JDBC driver |
| ver\proc\CryptoPlugin.dll | DB2 Everyplace database engine for data encryption |
| ver\proc\DB2e.dll | DB2 Everyplace database engine |
| ver\proc\DB2eJDBC.dll | DB2 Everyplace JDBC driver |
where ver is the Windows CE version, for example, v3 for version 3, or v4 for version 4;proc is the processor type, for example, ARMRel or X86Rel; and lang is the language code, for example, en_US.
Sync Client XScale libraries are available only for devices that run Windows CE 4.x. For Windows CE 3.0 (most Pocket PC 2000 and 2002 devices), use Sync Client libraries from ARM. For the DB2 Everyplace mobile database, XScale libraries are available for Windows CE 3 and 4.
| File Name | Description |
|---|---|
| db2sync.exe | IBM Sync Client GUI |
| dsyagent.dll | IBM Sync Remote Stored Procedure adapter |
| imsaconfig.dll | IBM Sync Configuration adapter |
| imsadb2e.dll | IBM Sync DB2 Everyplace adapter |
| imsafile.dll | IBM Sync File adapter |
| isync4j.dll | IBM Sync Java interface |
| isync4j.jar | IBM Sync Java interface |
| isyncconf.dll | IBM Sync engine |
| isyncore.dll | IBM Sync engine |
| isyncstat.dll | IBM Sync client statistics |
| isyncxpt.dll | IBM Sync transport library |
| wbxmllib.dll | IBM Sync WBXML library |
| upgrade\iUpgrade.exe | IBM Sync Auto Deploy |
The following table shows where to obtain Sync Client libraries for various emulators:
| File Name | Description |
|---|---|
| \Clients\WinCE\sync\lang\v3\X86EMRel | Pocket PC 2000 emulator |
| \Clients\WinCE\sync\lang\v3\X86Rel | Pocket PC 2002/2003 emulator |
| \Clients\WinCE\sync\lang\v4\emulatorRel | WinCE .NET emulator |
DB2 Everyplace also includes a development database library for Windows CE version 3 devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for Windows CE version 3 devices with x86 processors are located in \Clients\wince\database\wce300\x86Dev. To install this library, follow the procedure described in this topic, but copy the file from the appropriate Dev directory.
Prerequisites:
The Microsoft Strong Encryption download (available from Microsoft) for your operating system must be installed to use encryption between Windows clients and the DB2 Everyplace Sync Server.
To install DB2 Everyplace files on a Windows client:
DB2 Everyplace files are in the %DSYINSTDIR%\Clients\win32\database directory.
In the following table, lang represents a language code, for example, en_US.
| File name | Description |
|---|---|
| x86\CryptoPlugin.dll | DB2 Everyplace database engine for data encryption |
| x86\DB2e.dll | DB2 Everyplace database engine |
| x86\DB2eJDBC.dll | DB2 Everyplace JDBC driver |
| x86\DB2eODBC.dll | DB2 Everyplace ODBC driver |
| jdbc\db2ejdbc.jar | DB2 Everyplace JDBC driver |
| jdbc\DB2eAppl.class | Sample Java application |
| jdbc\DB2eJavaCLP.class | Command Line Processor written in Java |
| lang\DB2eCLP\uicode\DB2eCLP.exe | Command Line Processor executable |
| x86\ODBCInst.exe | Registers the DB2 Everyplace ODBC driver |
The Sync Client files are in the %DSYINSTDIR%\Clients\win32\sync\lang\ directory, where lang is a language code, for example, en_US.
| File Name | Description |
|---|---|
| db2sync_console.exe | DB2 Sync interface |
| dsyagent.dll | IBM Remote Stored Procedure adapter |
| imsaconfig.dll | IBM Sync Configuration adapter |
| imsadb2e.dll | IBM Sync DB2 Everyplace adapter |
| imsafile.dll | IBM Sync File adapter |
| isync4j.dll | IBM Sync Java interface |
| isync4j.jar | IBM Sync Java interface |
| isyncconf.dll | IBM Sync engine |
| isyncore.dll | IBM Sync engine |
| isyncstat.dll | IBM Sync Client statistics |
| isyncxpt.dll | IBM Transport library |
| wbxmllib.dll | IBM Sync WBXML library |
DB2 Everyplace also includes a development database library for Windows devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for Windows devices with x86 processors are located in %DSYINSTDIR%\Clients\win32\database\x86Dev.
DB2 Everyplace Express Edition provides a wizard and a command line tool you can use to change a DB2 Everyplace configuration.
The topic Troubleshooting configuration errors provides information about errors that might arise when you configure DB2 Everyplace.
Prerequisites:
DB2 Everyplace files must be installed before you configure DB2 Everyplace.
The Configuration wizard prompts you for the following data:
To configure DB2 Everyplace Express Edition after you perform a custom installation, the wizard prompts you for additional data:
To configure DB2 Everyplace Express Edition by using the DB2 Everyplace Configuration wizard:
Run the DSYconfig.exe file, installed by default in the %DSYINSTDIR%\config\bin directory.
You can also use a Start menu shortcut: Start -> Programs -> IBM DB2 Everyplace Express -> Setup Tools -> DB2 Everyplace Configuration Wizard.
DB2 Everyplace is not configured until you click Next in the Pre-configuration Summary panel.
Topics in this section provide information that will help you configure DB2 Everyplace on mobile devices.
Secure Sockets Layer (SSL) provides added security when synchronizing by encrypting data. To use SSL, you must install a certificate on the client device so that it can verify that it is in communication with the appropriate server. The certificate must be obtained from the public SSL certificate of the HTTP server with which the clients will synchronize data. Refer to the documentation for the server that is providing the SSL service for information about how to obtain and export the certificate in a format that the client can install and use. If you are using the IBM HTTP Server that is installed with the WebSphere Application Server, use the ikeyman tool in the <IHS>\bin directory to export the SSL certificate. If you are using the embedded version of the WebSphere Application server, ikeyman is in the <DSYINSTDIR>\WAS\bin directory. Be sure to export the public certificate.
Windows CE and Symbian devices do not need manual installation of certificates. When synchronizing with these client devices, you only need to specify the address of the SSL server. For example, https://www.syncsample:9558/
To configure SSL for DB2 Everyplace client devices:
Prerequisites:
Linux device clients require the OpenSSL libraries. Download these libraries from http://www.openssl.org and install the libraries before configuring SSL on Linux client devices.
To configure SSL for Linux client devices:
openssl x509 -noout -hash -in ca_certificate file
where ca_certificate file is the name of the base-64 encoded X.509 certificate file.ln -s ca_certificate file 9c975d97.0
where ca_certificate file is the name of the certificate file and 9c975d97 is the hash value obtained from the previous step.openssl verify -CApath /usr/share/ssl/certs /usr/share/ssl/certs/ca_certificate_file
You will see a message similar to the following if the installation succeeded: /usr/share/ssl/certs/ca_certificate_file: OKIf you receive an error message, go to http://www.openssl.org/docs/apps/verify.html to look up the error message.
Prerequisites:
Download the certificate conversion utility, palmdb.exe, from http://www.ibm.com/support/.
To configure SSL for Palm OS client devices:
For a self-signed certificate:
For a real certificate that is obtained from CA:
To configure SSL for Windows client devices:
https://server:port/db2e/db2erdb/.
Prerequisites:
Open Database Connectivity (ODBC) is an application programming interface for developing programs that are database independent or that access multiple data sources simultaneously. To reduce DB2 Everyplace's footprint, DB2 Everyplace ODBC driver and setup functions are provided in a separate file, DB2eODBC.dll.
The DB2 Everyplace ODBC driver supports the same functions as the DB2 Everyplace CLI interface, and faces the same limitations. It might not meet the requirements of most ODBC GUI tools. One good use of this driver is to write database-independent code without compiling or linking with DB2 Everyplace files. You can also access multiple data sources from different vendors simultaneously.
When you install DB2 Everyplace, the following files are copied to the same directory as DB2e.dll (default location: C:\Program Files\IBM\DB2Everyplace\Clients\win32\database\x86).
To configure the DB2 Everyplace ODBC driver:
Choose Start -> Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC)
After you configure the DB2 Everyplace ODBC driver, you can use it to execute the functions provided in the DB2 Everyplace CLI interface, plus the following additional C/C++ function.
SQLGetFunctions()
This function reports whether a specific function is supported, allowing applications to adapt to varying levels of support when connecting to different database servers.
Syntax
SQLRETURN SQLGetFunctions(
SQLHDBC ConnectionHandle,
SQLUSMALLINT FunctionId,
SQLUSMALLINT * SupportedPtr);
Arguments
ConnectionHandle
[Input]
Connection handle.
FunctionId
[Input]
A #define value that identifies the ODBC function of interest:
SupportedPtr [Output]
SupportedPtr can point to a single value or an array of values, depending on the value of FunctionId, as shown in the following table. Arrays returned in SupportedPtr use zero-based indexing
| FunctionId | SupportedPtr |
| identifies a single ODBC function | Points to a single SQLUSMALLINT value. The value is SQL_TRUE if the specified function is supported by the driver; otherwise, the value is SQL_FALSE. |
| SQL_API_ODBC3_ALL_FUNCTIONS | Points to a SQLSMALLINT array with a number of elements equal to SQL_API_ODBC3_ALL_FUNCTIONS_SIZE. The Driver Manager treats this array as a 4,000-bit bitmap that can be used to determine whether an ODBC 3.x or earlier function is supported. |
| SQL_API_ALL_FUNCTIONS | Points to
an SQLUSMALLINT array of 100 elements. The array is indexed by
#define values used
by FunctionId to identify each ODBC function; some elements of the array
are unused and reserved for future use.
An array element's value is SQL_TRUE if it identifies an ODBC 2.x or earlier function supported by the driver. It is SQL_FALSE if it does not identify an ODBC function, or if it identifies an ODBC function that the driver does not support. |
The First Steps launchpad provides links to sample applications and other resources that will help you get started using DB2 Everyplace.
Prerequisites:
Install and configure DB2 Everyplace.
To start the First Steps launchpad:
Run the First Steps command.
The First Steps launchpad provides buttons linked to resources that will help you get started with DB2 Everyplace. The number of buttons and associated resources varies depending on your operating system and DB2 Everyplace configuration.
This topic provides information that will help you troubleshoot errors that may arise while using the Configuration wizard or the command line configuration tool.
If you receive an error message due to an incorrect or invalid value for a property in the Configuration wizard or the dsyconfig.properties file, stop the servlet or process for the DB2 Everyplace Sync Server (the default name is IBMDB2eServer) before you run the Configuration wizard or command line configuration tool again.
To stop the Sync Server, open a command window and issue the following command:
You can also use a Start menu shortcut:
.
When a Windows service is stopped, files that are locked by that service are not always released immediately. As a result, the DB2 Everyplace configuration tools might be unable to delete certain files and directories, and the unconfiguration process will fail. If this happens, start the unconfiguration process again.
To ensure that the Sync Server can successfully communicate with clients, make sure that the servlet is running. You do not need to have any clients installed in order to perform a check.
DB2 Everyplace provides basic error logging facilities for devices that use Linux, QNX Neutrino, or Windows 32-bit operating systems. DB2 Everyplace also provides development libraries that you can install on these devices to generate trace data. This data can help you troubleshoot problems as you develop and test DB2 Everyplace applications.
To enable tracing, install development libraries on the mobile device. These libraries are in directories that end in "Dev". For example, the development libraries for Linux devices with x86 processors are located in \Clients\linux\database\x86Dev.
When you use the development libraries to run an application, DB2 Everyplace writes data to a trace file in the database directory, using a file name listed in the following table. If a trace file exists in the database directory, CLI trace information is appended to that file.
| Long file name | Short file name (8.3 format) | |
|---|---|---|
| Trace file | DSY_DB2eTRACE | _trc.DBs |
| Log file | db2ediag.log | _diag.DBs |
| Dump files | DB2e_cxxxxx * | _cxxxxx.DBs * |
* xxxxx is the process identifier (PID) number of the affected process.
DB2 Everyplace generates diagnostic data for applications running either release or development libraries. When an application encounters a severe system error (SQLState 58005), DB2 Everyplace logs the error in a log file and captures the system state in a dump file. The previous table lists the file names for log files and dump files. All files are located in the same directory as the database.
Data in the following log files can also help you diagnose problems:
The data integrity check tool reports whether tables and indexes are corrupted. To run this tool, execute the DBCHECK command in the sample CLP application. The command syntax is:
DBCHECK outputfile
The outputfile parameter specifies a text file in the database directory where the tool will write the results.
The table below lists all of the error messages that can be generated by the DB2 Everyplace Update Tool. Table 16 displays the error message and a possible remedy for the problem.
| Error message | Possible remedy |
|---|---|
| Authentication failed (invalid encryption key) - update aborted | Verify that the client settings match the user's settings defined in the Mobile Device Administration Center. |
| File size exceeds available memory | Delete any applications or files that are no longer needed on the device and try again. |
| Internal server error | This is an internal error that you need to report to IBM Software Support with the trace file. |
| Failed to open connection | Check your network connection and the SyncServer. Make sure that the host is connected and the server is running. |
| Failed to establish connection | Check your network connection and the SyncServer. Make sure that the host is connected and the server is running. |
| Failed to send request | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
| Failed to receive reply | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
| Timeout while receiving reply | Specify a larger timeout value or try to synchronize when there is less traffic on the network. |
| Failed to receive acknowledge | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
| Failed to open Net library | Verify that the network library exists on the device. Try to reinstall the library. |
| Failed to resolve hostname | Verify that the hostname and the DNS addresses are correct. |
| Failed to allocate working buffer for transport | Delete any applications or files that are no longer needed on the device and try again. |
| Unknown network error | This is an internal error that you need to report to IBM Software Support with the trace file. |
| Failed to create target file | Verify that the target file is not being used by another application. If the target file is being used, unlock it and synchronize again. |
| No files received for update | This is an informational message stating that the server does not have an update for the mobile device. |