Salesforce

DB2 Databases (Magic xpa 2.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

DB2 Databases (Magic xpa 2.x)

The following topics describe Magic xpa’s functionality when connecting with a DB2 database.

Physical Locking

A physical lock is a method that ensures that no one else can modify a record that is currently locked. Specifically, from the moment a user locks the record until that user releases the record, the record cannot be modified by another user. The physical lock is implemented as follows: When Magic xpa locks a record according to its locking strategy, Magic xpa issues a Select statement with a FOR UPDATE clause.

The FOR UPDATE clause prevents other applications from making changes to the record until the end of the transaction.

Recommendation: With a DB2 database, always use TIMEOUT = -1 (indefinite), since the DB2 database rolls back after a timeout. If you require a timeout, define an error strategy that rolls back after a lock.

Views

A View must have a virtual unique index defined. Insert, Update, and Delete operations are permitted.

Magic xpa considers a View as a regular table. Magic xpa should not be used to perform any rename or convert operations. If Magic xpa is used to execute any rename or convert operations, Magic xpa will display an error message and will not convert or rename the View in the database.

The Magic xpa Single User Edition does not support the DB2 database.

Reference
Attachment 
Attachment