Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

GOCDB/Regional Module Technical Documentation

From EGIWiki
< GOCDB
Revision as of 17:00, 21 December 2011 by Davidm (talk | contribs)
Jump to navigation Jump to search
1- Create Custom tablespaces for GOCDB (Optional)

GOCDB-4 database contains 3 distinct groups of tables: Metadata or core data, GOCDB data, and local data. Although this is not mandatory, we recommend that 3 different tablespaces are created to store these different tables.

  • If you prefer, you can skip this step and rely on the default 'USERS' tablespace.
Sugested Tablespace Name Min Recommended Size Purpose
TS_GRIDCORE 50m Will store the core tables containing schema metadata
TS_GOCDBDATA  50m  Will store GOCDB data tables (common structure to all GOCDB modules)
TS_LOCALDATA  50m  Will store your local tables if you have some local information to store

Note: You must configure gocdb to use these custom tablespace names in the 'local_info.xml' config file as described below.

To create these tablespaces, run the following script (as SYSTEM user):

 CREATE TABLESPACE TS_GRIDCORE; 
 CREATE TABLESPACE TS_GOCDBDATA; 
 CREATE TABLESPACE TS_LOCALDATA;

The created tablespaces will then be:

  • Permanent, locally managed and with system allocated extent size.
  • The corresponding datafiles will be created in the location provided in the DB_CREATE_FILE_DEST parameter and with size 100 MB.
  • The datafiles will be autoextensible with no maximum size.
  • Names of datafiles will be similar to "ora_applicat_zxyykpt000.dbf"

You can customise tablespace creation, there are many possible options (see Oracle docs for further info). For example:

 CREATE TABLESPACE <tblspc_name> DATAFILE 'C:\ORA\<fileNameForTableSpace>.dbf' SIZE 50M AUTOEXTEND ON MAXSIZE 100M;

If you created these custom tablespaces, you will need to grant your GOCDB user unlimited access (you do not need to do this if you rely on the default 'USERS' tablespace). Use the following script:

  ALTER USER GOCDB QUOTA UNLIMITED ON TS_GRIDCORE;
  ALTER USER GOCDB QUOTA UNLIMITED ON TS_GOCDBDATA;
  ALTER USER GOCDB QUOTA UNLIMITED ON TS_LOCALDATA;