2014-01-17 2 views
0
Select a.stmt_date,a.*,b.* from ES_CC_STATEMENTS a left outer join ES_STMT_TRANSACTIONS 
b on a.stmt_id = b.stmt_id 
where a.stmt_cc_number = #cc_number AND (stmt_date >= CONVERT(DATETIME, #dateFrom , 
101)) AND (stmt_date < CONVERT(DATETIME, #dateTo , 101)) order by b.txn_date desc 

나는 내가 다음과 같은 오류가 입니다 프로젝트 & 실행 비즈니스 서버 & 삽입 입력 매개 변수를 배포 할 때 OSB11g에서 비즈니스 서비스 건설 장 & 가지고 JDeveloper를 DB 어댑터에서이 쿼리를 작성 있습니다잘못된 열 이름 'txn_date'

The invocation resulted in an error: Invoke JCA outbound service failed with 
application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: 
oracle.tip.adapter.sa.api.JCABindingException: 
oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: 
servicebus:/WSDL/OSB%20DB%20Adapter/adapter/Jdev_OSB_DBAdapter/test_es_cc_STMT_new [ test_es_cc_STMT_new_ptt::test_es_cc_STMT_new(test_es_cc_STMT_newInput_msg,test_es_cc_STMT_n 
ewOutputCollection) ] - WSIF JCA Execute of operation 'test_es_cc_STMT_new' failed due 
to: Pure SQL Exception. 

Pure SQL Execute of Select a.stmt_date,a.*,b.* from ES_CC_STATEMENTS a left outer join 
ES_STMT_TRANSACTIONS b on a.stmt_id = b.stmt_id where a.stmt_cc_number = ? AND 
(a.stmt_date >= CONVERT(DATETIME, ? , 101)) AND (a.stmt_date < CONVERT(DATETIME, ? , 
101)) order by b.txn_date desc failed. 

Caused by com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 
'txn_date'.. 
; nested exception is: 
BINDING.JCA-11633 
Pure SQL Exception. 
Pure SQL Execute of Select a.stmt_date,a.*,b.* from ES_CC_STATEMENTS a left outer join 
ES_STMT_TRANSACTIONS b on a.stmt_id = b.stmt_id where a.stmt_cc_number = ? AND 
(a.stmt_date >= CONVERT(DATETIME, ? , 101)) AND (a.stmt_date < CONVERT(DATETIME, ? , 
101)) order by b.txn_date desc failed. 

Caused by com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 
'txn_date'.. 
The Pure SQL option is for border use cases only and provides simple yet minimal 
functionality. Possibly try the "Perform an operation on a table" option instead. This 
exception is considered not retriable, likely due to a modelling mistake. To classify 
it as retriable instead add property nonRetriableErrorCodes with value "-207" to your 
deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set 
these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, 
and jca.retry.backoff. All properties are integers. 

답변

0

txn_date이 (가) 테이블 ES_STMT_TRANSACTIONS에 없습니다.

스키마를 제공하면 문제가있는 곳을 쉽게 볼 수 있습니다.

+0

txn_date 열이 테이블 ES_STMT_TRANSACTIONS – user3198223

+0

사용 가능합니다 [정보] GO /****** 대상 :. GO SET ON 표 [DBO] [ES_STMT_TRANSACTIONS] ON SET의 ANSI_NULLS가 GO SET의 QUOTED_IDENTIFIER ANSI_PADDING ON GO 테이블 만들기 [dbo].[ES_STMT_TRANSACTIONS ( \t [TXN_ID] 숫자 (18, 0) NULL NOT, \t [TXN_CREATED_ON] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, \t [TXN_TRANSACTION_TYPE] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, \t [TXN_FLAG_DEBIT_CREDIT] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, \t [TXN_POSTING_DATE] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, – user3198223

+0

[TXN_DESCRIPTION] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, \t [TXN_AMOUNT] varchar] (최대) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, \t [TXT_CURRENCY_CODE] [varchar (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, \t [TXN_FOREIGN_TRANSACTION] VARCHAR (최대) COLLATE SQL_Latin1_General_CP1_CI_AS 데이터 NULL, 는 [STMT_ID] 숫자 (18, 0) NULL, – user3198223