This section contains the following topics: • Assumptions before Connection • How to Connect
• Required Permissions for Historical Server Activities • Mutually Exclusive Sessions
Assumptions before Connection
Before you can connect to Historical Server:
• The Adaptive Server whose performance data you want to collect must be running.
• A Monitor Server that is monitoring the Adaptive Server must be running. See Sybase Adaptive Server Enterprise Monitor Server User’s Guide for instructions on verifying whether an Adaptive Server/Monitor Server pair is running.
• The Historical Server must be running. See Chapter 3, “Starting and Stopping,” for instructions on verifying whether a Historical Server is running.
• Connection information must be configured correctly on both the Historical Server machine and its client machines. See Chapter 2, “Configuring Historical Server,” for more information.
How to Connect
Connect to Historical Server using a utility that offers an interactive interface to Sybase servers, such as SQL Advantage orisql. Follow the standard connection procedures for the utility. For example, in SQL Advantage, choose the Connect menu item. Inisql, start isql using the Historical Server name as the value of the-S parameter.
Required Permissions for Historical Server Activities
Connect to Historical Server using a user login and password that has permissions for the activities you intend to perform, as described in Table 4-3. Depending on the permissions required, you might have
4-6 Command Reference
Connecting to Historical Server ASE Monitor Historical Server Version 11.5
to disconnect and reconnect with different login accounts to perform various activities.
A single Historical Server can connect to and collect data from multiple Adaptive Server/Monitor Server pairs. For example, from the same Historical Server connection, you could create two
recording sessions, one gathering performance data for an Adaptive Server named server1 using a Monitor Server named server1_MON, and the other gathering data for an Adaptive Server named server2 using a Monitor Server named server2_MON. If you do not have a login account that is valid in both Adaptive Server instances, you Table 4-3:Permissions required for Historical Server activities
Activity Permissions Required to
Perform the Activity Superuser activities:
• Stop Historical Server. • Delete Historical Server files,
including recording session data files.
• Access files from private recording sessions.
Superuser permissions. To obtain superuser permissions, connect to Historical Server using the superuser account defined at startup.
The superuser account does not have to be a valid account in any Adaptive Server.
Create recording sessions. Valid login and password in the Adaptive Server being monitored. Execute permission on the
mon_rpc_connect stored procedure in the Adaptive Server being monitored. This permission is required in order to connect to Monitor Server.
Create playback sessions using public recording session files (from recording sessions whose
protection_level parameter ispublic). Usehs_list command on public recording session files.
Valid login and password in the Adaptive Server being monitored.
Create playback sessions using private recording session files (from recording sessions whose
protection_level parameter isprivate). Use thehs_list command on private recording session files.
The same login that created the private sessions, or superuser. In the latter case, the superuser account must be a valid login in the Adaptive Server being monitored.
ASE Monitor Historical Server Version 11.5 Connecting to Historical Server
would need to create these recording sessions in different
connections to Historical Server, using different login accounts. The data files from the two recording sessions, however, could reside in the same directory.
Thehs_create_recording_session command specifies the Monitor Server you want to connect to, which indirectly implies the Adaptive Server you want performance information about.
Mutually Exclusive Sessions
A Historical Server connection can only be involved with one session at a time. You can either be defining a recording session, or defining and executing a playback session, but you cannot mix together commands for multiple sessions. That is, if you start a recording session definition with thehs_create_recording_session command, you must finish the sequence of commands to define that session (or cancel the session) before you can start to define a playback session or a new recording session.
Note that defining a recording session is not the same thing as a recording session in progress. The user who defines a recording session is connected to and actively communicating with Historical Server during definition of a recording session. The user does not actively communicate with Historical Server during the actual recording. Any user connections are irrelevant during recording. For example, a user might connect to Historical Server at 3 pm , define a recording session that starts at 10 pm, and then disconnect from Historical Server. At 10 pm, it is irrelevant whether the user is connected to Historical Server; the recording session takes place if Historical Server is running.
A playback session, however, requires the user connection during both playback definition and playback execution. To cancel playback execution and allow the user connection to perform some other communication, the user must issue thehs_terminate_playback command.
Starting and Ending a Recording Session Definition
Thehs_create_recording_session command starts a recording session definition. After issuing this command, you further define the recording session by issuing other commands to create views, filters, and alarms for the recording session.
4-8 Command Reference