%META:TOPICPARENT{name="ErrorMessagesC"}%
==Error Messages (C)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

===Cursor name starting with 'CURSOR' (-32000)===

"Cursor name starting with 'CURSOR' (-32000)" is an Ingres II error. It is associated with an internal name conflict, which occured when an application issued a <nop>SQLSetCursorName() call to set a cursor name. "CURSOR.2" was generated, and the error occured. While CURSOR.2 is a valid Ingres 6.4 cursor name, Ingres II does not accept this naming convention.

Finally, this exceedingly rare error was addressed with a patch to a 3.2 Ingres II agent on VMS. This patch disabled <nop>SQLSetCursorName() at the database agent level. If you experience this problem, be sure to contact <nop>OpenLink Product Support to see if such a patch is available for you.
    
===Evidence===

Database Agent Version String (All Platforms)
DBMS Version
ODBC Client Trace