From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/bdb-sql/BDB-SQL-Guide.pdf | Bin 341898 -> 383726 bytes .../bdb-sql/accessing_bdb_sql_databases.title.html | 2 +- docs/bdb-sql/addedpragmas.html | 96 +++++-- docs/bdb-sql/admin.html | 40 ++- docs/bdb-sql/bdb-concepts.html | 2 +- docs/bdb-sql/bfile-c.html | 2 +- docs/bdb-sql/bfile-extension.html | 10 +- docs/bdb-sql/bfile-sql.html | 2 +- docs/bdb-sql/buildinstall.html | 25 +- docs/bdb-sql/changedpragmas.html | 2 +- docs/bdb-sql/datamigration.html | 10 +- docs/bdb-sql/dbfeatures.html | 2 +- docs/bdb-sql/dbsqlbasics.html | 21 +- docs/bdb-sql/index.html | 86 +++++- docs/bdb-sql/journaldirectory.html | 2 +- docs/bdb-sql/lockhandling.html | 2 +- docs/bdb-sql/lockingnotes.html | 2 +- docs/bdb-sql/miscdiff.html | 2 +- docs/bdb-sql/moreinfo.html | 14 +- docs/bdb-sql/mvcc.html | 2 +- docs/bdb-sql/normal-sql.html | 14 +- docs/bdb-sql/preface.html | 4 +- docs/bdb-sql/recoverysql.html | 80 ++++++ docs/bdb-sql/rep_usageexamples.html | 4 +- docs/bdb-sql/reppragma.html | 299 ++++++++++++++++++++- docs/bdb-sql/repstatistics.html | 2 +- docs/bdb-sql/selectpage_size.html | 2 +- docs/bdb-sql/sequencesupport.html | 9 +- docs/bdb-sql/sql_encryption.html | 83 ++++-- docs/bdb-sql/sqlrep.html | 121 ++++++++- docs/bdb-sql/statsql.html | 80 ++++++ docs/bdb-sql/sync.html | 14 +- docs/bdb-sql/unsupportedpragmas.html | 2 +- docs/bdb-sql/verifysql.html | 82 ++++++ 34 files changed, 1004 insertions(+), 116 deletions(-) create mode 100644 docs/bdb-sql/recoverysql.html create mode 100644 docs/bdb-sql/statsql.html create mode 100644 docs/bdb-sql/verifysql.html (limited to 'docs/bdb-sql') diff --git a/docs/bdb-sql/BDB-SQL-Guide.pdf b/docs/bdb-sql/BDB-SQL-Guide.pdf index dfcca036..4b69fee4 100644 Binary files a/docs/bdb-sql/BDB-SQL-Guide.pdf and b/docs/bdb-sql/BDB-SQL-Guide.pdf differ diff --git a/docs/bdb-sql/accessing_bdb_sql_databases.title.html b/docs/bdb-sql/accessing_bdb_sql_databases.title.html index 9e8d8ea5..dfd6675b 100644 --- a/docs/bdb-sql/accessing_bdb_sql_databases.title.html +++ b/docs/bdb-sql/accessing_bdb_sql_databases.title.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

diff --git a/docs/bdb-sql/addedpragmas.html b/docs/bdb-sql/addedpragmas.html index c9fabbeb..8f94b31f 100644 --- a/docs/bdb-sql/addedpragmas.html +++ b/docs/bdb-sql/addedpragmas.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -73,6 +73,11 @@ PRAGMA bdbsql_vacuum_pages +
+ + PRAGMA large_record_opt + +
PRAGMA multiversion @@ -289,6 +294,38 @@ PRAGMA auto_vacuum.

+
+
+
+
+

PRAGMA large_record_opt

+
+
+
+ 
PRAGMA large_record_opt [= number bytes]
+

+ Enables optimized storage of large records. Any record + larger than the given number of bytes will be stored in + a new format that improves read and write performance + for large records. +

+

+ This pragma must be called before any data is added to + the database, otherwise it will be ignored. +

+

+ This optimization is incompatible with encryption, and + SQLITE_ReadUncommitted. +

+

+ This optimization stores large records in a folder + called __db_bl in the journal folder. + So if the database is manually moved to a new location, + the folder with the large records most also be moved. + The Online Backup Function will automatically backup up + these records with the rest of the database. +

+
@@ -350,12 +387,6 @@ information into the shared cache without waiting for a write operation to complete.

-

- Specifying this PRAGMA without a percentage value - causes the current trickle value to be displayed. - Specify 0 to turn the trickle - functionality off. -

@@ -381,7 +412,7 @@

- Seven PRAGMAs were added to control replication. + Fourteen PRAGMAs were added to manage and control replication. They are described in Using Replication with the SQL API:

@@ -399,37 +430,72 @@ diff --git a/docs/bdb-sql/admin.html b/docs/bdb-sql/admin.html index e54174ed..bed12e8c 100644 --- a/docs/bdb-sql/admin.html +++ b/docs/bdb-sql/admin.html @@ -14,7 +14,7 @@
-

Library Version 11.2.5.3

+

Library Version 12.1.6.1

@@ -50,7 +50,7 @@
- Backing Up Replicated Berkeley DB SQL Databases + Backing Up Replicated Berkeley DB SQL Databases
@@ -93,6 +93,21 @@ +
+ + Catastrophic Recovery + +
+
+ + Database Statistics + +
+
+ + Verify Database Structure + +

@@ -111,7 +126,7 @@

- Backing Up Replicated Berkeley DB SQL Databases + Backing Up Replicated Berkeley DB SQL Databases
@@ -131,23 +146,21 @@ To learn how to use SQLite Online Backup API, see the official SQLite Documentation Page.

-

- If you are using replication, you will also need to copy the - file that contains the replication pragma information in order - to have a full backup. To do that copy the file named - pragma from the database journal directory. -

-

Backing Up Replicated Berkeley DB SQL Databases

+

Backing Up Replicated Berkeley DB SQL Databases

- When BDB SQL interface databases are replicated the process for backing up - a regular database should be followed. The user must then copy + When BDB SQL interface databases are replicated .dump and the SQLite Online + Backup API are not sufficient to create a backup. In a separate + process you should use the db_hotbackup utility or other methods + described in the + Oracle Berkeley DB Backup Procedures + section. You must then copy some additional files for the backup to be complete.

@@ -176,6 +189,9 @@

  • __db.rep.system
    • +
  • + pragma +

    • diff --git a/docs/bdb-sql/bdb-concepts.html b/docs/bdb-sql/bdb-concepts.html index 61308339..ec7715d3 100644 --- a/docs/bdb-sql/bdb-concepts.html +++ b/docs/bdb-sql/bdb-concepts.html @@ -14,7 +14,7 @@

    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/bfile-c.html b/docs/bdb-sql/bfile-c.html index 49108de9..6c26dd84 100644 --- a/docs/bdb-sql/bfile-c.html +++ b/docs/bdb-sql/bfile-c.html @@ -13,7 +13,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/bfile-extension.html b/docs/bdb-sql/bfile-extension.html index 67f91c93..4e5210ad 100644 --- a/docs/bdb-sql/bfile-extension.html +++ b/docs/bdb-sql/bfile-extension.html @@ -8,20 +8,20 @@ - +
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    - + @@ -95,12 +95,12 @@
    Appendix A. Using the BFILE Extension
    Prev Prev     Next
    - + - + diff --git a/docs/bdb-sql/bfile-sql.html b/docs/bdb-sql/bfile-sql.html index d4b6d20e..eb11bd37 100644 --- a/docs/bdb-sql/bfile-sql.html +++ b/docs/bdb-sql/bfile-sql.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    Prev Prev     Next
    Data Migration Verify Database Structure  Home
    diff --git a/docs/bdb-sql/buildinstall.html b/docs/bdb-sql/buildinstall.html index b0256550..cc275452 100644 --- a/docs/bdb-sql/buildinstall.html +++ b/docs/bdb-sql/buildinstall.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -58,7 +58,7 @@

    The BDB SQL interface comes as a part of the Oracle Berkeley DB download. This can be downloaded from the - Oracle Berkeley DB download page. + Oracle Berkeley DB download page.

    @@ -89,7 +89,7 @@

  • - libdb_sql50.dll + libdb_sql60.dll

    This is the library that provides the BDB SQL interface. @@ -99,6 +99,23 @@

    • +
    +

    Note

    +

    + If you are upgrading an existing BDB SQL + installation, and you are upgrading from release + 6.1.19 or lower, then see the SQL database upgrade + instructions + + at + + Updated SQLite Version + + + + in the Berkeley DB Installation and Build Guide. +

    +
    @@ -181,7 +198,7 @@

    Download the ADO.NET package from the - Oracle Berkeley DB download page. + Oracle Berkeley DB download page.

    diff --git a/docs/bdb-sql/changedpragmas.html b/docs/bdb-sql/changedpragmas.html index 32d8729a..ec8a1116 100644 --- a/docs/bdb-sql/changedpragmas.html +++ b/docs/bdb-sql/changedpragmas.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/datamigration.html b/docs/bdb-sql/datamigration.html index fe0951f1..24e0cc02 100644 --- a/docs/bdb-sql/datamigration.html +++ b/docs/bdb-sql/datamigration.html @@ -9,12 +9,12 @@ - +
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -23,7 +23,7 @@ - +
    Prev  Chapter 5. Administrating Berkeley DB SQL Databases Next Next
    @@ -130,14 +130,14 @@ Up -  Next +  Next Syncing with Oracle Databases  Home -  Appendix A. Using the BFILE Extension +  Catastrophic Recovery
    diff --git a/docs/bdb-sql/dbfeatures.html b/docs/bdb-sql/dbfeatures.html index d20be241..15f932fc 100644 --- a/docs/bdb-sql/dbfeatures.html +++ b/docs/bdb-sql/dbfeatures.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/dbsqlbasics.html b/docs/bdb-sql/dbsqlbasics.html index 2fb8f662..ce156803 100644 --- a/docs/bdb-sql/dbsqlbasics.html +++ b/docs/bdb-sql/dbsqlbasics.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -151,6 +151,11 @@ PRAGMA bdbsql_vacuum_pages +
    + + PRAGMA large_record_opt + +
    PRAGMA multiversion @@ -193,6 +198,20 @@ Encryption
    +
    +
    +
    + + Berkeley DB encryption + +
    +
    + + SQLite Encryption Extension + +
    +
    +
    Using Sequences diff --git a/docs/bdb-sql/index.html b/docs/bdb-sql/index.html index 41981dc5..2122709b 100644 --- a/docs/bdb-sql/index.html +++ b/docs/bdb-sql/index.html @@ -12,7 +12,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -30,11 +30,11 @@
    -

    Getting Started with the Oracle Berkeley DB SQL APIs

    +

    Getting Started with the Oracle Berkeley DB SQL APIs

    - +

    Legal Notice

    @@ -64,7 +64,7 @@

    To obtain a copy of this document's original source code, please submit a request to the Oracle Technology Network forum at: - http://forums.oracle.com/forums/forum.jspa?forumID=271 + https://forums.oracle.com/forums/forum.jspa?forumID=271

    @@ -72,7 +72,7 @@
    -

    5/11/2012

    +

    2/17/2015

    @@ -227,6 +227,11 @@ PRAGMA bdbsql_vacuum_pages +
    + + PRAGMA large_record_opt + +
    PRAGMA multiversion @@ -269,6 +274,20 @@ Encryption
    +
    +
    +
    + + Berkeley DB encryption + +
    +
    + + SQLite Encryption Extension + +
    +
    +
    Using Sequences @@ -391,6 +410,11 @@ Durability Guarantees
    +
    + + Permanent Message Handling + +
    Two-Site Replication Groups @@ -410,6 +434,21 @@ PRAGMA replication
    +
    + + PRAGMA replication_ack_policy + +
    +
    + + PRAGMA replication_ack_timeout + +
    +
    + + PRAGMA replication_get_master + +
    PRAGMA replication_initial_master @@ -420,6 +459,21 @@ PRAGMA replication_local_site
    +
    + + PRAGMA replication_num_sites + +
    +
    + + PRAGMA replication_perm_failed + +
    +
    + + PRAGMA replication_priority + +
    PRAGMA replication_remote_site @@ -430,6 +484,11 @@ PRAGMA replication_remove_site
    +
    + + PRAGMA replication_site_status + +
    PRAGMA replication_verbose_output @@ -484,7 +543,7 @@
    - Backing Up Replicated Berkeley DB SQL Databases + Backing Up Replicated Berkeley DB SQL Databases
    @@ -527,6 +586,21 @@
    +
    + + Catastrophic Recovery + +
    +
    + + Database Statistics + +
    +
    + + Verify Database Structure + +
    diff --git a/docs/bdb-sql/journaldirectory.html b/docs/bdb-sql/journaldirectory.html index 3a0e4cde..cd6d90f2 100644 --- a/docs/bdb-sql/journaldirectory.html +++ b/docs/bdb-sql/journaldirectory.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/lockhandling.html b/docs/bdb-sql/lockhandling.html index 8b3dd006..d548a7a9 100644 --- a/docs/bdb-sql/lockhandling.html +++ b/docs/bdb-sql/lockhandling.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/lockingnotes.html b/docs/bdb-sql/lockingnotes.html index c5da5a5b..3410d004 100644 --- a/docs/bdb-sql/lockingnotes.html +++ b/docs/bdb-sql/lockingnotes.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/miscdiff.html b/docs/bdb-sql/miscdiff.html index 491b9a48..dda2fb67 100644 --- a/docs/bdb-sql/miscdiff.html +++ b/docs/bdb-sql/miscdiff.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/moreinfo.html b/docs/bdb-sql/moreinfo.html index 04966f49..0f444bb8 100644 --- a/docs/bdb-sql/moreinfo.html +++ b/docs/bdb-sql/moreinfo.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -53,21 +53,21 @@
    diff --git a/docs/bdb-sql/normal-sql.html b/docs/bdb-sql/normal-sql.html index 403510b3..5d1ccfcd 100644 --- a/docs/bdb-sql/normal-sql.html +++ b/docs/bdb-sql/normal-sql.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -60,7 +60,9 @@

    SQLite datatyping is described in detail on the - Datatypes in SQLite Version 3 page. + + Datatypes in SQLite Version 3 + page.

  • @@ -74,9 +76,9 @@

    How NULLs are handled in SQLite may be different from what you are used to. See - + NULL Handling in SQLite Versus Other Database Engines - + for details.

    • @@ -84,9 +86,9 @@

    There are some features of SQL that SQLite does not support. For more information, see - + SQL Features That SQLite Does Not Implement. - +

    diff --git a/docs/bdb-sql/preface.html b/docs/bdb-sql/preface.html index 3d3f8a49..78d7626c 100644 --- a/docs/bdb-sql/preface.html +++ b/docs/bdb-sql/preface.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -64,7 +64,7 @@

    Welcome to the Berkeley DB SQL interface. This manual describes how to - configure and use the SQL interface to Berkeley DB 11g Release 2. + configure and use the SQL interface to Berkeley DB 12c Release 1. This manual also describes common administrative tasks, such as backup and restore, database dump and load, and data migration when using the BDB SQL interface. diff --git a/docs/bdb-sql/recoverysql.html b/docs/bdb-sql/recoverysql.html new file mode 100644 index 00000000..ed4d344f --- /dev/null +++ b/docs/bdb-sql/recoverysql.html @@ -0,0 +1,80 @@ + + + + + + Catastrophic Recovery + + + + + + + + +

    +
    +

    Library Version 12.1.6.1

    +
    +
    + + + + + + + + +
    Catastrophic Recovery
    Prev Chapter 5. Administrating Berkeley DB SQL Databases Next
    +
    +
    +
    +
    +
    +
    +

    Catastrophic Recovery

    +
    +
    +
    +

    + Catastrophic recovery is used when normal recovery is + unable to repair a corrupted database. + A detailed description of the recovery utility is described at + db_recover + . This + section describes how to use the utility with a SQL database. +

    +

    + The first step in running recovery is to add a DB_CONFIG + file + to the journal directory. In the file, add the following line: +

    + + add_data_dir .. + +

    + Then execute the following command in the journal directory + db_recover -c. +

    +
    +
    +
    + + + + + + + + + + + +
    Prev  + Up +  Next
    Data Migration  + Home +  Database Statistics
    +
    + + diff --git a/docs/bdb-sql/rep_usageexamples.html b/docs/bdb-sql/rep_usageexamples.html index 1894ef10..8aa95053 100644 --- a/docs/bdb-sql/rep_usageexamples.html +++ b/docs/bdb-sql/rep_usageexamples.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -113,7 +113,7 @@ dbsql univ.db

    Site 2:

    - 
     # Perform some reads on first replica.
+        
        # Perform some reads on first replica.
     select * from university where region = "Europe";
     select count(*) from country where top_100 > 0;
 
diff --git a/docs/bdb-sql/reppragma.html b/docs/bdb-sql/reppragma.html
index dac81daf..051a9a41 100644
--- a/docs/bdb-sql/reppragma.html
+++ b/docs/bdb-sql/reppragma.html
@@ -14,7 +14,7 @@
   
     
    
       
    
-        
    Library Version 11.2.5.3
    
+        
    Library Version 12.1.6.1
    @@ -43,6 +43,21 @@ PRAGMA replication +
    + + PRAGMA replication_ack_policy + +
    +
    + + PRAGMA replication_ack_timeout + +
    +
    + + PRAGMA replication_get_master + +
    PRAGMA replication_initial_master @@ -53,6 +68,21 @@ PRAGMA replication_local_site
    +
    + + PRAGMA replication_num_sites + +
    +
    + + PRAGMA replication_perm_failed + +
    +
    + + PRAGMA replication_priority + +
    PRAGMA replication_remote_site @@ -63,6 +93,11 @@ PRAGMA replication_remove_site
    +
    + + PRAGMA replication_site_status + +
    PRAGMA replication_verbose_output @@ -92,7 +127,9 @@ 
    PRAGMA replication=ON|OFF

    Enables the local environment to participate in - replication. + replication. You only need to specify this PRAGMA + once to turn on replication; all future uses of the + database will automatically enable replication.

    Before invoking this PRAGMA for a brand new @@ -127,6 +164,166 @@ PRAGMA replication=ON.

    +
    +
    +
    +
    +

    PRAGMA replication_ack_policy

    +
    +
    +
    + 
    PRAGMA replication_ack_policy=all|all_available|none|one|quorum
    +

    + Sets the replication group's acknowledgement policy. If + no policy is specified, then this PRAGMA returns the + current acknowledgement policy. This PRAGMA may be + called at any time during the life of the application. +

    +

    + Acknowledgement policies are used to describe how + permanent messages will be handled. A message is + considered to be permanent if the master site has + received enough responses (acknowledgements) from its + replicas. Once the master is satisfied that a message is + permanent, it considers the transaction that generated + the message to be complete. Therefore, the + acknowledgement policy you set affects your + application's write throughput, as well as the + durability strength of your transactions. +

    +

    + Message acknowledgements must be returned within a set + timeout period. See + PRAGMA replication_ack_timeout + for information on how to manage this timeout. + Also, + PRAGMA replication_perm_failed + provides useful diagnostic information that you can use + to fine-tune your acknowledgement policy. +

    +

    + See + Permanent Message Handling + for more information on message acknowledgements. +

    +

    + Possible permanent acknowledgement policies are: +

    +
    +
      +
    • +

      + all +

      +

      + All sites belonging to the replication group must + acknowledge the message before the generating + transaction is considered to be complete. This + provides the strongest possible durability + guarantee, but also the slowest possible write + throughput. +

      +

      + Note that if any site is shutdown or otherwise + cannot be reached due to networking errors, + this acknowledgement policy will prevent your + application from considering any transactions + durable. +

      +
      • +
    • +

      + all_available +

      +

      + All currently connected sites must acknowledge the message. +

      +
      • +
    • +

      + none +

      +

      + The master will not wait for any message + acknowledgements before completing the + transaction. This results in the fastest + possible write throughput, but also the weakest + durability guarantee. +

      +
      • +
    • +

      + one +

      +

      + At least one site must acknowledge the message + before the transaction is considered to be + complete. +

      +
      • +
    • +

      + quorum +

      +

      + The master waits until it has received + acknowledgements from the minimum number of + electable sites sufficient to ensure the record + change is durable in the event of an election. + This is the default acknowledgement policy. +

      +
      • +
    +
    +
    +
    +
    +
    +
    +

    PRAGMA replication_ack_timeout

    +
    +
    +
    + 
    PRAGMA replication_ack_timeout=<timeout in microseconds>
    +

    + Sets the replication site's acknowledgement timeout + value. If the acknowledgement policy cannot be met + within this timeout period, then the encompassing + transaction is not considered to be complete. This + PRAGMA may be called at any time during the life of the + application. The default is 1 second (1000000). +

    +

    + If no timeout is provided, then this PRAGMA returns + the replication site's current message acknowledgement + timeout value. +

    +

    + For information on specifying acknowledgement policies, + see + PRAGMA replication_ack_policy. + Also, + PRAGMA replication_perm_failed + provides useful diagnostic information that you can use + to fine-tune your acknowledgement timeouts. +

    +
    +
    +
    +
    +
    +

    PRAGMA replication_get_master

    +
    +
    +
    + 
    PRAGMA replication_get_master
    +

    + Returns a host/port pair representing the current + master. If replication has not yet started, or if the + master is currently not known (such as during an + election), NULL is returned. +

    +
    @@ -181,6 +378,84 @@ Sets the local site information for replication.

    +
    +
    +
    +
    +

    PRAGMA replication_num_sites

    +
    +
    +
    + 
    PRAGMA replication_num_sites
    +

    + Returns the number of sites in the replication group, + or 0 if replication has not yet + started. Any input provided to this PRAGMA is ignored. +

    +
    +
    +
    +
    +
    +

    PRAGMA replication_perm_failed

    +
    +
    +
    + 
    PRAGMA replication_perm_failed
    +

    + Returns the number of times that a permanent message + has failed the replication group's acknowledgement + policy since the last time this PRAGMA was called. Zero + is returned if replication has not yet started. +

    +

    + Every time a permanent message has failed + acknowledgement, a transaction was not considered + durable and the master waited the full acknowldgement + timeout period before returning from its commit. If + you are seeing a high number of permanent message + acknowledgement failures, then that might represent a + significant reduction in your application's + write-throughput. +

    +

    + To fix the problem, begin by examining your replicas to + make sure they are operating correctly, as well as your + network to make sure its performance is what you expect. + If all looks well, then you should either reduce your + acknowledgement policy (and accept a lessened + durability guarantee) or increase your acknowledgement + timeout period (which might reduce your write-throughput). +

    +

    + To manage your acknowledgement policies, see + PRAGMA replication_ack_policy. + To manage your acknowledgement timeout policy, see + PRAGMA replication_ack_timeout. +

    +
    +
    +
    +
    +
    +

    PRAGMA replication_priority

    +
    +
    +
    + 
    PRAGMA replication_priority=<non-0 positive integer>
    +

    + Sets the site's election priority. When holding + elections, if more than one site has the most + up-to-date copy of the data then the site with the + highest priority will become master. This PRAGMA may + be called at any time during the life of the + application. The default is 100. +

    +

    + If no priority is provided, then this PRAGMA returns + the site's current priority. +

    +
    @@ -237,6 +512,26 @@ (such as when, for example, elections are held).

    +
    +
    +
    +
    +

    PRAGMA replication_site_status

    +
    +
    +
    + 
    PRAGMA replication_site_status
    +

    + Returns whether the local site is the + MASTER, CLIENT, + or UNKNOWN. +

    +

    + UNKNOWN is returned if replication + has not yet started. CLIENT is another term for + replica. +

    +
    diff --git a/docs/bdb-sql/repstatistics.html b/docs/bdb-sql/repstatistics.html index a94c5d5c..66204c43 100644 --- a/docs/bdb-sql/repstatistics.html +++ b/docs/bdb-sql/repstatistics.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/selectpage_size.html b/docs/bdb-sql/selectpage_size.html index 24534435..ad79fde3 100644 --- a/docs/bdb-sql/selectpage_size.html +++ b/docs/bdb-sql/selectpage_size.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/sequencesupport.html b/docs/bdb-sql/sequencesupport.html index 71c251bd..80a27026 100644 --- a/docs/bdb-sql/sequencesupport.html +++ b/docs/bdb-sql/sequencesupport.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -130,7 +130,12 @@

    The starting value for the sequence. If this - parameter is not provided then + parameter is not provided it is set to + minvalue if + an incrementing sequence is used, and + maxvalue if a decrementing + sequence is used. If neither + of those parameters are set then 0 is used.

    diff --git a/docs/bdb-sql/sql_encryption.html b/docs/bdb-sql/sql_encryption.html index c575776a..4f301967 100644 --- a/docs/bdb-sql/sql_encryption.html +++ b/docs/bdb-sql/sql_encryption.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -36,25 +36,74 @@ -

    - The Berkeley DB SQL interface supports the SQLite Encryption Extension (SEE) to ensure security of - your data. The supported encryption algorithm is AES-128 in CBC mode. - For more information on the concepts relating to BDB encryption, see the - - Berkeley DB Programmer's Reference Guide. +

    +
    +
    + + Berkeley DB encryption + +
    +
    + + SQLite Encryption Extension - -

    +
    +
    +

    - To learn how to use the SQLite Encryption Extension (SEE), see the - official SQLite - Documentation Page. -

    -
    -

    Note

    -

    - The Berkeley DB SQL interface does not support the sqlite3_rekey method. + When encryption is enabled, the Berkeley DB SQL API uses + native Berkeley DB encryption to assure the security of + your data. As usual, the Berkeley DB SQL API is almost + identical to the SQLite API, so you can use the syntax of + the SQLite Encryption Extension to interact with your + encrypted data.

    +
    +
    +
    +
    +

    Berkeley DB encryption

    +
    +
    +
    +

    + Berkeley DB supports encryption using the Rijndael/AES + algorithm. It is configured to use a 128-bit key. Berkeley + DB uses a 16-byte initialization vector generated using the + Mersenne Twister. All encrypted information is additionally + checksummed using the SHA1 Secure Hash Algorithm, using a + 160-bit message digest. For more information on BDB + encryption, see the + + + Berkeley DB Programmer's Reference Guide. + + + +

    +
    +
    +
    +
    +
    +

    SQLite Encryption Extension

    +
    +
    +
    +

    + To learn how to use the SQLite Encryption Extension (SEE), + see the official + + SQLite Documentation Page. + +

    +
    +

    Note

    +

    + The Berkeley DB SQL interface does not support the + sqlite3_rekey method. +

    +
    diff --git a/docs/bdb-sql/sqlrep.html b/docs/bdb-sql/sqlrep.html index 56822bdb..cbbad427 100644 --- a/docs/bdb-sql/sqlrep.html +++ b/docs/bdb-sql/sqlrep.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -63,6 +63,11 @@ Durability Guarantees +
    + + Permanent Message Handling + +
    Two-Site Replication Groups @@ -82,6 +87,21 @@ PRAGMA replication
    +
    + + PRAGMA replication_ack_policy + +
    +
    + + PRAGMA replication_ack_timeout + +
    +
    + + PRAGMA replication_get_master + +
    PRAGMA replication_initial_master @@ -92,6 +112,21 @@ PRAGMA replication_local_site
    +
    + + PRAGMA replication_num_sites + +
    +
    + + PRAGMA replication_perm_failed + +
    +
    + + PRAGMA replication_priority + +
    PRAGMA replication_remote_site @@ -102,6 +137,11 @@ PRAGMA replication_remove_site
    +
    + + PRAGMA replication_site_status + +
    PRAGMA replication_verbose_output @@ -168,13 +208,6 @@ -
    -

    Note

    -

    - You cannot access a BDB SQL database using multiple - processes if you enable replication for that database. -

    -
    @@ -200,6 +233,11 @@ Durability Guarantees
    +
    + + Permanent Message Handling + +
    Two-Site Replication Groups @@ -335,7 +373,7 @@

    For replicated BDB SQL applications, the durability - guarantee is extended because data modifications are + guarantee is enhanced because data modifications are also replicated to those environments that are participating in the replication group. This ensures higher data durability than non-replicated applications @@ -343,6 +381,71 @@ reside on separate physical machines.

    +
    +
    +
    +
    +

    Permanent Message Handling

    +
    +
    +
    +

    + Permanent messages are created by replication masters + as a part of a transactional commit operation. When a + replica receives a message that is marked as permanent, + it knows that the message affects transactional + integrity. Receipt of a permanent message means that + the replica must send a message acknowledgment back to + the master server because the master + might be waiting for the + acknowledgment before it considers the transaction + commit to be complete. +

    +

    + Whether the master is actually waiting for message + acknowledgement depends on the acknowledgement policy + in effect for the replication group. Policies can range + from NONE (the master will not wait + for any acknowledgements before completing the + transaction) to ALL (the master will + wait for acknowledgements from all replicas before + completing the transaction). +

    +

    + Acknowledgements are only sent back to the master once + the replica has completed applying the message to its + local environment. Therefore, the stronger your + acknowledgement policy, the stronger you durability + guarantee. On the other hand, the stronger your + acknowledgement policy, the slower your application's + write throughput will be. +

    +

    + In addition to setting an acknowledgement policy, you + can also set an acknowledgment timeout. This time limit + is set in microseconds and it represents the length of + time the master will wait to satisfy its + acknowledgement policy for each transaction commit. If + this timeout value is not met, the transaction is still + committed locally to the master, but is not yet + considered durable across the replication group. Your + code should take whatever actions are appropriate for + that transaction. If enough other sites are available + to meet the acknowledgement policy, the transaction + will become durable after more time has passed. +

    +

    + You set acknowledgement policies and acknowledgement timeouts + using PRAGMAs. See + PRAGMA replication_ack_policy + and + PRAGMA replication_ack_timeout. + In addition, you can examine how frequently your + transactions do not achieve durability within the + acknowledgement timeout by using + PRAGMA replication_perm_failed. +

    +
    diff --git a/docs/bdb-sql/statsql.html b/docs/bdb-sql/statsql.html new file mode 100644 index 00000000..b92a2a32 --- /dev/null +++ b/docs/bdb-sql/statsql.html @@ -0,0 +1,80 @@ + + + + + + Database Statistics + + + + + + + + +
    +
    +

    Library Version 12.1.6.1

    +
    +
    + + + + + + + + +
    Database Statistics
    Prev Chapter 5. Administrating Berkeley DB SQL Databases Next
    +
    +
    +

    Database Statistics

    + The statistics utility can be used to print out information on + tables in a database. A detailed description of the statistics + utility is described at db_stat + . This + section describes how to use the utility with a SQL database. +

    + The first step in getting statistics on a table is to find the + internal name for the table. The internal table name is + table#####, where the number is the rootpage + number, which can be retrieved using the following SQL statement: +

    + SELECT rootpage FROM sqlite_master WHERE name='[table name]'; + + For example, if the root page is 10, the internal table name + will be table00010. +

    + In order to run the db_stat utility, + first add a DB_CONFIG + file to the journal directory. + In the file, add the following line: +

    + add_data_dir .. +

    + Then execute the following command in the directory + with the database: + db_stat -d [file name] -h [journal directory] -s [internal table name]. + That command will print out information on the table. +

    +
    +
    + + + + + + + + + + + +
    Prev  + Up +  Next
    Catastrophic Recovery  + Home +  Verify Database Structure
    +
    + + diff --git a/docs/bdb-sql/sync.html b/docs/bdb-sql/sync.html index 7bbd4d85..48e59648 100644 --- a/docs/bdb-sql/sync.html +++ b/docs/bdb-sql/sync.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    @@ -104,8 +104,8 @@ system, you can use the Oracle SQLite Mobile Client in exactly the same way as you would if you were using standard SQLite libraries and databases with it. See the - - Oracle Database Lite + + Oracle Database Mobile Server documentation. documentation for information on using SQLite Mobile Client.

    @@ -147,8 +147,8 @@ you can use the Oracle SQLite Mobile Client in exactly the same way as you would if you were using standard SQLite libraries and databases with it. See the - - Oracle Database Lite documentation for + + Oracle Database Mobile Server documentation for information on using SQLite Mobile Client.

    @@ -180,8 +180,8 @@ you can use the Oracle SQLite Mobile Client in exactly the same way as you would if you were using standard SQLite libraries and databases with it. See the - - Oracle Database Lite documentation for + + Oracle Database Mobile Server documentation for information on using SQLite Mobile Client.

    diff --git a/docs/bdb-sql/unsupportedpragmas.html b/docs/bdb-sql/unsupportedpragmas.html index afb2c513..b892fc60 100644 --- a/docs/bdb-sql/unsupportedpragmas.html +++ b/docs/bdb-sql/unsupportedpragmas.html @@ -14,7 +14,7 @@
    -

    Library Version 11.2.5.3

    +

    Library Version 12.1.6.1

    diff --git a/docs/bdb-sql/verifysql.html b/docs/bdb-sql/verifysql.html new file mode 100644 index 00000000..3daf91b4 --- /dev/null +++ b/docs/bdb-sql/verifysql.html @@ -0,0 +1,82 @@ + + + + + + Verify Database Structure + + + + + + + + +
    +
    +

    Library Version 12.1.6.1

    +
    +
    + + + + + + + + +
    Verify Database Structure
    Prev Chapter 5. Administrating Berkeley DB SQL Databases Next
    +
    +
    +
    +
    +
    +
    +

    Verify Database Structure

    +
    +
    +
    +

    + Verification is used to confirm that a database structure is + correct, and has not been corrupted by a crash or other failure. + A detailed description of the verify utility is described at + db_verify + . This + section describes how to use the utility with a SQL database. +

    +

    + The first step in running verify is to add a DB_CONFIG + file + to the journal directory. In the file, add the following line: +

    + + add_data_dir .. + +

    + Then execute the following command in the database directory + db_verify -h [journal directory] [database file]. + The command will either print out a message reporting success, + or will list any error found in the database. +

    +
    +
    +
    + + + + + + + + + + + +
    Prev  + Up +  Next
    Database Statistics  + Home +  Appendix A. Using the BFILE Extension
    +
    + + -- cgit v1.2.1