A data science team is using OCI Data Science to fine-tune a model. They notice that training jobs are failing due to out-of-memory errors on the notebook session. What should they do to resolve this?
A larger shape provides more memory, resolving OOM issues.
Why this answer
Out-of-memory errors during training on a notebook session indicate that the current shape's memory capacity is insufficient for the model or data being processed. Switching to a larger notebook session shape directly increases available RAM and compute resources, resolving the memory constraint without altering the training logic or infrastructure type.
Exam trap
Oracle often tests the misconception that autoscaling or reducing batch size can fix memory issues in a single-node notebook session, but the correct approach is to match the compute shape to the workload's memory requirements.
How to eliminate wrong answers
Option A is wrong because autoscaling adjusts the number of compute instances horizontally, not the memory of a single notebook session; it does not prevent OOM errors caused by insufficient per-instance memory. Option B is wrong because OCI Data Flow is a serverless Spark-based service for big data processing, not designed for fine-tuning deep learning models, and migrating would require rewriting the training pipeline. Option D is wrong because reducing batch size can mitigate memory usage but does not address the root cause of an undersized notebook session shape; it may also degrade training convergence or performance, and the question asks for a resolution to the failing jobs, not a workaround.