Clarity Service Management

Expand all | Collapse all

[JasperStudio] - AHD:12008 Error on SDM Data Adapter

  • 1.  [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 04-21-2017 06:08 AM
      |   view attached

    Hello Good Morning,

     

    After set up Jasper Studio Data Adapter to my SDM instance, and even restarted the SDM as well as JasperServer, i still got the error :

     

    java.sql.SQLException: [DataDirect][OpenAccess SDK JDBC Driver][OpenAccess SDK SQL Engine]AHD12008:Attribute OA_DEFERRABILITY referenced by Majic SQL query not found in object(s)  OA_FKEYS at OA_DEFERRABILITY ... AS

     

    Any idea?

     

     

    FULL ERROR DESCRIPTION:

    java.sql.SQLException: [DataDirect][OpenAccess SDK JDBC Driver][OpenAccess SDK SQL Engine]AHD12008:Attribute OA_DEFERRABILITY referenced by Majic SQL query not found in object(s) OA_FKEYS at OA_DEFERRABILITY ... AS
    at com.ddtek.openaccess.ssp.Diagnostic.toSQLException(Unknown Source)
    at com.ddtek.openaccess.ssp.Chain.cnvDiagnostics(Unknown Source)
    at com.ddtek.openaccess.ssp.Chain.decodeDiagnostic(Unknown Source)
    at com.ddtek.openaccess.ssp.Chain.decodeBody(Unknown Source)
    at com.ddtek.openaccess.ssp.Chain.decode(Unknown Source)
    at com.ddtek.openaccess.ssp.Chain.send(Unknown Source)
    at com.ddtek.openaccess.ctxt.stmt.StatementContext.execRsn(Unknown Source)
    at com.ddtek.jdbc.openaccess.OpenAccessImplStatement.execute(Unknown Source)
    at com.ddtek.jdbc.oabase.BaseStatement.commonExecute(Unknown Source)
    at com.ddtek.jdbc.oabase.BaseStatement.executeQueryInternal(Unknown Source)
    at com.ddtek.jdbc.oabase.BaseStatement.executeDatabaseMetaDataQuery(Unknown Source)
    at com.ddtek.jdbc.oabase.BaseDatabaseMetaData.getImportedKeys(Unknown Source)
    at com.jaspersoft.studio.data.sql.ui.metadata.MetaDataUtil.readForeignKeys(MetaDataUtil.java:215)
    at com.jaspersoft.studio.data.sql.ui.metadata.MetaDataUtil.readTableKeys(MetaDataUtil.java:179)
    at com.jaspersoft.studio.data.sql.ui.metadata.DBMetadata$9.run(DBMetadata.java:325)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)



  • 2.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 04-21-2017 07:44 AM

    SteveTroy may be able to help here... @Steve have you seen this error in any of the setups you have come across?



  • 3.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 04-21-2017 09:45 AM

    What's the Query?



  • 4.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 04-21-2017 10:38 AM

    can be a simple "select * from casd."in" " ...

     

    from the SD server, it also logs errors:

     

    04/21 15:29:44.64 [server_name] domsrvr 10332 ERROR sqlquery.c 2311 AHD12008:Attribute OA_DEFERRABILITY referenced by Majic SQL query not found in object(s) OA_FKEYS
    04/21 15:29:44.64 [server_name]  web:local 9464 ERROR odbc_backend.c 153 ODBC error: AHD12008:Attribute OA_DEFERRABILITY referenced by Majic SQL query not found in object(s) OA_FKEYS at OA_DEFERRABILITY ... AS



  • 5.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 04-24-2017 10:11 AM

    Please be more specific with the SQL you are trying.  

     

    The following query works in my system:  

     

    select ref_num from casd."in" where active = '1'



  • 6.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 06-22-2017 11:00 AM

    I would like to know if this inconvenience has been solved. We are affected by the same error.

    Regards,

    JOHN



  • 7.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 01-10-2019 10:01 AM

    We have resolved it. The user connecting had not enough privileges in CA SDM. That's the reason for this error.



  • 8.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 01-10-2019 09:57 AM

    We have the same issue, did you manage to solve it?



  • 9.  Re: [JasperStudio] - AHD:12008 Error on SDM Data Adapter

    Posted 01-10-2019 10:01 AM

    We have resolved it. The user connecting had not enough privileges in CA SDM. That's the reason for this error.