This content has been marked as final. Show 21 replies
How To Prevent The Secure Password Store Wallet From Being Moved to Another Host [ID 1114599.1]
Thanks for your reply. I couldn't find thread you mentioned. The closest match I could find was -
Tried the suggested stuff here, but the problem still seems to be same. (I added an entry to my windows host file also as suggested here)
But that wasn't a thread but an article on the support web site. Are you sure you logged in to it and couldn't find the article actually?
Do you have the link to that post/thread?
Hmm, I have just checked and the document is there. Did you go to https://support.oracle.com (don't use that myoraclesupport website, it's a fake) and searched for it in the Knowledge Base?
Thanks. Unfortunately the info at the support site is exactly the same as what was present in the earlier link I mentioned and neither of them worked for my case :(
Still stuck with the issue. Wondering if it is the 11G R2 issues specifically....
Anyone got a clue....
This issue didn't get solve and I had no other option but to downgrade the Database from 11G Release 2 to 11G Release 1. Once I put the R1, wallet was working fine.
I had the same issue on my Window 7 laptop and saw your thread as I was attempting to troubleshoot it. I figured it out and I'd like to share how. I turned on the Sysinternals tool Process Monitor and tried startup again. After the failure I stopped collecting data in process monitor. I filtered the output to include lines with .sso or .p12 which are the extensions on my two Wallet files. It showed me that the issue was ACCESS DENIED to the NT_AUTHORITY\SYSTEM account when accessing those two files. SYSTEM is the account my local test Oracle instance runs under. I granted the rights to SYSTEM for those two files and now my database is working.
How did you grant SYSTEM (db user) the rights for those two files on OS level?
Is this following post may helpful for you?
Thanks a lot.
Though, my wallet is working when I connect via sqlplus.
Where I'm having issues is, I want to use it for DataPump export job ... that is where I got the error:
ORA-12578: TNS:wallet open failed
Any hint on that?
Thanks for your response.
Can you paste your sqlnet.ora file here?
Here it is:
(METHOD = FILE)(METHOD_DATA =
(DIRECTORY = /oracle/product/11.2.0/ddw7/network/admin)))
SQLNET.WALLET_OVERRIDE = TRUE
SSL_CLIENT_AUTHENTICATION = FALSE
SSL_VERSION = 0
Change TRUE to FALSE and try, Usually this parameter is useful for who want connect particular schema from client machine, you can configure this parameter in client machine and configure which schema you want to connect without schema name and password.
I don't think so If this parameter is enabled in server, you can able to take export or connect other schema in database
SQLNET.WALLET_OVERRIDE = FALSE