GHOST BACKUP JOB!
Weird issue with our SAP Oracle 11.2.0.3. I refreshed our “DES” (destination) database with “SOU” (source) database. So “DES” is now a copy of “SOU”. I found in a backup log on the "DES" server showing that an attempt was made to backup “SOU” database but failed because it could not find “SOU” database. This is correct because “DES” database is the only one on the destination server. I checked the scheduler for Oracle and SAP on the "DES" environment and there is nothing scheduled for backups on the "DES" database but it continues to run the backup schedule as it was on the “SOU” database, as it was before the backup occurred. I hope I have not lost anyone. What is initiating the backup schedule from the “SOU” source environment to run on the newly refreshed “DES” destination environment?
LOG FILE:
BR0051I BRBACKUP 7.20 (27)
BR0055I Start of database backup: benaires.and 2014-01-20 22.00.14
BR0484I BRBACKUP log file: /oracle/DES/sapbackup/benaires.and
BR0613I Database instance SOU is shut down
BR0280I BRBACKUP time stamp: 2014-01-20 22.00.15
BR0304I Starting and opening database instance SOU ...
BR0278E Command output of '/oracle/DES/112_64/bin/sqlplus /nolog < /oracle/DES/sapbackup/.benaires.spi':
SQL*Plus: Release 11.2.0.3.0 Production on Mon Jan 20 22:00:15 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL>
SQL> SQL> SQL> SQL> ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/DES/112_64/dbs/initSOU.ora'
SQL> Disconnected
BR0280I BRBACKUP time stamp: 2014-01-20 22.00.15
BR0279E Return code from '/oracle/DES/112_64/bin/sqlplus /nolog < /oracle/DES/sapbackup/.benaires.spi': 0
BR0302E SQLPLUS call for database instance SOU failed
BR0306E Start and open of database instance SOU failed
BR0056I End of database backup: benaires.and 2014-01-20 22.00.15
BR0280I BRBACKUP time stamp: 2014-01-20 22.00.15
BR0054I BRBACKUP terminated with errors
NOTE: Of course it does not find the initSOU.ora because it is not on the destination server.