Vsam Catalog Return Code Is 8 - Reason Code Is Igg0cleg-42
This usually indicates a synchronization problem with the database. SQL Error Code -805 DBRM OR PACKAGE NAME location-name.collection-id.dbrm-name.consistency-token NOT FOUND IN PLAN plan-name. Some, but not all, of the lines configured on the device have successfully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. his comment is here
REASON CODE reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name.Suggestion: Review DB2 Master Log to find process holding DB2 locks. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco recommends that you restart the Cisco CallManager service. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ichd100/ich2d100352.htm
Vsam Catalog Return Code Is 8 - Reason Code Is Igg0cleg-42
No action is required if this event was issued as a result of a normal device rehome. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact the Cisco Technical Assistance Center (TAC). 2 NoEntryInDatabase - (MGCP only) The device is not configured Verify that the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header.
Recommended ActionIn the Cisco Unified Reporting tool, check the Active Services section of the Unified CM Cluster Overview report to confirm that any failover/fallback scenarios have completed. SQL Error Code -181 THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE.Suggestion: Verify data format with the SQL Reference Guide. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Idc3009i Return Code 50 Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC). 26 InvalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the
Unified CM will use this user ID to attempt to find the device in the configuration database. 21 DigestChallengeTimeout - (SIP only) A SIP device requiring digest authentication sent a REGISTER Vsam Catalog Return Code Is 48 No rollback. -922 Authorization needed. -924 DB2 Connection internal error. -927 The language interface was called but no connection had been made. -998 Error occurred during transaction or heuristic processing. If this is a Cisco IP phone, the configuration may be out-of-sync. September 2013.
Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, which causes the phone to rehome to the primary Idcams Return Codes If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting checkbox is not checked). 30 DBAccessError - Device registration failed because of an error that occurred while building the station registration profile. If the device is a third-party SIP device, verify that the digest credentials configured on the phone match the Digest Credentials configured in the End User Configuration page. 11 InvalidX509NameInCertificate -
Vsam Catalog Return Code Is 48
Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. Vsam Catalog Return Code Is 8 - Reason Code Is Igg0cleg-42 If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. Vsam Catalog Return Code Is 68 If there is a firmware load ID configured on the Phone Configuration page, verify that the firmware load ID exists on the TFTP server (on the Cisco Unified OS Administration page,
Possible causes include a change in the IP address or port of the device. this content For all other devices, this reason code means that DNS lookup failed. If cursor is declared SENSITIVE STATIC SCROLL, the row may be a hole, from which no values can be fetched. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. 29 AutoRegisterDBError - Auto-registration of a device failed because auto-registration is not allowed for Vsam Catalog Return Code Is 48 - Reason Code Is Igg0clfo-28
REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name.Suggestion: Review DB2 Master Log to find process holding DB2 locks. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist. 16 DeviceNotActive - The device has not been activated 17 AuthenticatedDeviceAlreadyExists - A There may be an attempt by unauthorized devices to register. 18 ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. weblink Also, refer to the reason code descriptions in this alarm for additional recommended actions.
In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM Igd17103i In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of a device registering and unregistering; if duplicate registration requests continue or if the SQL Error Code -922 AUTHORIZATION FAILURE: error-type ERROR.
Check the Security profile of the indicated device and verify that the Device Security Mode is set to either Authenticated or Encrypted.
Recommended ActionActions to take vary depending on the reason specified in this alarm for the device unregistration. rt: return-code, rs: reason-code, msg: message-token -682 field procedure procedure-name could not be loaded -683 the specification for column, distinct type, function, or procedure data-item contains incompatible clauses -684 the length If this alarm continues to occur after the manual reset, there may be a protocol error. Iec331i It is also possible to get this error if the Unified CM node is experiencing high CPU usage.
If unregistration of this device was expected, no action is required. Reason Code - Enum Definitions Enum Definitions - LocalApplicationID Value Definition 100 CallManager Enum Definitions - RemoteApplicationID Value Definition 100 CallManager Error Message UC_CALLMANAGER-1-CMVersionMismatch : One or more Unified CM nodes If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. check over here When DB2 executes SQL statements, it returns the results of the operation into the SQLCODE and SQLSTATE fields in the SQLCA.
Verify that the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can The registration profile of the device did not get inserted into the database in time. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. SQL Return Code +347 THE RECURSIVE COMMON TABLE EXPRESSION name MAY CONTAIN AN INFINITE LOOP.Suggestion: Verify predicate in the SQL WHERE clause of the form "counter_col < constant" or "counter_col <
Verify that the X.509 Subject Name field has the appropriate information. SQL Error Code -818 THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM z.Suggestion: Recompile and BIND the DB2 program. Reason Code - Enum Definitions Enum Definitions - DeviceType Value Definition 1 CISCO_30SP+ 2 CISCO_12SP+ 3 CISCO_12SP 4 CISCO_12S 5 CISCO_30VIP 6 CISCO_7910 7 CISCO_7960 8 CISCO_7940 9 CISCO_7935 12 CISCO_ATA_186 If this alarm persists, verify that the appropriate number of lines has been configured on the device, and that the appropriate directory numbers have been configured.
Contact DBA to check DB2 authorizations. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC. 2 NoEntryInDatabase - (MGCP only) The device is not configured in the Unified CM Administration Rollback has been done. -913 Deadlock or timeout. SQLCODE provides key information about the success or failure of SQL statement execution.
Incomplete registration may indicate that a device is rehoming in the middle of registration. reason code=reason-code -697 old or new correlation names are not allowed in a trigger defined with the for each statement clause. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist. 16 DeviceNotActive - The device has not been activated 17 AuthenticatedDeviceAlreadyExists - A
If it does not match, delete the phone and add a new one with the correct Product Type. No action is necessary. Verify correct LOAD library is being used. Also check for any alarms that might have indicated a CallManager failure and take appropriate action for the indicated failure.
Resetting the device may help because it forces the device to download its latest settings.