This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

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.

Note

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.

To configure your Sybase database

  1. 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.

    Note

    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.

  2. Install Sybase clients.
    For remote installations, install on the same computer as the BMC Remedy AR System server is installed on.
  3. From the directory on which the 64-bit Sybase client is installed, source the database:
    ../SYBASE.sh
  4. Ensure that TCP/IP is enabled for the database.
  5. Verify or set the DSQUERY and SYBASE environment variables as follows:
    DSQUERY=SybaseServer; export DSQUERY
    SYBASE=SybaseInstallDirectory; export SYBASE
    These examples use the syntax for Bourne shell.
  6. (UNIX only) Verify or set the LANG environment variable.
  7. If you are upgrading from BMC Remedy AR System 7.1.00 to 8.1, set the Select into database option for the database that you are upgrading.
  8. Ensure that your database can accept network communication using the parameters entered during the installation.

    Tip

    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.

  9. Change the minimum page size to 8 KB.
    For information about increasing the page size, see your Sybase documentation.
  10. Increase the default tempdb size to 600 MB.
  11. 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. 
  12. If the database is configured to extend automatically, perform the following actions:
    1. Set the BMC Remedy AR System data file size to 3 GB or larger.

      Note

      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.

    2. Set the log file size to 2 GB or larger.
    3. 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
  13. Set the following Sybase database configuration parameters:
    • Max Memory—128000
    • 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.
  14. 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
    • tempdb
      Use the following commands:
      sp_dboption databaseName, 'trunc log on chkpt', true
      go

      Note

      After successful installation and before any production activity, disable the trunc log on chkpt option for all databases.

  15. If you are using Sybase 15, ensure that the number of open partitions parameter is set appropriately.
    For more information, see your Sybase documentation.
  16. 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 Objects to 30000.
    • Set the Number of Open Indexes to 15000.
    • Increase the size of tempdb. (You might have to create another device.)

Pre-creating a database

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.

To pre-create a Sybase database

  1. 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
    
  2. Create the database; for example:

    create database ARSystem on  ARSystem_data=1024 log on ARSystem_log=500 with override
    go
    
    use master
    go
  3. Create the logon with a password; for example:

    sp_addlogin 'ARAdmin', 'AR#Admin#'
    go
  4. Create the db_owner group; for example:

    sp_addgroup db_owner
    go
     
    grant all to db_owner
    go
  5. Create the user pointing to the created logon and group; for example:

    sp_adduser 'ARAdmin', 'ARAdmin', db_owner
    go
    
    use master
    go
  6. Modify the logon to make its default database the previously created database; for example:

    sp_modifylogin ARAdmin, defdb, ' ARSystem'
    go
     
    use ARSystem
    go
  7. Change the owner of the database to the created user; for example:

    sp_changedbowner 'ARAdmin'
    go
     
    use master
    go
  8. Add the select into option to the created database; for example:

    sp_dboption 'ARSystem','select into',true
    go
  9. Use the created database; for example:

    use ARSystem
    go

Forms with more than 254 fields

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.

Workaround

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

Related topic

Preparing to install on a Unicode database


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments