<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrading the Teradata Data Warehouse Protector on</title><link>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/</link><description>Recent content in Upgrading the Teradata Data Warehouse Protector on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading the Protector on Single Node</title><link>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_upgrade_single_node/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_upgrade_single_node/</guid><description>&lt;p>The Teradata Data Warehouse Protector build provides an automated script to manage the upgrade process. The master script internally calls the scripts to install and upgrade the components. The master script installs and upgrades the components in the following order:&lt;/p>
&lt;ol>
&lt;li>Log Forwarder&lt;/li>
&lt;li>RPAgent&lt;/li>
&lt;li>Policy Enforcement Point (Database Protector)&lt;/li>
&lt;/ol>
&lt;p>The master script is available in the directory where the installation files are extracted. It provides the following arguments:&lt;/p>
&lt;ul>
&lt;li>&lt;code>install&lt;/code> - installs the components in an interactive mode.&lt;/li>
&lt;li>&lt;code>upgrade&lt;/code> - installs a newer version of the protector with minimal downtime.&lt;/li>
&lt;li>&lt;code>silent&lt;/code> - installs the components in a non-interactive mode.&lt;/li>
&lt;li>&lt;code>install.ini&lt;/code> - installs the components as per the parameters provided in the file.&lt;/li>
&lt;li>&lt;code>help&lt;/code> - lists the arguments available for the script.&lt;/li>
&lt;/ul>
&lt;p>During the upgrade process, the master script:&lt;/p></description></item><item><title>Upgrading the Protector on Multi Node</title><link>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_upgrade_multi_node/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_upgrade_multi_node/</guid><description>&lt;p>The Teradata Data Warehouse Protector build provides an automated script to manage the upgrade process. The master script internally calls the scripts to install and upgrade the components. The master script installs and upgrades the components in the following order:&lt;/p>
&lt;ol>
&lt;li>Log Forwarder&lt;/li>
&lt;li>RPAgent&lt;/li>
&lt;li>Policy Enforcement Point (Database Protector)&lt;/li>
&lt;/ol>
&lt;p>The master script is available in the directory where the installation files are extracted. It provides the following arguments:&lt;/p>
&lt;ul>
&lt;li>&lt;code>install&lt;/code> - installs the components in an interactive mode.&lt;/li>
&lt;li>&lt;code>upgrade&lt;/code> - installs a newer version of the protector with minimal downtime.&lt;/li>
&lt;li>&lt;code>silent&lt;/code> - installs the components in a non-interactive mode.&lt;/li>
&lt;li>&lt;code>install.ini&lt;/code> - installs the components as per the parameters provided in the file.&lt;/li>
&lt;li>&lt;code>help&lt;/code> - lists the arguments available for the script.&lt;/li>
&lt;/ul>
&lt;p>During the upgrade process, the master script:&lt;/p></description></item><item><title>Creating the UDFs after Upgrade</title><link>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_create_udfs_post_upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.1/docs/dwp/dwp_teradata/dwp_ter_upg_prot/dwp_teradata_create_udfs_post_upgrade/</guid><description/></item></channel></rss>