Search results

Create the page "Database" on this wiki!

• Benchmarking procedure
  ...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
• Operations Bulletin 220816
  * 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
• Operations Bulletin 150816
  * 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
• Tier1 Operations Report 2016-08-17
  ...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

• File:Figure7.jpg ER Diagram of Site Layout Database (553 × 262 (19 KB)) - 11:16, 6 September 2016

• Operations Bulletin 260916
  ...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
• Operations Bulletin 171016
  ...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
• Operations Bulletin 101016
  ...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
• Operations Bulletin 300117
  ...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
• Operations Bulletin 211116
  ...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
• Tier1 Operations Report 2017-03-15
  ...) 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
• Operations Bulletin 241016
  ...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
• Operations Bulletin 311016
  ...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
• Operations Bulletin 071116
  ...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
• Operations Bulletin 141116
  ...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
• Tier1 Operations Report 2016-11-09
  ...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
• Tier1 Operations Report 2017-06-07
  ... the early morning of Friday (2nd June) caused by blocking sessions in the database.
  16 KB (1,833 words) - 13:11, 7 June 2017
• Tier1 Operations Report 2016-12-14
  * FTS Database adjustments requested by ATLAS
  14 KB (1,563 words) - 12:48, 21 December 2016
• Operations Bulletin 051216
  ...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
• Operations Bulletin 121216
  ...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