Database Security Products (MOSC)

MOSC Banner

Can ORA-39173 be ignored?

in Database Security Products (MOSC) 1 commentAnswered ✓

Oracle database in version 19.3

Since we implemented TDE, we got below errors in our daily export jobs:

ORA-39173: Encrypted data has been stored unencrypted in dump file set.

Questions:

  1. Can we just ignore the warning and keep our daily jobs as is? We should be still able to use the dumpfile to import to the same database if needed, right? If we need to import to a different database, do we need any extra steps? (I think no but not sure)
  2. I understand by adding encryption_password parameter we can bypass the error. And we should be able to import to the same database by using the same encryption_password. What if we need to import to a different database, do we need any extra steps? What are the other impacts with this parameter?
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center