Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve the ORA-46952 problem in oracle12.2 adg". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to solve the ORA-46952 problem in oracle12.2 adg".

Oracle 12.2 adg has this problem in the App Log Times

Errors in file / app/oracle/oracle/diag/rdbms/o12dbadg/O12DBDG/trace/O12DBDG_pr00_186543.trc:

ORA-46952: standby database format mismatch for password file'/ app/oracle/oracle/product/12.2.0/dbhome_1/dbs/orapwO12DBDG'

The problem is that the manual creation of the password file of the slave database may not be standardized. You can solve this problem by directly finding out the password file on the main database and then copying it to the slave database again:

SQL > select * from v$passwordfile_info

FILE_NAME

FORMAT IS_AS CON_ID

+ DATA/O12DB/PASSWORD/pwdo12db.256.1024706535

12 TRUE 0

Another way to troubleshoot this error:

Was getting the same error after primary to standby switchover: ORA-46952: standby database format mismatch for password file AND MRP0: Background Media Recovery process shutdown1. Select * from v$passwordfile_info -- > showed different format in primary (12.2) and standby (12) 2.password changes were propagated correctly between primary and secondary* * For me fix was (RAC environments): 1. Delete password file on standby with version 12 pwdelete-- dbuniquename standby 2. Remove from SRVCTL srvctl modify database-db standby-pwfile 3. Create new password file in ASM (asmcmd) pwcreate-dbuniquename standby + DATASM/standby/PASSWORD/pwdstandby PwdThat# EnforcesThe12201ComplexityRules Password must contain at least 8 charactersPassword must not contain double quotesPassword must contain at least 1 letterPassword must contain at least 1 digitPassword must contain at least 1 special characterPassword must not contain the usernamePassword must not contain username reversed 4. Add the Pwd file back to SRVCTL srvctl modify database-db standby-pwfile + DATASM/standby/PASSWORD/pwdstandby 5. Select * from v$passwordfile_info-- > now shows same format 12.2 as primary passwordfile 6. ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION -- > started redo apply no issues I think our issue was due to the legacy password file we had on the original primary db where 12.2.0.1 password complexity rules were not followed so version was determined as 12 vs 12.2In 12.2.0.1 there should be no need to copy password files between primary and standby dbs.My issue got resolved after i followed below process:-1. Created the password file in primary with the old password.2. Deleted all the password file in the standby site.3. Started the MRP and standby got sync.4. Changed the password in the primary db (in sqlplus only like alter user sys) and it got sync automatically without copying file manually. SR has helped to resolve the issue:-The Workaround to bypass this difference in Redo are the steps in internal Note 2503352.1 Thank you for your reading, the above is the content of "how to solve the ORA-46952 problem in oracle12.2 adg". After the study of this article, I believe you have a deeper understanding of how to solve the ORA-46952 problem in oracle12.2 adg, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.