Home

	Expand Search

Installation Guide Adaptive Server Enterprise for Linux/Intel

Chapter 8 Upgrading Sybase Servers

Post-upgrade tasks

Post-upgrade tasks

After you have upgraded to the new version of Adaptive Server, perform the following tasks to make sure your new Adaptive Server is up and running.

After upgrade, there is no need to run update statistics on any tables. Upgrade process does not cause any changes in existing statistics.

Verifying that servers are running

1. To find out whether Adaptive Server is currently running, try to log in to the server, using isql:

   isql -Usa -P -Sserver_name

   If the server is running, you see the isql prompt:

      1>

   You can also use the showserver command to determine whether any Adaptive Server processes are running. For example:

   $SYBASE/$SYBASE_ASE/install/showserver

2. To verify that you are at the new version level, connect to Adaptive Server via isql and run the following commands:

   1> select @@version 
   2> go

   Look for "12.5" in the version string.

   1> sp_configure "upgrade version" 
   2> go

   sp_configure should return the Run Value "12500".

Restore functionality in Adaptive Server

To reset or enable options or functionality you had to change before the upgrade:

1. Reset the configuration parameters.

   If you changed any configuration parameters before the upgrade to ensure enough memory, use the sp_configure command to set them back to their previous values.

2. Use sp_dboption to reset any database options you disabled before the upgrade.

3. After you complete the upgrade, but before you use the upgraded Adaptive Server, verify that all scripts developed at your site point to Adaptive Server 12.5.

4. Procedure cache allocation after upgrade.

   This section is for information only. Adaptive Server ensures that procedure cache size after upgrade is the same as before upgrade, unless the before upgrade size was less than the default value.

   In Adaptive Server 12.5, procedure cache percent has been changed to procedure cache size. Adaptive Server now allocates memory dynamically and determines the size of the procedure and data caches in terms of megabytes. During the upgrade process, Adaptive Server converts the procedure cache percent to an absolute value and sets procedure cache size based on this value.

   For example, if procedure cache percent is configured as 20 percent of 200MB of memory, then the absolute value of procedure cache percent is 40MB. During the upgrade process, Adaptive Server converts procedure cache percent at 20 percent to procedure cache size at 40MB. If the value for procedure cache size is less than the default value, Adaptive Server sets procedure cache size to the default value. For example, if procedure cache percent is set to 10 percent in the example above, and the absolute value of 10 percent is less than the default value of procedure cache size, then procedure cache size will be set to the default value.

   With the introduction of dynamically reconfigured memory configuration parameters in Adaptive Server 12.5, an increase in Adaptive Server's memory use will not decrease the size of the procedure cache or the data cache. That is, if your default data cache is set to 40MB, and you increase your procedure cache, the default data cache is still 40MB.

   For more information about sp_configure, see the Reference Manual.

5. Check the procedure cache requirements.

   Stored procedures, triggers, and other compiled objects require more memory to run than older versions. The memory required to run a stored procedure increased by 20 percent between versions 10.x and 11.5. Adaptive Server 12.5 may need more procedure cache for the server to maintain the same performance.

   You may increase the procedure cache size during run-time, using sp_configure. You may verify any changes you make to the configuration file without having to reboot Adaptive Server using the verify option in sp_configure. The syntax is:

   sp_configure "configuration file", 0, "verify", "full_path_to_file"

   For example:

   sp_configure "configuration file", 0, "verify", "/work2/Sybase/ASE125.cfg"

   For more information about sp_configure and sp_sysmon, see the Reference Manual and the Performance and Tuning Guide. For more information about configuring memory, see the System Administration Guide.

6. Data cache allocation after upgrade. This section is for information only. Adaptive Server ensures that all the data cache sizes after upgrade will be the same as before upgrade.

   In pre-12.5 versions of Adaptive Server, the default data cache available depended on the amount of memory available to Adaptive Server. If the default data cache was set to 2MB, Adaptive Server allocated 2MB to the default data cache. If, after memory was allocated to all user-defined data caches and to the procedure cache, there was more memory available, that memory was allocated to the default data cache. However, if there was not enough memory available for Adaptive Server to set up the user-defined caches and the procedure cache, then memory would be taken from the default data cache regardless of the designated configuration parameter. Therefore, it was possible to set default data cache to the default value and have all remaining available memory be allocated to the default data cache.

   Adaptive Server 12.5 treats the default data cache size as an absolute value and sets it in the config file. The string DEFAULT in the config file has a different meaning for default data cache size in Adaptive Server 12.5.

   In pre-12.5 Adaptive Server, it meant all the memory left-over after allocating memory for other configurations, procedure and user defined named caches. In Adaptive Server 12.5, it means a default value of 8MB.

   During upgrade Adaptive Server ensures that the default data cache size before upgrade is the same as after upgrade. Therefore, during the preupgrade process, the size of the default data cache is obtained and written to the configuration file as an absolute value, not as "DEFAULT." This step is done to enable Adaptive Server 12.5 to have the same default data cache size as before the upgrade. If this size is less than the default size of default data cache of 8MB, then Adaptive Server 12.5 allocates a default data cache of size 8MB.

7. If you unmirrored devices, remirror them, using the disk remirror command.

8. If you used two-phase commit in 11.9.x, run the script to install the two-phase commit tables:

   isql -Usa -Psa_password -Sserver_name 
   -i$SYBASE/$SYBASE_ASE/scripts/installcommit

   You do not need to run this script if you do not use two-phase commit.

Reenabling replication server

If you disabled replication before the upgrade, you must reenable replication. To do so, first remove any older format log records from your database, and then reenable replication.

Use the dump database command after the upgrade to dump the database and transaction logs to remove the older format log records from your database. This prevents Replication Server from accessing the pre-upgrade portion of the transaction logs.

For example, to dump the sales database:

1> use master
2> go
1> dump database sales to "//./backup"
2> go

Follow the steps in this section to reenable replication after upgrading the primary databases and primary RSSDs.

For each primary database and RSSD:

1. Start Adaptive Server if it is not already running.

2. Log on to the server.

3. Clear the locator for the database by executing the following command in the RSSD for this database:

   1> use RSSD2> go 
   3> rs_zeroltm dataserver, database 
   4> go

4. Enable the truncation point for the database.

   1> use database2> go 
   1> dbcc settrunc("ltm", "valid")
   2> go

5. Restart the Replication Servers and LTMs.

6. Resume the DSI connections that were suspended before the upgrade by executing the following Replication Server command for each suspended database:

   1> resume connection to dataserver.database2> go

The replication system is now ready for Adaptive Server 12.5, and applications can resume.

If you installed any Sybase client products, such as Open Client, use the dsedit utility to edit your interfaces file and to specify the servers to which you want to connect.

For more information about establishing client/server connections, see the Open Client Configuration Guide or Chapter 8, "Upgrading Sybase Servers ."

Reenabling auditing

Reenable all auditing options for stored procedures using the audit options you recorded during pre-installation. See "Disable auditing"). Reenter the audit options using sp_audit.

• Adaptive Server 12.5 includes the following global audit options for sp_audit:

  • security

  • dbcc

• These options are turned off by default and will not be turned on even if you used sp_auditoption all to turn on all global audit options in a version earlier than 11.5.

  To turn on these options, use:

  1> sp_audit security "on"

  2> go

  1> sp_audit "dbcc" "on"

  2> go

  For more information, see the Reference Manual.

• The functionality provided by these obsolete sp_auditoption options is now covered by the sp_audit security global audit option:

  • server boot

  • role toggle

• The security option is turned off by default.

If any of these options were turned off before the upgrade, reset the security option to on to achieve the same auditing actions.