Company to upgrade to the 12 c database, so I just thinking about the user first, and table space is established, with 10 g, until 11 g build user table space, backup data migration is good until met 12 c this wonderful work
Under the first 12 c with CDB general user c # # at the beginning of success, but try to connect with conn username/password will prompt the user name password mistake, cut into the PDB build user is also suggested to establish successful, but the connection prompt the user name password mistake...
Since last model can't replace nocdb traditional model, the result is the same, I sysdba in build user, authorization, and so on are successful, the cut out try to use new user connection still hint user name password mistake...
Is speechless, the great god know how to solve???????

CodePudding user response:

Confirm with ordinary users to connect, whether the 12 c server,

CodePudding user response:

If is up sqlplus/as sysdba mode to enter into must be c # # user, need to switch to the PDB, and authorized, seems to be going to below the PDB authorized, authorized under the CDB seems to be no good,

CodePudding user response:

refer to the second floor u012556249 response:

, if is up sqlplus/as sysdba mode to enter into must be c # # user, need to switch to the PDB, and authorized, seems to be going to below the PDB authorized, authorized under the CDB seems to be no good,

Is established under the alter to the corresponding PDB user and authorization

CodePudding user response:

reference 1st floor wmxcn2000 response:

confirm that using ordinary users to connect, whether the 12 c server,

There is only one database on the server can't go wrong

CodePudding user response:

Can send once you enter the database SQL statements, including into the CDB, switch to the PDB, SQL, and log in

CodePudding user response:

Garbage 12 c against humanity simply, lemon no return 10 g, oracle more do more junk this year change database to postgresql forever farewell oracle the sinkhole

CodePudding user response:

12 c new library, password authentication rules have changed, change sqlnet forwards compatibility:
SQLNET. ALLOWED_LOGON_VERSION_SERVER=8
SQLNET. ALLOWED_LOGON_VERSION_CLIENT=8

Then a change on the user's password

It is ok to meet this situation

CodePudding user response:

Also encountered the same problem in oracle12c PDB container new user must begin with c # #, but use the new password login definite user name password authentication failure; Preliminary solution is to modify the c # # username username and password:
The select user#, name the from user $; Check it - to the required change user name
Update user $set name='newusername' where user#=139; (currently must be changed to uppercase user, landing can also have a question, also don't know how to solve)
commit;
Forced to refresh
The ALTER SYSTEM CHECKPOINT.
The ALTER SYSTEM FLUSH SHARED_POOL;
Change the password, otherwise or validation failure
The ALTER USER 'username' identified by passwd;
Commit;

CodePudding user response:

12 c # # user login

CodePudding user response:

Can only be created in the last global user (c # #) in the beginning, will create the user in the CDB and all the PDB (but global user need additional authorization of PDB can access in the PDB),
Can only be created by the user in the PDB for local users.
Conn/as sysdba connection is the CDB
PDB with conn/XXX XXX @ PDB to connect,

http://docs.oracle.com/database/122/ADMIN/overview-of-managing-a-multitenant-environment.htm#ADMIN13507