Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux
- Section I. Configuring SF Sybase ASE CE
- Preparing to configure SF Sybase CE
- Configuring SF Sybase CE
- Configuring the SF Sybase CE components using the script-based installer
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Performing an automated SF Sybase CE configuration
- Performing an automated I/O fencing configuration using response files
- Configuring a cluster under VCS control using a response file
- Section II. Post-installation and configuration tasks
- Section III. Upgrade of SF Sybase CE
- Planning to upgrade SF Sybase CE
- Performing a full upgrade of SF Sybase CE using the product installer
- Performing an automated full upgrade of SF Sybase CE using response files
- Performing a phased upgrade of SF Sybase CE
- Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
- Performing a rolling upgrade of SF Sybase CE
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Preparing to configure the Sybase instances under VCS control
- Installing, configuring, and upgrading Sybase ASE CE
- Section V. Adding and removing nodes
- Adding a node to SF Sybase CE clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding the new instance to the Sybase ASE CE cluster
- Removing a node from SF Sybase CE clusters
- Adding a node to SF Sybase CE clusters
- Section VI. Configuration of disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Sample installation and configuration values
- Appendix C. Tunable files for installation
- Appendix D. Configuration files
- Sample main.cf files for Sybase ASE CE configurations
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. High availability agent information
Configuring Sybase for detail monitoring
This section describes the tasks to be performed to configure a Sybase server for detail monitoring.
Note:
The steps that are described here are specific to the sample script, SqlTest.pl, provided with the agent. If you use a custom script for detail monitoring, you must configure the Sybase database accordingly.
Perform these steps only once in a Sybase cluster.
To configure Sybase for detail monitoring
- Source the SYBASE.sh file or SYBASE.csh file (depending on the user shell) to set the $SYBASE and $SYBASE_ASE environment variables.
- Start the Sybase server.
# startserver -f ./$SYBASE/$SYBASE_ASE/install/RUN_server_name
- Start the Sybase client on any cluster node.
# isql -Usa -SSYBASE_SERVER_NAME
Enter the administrator password when prompted to do so.
- Connect to the master database.
# use master # go
- Create a Sybase user account.
# sp_addlogin user_name, password # go
The detail monitor script should use this account to make transactions on the database.
- Create a database.
# create database database_name # go
The detail monitor script should make transactions on this database.
- If required, restrict the size of the log file for the database.
# sp_dboption database_name, "trunc log on chkpt", true # go
- Connect to the database that is created in step 6.
# use database_name # go
- Associate the user created in step 5 with the database created in step 6.
# sp_adduser user_name # go
- Change the user to the one created in step 5.
# setuser "user_name" # go
- Create a table in the database.
# create table table_name (lastupd datetime) # go
The detail monitor script should make transactions on this table.
If you use the SqlTest.pl for detail monitoring, make sure you create a table with a lastupd field of type datetime.
- Verify the configuration by adding an initial value to the table.
# insert into table_name (lastupd) values (getdate()) # go
- Exit the database.
# exit
More Information