Rebuilding Platform Databases

Platform databases need to be rebuilt regularly. Without regular maintenance, the database log can grow to be large (several gigabytes in size), and performance could degrade.

If you experience long shutdown times with data services for the data tier, you need to unload and reload data the dbunload utility. This rebuilds your database and maintains a healthy data tier performance.

To avoid this issue, SAP recommends that you perform this action every four or five months.

  1. Stop all runtime services (data tier and server nodes), including the cache database, the cluster database, and the messaging database, and synchronization services.
  2. Perform a full off-line backup of each, by copying the database and transaction log files to a secure location. See Backup and Recovery.
  3. Update the jConnect catalog to support the jConnect7 jdbc driver.
    dbisql -c "conn-string" -nogui read jcatalog12.sql

    The jcatalog12.sql file is located at SMP_HOMEServers\UnwiredServer\config in each SAP Mobile Server server node, not on the data tier.

  4. Rebuild each runtime database with the SQL Anywhere Unload (dbunload) utility.
    The dbunload utility is available in the SMP_HOME\Servers\SQLAnywhere16\BIN32 directory. For details, see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/dbunload.html .
  5. Validate the data before restarting the services.
Parent topic: Data Tier Administration