I dont know how to clone myself to attend all the interestign sessions out there but i hope to see all my fellow tweeters and bloggers over the course of this conference and all aboard for a wonderful conference.
The problem
Duplicate development database to new development server.
Tool Used
Rman command line
Server
AIX 5.3
After the DBA took the backup and had the backup NFS mounted on the system. He was unable to run duplicate on the new node. All auxialliary setup was complete and had seemed perfect.
An Rman catalog was used and Rman kept complaining that there were no backups to restore.
We tried a couple of things
remounted the NFS with the options rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,timeo=600,actimeo=0
based on Note:424785.1 which we thought didnt work
Looked at Note:356199.1 and set event=”10298 trace name context forever, level 32″
This didnt help either
The duplicate script was simple
connect target test/test@test
connect catalog abc/abc@abc
connect auxiliary aux/aux@aux
run {
duplicate target database to aux
}
The commands were being executed from the auxiliary server and network config was testedto be valid.
The Solution
The problem turned out to be that the dev database was changed to be an archivelog database and the archive logs were not backed up as part of the backup process. Rman kept generating an SCN that was in the archivelogs that it could not find in the catalog at all( I’m guessing since it was connected to the target it got the info from there).
As soon as the archive logs were backed up and made available the duplicate worked like a charm.
Moral of the Story : Rman needs less cryptic messages
The problem
Duplicate development database to new development server.
Tool Used
Rman command line
Server
AIX 5.3
After the DBA took the backup and had the backup NFS mounted on the system. He was unable to run duplicate on the new node. All auxialliary setup was complete and had seemed perfect.
An Rman catalog was used and Rman kept complaining that there were no backups to restore.
We tried a couple of things
remounted the NFS with the options rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,timeo=600,actimeo=0
based on Note:424785.1 which we thought didnt work
Looked at Note:356199.1 and set event=”10298 trace name context forever, level 32″
This didnt help either
The duplicate script was simple
connect target test/test@test
connect catalog abc/abc@abc
connect auxiliary aux/aux@aux
run {
duplicate target database to aux
}
The commands were being executed from the auxiliary server and network config was testedto be valid.
The Solution
The problem turned out to be that the dev database was changed to be an archivelog database and the archive logs were not backed up as part of the backup process. Rman kept generating an SCN that was in the archivelogs that it could not find in the catalog at all( I’m guessing since it was connected to the target it got the info from there).
As soon as the archive logs were backed up and made available the duplicate worked like a charm.
Moral of the Story : Rman needs less cryptic messages
Well thanks to the folks at Oracle I get to go to my First Oracle Openworld. While i have had the opportunity to go to IOUG and Hotsos have never had the chance to make it to Openworld.
Here is a list of the sessions i plan to attend based on my initial run thru of the schedule builder. I’m still hoping to get into the exam cram on sunday and maybe find more sessions of value
Well thanks to the folks at Oracle I get to go to my First Oracle Openworld. While i have had the opportunity to go to IOUG and Hotsos have never had the chance to make it to Openworld.
Here is a list of the sessions i plan to attend based on my initial run thru of the schedule builder. I’m still hoping to get into the exam cram on sunday and maybe find more sessions of value
While trying to look at dataguard as a reporting environment i found a very neat and fundamentally cost saving feature added on to dataguard in Oracle 11.
According to the Docs
“As of Oracle Database 11g, Data Guard provides increased flexibility for Data Guard configurations in which the primary and standby systems may have different CPU architectures, operating systems (for example, Windows & Linux), operating system binaries (32-bit/64-bit), and Oracle database binaries (32-bit/64-bit).
This is very interesting and actually provide a lot of cost savings to companies that have systems using Windows based servers and can purchase cheaper linux boxes and make that available . The problem is based on the matrix in note 413484.1 pretty much only Windows and Linux can live in a mixed environment . AIX and Solaris can only live with the same architecture.