Updating Components using the odacli update-registry Command

FAQs about the odacli update-registry command.

What are the components affected when specifying the system option with --component,-n in the odacli update-registry command?

The system components are sysinstance, gihome, and dbnode. The metadata related to these component is updated in appliance registry metadata when you specify the system option with --component,-n in the odacli update-registry command.

What are the components are affected when specifying the all option with --component,-n in the odacli update-registry command?

When you specify all, the components updated are DB, dbstorage, dbhome, and asr. The metadata related to these component is updated in appliance registry metadata when you specify the all option with --component,-n in the odacli update-registry command.

How does the odacli update-registry command work?

The odacli update-registry command attempts to discover values for different parameters corresponding to a component using comands such as srvctl, crsctl, sqlplus, or operating system commands. If the query succeeds and if the information is available, then the values are written in the appliance registry. Note that the odacli update-registry command does not configure or troubleshoot any component-related issues.

What are non-discoverable parameters?

Parameter values that cannot be discovered using commands such as srvctl, crsctl, sqlplus, or operating system commands are non-discoverable parameters. Refer to the Oracle Database Appliance Deployment and User's Guide for your hardware model.

When do I use the odacli update-registry command?

Use the odacli update-registry command to discover appliance registry metadata for components dbhome and gihome after out-of-cycle patching.

Which values does the odacli update-registry command modify?

Except for values that are specific to Oracle Database Appliance, all other values can be modified correctly in the metadata. Values which are specific to Oracle Database Appliance such as dbshape, dbclass, and enableSEHA remain the same in the metadata. If the registry metadata for parameters of any component is incorrect, and the component is not mentioned in the Non Discoverable Parameters section, then when you run the odacli update-registry command, the components are rediscovered and the metadata is updated. Refer to the Oracle Database Appliance Deployment and User's Guide for your hardware model for the values that are updated. You can update the registry metadata of an individual database or dbstorage using the -u option.
If the value specific to Oracle Database Appliance was null before running the odacli update-registry command, then it remains the same after the command is run. Contact Oracle Support in these cases.

What values does the odacli update-registry command modify when the database option is specified using the -n DB option?

Databases for which the metadata already exists in appliance registry can only be re-discovered using the odacli update-registry command. For discovering databases that are migrated from outside your Oracle Database Appliance deployment, use the odacli register-database command. For information about migrating databases, see the Oracle Database Appliance Deployment and User's Guide for your hardware model.

What values does the odacli update-registry command modify when the database storage option is specified using the -b dbstorage option?

The dbstorages for which the metadata already exists, can only be discovered using the odacli update-registry command. For discovering dbstorage that is migrated from outside your Oracle Database Appliance deployment, use the odacli create-dbstorage command. The odacli create-dbstorage command does not create another dbstorage, it discovers the values and stores the same in the metadata. For Oracle ACFS dbstorage, it creates the file system, if required.

Can I manually modify or delete the appliance registry metadata and then run the odacli update-registry command to discover related information?

Erasing entries from the metadata and then using the odacli update-registry command for discovery is not supported.