PeopleTools Question: Download Questions PDF
Tell me why the call section & SQL(both are mutually exclusive) are not able to use at a time in application engine?
Answers:
Answer #1When a SQL is run, there is a lock on the table by the database until that section is completed. If during that time there runs some other process which will use the same table locked by our section using call section, this process will fail.
Answer #2Let\\'s say.... we have an App Engine \\"TEST_AE\\".
In this AE, we have a SQL action that updates a record \\"RECA\\".
commit can happen at STEP level. There is no commit happens below than step level.
Now, Since AE updates the record RECA, it locks the record object. It means no other process can make any changes to this record, until the AE \\"TESTAE\\" commits.
Now assume, next to SQL Action we have a call section which calls another AE \\'TEST2_AE\\". As I said before, this TEST2_AE cannot make any changes to the RECA because it is already locked by TESTAE. This is DEADLOCK. To avoid this situation, SQL and CALL sections are made mutually exclusive.
In this AE, we have a SQL action that updates a record \\"RECA\\".
commit can happen at STEP level. There is no commit happens below than step level.
Now, Since AE updates the record RECA, it locks the record object. It means no other process can make any changes to this record, until the AE \\"TESTAE\\" commits.
Now assume, next to SQL Action we have a call section which calls another AE \\'TEST2_AE\\". As I said before, this TEST2_AE cannot make any changes to the RECA because it is already locked by TESTAE. This is DEADLOCK. To avoid this situation, SQL and CALL sections are made mutually exclusive.
Download PeopleTools Interview Questions And Answers
PDF