Archive for 01/01/2009 - 02/01/2009
RMAN-03009 ORA-19554 ORA-27211
RMAN-00571: ===========================================================
RMAN-00569: ====== ERROR MESSAGE STACK FOLLOWS =======
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on DP_TEST channel at 01/22/2009 08:54:22
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Recovery Manager complete.
Problem is about linking the "libob2oracle8_64bit.so" file in DP library directory to oracle library directory. following softlink create command fixes the problem:
cd $ORACLE_HOME/lib
ln -s /opt/omni/lib/libob2oracle8_64bit.so libobk.so
Security with a different point of view
"There are ways to audit Oracle databases which the DBA cannot change or at least not change in an undetectable manner) but that still leaves you at the mercy of your system admins. Something that auditors seem to have a real problem understanding is that to run your systems you have to have people who, if they went bad, could do serious damage to your company and even place it in a legally difficult situation.
There is, however, a really simple yet effective solution. It's so simple and effective that it's been in use for about 550-600 years at least (i.e. since the Tudor monarchy in England).
* Be very selective in your selection and actually do background checks (it amazes me how many companies simply don't bother to do something as simple as a criminal records check).
* Pay them a lot and give them nice workplace faccilities. The more they have to lose, the more profitable any wrong doing has to be before they'll get tempted.
* Put them fairly high up in the political structure and make sure that the board back them to the hilt. If they can, figuratively speaking, 'flip the bird' to anyone who tries to put them under
pressure to do something unethical and have no fear of being sacked if they blow the whistle then they will be less likely to fall prey to political machinations in the organisations. Sometime make a list of all the companies, in say the last 35 years, that have gone under, suffered a major loss or been prosecuted due to some wrongdoing, then divide the list according to whether the person responsible was a business/finance person or a technical person. It'll be a very much one-sided list.
* Make it clear from the get go that anyone found acting unethically will be publicly sacked and their wrong doing will be publicised so they'll be lucky if McDonalds hires them to clean the grease traps. Then actully do it. I believe that in the first use of this system the punishment was public beheading (it was in the 1500s) but you don't need to go that far."
Performing a Recovery After a Resetlogs Option
Q - You have a backup from two days ago. It is discovered that corruption was introduced today at 6:30 P.M. You perform an incomplete recovery of the database to 6:25 P.M. before the corruption. One day later you have a media failure, and you need to recover but you only have the same backup that was used to perform an incomplete recovery prior to the corruption. What will happen to the recovery attempt for the media failure?
A - The media recovery will be successful because you can perform a RESETLOGS to recover from an incomplete recovery to a new point-in-time greater than the RESETLOGS operation.
With 10g, you can now recover through an incomplete recovery, which uses RESETLOGS to open the database. In previous Oracle versions, you had to take a backup immediately following an incomplete recovery, because the redo log sequences got reset, making the backup unusable.
