<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Using public and private IP networks</title>
    <link>/en/data-export/db-export-and-import/using-public-and-private-ip-networks/</link>
    <description>Recent content in Using public and private IP networks on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/data-export/db-export-and-import/using-public-and-private-ip-networks/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Data-Export: Identify the public network to OpenText Analytics Database</title>
      <link>/en/data-export/db-export-and-import/using-public-and-private-ip-networks/identify-public-network-to/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/data-export/db-export-and-import/using-public-and-private-ip-networks/identify-public-network-to/</guid>
      <description>
        
        
        &lt;p&gt;To be able to import to or export from a public network, OpenText™ Analytics Database needs to be aware of the IP addresses of the nodes or clusters on the public network that will be used for import/export activities. Your public network might be configured in either of these ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Public network IP addresses reside on the same subnet (create a subnet)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Public network IP addresses are on multiple subnets (create a network interface)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;To identify public network IP addresses residing on the same subnet:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use the &lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-subnet/&#34;&gt;CREATE SUBNET&lt;/a&gt; statement provide your subnet with a name and to identify the subnet routing prefix.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;To identify public network IP addresses residing on multiple subnets:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use the &lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-network-interface/&#34;&gt;CREATE NETWORK INTERFACE&lt;/a&gt; statement to configure import/export from specific nodes in the database cluster.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;After you&#39;ve identified the subnet or network interface to be used for import/export, you must &lt;a href=&#34;../../../../en/data-export/db-export-and-import/using-public-and-private-ip-networks/identify-db-or-nodes-used-importexport/&#34;&gt;Identify the Database Or Nodes Used For Import/Export.&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-subnet/#&#34;&gt;CREATE SUBNET&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/alter-statements/alter-subnet/#&#34;&gt;ALTER SUBNET&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/drop-statements/drop-subnet/#&#34;&gt;DROP SUBNET&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-network-interface/#&#34;&gt;CREATE NETWORK INTERFACE&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/alter-statements/alter-network-interface/#&#34;&gt;ALTER NETWORK INTERFACE&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../en/sql-reference/statements/drop-statements/drop-network-interface/#&#34;&gt;DROP NETWORK INTERFACE&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Data-Export: Identify the database or nodes used for import/export</title>
      <link>/en/data-export/db-export-and-import/using-public-and-private-ip-networks/identify-db-or-nodes-used-importexport/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/data-export/db-export-and-import/using-public-and-private-ip-networks/identify-db-or-nodes-used-importexport/</guid>
      <description>
        
        
        &lt;p&gt;After you identify the public network to OpenText™ Analytics Database, you can configure a database and its nodes to use it for import and export operations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Use 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/statements/alter-statements/alter-db/#&#34;&gt;ALTER DATABASE&lt;/a&gt;&lt;/code&gt; to &lt;a href=&#34;../../../../en/data-export/db-export-and-import/changing-node-export-addresses/&#34;&gt;specify a subnet&lt;/a&gt; on the public network for the database. After doing so, all nodes in the database automatically use the network interface on the subnet for import/export operations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On each database node, use 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/statements/alter-statements/alter-node/#&#34;&gt;ALTER NODE&lt;/a&gt;&lt;/code&gt; to specify a network interface of the public network.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;

&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-procedure-external/#&#34;&gt;CREATE PROCEDURE (external)&lt;/a&gt;&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;

&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-network-address/#&#34;&gt;CREATE NETWORK ADDRESS&lt;/a&gt;&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;

&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/system-tables/v-monitor-schema/network-interfaces/#&#34;&gt;NETWORK_INTERFACES&lt;/a&gt;&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
  </channel>
</rss>
