Db2 Sql Error Code 203
Contents |
Events Forums DB2-LDB2-L ArchivesNA ConferenceEMEA Conference Resources BlogsIDUG eBulletinIDUG NewsroomCommunitiesRegional User Groups Articles&Content IDUG Content ArticlesTech ChannelBeginner's BlogDB2 Hot Topics BlogContent LibraryIDUG YouTubePast Conference ContentCodeplace Library GetInvolved Volunteering with IDUGVolunteer PositionsJoin a Regional User GroupBecome an IDUG MentorSponsorship OpportunitiesJoin a CommunitySpeaker
Db2 Sql Error Code 803
Community SQl Code of -203 jake anderson SQl Code of -203 May 14, db2 sql error code 811 2012 04:17 AM Dear All, When i try to combine the data from two tablesinvolving Joins it is giving me db2 sql error code 204 the SQl Code of -203 (A reference to the Existing Column is Ambigious). i can see TSOID the column is the common one appering in both the tables.(i.e TB_PROJ_PERSONAL AND TB_PROJ_TRAINING1). http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/p203.html Error : SQLCODE= -203 SQLSTATE=42702 Could anyone please direct me. Regards, Jake Cuneyt Goksu SQl Code of -203 May 14, 2012 04:22 AM (in response to jake anderson) Hi Try to use short names for your tables in FROM Clause and reference your columns with those short names. Such as SELECT A.C1, B.C2 FROM T1 A, T2 B WHERE A.TSOID = B.TSOID Regards, http://www.idug.org/p/fo/et/thread=40599 Cuneyt From: jake anderson [mailto:[login to unmask email] Sent: Monday, May 14, 2012 12:18 PM To: [login to unmask email] Subject: [DB2-L] - SQl Code of -203 Dear All, When i try to combine the data from two tablesinvolving Joins it is giving me the SQl Code of -203 (A reference to the Existing Column is Ambigious). i can see TSOID the column is the common one appering in both the tables.(i.e TB_PROJ_PERSONAL AND TB_PROJ_TRAINING1). Error : SQLCODE= -203 SQLSTATE=42702 Could anyone please direct me. Regards, Jake -----End Original Message----- jake anderson RE: SQl Code of -203 May 14, 2012 04:39 AM (in response to Cuneyt Goksu) Dear Cuneyt, I will try with short names, but out of curiosity any technical reason behind using Short names only ? Jake In Reply to Cuneyt Goksu: Hi Try to use short names for your tables in FROM Clause and reference your columns with those short names. Such as SELECT A.C1, B.C2 FROM T1 A, T2 B WHERE A.TSOID = B.TSOID Regards, Cuneyt From: jake anderson [mailto:[login to unmask email] Sent: Monday, May 14, 2012 12:18 PM To: [login to unmask email] Subject: [D
Events Forums DB2-LDB2-L ArchivesNA ConferenceEMEA Conference Resources BlogsIDUG eBulletinIDUG NewsroomCommunitiesRegional User Groups Articles&Content IDUG Content ArticlesTech ChannelBeginner's BlogDB2 Hot Topics BlogContent LibraryIDUG YouTubePast Conference ContentCodeplace Library GetInvolved Volunteering with IDUGVolunteer PositionsJoin a http://www.idug.org/p/fo/et/thread=17373 Regional User GroupBecome an IDUG MentorSponsorship OpportunitiesJoin a CommunitySpeaker Community SQLCODE -203 No Name Available SQLCODE -203 January 13, 2004 03:11 PM Hello, I am having a http://ibmmainframes.com/about30530.html problem with the below query at BIND time. I am trying to minimize coding, and save extra work when we go to V8, by using the group db2 sql items in the FETCH: FETCH RI_PARENT INTO :DCL-RLIBM :DCL-RLIBM-NI , :DCL-FKIBM :DCL-FKIBM-NI , :DCL-RLWRK :DCL-RLWRK-NI , :DCL-FKWRK :DCL-FKWRK-NI I guess my question, can the parser not figure out something as simple as this, or is there another way around this? DECLARE RI_PARENT CURSOR FOR SELECT * FROM (SELECT * FROM SYSIBM.SYSRELS RL , SYSIBM.SYSFOREIGNKEYS FK db2 sql error WHERE FK.CREATOR = 'COLLA' AND FK.TBNAME = 'TABLE001' AND FK.CREATOR = RL.CREATOR AND RL.RELNAME = FK.RELNAME ) BASE FULL OUTER JOIN (SELECT * FROM SYSIBM.SYSRELS RL , SYSIBM.SYSFOREIGNKEYS FK WHERE FK.CREATOR = 'COLLB' AND FK.TBNAME = 'TABLE001' AND FK.CREATOR = RL.CREATOR AND RL.RELNAME = FK.RELNAME ) TARG ON BASE.RELNAME = TARG.RELNAME AND BASE.COLNAME = TARG.COLNAME ORDER BY BASE.RELNAME, BASE.COLSEQ DSNT408I SQLCODE = -203, ERROR: A REFERENCE TO COLUMN RELNAME IS AMBIGUOUS DSNT418I SQLSTATE = 42702 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNXORSO SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = -525 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'FFFFFDF3' X'00000000' X'00000000' X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION --------------------------------------------------------------------------------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG c