checkout and checkin in informatica 8.6
Answers were Sorted based on User's Feedback
Answer / kondeti.srinivas
if source or target or wf or mappings are checked in state
we can not delete or update those. those can be modified by
user which is originally created by using cheked out.
if created user checked out,he can only can cheked out.
this nothing but a version control...
| Is This Answer Correct ? | 18 Yes | 0 No |
Check out & check in are users locks over WF/Session/source
or target .A user has to checkOut a object for any
modification. If the object is checked in it cant be
modified.any changes done by checking out will reflect on
server only ofter checking in...we can run a wf at any
state irrespective of whether it is checked in or out
| Is This Answer Correct ? | 13 Yes | 1 No |
What are the two modes of datamovement in informatica sever?
what is granularity,what type of granularity we will take in fact tables either lowlevel or highlevel,if two tables having same granularity that is posiable or not
sorce is a flatfile only 1st and last row should insert to target how will u do?
Why the workflow is failed after running two hours in informatica?
How do you Merge multiple Flat files for example 100 flat files with out using Union T/F
Informatica Server and Client are in different machines. You run a session from the server manager by specifying the source and target databases. It displays an error. You are confident that everything is correct. Then why it is displaying the error?
How do you load first and last records into target table? How many ways are there to do it? Explain through mapping flows.
What is an unconnected transformation?
in source one table is there. id value --- ------ 1 a 2 b 3 c 1 d 2 e 1 f in target i want id value ---- ------ 1 a,d,f 2 b,e 3 f How to implement it in informatica without using normalizer transformation?
whats the logic to load the lower level of granularity of data to fact table.
Q. In source area, it is use complex query we have using 5 to 10 table we has been join now all join clolumn having indexes but still we having performance issue. how to fix the performnce issue of the query.
What is meant by target load plan?