Dear community,
at university we try to process the Integration Education Package. Therefore we want to use the exisiting JDBC-Adapter-Services from the CampusConnect-Package, but all service, which are using mutliple tables throw an error.
The following error occurs:
com.wm.pkg.art.error.DetailedSystemException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service CampusConnect.adapters.Courses:selectCourseExamsForStudent.
[ADA.1.316] Cannot execute the SQL statement "SELECT ExamID,StudentID,Regdate,Grade FROM CampusConnect.dbo.Students_Courses, CampusConnect.dbo.Exams, CampusConnect.dbo.Students_Exams WHERE (t1.CourseID = t2.CourseID AND t2.ID = t3.ExamID) AND (CourseID = ? AND StudentID = ? AND StudentID = ?) ". "
(HY000/4104) [SoftwareAG][SQLServer JDBC Driver][SQLServer]The multi-part identifier "t1.CourseID" could not be bound.
(HY000/4104) [SoftwareAG][SQLServer JDBC Driver][SQLServer]The multi-part identifier "t2.CourseID" could not be bound.
(HY000/4104) [SoftwareAG][SQLServer JDBC Driver][SQLServer]The multi-part identifier "t2.ID" could not be bound.
(HY000/4104) [SoftwareAG][SQLServer JDBC Driver][SQLServer]The multi-part identifier "t3.ExamID" could not be bound.
(HY000/209) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Ambiguous column name 'CourseID'.
(HY000/209) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Ambiguous column name 'StudentID'.
(HY000/209) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Ambiguous column name 'StudentID'.
(HY000/209) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Ambiguous column name 'StudentID'.
(HY000/209) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Ambiguous column name 'Regdate'.
(HY000/8180) [SoftwareAG][SQLServer JDBC Driver][SQLServer]Statement(s) could not be prepared."
[SoftwareAG][SQLServer JDBC Driver][SQLServer]The multi-part identifier "t1.CourseID" could not be bound.
In our opinion the generated SQL-Statement is not valid, because the table-aliases (Exams t2, Student_Courses t3) are missing.
We also tried to create an own JDBC-Adapter. If we choose the template CustomSQL and write our own join statement it works fine, otherwise the equivalent error message occurs.
Thanks for advice.