This content has been marked as final. Show 11 replies
Can you create one procedure as given below
command on target
raise ("\n\n\n\n <%=odiRef.getInfo("SRC_DSERV_NAME")%> \n\n\n\n\n")
Command on source
technology : oracle
logical schema: select the source logical schema for source data server where you have given the dblink name
no code is required here. leave it blank.
Now save and run it. go to operator to check whether the dblink name is coming or not.
Still no luck in KM. I've also tried the procedure and it reports the correct dblink.
Further invistigation showd that even though that stage and source datastores are different, ODI creates a synonym on the staging area for a view that exists at the source datastore. Strange !!!!
Any suggestions please, becuase I'm stuck !!!
Thank you for your syggestion on Uli's solution.
We still need to use ODI's out-of -the-box solution. I recap by posting the simumated Task
Task Type : C
Task Name 1: Loading
Task Name 2: SrcSet0
Task Name 3: Create database link on target
Exe Channel: J
Source Context Code: PRODUCTION
Source Logical Schema Name: L-SOURCE
Source Connection Name:
Source Commit Indicator:
Source Isolation Level:
Source Plan Comp: 0
Source Technology Internal Name: ORACLE
Target Context Code: PRODUCTION
Target Logical Schema Name: L-ODI
Target Connection Name:
Target Commit Indicator:
Target Isolation Level:
Target Plan Comp: 0
Target Technology Internal Name: ORACLE
Default Command (Destination):
create database link
identified by "<@=snpRef.getInfo("SRC_PASS") @>"
and pointing out that in other tasks I have'd seen any substitution api commands, but only SQL commands.
Any ideas, or suggestions. Are we doing something wrong here, or have we stumbled in a bug ?