Test load In Informatica :-
This option is to ensure that the mapping is running fine without any errors or exception.
Test load is very useful property while working in production support.If your sessions fails for
any duplicate issues /Null issues.You can do test load by enabling test load option.By doing so it
will reject the records(Null/Duplicate) while loading into the target.(Here its not ACTUAL load just
like a test run).After completion of the session you can see the rejected counts. From that you can
indentify how many records are bad records.
Pre request:
1.Test load option should be enabled.
2. Number of rows to be tested.(U can mention what ever u need.Better go for larger values eg: 100000)
3. Set stop on errors to 0.(Session wont get abend while rejecting the bad records)
Last but not least,After doing test load DISABLE the test load option and REVERT stop on errors.
Let me know if you have any question...
we remind 2 thing before test load:-
1)It will work only normal mode.
2)Truncate option is not checked
In simple words, 'test load' is a load without a 'commit' to the targets! The source qualifier fetches data and all
the rows are processed through all transformations. Even the target insert queries are generated. But, rows are not
inserted.
In the session log u will not find the entry of a commit issued. Also, in the session load summary,
the entry will be 'Target test load summary' instead of 'Target load summary'.
The advantage of this is already evident in the above explanation. Especially when there is no access to
debug mode, this option is very helpful and can be used with a verbose data to check for errors and issues.
This option is to ensure that the mapping is running fine without any errors or exception.
Test load is very useful property while working in production support.If your sessions fails for
any duplicate issues /Null issues.You can do test load by enabling test load option.By doing so it
will reject the records(Null/Duplicate) while loading into the target.(Here its not ACTUAL load just
like a test run).After completion of the session you can see the rejected counts. From that you can
indentify how many records are bad records.
Pre request:
1.Test load option should be enabled.
2. Number of rows to be tested.(U can mention what ever u need.Better go for larger values eg: 100000)
3. Set stop on errors to 0.(Session wont get abend while rejecting the bad records)
Last but not least,After doing test load DISABLE the test load option and REVERT stop on errors.
Let me know if you have any question...
we remind 2 thing before test load:-
1)It will work only normal mode.
2)Truncate option is not checked
In simple words, 'test load' is a load without a 'commit' to the targets! The source qualifier fetches data and all
the rows are processed through all transformations. Even the target insert queries are generated. But, rows are not
inserted.
In the session log u will not find the entry of a commit issued. Also, in the session load summary,
the entry will be 'Target test load summary' instead of 'Target load summary'.
The advantage of this is already evident in the above explanation. Especially when there is no access to
debug mode, this option is very helpful and can be used with a verbose data to check for errors and issues.
No comments:
Post a Comment