Last updated: 2026-04-05

Package Explorer

The Package Explorer (Oracle only) gives you a single, searchable list of every PL/SQL package across all schemas within the database you selected when you opened the tab, so you can find and open packages without drilling through the Object Explorer tree. Each Package Explorer tab is bound to one connection and one database — the same scoping rule used by Table Explorer. Switch databases by opening another Package Explorer tab.

Opening Package Explorer

  1. Connect to an Oracle database.
  2. Click More in the main toolbar.
  3. Choose Package Explorer from the menu.

A new tab opens titled Package Explorer — database. The left panel lists every package visible to the current user, sorted by schema with the schema name shown beneath each package name.

Searching

Type any part of a package name — or schema.name — into the search box at the top of the left panel. The list narrows as you type. Press Esc or click the × button to clear the query and restore the full list.

Future improvements

The Package Explorer is being built in stages. Planned additions include:

  • Selecting a package to view and edit its source in an embedded PL/SQL editor.
  • Pinning favorite packages to the top of the list.
  • Red-dot indicators for packages in an invalid compile state.
  • Refresh button and right-click context menu with the standard Oracle package actions.

Frequently asked questions

What databases does the Package Explorer support?

Package Explorer is an Oracle-only feature. It is available whenever you are connected to an Oracle database.

How do I open the Package Explorer?

Connect to an Oracle database, then click More in the main toolbar and choose Package Explorer from the menu.

Can I search across schemas in the Package Explorer?

Yes — within the database the Package Explorer tab is bound to. Type a partial name into the search box to filter all packages across every schema in that database. You can also type schema.name to match both parts at once. Each Package Explorer tab is scoped to one connection and one database, the same way Table Explorer is.