Export,backup using OEM

Dear friends,
What file sql file should be run for taking backup, export through oracle enterprise manager. I have configured everything and the script works from the command prompt but when run through OEM it shows vni - authentication error.
Please help the sql file that i should run at command prompt.

I came across this issue when testing 10.2 havent tried it recently and didnt exactly find and ans. How ever later found that for a proper install one need an OS account (i'm on win2003) which is in the in the administrators group, and logon as batch in local sec pol. I think there is one other sec group memebership. This is all iff the top of my head so not 100% on detail and havent got access to box right now to double check.
Look in the install guide should have this info. else i'll try post details on Mon when i'm got my notes.

Similar Messages

Date-wise backup using expdp

Dear Friends ,
I am using Oracle database 10g . Every week I take full export backup using 'expdp' . Beetween the days of the week, I dont take any backup . Now I need backup of two days ago . In this moment , is it possible to take backup using datapump (expdp) before two days ago ?
i.e., Is there any facility in oracle 10g datapump to take export backup using date-wise ?
My another question ,
Is there any incremental backup procedure available in oracle 10g datapump ?
Waiting for kind reply ... ...

Hi,
Dear Friends ,
I am using Oracle database 10g . Every week I take full export backup using 'expdp' . Beetween the days of the week, I dont take any backup . Now I need backup of two days ago . In this moment , is it possible to take backup using datapump (expdp) before two days ago ?
i.e., Is there any facility in oracle 10g datapump to take export backup using date-wise ?
My another question ,
Is there any incremental backup procedure available in oracle 10g datapump ?
Waiting for kind reply ... ...You must not use or treat Expdp or logical backup as the Backup which can be used for future purpose. Please search forums their are so many links you lan find out and so many people told many time.. even ORACLE suggest that.
Go for Custom backups and RMAn backups.
- Pavan Kumar N
- Pavan Kumar N

Export Backup Size is different

Hi Gurus,
We are using Oracle 10G (10.2.0.1.0) on Solaris 10 and we used to take export backup daily basis. While taking export backup using 'exp' then .dmp file size is becoming 30.3 GB where as when we use 'expdp' .dmp file size is 26.1 GB. I've checked both the log files and found no. of tables along with their records are same. so I'm confused why this size difference? and as a result we are not in a position to implement 'expdp'. Can anybody tell me why this size difference and whether can we rely on expdp or not?

user606947 wrote:
Hi Gurus,
We are using Oracle 10G (10.2.0.1.0) on Solaris 10 and we used to take export backup daily basis. While taking export backup using 'exp' then .dmp file size is becoming 30.3 GB where as when we use 'expdp' .dmp file size is 26.1 GB. I've checked both the log files and found no. of tables along with their records are same. so I'm confused why this size difference? and as a result we are not in a position to implement 'expdp'. Can anybody tell me why this size difference and whether can we rely on expdp or not?
Oracle recommends that you use the new Data Pump Export and Import utilities because they support all Oracle Database 10g features
Look at the following documentation:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_overview.htm#sthref14

Backup Or Export file is not created by using OEM

Hi All,
I'm facing a typical problem. When i will export/backup some table/database/tablespace by using ORACLE ENTERPRICE MANAGER ,export/backup is shown on job pain in OEM but the physical file will not exist on the showing path by OEM.
My Database version is 9.2.0.1 & it's running on Win XP2.
Please help me.
Regards
Subhradip

It has been a long time that I have seen 9i on windows, but if recall that right, you must additionally give the OS user the right "logon as batch job".

Error Using OEM to create export files

Hi
I get the following error whenever I try to use OEM to create export files (login to OS as oracle user -> http://localhost:1158/em -> login as SYSTEM -> Maintenance -> Export to Export Files (with oracle user as host credentials)
>>>
Validation Error
Examine and correct the following errors, then retry the operation:
Error - ERROR: NMO not setuid-root (Unix-only)
>>>
From what I've read in this forum and in others is that the problem is often related to the owner/group permissions associated with the bin/nmo and bin/nmb files. However I've tried the posted solutions by changing the owner/permissions as suggested, but this does not help. I get the same error regardless if the files are owned by oracle or by root.
Here is some more info
>>>
[root@rhlinux bin]# id oracle
uid=501(oracle) gid=502(dba) groups=502(dba)
[root@rhlinux bin]# ls -ld /app/
drwxr-xr-x 4 root root 4096 Jul 6 13:36 /app/
[root@rhlinux bin]# ls -ld /app/oracle/
drwxrwxr-x 5 oracle dba 4096 Jul 10 10:13 /app/oracle/
[root@rhlinux bin]# ls -ld /app/oracle/product/
drwxrwx--- 3 oracle dba 4096 Jul 6 16:04 /app/oracle/product/
[root@rhlinux bin]# ls -ld /app/oracle/product/v10.2.0/
drwxr-x--- 58 oracle dba 4096 Jul 11 15:31 /app/oracle/product/v10.2.0/
[root@rhlinux bin]# ls -ld /app/oracle/product/v10.2.0/bin/
drwxr-xr-x 2 oracle dba 8192 Jul 20 11:19 /app/oracle/product/v10.2.0/bin/
[root@rhlinux bin]# ll nm?
-rwxr-x--- 1 root dba 18462 Jul 6 16:16 nmb
-rwxr-x--- 1 root dba 19624 Jul 6 16:16 nmo
>>>
>>>
[oracle@rhlinux bin]$ uname -a
Linux rhlinux 2.6.9-34.0.2.EL #1 Fri Jun 30 10:23:19 EDT 2006 i686 i686 i386 GNU/Linux
>>>
>>>
[oracle@rhlinux bin]$ sqlplus system@dware
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jul 20 16:34:16 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
>>>
>>>
[oracle@rhlinux bin]$ emctl status agent
TZ set to Canada/Saskatchewan
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.4.1
OMS Version : 10.1.0.4.0
Protocol Version : 10.1.0.2.0
Agent Home : /app/oracle/product/v10.2.0/rhlinux.swlocal_DWARE
Agent binaries : /app/oracle/product/v10.2.0
Agent Process ID : 32098
Parent Process ID : 30792
Agent URL : http://rhlinux.swlocal:3938/emd/main
Started at : 2006-07-20 12:00:05
Started by user : oracle
Last Reload : 2006-07-20 12:00:05
Last successful upload : 2006-07-20 16:27:29
Total Megabytes of XML files uploaded so far : 1.54
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 47.83%
Agent is Running and Ready
>>>
>>>
[oracle@rhlinux bin]$ emctl status dbconsole
TZ set to Canada/Saskatchewan
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://rhlinux.swlocal:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is running.
Logs are generated in directory /app/oracle/product/v10.2.0/rhlinux.swlocal_DWARE/sysman/log
>>>
Any other ideas what might be causing this problem?
Thanks and take care,
Shayne

From what I've read in this forum and in others is
that the problem is often related to the owner/group
permissions associated with the bin/nmo and bin/nmb
files. However I've tried the posted solutions by
changing the owner/permissions as suggested, but this
does not help. I get the same error regardless if the
files are owned by oracle or by root.
I am not sure which "posted solutions" you had, but this is related to not running root.sh which must be run against the Agent Home.
1. Stop the Agent (emctl stop agent) while connected to the OS as Oracle user (normally oracle) that installed Grid Control
2. Connect to the OS as root and run root.sh from Agent ORACLE_HOME (if you do not have root access, your System Admin can do it)
3. Start the Agent (emctl start agent) while connected to the OS as Oracle user

Export backup error while using where clause

I am heaving Oracle9i on solaris platform. Whem i am trying to take the export backup of a table it is giving below error:
exp swtiob tables=NDC_ATMPROOF_HIST file=NDC_ATMPROOF_HIST.dmp log=NDC_ATMPROOF_HIST.log query="where PROOF_DATE >= '01-july-2010'" statistics=none
LRM-00112: multiple values not allowed for parameter 'query'
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
EXP-00000: Export terminated unsuccessfully

You need to escape the stuff like this:
$ exp scott/tiger tables=emp file=emp.dmp log=emp.log query=\"where HIREDATE\>\'09-JUN-1981\'\"
Export: Release 9.2.0.8.0 - Production on Wed Jul 7 12:54:48 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table EMP 6 rows exported
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.
$

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

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 .

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.

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

How much(in size) export backup can be used

hi,
i want to know is there any limit of export backup size ? means export backup should not exceed a limit size otherwise it would be difficult or problematic to import .
Thanxs

can you tell me how we can split export dump file in multiple file... ?http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_imp.htm#sthref2270

Need help for DB backup through OEM 11g grid

I need to know how to schedule the hot backup of whole DB using OEM 11g grid.
In our system there is a backup running for DB (10gr2). It is not scheduled through jobs.
I am not able to find this scheduled db backup information from OEM.
Can anyone guide me how to check the current backup schedules and backup script ?
Is there any good document for this ?

Hi Dhaval,
You may look out option for restore backup from production and restore the same on QAS.
Refer SAP note
683447
SAP Tools for MS SQL Server
Which shall help you with post restore steps on the database.
Once DB and SAP is up you may perform generic post restore steps like
- STMS re-configuration
- Adjusting profiles
- Executing BDLS
- Importing RFCs and user master ( if exported before the restore)
- Adjusting Partner profiles
- Configuring backup
- Apply SAP license
Above are just a few of them to name. There could be many more as per customer landscape.
Regards,
Deepak Kori

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

Oracle 10 g Datbase export problem using Data Pump

I am using Oralce 10 g on SOlaris 10 OS.I installed Oracle 10 G on Soalris suucessfully (without ASM).But when I tried to take the export using OEM faclity i.e:
OEM>Maintennace>High Avaiablity >Data Movement >Export to Export File
At last screen we got following error:-
ORA-39006: internal error Exception : ORA-39006: internal error ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DATAPUMP", line 2926 ORA-06512: at "SYS.DBMS_DATAPUMP", line 3162 ORA-06512: at line 2 .
Please help me to sort it out.
Reagrds
R N sharma

It refers to some issues with datapump utility.
Check Note:402053.1 - Internal error during EXPDP ORA-39006

Export,backup using OEM

Similar Messages

Maybe you are looking for