db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1129814 - /db/derby/docs/trunk/src/adminguide/
Date Tue, 31 May 2011 17:30:28 GMT
Author: chaase3
Date: Tue May 31 17:30:27 2011
New Revision: 1129814

URL: http://svn.apache.org/viewvc?rev=1129814&view=rev
Log:
DERBY-1780  Document all supplied system procedures in the Server and Administration Guide (e.g. class loading utils and import/export)

This patch adds 14 topics to the Admin Guide and modifies 4.

Patches: DERBY-1780-1.diff

Added:
    db/derby/docs/trunk/src/adminguide/cadminimport16245.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimport27052.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimport98264.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita   (with props)
    db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita   (with props)
    db/derby/docs/trunk/src/adminguide/radminexportarguments.dita   (with props)
    db/derby/docs/trunk/src/adminguide/radminimport64241.dita   (with props)
    db/derby/docs/trunk/src/adminguide/radminimport91458.dita   (with props)
    db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita   (with props)
    db/derby/docs/trunk/src/adminguide/tadminexporting.dita   (with props)
    db/derby/docs/trunk/src/adminguide/tadminimporting.dita   (with props)
Modified:
    db/derby/docs/trunk/src/adminguide/cadminov83312.dita
    db/derby/docs/trunk/src/adminguide/cadminpreface23947.dita
    db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita
    db/derby/docs/trunk/src/adminguide/derbyadmin.ditamap

Added: db/derby/docs/trunk/src/adminguide/cadminimport16245.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimport16245.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimport16245.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimport16245.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimport16245" xml:lang="en-us">
+<title>Importing and exporting data</title>
+<shortdesc>You can import and export large amounts of data between files and
+the <ph conref="../conrefs.dita#prod/productshortname"></ph> database. Instead
+of having to use INSERT and SELECT statements, you can use
+<ph conref="../conrefs.dita#prod/productshortname"></ph> system procedures to
+import data directly from files into tables and to export data from tables into
+files.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>bulk import and export<indexterm>overview</indexterm></indexterm>
+<indexterm>import procedures<indexterm>overview</indexterm></indexterm>
+<indexterm>export procedures<indexterm>overview</indexterm></indexterm>
+<indexterm>system procedures<indexterm>import and export, overview</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> system
+procedures import and export data in delimited data file format.</p>
+<ul>
+<li>Use the export system procedures to write data from a database to one
+or more files that are stored outside of the database. You can use a procedure
+to export data from a table into a file or export data from a SELECT statement
+result into a file.</li>
+<li>Use the import system procedures to import data from a file into a table.
+If the target table already contains data, you can replace or append to the
+existing data.</li>
+</ul>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimport16245.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimport27052.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimport27052.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimport27052.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimport27052.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimport27052" xml:lang="en-us">
+<title>Bulk import and export requirements and considerations</title>
+<shortdesc>There are requirements and limitations that you must consider before
+you use the <ph conref="../conrefs.dita#prod/productshortname"></ph> import
+and export procedures.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>bulk import and export<indexterm>requirements</indexterm></indexterm>
+<indexterm>import procedures<indexterm>requirements</indexterm></indexterm>
+<indexterm>import procedures<indexterm>limitations</indexterm></indexterm>
+<indexterm>export procedures<indexterm>requirements</indexterm></indexterm>
+<indexterm>export procedures<indexterm>limitations</indexterm></indexterm>
+<indexterm>system procedures<indexterm>import and export, requirements</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<dl><dlentry>
+<dt>Database transactions</dt>
+<dd>You should issue either a COMMIT or ROLLBACK statement to complete all
+transactions and release all table-level locks before you invoke an import
+or export procedure. <ph conref="../conrefs.dita#prod/productshortname"></ph>
+issues a COMMIT or a ROLLBACK statement after each import and export procedure
+is run.<note>Imports are transactional. If an error occurs during bulk import,
+all changes are rolled back.</note></dd>
+</dlentry><dlentry>
+<dt>Database connections</dt>
+<dd>To invoke a <ph conref="../conrefs.dita#prod/productshortname"></ph> import
+or export procedure, you must be connected to the database into which the
+data is imported or from which the data is exported. Other user applications
+that access the table with a separate connection do not need to disconnect.</dd>
+</dlentry><dlentry>
+<dt>Classpath</dt>
+<dd>You must have the <filepath>derbytools.jar</filepath> file in your classpath
+before you can use the import or export procedures from
+<codeph>ij</codeph>.</dd>
+</dlentry><dlentry>
+<dt>The table must exist</dt>
+<dd>To import data into a table, the table must already exist in
+<ph conref="../conrefs.dita#prod/productshortname"></ph>. The table does not
+have to be empty. If the table is not empty, bulk import performs single row
+inserts, which result in slower performance.</dd>
+</dlentry><dlentry>
+<dt>Create indexes, keys, and unique constraints before you import</dt>
+<dd>To avoid a separate step, create the indexes, keys (primary and foreign),
+and unique constraints on tables before you import data. However, if your
+memory and disk space resources are limited, you can build the indexes and
+primary keys after importing data.</dd>
+</dlentry><dlentry>
+<dt>Data types</dt>
+<dd><ph conref="../conrefs.dita#prod/productshortname"></ph> implicitly converts
+the strings to the data type of the receiving column. If any of the implicit
+conversions fail, the whole import is aborted. For example, "3+7" cannot be
+converted into an integer. An export that encounters a runtime error stops.
+<note>You cannot import or export the XML data type.</note></dd>
+</dlentry><dlentry>
+<dt>Locking during import</dt>
+<dd>Import procedures use the same isolation level as the connection in which
+they are executed to insert data into tables. During import, the entire table
+is exclusively locked irrespective of the isolation level.</dd>
+</dlentry><dlentry>
+<dt>Locking during export</dt>
+<dd>Export procedures use the same isolation level as the connection in which
+they are executed to fetch data from tables.</dd>
+</dlentry><dlentry>
+<dt>Import behavior on tables with triggers</dt>
+<dd>The import procedures enable INSERT triggers when data is appended to the
+table. The REPLACE parameter is not allowed when triggers are enabled on the
+table.</dd>
+</dlentry><dlentry>
+<dt>Restrictions on the REPLACE parameter</dt>
+<dd>If you import data into a table that already contains data, you can either
+replace or append to the existing data. You can use the REPLACE parameter
+on tables that have dependent tables. The replaced data must maintain
+referential integrity; otherwise, the import operation will be rolled back. You
+cannot use the REPLACE parameter if the table has triggers enabled.</dd>
+</dlentry><dlentry>
+<dt>Restrictions on tables</dt>
+<dd>You cannot use import procedures to import data into a system table or a
+declared temporary table.</dd>
+</dlentry></dl>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimport27052.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimport98264.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimport98264.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimport98264.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimport98264.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimport98264" xml:lang="en-us">
+<title>Methods for running the import and export procedures</title>
+<shortdesc>You can run the import and export procedures from within an SQL
+statement using <codeph>ij</codeph> or any Java application.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>bulk import and export<indexterm>methods for running procedures</indexterm></indexterm>
+<indexterm>import procedures<indexterm>methods for running</indexterm></indexterm>
+<indexterm>export procedures<indexterm>methods for running</indexterm></indexterm>
+<indexterm>bulk import and export<indexterm>client/server mode</indexterm></indexterm>
+<indexterm>import procedures<indexterm>client/server mode</indexterm></indexterm>
+<indexterm>export procedures<indexterm>client/server mode</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<p>The import and export procedures read and write text files, and if you
+use an external file when you import or export data, you can also import and
+export blob data. The import procedures do not support read-once streams (live
+data feeds), because the procedures read the first line of the file to determine
+the number of columns, then read the file again to import the data.</p>
+<note>The import and export procedures are server-side utilities that exhibit
+different behavior in client/server mode. Typically, you use these procedures
+to import data into and export data from a locally running
+<ph conref="../conrefs.dita#prod/productshortname"></ph> database. However, you
+can use the import and export procedures when
+<ph conref="../conrefs.dita#prod/productshortname"></ph> is running in a server
+framework if you specify import and export files that are accessible to the
+server.</note>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimport98264.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimportdefaultformat" xml:lang="en-us">
+<title>File format for input and output</title>
+<shortdesc>There are specific requirements for the format of the input and
+output files when you import and export data.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>input and output file format</indexterm></indexterm>
+<indexterm>importing data<indexterm>required file format</indexterm></indexterm>
+<indexterm>exporting data<indexterm>required file format</indexterm></indexterm>
+<indexterm>system procedures<indexterm>import using</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<p>The default file format is a delimited text file with the following
+characteristics:</p>
+<ul>
+<li>Rows are separated by a newline</li>
+<li>Fields are separated by a comma (<codeph>,</codeph>)</li>
+<li>Character-based fields are delimited with double quotes
+(<codeph>"</codeph>)</li>
+</ul>
+<note type="restriction">Before you perform import or export operations, you
+must ensure that the chosen delimiter character is not contained in the data
+to be imported or exported. If you chose a delimiter character that is part
+of the data to be imported or exported, unexpected errors might occur. The
+following restrictions apply to column and character delimiters:
+<ul>
+<li>Delimiters are mutually exclusive</li>
+<li>A delimiter cannot be a line-feed character, a carriage return, or a blank
+space</li>
+<li>The default decimal point (<codeph>.</codeph>) cannot be a character
+delimiter</li>
+<li>Delimiters cannot be hexadecimal characters (0-9, a-f, A-F).</li>
+</ul></note>
+<p>The record delimiter is assumed to be a newline character. The record
+delimiter should not be used as any other delimiter.</p>
+<p>Character delimiters are permitted with the character-based fields (CHAR,
+VARCHAR, and LONG VARCHAR) of a file during import. Any pair of character
+delimiters found between the enclosing character delimiters is imported into
+the database. For example, suppose that you have the following character string:
+<codeblock>"What a ""great"" day!"</codeblock>
+The preceding character string gets imported into the database as:
+<codeblock>What a "great" day!</codeblock></p>
+<p>During export, the rule applies in reverse. For example, suppose you have
+the following character string:
+<codeblock>"The boot has a 3" heel."</codeblock>
+The preceding character string gets exported to a file as:
+<codeblock>"The boot has a 3""heel."</codeblock></p>
+<p>The following example file shows four rows and four columns in the default
+file format:
+<codeblock>1,abc,22,def
+22,,,"a is a zero-length string, b is null"
+13,"hello",454,"world"
+4,b and c are both null,,</codeblock></p>
+<p>The export procedure outputs the following values:
+<codeblock>1,"abc",22,"def"
+22,,,"a is a zero-length string, b is null"
+13,"hello",454,"world"
+4,"b and c are both null",,</codeblock></p>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimportdefaultformat.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimportidentitycol" xml:lang="en-us">
+<title>Import into tables that contain identity columns</title>
+<shortdesc>You can use the either the SYSCS_UTIL.SYSCS_IMPORT_DATA procedure
+or the SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE procedure to import
+data into a table that contains an identity column. The approach that you take
+depends on whether the identity column is GENERATED ALWAYS or GENERATED BY
+DEFAULT.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>importing data<indexterm>tables with identity columns</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<section><title>Identity columns and the REPLACE parameter</title>
+<p>If the <parmname>REPLACE</parmname> parameter is used during import, <ph
+conref="../conrefs.dita#prod/productshortname"></ph> resets its internal counter
+of the last identity value for a column to the initial value defined for the
+identity column.</p>
+</section>
+<section><title>Identity column is GENERATED ALWAYS</title>
+<p>If the identity column is defined as GENERATED ALWAYS, an identity value is
+always generated for a table row. When a corresponding row in the input file
+already contains a value for the identity column, the row cannot be inserted
+into the table and the import operation will fail.</p>
+<p>To prevent such failure, the following examples show how to specify
+parameters in the SYSCS_UTIL.SYSCS_IMPORT_DATA and
+SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE procedures to ignore data for the
+identity column from the file, and omit the column name from the insert column
+list.</p>
+<p>The following table definition contains an identity column,
+<codeph>c2</codeph>, and is used in the examples below:</p>
+<codeblock>CREATE TABLE tab1 (c1 CHAR(30), c2 INT GENERATED ALWAYS AS IDENTITY, 
+   c3 REAL, c4 CHAR(1))</codeblock>
+<ul>
+<li>Suppose that you want to import data into <codeph>tab1</codeph> from a file,
+<codeph>myfile.del</codeph>, that does not have identity column information.
+The <codeph>myfile.del</codeph> file contains three fields with the following
+data:
+<codeblock>Robert,45.2,J
+Mike,76.9,K
+Leo,23.4,I</codeblock>
+To import the data, you must explicitly list the column names in the
+<codeph>tab1</codeph> table, except for the identity column <codeph>c2</codeph>,
+when you call the procedure. For example:
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4', 
+    null, 'myfile.del',null, null, null, 0)</codeblock></li>
+<li>Suppose that you want to import data into <codeph>tab1</codeph> from a file,
+<codeph>empfile.del</codeph>, that also has identity column information. The
+file contains three fields with the following data:
+<codeblock>Robert,1,45.2,J
+Mike,2,23.4,I
+Leo,3,23.4,I</codeblock>
+To import the data, you must explicitly specify an insert column list without
+the identity column <codeph>c2</codeph> and specify the column indexes without
+identity column data when you call the procedure. For example:
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4', 
+    '1,3,4', 'empfile.del',null, null, null, 0)</codeblock></li>
+</ul>
+</section>
+<section><title>Identity column is GENERATED BY DEFAULT</title>
+<p>If the identity column is defined as GENERATED BY DEFAULT, an identity value
+is generated for a table row only if no explicit value is given. This means that
+you have several options, depending on the contents of your input file and the
+desired outcome of the import processing:</p>
+<ul>
+<li>You may omit the identity column from the insert column list, in which case 
+<ph conref="../conrefs.dita#prod/productshortname"></ph> will generate a new
+value for the identity column for each input row. You may use this option
+whether or not the input file contains values for the identity column, but note
+that if the input file contains values for the identity column, you must also
+then omit the identity column from the column indexes when you call the
+procedure.</li>
+<li>You may include the identity column in the insert column list, in which case
+<ph conref="../conrefs.dita#prod/productshortname"></ph> will use the column
+values from the input file. Of course, this option is available only if the
+input file actually contains values for the identity column.</li>
+</ul>
+<p>The following table definition contains an identity column,
+<codeph>c2</codeph>, and is used in the examples below:</p>
+<codeblock>CREATE TABLE tab1 (c1 CHAR(30),
+   c2 INT GENERATED BY DEFAULT AS IDENTITY, 
+   c3 REAL, c4 CHAR(1))</codeblock>
+<ul>
+<li>Suppose that you want to import data into <codeph>tab1</codeph> from a
+file, <codeph>myfile.del</codeph>, that does not have identity column
+information. The <codeph>myfile.del</codeph> file contains three fields with the
+following data: 
+<codeblock>Robert,45.2,J
+Mike,76.9,K
+Leo,23.4,I</codeblock>
+To import the data, you must explicitly list the column names in the
+<codeph>tab1</codeph> table, except for the identity column <codeph>c2</codeph>,
+when you call the procedure. For example:
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4', 
+    null, 'myfile.del',null, null, null, 0)</codeblock></li>
+<li>Suppose that you want to import data into <codeph>tab1</codeph> from a file,
+<codeph>empfile.del</codeph>, that also has identity column information. The
+file contains three fields with the following data:
+<codeblock>Robert,1,45.2,J
+Mike,2,23.4,I
+Leo,3,23.4,I</codeblock> 
+In this case, suppose that you wish to use the existing identity column values
+from the input file. To import the data, you may simply pass
+<codeph>null</codeph> for the insert column list and column indexes parameters
+when you call the procedure. For example:
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', NULL, 
+    NULL, 'empfile.del',null, null, null, 0)</codeblock></li>
+<li>Suppose (again) that you want to import data into <codeph>tab1</codeph>
+from a file, <codeph>empfile.del</codeph>, that also has identity column
+information, but in this case, suppose that you do <b>not</b> wish to use the
+identity column values from the input file, but would prefer to allow
+<ph conref="../conrefs.dita#prod/productshortname"></ph> to generate new
+identity column values instead. In this case, to import the data, you must
+specify an insert column list without the identity column <codeph>c2</codeph>
+and specify the column indexes without identity column data when you call the
+procedure. For example:
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4', 
+    '1,3,4', 'empfile.del',null, null, null, 0)</codeblock></li>
+</ul>
+</section>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimportidentitycol.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimportjdbc" xml:lang="en-us">
+<title>Running import and export procedures from JDBC</title>
+<shortdesc>You can run import and export procedures from a JDBC
+program.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>running from JDBC</indexterm></indexterm>
+<indexterm>JDBC<indexterm>running import and export procedures</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<conbody>
+<p>The following code fragment shows how you might call the
+SYSCS_UTIL.SYSCS_EXPORT_TABLE procedure from a Java program. In this example,
+the procedure exports the data in the <codeph>staff</codeph> table in the
+default schema to the <codeph>staff.dat</codeph> file. A percentage
+(<codeph>%</codeph>) character is used to specify the column delimiter.</p>
+<codeblock>PreparedStatement ps=conn.prepareStatement(
+    "CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (?,?,?,?,?,?)");
+    ps.setString(1,null);
+    ps.setString(2,"STAFF");
+    ps.setString(3,"staff.dat");
+    ps.setString(4,"%");
+    ps.setString(5,null);
+    ps.setString(6,null);
+    ps.execute();
+</codeblock>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimportjdbc.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,118 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimportlobs" xml:lang="en-us">
+<title>Bulk import and export of large objects</title>
+<shortdesc>You can import and export large objects (LOBs) using the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> system
+procedures.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>bulk import and export<indexterm>large objects</indexterm></indexterm>
+<indexterm>large objects <indexterm>importing and exporting</indexterm></indexterm>
+<indexterm>importing data<indexterm>large objects</indexterm></indexterm>
+<indexterm>exporting data<indexterm>large objects</indexterm></indexterm>
+<indexterm>CLOB data<indexterm>importing and exporting</indexterm></indexterm>
+<indexterm>BLOB data<indexterm>importing and exporting</indexterm></indexterm>
+<indexterm>CHAR FOR BIT DATA<indexterm>importing and exporting</indexterm></indexterm>
+<indexterm>VARCHAR FOR BIT DATA<indexterm>importing and exporting</indexterm></indexterm>
+<indexterm>LONG VARCHAR FOR BIT DATA<indexterm>importing and exporting</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<conbody>
+<section><title>Importing and exporting CLOB and BLOB data</title>
+<p>CLOB and BLOB data can be exported to the same file as the rest of the column
+data, or the LOB column data can be exported to a separate external file. When
+the LOB column data is exported to a separate external file, reference to the
+location of the LOB data is placed in the LOB column in the main export
+file.</p>
+<p>Importing and exporting LOB data using a separate external file might be
+faster than storing the LOB data in the same file as the rest of the column
+data:</p>
+<ul>
+<li>The CLOB data does not have to be scanned for the delimiters inside the
+data</li>
+<li>The BLOB data does not need to be converted to hexadecimal format</li>
+</ul>
+</section>
+<section><title>Importing and exporting other binary data</title>
+<p>When you export columns that contain the data types CHAR FOR BIT DATA,
+VARCHAR FOR BIT DATA, and LONG VARCHAR FOR BIT DATA, the column data is always
+exported to the main export file. The data is written in hexadecimal format. To
+import data into a table that has columns of these data types, the data in the
+import file for those columns must be in hexadecimal format.</p>
+</section>
+<section><title>Importing LOB data from a file that contains all of the
+data</title>
+<p>You can use the SYSCS_UTIL.SYSCS_IMPORT_TABLE and
+SYSCS_UTIL.SYSCS_IMPORT_DATA procedures to import data into a table that
+contains a LOB column. The LOB data must be stored in the same file as the other
+column data that you are importing. If you are importing data from a file that
+was exported from a non-<ph conref="../conrefs.dita#prod/productshortname"></ph>
+source, the binary data must be in hexadecimal format.</p>
+</section>
+<section><title>Importing LOB data from a separate external file</title>
+<p>You can use the SYSCS_UTIL.SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE and
+SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE procedures to import LOB data
+that is stored in a file that is separate from the main import file. These
+procedures read the LOB data using the reference that is stored in the main
+import file.  If you are importing data from a
+non-<ph conref="../conrefs.dita#prod/productshortname"></ph> source, the
+references to the LOB data must be in the main import file in the format
+<parmname>lobsFileName.Offset.length/</parmname>. This is the same method that
+the <ph conref="../conrefs.dita#prod/productshortname"></ph> export procedures
+use to export the LOB data to a separate external file.</p>
+</section>
+<section><title>Exporting LOB data to the same file as the other column
+data</title>
+<p>You can use the SYSCS_UTIL.SYSCS_EXPORT_TABLE and
+SYSCS_UTIL.SYSCS_EXPORT_QUERY procedures to write LOB data, along with rest of
+the column data, to a single export file.</p>
+<p>CLOB column data is treated same as other character data. Character
+delimiters are allowed inside the CLOB data. The export procedures write the
+delimiter inside the data as a double-delimiter.</p>
+<p>BLOB column data is written to the export file in hexadecimal format. For
+each byte of BLOB data, two characters are generated. The first character
+represents the high nibble (4 bits) in hexadecimal and the second character
+represents the low nibble.</p>
+</section>
+<section><title>Exporting LOB data to a separate external file from the other
+column data</title>
+<p>You can use the SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE and
+SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE procedures to write LOB data to a
+separate external file. These procedures include the
+<parmname>lobFileName</parmname> parameter, which specifies the name of the
+external file for the LOB data.</p>
+<p>When you use these procedures, the location of the LOB data is written to the
+main export file. The format of the  reference to the LOB stored in the main
+export file is <parmname>lobsFileName.Offset.length/</parmname>.</p>
+<ul>
+<li><parmname>Offset</parmname> is the position in the external file in
+bytes</li>
+<li><parmname>length</parmname> is the size of the LOB column data in
+bytes</li>
+</ul>
+<p>If a LOB column value is NULL, length is written as -1. No data conversion
+is performed when you export LOB data to an external file. BLOB data is written
+in binary format, and CLOB data is written using the codeset that you
+specify.</p>
+<p>See <xref href="radminimport91458.dita#radminimport91458"></xref> for
+examples using each of the import and export procedures.</p></section>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimportlobs.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita (added)
+++ db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cadminimportnulls" xml:lang="en-us">
+<title>How the import and export procedures process NULL values</title>
+<shortdesc>In a delimited file, a NULL value is exported as an empty
+field.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>NULL values</indexterm></indexterm>
+<indexterm>importing data<indexterm>NULL values</indexterm></indexterm>
+<indexterm>exporting data<indexterm>NULL values</indexterm></indexterm>
+</keywords></metadata></prolog>
+<conbody>
+<p>The following example shows the export of a four-column row where the third
+column is empty:</p>
+<codeblock>7,95,,Happy Birthday</codeblock>
+<p>The import procedures work the same way; an empty field is imported as
+a NULL value.</p>
+</conbody>
+</concept>

Propchange: db/derby/docs/trunk/src/adminguide/cadminimportnulls.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/docs/trunk/src/adminguide/cadminov83312.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminov83312.dita?rev=1129814&r1=1129813&r2=1129814&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminov83312.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminov83312.dita Tue May 31 17:30:27 2011
@@ -21,11 +21,17 @@ limitations under the License.
 <prolog>
 </prolog>
 <conbody>
-<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides some tools and features to assist database administrators, including:</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides some tools
+and features to assist database administrators, including:</p>
 <ul>
 <li>Consistency checker</li>
 <li>Online backup</li>
+<li>Procedures for importing and exporting data</li>
+<li>Database replication</li>
 <li>The ability to put a database's log on a separate device</li>
+<li>Locking information monitoring</li>
+<li>Reclaiming unused space</li>
 </ul>
-<p>These tools and features are discussed in part two of this guide. See the sections in that part for more information.</p>
+<p>These tools and features are discussed in Part Two of this guide. See the
+sections in that part for more information.</p>
 </conbody></concept>

Modified: db/derby/docs/trunk/src/adminguide/cadminpreface23947.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminpreface23947.dita?rev=1129814&r1=1129813&r2=1129814&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminpreface23947.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminpreface23947.dita Tue May 31 17:30:27 2011
@@ -38,6 +38,9 @@ line, and the Network Server API to mana
 <li><i><xref href="cadminadvtops.dita#cadminadvtops"/></i> 
 <p>Describes
 advanced topics for <ph conref="../conrefs.dita#prod/productshortname"></ph> Network Server users.</p></li>
+<li><i><xref href="radminsampleprograms.dita#radminsampleprograms"/></i>
+<p>Describes several <ph conref="../conrefs.dita#prod/productshortname"></ph>
+Network Server sample programs for Network Server users.</p></li>
 </ul>
 <p>Part two: <ph conref="../conrefs.dita#prod/productshortname"></ph> Administration Guide</p>
 <ul>
@@ -45,6 +48,11 @@ advanced topics for <ph conref="../conre
 <p>Describes how to check the consistency of <ph conref="../conrefs.dita#prod/productshortname"></ph> databases.</p></li>
 <li><i><xref href="cadminhubbkup98797.dita#cadminhubbkup98797"/></i>  
 <p>Describes how to back up a database when it is online.</p></li>
+<li><i><xref href="cadminimport16245.dita#cadminimport16245"/></i>
+<p>Describes how to import and export large amounts of data between files and
+database tables.</p></li>
+<li><i><xref href="cadminreplication.dita#cadminreplication"/></i>
+<p>Describes how to replicate databases.</p></li>
 <li><i><xref href="cadminlog98.dita#cadminlog98"/></i>  
 <p>Describes how to put a database's log on a separate device, which can improve the performance of large databases.</p></li>
 <li><i><xref href="cadminlockvti42553.dita#cadminlockvti42553"/></i>  

Modified: db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita?rev=1129814&r1=1129813&r2=1129814&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita Tue May 31 17:30:27 2011
@@ -85,8 +85,10 @@ are not actually there. Therefore, you m
 slave after a failover by calling either <codeph>SQLJ.remove_jar</codeph>
 followed by <codeph>SQLJ.install_jar</codeph>, or
 <codeph>SQLJ.replace_jar</codeph>. (For information on installing jar files, see
-"Storing jar files in a database" in the
-<ph conref="../conrefs.dita#pub/citutilities"></ph>.)</p>
+"Loading classes from a database" in the 
+<ph conref="../conrefs.dita#pub/citdevelop"></ph> and
+"System procedures for storing jar files in a database" in the
+<ph conref="../conrefs.dita#pub/citref"></ph>.)</p>
 <p>If the jar files must be available to clients immediately after a failover,
 you must stop replication and then start replication over again from the
 beginning, so that the slave database will have the same jar files as the

Modified: db/derby/docs/trunk/src/adminguide/derbyadmin.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/derbyadmin.ditamap?rev=1129814&r1=1129813&r2=1129814&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/derbyadmin.ditamap (original)
+++ db/derby/docs/trunk/src/adminguide/derbyadmin.ditamap Tue May 31 17:30:27 2011
@@ -33,6 +33,125 @@
 <vrmlist><vrm version="@RELEASE_ID_SHORT@"/></vrmlist>
 <brand>Apache Derby</brand></prodinfo>
 </topicmeta>
+<!--The following relationship table is only for the Import and Export topics.  The remaining topics need to be added to this table.-->
+<reltable>
+<!---->
+<relrow>
+<relcell>
+<topicref collection-type="family" href="cadminimport16245.dita" navtitle="Using the bulk import and export procedures">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimport98264.dita" navtitle="Methods for running the import and export procedures">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimport27052.dita" navtitle="Bulk import and export requirements and considerations">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimportlobs.dita" navtitle="Bulk import and export of large objects">
+</topicref>
+</relcell>
+<relcell>
+<topicref href="radminimport91458.dita" navtitle="Examples of bulk import and export">
+</topicref>
+</relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimportdefaultformat.dita" navtitle="File format for input and output">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="tadminimporting.dita" navtitle="Importing data using the built-in procedures">
+</topicref>
+</relcell>
+<relcell>
+<topicref href="cadminimport27052.dita" navtitle="Bulk import and export requirements and considerations">
+</topicref>
+<topicref href="radminimport91458.dita" navtitle="Examples of bulk import and export">
+</topicref>
+<topicref href="radminimport64241.dita" navtitle="Parameters for the import procedures">
+</topicref>
+</relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="radminimport64241.dita" navtitle="Parameters for the import procedures">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimportidentitycol.dita" navtitle="Import into tables that contain identity columns">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="tadminexporting.dita" navtitle="Exporting data using the built-in procedures">
+</topicref>
+</relcell>
+<relcell>
+<topicref href="cadminimport27052.dita" navtitle="Bulk import and export requirements and considerations">
+</topicref>
+<topicref href="radminimport91458.dita" navtitle="Examples of bulk import and export">
+</topicref>
+<topicref href="radminexportarguments.dita" navtitle="Parameters for the export procedures">
+</topicref>
+</relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="radminexportarguments.dita" navtitle="Parameters for the export procedures">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="radminimport91458.dita" navtitle="Examples of bulk import and export">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimportjdbc.dita" navtitle="Import and export procedures from JDBC">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="cadminimportnulls.dita" navtitle="How the import and export procedures process NULL values">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+<relrow>
+<relcell>
+<topicref href="radminimportcodeset.dita" navtitle="CODESET values for import and export procedures">
+</topicref>
+</relcell>
+<relcell></relcell>
+</relrow>
+</reltable>
 <topicref href="radmincopyright.dita" navtitle="Copyright"></topicref>
 <topicref href="radminlicense.dita" navtitle="License"></topicref>
 <topicref collection-type="family" href="cadminpreface30074.dita" navtitle="About this guide">
@@ -257,6 +376,34 @@ procedures to perform an online backup">
 <topicref href="cadminrollforward.dita" navtitle="Roll-forward recovery">
 </topicref>
 </topicref>
+<topicref collection-type="family" href="cadminimport16245.dita" navtitle="Importing and exporting data">
+<topicref href="cadminimport98264.dita" navtitle="Methods for running the import and export procedures">
+</topicref>
+<topicref href="cadminimport27052.dita" navtitle="Bulk import and export requirements and considerations">
+</topicref>
+<topicref href="cadminimportlobs.dita" navtitle="Bulk import and export of large objects">
+</topicref>
+<topicref href="cadminimportdefaultformat.dita" navtitle="File format for input and output">
+</topicref>
+<topicref href="tadminimporting.dita" navtitle="Importing data using the built-in procedures">
+<topicref href="radminimport64241.dita" navtitle="Parameters for the import procedures">
+</topicref>
+<topicref href="cadminimportidentitycol.dita" navtitle="Importing into tables that contain identity columns">
+</topicref>
+</topicref>
+<topicref href="tadminexporting.dita" navtitle="Exporting data using the built-in procedures">
+<topicref href="radminexportarguments.dita" navtitle="Parameters for the export procedures">
+</topicref>
+</topicref>
+<topicref href="radminimport91458.dita" navtitle="Examples of bulk import and export">
+</topicref>
+<topicref href="cadminimportjdbc.dita" navtitle="Running import and export procedures from JDBC">
+</topicref>
+<topicref href="cadminimportnulls.dita" navtitle="How the import and export procedures process NULL values">
+</topicref>
+<topicref href="radminimportcodeset.dita" navtitle="CODESET values for import and export procedures">
+</topicref>
+</topicref>
 <topicref collection-type="family" href="cadminreplication.dita" navtitle="Replicating databases">
 <topicref href="cadminreplicstartrun.dita" navtitle="Starting and running replication">
 </topicref>

Added: db/derby/docs/trunk/src/adminguide/radminexportarguments.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/radminexportarguments.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/radminexportarguments.dita (added)
+++ db/derby/docs/trunk/src/adminguide/radminexportarguments.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="radminexportarguments" xml:lang="en-us">
+<title>Parameters for the export procedures</title>
+<shortdesc>The <ph conref="../conrefs.dita#prod/productshortname"></ph> export
+procedures use specific parameters.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>export parameters</indexterm></indexterm>
+<indexterm>bulk export<indexterm>procedure parameters</indexterm></indexterm>
+<indexterm>exporting data<indexterm>procedure parameters</indexterm></indexterm>
+</keywords></metadata></prolog>
+<refbody>
+<section><dl><dlentry>
+<dt id="radminexportschemaname">SCHEMANAME</dt>
+<dd>Specifies the schema of the table. You can specify a NULL value to use the
+default schema name. The <parmname>SCHEMANAME</parmname> parameter takes an
+input argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportselectstatement">SELECTSTATEMENT</dt>
+<dd>Specifies the SELECT statement query that returns the data to be exported.
+Specifying a NULL value will result in an error. The
+<parmname>SELECTSTATEMENT</parmname> parameter takes an input argument that is
+a VARCHAR(32672) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexporttablename">TABLENAME</dt>
+<dd>Specifies the table name of the table or view from which the data is to
+be exported. This table cannot be a system table or a declared temporary table.
+The string must exactly match the case of the table name. Specifying a NULL
+value results in an error. The <parmname>TABLENAME</parmname> parameter takes
+an input argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportfilename">FILENAME</dt>
+<dd>Specifies the file to which the data is to be exported. If the path is
+omitted, the current working directory is used. If the name of a file that
+already exists is specified, the export utility overwrites the contents of the
+file; it does not append the information. The specified location of the file
+should refer to the server-side location if you are using the Network Server.
+Specifying a NULL value results in an error. The <parmname>FILENAME</parmname>
+parameter takes an input argument that is a VARCHAR(32672) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportcolumndelimiter">COLUMNDELIMITER</dt>
+<dd>Specifies a column delimiter. The specified character is used in place of a
+comma to signify the end of a column. You can specify a NULL value to use the
+default value of a comma. The <parmname>COLUMNDELIMITER</parmname> parameter
+must be a CHAR(1) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportcharacterdelimiter">CHARACTERDELIMITER</dt>
+<dd>Specifies a character delimiter. The specified character is used in place of
+double quotation marks to enclose a character string. You can specify a NULL
+value to use the default value of a double quotation mark. The
+<parmname>CHARACTERDELIMITER</parmname> parameter takes an input argument that
+is a CHAR(1) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportcodeset">CODESET</dt>
+<dd>Specifies the code set of the data in the export file. The code set name
+should be one of the Java supported character encoding sets.  Data is converted
+from the database code page to the specified code page before writing to the
+file. You can specify a NULL value to write the data in the same code page
+as the JVM in which it is being executed. The <parmname>CODESET</parmname>
+parameter takes an input argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminexportlobsfilename">LOBSFILENAME</dt>
+<dd>Specifies the file that the large object data is exported to. If the path is
+omitted, the LOB file is created in the same directory as the main export file.
+If you specify the name of an existing file, the export utility overwrites the
+contents of the file. The data is not appended to the file. If you are using the
+Network Server, the file should be in a server-side location. Specifying a NULL
+value results in an error. The <parmname>LOBSFILENAME</parmname> parameter takes
+an input argument that is a VARCHAR(32672) data type.</dd>
+</dlentry></dl>
+<p>If you create a schema, table, or column name as a non-delimited identifier,
+you must pass the name to the export procedure using all uppercase characters.
+If you created a schema or table name as a delimited identifier, you must pass
+the name to the export procedure using the same case that was used when it was
+created.</p>
+</section>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/adminguide/radminexportarguments.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/radminimport64241.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/radminimport64241.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/radminimport64241.dita (added)
+++ db/derby/docs/trunk/src/adminguide/radminimport64241.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="radminimport64241" xml:lang="en-us">
+<title>Parameters for the import procedures</title>
+<shortdesc>The <ph conref="../conrefs.dita#prod/productshortname"></ph> import
+procedures use specific parameters.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>import parameters</indexterm></indexterm>
+<indexterm>bulk import<indexterm>procedure parameters</indexterm></indexterm>
+<indexterm>importing data<indexterm>procedure parameters</indexterm></indexterm>
+</keywords></metadata></prolog>
+<refbody>
+<section>
+<dl><dlentry>
+<dt id="radminimportschemaname">SCHEMANAME</dt>
+<dd>Specifies the schema of the table. You can specify a NULL value to use
+the default schema name. The <parmname>SCHEMANAME</parmname> parameter takes
+an input argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimport27122">TABLENAME</dt>
+<dd>Specifies the name of the table into which the data is to be imported.
+This table cannot be a system table or a declared temporary table. The string
+must exactly match the case of the table name. Specifying a NULL value results
+in an error. The <parmname>TABLENAME</parmname> parameter takes an input
+argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportinsertcolumns">INSERTCOLUMNS</dt>
+<dd>Specifies the comma-separated column names of the table into which the
+data will be imported. You can specify a NULL value to import into all columns
+of the table. The <parmname>INSERTCOLUMNS</parmname> parameter takes an input
+argument that is a VARCHAR(32672) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportcolumnindexes">COLUMNINDEXES</dt>
+<dd>Specifies the comma-separated column indexes (numbered from one) of the
+input data fields that will be imported. You can specify a NULL value to use all
+input data fields in the file. The <parmname>COLUMNINDEXES</parmname> parameter
+takes an input argument that is a VARCHAR(32672) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportfilename">FILENAME</dt>
+<dd>Specifies the name of the file that contains the data to be imported.
+If the path is omitted, the current working directory is used. The specified
+location of the file should refer to the server side location if you are using
+the Network Server. Specifying a NULL value results in an error. The
+<parmname>FILENAME</parmname> parameter takes an input argument that is a
+VARCHAR(32672) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportcolumndelimiter">COLUMNDELIMITER</dt>
+<dd>Specifies a column delimiter. The specified character is used in place
+of a comma to signify the end of a column. You can specify a NULL value to
+use the default value of a comma. The <parmname>COLUMNDELIMITER</parmname>
+parameter takes an input argument that is a CHAR(1) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportcharacterdelimiter">CHARACTERDELIMITER</dt>
+<dd>Specifies a character delimiter. The specified character is used in place
+of double quotation marks to enclose a character string. You can specify a
+NULL value to use the default value of a double quotation mark. The
+<parmname>CHARACTERDELIMITER</parmname> parameter takes an input argument that
+is a CHAR(1) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportcodesetarg">CODESET</dt>
+<dd>Specifies the code set of the data in the input file. The code set name
+should be one of the Java supported character encoding sets. Data is converted
+from the specified code set to the database code set (UTF-8). You can specify
+a NULL value to interpret the data file in the same code set as the JVM in
+which it is being executed. The <parmname>CODESET</parmname> parameter takes
+an input argument that is a VARCHAR(128) data type.</dd>
+</dlentry><dlentry>
+<dt id="radminimportreplace">REPLACE</dt>
+<dd>A non-zero value for the replace parameter will import in REPLACE mode,
+while a zero value will import in INSERT mode. REPLACE mode deletes all existing
+data from the table by truncating the table and inserts the imported data.
+The table definition and the index definitions are not changed. You can import
+with REPLACE mode only if the table already exists. INSERT mode adds the
+imported data to the table without changing the existing table data. Specifying
+a NULL value results in an error. The <parmname>REPLACE</parmname> parameter
+takes an input argument that is a SMALLINT data type.</dd>
+</dlentry></dl>
+<p>If you create a schema, table, or column name as a non-delimited identifier,
+you must pass the name to the import procedure using all uppercase characters.
+If you created a schema, table, or column name as a delimited identifier, you
+must pass the name to the import procedure using the same case that was used
+when it was created.</p>
+</section>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/adminguide/radminimport64241.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/radminimport91458.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/radminimport91458.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/radminimport91458.dita (added)
+++ db/derby/docs/trunk/src/adminguide/radminimport91458.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="radminimport91458" xml:lang="en-us">
+<title>Examples of bulk import and export</title>
+<shortdesc>All of the examples in this section are run using the
+<codeph>ij</codeph> utility.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>examples</indexterm></indexterm>
+<indexterm>bulk export<indexterm>examples</indexterm></indexterm>
+<indexterm>exporting data<indexterm>examples</indexterm></indexterm>
+<indexterm>bulk import<indexterm>examples</indexterm></indexterm>
+<indexterm>importing data<indexterm>examples</indexterm></indexterm>
+</keywords></metadata></prolog>
+<refbody>
+<section><title>Example: Importing all data from a file</title>
+<p>The following example shows how to import data into the STAFF table in a
+sample database from the <codeph>myfile.del</codeph> file. The data will be
+appended to the existing data in the table.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE( 
+    null,'STAFF','myfile.del',null,null,null,0);</codeblock>
+</section>
+<section><title>Example: Importing all data from a delimited file</title>
+<p>The following example shows how to import data into the STAFF table in a
+sample database from a delimited data file, <codeph>myfile.del</codeph>. This
+example defines the percentage character (<codeph>%</codeph>) as the string
+delimiter, and a semicolon as the column delimiter. The data will be appended to
+the existing data in the table.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(
+    null,'STAFF','c:\output\myfile.del',';','%',null,0);</codeblock>
+</section>
+<section><title>Example: Importing all data from a table, using a separate
+import file for the LOB data</title>
+<p>The following example shows how to import data into the STAFF table in a
+sample database from a delimited data file, <codeph>staff.del</codeph>. The
+import file <codeph>staff.del</codeph> is the main import file and contains
+references that point to a separate file which contains the LOB data. This
+example specifies a comma as the column delimiter. The data will be appended to
+the existing data in the table.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE(
+    null,'STAFF','c:\data\staff.del',',','"','UTF-8',0);</codeblock>
+</section>
+<section><title>Example: Importing data into specific columns, using a separate
+import file for the LOB data</title>
+<p>The following example shows how to import data into several columns of the
+STAFF table. The STAFF table includes a LOB column in a sample database. The
+import file, <codeph>staff.del</codeph>, is a delimited data file. The
+<codeph>staff.del</codeph> file contains references that point to a separate
+file which contains the LOB data. The data in the import file is formatted using
+double quotation marks (<codeph>"</codeph>) as the string delimiter and a comma
+(<codeph>,</codeph>) as the  column delimiter. The data will be appended to the
+existing data in the STAFF table.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE(
+    null, 'STAFF', 'NAME,DEPT,SALARY,PICTURE', '2,3,4,6', 
+    'c:\data\staff.del', ',','"','UTF-8',  0);</codeblock>
+</section>
+<section><title>Example: Exporting all data from a table to a single export
+file</title>
+<p>The following example shows how to export data from the STAFF table in a
+sample database to the file <codeph>myfile.del</codeph>.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE(
+    null,'STAFF','myfile.del',null,null,null);</codeblock>
+</section>
+<section><title>Example: Exporting data from a table to a single delimited
+export file</title>
+<p>The following example shows how to export data from the STAFF table to a
+delimited data file, <codeph>myfile.del</codeph>, with the percentage character
+(<codeph>%</codeph>) as the character delimiter, and a semicolon as the column
+delimiter from the STAFF table.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE(
+    null,'STAFF','c:\output\myfile.del',';','%',null);</codeblock>
+</section>
+<section><title>Example: Exporting all data from a table, using a separate
+export file for the LOB data</title>
+<p>The following example shows how to export data from the STAFF table in a
+sample database to the main file, <codeph>staff.del</codeph>, and the LOB export
+file, <codeph>pictures.dat</codeph>.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE(null,'STAFF',
+    'c:\data\staff.del',',','"','UTF-8', 'c:\data\pictures.dat');</codeblock>
+</section>
+<section><title>Example: Exporting data from a query to a single export
+file</title>
+<p>The following example shows how to export employee data in department 20 from
+the STAFF table in a sample database to the file
+<codeph>awards.del</codeph>.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY(
+    'SELECT * FROM STAFF WHERE dept=20', 
+    'c:\output\awards.del',null,null,null);</codeblock>
+</section>
+<section><title>Example: Exporting data from a query, using a separate export
+file for the LOB data </title>
+<p>The following example shows how to export employee data in department 20 from
+the STAFF table in a sample database to the main file,
+<codeph>staff.del</codeph>, and the LOB data to the file
+<codeph>pictures.dat</codeph>.</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE(
+    'SELECT * FROM STAFF WHERE dept=20',
+    'c:\data\staff.del', ',' ,'"', 
+    'UTF-8','c:\data\pictures.dat');</codeblock>
+</section>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/adminguide/radminimport91458.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita (added)
+++ db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="radminimportcodeset" xml:lang="en-us">
+<title>CODESET values for import and export procedures</title>
+<shortdesc>Import and export procedures accept arguments to specify codeset
+values. You can specify the codeset (character encoding) for import and export
+procedures to override the system default.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>codesets</indexterm></indexterm>
+<indexterm>codeset values<indexterm>import and export procedures</indexterm></indexterm>
+</keywords></metadata></prolog>
+<refbody>
+<section>
+<p>For a table that shows a sample of the character encodings supported
+by the Java Development Kit, see "derby.ui.codeset property" in the
+<ph conref="../conrefs.dita#pub/citutilities"></ph>. To review the complete list
+of character encodings, refer to your Java documentation.</p>
+</section>
+<section><title>Examples: Specifying the codeset in import and export
+procedures</title>
+<p>The following example shows how to specify UTF-8 encoding to export to the
+<codeph>staff.dat</codeph> table:</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE(
+    NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8')</codeblock>
+<p>The following example shows how to specify UTF-8 encoding to import from the
+<codeph>staff.dat</codeph> table:</p>
+<codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(
+    NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8',0)</codeblock>
+</section>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/adminguide/radminimportcodeset.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/tadminexporting.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/tadminexporting.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/tadminexporting.dita (added)
+++ db/derby/docs/trunk/src/adminguide/tadminexporting.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
+ "../dtd/task.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!--##### DO NOT CHANGE ANYTHING ABOVE THIS LINE #####-->
+<task id="tadminexporting" xml:lang="en-us">
+<title>Exporting data using the built-in procedures</title>
+<shortdesc>You can use the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> export procedures to
+export all of the data from table or query, or to export LOB data separately
+from the other data.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>bulk export</indexterm></indexterm>
+<indexterm>exporting data</indexterm>
+<indexterm>system procedures<indexterm>export using</indexterm></indexterm>
+</keywords></metadata></prolog>
+<taskbody>
+<context></context>
+<steps>
+<step><cmd>Use the following table to choose the correct procedure for the type
+of export that you want to perform. For examples of these procedures, see
+<xref href="radminimport91458.dita#radminimport91458"></xref>.</cmd>
+<info>
+<table>
+<title>Using the built-in export procedures</title>
+<tgroup cols="3" colsep="1" rowsep="1">
+<colspec colname="col1" colnum="1" colwidth="33*"/>
+<colspec colname="col2" colnum="2" colwidth="67*"/>
+<thead>
+<row valign="bottom">
+<entry colname="col1">Type of Export</entry>
+<entry colname="col2">Procedure to Use</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="col1">To export all the data from a table to a single export
+file, including the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_EXPORT_TABLE
+ (IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportschemaname">SCHEMANAME</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexporttablename">TABLENAME</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcodeset">CODESET</xref> VARCHAR(128))</codeblock></entry>
+</row>
+<row>
+<entry colname="col1">To export all the data from a table, and place the LOB
+data into a separate export file</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE
+ (IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportschemaname">SCHEMANAME</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexporttablename">TABLENAME</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcodeset">CODESET</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportlobsfilename">LOBSFILNAME</xref> VARCHAR(32672))</codeblock>
+<p>A reference to the location of the LOB data is placed in the LOB column in
+the main export file.</p></entry>
+</row>
+<row>
+<entry colname="col1">To export the result of a SELECT statement to a single
+file, including the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_EXPORT_QUERY
+ (IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportselectstatement">SELECTSTATEMENT</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcodeset">CODESET</xref> VARCHAR(128))</codeblock></entry>
+</row>
+<row>
+<entry colname="col1">To export the result of a SELECT statement to a main
+export file, and place the LOB data into a separate export file</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE
+ (IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportselectstatement">SELECTSTATEMENT</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportcodeset">CODESET</xref> VARCHAR(128),
+  IN <xref href="radminexportarguments.dita#radminexportarguments/radminexportlobsfilename">LOBSFILENAME</xref> VARCHAR(32672))</codeblock>
+<p>A reference to the LOB data is written to the main export file.</p></entry>
+</row>
+</tbody>
+</tgroup>
+</table> 
+</info>
+</step>
+</steps>
+</taskbody>
+</task>

Propchange: db/derby/docs/trunk/src/adminguide/tadminexporting.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Added: db/derby/docs/trunk/src/adminguide/tadminimporting.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/tadminimporting.dita?rev=1129814&view=auto
==============================================================================
--- db/derby/docs/trunk/src/adminguide/tadminimporting.dita (added)
+++ db/derby/docs/trunk/src/adminguide/tadminimporting.dita Tue May 31 17:30:27 2011
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
+ "../dtd/task.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!--##### DO NOT CHANGE ANYTHING ABOVE THIS LINE #####-->
+<task id="tadminimporting" xml:lang="en-us">
+<title>Importing data using the built-in procedures</title>
+<shortdesc>You can use the
+<ph conref="../conrefs.dita#prod/productshortname"></ph> import procedures to
+import all of the data from a table or query, or to import LOB data separately
+from the other data.</shortdesc>
+<prolog><metadata><keywords>
+<indexterm>import and export procedures<indexterm>bulk import</indexterm></indexterm>
+<indexterm>importing data</indexterm>
+<indexterm>system procedures<indexterm>import using</indexterm></indexterm>
+</keywords></metadata></prolog>
+<taskbody>
+<context></context>
+<steps>
+<step><cmd>Use the following table to choose the correct procedure for the type
+of import that you want to perform. For examples of these procedures, see
+<xref href="radminimport91458.dita#radminimport91458"></xref>.</cmd>
+<info>
+<table>
+<title>Using the built-in import procedures</title>
+<tgroup cols="3" colsep="1" rowsep="1">
+<colspec colname="col1" colnum="1" colwidth="33*"/>
+<colspec colname="col2" colnum="2" colwidth="67*"/>
+<thead>
+<row valign="bottom">
+<entry colname="col1">Type of Import</entry>
+<entry colname="col2">Procedure to Use</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="col1">To import all the data to a table, where the import file
+contains the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_IMPORT_TABLE 
+ (IN <xref href="radminimport64241.dita#radminimport64241/radminimportschemaname">SCHEMANAME</xref> VARCHAR(128), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimport27122">TABLENAME</xref> VARCHAR(128), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportfilename">FILENAME</xref> VARCHAR(32672), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcharacterdelimiter">CHARACTERDELIMITER</xref>  CHAR(1), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcodesetarg">CODESET</xref> VARCHAR(128), 
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportreplace">REPLACE</xref> SMALLINT)</codeblock></entry>
+</row>
+<row>
+<entry colname="col1">To import the data to a table, where the LOB data is
+stored in a separate file and the main import file contains all of the other
+data with a reference to the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE
+ (IN <xref href="radminimport64241.dita#radminimport64241/radminimportschemaname">SCHEMANAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimport27122">TABLENAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcodesetarg">CODESET</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportreplace">REPLACE</xref> SMALLINT)</codeblock>
+<p>The import utility looks in the main import file for a reference to the
+location of the LOB data. The format of the reference to the LOB stored in the
+main import file must be <codeph>lobsFileName.Offset.length/</codeph>.</p>
+</entry>
+</row>
+<row>
+<entry colname="col1">To import data from a file to a subset of columns in a
+table, where the import file contains the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_IMPORT_DATA
+ (IN <xref href="radminimport64241.dita#radminimport64241/radminimportschemaname">SCHEMANAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimport27122">TABLENAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportinsertcolumns">INSERTCOLUMNS</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumnindexes">COLUMNINDEXES</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcodesetarg">CODESET</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportreplace">REPLACE</xref> SMALLINT)</codeblock>
+<p>You must specify the INSERTCOLUMNS parameter on the table into which data
+will be imported. You must specify the COLUMNINDEXES parameter to import data
+fields from a file to column in a table.</p></entry>
+</row>
+<row>
+<entry colname="col1">To import data to a subset of columns in a table, where
+the LOB data is stored in a separate file and the main import file contains all
+of the other data with a reference to the LOB data</entry>
+<entry colname="col2"><codeblock>SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE
+ (IN <xref href="radminimport64241.dita#radminimport64241/radminimportschemaname">SCHEMANAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimport27122">TABLENAME</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportinsertcolumns">INSERTCOLUMNS</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumnindexes">COLUMNINDEXES</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportfilename">FILENAME</xref> VARCHAR(32672),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcolumndelimiter">COLUMNDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcharacterdelimiter">CHARACTERDELIMITER</xref> CHAR(1),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportcodesetarg">CODESET</xref> VARCHAR(128),
+  IN <xref href="radminimport64241.dita#radminimport64241/radminimportreplace">REPLACE</xref> SMALLINT)</codeblock>
+<p>The import utility looks in the main import file for a reference to the
+location of the LOB data. The format of the reference to the LOB stored in the
+main import file must be <codeph>lobsFileName.Offset.length/</codeph>.</p>
+</entry>
+</row>
+</tbody>
+</tgroup>
+</table> 
+</info></step>
+</steps>
+</taskbody>
+</task>

Propchange: db/derby/docs/trunk/src/adminguide/tadminimporting.dita
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message