What to do when oracle 12c imports 10g users by expired and locked
Editor to share with you what to do by expired and locked when oracle 12c imports 10g users. I believe most people don't know much about it, so share this article for your reference. I hope you will get a lot after reading this article. Let's learn about it together.
Because the business needs to import a user data into the 12c database, but the business does not know the original password, the password has been saved in an application software and needs to be imported into
12c data is guaranteed to be the original password. Here, the data pump is imported. In the past, as long as the user's tablespace existed in the database, the data pump would automatically
Create a user and give the relevant permissions consistent with the source side. However, when it was imported this time, the report was wrong.
Ora-39384 tells us that the user's status is expired and locked, but the user is normal in the source environment.
Find a document on mos for similar issues (ID 2273707.1), add a line of parameters to the sqlnet.ora file on the 12c database server, and then import it again.
Problem solved.
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10
The above is all the content of this article "what to do when oracle 12c imports 10g users by expired and locked". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!