Upgrade utility (dbupgrad)

Note

You cannot use the Upgrade utility (dbupgrad) to upgrade SQL Anywhere 9.0.2 and earlier databases to SQL Anywhere 16. To upgrade SQL Anywhere 9.0.2 and earlier databases to SQL Anywhere 16, you must rebuild the database by performing an unload and reload. See SQL Anywhere Server upgrades.

Updates the system tables and views, adds new database options, recreates all system stored procedures, installs jConnect support, changes support for Java in the database, archives the transaction log, creates a new transaction log. This utility also stops and restarts the database.

Syntax

dbupgrad [ options ]

Option

Description

@data

Reads in options from the specified environment variable or configuration file.

To protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file.

-c "keyword=value; ..."

Specifies connection parameters.

For example, the following command upgrades a database called sample16 and does not install jConnect support, connecting as user DBA with password sql:

dbupgrad -c "UID=DBA;PWD=sql;DBF=c:\sa16\sample16.db" -i

-i

Excludes jConnect metadata support. To use the jConnect JDBC driver to access system catalog information, do not use this option. You can still use jConnect when this option is specified, as long as you do not access system catalog information. You can add jConnect metadata support later using Sybase Central or the ALTER DATABASE UPGRADE statement.

-nrs

Stops but does not restart the database after the upgrade. If this option is not specified, the database is restarted after the upgrade, unless the AutoStop connection parameter is set to Yes.

-o filename

Writes output messages to the specified file.

-pd [ Y | N ]

Specifies whether pre-16.0 system procedures that perform privileged operations will execute with the privileges of the definer (owner) or the invoker. For a list of these procedures, see Running pre-16.0 system procedures as invoker or definer.

When -pd N is specified, the system procedures are executed with the privileges of the invoker (the user who is executing the system procedure).

When -pd Y is specified, the system procedures are executed with the privileges of the definer (the user or role that owns the system procedures).

If nothing is specified, the behavior is to maintain the current setting for the database that is being upgraded. In the case of upgrading a pre-16.0 database, this means to execute these system procedures with definer privileges.

This setting does not impact system procedures added in version 16.0 or later, and does not impact the default behavior for user-defined procedures, which continues to be definer.

-q

Runs in quiet mode—messages and windows are not displayed.

Privileges

Remarks

Caution

Back up your database files before upgrading.

The dbupgrad utility upgrades a database created with earlier versions of the software to enable features from the current version of the software. The earliest version that can be upgraded is SQL Anywhere 10.0.0. While later versions of the database server can run against databases that were created with earlier releases of the software, some of the features introduced since the version that created the database are unavailable unless the database is upgraded.

An error message is returned if you use the Upgrade utility to upgrade a database that is currently being mirrored.

Note

Refresh the materialized views in your database after upgrading the database.

Note

Features that require a physical reorganization of the database file are not made available by dbupgrad. Such features include index enhancements and changes in data storage. To obtain the benefits of these enhancements, you must unload and reload your database.

As new versions and software updates become available for SQL Anywhere, you can use the Upgrade utility to take advantage of the new features.

Upgrading a database does not require you to unload and reload your database.

During the upgrade, the transaction log is archived. A new transaction log is created when the database starts after the upgrade.

Exit codes are 0 (success) or non-zero (failure).