Veritaban\u0131 Y\u00f6neticileri (DBAlar), genellikle i\u015f g\u00fcnlerine veya sorun giderme oturumlar\u0131na ba\u015flarken, veritaban\u0131n\u0131n sa\u011fl\u0131\u011f\u0131, performans\u0131 ve durumu hakk\u0131nda h\u0131zl\u0131 bir genel bak\u0131\u015f elde etmek i\u00e7in belirli sorgular \u00e7al\u0131\u015ft\u0131r\u0131rlar. Buna sa\u011fl\u0131k kontrol\u00fc veya g\u00fcnl\u00fck rutin denir. Bu sorgular, potansiyel sorunlar\u0131 belirlemelerine, sistem kaynaklar\u0131n\u0131 izlemelerine ve her \u015feyin sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmalar\u0131na yard\u0131mc\u0131 olur. \u0130\u015fte DBAlar\u0131n her \u015feyden \u00f6nce \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131 \u00fc\u00e7 temel sorgu ve bunlar\u0131n neden kritik oldu\u011funa dair a\u00e7\u0131klamalar:<\/p>
## 1. Veritaban\u0131 \u00c7al\u0131\u015fma S\u00fcresi ve Durumunu Kontrol Etme<\/p>
```sql
SELECT
instance_name,
status,
database_status,
startup_time,
host_name
FROM
v$instance;
```<\/p>
**\u00c7\u0131kt\u0131 \u00d6rne\u011fi:**<\/p>
| INSTANCE_NAME | STATUS | DATABASE_STATUS | STARTUP_TIME | HOST_NAME |
|---------------|--------|-----------------|--------------------|---------------|
| ORCL | OPEN | ACTIVE | 2023-10-01 08:00:00| db-server-01 |<\/p>
**Neden \u00d6nemli?**<\/p>
- **Veritaban\u0131 Eri\u015filebilirli\u011fi:** Veritaban\u0131n\u0131n \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 do\u011frular.
- **\u00c7al\u0131\u015fma S\u00fcresi:** Veritaban\u0131n\u0131n son ba\u015flat\u0131ld\u0131\u011f\u0131ndan bu yana ne kadar s\u00fcredir \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterir, bu da beklenmeyen yeniden ba\u015flatmalar\u0131 tespit etmeye yard\u0131mc\u0131 olabilir.
- **Durum:** Veritaban\u0131n\u0131n sa\u011fl\u0131kl\u0131 bir durumda olup olmad\u0131\u011f\u0131n\u0131 g\u00f6sterir (\u00f6rne\u011fin, \u2018OPEN\u2019, \u2018MOUNTED\u2019 veya \u2018DOWN\u2019).<\/p>
## 2. Aktif Oturumlar\u0131 ve Kaynak Kullan\u0131m\u0131n\u0131 \u0130zleme<\/p>
```sql
SELECT
sid,
serial#,
username,
status,
program,
sql_id,
event,
wait_time,
seconds_in_wait
FROM
v$session
WHERE
status = 'ACTIVE';
```<\/p>
**\u00c7\u0131kt\u0131 \u00d6rne\u011fi:**<\/p>
| SID | SERIAL# | USERNAME | STATUS | PROGRAM | SQL_ID | EVENT | WAIT_TIME | SECONDS_IN_WAIT |
|-----|---------|----------|--------|-------------|-----------|------------------------|-----------|-----------------|
| 123 | 45678 | APP_USER | ACTIVE | sqlplus.exe | abc123xyz | db file sequential read| 0 | 5 |<\/p>
**Neden \u00d6nemli?**<\/p>
- **Performans \u0130zleme:** Aktif oturumlar\u0131 ve ne yapt\u0131klar\u0131n\u0131 belirler, uzun s\u00fcren sorgular\u0131 veya kaynak darbo\u011fazlar\u0131n\u0131 tespit etmeye yard\u0131mc\u0131 olur.
- **Sorun Giderme:** Belirli olaylar\u0131 bekleyen oturumlar\u0131 ortaya \u00e7\u0131kar\u0131r (\u00f6rne\u011fin, G\/\u00c7, kilitler), bu da performans sorunlar\u0131n\u0131 g\u00f6sterebilir.
- **Kaynak Kullan\u0131m\u0131:** Kimin ba\u011fl\u0131 oldu\u011funu ve hangi kaynaklar\u0131 t\u00fcketti\u011fini anlamaya yard\u0131mc\u0131 olur.<\/p>
## 3. Tablo Alan\u0131 Kullan\u0131m\u0131n\u0131 Kontrol Etme<\/p>
```sql
SELECT
tablespace_name,
file_name,
bytes \/ 1024 \/ 1024 AS size_mb,
(bytes - (SELECT SUM(bytes) FROM dba_free_space WHERE file_id = file_id)) \/ 1024 \/ 1024 AS used_mb,
(bytes - (SELECT SUM(bytes) FROM dba_free_space WHERE file_id = file_id)) \/ bytes * 100 AS pct_used
FROM
dba_data_files;
```<\/p>
**\u00c7\u0131kt\u0131 \u00d6rne\u011fi:**<\/p>
| TABLESPACE_NAME | FILE_NAME | SIZE_MB | USED_MB | PCT_USED |
|-----------------|---------------------|---------|---------|----------|
| USERS | \/u01\/oradata\/users01| 1024 | 800 | 78.12 |
| SYSTEM | \/u01\/oradata\/system01| 512 | 450 | 87.89 |<\/p>
**Neden \u00d6nemli?**<\/p>
- **Depolama \u0130zleme:** Her tablo alan\u0131nda ne kadar alan kullan\u0131ld\u0131\u011f\u0131n\u0131 ve ne kadar\u0131n\u0131n kullan\u0131labilir oldu\u011funu takip eder, bu da alan t\u00fckenmesi hatalar\u0131n\u0131 \u00f6nlemeye yard\u0131mc\u0131 olur.
- **Kapasite Planlama:** Dolmak \u00fczere olan tablo alanlar\u0131n\u0131 belirler, bu da DBAlar\u0131n proaktif olarak daha fazla alan eklemesine olanak tan\u0131r.
- **Performans Etkisi:** Dolu tablo alanlar\u0131 performans d\u00fc\u015f\u00fc\u015f\u00fcne neden olabilir, bu nedenle kullan\u0131m\u0131 izlemek kritiktir.<\/p>
## 4. Engelleme Kilitlerini Kontrol Etme<\/p>
```sql
SELECT
blocking_session,
sid,
serial#,
wait_class,
event,
seconds_in_wait
FROM
v$session
WHERE
blocking_session IS NOT NULL;
```<\/p>
**\u00c7\u0131kt\u0131 \u00d6rne\u011fi:**<\/p>
| BLOCKING_SESSION | SID | SERIAL# | WAIT_CLASS | EVENT | SECONDS_IN_WAIT |
|------------------|-----|---------|--------------|---------------------------|-----------------|
| 123 | 456 | 78901 | Application | enq: TX - row lock contention | 120 |<\/p>
**Neden \u00d6nemli?**<\/p>
- **Kilitlenme Tespiti:** Di\u011fer oturumlar\u0131 engelleyen oturumlar\u0131 belirler, bu da uygulama zaman a\u015f\u0131mlar\u0131na veya hatalara neden olabilir.
- **Performans Darbo\u011fazlar\u0131:** Veritaban\u0131n\u0131 yava\u015flatan \u00e7eki\u015fme sorunlar\u0131n\u0131 \u00e7\u00f6zmeye yard\u0131mc\u0131 olur.<\/p>
## Bu Sorgular Neden DBAlar \u0130\u00e7in Kritiktir?<\/p>
1. **Proaktif \u0130zleme:** Bu sorgular, veritaban\u0131n\u0131n sa\u011fl\u0131\u011f\u0131na ili\u015fkin bir anl\u0131k g\u00f6r\u00fcnt\u00fc sa\u011flar, bu da DBAlar\u0131n sorunlar\u0131 b\u00fcy\u00fcmeden \u00f6nce yakalamas\u0131na olanak tan\u0131r.
2. **Sorun Giderme:** Performans sorunlar\u0131n\u0131n, kaynak \u00e7eki\u015fmesinin veya depolama sorunlar\u0131n\u0131n k\u00f6k nedenini h\u0131zl\u0131 bir \u015fekilde belirlemeye yard\u0131mc\u0131 olurlar.
3. **Operasyonel Verimlilik:** Bu sorgular\u0131 d\u00fczenli olarak \u00e7al\u0131\u015ft\u0131rarak, DBAlar veritaban\u0131n\u0131n en iyi \u015fekilde \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olabilir ve beklenmeyen kesintilerden ka\u00e7\u0131nabilir.<\/p>
Bu sorgular, bir DBA\u2019n\u0131n ara\u00e7 setinin temelini olu\u015fturur ve genellikle s\u00fcrekli denetim i\u00e7in otomatikle\u015ftirilir veya izleme ara\u00e7lar\u0131na entegre edilir.<\/p>","excerpt":"Veritaban\u0131 Y\u00f6neticileri (DBAlar), genellikle i\u015f g\u00fcnlerine veya sorun giderme oturumlar\u0131na ba\u015flarken, veritaban\u0131n\u0131n sa\u011fl\u0131\u011f\u0131, performans\u0131 ve durumu hakk\u0131nda h\u0131zl\u0131 bir genel bak\u0131\u015f elde etmek i\u00e7in belirli sorgular \u00e7al\u0131\u015ft\u0131r\u0131rlar. Buna sa\u011fl\u0131k kontrol\u00fc veya g\u00fcnl\u00fck rutin denir. Bu sorgular, potansiyel sorunlar\u0131 belirlemelerine, sistem kaynaklar\u0131n\u0131 izlemelerine ve her \u015feyin sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmalar\u0131na yard\u0131mc\u0131 olur. \u0130\u015fte DBAlar\u0131n her \u015feyden \u00f6nce \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131 \u00fc\u00e7 temel sorgu ve bunlar\u0131n neden kritik oldu\u011funa dair a\u00e7\u0131klamalar:","created_at":"2025-01-13 14:17:40","updated_at":"2026-09-07 12:57:00","category_id":6,"view_count":599,"reading_time":5,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2025-01-13 14:17:40","featured_image":"resimyok.jpg","slug":"veritabani-yoneticilerinin-ilk-sorguladigi-seyler","category_name":"Sistem","category_slug":"sistem","category_color":"#3b82f6"}