Oracle Manager: Oracle Database DBA work on Unix and Linux

Oracle Manager carries out Oracle Database DBA work on Unix and Linux: instances that are down, connection problems, storage running out, archived logs and backups.

REQUEST DEMO

READ THE DOCS

When an Oracle Database on a Unix or Linux server is down, refusing connections or out of space, 2501's Oracle Manager specialty investigates it the way a DBA would and fixes what you allow it to.

An Oracle alert at night usually comes down to a handful of causes: the instance is not open, clients cannot connect, the database has run out of storage space, or archived logs have filled their disk and the database can no longer accept changes. Someone has to work out which before anything can safely change.

What 2501 does

The Oracle specialty takes these requests from your ticketing system and covers maintenance, troubleshooting and optimisation. It investigates the instance, client connections, database storage and disk usage, memory and disk load on the host, and the database's error log. It carries out routine DBA work: starting and stopping the database, taking backups, clearing archived logs, and exporting or importing data. It confirms the database is healthy after every change and reports what it changed, and why.

Scope map of 2501's Oracle Manager: it starts and stops the instance, clears archived logs in step with your backup records, takes backups and runs exports and imports, and reads client connections, the error log, database storage and the host's memory and disk; it never drops databases, schemas or storage areas and never reboots the server.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Destructive work is off the table: the specialty does not drop databases, schemas or storage areas, and it does not reboot the server.
The host account is the hard limit: a dedicated user allowed only the commands its job needs, and destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do, including fully air-gapped on-prem networks.

Frequently asked

Can it clear archived logs when their disk fills up? Yes, where you allow it. They are cleared in step with your backup records, not deleted behind their back.

Will it force a shutdown? Only as a last resort. It shuts the database down cleanly, and forces it only when nothing else will recover the instance.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

A disk filled by Oracle archived logs, with the database no longer accepting changes, gets space back after 2501 clears the logs in step with the backup records and checks the database is healthy

Problem

Oracle archived logs filling the disk

Deleting archived logs by hand frees the disk and leaves Oracle's backup records out of step. How 2501 clears them in step with those records, within limits you set.

See how it is handled

Oracle Manager: Oracle Database DBA work on Unix and Linux

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE