T) Explain the differences between api & utility mode?

-

 Answer 1: 

  • When u load the data into a table in Utility mode all the constraints are disabled & then data is loaded which leads to faster access. During API Mode constraints will be enabled so that the access will be slow.

 Answer 2:

  • API & UTILITY are two possible interfaces to connect to the db’s to perform certain user specific tasks. These interfaces allow the user to access or use certain functions (provided by the db vendor) to perform operation on db’s. The functionality of each of these interfaces depends on  db’s. API has more flexibility but often considered as a slower process as compared to UTILITY mode. Well the trade off is their performance and usage.

 Answer 3: 

  • API mode is more diagnostic purpose for retrieving data from db means like selecting particular fields like retrieving the data relatively according to the constraints. Whenever we select API we will get the option of ablocal expression (ab_exp) every time where ever record is passing it will look for the query we write in that ablocal expression block then it will send. That is why it’s slow. Where as utility is like retrieving the data fields without any constraints or any conditions that is why it is fast.  

Answer 4: 

  • In API mode data processing(load/update/insert/delete) is slow however other process can access the database tables during the update. Compared to above Utility mode processing(load/update/insert/delete) goes faster as it handles data records in large chunks however during that time no other process can access  db table i.e. the process running in Utility mode locks the table/owns exclusive ownership of that db instance. In cross functional & largely distributed organizations API mode is recommended considering the performance aspect over Utility mode. For one time loads/initialization of huge volume data in tables Utility mode can be used.


Comments

Post a Comment

Popular posts from this blog

T) For data parallelism, we can use partition components. For component parallelism, we can use replicate component. Like this which component(s) can we use for pipeline parallelism?

-
You can use components that does not require any sorted data (explicit or in memory sort) to get pipeline parallelism. Like Reformat,FBE, Redefine components. And Components that needed sorted data like join, roll-up, merge, sort, partition by key and sort breaks the pipeline parallelism.  
Read more

T) When to use sort within groups ?

-
Use Sort within Groups only if records within a group are processed before being sorted on a minor key. i.e. if processing "A" needs records to be sorted on field {"1"} and later in the flow processing "B" needs records to be sorted on field {"1", "2"}. In this case before processing "2" and after processing "1" use sort within groups with major-key as {"1"} and minor key as {"2"}. If records are not grouped to start with, use Sort with a multi-part key. There is no benefit to using Sort within Groups directly after using a Sort component.
Read more

T) Explain about on .abi-unc files in abinitio ?

-
 These are temporary files used by the checkout process. Under normal circumstances you should not see them. However, if the checkout failed or was interrupted, these files can be left behind. Delete them and try checking out again.    Details: The checkout procedure includes two steps to ensure that a checkout does not leave your sandbox in a half-checked-out state: 1. It checks out the files, but gives them the .abi-unc suffix (for "uncommitted"). 2. Once every file is successfully checked out, the . abi-unc files replace the real files. If an error occurs midway through checkout, any .abi-unc files that have been created might be left behind. If you receive the error message "Cannot write project parameters file: /path/filename.abi-unc" during checkout and you see . abi-unc files, delete them and try checking out again. Uncommitted files are usually left behind because a checkout process was aborted.  
Read more