Configuring Sybase databases
This section describes the steps to configure your Sybase database before you install BMC Remedy Action Request (AR) System or any application in the BMC Remedy IT Service Management (ITSM) Suite.
These steps are usually performed by a user who has database administrator privileges.
If you try to install the BMC Remedy AR System server on top of Sybase 15.0.2/EBF 14328, the installation might fail. You will receive the following error message:
Failure during SQL operation to the database : Incorrect syntax near the keyword 'path'.
For troubleshooting information, see Sybase error 156 in your Sybase documentation and BMC Remedy AR System error message 552.
Install the Sybase database.
You can install on the same computer on which BMC Remedy AR System is installed, or on a remote server that is networked to the computer on which you plan to install BMC Remedy AR System.
A warning message with the names and paths of the dummy devices is displayed during the installation procedure (after the Database File Input Panel is displayed). You must manually delete these dummy devices after the installation procedure is complete.
- Install Sybase clients.
For remote installations, install on the same computer as the BMC Remedy AR System server is installed on.
- From the directory on which the 64-bit Sybase client is installed, source the database:
- Ensure that TCP/IP is enabled for the database.
- Verify or set the
SYBASEenvironment variables as follows:
DSQUERY=SybaseServer; export DSQUERY
SYBASE=SybaseInstallDirectory; export SYBASE
These examples use the syntax for Bourne shell.
- (UNIX only) Verify or set the LANG environment variable.
- If you are upgrading from BMC Remedy AR System 7.1.00 to 8.1, set the
Select intodatabase option for the database that you are upgrading.
Ensure that your database can accept network communication using the parameters entered during the installation.
Refer to the planning spreadsheet for AR System installation parameters.
Network communication occurs through Open Database Connectivity (ODBC). The network must be able to recognize your ODBC data source.
- Change the minimum page size to 8 KB.
For information about increasing the page size, see your Sybase documentation.
- Increase the default
tempdbsize to 600 MB.
- If you created a device in addition to a master device, designate the database device as the default database device. This designation is required, because BMC Remedy AR System is always created on the default device.
- If the database is configured to extend automatically, perform the following actions:
Set the BMC Remedy AR System data file size to 3 GB or larger.
If the database is not configured to extend automatically, set the BMC Remedy AR System data file size to at least 2 GB for one BMC Remedy ITSM application, or to at least 8 GB if you are installing all BMC Remedy ITSM applications.
- Set the log file size to 2 GB or larger.
In the Sybase configuration file, set the following recommended minimum values, and then restart the Sybase server:
\[Meta-Data Caches\] number of open objects = 1310072 number of open indexes = 512000 number of open partitions = 6000 \[Physical Memory\] max memory = 128000 \[SQL Server Administration\] procedure cache size = 7000 \[Lock Manager\] lock scheme=datarows \[User Connections\] number of user connections=50
- Set the following Sybase database configuration parameters:
Number of Locks—15000
Number of Open Partitions—15000
The BMC Remedy AR System 8.1 installer optimizes SQL calls for installation on Sybase. Therefore, a larger number of LOCKS must be configured for the database.
For more information about the LOCKS setting, see your Sybase documentation.
- To prevent the transaction log from filling up during installation, set the
trunc log on chkptdatabase option on the following databases:
- BMC Remedy AR System database
Use the following commands:
sp_dboption databaseName, 'trunc log on chkpt', true
After successful installation and before any production activity, disable the
trunc log on chkptoption for all databases.
- If you are using Sybase 15, ensure that the
number of open partitionsparameter is set appropriately.
For more information, see your Sybase documentation.
- If you plan to install the BMC Atrium CMDB Product Catalog or any BMC Remedy ITSM application, make the following changes:
- Set the
Number of Open Objectsto 30000.
- Set the
Number of Open Indexesto 15000.
- Increase the size of
tempdb. (You might have to create another device.)
- Set the
If you do not have DBA privileges, your database administrator must create an empty database so that you are not asked for database information during the installation.
Create a device; for example:
use master go disk init name='ARSystem_data', physname='/data1/ardata/ ARSys', size='1024M' go disk init name=' ARSystem_log', physname='/data1/ardata/ARSysLog', size='500M' go
Create the database; for example:
create database ARSystem on ARSystem_data=1024 log on ARSystem_log=500 with override go use master go
Create the logon with a password; for example:
sp_addlogin 'ARAdmin', 'AR#Admin#' go
Create the db_owner group; for example:
sp_addgroup db_owner go grant all to db_owner go
Create the user pointing to the created logon and group; for example:
sp_adduser 'ARAdmin', 'ARAdmin', db_owner go use master go
Modify the logon to make its default database the previously created database; for example:
sp_modifylogin ARAdmin, defdb, ' ARSystem' go use ARSystem go
Change the owner of the database to the created user; for example:
sp_changedbowner 'ARAdmin' go use master go
Add the select into option to the created database; for example:
sp_dboption 'ARSystem','select into',true go
Use the created database; for example:
use ARSystem go
By default, Sybase does not work with forms that have more than 254 fields. Because some forms have more than 254 fields at the time of installation, or can be expanded to have more than 254 fields during an integration with another application, you might receive an error message similar to the following example when you install the application on Sybase:
552 Failure during SQL operation to the database Number of variable length columns exceeds limit of 254 forallpage locked tables. ALTER TABLE for 'T566' failed
If this failure occurs during an integration, you might also receive a message similar to the following example:
303 Form does not exist on server SIT:Site Group
This issue occurs when the integration process adds fields to a form (using the
ALTER TABLE command) and the addition increases the number of fields to more than 254. In this case, Sybase rolls back the change and drops the original table, resulting in further installation errors because additional dependencies fail to import.
Form:NTE:SYS-Group NT Control Clause: lock datarowsForm:NTE:SYS-NTUnProcessedRecords Clause: lock datarowsForm:NTE:SYS-NT Process Control Clause: lock datarowsForm:CHG:Infrastructure Change Clause: lock datarowsForm:SRM:Request Clause: lock datarowsForm:SRM:RequestApDetailsSignature Clause: lock datarowsForm:SRM:RequestInterface Clause: lock datarowsForm:HPD:Help Desk Clause: lock datarows