You can use a database link to update a remote object only if you are using Oracle Database distributed functionality.
Adapt the PATH variable so that it no longer contains references to the old Oracle home.
Check the environment with: $ env | grep ORACLE_HOME $ env | grep ORACLE_BASE $ env | grep PATH (this should no longer contain a reference to 112_64) Run the SBP post-installation instructions as described in the corresponding SBP README set IHRDBMS=/oracle/SID/12102 set OHRDBMS=/oracle/SID/121 set SBPFUSER=/sbin/fuser env ORACLE_HOME=$OHRDBMS $OHRDBMS/sapbundle/catsbp - Create the symbolic link for BR*Tools 7.40: cd /oracle/client If the link or directory 11x_64 already exists, rename it, as in this example: mv 11x_64 11x_64_save Create the symbolic link: ln -s /oracle/client/12x /oracle/client/11x_64 OK, now you can stop and start your system and check that you are working on 12c.
Upgrades can be very complicated, so you must always read the upgrade manual, and test thoroughly before considering an upgrade of a production environment.
This article does not include any references to pluggable databases, as in most cases the upgrade to 12c is a prerequisite of conversion to pluggable databases.
You need not specify the partition name when updating values in a partitioned table.
However in some cases specifying the partition name can be more efficient than a complicated Specify a complete or partial name of a database link to a remote database where the object is located.
When used in the subquery of a DML statement, you can specify this clause in a subquery in the can be a subquery, a column, a function, or a collection constructor.
Regardless of its form, it must return a collection value—that is, a value whose type is nested table or varray.
Hope this tutorial could help others to accomplish this task.
This article provides an overview of some of the options for upgrading existing databases to Oracle 12c Release 1.
You may wish to update records in one table based on values in another table.