Lookup Table is populated with data even after we truncate the table in Oracle.
Following is the user defined SQL in the Lookup table -
SELECT
Trim(EMPLID) as EMPLID,Trim(PERNR) as PERNR,TRIM(COMPANY_CODE) AS COMPANY_CODE,Trim(RFPRNR) as RFPRNR
FROM #$SCE_SSA_SCHEMA#.#JPM_MSTR_PERNR#
WHERE Trim(EMPLID)=ORCHESTRATE.EMPLID AND
(TRIM(COMPANY_CODE) =ORCHESTRATE.COMPANY_CODE
OR EMPL_RCD=ORCHESTRATE.EMPL_RCD
)
Problem with ORCHESTRATE
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 236
- Joined: Sun Apr 01, 2007 7:41 am
- Location: Michigan
You posted SQL but didn't explain what the problem is.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It might also be a timing issue. After all, what you look up from is not the Oracle table itself, but the virtual Data Set associated with the link. Therefore, if the LUT_CreateOp operator had finished before you truncated the table in Oracle, all of the reference data would still be present in your job. It will disappear from memory when the job finishes.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.