Issues with Oracle ASM disk groups on existing database sources and sandboxes after upgrading from Velocity 2.8 to Velocity 2.9.

Oracle ASM disk groups on existing database sources and sandboxes cannot be mounted after upgrading to Velocity 2.9.

Additionally, sandboxes or database ingestions may fail with the following error:

The ASM disk group could not be attached on the Oracle host server.

To resolve these issues, do the following on the Oracle host server where the database source or sandbox is mounted:

1. Type the following commands to find the Oracle user ID and primary group ID:

• grep ora /etc/passwd

• id oracle

2. Type the following commands to find the grid infrastructure user ID and group ID, if applicable:

• grep grid /etc/passwd

• id grid

3. Locate the Velocity NFS mount path on the Oracle host server.

4. Set the owner of the <NFS Mount Path>/.vpfssnap_exclude folder to <OracleUserId>:<OraceUser's_Primary_Group_id>

For example, chown oracle:oinstall /mnt/velocity/DBASM_c070203e-d79e-4a0a-a507-19d09aa338d1/.vpfssnap_exclude

5. Set the ownership of the BackupTag folder and its files { <NFS Mount Path>/vbt_***** } on the <NFS mount path> to <OracleUserId>:<OraceUser's_Primary_Group_id>.

For example, chown -R oracle:oinstall /mnt/velocity/DBASM_c070203e-d79e-4a0a-a507-19d09aa338d1/vbt_19ee3a07aa384996a57637f762

6. If you find files that start with the pattern asm* under the <NFS Mount Path>/.velocity/volumes folder, then set the ownership of the <NFS Mount Path>/.velocity/volumes folder and its files to the <GridUser>:<GridUser's Primary Group Id>.

For example, chown -R grid:oinstall /mnt/velocity/DBASM_c070203e-d79e-4a0a-a507-19d09aa338d1/.velocity/volumes

7. Set the ownership of the file <NFS Mount Path>/.velocity/config/asm_config.json to <GridUser>:<GridUser's Primary Group Id>.

For example, chown -R grid:oinstall /mnt/velocity/DBASM_c070203e-d79e-4a0a-a507-19d09aa338d1/.velocity/config/asm_config.json

8. Delete all the log files from <NFS Mount Path>/logs folder.

For example, /bin/rm -f /mnt/velocity/DBASM_c070203e-d79e-4a0a-a507-19d09aa338d1/log/*.log

9. Repeat steps 4 through 8 for all remaining Velocity NFS mount paths that are mounted on the Oracle host server.

The upgrade rolls back to the previous version in the following situations:

• You upgraded Velocity without running a self-test first.

• You ran the self-test on a different day than you upgraded.

• The upgrade was started on the same day that the self-test ran, but the upgrade completed on a different day.

Run the self-test and then try the upgrade again.

1. Log in to the Velocity shell menu.

2. From the Main Menu > Support view, type the following command:

Test Software

When you install the Velocity Client for Solaris, if you answer yes to the prompt "Do you want to continue with the installation of <name>?", the message "Error: Please enter yes or no" may appear.

Do the following to complete the installation:

• In the Velocity Cloud Console, on the Configure the Velocity Client wizard, click Show the commands.

• Copy the following portion of the command to the terminal:

  /opt/veritas/velocity/bin/velocity_registration initialize -s https://<IP address> -u <user> -p <password>

Restarting, upgrading, or restarting services on the Velocity Storage Server may cause ingestion and sandbox performance issues.

This issue may be caused by a large number of messages in the rabbitmq log queue. Contact Velocity Support for assistance. Reference technote 000127999.

When you create a new sandbox from an Oracle CDB database, Velocity automatically starts all PDB databases in that CDB database in read/write mode. If you restart the CDB database, the PDB databases are placed into the state that was configured in Oracle instead of in read/write mode.

Run an appropriate Oracle command to open the PDB databases in read/write mode.

The following example command opens a single PDB database in read/write mode:

ALTER PLUGGABLE DATABASE pdb_name OPEN;

The following example command opens all PDB databases in read/write mode:

ALTER PLUGGABLE DATABASE ALL OPEN;

You cannot create concurrent new sandboxes from an Oracle database that was ingested from a NetBackup deduplicated backup.

Only one sandbox can be created at a time. When sandbox creation is complete for one sandbox, you can then create another sandbox.

The Create Recovery Sandbox option on the Database Sources window is not supported for database copies that were created using the NetBackup OST database ingestion method.

This is a known issue that should be fixed in a future release.

The temporary tablespace may not be created in the database instance when a sandbox is created.

A missing temporary tablespace may impact some Oracle operations, such as sorting and grouping.

Manually add a temporary tablespace file after the sandbox is created.

If you use NetBackup CoPilot to ingest data into Velocity, some NetBackup CoPilot backups fail due to issues with certain directory permissions.

Permissions on a share are reverted after a reboot.

Do the following after every reboot to enable backups to succeed:

1. Determine the share that will be used as a backup destination in the NetBackup policy.

2. Check the share permissions on the Oracle node, which will be "drwxrwx--x 6 root velocity".

3. Type the following command to change the owner of the share:

chown root:root sharename

4. Type the following command to provide the read and write permissions to the share:

chmod 777 <sharename>

5. Check the share permissions on the Oracle node, which will be changed to "drwxrwxrwx 5 root root"

After the Velocity physical appliance rolls back and restarts, database ingests fail or hang. The Velocity client may also stop receiving commands from the appliance. Refer to the associated tech note for a workaround.

000127361

If you attempt to perform a factory reset on a Velocity physical appliance when any of the database sources or sandboxes are mounted, or any of the Velocity services are running, the factory reset will fail. The appliance is left in an unconfigurable state as a result of this issue.

To avoid the issue, do the following:

1. Follow the best practice and stop all mounts before you perform a factory reset on the appliance.

   See Stopping and starting all mounts

2. Run the following command to stop all Velocity services:

   Main > Support > Processes > Velocity Stop

000127362

The appliance proxy settings do not take effect for communications with the Velocity Cloud Console when you use the Main > Network > Proxy Enable|Disable commands. To work around this issue, use the Main > Network > Proxy Set|Unset commands whenever you make changes to the appliance proxy settings