Since you have exported the data, I assume that your dump file is
un-encrypted. If not, I would re-export the data without encrypting the
dump file.
Then, I would forget about the old 10g wallet, and create a new one on 12c
and re-encrypt the data during import? You can do this by pre-creating your
tables, make sure what needs to be encrypted, is encrypted, and then just
run your import.
Stefan
On Tue, Nov 17, 2015 at 11:34 PM, Lyall Barbour <
lyallbarbour@xxxxxxxxxxxxxxx> wrote:
Hi,
I'm trying to upgrade a 10g database to 12c. Best way i've learnt to do
this is export/import. Trick with this current database is that it has a
wallet. I know the password, i can open/close the wallet in the 10g
database. I've copied over the sqlnet.ora to the new 12c $TNS_ADMIN
directory. I'm using that listener.ora now for the listener. My
local_listener parameter is set. querying v$encryption_wallet shows that
the 12c container database sees the wallet directory in the sqlnet.ora file.
... in other words, everything looks GREAT!
except i can't open the dang wallet to have the import run properly. I've
used multiple syntax, old ones from 10g and 11g. Plus a new one i've
learnt from 12c documents. Any one have any suggestions? OWM never seems
to work for me in any version. NOt sure if that's a/the problem.
ALTER SYSTEM SET ENCRYPTION KEY AUTHENTICATED BY
*ALTER SYSTEM SET WALLET OPEN IDENTIFIED BY *
ALTER SYSTEM SET ENCRYPTION WALLET OPEN IDENTIFIED BY
plus,
ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY
software_keystore_password [CONTAINER = ALL | CURRENT];
constantly (consistently) getting ORA-28353: failed to open wallet
Any suggestions?
Lyall Barbour
-- //www.freelists.org/webpage/oracle-l
