1 / 6

Online Databases Status

Online Databases Status . V.Sirotenko, 6/6/2005. D0 Oracle Cluster (Green) Hardware: Intel Xeon, 2.8 GHz, 2 CPU, 4 Gb RAM OS: Fermi Linux LTS 3.03 Oracle Software installed: d0olg : Oracle Database 10g, v10.1.0.3.0 (production DB)

hali
Download Presentation

Online Databases Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Online Databases Status V.Sirotenko, 6/6/2005 • D0 Oracle Cluster (Green) • Hardware: Intel Xeon, 2.8 GHz, 2 CPU, 4 Gb RAM • OS: Fermi Linux LTS 3.03 • Oracle Software installed: • d0olg : Oracle Database 10g, v10.1.0.3.0 (production DB) • d0olh : Oracle Database 10g, v10.1.0.3.0 (development DB) • Oracle Designer Repository, v9.0.4 • d0oli : Oracle Enterprise Manager 10g Grid Control, v10.1.0.3 • With latest April 2005 patchset V.Sirotenko, June 6, 2005

  2. Monitoring Grid Control Portal V.Sirotenko, June 6, 2005

  3. Monitoring Grid Control Portal (cont) V.Sirotenko, June 6, 2005

  4. Database sizes & backup strategy • Space usage: • production 47 Gb ( was 37 Gb in November 2004) • development 53 Gb ( was 48 Gb in November 2004) • So estimated growth is 20 Gb/year (prod) and 10 Gb/year (dev) • * could be much more after implementation of SESDB schema • Archive Logs: keep on disk for three consecutive days • RMAN: full automatic backup every day for read/write tablespaces, • keep 2 consecutive days on disk; manual backup for readonly tablespaces as needed • Export: three times a week V.Sirotenko, June 6, 2005

  5. What was done since 11/2004 - implemented e-mail notification about alerts from OEM Grid - dbMonitor.py was reconfigured and moved on DB production node, self restarts itself through cronjob mechanism - set of dba scripts was written to allow db services failover from d0olg(d0olh) d0oli - schemas fpd_onl, stt_param moved from dev to prod DB - partitioning schemes were implemented for: smt_calib, cft_calib For cal_calib partitioning design is ready but not implemented yet V.Sirotenko, June 6, 2005

  6. Still to be done • - there is a bug in Fermi Linux LTS 3.03 which causes frequent DB • failover (kernel panic) which seems to be fixed in 3.04. • Upgrading of the DB cluster to 3.04 will be done shortly • - because Fermi Linux LTS is not certificated by Oracle, we will setup new online DB cluster based on Red Hat Enterprise Linux AS • and clone existing online prod and dev DB there, work already started • - modification to RUNS database: table RUN_STREAMS has to be • changed (extra column LOGICAL_STREAM NAME should be added). • RunGrabber has to be modified accordingly • - new schema SES will be designed and implemented to hold messages from Significant Event System (SES). At present we use flat ASCII files • and hope that moving to Oracle will make access to the data and data maintenance easier • others .. V.Sirotenko, June 6, 2005

More Related