Log on as SID<ADM> user stop the SAP system and the ASE Server using the management console. Disable the Sybase BCKServer_<SID>_BS and Sybase SQLServer_<SID> services. Also make sure that no process isql,sqlsrver.exe or bcksrvr.exe are running in task manager reboot the host as well.
Log on as SYB<SID> user , download the file dbsrvresp_update_win.txt from note 1607816 and copy it to the temporary location d:\droplocation where you extracted the patch file earlier. Open cmd in administration (elevated mode) Run the command syntax setupConsole.exe -f <TMPDRIVE>:\<PATH_TO_TMPDIR>\dbsrvresp_update.txt -i silent -DUSER_INSTALL_DIR=<SYBDRIVE>:\sybase\<DBSID> -DAGREE_TO_SAP_LICENSE=true
Replace DBSID with your SAP System ID, and replace Sybdrive with the drive where you ASE software is installed. Replace <TMPDRIVE> and <PATH_TO_TEMPDIR> as relevant
This is the longest phase and usually took me 10 - 15 minutes.
When the install process has finished check the ASEsuite.log which is located in %SYBASE%\log or in this case D:\sybase\<DBSID>\log and check for errors.
Perform the post upgrade tasks as user syb<sid> enable the services for Sybase Sybase BCKServer _<DBSID>_BS and Sybase SQLServer _<DBSID> only and not SAP. Sybase SQLServer _<DBSID> service takes a long time to start after update, do not panic check the DBSID.log in my example it is updating statistics below. Can take up to 10 minutes maybe more to startup initially.
Check the database <SID>.log for errors of Job Scheduler as per the note, if you do see the below error you can ignore the error at this point.
Logon with user syb<sid>, Unlock user sa again by logging on as sapsso user. The user sa is locked by the installation script dbsrvresp_update_win.txt.
Execute the Sybase installation scripts located in the directory D:\sybase\<DBSID>\ASE-16_0\scripts execute with command syntax Isql64 -Usa -S<SID> -X -iinstmstr -o<output file> Always specify full path to input file (script) and output file (log file). Check the output log file for errors afterwards in detail.
Example of text command of instmaster.
isql64 -X -Usa -SSID -i D:\sybase\SID\ASE-16_0\scripts\instmstr -o D:\droplocation\instmstrlog.txt
Repeat these steps for the following scripts:
Instcomm, instmodl, instmsgs. ebf,installjsdb, installdbextend
instsecu (necessary only if database sybsecurity has been setup)
installdbccdb (optional, necessary only if you configured the dbcc database
Execute the script syb_update_db.TXT which is attached to this SAP note. Copy the script to a temporary directory (e.g. the temporary directory to which you copied the Sybase software package). Change to that directory and execute the script:
$>isql -X -Usa -S<SID> -e -i syb_update_db.TXT -o sybupd_out.txt
Take note command syntax changes here
Restart the job scheduler. Log in to ASE with isql with the account sapsa and execute the
command:
sp_configure "enable job scheduler", 1
exec sybmgmtdb..sp_sjobcontrol '' , 'start_js'
Run the following command in the directory where you previously implemented this script , note you must use SA user and therefore it needs to be still unlocked. Substitute SID with your SID:
isql -SSID -Usa -DSID -X -e -i sp_thresholdaction_logfreespace.sql
Lock user "sa" again. Log in to ASE with isql with the account sapsso and execute the command as per below.
As user SYB<SID> stop Sybase and disable services again
Remove the newly installed sample client library applications according to SAP Note 1598817 (optional). Ensure that all physical devices created by the process have only write permission for the operating system user who installs, configures and runs SAP ASE. In a standard installation, that is the user 'syb<sid>' for /sybase/<DBSID>. On a Windows system, the file permission inheritance is already set up and the Adaptive Server services are running as the syb<sid> operating system user. As you can see the inheritance is running to Sybase subfolders and the services are running as per below image.
The Adaptive Server update includes folders containing sample client library applications. Note: These sample programs are included for training purposes only and are not intended to be installed in a production environment.
!!!Be very careful not to delete any parent folders!!!
$SYBASE/OCS-16_0/sample
$SYBASE/DataAccess/ODBC/samples
$SYBASE/jConnect-7_0/sample2
$SYBASE/jConnect-7_0/classes/sample2
$SYBASE/ASE-16_0/sample
$SYBASE/WS-16_0/samples
In our case here is nothing to delete as you can see above!
Log in as <sid>adm user. Copy the suitable <DBCLNT>.SAR file to the directory <drive>:\usr\sap\<SID>\SYS\global\syb\NTAMD64\. Copy the downloaded ASEBC1600001_2-20012478.SAR to the directory E:\usr\sap\SID\SYS\global\syb\NTAMD64 and extract it
Update the JDBC driver and reconfigure your Java stack to use this JDBC driver with the changed name, see SAP Note 867976.(This is for dual stack or Java only systems)
Log in as user<sid>adm and re-enable the services for Sybase and SAP and start the SAP system through the SAP Management Console.
Now check the version of the database after the upgrade as per above
Now after system is started access tcode DBACOCKPIT specify the password of user sapsa and select the option Use the standard connect user and do not ask again and click on logon.
Open DBACOCKPIT -> Click on Database <SID> -> Configuration -> Data Collection Framework -> Collector Configuration (check for any yellow or red collectors and repair them as required)
As per this example click on repair.
Now you can see it is displaying correctly. Always start with the Framework collector first.
Now you will have to check that your installed threshold script still exist by running below query in iqsl and switching to the master database. As you can see your threshold script is still installed in SID database.
Now you must check that your set thresholds are still active for the script. Switch to your <DBSID> should be the one identified by query above. Then run the command as per above. As you can see from above I had only installed the one threshold and the last chance threshold values with the script sp_thresholdaction_logfreespace. This configuration should still be intact.
Now switch to master database again and verify that you dump configuration still exists. As you can see the dump configuration is still existing and configuration is correct as per what I set it up. This configuration should still be intact.
REFERENCE DOCUMENTS
1607816 - SYB: Installing Service Packs for SAP ASE (Windows)
2162735 - SYB Performing a major ASE upgrade (Windows)
2116143 - Use of sqlupgrade or sqlupgraderes utilities may fail to upgrade ASE with messages: "Unable to boot server" and "Adaptive Server failed to restart" - SAP ASE
867976 - Changing JDBC driver on WEB AS Java 6.40 NW 7.0x 7.1x
1982469 - SYB Updating SAP ASE with saphostctrl sapdbctrl
1598817 - SYB Removal of sample client library applications
1031096 - Installing Package SAPHOSTAGENT
2075653 - Targeted ASE 16.0 Release Schedule and CR list Information
1835880 - SYBHow to diagnose issues with Sybase ASE Job Scheduler, ATM, or Scheduled Jobs
2087323 - SYB Important solved problems for SAP Applications running on SAP ASE
1940536 - SYB Mandatory requirement to turn off 'plan sharing' feature in SAP ASE
1722359 - SYB Running SAP applications on SAP ASE - Best Practice
1539125 - SYB Configuration Guide for SAP ASE 15.7.0.0xx
- SAP Managed Tags:
4 Comments
