Thursday 21 May 2015

ODI-1519 ERROR


In BIACM,the load plan got failed with ODI-1519.


CAUSE:
END_DATE in BIACM parameter is not high enough.
SOLUTION:
Please check the value of the parameter END_DATE in BIACM.If it is set to DEC 31of 1950,then it needs to set to large/higher value that covers the year 2015(e.g.,set it to Dec 31 of 2050).Once this is re-set,the fix is noticed in the next run.

how to get position(sequence number) of columns in targetdatastore at interface level

Position(sequence number) is not generated for the custom columns of target data store at interface level after applying bundle patche6 in biapps 11g(11.1.1.8.1)

 To resolve this issue,we need to drag the data store(W_GL_OTHER_F) from the Models to the interface of existing Target data store.
It will prompt the message like below.
click yes.then we can able to see the sequence number.


Thursday 14 May 2015

How to use Hints in ODI11G(BIApps11g)

There is a variable called ETL_HINT_EXTRACT in BIApps 11g.If we want use hints then we need to assign the hints to this ETL_HINT_EXTRACT variable and this need to be used in package like below.





After assigning hints to this variable in package,this value will be substituted in one of the property OBI_HINT_EXTRACT in flow tab like below.

When used in regular IKM this gets applied to the inner query which runs directly against the source when FLOW_CONTROL is not enabled E.g.

  insert into W_XXX_XXX
  select  ...from
      (select <OBI_EXTRACT_HINT> from source)

When  used in regular IKM this gets applied to the select query on the source for the interface when FLOW_CONTROL is enabled E.g.

  insert into I$_...
      select <OBI_EXTRACT_HINT> from source