Why should you care?

Production outages and slow systems are diagnosed with putty & winscp setup knowledge — not guesswork.

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.

-- Putty & WinSCP Setup — DBA style check (privileges required)
SELECT name, open_mode FROM v$database;
SELECT instance_name, status FROM v$instance;

-- Common dictionary peek
SELECT table_name FROM user_tables ORDER BY table_name FETCH FIRST 10 ROWS ONLY;

What happened?

• v$database / v$instance confirm the DB is open.
• user_tables lists objects you own — a gentle way to explore without changing anything.

Practice next

1. Connect to your lab as a user with the needed privileges.
2. Run the read-only checks first.
3. Write the definition of this topic in your own words.
4. Change one literal in the example and re-run.
5. Write a second example from memory without looking.

Remember

You can explain Putty & WinSCP Setup in plain English. You ran at least one related command or query. You know one real system where it matters.

Putty & WinSCP Setup on a banking PDB

On-call DBA reviews putty & winscp setup during a health check before peak traffic.

Outcome: You know which view/command to open first.