This documentation supports the 9.1 version of Remedy Action Request System.

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

Changing the next available ID for new requests

In this topic:

The Request ID is used to automatically generate the unique index number attached to each BMC Remedy AR System request. Under some conditions, you might need to reset the next available ID. For example, you might need to establish different ranges for a similar form on two different servers, or you might need to reserve a range of numbers for later use.

You must restart the AR System server to see the latest request IDs.

Note

Do not change the next available ID to a number lower than the greatest existing ID. The Request ID field value must be unique within BMC Remedy AR System, and resetting the ID to a lower number could conflict with existing Request ID field values. If you try to submit a request with an existing ID, BMC Remedy AR System returns an error and prevents the request from being submitted until the conflict is resolved.

If you must change the next available ID, change it when the system is not in use to avoid conflicts with users who are submitting new requests.

To change the next available ID for a form in an SQL database

  1. Stop AR System server.
  2. Using any front-end tool that provides direct access to an SQL database, log in as a user with write access to the AR System tables.
  3. Connect to the AR System table area.
  4. Find the Request ID field for the form that you want to modify. The maximum next ID range is 9999999999 (10 digits). We allow five characters for the Request ID field prefix. 
  5. Update the next available ID.
  6. Restart the AR System server.

Database command scenarios for changing the next available request ID

The following scenarios show how to change the next available ID for Oracle, and Microsoft SQL Server databases. In the scenarios, the next available ID for a form named ZZZ is changed from the current value of 1291 to a new value of 25000.

Oracle scenario

% sqlplus
Enter user-name: ARAdmin
Enter password: <password> (AR#Admin# by default.)
SQL>select name, nextId from ARAdmin.arschema where name ='ZZZ';
NAME     NEXTID
------------------------------ ----------
ZZZ     1291
SQL>update ARAdmin.arschema set nextId = 25000 where name = 'ZZZ';
1 row updated.

SQL>Commit;

commit complete

SQL>exit

Microsoft SQL Server scenario

% isql -Usa
Password: <password>
1>use ARSystem
2>go
1>select name, nextId from arschema where name = 'ZZZ'
2>go
name     nextId
ZZZ     1291
------------------------------ ----------
(1 row affected)
1>update arschema set nextId = 25000 where name = 'ZZZ'
2>go
(1 row affected)
1>exit

Note

If you have a form overlay, always update the base form's next ID properties. For example, you can update the query as mentioned below:
update ARAdmin.arschema set nextId = 25000 where name = 'ZZZ' and overlayGroup = '0';


Was this page helpful? Yes No Submitting... Thank you

Comments