Category: Troubleshooting

An Oracle schema import can fail when object types are imported back into the same database under a different schema. The log commonly shows IMP-00017 together with ORA-02304: invalid object identifier literal, or the Data Pump wrapper error ORA-39083. Why it happens Oracle object types can have database-wide object identifiers (OIDs). By default, an export…

ORA-19511 is Oracle RMAN reporting an error returned by the media-management layer. When the accompanying NetBackup message is status 25: cannot connect on socket, troubleshoot the NetBackup connection rather than the Oracle database first. What status 25 means A NetBackup process timed out while connecting to another NetBackup process. Common causes include name-resolution errors, a…

ANS1017E (RC-50) Session rejected: TCP/IP connection failure is a client-side message used by IBM Tivoli Storage Manager, now IBM Storage Protect. It tells you the session could not be established or continued, but it does not by itself identify the cause. The server activity log at the same timestamp is usually the best place to…

During point-in-time recovery, RMAN can report ORA-01861: literal does not match format string when the value supplied to SET UNTIL TIME does not match the session’s date format. The reliable fix Use an explicit TO_DATE expression with a matching format mask. This makes the recovery script independent of the current NLS_DATE_FORMAT setting. In RMAN, the…

EXP-00003: no storage definition found for segment is raised by Oracle’s legacy Export utility when it cannot obtain the storage definition for a table, index, or cluster. On older releases, a common trigger was running an exp executable whose patch level did not match the source database. First checks Record the full export log, including…

This note refers to an old Oracle 10g issue in which very wide ANSI join queries could fail after internal query transformation. The reported threshold was roughly 1,050 projected columns, and some failures surfaced as ORA-01445. It should not be treated as a universal limit in current Oracle releases. Historical context The issue was associated…

On UNIX and Linux hosts with several Oracle instances, ipcs can show many shared-memory and semaphore resources without identifying the owning database clearly. Oracle’s sysresv utility maps System V IPC resources to an Oracle SID. Report resources for an instance To check one or more explicitly named instances: Run the command as the Oracle software…

When RMAN reports RMAN-10035, ORA-19502, and ORA-27030 during an SBT backup, the useful diagnosis is usually in the final media-manager message. The Oracle stack says the backup write failed; the vendor text says why. Read the error stack from the bottom ORA-19511 means the linked media-management software returned a failure. Treat the vendor message, backup-server…

Shared pool and large pool usage should be monitored as trends, not judged from a single “free memory” number. Oracle can use most of a pool efficiently, and a low free value does not by itself prove memory pressure. Summarize current allocations SELECT pool, name, ROUND(SUM(bytes) / 1024 / 1024, 1) AS mb FROM v$sgastat…

Monitor the volumes that contain SQL Server database files with sys.dm_os_volume_stats. It returns capacity information without enabling operating-system command execution. Free space for database volumes SELECT DISTINCT vs.volume_mount_point, vs.logical_volume_name, CAST(vs.total_bytes / 1073741824.0 AS decimal(18,2)) AS total_gb, CAST(vs.available_bytes / 1073741824.0 AS decimal(18,2)) AS free_gb, CAST(100.0 * vs.available_bytes / NULLIF(vs.total_bytes, 0) AS decimal(5,2)) AS free_percent FROM sys.master_files…