<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Create an empty database</title>
    <link>/en/admin/configuring-db/config-procedure/create-an-empty-db/</link>
    <description>Recent content in Create an empty database on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/admin/configuring-db/config-procedure/create-an-empty-db/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Admin: Creating a database name and password</title>
      <link>/en/admin/configuring-db/config-procedure/create-an-empty-db/creating-db-name-and-password/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/admin/configuring-db/config-procedure/create-an-empty-db/creating-db-name-and-password/</guid>
      <description>
        
        
        &lt;h2 id=&#34;database-names&#34;&gt;Database names&lt;/h2&gt;
&lt;p&gt;Database names must conform to the following rules:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Be between 1-30 characters&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Begin with a letter&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Follow with any combination of letters (upper and lowercase), numbers, and/or underscores.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Database names are case sensitive; however, it is recommended that you do not create databases with names that differ only in case. For example, do not create a database called &lt;code&gt;mydatabase&lt;/code&gt; and another called &lt;code&gt;MyDataBase&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&#34;database-passwords&#34;&gt;Database passwords&lt;/h2&gt;
&lt;p&gt;Database passwords can contain letters, digits, and special characters listed in the next table. Passwords cannot include non-ASCII Unicode characters.&lt;/p&gt;
&lt;p&gt;The allowed password length is between 0-100 characters. The database superuser can change a user&#39;s maximum password length using &lt;a href=&#34;../../../../../en/sql-reference/statements/alter-statements/alter-profile/#&#34;&gt;ALTER PROFILE&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You use &lt;a href=&#34;../../../../../en/security-and-authentication/client-authentication/hash-authentication/passwords/profiles/#&#34;&gt;Profiles&lt;/a&gt; to specify and control password definitions. For instance, a profile can define the maximum length, reuse time, and the minimum number or required digits for a password, as well as other details.&lt;/p&gt;
&lt;p&gt;The following special (ASCII) characters are valid in passwords. Special characters can appear anywhere in a password string. For example, &lt;code&gt;mypas$word&lt;/code&gt; or &lt;code&gt;$mypassword&lt;/code&gt; are both valid, while &lt;code&gt;±mypassword&lt;/code&gt; is not. Using special characters other than the ones listed below can cause database instability.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;#&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;?&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;=&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;_&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&#39;&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;)&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;(&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;@&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;\&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;/&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;!&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;,&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;~&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;:&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;%&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;;&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;`&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;^&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;+&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;.&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;-&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;space&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&amp;amp;&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&amp;lt;&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&amp;gt;&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;[&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;]&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;{&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;}&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;|&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;*&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;$&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;&amp;quot;&lt;/code&gt;&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;a href=&#34;../../../../../en/security-and-authentication/client-authentication/hash-authentication/passwords/password-guidelines/#&#34;&gt;Password guidelines&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/statements/alter-statements/alter-profile/#&#34;&gt;ALTER PROFILE&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/statements/create-statements/create-profile/#&#34;&gt;CREATE PROFILE&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../../../en/sql-reference/statements/drop-statements/drop-profile/#&#34;&gt;DROP PROFILE&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Admin: Create a database using administration tools</title>
      <link>/en/admin/configuring-db/config-procedure/create-an-empty-db/create-db-using-admin-tools/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/admin/configuring-db/config-procedure/create-an-empty-db/create-db-using-admin-tools/</guid>
      <description>
        
        
        &lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Run the &lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/admin-tools/&#34; title=&#34;OpenText&amp;amp;trade; Analytics Database Administration Tools provides a graphical user interface for managing the database.&#34;&gt;Administration tools&lt;/a&gt; from your &lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/admin-host/&#34; title=&#34;The host on which the OpenText&amp;amp;trade; Analytics Database rpm package was manually installed.&#34;&gt;Administration host&lt;/a&gt; as follows:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ /opt/vertica/bin/admintools
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you are using a remote terminal application, such as PuTTY or a Cygwin bash shell, see &lt;a href=&#34;../../../../../en/admin/using-admin-tools/notes-remote-terminal-users/#&#34;&gt;Notes for remote terminal users&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Accept the license agreement and specify the location of your license file. For more information see &lt;a href=&#34;../../../../../en/admin/managing-licenses/#&#34;&gt;Managing licenses&lt;/a&gt; for more information.&lt;/p&gt;
&lt;p&gt;This step is necessary only if it is the first time you have run the Administration Tools&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Main Menu, click &lt;strong&gt;Configuration Menu&lt;/strong&gt;, and click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Configuration Menu, click &lt;strong&gt;Create Database&lt;/strong&gt;, and click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Enter the name of the database and an optional comment, and click &lt;strong&gt;OK&lt;/strong&gt;. See &lt;a href=&#34;../../../../../en/admin/configuring-db/config-procedure/create-an-empty-db/creating-db-name-and-password/#&#34;&gt;Creating a database name and password&lt;/a&gt; for naming guidelines and restrictions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Establish the superuser password for your database.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;To provide a password enter the password and click &lt;strong&gt;OK&lt;/strong&gt;. Confirm the password by entering it again, and then click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If you don&#39;t want to provide the password, leave it blank and click &lt;strong&gt;OK&lt;/strong&gt;. If you don&#39;t set a password, you must verify that you truly do not want to establish a superuser password for this database. Click &lt;strong&gt;Yes&lt;/strong&gt; to create the database without a password or &lt;strong&gt;No&lt;/strong&gt; to establish the password.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class=&#34;admonition caution&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Caution&lt;/h4&gt;

If you do not enter a password at this point, the superuser password is set to empty. Unless the database is for evaluation or academic purposes, it is strongly recommended that you enter a superuser password. See &lt;a href=&#34;../../../../../en/admin/configuring-db/config-procedure/create-an-empty-db/creating-db-name-and-password/#&#34;&gt;Creating a database name and password&lt;/a&gt; for guidelines.

&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Select the hosts to include in the database from the list of hosts specified when the database was installed (
&lt;code&gt;install_vertica -s&lt;/code&gt;), and click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the directories in which to store the data and &lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/catalog/&#34; title=&#34;A set of files that contains information (metadata) about the objects—such as nodes, tables, constraints, and projections—in a database.&#34;&gt;catalog&lt;/a&gt; files, and click &lt;strong&gt;OK&lt;/strong&gt;.&lt;/p&gt;

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

Do not use a shared directory for more than one node. Data and catalog directories must be distinct for each node. Multiple nodes must not be allowed to write to the same data or catalog directory.

&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Catalog and data path names must contain only alphanumeric characters and cannot have leading spaces. Failure to comply with these restrictions results in database creation failure.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Catalog pathname:&lt;/strong&gt; /home/dbadmin&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Data Pathname:&lt;/strong&gt; /home/dbadmin&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Review the &lt;strong&gt;Current Database Definition&lt;/strong&gt; screen to verify that it represents the database you want to create, and then click &lt;strong&gt;Yes&lt;/strong&gt; to proceed or &lt;strong&gt;No&lt;/strong&gt; to modify the database definition.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If you click &lt;strong&gt;Yes&lt;/strong&gt;, the admin tool creates the database you defined and then displays a message to indicate that the database was successfully created.&lt;/p&gt;

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

For databases created with 3 or more nodes, the admin tool automatically sets &lt;a class=&#34;glosslink&#34; href=&#34;../../../../../en/glossary/k-safety/&#34; title=&#34;For more information, see Designing for K-Safety.&#34;&gt;K-safety&lt;/a&gt; to 1 to ensure that the database is fault tolerant in case a node fails. For more information, see &lt;a href=&#34;../../../../../en/admin/failure-recovery/#&#34;&gt;Failure recovery&lt;/a&gt; in the Administrator&#39;s Guide and &lt;a href=&#34;../../../../../en/sql-reference/functions/management-functions/catalog-functions/mark-design-ksafe/#&#34;&gt;MARK_DESIGN_KSAFE&lt;/a&gt;.

&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Click &lt;strong&gt;OK&lt;/strong&gt; to acknowledge the message.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;

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