APAR status
Closed as program error.
Error description
While trying to import metadata from Sybase server using the ODBC Connector in IA, the following error is thrown in the IA logs "Catalogue procedure SP_Pkeys cannot be run in a transaction."
Local fix
This works fine while importing the Metadata using the ODBC Connector in the Datastage Designer. Import through data stage and shared meta data with IA
Problem summary
Trying to import metadata from Sybase in IA recieves error: "Catalogue procedure SP_Pkeys cannot be run in a transaction." The MDI using the ODBC Connector works fine through the Datastage Designer. This message is seen in the CAS logs <Message><![CDATA[ODBC function "SQLPrimaryKeys" reported: SQLSTATE = HY000: Native Error Code = 18,040: Msg = [IBM (DataDirect OEM)][ODBC Sybase Wire Protocol driver] [SQL Server]Catalog procedure 'sp_pkeys' can not be run in a transaction.]]></Message>
Problem conclusion
Since the Sybase Database does not allow calling of the Stored Procedure SQLPrimary Keys in a transaction, we should explicitly set the Auto Commit mode.
Temporary fix
Import the Metadata using the Information Server Designer and share the Metadata
Comments
APAR Information
APAR number
JR46217
Reported component name
WIS INFORM ANAL
Reported component ID
5724Q36IA
Reported release
870
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-02
Closed date
2013-04-15
Last modified date
2013-04-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS INFORM ANAL
Fixed component ID
5724Q36IA
Applicable component levels
R870 PSY
UP
R910 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSZJLG","label":"InfoSphere Information Analyzer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7"}]
Document Information
Modified date:
12 October 2021