WARNING: This web is not used anymore. Please use PDBService.CheckOracleIAS instead!
 

Procedure

1) Check if the endpoints are reachable (validate service) 2) Check if the container is running

If there are problems, the best is to move to another node:

1) Warn users about the problem 2) Check if a spare machine is ready to production (validate endpoint other machine) 3) Perform the DNS switch 4) Notice users the service is back

Validate service

http://cern.ch/phydb/documents/old/Validate_service_.php

DNS Switch

http://cern.ch/phydb/documents/old/Validate_service_.php

Dataguard for RLS

http://cern.ch/phydb/documents/old/Data_Guard.html

Reconfigure datasource using a script

This document describes how to change the database backend that a deployed application uses using an script.

Index

  1. Getting the script files.
  2. Using the script

1. Obtaining and preparing the script files

The scripts are in CERN's CVS system in lcg-orat1 project under the Applications/RLS/as-deployment/ directory.

  1. Logon to the target machine as the oracle user
  2. Copy the following two scripts to a working directory on the target machine * change-data-sources * Dcmctl.pm
  3. Set the scripts' execution mode to 755

2. Execute the script

The datasource configuration for a given VO can be checked manually by looking at the datasources configuration file: $ORACLE_HOME/j2ee/test/config/data-sources.xml

The automatic script will change the datasources by modifying the datasources.xml configuration file. The database host and database SID will be replaced with the new ones for the given VO. The script then will restart the container.

The script usage is as follows:

usage: ./change-data-source --sid=SID --db_host=DBHOST --vo=VO [-v]

Options: vo name of the virtual organization (atlas, cms, ...) db_host hostname of the database server of LRC and RMC sid SID of the database of LRC and RMC v verbose mode

Example: ./change-data-source --sid=certrls4 --db_host=lxshare333d --vo=atlas

Checking the update

You can check that the update was successful by looking at the datasource now configured in the datasources.xml file


Deploy old end points of CMS

CMS needs for temporary timescale that old endpoints (before the last convention was established) are also deployed, so they can get the RLS services from hard-coded endpoints.

The fastest way is to deploy via command line AFTER normally deploy the present RLS services endpoints.

1. Get the files 2. Deploy the applications 3. Change the URL binding 4. Redeploy the applications 5. (Re)Start the container

1. Get the files

The necessary files are the .ear files for the corresponded version, which can be found in: /afs/cern.ch/project/grid/wp2/oracle-deployment/edg-local-replica-catalog//

/afs/cern.ch/project/grid/wp2/oracle-deployment/edg-replica-metadata-catalog//

For version 2.0.2 you can just run these commands:

scp @lxplus:/afs/cern.ch/project/grid/wp2/oracle-deployment/edg-local-replica-catalog/2.0.2/*.war .

scp @lxplus:/afs/cern.ch/project/grid/wp2/oracle-deployment/edg-replica-metadata-catalog/2.0.2/*.war . 2. Deploy the applications

To deploy the applications run the following commands:

dcmctl deployApplication -file ./edg-local-replica-catalog-2.0.2.war -a edg-local-replica-catalog -co cms -rc /edg-replica-location -d -v

dcmctl deployApplication -file ./edg-replica-metadata-catalog-2.0.2.war -a edg-replica-metadata-catalog -co cms -rc /edg-replica-metadata-catalog -d -v 3. To start or restart the container now just do:

to start:

dcmctl start -co cms

to restart:

dcmctl restart -co cms

to start the http server:

dcmctl start -ct ohs 4. Validation

To validate and check if everything went well, go to the URLs and ping the services: http://.cern.ch:7777/edg-replica-location/

http://.cern.ch:7777/edg-replica-metadata-catalog/

Retrieve backup data from TSM for RLS

This page describes the necessary steps to retrieve files required for a restore and recovery of the RLS1 database from TSM tape storage. At the moment, archived files must be first retrieved from TSM tape storage.

These steps should be executed as 'orapdm' on the PDB backup server, pdb-backup1, which currently is an alias to lxshare077d. Create temporary directories for the retrieval:

Create a temporary directory to stagein files from TSM to pdb-backup1 if one does not already exist: > sudo mkdir /data/pdb-backup1/restore/rls1 > sudo mkdir /data/pdb-backup1/restore/rls1/archivelogs

Copy the archive logs to the retrieval directory:

> cd /data/pdb-backup1/rls1/archivelogs > sudo -s > tar cvf - * | (cd /backup/restore/rls1/archivelogs/; tar xvf -) >exit

Retrieve the data:

Startup the Tivoli Storage Manager and locate the file space name that you need to retrieve, i.e. /data/pdb-backup1: sudo /usr/bin/dsmc tsm> query filespace tsm> query archive "/data/pdb-backup1/rls1/*" -subdir=yes

Retrieve the data. The time taken to mount the required media may be long tsm> retrieve "/data/pdb-backup1/rls1/*" /data/pdbbackup1/restore/rls1/ -subdir=yes

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2005-12-07 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    PSSGroup All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback