Backup Failure using OEM

Backup Failure using OEM
I have oracle 9i (windows 2000 server)
I tried to make a fullbackup using OEM, it gives me NO error messages
I got result file with 890 MB (my Db is not huge),
but when I go back to the JOBs in OEM I found the status of the job FAILED
I tried to do the same thing using incremental backup level 0, but I got the same result
any Idea why the job didn't complete successfully
thanx in advance

Use command line -> rman .

Similar Messages

Backup Failure using OEM (Oracle 9i)

Backup Failure using OEM
I have oracle 9i (windows 2000 server)
I tried to make a fullbackup using OEM, it gives me NO error messages
I got result file with 890 MB (my Db is not huge),
but when I go back to the JOBs in OEM I found the status of the job FAILED
I tried to do the same thing using incremental backup level 0, but I got the same result
any Idea why the job didn't complete successfully
thanx in advance

Here is the deal.
I need to be able to work in the OEM for my class. (Oracle DBA in Training) It is a significant part of my grade to be able to find the required help through forums like these to help me get the backup/recovery process to work through the OEM. My books deal with the OEM in a Win2000 Pro/Server environment, and don't take into consideration the variances in XP Pro. My install works great, other than I am receiving a "Fail" on my OEM Backups under Jobs. It further explains that I do not have the proper permissions to perform the backup job that was created. My instructor is completely hands off when it comes to help. So if anyone has run into this problem and been successful in fixing the problem without using a different utility. Please let me know.
Thanks in advance,
Vic

RMAN backup fails using OEM with no output error

I am trying to do a weekly automatic full backup of a database in noarchivelog mode using RMAN in Enterprise Manager. Every time I submit the backup job (even if I try to do an immediate backup) the job fails almost immediately. When I Iook at the job output for the failed attempt, it says that there is no output for the job. I believe I have all of the preferred credentials and priveleges correct. Does anyone have any ideas as to what the problem could be or maybe where I can find an error log for rman to get a better explanation of the error?
Thanks

please check in metalink.....
you find useful informations here:
RMAN backup using Oracle Secure Backup fails with ORA-19511 (sbt__rpc_connect)
Doc ID: Note:396046.1
Best Regards,
Shishir Tekade.
My Blog: http://shishirtekade.blogspot.com

Backup & Recovery through OEM

HI,
I have Oracle 10g Application Server installed on Windows server 2003, with infra and portal on two different nodes...i need to setup a backup strategy using OEM for the infra database..i already put my database in Archivelog mode and scheduled a RMAN backup through OEM at Flash Recovery Area..
Please suggest , what all precautions i need to take to preserve this backup and what steps i need to follow in case i need to recover my database ( Manually or using OEM ).
I appreciate ur answer in detail..
regards,
Sajad.

I need suggestions ..please..
thanks.

Using OEM to backup/restore DB using EMC Avamar (3rd party)

Hi,
I'm trying to find a solution for using OEM to backup and restore DB using EMC Avamar software.
Normally, we can backup/restore DB using Avamar through RMAN CLI using scripts similar to the following:
connect target /
run {
configure controlfile autobackup on;
set controlfile autobackup format for device type sbt to 'CONTROLFILE.orcl.%F';
allocate channel c0 type sbt PARMS="SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll" format '%d_%U';
send '"--prefix=11g/orcl/" "--flagfile=c:\flagfile\avtar-flags.txt" "--bindir=c:\PROGRA~1\avs\bin"';
backup database plus archivelog delete input;
release channel c0;
Where orasbt64.dll is the name of Avamar's 64bit library and flagfile contains some internal flags necessary for backup/restore operations.
Now, I want to use OEM for the same thing so, what I did was try to specify the Media Management Vendor Library Parameters under Backup Settings in OEM. I saved the following as the parameters:
"SBT_LIBRARY=c:\PROGRA~1\avs\bin\orasbt64.dll";
Even after this, the backup script generated by OEM does not contain this parameter. Naturally, backups to EMC Avamar fail.
I would like answers to these 2 questions:
1. How to correctly specify the Media Management Vendor Library Parameters?
2. Is there a way to specify all the parameters (--prefix, flagfile, bindir, PARMS etc.) so that the script generated by OEM is same (or as close as possible) to the one I use for RMAN CLI backups.
Thanks!

Hi Anant,
I'm also having the same issue. It fails because it doesn't understand the "send" command in OEM. Here is the output of the tape backup test:
RMAN> run {
2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
3> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
4> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
5> backup as COMPRESSED BACKUPSET current controlfile tag '04302012033156';
6> restore controlfile validate from tag '04302012033156';
7> release channel oem_sbt_backup;
8> }
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on oem_sbt_backup channel at 04/30/2012 15:32:00
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
RMAN> allocate channel for maintenance type 'sbt_tape' parms 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,
2> ENV=(PATH=/bin:/usr/bin:/usr/local/avamar/bin);
3> send "--flagfile=/home/oracle/scripts/backup/my-avtar-flags.txt"';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 04/30/2012 15:32:01
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
When I use TSM it doesn't require the "send" command and it backs up successfully. I guess the other option would be to create an EM job to do the backups. However, this wouldn't populate the EM tables for backup reporting.

Anyone using OEM for scheduling backups?

I'd like to see a poll for the number of users using OEM for taking database backups. Had some interesting conversations with some colleagues via social media and it seems like some DBAs don't trust OEM for their backups even though the feature works IMO.
Are you using OEM to do backups?
Edited by: DBA on May 3, 2012 1:02 PM

I have 91 scheduled recurring backup jobs running through OEM 12c BP1. They work quite well. I've only noticed a few problems and nitpicks:
1) Occasionally, for unknown reasons, a backup job against a newly-added database target will fail stating that the backup cannot be run since the database is closed. The database is not closed, it's up and running fine. Changing the backup job to run using SYS as SYSDBA credentials resolves this problem.
2) Identification of failed backups is not as customizable as I would like. For example, if I have a full "backup database plus archivelog" running, and during the course of that backup an archivelog backup runs and deletes archived logs, OEM will report that the backup job has failed since RMAN throws an error about not being able to backup an archivelog it expected to find. I dealt with this by adding SKIP INACCESSIBLE to the backup statement. I'm not totally comfortable about that but I monitor for offline datafiles so I consider this only a minimal risk. Our custom backup scripts used to catch this warning and ignore it.
3) It's really annoying that, after creating a backup job through the target Availability -> Schedule Backup tool, I cannot then run a 'Create Like' against that backup job to create a nearly identical one against a different database target. You have to schedule each of them from the Schedule Backup tool. Clicky clicky clicky clicky.
4) A backup job created through the 'Schedule Backup' tool has a job type of 'Database Backup', therefore when the job fails a high-availability incident is created, so you can configure incident rules to receive notification of this event. This is good. Unfortunately a backup job created from the Jobs page has a job type of 'RMAN Script' does NOT create an incident on job failure out of the box. I've had difficulty configuring incident rules to catch failures for RMAN Script job types. This is not good.
5) The repeating schedule options for jobs are limited compared even to something like cron. I can schedule a job for a day of the week, or a day of the month, but cannot easily schedule a job for "the first Tuesday of each month". This can be worked around.
6) After creating and submitting a backup job through the Schedule Backup tool, you cannot edit the RMAN script without recreating the job. You can only edit the RMAN script before submitting the job. I deal with this by having my backups run stored scripts in the recovery catalog, and make the changes there if I need to change something.
7) It is very annoying that if I 'stop' a repeating job (instead of suspend), there is no way to resume that job. It has to be recreated. This is my own user error -- I just don't click the stop button. Not OEM's fault but I'd rather not even have that button.
8) No ability to sequence jobs. You can sequence steps within a job, but then the entire job succeeds or fails as a unit. If you want to back up database A then immediately back up database B afterwards, you have to create a multi-task job. The multi-task job has the same problem as item #4 above such that it does not create a "backup failed" incident when the backup fails.
Even with all of these gripes, I am quite pleased with the backups I have running through OEM.

PC Suite 6.86.9.0 Backup Failure

PC Suite 6.86.9.0 Backup Failure
When backing up the messages on my N80(firmware v5.0719.0.2) the backup always fails when processing multimedia messages and windows reports "Windows Driver Foundation - User-mode Driver Framework Host Process" (WUDFHost.exe) has failed. All other parts of the backup work successfully.
What version of Windows is being used? Vista
What Service Pack is installed? SP1
What version of PC Suite is installed? 6.86.9.0
What is the connection method, cable, bluetooth or IR? usb cable
Does anyone know how to correct this issue ?

13-Apr-2008 12:16 PM
chris9 wrote:
PC Suite 6.86.9.0 Backup Failure
When backing up the messages on my N80(firmware v5.0719.0.2) the backup always fails when processing multimedia messages and windows reports "Windows Driver Foundation - User-mode Driver Framework Host Process" (WUDFHost.exe) has failed. All other parts of the backup work successfully.
What version of Windows is being used? Vista
What Service Pack is installed? SP1
What version of PC Suite is installed? 6.86.9.0
What is the connection method, cable, bluetooth or IR? usb cable
Does anyone know how to correct this issue ?
plz can u post the Screenshot of error?
i m not having this type of problem, Backup is working Fine for Me.
Nokia 5530 Xpress Music RM-504
v30.0.009
31-5-10

Time Machine backup failure on case-sensitive disk?

Hello,
I just started getting a Time Machine backup failure error that says "A disk you are backing up is case-sensitive, but the backup disk is not."
None of my external disks have changed and I've not added any new ones.
The error seems to be stemming from the fact that I'm logged in as multiple users on my system, all with MobileMe accounts. When I "get info" on all mounted disks, the only ones that are reporting "Mac OS Extended (Case-sensitive, Journaled)" are the mounted iDisks from the other use accounts that I'm currently logged in as.
Does this mean I cannot use Time Machine while logged in as multiple users, all with the iDisks mounted? That would be a major annoyance to either have to log out/log in to each user as I need them or to disable iDisk syncing in my MobileMe prefs.
Regards,
Terry

That seems odd to me; my iDisk shows WebDAV as the format and doesn't interfere with backups, but I don't have any other users' iDisks, either.
Another possibility would be to reformat your TM drive as case-sensitive. That would, of course, erase all your backups so TM would start over from scratch, and some possible troubles when restoring (see the pink box in #5 of the Frequently Asked Questions *User Tip,* also at the top of this forum, for details); but you'd no longer have the backup problem.

Rediscover using OEM in Oracle 10.2.0.4

Hi,
Can somebody post detailed steps as to how to rediscover using OEM. (I have performed at the session level)
My system is Oracle 10.2.0.4 RAC on RHEL.
Example: Steps to rediscover an instance (or) agent (or) listener using OEM.
To put it in simple terms...mys listener is showing DOWN status in OEM, but is actually UP when I go in and check at the session level.
I do not want to restart the agent at the sesion level which I have already done. Kindly help.
Edited by: Redstorm on Feb 24, 2009 7:09 PM

Do you have a lot of jobs scheduled via OEM ? (you can save the definitions in the job library and re-submit them later if not. You may also have to reset the backup preferences etc.)
This seems strange. Is there an error message with the listener status (click on the Down targets from the homepage.)
Also can you provide the output from the agent status.
cheers,
graham
Edited by: Graham_R on Feb 24, 2009 5:12 PM

Trying to register 10.2.0.3 db in Rec Catalog using OEM, getting errors

Hi all,
I didn't know whether to post this here in the RMAN forum or in the OEM Grid Control forum, but the issue is more related to RMAN, so I'll post it here, and hope someone can help me out!
I have a new 10.2.0.3 database that I am getting configured to manage using OEM Grid Control. Through the OEM interface, I am trying to register this database with my recovery catalog - the recovery catalog is version 10.02.00.02. When I try to register this new db with the recovery catalog, I am getting this lengthy collection of errors:
Recovery Manager: Release 10.2.0.3.0 - Production on Wed Jan 30 14:58:36 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved. RMAN> connected to target database: INSIGHT (DBID=4016731035) RMAN> connected to recovery catalog database PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.02 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 10.02.00.02 in RCVCAT database is not current RMAN> echo set on RMAN> register database; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of register command at 01/30/2008 14:58:40 RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 2453: PLS-00302: component 'RESTORECMD_T' must be declared ORA-06550: line 1, column 2424: PL/SQL: Statement ignored RMAN> exit; Recovery Manager complete.
It sounds like it has something to do with the fact that my recovery catalog database is not at a current version?? In the OEM tool, I went to the page that lists the Recovery Catalog, and tried hitting the Update button, and it succeeded, but the Recovery Catalog version did not change, it is still at 10.02.00.02.
Can anyone give me some assistance on this one?
Thanks!
--Brad

Hi,
please check with
select comp_name,status,version from dba_registry;
COMP_NAME
STATUS VERSION
Oracle Database Catalog Views
VALID 10.2.0.3.0
Oracle Database Packages and Types
UPGRADED 10.2.0.3.0
The UPGRADED status is not good. Run utlrp.sql again and then again as rman user the "upgrade catalog". Now it should work fine.
Bye
Matthias

Windows SBS 2011 Standard - Windows Image Backup Failure VSS Erros

Hello,
I was wondering if someone could point me in the right direction regarding a SBS backup failure on 2011. It seems i'm currently getting the typical
"Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.
Operation:
Gather writers' status
Executing Asynchronous Operation
Context:
Current State: GatherWriterStatus
Error-specific details:
Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist."
But i have gone through many different pages regard's to fix's and nothing of the sort has resolved my issue yet. I get an error in the application logs informing me:
The backup operation that started at '‎' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and
then rerun the backup operation once the issue is resolved.
I have made the change in which to change the reg entry's for the spfarm and spsearch are set to "0" and added the vssregistrygroup group with entry of 1.
I have drawn up a list of VSSadmin List Writers and the system writer is showing the following.
Writer name: 'System Writer'
Writer ID: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance ID: {b3d9ec72-b1a7-4557-b3b5-dafe1f97b8f2}
State: [5] Waiting for completion
Last Error: No Error
I can see the SQL server writer is showing Failed and Non-retryable error? i have rebooted the server twice now after making changes but nothing seems to be working? anyone with any ideas? if you need more information then please let me know! kinda getting
stuck for ideas.
Regards
Mike

Thanks for the reply Justin
I have gone through our list and i can confirm the following.
did you install any third-party backup utility
on the SBS 2011? Or just use Windows Server Backup?
Its just windows server backup, not 3rd party backup software installed on the server.
Did you mean that set Data of spfarm and spsearch to
0 via following path?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
<Domain>\
spfarm = dword: 0x00000001(1)
<Domain>\
spsearch = dword: 0x00000001(1)
Yes this is correct the both have been set to "0" while <domain>\VSSRegistryGroup and NT Authority\NetworkService both have Dword value of "1"
Did you right click on VSSAccessControl, select “Permissions…”, then add backup account and give it Full Control? Meanwhile, please check if
Administrators group is owner of this key.
In response to this, i have Administrators as the owner of the folder, but when you mean "add backup account" which specific account are you referring to?
Did you set the Startup type as Automatic and restart the service? Any find?
Yep this service is set to Automatic but every time i try and start it, it comes up with:
the sharepoint 2010 vss writer service on local computer started and then stopped. Some services stop automatically
if they are not in use by other services or programs.
Any feedback would be great.
Thanks
Mike

Export backup failures:

We are getting export backup failures here is the export log:
Connected to: Oracle9i Release 9.2.0.5.0 - Production JServer Release 9.2.0.5.0 - Production Export done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set server uses WE8MSWIN1252 character set (possible charset conversion)
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions . exporting database links . exporting sequence numbers . exporting directory aliases . exporting context namespaces . exporting foreign function library names . exporting PUBLIC type synonyms
EXP-00008: ORACLE error 904 encountered
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier
EXP-00000: Export terminated unsuccessfully
PLease help me to get the export done.
Thanks
Niket

done these steps...
startup mount;
alter system set "_system_trig_enabled" = false scope=memory;
alter system enable restricted session;
alter database open;
@?/rdbms/admin/catnojav.sql
@?/xdk/admin/rmxml.sql
@?/javavm/install/rmjvm.sql
truncate table java$jvm$status;
SQL> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> /
SP2-0103: Nothing in SQL buffer to run.
SQL> alter system set "_system_trig_enabled" = false scope=memory
2 /
System altered.
SQL> alter system enable restricted session
2 /
System altered.
SQL> alter database open
2 /
alter database open
ERROR at line 1:
ORA-01531: a database already open by the instance
SQL> start E:\ORA924\rdbms\admin\catnojav.sql
SQL> Rem
SQL> Rem $Header: catnojav.sql 15-jul-2002.07:13:41 rburns Exp $
SQL> Rem
SQL> Rem catnojav.sql
SQL> Rem
SQL> Rem Copyright (c) 2002, Oracle Corporation. All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem catnojav.sql - CATalog NO JAVa classes for RDBMS
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem This script removes the RDBMS Java classes and system
SQL> Rem triggers created by the CATJAVA.SQL script.
SQL> Rem
SQL> Rem NOTES
SQL> Rem Must be run AS SYSDBA
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem rburns 07/15/02 - rburns_bug-2415848
SQL> Rem rburns 06/13/02 - Created
SQL> Rem
SQL>
SQL> Rem =====================================================================
SQL> Rem Check CATJAVA and JAVAVM status; conditionally abort the script
SQL> Rem =====================================================================
SQL>
SQL> WHENEVER SQLERROR EXIT;
SQL>
SQL> BEGIN
2 IF dbms_registry.status('CATJAVA') IS NULL THEN
3 RAISE_APPLICATION_ERROR(-20000,
4 'CATJAVA has not been loaded into the database.');
5 END IF;
6 IF dbms_registry.is_loaded('JAVAVM') != 1 THEN
7 RAISE_APPLICATION_ERROR(-20000,
8 'JServer is not operational in the database; ' ||
9 'JServer is required to remove CATJAVA from the database.');
10 END IF;
11 END;
12 /
BEGIN
got this error....

Backup failure, read only message

I've been using a time capsule for about 6 mo. Recently I have been getting a backup failure message from Time Machine, saying that the backup volume, my Time Capsule, is read only. I reset the Time Capsule settings and still am having problems. Does anyone know why I would get a "read only" message about the Time Capsule?

I'd run /Utilities/Disc Utility and re-format it yourself, it most likely came formatted for PC not Mac ...

Documents backup failure in commvault with error Cannot open file ReportViewer.dwp

Hi,
SharePoint Documents backup failure in commvault with error "Cannot open file ReportViewer.dwp" even all necessary permissions are available for all the sites , sql

Hi Praveen,
Whether you tried to backup the library using PowerShell exporting command.
Export sites, lists, or document libraries in SharePoint 2013:
http://technet.microsoft.com/en-us/library/ee428301(v=office.15).aspx
As the commvault is a third party tool and I am not familar with it, I suggest you ask the third party support or forum for help.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Regular backup failures.

hello all,
I am getting a backup failures every 14th calendar day of the backup schedule.
the error is..
BR278E Command output of 'dd bs=32k conv=sync if=D:\ORACLE\EP1\SAPDATA6\BTABD_1\BTABD.DATA1 of=/dev/nmt0':
dd: unable to initialize ASPI manager
dd: using NT tape support
17600+1 records in
17601+0 records out
dd: Data error (cyclic redundancy check).
BR280I Time stamp 2006-11-12 20.03.33
BR279E Return code from 'dd bs=32k conv=sync if=D:\ORACLE\EP1\SAPDATA6\BTABD_1\BTABD.DATA1 of=/dev/nmt0': 0
BR222E Copying D:\ORACLE\EP1\SAPDATA6\BTABD_1\BTABD.DATA1 to/from /dev/nmt0 failed due to previous errors
BR280I Time stamp 2006-11-12 20.03.38
BR317I 'Alter tablespace PSAPBTABD end backup' successful
BR056I End of database backup: bdtxujdy.ant 2006-11-12 20.03.33
BR280I Time stamp 2006-11-12 20.03.38
BR054I BRBACKUP terminated with errors
it happend today but will again go on error free for next 13 days and on 14th day it will again give the same error.
I think there is some problem in ASPI manger when it calls the device to be initialized.
kindly help in resolving this...
precise and good answers will be rewarded accordingly.
thanks
saurabh

Hi Saurabh,
You need to remove this tape and replace it with a new one, youre not going to be able to do a backup of the tape because the tape is gone, just remove the tape and replace it with a new tape with a new label (or the same one if its possible)
Hope this help!
Juan
Please reward with points if helpful

Backup Failure using OEM

Similar Messages

Maybe you are looking for