Abhijeet,
There were several patches for SLA 6, which addressed a number of issues.
Patch 1537 (readme attached) is a cumulative patch which also addresses bug
fixes for patch 1456 and 1498. The problem you are seeing may be related to
one or more of these bugs.
HTH
Leonard Neely
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Abhijeet N Raut
Sent: Friday, April 24, 2009 8:55 AM
To: [email protected]
Subject: Problem In SLA Deployment
**
Hello All ,
Kindly help me with the following issue
Issue Summary:
Problem In SLA Deployment ( SLA in not properly getting built when you
deploy it). So as mail should go to the desired Group when SLA is met.. is
not going.
Issue Details:
When we are Deploying SLA, the filter need to be created as per the
milestones is not getting built and so as it is not sending the mail to the
desired mail group. Also SLA built messages is not giving any error, its
blank.
Kindly let me know what could be for the issue and what need to be done in
order to get out of this error.
Server Version : 6.3
SLA Version 6.0 with No patch.
Opreting System - AIX
Database - DB2
=============================================
Thanks and Regards
Abhijeet Raut,
============================================= _Platinum Sponsor:
[email protected] ARSlist: "Where the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
Product: Remedy Service Level Agreements
Version: 6.0
Patch #: Patch 1537
Patch Type: Cumulative (includes fixes from Patch 1456, and Patch 1498)
Release Date:
Software Platforms: All
Bugs fixed in patch 1456:
SW00223628 MeasStdStart_Filter1 filters show two different values for
'ParentStartTime' in the push fields action, where it should only show one
value being pushed to 'ParentStartTime'
Bugs fixed in patch 1498:
SW00242606 When the License Information string exceeds 80 character length
it throws error as the Input length for License Information Field is 80 in 3
forms; SLA:Actions, SLA:Main, and SLA:MainConsole
SW00235722 Elapsed Time values are not being calculated on the
SLA:Measurement record for Availability SLAs.
SW00239567 The report Service Level Agreementes==>General==>SLA Milestones
does not have a value in the Ticket ID column.
SW00243213 SLA 6.0 If you import an SLA with submitter mode locked and
then try to modify it you get a 371 error
SW00234454 BRIE die during build since we've passed a NULL pointer to
'sprintf' in function "Workflow::DeleteOMFObjectActions(
SW00234494 SLA 6.0 - create a milestone with 255 char message gives ARERR
306
SW00242017 performance drop for SLA 6.0 build
SW00242019 OR SW00228694 SLA 6.0 - 'brsvcbrie' service does not honour the
'Connect-Server-Name:' ar.conf setting
SW00221181 PATCHED The number of filters in a SLA are reduced after the
SLA is imported (Fixed: SLA Export now works with AssocStop and Team
Measurement filters)
SW00224673 Exporting 1 SLA takes 32 minutes to complete. Incorrect SQL
beeing generated causes a lookup against all the entries. (Fix: Take out
pre-cache for Association table)
SW00231765 ARERR [353] You have no access to form: SLA:Notifier when
accessing Alerts sent by SLA.
SW00247408 Two SLAs in a group, when the second attaches, the milestones
are being deleted along with the first SLA milestones (SLAs in a group scenario
does not create Milestones when using Reference Start Time)
Bugs fixed in patch 1537:
SW00236045 (AR 7.0 Only) Saving SLA gives error "ARERR [382] The value(s)
for this entry violate a unique index that has been defined for this form" and
SLA is not Saved.
No Bug Id Command line options for arimportcmd have changed in AR System
7.0. This makes the import utility for SLA work incorrectly. It may overwrite
some existing records during import.
This needs a change in the arimport command syntax used within
the SLA Import/Export dll (omfobjiefilapi.dll)
Install Instructions
====================
Perform the following steps to install this patch.
1. Stop AR System service.
2. From your SLA install directory/bin, backup your original 'brsvcbrie' and
'omfobjiefilapi' binary - copy it to another directory or rename it.
3. Copy brsvcbrie and omfobjiefilapi from patch folder to this bin directory.
4. Restart AR System.
5. Copy Patch1498.def to the local drive
6. Use the Remedy Administrator to import the def file with the option "Import
In Place" checked
7. User AR Import tool to import SHARE%AssociationType_SLA60.arx to form
SHARE:AssociationType
8. User AR Import tool to import SHARE%AssociatonType_Object_SLA60.arx to form
SHARE:AssociationType_Object
9. Re-save the SLA you want to export. (the patched workflow will allow export
the AssocStop and TeamAssignment filters)
10.Export the SLA.
11.Make field length changes to the following:
Form: SLA:Set Value Item_base
Field: SLA_Field Value Expression - 500000100 -> change to DB Length of 0
Form: SLA:Clone Base
Field: SLA_Field Value Expression - 500000100 -> change to DB Length of 0
Form: SLA:Notifier
Field: SLA_NotificationSubject - 300445100 -> change to DB Length of 0
12. If you are upgrading from AR 6.3 with SLA 6.0 to AR 7.0:
a. After you export a SLA.
b. If the lines "CHAR-SET windows-1252" exist on the .arx data file, please use
any text editor to remove them.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
