Search results

Jump to: navigation, search
  • ... Documents ("KeyDocs"). A list of these KeyDocs is maintained in the MySQL database, along with the [[:Category:GridPP_Operations|core tasks area name]]. Key D ...ese templates and the dates are monitored at the level of the Wiki's MySQL database to dynamically produce a table of current document status on the fly. Remin
    3 KB (470 words) - 10:02, 19 September 2017
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    3 KB (404 words) - 15:14, 12 September 2014
  • This may be carried out via the Grid Operations Centre Database, [https://goc.egi.eu/ GOCDB]
    6 KB (886 words) - 14:08, 17 August 2023
  • ...vers run a local MySQL database. Each slave has a local copy of the master database which is kept up-to-date * make a final backup of the database, the easiest way is to run the backup script that creates backups for all V
    9 KB (1,391 words) - 06:52, 12 June 2019
  • * On Tuesday 28th April the Oracle database behind the LFC srevice was upgraded to version 11.2.0.4. ...ular Oracle patches were applied the database hosting the Atlas Conditions database (behind Frontier).
    16 KB (1,794 words) - 12:58, 6 May 2015
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. In the meantime we will carry out the (separate) update of t
    40 KB (4,974 words) - 12:18, 11 April 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,356 words) - 09:59, 16 March 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    11 KB (1,098 words) - 09:42, 17 February 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,411 words) - 08:55, 10 December 2015
  • * On Tuesday morning (24th June) there was a crash of the database system for the Atlas SRM which failed over to another node (and was subsequ ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,342 words) - 16:20, 25 June 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,357 words) - 12:47, 9 May 2014
  • ...id=106876 GGUS 106876]. Currently reinstalling APEL node, after backing up database. (14/07: Last updated 24/07). ...]. Cross-contamination of information due to the GEN-CASTOR SRMs sharing a database, and some VOs sharing service classes. In progress. (04/07: Last update 24/
    184 KB (30,332 words) - 17:18, 16 December 2014
  • ...OCDB on 5th March for which an incident review has taken place. An initial database disk failure and no automated DNS switch from goc.egi.eu to goc.dl.ac.uk wa
    42 KB (5,176 words) - 11:12, 17 March 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    46 KB (5,930 words) - 18:40, 28 April 2014
  • === Database administration === === Log files and database ===
    5 KB (709 words) - 16:59, 3 January 2019
  • ** Apply latest Oracle patches (PSU) to the production database systems (Castor, LFC). ** A new database (Oracle RAC) is being set-up that will host the Atlas3D database and be updated from CERN via a new method Oracle GoldenGate).
    13 KB (1,367 words) - 13:30, 10 September 2014
  • == MySQL database ==
    4 KB (586 words) - 14:28, 23 December 2016
  • * (Ongoing at time of meeting). The Castor standby Oracle database system is being moved to the Atlas building. This is expected to take most ** Week 26-28 May: Install software on Database Systems (some 'At Risks')
    13 KB (1,442 words) - 11:25, 20 May 2015
  • ** Switch LFC/FTS/3D to new Database Infrastructure. ...s. The appear as "User Timeout" problem as yesterday - bad request in the database.
    14 KB (1,553 words) - 11:36, 19 March 2014
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,364 words) - 12:54, 20 January 2016
  • ... to version 2.1.14-15 ahead of migrating to the next version of the Oracle database.
    46 KB (5,846 words) - 07:57, 9 March 2015
  • The raw data was already backed up to a second RAID system. For the database I followed Alessandra Forti's notes at - Dump the old database with
    40 KB (6,398 words) - 09:45, 8 November 2017
  • ...OCDB on 5th March for which an incident review has taken place. An initial database disk failure and no automated DNS switch from goc.egi.eu to goc.dl.ac.uk wa ...Castor instance at the end of last week and the start of this. The Castor /Database teams have some ideas for the cause of this which looks to be load related.
    48 KB (6,293 words) - 07:35, 31 March 2014
  • ...OCDB on 5th March for which an incident review has taken place. An initial database disk failure and no automated DNS switch from goc.egi.eu to goc.dl.ac.uk wa ...Castor instance at the end of last week and the start of this. The Castor /Database teams have some ideas for the cause of this which looks to be load related.
    48 KB (6,293 words) - 07:36, 31 March 2014
  • ...y evening on Tuesday 25th March. The failover triggered a call-out and the database was put back onto its allocated node. The cause is a bug that has been repo ** Switch LFC/FTS/3D to new Database Infrastructure.
    16 KB (1,769 words) - 14:16, 2 April 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,469 words) - 10:34, 16 April 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    14 KB (1,599 words) - 11:33, 14 April 2014
  • ...e NN_FILE_STAGERTIME constraint has been removed for the Facilities CASTOR database, completing the 2.1.14 upgrade. This upgrade was thought to be transparent,
    1 KB (221 words) - 10:09, 15 April 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    45 KB (5,796 words) - 22:44, 21 April 2014
  • ...e name will be manually associated with their email address in the KeyDocs database so reminder emails can be sent correctly. * Once the KeyDocs database has been updated you should get a reply from Andrew and your page will be l
    7 KB (1,195 words) - 09:15, 19 September 2017
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,411 words) - 10:57, 23 April 2014
  • ...reviously been applied to the GEN instance was applied to the Atlas stager database and the problem resolved on the Monday afternoon. ...ouble-slash (//) with a single-slash in a filename applied to the Atas SRM database on Monday 7th December and the LHCb & CMS the following day.
    14 KB (1,492 words) - 13:08, 10 December 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    14 KB (1,557 words) - 13:24, 30 April 2014
  • ...er nodes, configured with automount support for Atlas,the Atlas conditions database, CMS and LHCb. We have two squids dedicated to cvmfs.
    4 KB (560 words) - 12:39, 17 July 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    41 KB (5,106 words) - 19:52, 5 May 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    37 KB (4,615 words) - 08:50, 12 May 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,393 words) - 10:46, 14 May 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    46 KB (6,091 words) - 11:47, 19 May 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    14 KB (1,427 words) - 13:22, 21 May 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    14 KB (1,452 words) - 12:18, 29 May 2014
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    41 KB (5,148 words) - 09:38, 2 June 2014
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,425 words) - 11:34, 2 December 2015
  • * The APEL accounting system has been undergoing database maintenance to improve performance and reliability. Networking problems at
    41 KB (5,148 words) - 07:10, 9 June 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    15 KB (1,592 words) - 12:26, 11 June 2014
  • ...t was put into a downtime and drained out over the weekend after which its database was reset. It was returned to service on Monday (16th Jun). ** Switch LFC/FTS/3D to new Database Infrastructure.
    12 KB (1,236 words) - 13:13, 18 June 2014
  • ...tions regarding required outage for the Atlas intervention relating to the database upgrade script step - being investigated.
    3 KB (412 words) - 13:13, 13 June 2014
  • ...tions regarding required outage for the Atlas intervention relating to the database upgrade script step and - being investigated.
    3 KB (423 words) - 12:45, 20 June 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    35 KB (4,220 words) - 09:11, 30 June 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    12 KB (1,212 words) - 10:15, 2 July 2014
  • ...instance on Thursday and Friday of last week (3/4 July). It was fixed by a database edit. ** Switch LFC/FTS/3D to new Database Infrastructure.
    11 KB (1,140 words) - 13:17, 9 July 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    43 KB (5,584 words) - 12:52, 7 July 2014
  • ...ce dark data search ceased. A new VM configured to run against the standby database will be created as a front-end for such queries. Chris will be leading this
    2 KB (308 words) - 13:48, 14 July 2014
  • The '''BDII''' (Berkeley Database Information Index) is a Perl / BDB 'glue' used to manage LDAP updates.
    2 KB (315 words) - 15:07, 22 November 2016
  • ...d spoke network architecture Gridmon supplies a centralised web server and database hosted at a core site and single system clients at remote sites. The core s ...client.The output from these tests are stored centrally within the primary database and web server environment. These are then accessed via a standard HTTP env
    7 KB (1,074 words) - 08:54, 18 September 2018
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,422 words) - 13:41, 16 July 2014
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies were found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,241 words) - 14:07, 25 February 2015
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    39 KB (4,936 words) - 09:03, 21 July 2014
  • * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (318 words) - 09:07, 21 July 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    39 KB (4,833 words) - 10:09, 28 July 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,382 words) - 13:24, 23 July 2014
  • # Consider optimal configuration of the MySQL database backend. As the database backend needs to be written to for every transaction that DPM performs, opt
    13 KB (2,180 words) - 16:50, 3 January 2019
  • * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (262 words) - 15:46, 25 July 2014
  • ** Switch LFC/FTS/3D to new Database Infrastructure.
    13 KB (1,402 words) - 13:04, 30 July 2014
  • * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (279 words) - 16:48, 1 August 2014
  • ...id=106876 GGUS 106876]. Currently reinstalling APEL node, after backing up database. (14/07: Last updated 24/07). ...]. Cross-contamination of information due to the GEN-CASTOR SRMs sharing a database, and some VOs sharing service classes. In progress. (04/07: Last update 24/
    42 KB (5,191 words) - 14:37, 2 August 2014
  • * Discrepancies were found in some of the Castor database tables and columns. The Castor team are considering options with regard to ** Switch LFC/FTS/3D to new Database Infrastructure.
    12 KB (1,257 words) - 12:25, 6 August 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (300 words) - 11:01, 15 August 2014
  • * Discrepancies were found in some of the Castor database tables and columns. The Castor team are considering options with regard to ** Switch LFC/FTS/3D to new Database Infrastructure.
    11 KB (1,152 words) - 10:26, 13 August 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (313 words) - 10:40, 15 August 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    41 KB (5,255 words) - 08:52, 18 August 2014
  • * The database fix for active draining has been rolled out to all Tier 1 (not facilities) * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (312 words) - 10:55, 22 August 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    42 KB (5,304 words) - 10:39, 25 August 2014
  • * Oracle patches were applied to the 'somnus' database behind the LFC on Thursday (30th Oct). ** A new database (Oracle RAC) has been set-up to host the Atlas3D database. This is updated from CERN via Oracle GoldenGate.
    12 KB (1,238 words) - 08:50, 11 November 2014
  • ...as an (Atlas) Oracle database crash due to a known (and reported) bug. The database failed over to another node in the Oracle RAC. There were some restarts of * Discrepancies were found in some of the Castor database tables and columns. The Castor team are considering options with regard to
    14 KB (1,421 words) - 13:42, 27 August 2014
  • ...ributions/2359189/attachments/1367049/2071368/SiteLayoutDB.pdf Site Layout Database], showing how ARC/Condor cluster is made up. All the nodes currently run SL
    121 KB (17,569 words) - 08:26, 28 November 2019
  • ...ing a small number of disk servers without incident following rollout of a database fix last week (to all Tier 1 not facilities) * Duplicate files in the CMS SRM database - contacted CMS representatives and clearing up as they occur.
    2 KB (338 words) - 15:06, 29 August 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    42 KB (5,358 words) - 10:48, 1 September 2014
  • * Discrepancies were found in some of the Castor database tables and columns. The Castor team are considering options with regard to ** Apply latest Oracle patches (PSU) to the production database systems (Castor, Atlas3D).
    13 KB (1,342 words) - 11:16, 3 September 2014
  • | Load slowly increases on lcgdb05. Database good so far (no errors or performances issue) and next backup postponed for ...failures whilst suspecting some network problem. Also during the night the Database Team on-call was contacted and identified a problem accessing a disk area u
    10 KB (1,628 words) - 09:31, 14 November 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (279 words) - 12:37, 5 September 2014
  • *I have a link to software to sync user database from a VOMS server, haven’t looked into this in detail yet.
    46 KB (6,062 words) - 10:07, 15 September 2014
  • ...stigating why the Atlas Frontier systems had problems using the new Cronos database. * Oracle patches (PSU) applied to the standby Neptune database (Castor Atlas & GEN) yesterday (Tuesday 30th Sep).
    13 KB (1,429 words) - 10:06, 8 October 2014
  • * Discuss with VOs and schedule a move of the database after the intervention.
    9 KB (1,409 words) - 15:12, 16 September 2014
  • ...problem where large numbers of invalid subrequests got stuck in the stager database, causing the instance to become blocked. After a few hours of getting worse ...Saturday evening by deleting all invalid subrequests from the ATLAS stager database. This restored service, and the downtime was ended at 11:36 on Sunday morni
    10 KB (1,594 words) - 10:56, 1 May 2015
  • * The Atlas Frontier service will be switched to use the new database system that updates from CERN using Oracle "GoldenGate" on 24th Sep. ** Apply latest Oracle patches (PSU) to the production database systems (Castor, LFC).
    12 KB (1,195 words) - 14:07, 17 September 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (297 words) - 16:23, 19 September 2014
  • ...ay morning (around 07:40) there was a crash of the Atlas SRM database. The database immediately restarted on a different RAC node, and has subsequently been pu ... it was switched back to the former database ("Ogma"). The Cronos Atlas 3D database updates from CERN via Oracle "Goldengate" which supersedes the Oracle "Stre
    12 KB (1,304 words) - 10:59, 24 September 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (383 words) - 10:53, 4 February 2015
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (274 words) - 15:25, 26 September 2014
  • * A new database back end for the Atlas 3D/Frontier system will be brought into use this aft
    49 KB (6,449 words) - 10:22, 29 September 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (366 words) - 15:20, 16 January 2015
  • # Path Authorization DataBase # QMUL runs the frontend, backend and database on one machine.
    12 KB (1,735 words) - 09:33, 5 July 2017
  • ...were some problems with the switch of the Atlas Frontier system to the new database last week - and that change was reverted.
    41 KB (5,169 words) - 09:22, 6 October 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    3 KB (479 words) - 09:41, 7 October 2014
  • ...ing Oracle 'DataGuard' which replicates the updates applied to the primary database onto the standby. At the time of writing this report we are awaiting an eng ...ce of the disk array that is being used temporarily by the Cronos back end database. An alternative, faster, disk array is being tested.
    15 KB (1,740 words) - 10:50, 15 October 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    3 KB (479 words) - 16:36, 10 October 2014
  • Database Issues |Database
    6 KB (928 words) - 16:45, 3 January 2019
  • ...ere was a scheduled outage of the Atlas and GEN Castor instances while the database configuration was put back in its normal operating state. ...has now changed back, the problem has is solved. More generally, the CIP's database connectors need updating when the connection details change.
    14 KB (1,556 words) - 13:12, 15 October 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (378 words) - 12:09, 17 October 2014
  • ...a downtime of the Castor Atlas and GEN instances to revert to the 'normal' database configuration.
    39 KB (4,711 words) - 03:39, 21 October 2014
  • ... completing the change. (This alleviates a problem whereby the replacement database system for OGMA ("Cronos") was not performing well enough owing to limitati ...(29th Oct). This is expected to be a transparent intervention. The 'Pluto' database hosts the Castor Nameserver as well as the CMS and LHCb stager databases.
    14 KB (1,591 words) - 11:09, 22 October 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (270 words) - 14:50, 27 October 2014
  • * Oracle patching is ongoing with the pluto standby database patched on Monday (27th). The pluto primary is being patched today (29th). ...(29th Oct). This is expected to be a transparent intervention. The 'Pluto' database hosts the Castor Nameserver as well as the CMS and LHCb stager databases.
    14 KB (1,569 words) - 13:13, 29 October 2014
  • ...cessary following problems with one of the disk arrays hosting the primary database. * The OGMA database system (Atlas3D/Frontier) has been updated and switched to using Oracle Gol
    40 KB (4,976 words) - 10:25, 27 October 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e * New VM configured to run against the standby CASTOR database will be created as a front-end for dark data etc queries.
    2 KB (355 words) - 10:19, 3 November 2014
  • ...e applied to the pluto standby database yesterday and the production pluto database will be patched tomorrow. ...cessary following problems with one of the disk arrays hosting the primary database.
    42 KB (5,228 words) - 10:37, 4 November 2014
  • * [[DPM MySQL database]] - Description of the DPM MySQL database tables.
    5 KB (882 words) - 10:18, 1 August 2018
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    1 KB (226 words) - 13:51, 12 November 2014
  • * The OGMA database system (Atlas3D/Frontier) has been updated and switched to using Oracle Gol
    48 KB (6,138 words) - 09:19, 10 November 2014
  • * Over the weekend there was a hardware problem on one of the database nodes behind the Atlas 3D/Frontier service. The Oracle RAC continued to fun ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be
    13 KB (1,376 words) - 15:37, 12 November 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (267 words) - 14:41, 14 November 2014
  • ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,302 words) - 14:14, 19 November 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (265 words) - 14:14, 21 November 2014
  • ... of Friday 21st Nov. there was a problem of locking sessions in the Castor database that affected CMS & LHCb. Whilst this was transitory the cause has been und ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be
    14 KB (1,484 words) - 15:28, 26 November 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (364 words) - 15:03, 2 December 2014
  • * The problem of locking sessions in the Castor database that affected CMS & LHCb recurred on the morning of Tuesday 2nd December. W ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be
    13 KB (1,397 words) - 12:01, 3 December 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (331 words) - 10:53, 4 February 2015
  • ** Application of Oracle PSU patches to database systems. ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be
    14 KB (1,514 words) - 17:14, 21 January 2015
  • ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,504 words) - 14:50, 17 December 2014
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    3 KB (386 words) - 11:33, 19 December 2014
  • 46 KB (5,865 words) - 23:34, 26 December 2014
  • ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be ** Switch LFC/3D to new Database Infrastructure.
    17 KB (1,780 words) - 12:56, 7 January 2015
  • 47 KB (5,942 words) - 15:24, 8 January 2015
  • BDII - Berkeley Database Information Index.
    2 KB (306 words) - 12:29, 12 March 2015
  • * A Tier 1 Database cleanup is planned so as to eliminate a number of excess tables and other e
    2 KB (368 words) - 13:40, 9 January 2015
  • ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,559 words) - 10:52, 21 January 2015
  • 44 KB (5,523 words) - 22:20, 18 January 2015
  • 44 KB (5,505 words) - 10:46, 26 January 2015
  • ** Application of Oracle PSU patches to database systems. ** A new database (Oracle RAC) has been set-up to host the Atlas 3D database. This is updated from CERN via Oracle GoldenGate. This system is yet to be
    13 KB (1,340 words) - 12:21, 28 January 2015
  • ...tance on your head node (or wherever your DPM database is) to create a new database for accounting purposes. The final line, which grants access to the dpminfo ...n to write daily logs of the usage of the DPM, by user and group, into the database you just created.
    13 KB (1,952 words) - 16:03, 3 February 2015
  • ... Castor service restarts were carried out to ensure the connections to the database were correct. * Application of Oracle patches to some database nodes.
    13 KB (1,435 words) - 11:48, 4 February 2015
  • ...th production Atlas Frontier machines are now using Cronos as the Atlas 3D database backend instead of Ogma. ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,187 words) - 13:13, 18 February 2015
  • * Application of Oracle patches to some database nodes (ongoing). | Castor services At Risk during application of regular patches to back end database systems.
    13 KB (1,290 words) - 11:23, 11 February 2015
  • Database
    11 KB (608 words) - 15:00, 17 March 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,197 words) - 08:36, 8 April 2015
  • The dpm database may need updated to replace "null" entries with "0" entries for the banned ...iles/usr/etc/DPMCONFIG /usr/etc/NSCONFIG had the old hostname which causes database problems. This would not happen if you did not run yaim before
    8 KB (1,351 words) - 10:30, 4 March 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies were found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,175 words) - 14:56, 4 March 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies were found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,242 words) - 14:15, 11 March 2015
  • ...uarantor for everyone, so by default everyone will be”‘LCG"’d in the database (new HR rules mean Externals automatically take on the organic-unit of the
    48 KB (6,074 words) - 10:36, 16 March 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,182 words) - 14:05, 18 March 2015
  • ...uarantor for everyone, so by default everyone will be”‘LCG"’d in the database (new HR rules mean Externals automatically take on the organic-unit of the
    44 KB (5,438 words) - 08:48, 23 March 2015
  • ...etwork switch turned itself off. This affected connectivity to many of the database servers. Staff attended site and reset the PDU. Most services were affected ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,330 words) - 10:18, 1 April 2015
  • ...uarantor for everyone, so by default everyone will be”‘LCG"’d in the database (new HR rules mean Externals automatically take on the organic-unit of the
    44 KB (5,487 words) - 08:53, 30 March 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies found in some of the Castor database tables and columns. (The issue has no operational impact.)
    12 KB (1,175 words) - 10:12, 8 April 2015
  • * Check monitoring of the database servers to flag load issues. * Make a system available a system for regular validation of database backups
    8 KB (1,074 words) - 09:36, 18 September 2018
  • ...gh there appears to be two extended outages affecting access to the Hermes database. It is not understood why this was the case.
    15 KB (2,406 words) - 16:43, 17 August 2015
  • ** Switch LFC/3D to new Database Infrastructure. ** Fix discrepancies found in some of the Castor database tables and columns. (The issue has no operational impact.)
    13 KB (1,382 words) - 13:27, 15 April 2015
  • ... on Tuesday next week (28th April) for an update to Oracle on the back end database.
    43 KB (5,339 words) - 06:42, 27 April 2015
  • * Update to the Oracle database behind the LFC during today (Tuesday 28th April).
    40 KB (4,831 words) - 21:51, 8 May 2015
  • * Update to the Oracle database behind the Atlas Frontier service this morning (Tuesday 5th May). * Draft dates for the upgrade of the Oracle database behind Castor(to version 11.2.0.4) were presented.
    40 KB (4,963 words) - 21:55, 8 May 2015
  • ...ed at http://hostname:port/, and in addition data is exported to a central database. For sites running a batch system with cgroups enabled, cAdvisor can provid ...me in the 'Database Details' part of 'Create a Database' and click 'Create Database'.
    4 KB (584 words) - 20:09, 12 May 2015
  • ** Week 26-28 May: Install software on Database Systems (some 'At Risks') ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,523 words) - 12:07, 13 May 2015
  • * We are planning an update to the version of the Oracle database behind Castor. Dates to be finalised. * Revised (still draft) dates for the upgrade of the Oracle database behind Castor (to version 11.2.0.4) were presented.
    46 KB (5,803 words) - 11:48, 16 May 2015
  • * We are planning an update to the version of the Oracle database behind Castor. Dates to be finalised. * Revised (still draft) dates for the upgrade of the Oracle database behind Castor (to version 11.2.0.4) were presented.
    46 KB (5,732 words) - 18:32, 23 May 2015
  • * On Wednesday 20th May the rack containing the standby database systems for Castor were moved to the Atlas building. There were some diffic ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,470 words) - 11:04, 27 May 2015
  • * Tier-1problems with secondary database system for Castor - resolved quickly. * Our plans to update to the version of the Oracle database behind Castor are delayed so that we avoid interventions for this cause dur
    43 KB (5,271 words) - 22:18, 31 May 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    16 KB (1,741 words) - 13:24, 10 June 2015
  • * Tier-1problems with secondary database system for Castor - resolved quickly. * Our plans to update to the version of the Oracle database behind Castor are delayed so that we avoid interventions for this cause dur
    43 KB (5,271 words) - 13:02, 6 June 2015
  • * Tier-1problems with secondary database system for Castor - resolved quickly.
    43 KB (5,391 words) - 15:50, 14 June 2015
  • | Outage of All Castor instances during upgrade of Oracle back end database. | Warning (At Risk) on All Castor instances during upgrade of back end Oracle database.
    14 KB (1,579 words) - 07:36, 27 August 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,692 words) - 12:10, 17 June 2015
  • * Tier-1problems with secondary database system for Castor - resolved quickly.
    45 KB (5,632 words) - 13:32, 21 June 2015
  • * The change to a database procedure to speeds up file open times within Castor was made to the Atlas ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,370 words) - 13:22, 1 July 2015
  • * A detailed change to a database procedure has been made to the LHCb Castor stager (yesterday - Tuesday 23rd ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,738 words) - 13:30, 24 June 2015
  • * Following completion of the roll-out of the modified Castor database procedure we have started adjusting the length of a 'wait' to study the eff ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,261 words) - 11:39, 15 July 2015
  • * The change a database procedure to speeds up file open times within Castor was made to the GEN in ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,329 words) - 09:31, 8 July 2015
  • ...some stored files do not have the correct location on disk recorded in the database. Investigations show this applies to very few files (10 files for Atlas in ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,372 words) - 11:46, 22 July 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,341 words) - 12:17, 29 July 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,380 words) - 13:20, 12 August 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,580 words) - 13:55, 19 August 2015
  • | Castor SRM systems. Small number of internal service machines. Database systems on Red Hat Enterprise 5.
    2 KB (318 words) - 15:36, 29 March 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,588 words) - 12:05, 5 August 2015
  • ...isk servers OS during second half of August and updating the Castor Oracle database during September.
    52 KB (6,730 words) - 22:58, 9 August 2015
  • ...isk servers OS during second half of August and updating the Castor Oracle database during September.
    52 KB (6,730 words) - 23:00, 9 August 2015
  • ...isk servers OS during second half of August and updating the Castor Oracle database during September.
    48 KB (6,103 words) - 23:03, 16 August 2015
  • ...ly for 26/27 August). Also finalizing plans for updating the Castor Oracle database during September/October. (See dates in report linked just above).
    45 KB (5,578 words) - 19:59, 22 August 2015
  • ...rsday 3rd Sep) and a series of Castor interventions as the back-end Oracle database is upgraded to a later version.
    41 KB (5,000 words) - 04:11, 1 September 2015
  • | Outage of All Castor instances during upgrade of Oracle back end database. | Warning (At Risk) on All Castor instances during upgrade of back end Oracle database.
    14 KB (1,541 words) - 11:10, 2 September 2015
  • ...rsday 3rd Sep) and a series of Castor interventions as the back-end Oracle database is upgraded to a later version.
    43 KB (5,351 words) - 16:49, 6 September 2015
  • == Install a new database/service etc == Database InstalledComponentsDB from DIRAC/FrameworkSystem installed successfully
    8 KB (1,208 words) - 10:35, 27 July 2023
  • ...rsday 3rd Sep) and a series of Castor interventions as the back-end Oracle database is upgraded to a later version.
    44 KB (5,604 words) - 10:22, 15 September 2015
  • | Outage of All Castor instances during upgrade of Oracle back end database. | Warning (At Risk) on All Castor instances during upgrade of back end Oracle database.
    15 KB (1,569 words) - 12:24, 16 September 2015
  • ...st week, have continued. As the backlog (and queue length) has reduced the database load has dropped. CMS have also submitted many transfers with a large numbe | Outage of All Castor instances during upgrade of Oracle back end database.
    14 KB (1,604 words) - 12:01, 23 September 2015
  • | Outage of All Castor instances during upgrade of Oracle back end database. | Warning (At Risk) on All Castor instances during upgrade of back end Oracle database.
    13 KB (1,415 words) - 12:15, 30 September 2015
  • ... was the switch-over of the production and standby versions of the "pluto" database to return these to their correct configuration. This completes the upgrades ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,416 words) - 09:37, 14 October 2015
  • ...the time of the meeting Castor is down. This is the upgrade of the "Pluto" database which hosts the Nameserver as well as the CMS & LHCb stager databases. The
    52 KB (6,786 words) - 16:22, 12 October 2015
  • * The Castor Oracle database "pluto" was successfully upgraded to Oracle 11.2.0.4 yesterday (6th Oct). | Outage of All Castor instances during upgrade of Oracle back end database.
    14 KB (1,524 words) - 14:55, 8 October 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,299 words) - 11:10, 21 October 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,221 words) - 12:58, 28 October 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,234 words) - 14:05, 11 November 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,253 words) - 10:56, 4 November 2015
  • ...n on the CPU efficiency accounting discussion of last week."Stuart has the database merge under way now. We had hoped it would be done by the end of October bu
    48 KB (6,095 words) - 12:37, 16 November 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,287 words) - 09:15, 18 November 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,218 words) - 09:50, 25 November 2015
  • ...n on the CPU efficiency accounting discussion of last week."Stuart has the database merge under way now. We had hoped it would be done by the end of October bu
    48 KB (6,163 words) - 16:24, 29 November 2015
  • * Plan to replace disk array and database nodes underway - also a possible improvement in configuration, frequent wri
    6 KB (1,018 words) - 12:25, 4 December 2015
  • * Plan to replace disk array and database nodes underway - also a possible improvement in configuration, frequent wri
    7 KB (1,141 words) - 15:00, 11 December 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    16 KB (1,824 words) - 12:29, 6 January 2016
  • | Ask CIC portal people if we can have access to the reports database for analysis | Steve Lloyd test failures coincident with backup of WMS database, which was locking the DB (for ~45mins) and preventing job-handling. Glasgo
    68 KB (11,032 words) - 13:08, 16 September 2016
  • ...account with the VO Administrator Role. Now you will be able manage the VO database. ...he registration of users and their associated groups and roles in the VOMS database;<br> By agreement with you the formal registration of a new user can be don
    14 KB (2,315 words) - 11:12, 16 December 2015
  • ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,710 words) - 11:39, 23 December 2015
  • ...a few files badly drained back in 2014. I'm trying to figure out a clever, database-y way of listing all the files on these long gone servers (the best I've go
    150 KB (23,740 words) - 12:54, 9 January 2017
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,350 words) - 10:02, 27 January 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,458 words) - 14:30, 13 January 2016
  • * Plan to replace disk array and database nodes underway - also a possible improvement in configuration, frequent wri
    7 KB (1,085 words) - 16:11, 18 January 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    11 KB (1,138 words) - 08:33, 2 March 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    46 KB (5,834 words) - 12:12, 28 November 2016
  • * Plan to replace disk array and database nodes underway - also a possible improvement in
    7 KB (1,203 words) - 17:47, 23 January 2016
  • * We are working a refresh of the database system behind the LFC. * Operational issues (DPM database errors) and kablooie
    47 KB (5,867 words) - 21:18, 31 January 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,664 words) - 09:48, 10 February 2016
  • * We are working a refresh of the database system behind the LFC. * Operational issues (DPM database errors) and kablooie
    46 KB (5,812 words) - 23:00, 8 February 2016
  • * We are working a refresh of the database system behind the LFC. * Operational issues (DPM database errors) and kablooie
    54 KB (7,071 words) - 09:10, 15 February 2016
  • * We are working a refresh of the database system behind the LFC. * Operational issues (DPM database errors) and kablooie
    44 KB (5,398 words) - 11:29, 22 February 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,237 words) - 09:21, 24 February 2016
  • * We are working a refresh of the database system behind the LFC. * Operational issues (DPM database errors) and kablooie
    45 KB (5,688 words) - 11:06, 29 February 2016
  • * We are working a refresh of the database system behind the LFC.
    43 KB (5,347 words) - 17:58, 6 March 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,208 words) - 15:53, 9 March 2016
  • ...stor for CMS overnight last night (Tuesday/Wednesday 25/26 April) when the database reported blocking sessions. This fixed itself after a couple of hours.
    14 KB (1,457 words) - 10:30, 26 April 2017
  • * Birmingham DPM MySQL database corruption - what was the fix?
    47 KB (6,060 words) - 23:16, 13 March 2016
  • * Birmingham DPM MySQL database corruption - what was the fix? ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor.
    42 KB (5,278 words) - 01:55, 20 March 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,283 words) - 21:43, 22 March 2016
  • * Birmingham DPM MySQL database corruption - what was the fix? ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor.
    44 KB (5,455 words) - 02:03, 29 March 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,394 words) - 11:01, 30 March 2016
  • * Birmingham DPM MySQL database corruption - what was the fix? ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor.
    44 KB (5,446 words) - 23:24, 3 April 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,352 words) - 12:13, 6 April 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,266 words) - 09:46, 20 April 2016
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. In the meantime we will carry out the (separate) update of t
    40 KB (4,974 words) - 12:23, 17 April 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,408 words) - 10:29, 20 April 2016
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. We had thought to update the Castor SRMs to version 2.14 in
    46 KB (5,853 words) - 07:32, 9 May 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,468 words) - 13:32, 27 April 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,309 words) - 10:33, 10 May 2016
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. We had thought to update the Castor SRMs to version 2.14 in
    46 KB (5,853 words) - 07:33, 9 May 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,576 words) - 08:37, 25 May 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,613 words) - 10:29, 25 May 2016
  • * The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful r ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,734 words) - 10:46, 11 May 2016
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. We had thought to update the Castor SRMs to version 2.14 in
    45 KB (5,695 words) - 00:36, 24 May 2016
  • ... This is pending resolution of a problem around memory usage by the Oracle database behind Castor. We had thought to update the Castor SRMs to version 2.14 in
    43 KB (5,401 words) - 01:24, 30 May 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,454 words) - 07:42, 7 June 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    13 KB (1,445 words) - 10:54, 15 June 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    14 KB (1,602 words) - 11:11, 8 June 2016
  • writes to the primary database causing ca. 20 min of writes to standby database
    3 KB (485 words) - 10:59, 24 June 2016
  • ...e) by invoking it (on the DPM head node, or any other node with sufficient database and security permissions with respect to DPM and '''$DPNS_HOST''' set to po
    1 KB (199 words) - 13:32, 8 June 2016
  • ...uch writes to the primary database causing ca. 20 min of writes to standby database Need to keep track of DB activity over the next weeks
    3 KB (602 words) - 12:30, 24 June 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    15 KB (1,605 words) - 09:56, 29 June 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,248 words) - 12:21, 6 July 2016
  • ** Switch LFC database to use new Database Infrastructure.
    12 KB (1,173 words) - 12:29, 20 July 2016
  • ** Switch LFC/3D to new Database Infrastructure.
    12 KB (1,293 words) - 14:21, 13 July 2016
  • * Note: Upgrade of Database System behind the LFC on Monday (1st August).
    42 KB (5,278 words) - 19:59, 1 August 2016
  • * The database behind the LFC was moved to new hardware on Monday (1st Aug).
    12 KB (1,328 words) - 15:58, 9 August 2016
  • * Note: Upgrade of Database System behind the LFC on Monday (1st August).
    42 KB (5,192 words) - 21:21, 7 August 2016
  • ...g information and cluster power. We'll also show how we have used a simple database tool to manage the cluster layout and do the necessary arithmetic for a div =The site layout database=
    23 KB (3,689 words) - 09:13, 4 April 2019
  • * The Database System behind the LFC was upgraded (to new hardware) at the start of last w
    45 KB (5,779 words) - 09:19, 22 August 2016
  • * The Database System behind the LFC was upgraded (to new hardware) at the start of last w
    50 KB (6,392 words) - 07:47, 16 August 2016
  • ...n the server but the corresponding cleanup had not been done in the Castor database. This has since been resolved.
    12 KB (1,323 words) - 08:20, 24 August 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    49 KB (6,409 words) - 00:39, 26 September 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    47 KB (5,958 words) - 09:02, 15 October 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    54 KB (7,110 words) - 14:59, 10 October 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    46 KB (5,756 words) - 13:12, 30 January 2017
  • ...iny new kernels. He undertook some preliminary checks and the pages, Wiki, database etc all look ok, but we should inform him of any issues observed. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    47 KB (6,026 words) - 09:22, 21 November 2016
  • ...) there were problems with Castor during a reconfiguration of the back-end database nodes. A GGUS ticket was received from LHCb - other VOs were also affected. ** Removal of "asmlib" layer on Oracle database nodes. (Ongoing)
    15 KB (1,598 words) - 12:18, 15 March 2017
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    50 KB (6,392 words) - 08:14, 23 October 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    50 KB (6,401 words) - 08:48, 31 October 2016
  • ...iny new kernels. He undertook some preliminary checks and the pages, Wiki, database etc all look ok, but we should inform him of any issues observed. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    51 KB (6,619 words) - 11:34, 7 November 2016
  • ...iny new kernels. He undertook some preliminary checks and the pages, Wiki, database etc all look ok, but we should inform him of any issues observed. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    52 KB (6,786 words) - 05:33, 14 November 2016
  • ...a problem with the "test" FTS3 service. The disk area hosting the back end database filled up. Atlas (the only users of this) were asked to move to the "produc
    12 KB (1,334 words) - 12:48, 16 November 2016
  • ... the early morning of Friday (2nd June) caused by blocking sessions in the database.
    16 KB (1,833 words) - 13:11, 7 June 2017
  • * FTS Database adjustments requested by ATLAS
    14 KB (1,563 words) - 12:48, 21 December 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    44 KB (5,462 words) - 10:47, 6 December 2016
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    45 KB (5,745 words) - 13:04, 12 December 2016
  • ***RHUL: There was a DPM database move scheduled during the month. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    49 KB (6,219 words) - 11:44, 9 January 2017
  • ***RHUL: There was a DPM database move scheduled during the month. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    46 KB (5,848 words) - 09:12, 20 December 2016
  • ... (6/11) ''Reducing the number of simultaneous connections and allowing the database to catch up fixed things. Solved.''
    121 KB (19,081 words) - 12:04, 23 January 2018
  • | 20140219-01 || Normal || N/A || John || Start post-mortem of loss of FTS3 database VM || Closed || 2014-02-25
    2 KB (289 words) - 14:09, 21 December 2016
  • ***RHUL: There was a DPM database move scheduled during the month. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    49 KB (6,317 words) - 09:33, 3 January 2017
  • ***RHUL: There was a DPM database move scheduled during the month. ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    51 KB (6,530 words) - 08:56, 16 January 2017
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    47 KB (5,971 words) - 09:04, 23 January 2017
  • ...articular library used by Castor needed updating, a Castor parameter and a database parameter was also adjusted. * There will need to be an update to all Oracle database servers to remove a component called ASMLIB. This si being tested now.
    15 KB (1,614 words) - 14:30, 25 January 2017
  • ** Two VOs, Atlas and LHCb have seen issues with database resources (number of cursors). The latest being Atlas on Friday 10th. We st ** Removal of "asmlib" layer on Oracle database nodes.
    13 KB (1,310 words) - 11:47, 15 February 2017
  • ** There has been a problem with the LHCb instance - we see a database resource (number of cursors) exhausted - and have had to restart the servic ** Removal of "asmlib" layer on Oracle database nodes.
    16 KB (1,827 words) - 13:03, 9 February 2017
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    44 KB (5,446 words) - 15:00, 8 February 2017
  • ...te issuance problems. Jens reported that on 15th a partial but significant database corruption occurred on the signing system for the CA. Data was restored fr
    49 KB (6,270 words) - 11:57, 13 February 2017
  • ** An occasional problem with a database resource (number of cursors) becoming exhausted. This has affected more th ...ystems have had security and other patches applied. In particular back end database systems are being updated to remove a software layer ("asmlib").
    14 KB (1,425 words) - 14:24, 22 February 2017
  • * A round of Linux kernel patching of back-end database systems has been completed.
    17 KB (1,714 words) - 14:41, 3 January 2018
  • * Various systems have had security and other patches applied. More back-end database systems have been updated to remove a software layer ("asmlib"). ** Removal of "asmlib" layer on Oracle database nodes.
    15 KB (1,577 words) - 14:44, 1 March 2017
  • * Ongoing work applying security and other patches. More back-end database systems have been updated to remove a software layer ("asmlib"). ** Removal of "asmlib" layer on Oracle database nodes. (Ongoing)
    14 KB (1,423 words) - 15:14, 8 March 2017
  • ... problem. The cause was a known bug that causes exhaustion of a particular database resource. ** Removal of "asmlib" layer on Oracle database nodes. (Ongoing)
    14 KB (1,476 words) - 15:53, 22 March 2017
  • ...t to migrate the disk nodes until the head node has finished importing the database. == Database dumps ==
    9 KB (1,549 words) - 14:53, 26 April 2023
  • ...stor for CMS overnight last night (Tuesday/Wednesday 25/26 April) when the database reported blocking sessions. This fixed itself after a couple of hours.
    16 KB (1,689 words) - 12:44, 4 May 2017
  • ...y - DPM can have these daemons hosted elsewhere (and even have the backend database server for these daemons on a different machine again). As of DPM 1.9.x, DP
    3 KB (461 words) - 15:03, 3 May 2017
  • ...when the node is built. Hiera looks them up in a user-defined hierarchical database. Hence general, default settings can be generally applied to some nodes, wh ...base fields. If a hit is made, the specific value is pulled from the Hiera database and may be used as the final resolution of a variable (or it may be overrid
    17 KB (2,792 words) - 16:35, 2 January 2018
  • ...er nodes at NERSC worked very well. We have made some minor optimisations (database cache, number of threads etc) on the UK side and have enquired with NERSC a
    3 KB (554 words) - 12:28, 16 October 2018
  • ...roblem with the CMS Castor instance. On-call staff responded. The back-end database reported locking sessions and hot-spotting of files was seen. The problem a
    16 KB (1,785 words) - 07:47, 26 July 2017
  • ...s Frontier service on Thursday 27th July. We saw high load on the back end database systems. ...Ms from Atlas work. This overwhelmed the SRMs. After some work by both the database and Castor on-call staff an outage was declared for Atlas in the GOC DB. On
    19 KB (2,046 words) - 13:05, 9 August 2017
  • | FTS3 database VM migration ongoing ...ssible to submit new transfers or query the status of transfers during the database migration.
    17 KB (1,707 words) - 09:27, 23 August 2017
  • ... FTS3 services will be merged and will make use of a resilient distributed database.
    15 KB (1,513 words) - 15:44, 18 October 2017
  • ... FTS3 services will be merged and will make use of a resilient distributed database. ...the FTS3 services have been merged and set-up on a resilient (distributed) database they will have IPv6 dual-stack enabled.
    15 KB (1,589 words) - 14:02, 11 October 2017
  • ... FTS3 services will be merged and will make use of a resilient distributed database. ** On a new distributed database (a Galera MariaDB cluster) for FTS3
    14 KB (1,387 words) - 07:31, 26 October 2017
  • * Production FTS was migrated to a distributed database for the back-end. (Tuesday, 21st November).
    16 KB (1,623 words) - 13:52, 22 November 2017
  • ... FTS3 services will be merged and will make use of a resilient distributed database.
    14 KB (1,437 words) - 09:24, 7 November 2017
  • ... FTS3 services will be merged and will make use of a resilient distributed database.
    15 KB (1,557 words) - 16:32, 8 November 2017
  • * Production FTS migrating to a distributed database for the back-end. (Proposed for next Tuesday, 21st November). ... FTS3 services will be merged and will make use of a resilient distributed database.
    15 KB (1,515 words) - 14:36, 15 November 2017
  • Patching of the Juno database on 7th of March: CASTOR downtime from 10:30 to 13:30
    2 KB (348 words) - 14:44, 5 March 2018
  • * There is an outage on Castor announced for Thursday (1st March) while the database systems have Oracle patches applied.
    16 KB (1,553 words) - 11:43, 28 February 2018
  • .... There has been a high rate of deletion requests, and the back end stager database has been struggling to keep up with the total load (reads, writes and delet | emergency downtime of Castor Atlas while rebuilding some database tables
    17 KB (1,803 words) - 14:26, 24 January 2018
  • ... file metadata access problems would be more exact). The ticket mentions a database move, did you get round to this? In progress (18/9) A fresh atlas transfer error ticket. Robert found that their DPM's mysql database wasn't responding, but a restart should have fixed it (and indeed a peek at
    141 KB (22,376 words) - 17:35, 21 January 2019
  • |emergency downtime of Castor Atlas while rebuilding some database tables
    19 KB (1,995 words) - 13:13, 7 February 2018
  • Patching of the Juno database on 7th of March: CASTOR downtime from 10:30 to 13:30
    2 KB (335 words) - 12:28, 23 February 2018
  • Run the final backup of mysql database on the old headnode Load old mysql backup database to new db
    3 KB (466 words) - 11:49, 13 March 2018
  • * There is an outage on Castor announced for Thursday (1st March) while the database systems have Oracle patches applied.
    16 KB (1,553 words) - 11:09, 6 March 2018
  • ...f availability in the poor weather. (It was to apply Oracle patches to the database systems behind Castor). It is being re-scheduled possibly towards the end
    17 KB (1,682 words) - 11:38, 12 March 2018
  • Database TransformationDB from DIRAC/TransformationSystem installed successfully
    4 KB (544 words) - 13:51, 20 June 2018
  • ...the new namespace provider for dCache, which replaced PNFS. It is built on database technology, but is designed in such a way that it will still be possible to
    398 B (65 words) - 10:53, 1 August 2018
  • * It was noted that the migration of the LHC from an Oracle backend database to MySQL was underway.
    19 KB (1,944 words) - 13:25, 22 August 2018
  • Install FTS3 database and add index as per [[https://github.com/DIRACGrid/DIRAC/wiki/DIRAC-v6r20p Database FTS3DB from DIRAC/DataManagementSystem installed successfully
    2 KB (348 words) - 10:46, 17 August 2018
  • ...d LFC database. More correctly we believe a value (or values), within that database is causing an issue. We don't often see metadata showing a file-size of 184 ...ng and corrupted between the latest working and rolled back version of the database.
    17 KB (1,732 words) - 10:02, 26 September 2018
  • ...breakage of database = 19th August Fixed 21st September Second breakage of database = Tuesday 25th September 1pm. ** This is explanation also accounts for the fact that rolling back the database to an earlier backup also worked
    16 KB (1,646 words) - 14:01, 3 October 2018
  • Once APEL accounting is working, the APEL client database server also needs to be registered with with this service type (see below).
    16 KB (2,635 words) - 15:21, 7 November 2019
  • ...he Production Manager to find out when the disk replacement for the Oracle database took place and if it went smoothly.
    13 KB (1,286 words) - 10:08, 3 July 2019
  • ...stor Downtime for 22 January for all WLCG and other HEP VOs. ( Nameserver database upgrade.) https://goc.egi.eu/portal/index.php?Page_Type=Downtime&id=28258
    15 KB (1,714 words) - 09:39, 22 January 2020
  • ...stor Downtime for 22 January for all WLCG and other HEP VOs. ( Nameserver database upgrade.) https://goc.egi.eu/portal/index.php?Page_Type=Downtime&id=28258
    15 KB (1,701 words) - 11:20, 22 January 2020
  • ...iar with the dynamics of the system. For example, checking the GOCDB sites database to see if sites are unavailable due to a planned downtime for an upgrade or
    2 KB (377 words) - 12:27, 3 February 2020
  • # Using the daily backup of DB02 move this to DB03 and apply the database * Find the database name on DB03
    2 KB (289 words) - 12:32, 8 September 2021
  • existing Rucio database, it should be possible to start using the m-VO instance without any of the following configuration steps once the database has been
    24 KB (3,490 words) - 13:51, 19 April 2021
  • ** Core & Internals: M-VO database conversion improvements addresses for the database, server etc. should be set in `etc/rucio.cfg` as
    9 KB (1,497 words) - 13:05, 19 April 2021
  • * database login in the environmental variable RUCIO_CFG_DATABASE_DEFAULT
    2 KB (230 words) - 11:26, 12 November 2021

View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)