Unable to import metadata of flat files by using IA

arvind_ds · Post by **arvind_ds** » Tue Jun 16, 2015 8:51 am

Hi Experts,

Getting below error while trying to import metadata of flat files in information analyzer. Flat files are located on datastage server itself.

Error Message : "Failed while importing". Please see log files for details.

I browsed to webconsole to the below path and this is what I got in the Log views.

Webconsole --> Administration --> Log Management --> Log Views -->IA_With_CAS_Log --> View Log

Log Views:

An exception was received from the handler: ODBC function "
SQLPrimaryKeys" reported:SQLSTATE = 74: Native Error Code = 0:
Msg = 523 72

Fatal error message received from the native (C++) layer:
CC_OdbcMetadataHelper::describePrimaryKeys, file CC_OdbcMetadataHelper.
cpp, line 3187

Please share your inputs on how to fix this issue.

arvind_ds · Post by **arvind_ds** » Tue Jun 16, 2015 9:25 am

Found the below technote but it didn't resolve the reported issue.

http://www-01.ibm.com/support/docview.w ... wg21395196

ray.wurlod · Post by **ray.wurlod** » Tue Jun 16, 2015 4:24 pm

Have you tried importing using Metadata Asset Manager?

Have you used the "discover flat file" option in the IA tasks menu, which builds/maintains the QETXT.INI file?

arvind_ds · Post by **arvind_ds** » Wed Jun 17, 2015 3:39 am

I have used "identify flat files" option in IA tasks menu which is populating QETXT.INI correctly.

I tried to import through metadata asset manager but got the same error as mentioned below.

Errorx [CDIMR3790E] An error occurred while importing data from bridge or connector (CAS/ODBCConnector__3.5). ([CDIMR3857I] Additional import error details may be found in the Import Log.) [CDIMR0071E] There was an error querying the PMR|3.txt table. ODBC function "SQLPrimaryKeys" reported: SQLSTATE = 74: Native Error Code = 0: Msg = 523 72+Details
com.ibm.mif.ChannelException: [CDIMR0071E] There was an error querying the PMR|3.txt table. ODBC function "SQLPrimaryKeys" reported: SQLSTATE = 74: Native Error Code = 0: Msg = 523 72
Caused by:com.ascential.asb.cas.shared.ConnectorServiceException: ODBC function "SQLPrimaryKeys" reported: SQLSTATE = 74: Native Error Code = 0: Msg = 523 72 OK

Any idea about this error? Please share your inputs.

Mike · Post by **Mike** » Wed Jun 17, 2015 6:01 am

arvind_ds wrote:error querying the PMR|3.txt table.

Special character in your text file name?

Try escaping the special character: PMR\|3.txt

Mike

arvind_ds · Post by **arvind_ds** » Wed Jun 17, 2015 6:42 am

Thank you for your response Mike.

There is no special character in the file name. The file name is 3.txt

ray.wurlod · Post by **ray.wurlod** » Wed Jun 17, 2015 3:34 pm

Can you try renaming the file, perhaps to A3.txt ? ODBC in particular does not like identifiers beginning with numeric characters.

arvind_ds · Post by **arvind_ds** » Thu Jun 18, 2015 4:03 am

Same error even after renaming the file to A3.txt

IA identified both the files 3.txt as well as A3.txt (through identify flat file feature). Then I clicked on identify next level option in IA and it also worked fine but when I clicked on "Import" button, I got the same error which was reported in the beginning of this thread.

ray.wurlod · Post by **ray.wurlod** » Thu Jun 18, 2015 6:03 pm

When you ran through the identify flat file process, did you specify any field(s) as primary key? The error is being thrown by the SQLPrimaryKey() function in the ODBC API, the purpose of which is to identify whether a column is a primary key or not. It really should not throw an error if no primary key column exists.

arvind_ds · Post by **arvind_ds** » Fri Jun 19, 2015 6:42 am

I didn't find any option to mark any column as primary key while using "Identify flat file" option in information analyzer.

ray.wurlod · Post by **ray.wurlod** » Sat Jun 20, 2015 12:25 am

Then I think it's time to involve your official support provider.

stuartjvnorton · Post by **stuartjvnorton** » Sun Jun 21, 2015 5:50 pm

Shot in the dark here.
Can you restart the NodeAgents?

Whenever I've had CAS issues in the past, restarting the NodeAgents has fixed it for me.

arvind_ds · Post by **arvind_ds** » Mon Jun 22, 2015 5:59 am

Thanks for your inputs experts. I even tried to re-start the services(WAS, Agents, datastage engine) but it didn't work.

I will raise a ticket with IBM and will update this thread later.

stephenlrobson · Post by **stephenlrobson** » Fri Jun 30, 2017 11:55 am

Was this issue ever resolved? I'm having an eerily similar issue on 11.3.1.2.

Thanks
Stephen