I was recently configuring backup on the customers Exadata with IBM TSM Data Protection for Oracle and run into weird RMAN error. The configuration was Oracle Database 11.2, TSM client version 6.1 and TSM Server version 5.5 and this was the error:
[oracle@oraexa01 ~]$ rman target / Recovery Manager: Release 22.214.171.124.0 - Production on Wed Jan 29 16:41:54 2014 Copyright (c) 1982, 2011, Oracle and/or its affiliates. (more...)
rman target /
Recovery Manager: Release 126.96.36.199.0 - Production on Wed Sep 18 20:47:38 2013
I want to cover ASM to non-ASM (more...)
So I’ve performed some tests and decided to (more...)
Flashback database is not enabled by default so first step would be to enable it. When enabled a process RVWR (Recovery Writer) copies modified blocks to flashback buffer. Later this buffer (more...)
But I think it’s much better (more...)
I have announced my webinar on Oracle ZFS Storage Appliance for Exadata Backup & Recovery in NYOUG DBA webinar series. You can download webinar slides and voice recod from NYOUG web site
These days I’m implementing Oracle Dataguard for two Oracle databases 10.2 as part of disaster recovery project, one of them is around 1.7TB, not yet production. As part of the DG setup backups have to be available for both primary and standby. I preferred to use ASM and was able to negotiate with the storage admin to run storage replication for the FRA disks during the backup. This way I would have the same structure and files, locally at the disaster site immediately after the backup of the primary database is completed.
Unfortunately two weeks passed and by (more...)
To check the performance of RMAN backup I recently started to trace it a little bit. As most of the time was not spent in any reading from disk or writing to media manager library event, it was on CPU. It's good to know the CPUs are of any good, but as I still want to know what's going on I tried to dig any deeper. CPU cycles are not just a magic black box where we put in a problem and the answer comes out after some times. At an abstraction layer it's a chain of functions where one (more...)
This is a quick post regarding the error on the subject. This is the second time it happens to me, so I thought I will write a bit about it.
I am refreshing one of my UAT environments (happens to be a Full Rack Exadata) using Oracle RMAN duplicate command. Then the following happens (on both occasions).
1.- Duplicate command fails (lack of space for restoring archivelogs, or any other error). This is can be fixed quite easy.
2.- following error while trying to open the database after restore and recover has finished:
SQL> alter database (more...)
I must say, this has been a busy weekend.
We have been promoting a release to production and a guaranteed restore point was created on Friday as rollback strategy. On Sunday I was called as we started to receive alerts.
Our monitoring system started to send emails and SNMP Traps with the following alerts:
OEM alert for Automatic Storage Management +ASM4_ssssss4: Disk group RECO has used 100% of safely usable free space. (Current Disk Group Used % of Safely Usable value: 100) OEM alert for Automatic Storage Management +ASM2_ssssss2: Disk group RECO has used 100% of safely usable (more...)
The operation can be performed by creating a datafile copy, either with the traditional commands or by means of recovery manager. In this case the following script was prepared to move a datafile.
copy datafile '
sql 'ALTER TABLESPACE
set newname for datafile (more...)
This afternoon on a Oracle 188.8.131.52 installation, i was trying to run the Oracle RMAN utility. Rman cli was just hanging and not going into RMAN.
[oracle@linux2 ~]$ . oraenv ORACLE_SID = [oracle] ? 11202 The Oracle base has been set to /opt/oracle/product/rhel4/database/184.108.40.206 [oracle@linux2 ~]$ rman
After entering above rman command, nothing happened. It just hung on the command prompt. I did not receive any error at all. Hmm… whats happening? I issued an CTRL-C to cancel it and tried again. Still same result. Okay lets trace it using Linux strace utility.
oracle@linux2 ~]$ strace rman (more...)
Us Linux DBAs love cron for scheduling jobs. These fancy software schedulers with their dependencies and clever logic have never really replaced a really dense, difficult to read crontab file. And that's just the way we like (more...)
We were moving a database to a new server. Same OS, same version of Oracle (10.2.0.4). The database is in Archivelog mode, but to keep things easy, we decided to do an offline, consistent backup.
So, we shutdown the database, then mounted it and performed an RMAN backup to a flash_recovery_area on a shared NFS filesystem:
backup device type disk database plus archivelog include current controlfile;The backup worked fine. So we logged on to the new server, made sure that we could (more...)
Some time ago I read a post about RMAN on Oracle-L that detailed what seemed like a very good idea.
The poster's RMAN scripts were written so that the only connection while making backups was a local one using the control file only for the RMAN repository.
rman target sys/manager nocatalog
After the backups were made, a connection was made to the RMAN catalog and a SYNC command was issued.
The reason for this was that if the catalog was unavailable for some reason, the backups would still succeed, which would not (more...)
In this post, I'll discuss a couple of other issues that you may come across; although, admittedly, they are fairly uncommon.
Standby DB Restores
Like a lot of other sites we maintain a physical standby database, managed using Dataguard, ready to use as a failover instance, in case of problems with the main RAC database. This database is the source for all backups, to avoid overloading the production servers. This leads to a small (more...)