+<H2><A NAME="ss11.31">11.31</A> <A HREF="adminmanual_en.html#toc11.31">dbcreate <name> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name></B> Create a database entry</CODE></P>
+
+<H2><A NAME="ss11.32">11.32</A> <A HREF="adminmanual_en.html#toc11.32">dbcreate <name> chain <name> [<name>..] (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry</CODE></P>
+
+<H2><A NAME="ss11.33">11.33</A> <A HREF="adminmanual_en.html#toc11.33">dbcreate <name> cmd <dxspider command> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> cmd <dxspider command></B> make a local command available as a DB</CODE></P>
+<P>DBCREATE allows you to define a database in the system. It doesn't actuallycreate anything, just defines it.The databases that are created are simple DB_File hash databases, they are therefore already 'indexed'.You can define a local database with the first form of the command eg:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE sdx_qsl chain sql_ad
+</PRE>
+</CODE></BLOCKQUOTE>
+No checking is done to see if the any of the chained databases exist, infact it is usually better to do the above staement first then do each ofthe chained databases.Databases can exist offsite. To define a database that lives on another node do:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE buckmaster remote gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE qsl chain gb7dxc
+</PRE>
+</CODE></BLOCKQUOTE>
+To see what databases have been defined do:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+</PRE>
+</CODE></BLOCKQUOTE>
+It would be normal for you to add an entry into your local Aliases fileto allow people to use the 'SHOW/<dbname>' style syntax. So you wouldneed to add a line like:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
+</PRE>
+</CODE></BLOCKQUOTE>
+to allow
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK g1tlh
+</PRE>
+</CODE></BLOCKQUOTE>
+to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBCREATE dxqsl cmd show/dxqsl
+</PRE>
+</CODE></BLOCKQUOTE>
+You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases.See DBSHOW for generic database enquiry</P>
+<H2><A NAME="ss11.34">11.34</A> <A HREF="adminmanual_en.html#toc11.34">dbcreate <name> remote <node> (9)</A>
+</H2>
+
+<P><CODE><B>dbcreate <name> remote <node></B> Create a remote database entry</CODE></P>
+
+<H2><A NAME="ss11.35">11.35</A> <A HREF="adminmanual_en.html#toc11.35">dbimport <dbname> <filename> (9)</A>
+</H2>
+
+<P><CODE><B>dbimport <dbname> <filename></B> Import AK1A data into a database</CODE></P>
+<P>If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an existingdatabase. For example:-
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBIMPORT oblast /tmp/OBLAST.FUL
+</PRE>
+</CODE></BLOCKQUOTE>
+will import the standard OBLAST database that comes with AK1A into theoblast database held locally.</P>
+<H2><A NAME="ss11.36">11.36</A> <A HREF="adminmanual_en.html#toc11.36">dbremove <dbname> (9)</A>
+</H2>
+
+<P><CODE><B>dbremove <dbname></B> Delete a database</CODE></P>
+<P>DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example:
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBREMOVE oblast
+</PRE>
+</CODE></BLOCKQUOTE>
+will remove the oblast database from the system and it will also removethe associated datafile.I repeat:There is no warning, no comeback, no safety net.You have been warned.</P>
+<H2><A NAME="ss11.37">11.37</A> <A HREF="adminmanual_en.html#toc11.37">dbshow <dbname> <key> (0)</A>