Why should you care?

When a DBA says “instance is down”, the processes/memory stopped. When “database is corrupted”, files on disk are the problem. You need both words correctly in production calls.

See it live — copy this example

Run these statements in SQL Developer or SQL*Plus against your lab PDB. Prefer a practice user — not SYS — for application SQL.

-- Instance vs database (run as SYS or DBA)
SELECT instance_name, status, database_status FROM v$instance;
SELECT name, open_mode, database_role FROM v$database;

What happened?

• v$instance shows the running instance status.
• v$database shows the database name and open mode (READ WRITE, MOUNTED, etc.).

Practice next

1. Connect as SYS AS SYSDBA in the lab.
2. Query v$instance and note STATUS.
3. Query v$database and note OPEN_MODE.
4. Add SELECT startup_time FROM v$instance;
5. Compare OPEN_MODE before and after a shutdown/startup lab.

Remember

Instance = SGA + background processes. Database = files on disk. Both must be healthy for apps to work.

Nightly restart confusion

Ops restarts the server. Apps fail until the Oracle instance starts and opens the database.

Outcome: You check v$instance and v$database first, not random SQL.