Friday, April 24, 2015

ORA-17628: Oracle error 19505 returned by remote Oracle server


RMAN error

released channel: t1
released channel: t2
released channel: t3
released channel: t4
released channel: t5
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/01/2015 09:19:11
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on t1 channel at 03/01/2015 09:19:11
ORA-17628: Oracle error 19505 returned by remote Oracle server



CAUSE

1. Shortage of space in the destination directory which will be accompanied by alertlog enter similar to the following:

ORA-19505: failed to identify file "+data"
ORA-17502: ksfdcre:4 Failed to create file +data
ORA-15041: diskgroup "DATA" space exhausted

Solution

Check the destination directory for data and archive files specified by DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST parameters respectively. Then make space in the specified diskgroup as manifested in the alert log ifle as exhausted,either by adding disks to it or deleting unwanted files from it.


2.Missing destination directory for DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST

Solution

Specify appropriate valid destinations for DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST to match with DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT.

Remember sometimes this error requires us to create destinations manually

for instance:
mkidr ARCHIVELOG/ CONTROLFILE/ DATAFILE/ ONLINELOG/ PARAMETER/ TEMPFILE

Thursday, April 16, 2015

ORA-1652: unable to extend temp segment by 128 in tablespace TEMP

Reference Note 748251.1

Possible Cause 

ISSUE IS LIKELY CAUSED BY 
Bug 5689290 - VIEW V$RMAN_BACKUP_JOB_DETAILS SLOW CAUSING DATABASE CONSOLE LOGIN TIMEOUTS
which identified an issue with excessive temp space usage by emagent.

Bug 5689290 was closed as a duplicate of
Bug 5466436 - VIEW V$RMAN_BACKUP_JOB_DETAILS SLOW CAUSING DATABASE CONSOLE LOGIN TIMEOUTS
which was subsequently closed as a duplicate of:
Bug 8434467 - SLOW PERFORMANCE FOR QUERY ON V$RMAN_BACKUP_JOB_DETAILS

Solution

1.  Upgrade to any fixed version, e.g.
12.1 (Future Release)
11.2.0.2 (Server Patch Set)
11.2.0.1 Patch 4 on Windows Platforms
11.1.0.7 Patch 37 on Windows Platforms
10.2.0.5 Patch 4 on Windows Platforms
10.2.0.4 Patch 41 on Windows Platforms
- OR -

2. Apply Patch 8434467 as available for the your actual platform and Oracle version.
- OR -

3. Use the following workaround to reduce the temp usage by emagent / dbsnmp:
exec dbms_stats.DELETE_TABLE_STATS('SYS','X$KCCRSR'); ==> deletes the statistics on the fixed object
exec dbms_stats.LOCK_TABLE_STATS('SYS','X$KCCRSR'); ==> lock that object so that statistics will not be collected in future
alter system flush shared_pool;  ==> cannot be skipped