0% found this document useful (0 votes)
3 views6 pages

Senior Oracle DBA Interview Prep Final

The document is a comprehensive guide for preparing for a Senior Oracle DBA interview, covering essential topics such as Oracle architecture, point-in-time recovery, performance bottlenecks, database security, and Data Guard configuration. It includes practical scenarios and troubleshooting techniques for common issues like high CPU usage, data corruption, and locking problems. Additionally, it outlines best practices for database management, patching strategies, and disaster recovery planning.

Uploaded by

Prakash A
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views6 pages

Senior Oracle DBA Interview Prep Final

The document is a comprehensive guide for preparing for a Senior Oracle DBA interview, covering essential topics such as Oracle architecture, point-in-time recovery, performance bottlenecks, database security, and Data Guard configuration. It includes practical scenarios and troubleshooting techniques for common issues like high CPU usage, data corruption, and locking problems. Additionally, it outlines best practices for database management, patching strategies, and disaster recovery planning.

Uploaded by

Prakash A
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Senior Oracle DBA Interview Prep Guide

Explain the Oracle architecture. How does the instance and database interact?
Oracle architecture consists of an Instance (memory + background processes) and a
Database (physical files). The instance includes the SGA (System Global Area) and
background processes like DBWn, LGWR, CKPT, etc. The instance manages access to the
database, which is made up of control files, datafiles, and redo logs. In Oracle 19c/21c,
Multitenant Architecture (CDB/PDB) is common, where the CDB contains shared
components, and each PDB behaves like a self-contained database.

How do you perform point-in-time recovery (PITR)?


Using RMAN:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
RUN {
SET UNTIL TIME '2025-04-01 09:00:00';
RESTORE DATABASE;
RECOVER DATABASE;
}
ALTER DATABASE OPEN RESETLOGS;
In 19c, PITR is supported at the pluggable database (PDB) level.

How do you identify and resolve performance bottlenecks?


Use AWR, ASH reports, and views like v$active_session_history, v$sql_monitor. Analyze
execution plans using DBMS_XPLAN.DISPLAY_CURSOR. Tune by gathering fresh stats,
creating indexes, or using SQL Profiles/SPM. 19c/21c tools like Automatic Indexing and
Real-Time Stats can help.

What are your best practices for database security?


Apply least privilege using roles and profiles, enable Transparent Data Encryption (TDE),
configure Unified Auditing, use wallets for key management, apply regular patching, and
implement Oracle Data Redaction or Database Vault as needed.

How do you configure Oracle Data Guard?


Enable FORCE LOGGING, configure standby redo logs and listener entries, use RMAN
DUPLICATE FOR STANDBY, and set log_archive_dest parameters. Use DGMGRL for Data
Guard Broker configuration. 19c/21c offer real-time cascading and automatic gap
resolution.
How do you patch an Oracle database with minimal downtime?
Apply patches on test first. Use opatch or opatchauto for GI/RAC. Use datapatch post-
patching. For RAC, use rolling patch mode. 19c/21c support Fleet Patching and Zero
Downtime Patching.

How do you perform database cloning using RMAN?


Use: RMAN> DUPLICATE TARGET DATABASE TO clone FROM ACTIVE DATABASE
NOFILENAMECHECK;
In 19c+, you can also clone pluggable databases (PDBs) for faster provisioning.

A query is suddenly running slow. How do you troubleshoot?


Check SQL_ID, execution plan, compare with historical (AWR). Use bind peeking analysis,
statistics, indexes, or SQL plan management. Consider environmental/system resource
checks.

What are key improvements in Oracle 19c/21c that you've worked with?
Automatic Indexing, Read-only Oracle Home, PDB-level recovery, Real-Time Stats,
Blockchain/Immutable Tables (21c), and improved Data Guard management.

How do you handle a hung production database?


Connect via sqlplus / as sysdba, use v$session, v$process, and system event views. Generate
system state dump if needed. Kill blocking sessions or restart DB if necessary. Analyze alert
and trace logs post-incident.
Real-World Scenario Q&A (Advanced)

Redo logs are filling up quickly. What could be the cause and solution?
Possible causes include high DML activity, insufficient log size, or missing archiving
configuration. Check v$log, v$log_history, and ARCH process. Increase log size, enable
ARCH, and ensure LGWR isn’t bottlenecked. Consider switching to faster storage or
increasing redo log groups.

Archive log destination is full. How do you resolve it without downtime?


1. Move old archive logs to another location.
2. Use RMAN to backup and delete logs:
RMAN> BACKUP ARCHIVELOG ALL DELETE INPUT;
3. Add another archive destination temporarily using LOG_ARCHIVE_DEST_n.
4. Ensure FRA isn’t full if using it.

User reports ORA-01555: Snapshot Too Old. What’s your approach?


This is typically caused by insufficient undo retention. Increase UNDO_RETENTION
parameter, size the undo tablespace appropriately, and check for long-running queries.
Consider enabling RETENTION GUARANTEE if needed.

You need to migrate a large production database with near-zero downtime.


What’s your approach?
Use Oracle GoldenGate for real-time replication. Set up a new environment, initiate
GoldenGate to sync changes, perform switchover during a short cutover window. Validate
data consistency before finalizing.

You see contention on TEMP tablespace. What’s causing it and how do you fix
it?
Common causes: large sorts, hash joins, bad execution plans. Monitor v$tempseg_usage and
v$sql_workarea. Increase TEMP size, enable autoextend, or tune the queries. Consider using
PGA_AGGREGATE_LIMIT to avoid excessive spilling to disk.

Application is locking tables and causing blocking. How do you identify and
resolve it?
Use:
SELECT * FROM v$session WHERE blocking_session IS NOT NULL;
Check v$lock for lock types. Kill offending session if needed. Review application logic to
reduce row-level locking or apply proper indexes.
Sudden spike in CPU usage by Oracle. What’s your response?
Check v$session for high CPU consumers, analyze SQL_IDs. Use AWR/ASH to identify top
SQLs. If necessary, kill runaway sessions. Investigate plan changes, missing stats, or system
overload. Tune SQLs or increase system resources.

You need to enforce encryption for sensitive columns. How do you proceed?
Use Transparent Data Encryption (TDE) for tablespaces or column-level encryption. Set up
Oracle Wallet. Example:
ALTER TABLE employees MODIFY (ssn ENCRYPT USING 'AES256');

You suspect data corruption. What do you do?


Run DBVERIFY on datafiles, use RMAN VALIDATE. Check alert logs for ORA-01578 or ORA-
01110. If corruption found, restore from backup or use block media recovery. Verify storage
subsystem for root cause.

Developers request a copy of production for testing. How do you safely provide
it?
Mask sensitive data using Oracle Data Masking, then clone using RMAN or PDB cloning.
Alternatively, use Data Pump export/import with remap and masking procedures. Always
test clone to ensure no real data leaks.
Tough Oracle DBA Interview Questions

How do you handle ORA-600 and ORA-7445 errors in production?


These are internal errors indicating a bug or memory corruption. Steps:
1. Check alert log and trace files.
2. Use the error arguments to search Oracle Support (MOS).
3. Gather system state dump if needed.
4. Open SR with Oracle, upload logs and diagnostic data.
5. Apply patches or workarounds if advised.

How do you diagnose a performance degradation that occurred two weeks


ago?
Use AWR snapshots stored in dba_hist views or use awr reports:
1. Compare AWR reports before and after the issue.
2. Use dba_hist_sqlstat to track SQL performance history.
3. Identify changes in plans, object stats, or load patterns.
4. Investigate changes in indexes, execution paths, or CPU usage.

Explain the steps to recover from a lost datafile in ARCHIVELOG mode with no
recent backup.
1. Check if the datafile is critical.
2. Try to recover with available archived logs:
STARTUP MOUNT;
RMAN> RESTORE DATAFILE <n>;
RMAN> RECOVER DATAFILE <n>;
ALTER DATABASE OPEN;
3. If no backup, recreate tablespace if non-critical or restore full DB to another server and
extract missing data.

What’s the difference between SCN, checkpoint, and redo log sequence?
SCN (System Change Number) tracks database changes.
Checkpoint marks a synchronization point between memory and disk.
Redo log sequence numbers identify the chronological order of redo logs. They're related
but serve different purposes in recovery.

How do you analyze and fix latch contention?


1. Use AWR/ASH to identify high latch waits.
2. Use v$latch, v$latch_children, and v$latch_misses.
3. Identify root cause: poor SQL, shared pool issues, buffer contention.
4. Solutions: tune SQL, increase spin_count (rare), resize shared pool, or patch if bug-
related.
How do you manage Oracle patches across a large fleet of databases?
1. Maintain inventory using Oracle Enterprise Manager (OEM) or scripts.
2. Group DBs by version/platform.
3. Use Fleet Maintenance for patch rollout.
4. Automate pre-checks, patching, and post-validation using Ansible/Shell.
5. Maintain rollback plans and test in staging first.

Explain how you would upgrade a RAC environment from 12c to 19c.
1. Review Oracle documentation and certification matrix.
2. Backup GI and DB.
3. Upgrade GI first using runInstaller.
4. Upgrade database using DBUA or manually (preupgrade.jar, datapatch).
5. Handle post-upgrade tasks (stats, timezone).
6. Validate RAC services, listeners, and CRS status.

Describe how Oracle handles concurrency and consistency with read


consistency.
Oracle uses undo segments to maintain read consistency. A query sees data as it was at the
time it started. Changes by other sessions are hidden until committed. Undo provides the
consistent snapshot for multi-version concurrency control.

How would you design a DR strategy for a 50TB Oracle database?


Use Oracle Data Guard for near real-time DR. Use Fast Sync with Maximum Performance
mode. If RTO/RPO is critical, combine with Oracle ZDLRA or storage-level replication.
Periodic tests, monitoring, and bandwidth planning are essential.

How do you troubleshoot a slow RMAN backup?


1. Check I/O throughput, bottlenecks in disk/network.
2. Use RMAN views (v$rman_backup_job_details).
3. Enable backup compression or parallelism.
4. Check CPU and memory on backup server.
5. If backing up to NFS, review mount options and throughput.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy