Messaging Installer Completed With Errors

Explanation: This error happens when the messaging server database upgrade does not complete. Several scenarios may cause this to happen, including general upgrade failure, database configuration problems, inaccessible database, or database errors.

Solution: Check the trace file to get more information, and use it to further diagnose the problem. The trace file is located in SMP_HOME\Servers\MessagingServer\Bin\scripts. The trace file is prefixed with the DBUpgraderTrace_ followed by a timestamp (YYYYMMDDHH24MMSS) indicating when it was written; for example: DBUpgraderTrace_20121106144758.txt. A new trace file is written every time DBUpgrader is run, so look for the most recently written trace file for information about the latest run of DBUpgraderTrace.

Example error log:

“***Error!!! Error!!!***
The Messaging installer completed with the following errors. These errors will have to 
be addressed before the services become functional.
Please refer to documentation for recovery process.
Database upgrade failed."

Scenario 1 – Database Upgrade Failure

Explanation: If you find the Database upgrade failed message in DBUpgraderTrace.log, this may indicate that the messaging server database had some lingering connections to a table while the upgrade was running.

Solution:

Stop all SAP Mobile Server services in all the application nodes.
Restart the database services in the data tier node. This is to make sure the messaging database has no open connections.
From the primary server node, open a Windows command window and navigate to SMP_HOME\Servers\MessagingServer\Bin.
Run the command dbupgrader –v current and make sure no error messages are displayed.

Scenario 2 – Database Configuration

Explanation: If you find this syntax error in DBUpgraderTrace.log, you need to configure the cache database (CDB) with the database option quoted_identifier='ON' for all database users:

20120918T234644.977|ERROR: Syntax error near 'ENCRYPTED' on line 19
20120918T234644.980|-- Caught unexpected exception: Error creating database schema
20120918T234644.981|Got global error [Error creating database schema]

Solution:

Configure the cache database (CDB) with the database option quoted_identifier='ON' for all database users.
1. Use the dbisql tool.
2. Run this SQL statement:
```
set option quoted_identifier = 'ON'
```
Stop all SAP Mobile Server services in all the application nodes.
Restart the database services in the data tier node. This is to make sure the messaging database has no open connections.
From the primary server node, open a Windows command window and navigate to SMP_HOME\Servers\MessagingServer\Bin.
Run the command dbupgrader –v current and make sure no error messages are displayed.

Scenario 3 – Database Not Accessible

Explanation: If you find several Database not ready messages followed by a final Database is not accessible message in the DBUpgraderTrace.log, this typically means that the cache database server was not running during the upgrade, or the system has been configured so that the database server is not visible at the configured location.

Solution:

Ensure that the cache database service is running.
Ensure that the cache database service is network-accessible from the machine running the DBUpgrader.
Stop all SAP Mobile Server services in all the application nodes.
Restart the database services in the data tier node. This is to make sure the messaging database has no open connections.
From the primary server node, open a Windows command window and navigate to SMP_HOME\Servers\MessagingServer\Bin.
Run the command dbupgrader –v current and make sure no error messages are displayed.

Scenario 4 – Database Errors

Explanation: Other messages in DBUpgraderTrace.log represent database errors issued while executing particular upgrade commands. The errors generally contain error messages supplied by the database server, next to the command that triggered the error.

Solution:

Look up the error codes in the SQL Anywhere error message documentation, for example: http://dcx.sybase.com/index.html#sa160/en/saerrors/sa-errors-by-sqlcode.html
Use the error code to resolve the database problem.
Stop all SAP Mobile Server services in all the application nodes.
Restart the database services in the data tier node. This is to make sure the messaging database has no open connections.
From the primary server node, open a Windows command window and navigate to SMP_HOME\Servers\MessagingServer\Bin.
Run the command dbupgrader –v current and make sure no error messages are displayed.