Differences between revisions 6 and 80 (spanning 74 versions)
Revision 6 as of 2007-07-19 19:37:32
Size: 2976
Editor: biodhcp-185-86
Comment: addition of restore code
Revision 80 as of 2020-10-08 19:15:03
Size: 3876
Editor: NikiLearn
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page will be used to store codes, protocols, and procedures for use by the Data Managers. This page is used to store codes, protocols, and procedures for use by the Data Managers.
Line 3: Line 3:
== Adding a User to Babase == === Babase Technical Information ===
These links are primarly of interest to the Babase support staff.
Line 5: Line 6:
 * Users can be added to babase, as well as a schema created, and permissions set, by completing the following steps using a SSH client.
{{{
PGPASSWORD='*********' babase-user-add username babase_readers}}}
 * [[RankerProgram|Ranker Program]] -- The ranker program is used to develop and input Baboon social ranks.
 * [[BabaseVPN|The Babase VPN]] -- The Babase Virtual Private Network is available to those people who have a Unix Login on Papio. It is primarly used to run the ranker program.
 * [[PsionFormat|The Psion Data Format]] -- The Psions are handheld data collection devices. They output their data in a custom format.
 * [[UserManagement|User Management]]
 * [[DukeOITTools|Duke OIT Tools]]
 * [[ABRPGenomicsTestSite|Accessing the ABRP-Genomics test site]] -- Testing changes to the ABRP Genomics site
 * [[BabaseChangelog|Babase 2.0 Changelog]]
Line 9: Line 14:
 * The ********* here would be the babase_admin password
 * The Username selected will become not only the babase username and temporary password but also the schema name.
 * It is very important that the user immediately change their password using PPA's password change option.
==== Programs ====
 * [[ProgramLinks|Generic Programs]]
 * [[ProgramLinks|Babase's Bespoke Programs]]
Line 13: Line 18:
== Backing up the Database or Schemas == ==== Protocols ====
 * [[attachment:Duke Data Management Protocol.pdf|Duke Data Management Protocol.pdf]] (last updated 2018-07-06)-- Protocol for maintenance of interaction data, focal sampling data, GPS/SWERB data, male ranks, dartings, and predation and human disturbance data
 * [[attachment:Princeton Data Management Protocol_Sep 2020.pdf|Princeton Data Management Protocol_Sep 2020.pdf]] -- Princeton Protocol for Data Maintenance and the Demography/Reproduction Update, last updated Sep 2020.
 * [[attachment:Data Storage.pdf]] -- See attachment for information on how data that come from the field are stored
 * [[attachment:Electronic Data Handling.pdf]] --See attachment for information on how electronic data are processed
 * [[attachment:Paper Data Handling.pdf]] --See attachment for information on how paper data are processed
 * [[GeneticTableForms|Forms for adding new data to the genetics tables]]
Line 15: Line 26:
 * When Backing up the DB, the 'help' directory can offer some direction
{{{
[YOU@papio ~]$ pg_dump --help}}}
==== Wiki Administration ====
 * BabaseWikiAdminGroup
 * BabaseWikiEditorsGroup
 * DatasetStatus
 * DatasetStatusTable
 * EmailManagement
Line 19: Line 33:
== Restoring the Database or Schemas == ==== Misc Links ====
 * [[TabbyTest|Tabby's test page]]
 * SandboxPage -- Sandbox page for sharing code remotely
 * RankerDiffs
 * TheJeanneAndSusanAttachmentPage
 * [[WritingAComplexQuery]]
 * ExtendedQuizQuestions
 * [[attachment:Historic Agonism Summary.xls]]
Line 21: Line 42:
 * If you are going to want to restore tables within the schema:
{{{
[YOU@papio ~]$ pg_dump --file YOURBACKUP.sql --host=localhost --format=c schema=fecal --user lmaryott babase}}}
 
 * after the backup file is created, it is useful to be able to look at the file to ensure you have the correct search path (the tables are getting put in the correct place ie. your schema) one way to do this is to view what the command is doing by having the output displayed in your unix window
{{{
[YOU@papio ~]$ pg_restore --host=localhost --file=/dev/stdout --user YOU YOURBACKUP.sql}}}
 * you can also save this information into a file, rather than having it just display in your unix window
{{{
[YOU@papio ~]$ pg_restore --host=localhost --file=YOURRESTORE.sql --user YOU YOURBACKUP.sql}}}
 * you can then just read the output within the window as well as having saved it for restore use
=== Copying the Babase Schema ===
The babase-copy-babase-schema Unix program copies the entire babase schema, including data, table definitions, validation, and everything else, from one database to another. All existing data, table definitions, validation, etc is deleted from the babase schema in the target database. You must be logged in to papio and at the Unix prompt to run the program.

The following example copies the babase schema from the babase database to the babase_test database. The first database ({{{babase}}}) is the database to copy from, the second ({{{babase_test}}}) the database to copy into.
Line 34: Line 48:
[YOU@papio ~]$ less YOURRESTORE.SQL}}} PGPASSWORD='*********' babase-copy-babase-schema YOURADMINNAME babase babase_test
}}}
 * The ********* here would be the password of YOURADMINNAME
Line 36: Line 52:
 * the output on your screen will then resemble the text below:
{{{CREATE SCHEMA schemaname1;
The next example copies the babase scheme from the babase_test database to the babase_database. The program will not copy into the babase database unless the {{{-f}}} (force) flag is given.
Line 39: Line 54:
{{{
PGPASSWORD='*********' babase-copy-babase-schema -f YOURADMINNAME babase_test babase
}}}
 * When Backing up the DB, the 'help' directory can offer some direction
Line 40: Line 59:
SET search_path = schemaname1, pg_catalog; {{{
[YOU@papio ~]$ pg_dump --help
}}}
=== Killing a Process in PPA ===
After you have logged into the database as the administrator, select the babase database.
Line 42: Line 65:
SET default_tablespace = ''; There is a tab along the top of the browser window with a button for Processes. Click this button.
Line 44: Line 67:
SET default_with_oids = false;}}}

 * If you desire for the data to be restored to a different location, you can use the emacs application to edit the text of YOURRESTORE.sql.
{{{
[YOU@papio ~]$ emacs -nw YOURRESTORE.sql}}}
 * IT IS IMPORTANT YOU NOT USE EMACS WITHOUT KNOWLEDGE OF HOW TO EXIT OUT OF IT!!!!!!!
 * After changing the first search path in the file, it should look like the following
{{{CREATE SCHEMA schemaname1;


SET search_path = schemaname2, pg_catalog;

SET default_tablespace = '';

SET default_with_oids = false;}}}
 * the PSQL terminal should then be used for the restore, at which point the tables from your schema will be created in the schema specified in the search path
{{{
[YOU@papio ~]$ psql --dbname=babase --user=YOU --host=localhost < YOURRESTORE.sql}}}
 * If you enter the previous command without the '< YOURRESTORE.sql', you will be prompted with "babase>" This is just another front end for babase, and any queries could also be performed here, just for future reference.
You may have to click cancel on the process you are killing a couple of times. It will tell you that the function has failed, its just kidding!

This page is used to store codes, protocols, and procedures for use by the Data Managers.

Babase Technical Information

These links are primarly of interest to the Babase support staff.

Programs

Protocols

Wiki Administration

Copying the Babase Schema

The babase-copy-babase-schema Unix program copies the entire babase schema, including data, table definitions, validation, and everything else, from one database to another. All existing data, table definitions, validation, etc is deleted from the babase schema in the target database. You must be logged in to papio and at the Unix prompt to run the program.

The following example copies the babase schema from the babase database to the babase_test database. The first database (babase) is the database to copy from, the second (babase_test) the database to copy into.

PGPASSWORD='*********' babase-copy-babase-schema YOURADMINNAME babase babase_test
  • The ********* here would be the password of YOURADMINNAME

The next example copies the babase scheme from the babase_test database to the babase_database. The program will not copy into the babase database unless the -f (force) flag is given.

PGPASSWORD='*********' babase-copy-babase-schema -f YOURADMINNAME babase_test babase
  • When Backing up the DB, the 'help' directory can offer some direction

[YOU@papio ~]$ pg_dump --help

Killing a Process in PPA

After you have logged into the database as the administrator, select the babase database.

There is a tab along the top of the browser window with a button for Processes. Click this button.

You may have to click cancel on the process you are killing a couple of times. It will tell you that the function has failed, its just kidding!

DataManagement (last edited 2024-06-20 14:58:32 by JakeGordon)

Wiki content based upon work supported by the National Science Foundation under Grant Nos. 0323553 and 0323596. Any opinions, findings, conclusions or recommendations expressed in this material are those of the wiki contributor(s) and do not necessarily reflect the views of the National Science Foundation.