Categories
- All Categories
- 168 Oracle Analytics News
- 34 Oracle Analytics Videos
- 14.8K Oracle Analytics Forums
- 5.8K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 56 Oracle Analytics Trainings
- 13 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
ora-28040 No matching authentication protocol when running 11g RCU against 12c DB

Hi Guys,
Need to create the metadata schemas through RCU 11g on a 12c DB and getting the above error.
The RCU was downloaded from
https://www.oracle.com/middleware/technologies/bi-downloads.html
Checked the forum and saw many reported this error, but did not find a solution yet.
Updated all the sqlnet.ora with
SQLNET_ALLOWED_LOGON_VERSION_SERVER=(12a,12,11,10,9,8)
SQLNET_ALLOWED_LOGON_VERSION_CLIENT=(12a,12,11,10,9,8)
Tried to run the RCU from \ORA\MWFR\12cappr2\oracle_common and there I getting the below error
Unable to connect to the DB. Check if DB connection details entered are correct.
Invalid username/password.
Enter valid username/password
I have correct credentials as I can login into sqlplus without any problem.
Any suggestions?
Answers
-
1.) "11g" - that covers about 7 years of product lifecycle and something like 50 releases.
Be specific!
2.) Have you looked at any of the log files which these wizards produce?
3.) 11g is completely outdated and you really shouldn't be using it anymore.
0 -
Hello Christian,
I used the RCU i download from https://www.oracle.com/middleware/technologies/bi-downloads.html where I also downloaded the OBIEE media files on 11.1.1.19
When I run the 11.1.1.19, it did not generate any log file I could find.
When I run the rcu I found in
\ORA\MWFR\12cappr2\oracle_common, it generates a log file, which I am attaching.
In regards to 11g being outdated, I know it, but as far as we as oracle do not announce end of life for some products that works only with 11g, I am afraid I am forced to install it.
thanks for any help
0 -
Its old thread but will help others in same problem.
you have to add below in sqlnet.ora and then it will work.
SQLNET.ALLOWED_LOGON_VERSION = 11
0