Tuesday, May 9, 2017

Error 1017 received logging on to the standby - Along with ORA-16191

Most probable reason for this error appearing in the alert log file of standby database is that primary database is not able to connect to the standby database to ship redo log data because the password for the SYS user in the standby database is not in sync with the primary database. Standby database is also not able to fetch the archive gap because of same discrepancy. Full error stack in the alert log file would look similar to the following.

Friday, May 5, 2017

File #... added to control file as UNNAMED000 and ORA-15041

On your standby database if you see a datafile with the name similar to ‘UNNAMED000’, it means that you have STANDBY_FILE_MANAGEMENT parameter set to auto and managed recovery process tried to create a new datafile (after you already added this file on primary database), but it could not create file because of some reason. I faced this error because my ASM diskgroup was full. Following were the entries in my alert log file of my standby database after adding a datafile in my primary database using command ‘ALTER TABLESPACE my_tablespace ADD DATAFILE ‘+DATA/datafile06.dbf’ SIZE 20g’

Thursday, April 27, 2017

ORA-38701: Flashback database log...

If you are trying to list the restore points you have, and your flashback logs are not available on the disk (in the FRA), you might face ORA-38701.
SQL> select * from v$restore_point;
select * from v$restore_point
ERROR at line 1:
ORA-38701: Flashback database log 1 seq 1 thread 1:

Friday, April 21, 2017

ORA-38760: This database instance failed to turn on flashback database

I faced this error message while opening my database, after restoring the database from a cold backup (OS level copy of all database files). I realized that when I backed up my database, it had flashback feature turned on and there was also a guaranteed restore point at the time I took the backup. And this time when I was trying to open this database, there were no old flashback logs available in fast recovery area.

Thursday, April 13, 2017

Data Masking using OEM Cloud Control

Data masking is a technique whereby we mask the sensitive data in the cloned copies of production databases (cloned for testing purposes) so that testing databases don’t contain any sensitive information like credit card numbers or other personal information data like email address or phone numbers etc. Once we create a clone of production database, we mask the data before handing over to the users.

Wednesday, April 5, 2017

Transparent Data Encryption in 12c

One of my previous article explains how to setup TransparentData Encryption in 11g. In this article I would discuss how to implement Transparent Data Encryption (TDE) in 12c database to encrypt the data in tables/column and tablespace. Following is the link to official 12c documentation I used to write this article https://docs.oracle.com/database/121/ASOAG/asotrans_config.htm#ASOAG10474.

Thursday, March 30, 2017

ORA-46630: keystore cannot be created at the specified location

This error comes while creating a keystore at a location where there is already a keystore exists and you can see ewallet.p12 file already present there.
To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location.

Wednesday, March 22, 2017

ORA-46633: creation of a password-based keystore failed

You can face this error while creating a keystore but you have specified a wrong keystore location while executing the statement.

Wednesday, March 15, 2017

ORA-46658: keystore not open in the container

You may face this error when database needs to access the keystore and keystore is not open. For example, while changing keystore password, or while creating/rotating master encryption key. In the following example, I faced this error while creating master encryption key.

Thursday, March 2, 2017

ORA-28417: password-based keystore is not open

You may face this error while creating a master encryption key while having/using auto-login (or local auto-login) keyswtore, but your password-based keystore is still closed which is required to be open before you can create master encryption key.

Popular Posts - All Times