This section describes the general problems that you might encounter when you declare a record. These problems are common to all of the clients integrated with Content Manager Records Enabler.
Problem: If you use a DB2 Content Manager client and select an item and click Declare, the declaration page is displayed. You can switch profiles if you have the use permissions defined in the IBM® Records Manager Administration client for more than one profile. A new record is successfully declared in IBM Records Manager, but the item is not marked as a record in DB2 Content Manager.
Resolution: Add the RecHsID and XtRecID fields into the profiles in the IBM Records Manager administration client. Then, you can use the profiles when you declare items from a DB2 Content Manager client.
Problem: During the record declaration process, you get an ICM7015 unexpected SQL error when attempting to create an item in an eRecords-enabled item type.
Possible causes: You attempted to set a DB2 Content Manager attribute, such as eRecord, to an invalid value.
Resolution: Make sure you are not trying to set the eRecord attribute to a setting other than aut or no. If you are using DB2 Document Manager, then the eRecord attribute could be listed in the dialog box that can cause the above error condition.
Problem: During the record declaration process, when the user clicks the Classification icon, the user cannot access some or all of the file plan codes.
Possible causes: The current user is either not authorized to access the file plan code or the current user is a new user and there are currently no access permissions assigned to the user for any of the file plan codes.
Resolution: Log on to IBM Records Manager as a records administrator and assign the appropriate file plan component access permissions to the current user.
A component named 'xxxxxx' already exists in the selected classification.
Possible causes: Another record that has the same document or component name already exists in the same classification or file plan category.
Resolution: Change the document name and try declaring the record again.
DGL3819A: User does not exist [Name=...]
Possible causes: The user was removed from the DB2 Content Manager library server, but the user was imported into IBM Records Manager and was not removed.
Resolution: The user needs to be removed from IBM Records Manager first before deleting it from the DB2 Content Manager library server.
Problem: The Web browser displays a Page not found error when you try to declare a record from the Notes®, Outlook, eClient, Client for Windows®, or DB2 Document Manager.
Possible causes: The Content Manager Records Enabler servers are not running.
Resolution: Restart the Content Manager Records Enabler server (cmresvr) and the host interface server (rmecmhost). See Restarting Content Manager Records Enabler for information.
Problem: The declare record menu does not show up if the DB2 Content Manager library server database name cataloged in the Content Manager Records Enabler host server and the DB2 Content Manager library server datastore name are different.
Possible causes: The name of the DB2 Content Manager library server database is assumed to be the same as the cataloged name that Content Manager Records Enabler registers on IBM Records Manager.
Resolution: Uncatalog the DB2 Content Manager library server database. Then, catalog it again and ensure that the alias is the same as the DB2 Content Manager library server database name.
