TAW_11 Chapter 8, Organization of Database updates

Question 1

Perform on commit occurs when..

Answer 1

when the commit work statement is issued

Question 2

How can a rollback be initiated from a perform on commit?

Answer 2

type A message

Question 3

What transaction is used for monitoring update requests

Answer 3

SM13

Question 4

Update modules contain IMPORTING and EXPORTING?

Answer 4

No, only importing pass by value

Question 5

How are update modules called from a dialog program?

Answer 5

Call the function module IN UPDATE TASK

Question 6

How are LUW updates stored?

Answer 6

In VB tables with a VBKEY.

VBDATA and VBMOD, VBHDR after commit

Question 7

How can FM IN UPDATE TASKS be aborted before commit?

Answer 7

ROLLBACK WORK, Message A or X

Question 8

If I leave a transaction before commit work but without a rollback or message A or X, what happens to the log entries?

Answer 8

They remain in the VBDATA, VBMOD logs and must be removed later

Question 9

There are 4 ways to reorg the update logs, what are they?

Answer 9

Directly from SM13
An auto update based on profile parameters
Deleted after ## days based on profile parameter
Scheduled run of RSM13002

Question 10

What two things cannot be used in an update FM?

Answer 10

Commit work and Rollback work

Question 11

What is the difference between COMMIT WORK and COMMIT WORK AND WAIT

Answer 11

COMMIT WORK is async COMMIT WORK AND WAIT is sync

Question 12

During commit work and wait, is the work process retained?

Answer 12

No, it is rolled out

Question 13

How is a local update initiated?

Answer 13

SET UPDATE TASK LOCAL before the commit

Question 14

Are local updates written to the VB tables

Answer 14

No

Question 15

It is best to use LOCAL updates in dialog programs?

Answer 15

No, LOCAL updates should only be used in batch processes because they tie up dialog processes

Question 16

Are local updates sync or async

Answer 16

sync even though they don’t have a wait

Question 17

what are the two ways to force a sync update

Answer 17

COMMIT WORK AND WAIT

Or SET UPDATE TASK LOCAL and COMMIT WORK

Question 18

Can V1 updates be restarted?

Answer 18

Yes

Question 19

What determines if an update is V1 or V2?

Answer 19

Immediate start is V1, delayed or collective is V2

Question 20

If V1 fails do V2 requests occur?

Answer 20

No

Question 21

If no UP2 work requests exist, where do V2 updates run?

Answer 21

UPD

Question 22

The V2 process always runs without SAP locks?

Answer 22

Correct, locks are released by V1.

Question 23

Does ABAP have SELECT …FOR UPDATE?

Answer 23

Yes, it locks at the database level.

Question 24

How can I insure that a DB change is last in the Db LUW

Answer 24

In the update function module add a form with perform on commit. These will always be last