Predefined Database Service Names for Autonomous Transaction Processing

The tnsnames.ora file provided with the credentials zip file contains five database service names identifiable as tpurgent, tp, high, medium, and low. The predefined service names provide different levels of performance and concurrency for Autonomous Transaction Processing.

  • tpurgent: The highest priority application connection service for time critical transaction processing operations. This connection service supports manual parallelism.

  • tp: A typical application connection service for transaction processing operations. This connection service does not run with parallelism.

  • high: A high priority application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing.

  • medium: A typical application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing. Using this service the degree of parallelism is limited to four (4).

  • low: A lowest priority application connection service for reporting or batch processing operations. This connection service does not run with parallelism.

Note:

After connecting to the database using one service, do not attempt to manually switch that connection to a different service by simply changing the consumer group of the connection. When you connect using a service, Autonomous Transaction Processing performs more actions to configure the connection than just setting its consumer group.

Sessions in these services may get disconnected if they stay idle for more than five (5) minutes and other users' sessions require the resources consumed by the idle session. This allows resources to be freed for other active users in your database.

Note:

When connecting for replication purposes, use the low database service name. For example use this service with Oracle GoldenGate connections.