TT-05298
Propagation will be serialized because there are Oracle tables with unique indexes, unique or foreign key constraints that are cached in an AWT cache group with parallel propagation enabled that do not have the corresponding constraint on TimesTen.
Cause
Some unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen.
Action
- Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.
- To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
Additional Information
Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.
TT-05298
Propagation will be serialized because there are Oracle tables with unique indexes, unique or foreign key constraints that are cached in an AWT cache group with parallel propagation enabled that do not have the corresponding constraint on TimesTen.
Cause
Some unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen.
Action
- Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.
- To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
Additional Information
Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.
TT-05298
Propagation will be serialized because there are Oracle tables with unique indexes, unique or foreign key constraints that are cached in an AWT cache group with parallel propagation enabled that do not have the corresponding constraint on TimesTen.
Cause
Some unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen.
Action
- Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.
- To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a cache group in the Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a cache group in the Oracle TimesTen In-Memory Database Cache Guide.
Additional Information
Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.
