March 8, 2013 at 4:36 pm
This has been driving me crazy. I'm querying an Oracle db using an OLE DB source tool connected through the Oracle Provider for OLE DB. The query works completely fine in PL/SQL and I'm able to preview the results in the OLE DB source editor but when I run the package, I get the following error:
An OLE DB error has occurred. Description: "ORA-00907: missing right parenthesis".
Get Data failed validation and returned validations status "VS_ISBROKEN"
I was able to run the package without an error before when I had ACCT_DT = PROD_DT but when I changed it to AND ACCT_DT = (PROD_DT + 1-EXTRACT(DAY FROM prod_dt)) I keep getting the error. So I'm guessing it has to do with that but I'm definitely not missing a parenthesis and it runs fine directly using PL/SQL.
Here's a simplified version of the query:
SELECT
FEE_TYPE_CD
,SUM(AppliedVolume) AS AppliedVolume
FROM (
SELECT TRIM(FEE_TYPE_CD) AS FEE_TYPE_CD
,SUM(APPLIED_VOL) AS AppliedVolume
FROM QRMTIPS.QPOST_SETTLE_FEE
WHERE TO_CHAR(PROD_DT, 'YYYY') >= '2010'
AND ACCT_DT = (PROD_DT + 1-EXTRACT(DAY FROM prod_dt))
GROUP BY FEE_TYPE_CD
UNION ALL
SELECT
FEE_TYPE_CD AS FeeTypeCode
,SUM(TRANS_VOL) AS AppliedVolume
FROM QRMTIPS.QPOST_RPTS_INVOICE_DTL a
WHERE TO_CHAR(PROD_DT, 'YYYY') >= '2010'
AND PLANT_NO = 'ALL'
AND ACCT_DT = (PROD_DT + 1-EXTRACT(DAY FROM prod_dt))
GROUP BY FEE_TYPE_CD
)
GROUP BY FEE_TYPE_CD
ORDER BY FEE_TYPE_CD
Please help! Any suggestions?
March 8, 2013 at 7:01 pm
Nevermind, I had --acct_dt = prod_dt commented out in the statement, which runs in PL/SQL but not SSIS.
July 13, 2018 at 12:20 am
I know this topic is a little bit outdated, but it can be useful for later searches. I have run into the same problem. My resolution was to take the timestamp fields into a trunc(*timestamp*) function. In this case ACC_DT or PROD_DT or both is a timestamp field, not date. In database developer tools like DbVis, HORA or else it runs fine, but SSIS is a complicated one... 🙂
Hope it helps,
Loránd
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply