Not only it is common, but it's also a best practice to place volumes containing an Oracle database into Protection Groups. When we need to take a snapshot of the database, we take a snapshot of the protection group instead of individual volumes. That ensures all volumes are write-consistent with each other and they are snapshotted as of the same time.
We cannot move an existing protection group into a pod. We need to create a new protection group within the pod, and then move existing database volumes into it.
In the GUI, go to Storage --> Pods and click on the pod we created in the previous step. That will open the detail page for the pod. Click on the plus icon at the top right corner of the Protection Groups panel. That will bring up the Create Protection Group dialog shown below.
Enter the name of the protection group and click Create. A new protection group will be created within the pod as shown below. Notice how a unique namespace is created by qualifying the pod name with the protection group name.
Here is the CLI command to create the protection group within the pod. Notice that we have used the fully qualified name format to specify that the oraprd12-pg protection group should be created inside pod oraprd12-pod.
pureuser@sn1-x70r2-e03-27> purepgroup create oraprd12-pod::oraprd12-pg
Name Source Targets Host Groups Hosts Volumes
oraprd12-pod::oraprd12-pg oraprd12-pod - - - -