100% Asked - Informatica Interview Questions

11 Informatica Interview Questions

100% Asked – Informatica Interview Questions 2024

1. What are the scheduling options to run a session? Answer : You can shedule a session to run at a given time or intervel,or u can manually run the session. Different options of scheduling Run only on demand: server runs the session only when user starts session explicitly Run once: Informatica server runs the session only once at a specified date and time. Run every: Informatica server runs the session at regular intervels as u configured. Customized repeat: Informatica server runs the session at the dats and times secified in the repeat dialog box.
2 .What is tracing level and what are the types of tracing level? Answer : Tracing level represents the amount of information that informatcia server writes in a log file. Types of tracing level 1.Normal 2.Verbose 3.Verbose init 4.Verbose data
3. What is difference between stored procedure transformation and external procedure transformation? Answer : In case of stored procedure transformation procedure will be compiled and executed in a relational data source.U need data base connection to import the stored procedure in to u’r mapping. Where as in external procedure transformation procedure or function will be executed out side of data source. Ie you need to make it as a DLL to access in u r mapping. No need to have data base connection in case of external procedure transformation.
4. Explain about Recovering sessions? Answer : If you stop a session or if an error causes a session to stop, refer to the session and error logs to determine the cause of failure. Correct the errors, and then complete the session. The method you use to complete the session depends on the properties of the mapping, session, and Informatica Server configuration. Use one of the following methods to complete the session: 1 Run the session again if the Informatica Server has not issued a commit. 2 Truncate the target tables and run the session again if the session is not recoverable. 3 Consider performing recovery if the Informatica Server has issued at least one commit.
5. If a session fails after loading of 10,000 records in to the target.How can you load the records from 10001 th record when you run the session next time? Answer : As explained above informatcia server has 3 methods to recovering the sessions.Use performing recovery to load the records from where the session fails.
6. Explain about perform recovery? Answer : When the Informatica Server starts a recovery session, it reads the OPB_SRVR_RECOVERY table and notes the row ID of the last row committed to the target database. The Informatica Server then reads all sources again and starts processing from the next row ID. For example, If the Informatica Server commits 10,000 rows before the session fails, when you run recovery, the Informatica Server bypasses the rows up to 10,000 and starts loading with row 10,001. By default, Perform Recovery is disabled in the Informatica Server setup. You must enable Recovery in the Informatica Server setup before you run a session so the Informatica Server can create and/or write entries in the OPB_SRVR_RECOVERY table.
7. How to recover the standalone session? Answer : A standalone session is a session that is not nested in a batch. If a standalone session fails, you can run recovery using a menu command or pmcmd. These options are not available for batched sessions. To recover sessions using the menu: 1. In the Server Manager, highlight the session you want to recover. 2. Select Server Requests-Stop from the menu. 3. With the failed session highlighted, select Server Requests- Start Session in Recovery Mode from the menu. To recover sessions using pmcmd: 1.From the command line, stop the session. 2.From the command line, start recovery.
8. How can u recover the session in sequential batches? Answer : If you configure a session in a sequential batch to stop on failure, you can run recovery starting with the failed session. The Informatica Server completes the session and then runs the rest of the batch. Use the Perform Recovery session property. To recover sessions in sequential batches configured to stop on failure: 1.In the Server Manager, open the session property sheet. 2.On the Log Files tab, select Perform Recovery, and click OK. 3.Run the session. 4.After the batch completes, open the session property sheet. 5.Clear Perform Recovery, and click OK. If you do not clear Perform Recovery, the next time you run the session, the Informatica Server attempts to recover the previous session. If you do not configure a session in a sequential batch to stop on failure, and the remaining sessions in the batch complete, recover the failed session as a standalone session.
9. How to recover sessions in concurrent batches? Answer : If multiple sessions in a concurrent batch fail, you might want to truncate all targets and run the batch again. However, if a session in a concurrent batch fails and the rest of the sessions complete successfully, you can recover the session as a standalone session. To recover a session in a concurrent batch: 1.Copy the failed session using Operations-Copy Session. 2.Drag the copied session outside the batch to be a standalone session. 3.Follow the steps to recover a standalone session. 4.Delete the standalone copy.
10. How can u complete unrecoverable sessions? Answer : Under certain circumstances, when a session does not complete, you need to truncate the target tables and run the session from the beginning. Run the session from the beginning when the Informatica Server cannot run recovery or when running recovery might result in inconsistent data.
11. What r the circumstances that infromatica server results an unrecoverable session? Answer : The source qualifier transformation does not use sorted ports. If u change the partition information after the initial session fails. Perform recovery is disabled in the informatica server configuration. If the sources or targets changes after initial session fails. If the maping consists of sequence generator or normalizer transformation. If a concuurent batche contains multiple failed sessions.