You are running your warehouse using Autonomous Data Warehouse (ADW) service and you noticed that a newly configured batch job i
s always running in serial even through nothing else is running in the database. All your jobs are configured to run with parallelism enabled.What could be the reason for this batch job to run in serial?A. The batch job depends on only one table and parallelism cannot be enabled on single-table queries.B. The parallelism of batch job depends on the number of ADW databases involved in the queryC. The new batch job is connected to LOW consumer group.D. The new batch job runs on database tables that are not enable for parallel execution.E. Parallelism on the database is controlled by the application, not the database.
<u>C. The new batch job is connected to the LOW consumer group.</u>
Explanation:
<em>Remember</em>, one of the main characteristics of the LOW consumer group <u>database service</u> is that queries would run serially.
Since in this case, we are told that the newly configured batch job is always running in serial, it most likely would be because the new batch job is connected to the LOW consumer group; as queries are designed to always run serially.
You would not have to make a whole new set of punch cards if you knew the card that had the mistake. Simply remove this card from the pile and make a new punch card in its place.
