ORA-01017

problem

01017, 00000, "invalid username/password; logon denied"
// *Cause:
// *Action:

screening 1 - Confirm that the account and password are correct （ Reset password ）

alter user  Account  identified by  password ;

screening 2 – Case sensitive

show parameter case

screening 3 – Check monitor

lsnrctl status

listener.ora

Positioning reason ： It needs to be configured as $ORACLE_HOME

SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = orcl) #show parameter service
      (ORACLE_HOME = /u01/app/oracle/product/12.1.0/dbhome_1) # echo $ORACLE_HOME
      (SID_NAME = orcl) # show parameter name
    )
  )

GLOBAL_DATABASE_NAME： 

①GLOBAL_DATABASE_NAME  yes listener Configured external network connection name , It could be any value  

② Configure listening on the client side tnsnames.ora  In the document service_name With this GLOBAL_DBNAME  Just be consistent  

③ When configuring static listening registration , Need to enter SID and GLOBAL_NAME


DB_NAME： 

① It's the database name , The length cannot exceed 8 Characters , Recorded in the datafile、redolog and control file in  

② stay DataGuard Environment DB_NAME Same as DB_UNIQUE_NAME Different  

③ stay RAC Environment , Of each node DB_NAME All the same , however INSTANCE_NAME Different  

④DB_NAME It also works when dynamically registering for monitoring , Whether defined or not SERVICE_NAME,PMON All processes will use DB_NAME Dynamic registration monitoring  


DBID： 

①DBID You can view it as DB_NAME Representation inside the database , It is used when the database is created DB_NAME Combined with the algorithm  

② It exists in datafile and control file in , Used to indicate the ownership of a data file , therefore DBID Is the only one. , For different databases ,DB_NAME It could be the same , however DBID It must be unique , For example, in DataGuard in , The main and backup libraries are DB_NAME identical , however DBID It must be different （ I've seen a very vivid example , That is, there can be people with the same name , But the ID number must be different ） 


DB_UNIQUE_NAME： 
① stay DataGuard in , The primary and secondary libraries have the same DB_NAME, To distinguish , It has to be different DB_UNIQUE_NAME 

②DB_UNIQUE_NAME stay DG Will affect the dynamic registration of SERVICE_NAME, That is, if dynamic registration is used , Then registered SERVICE_NAME by DB_UNIQUE_NAME, But the example is still INSTANCE_NAME, namely SID 


INSTANCE_NAME： 

① The name of the database instance ,INSTANCE_NAME The default value is SID, In general, the name of the database and （DB_NAME) identical , It can be different  

②initSID.ora  and orapwSID  The file should be consistent with INSTANCE_NAME bring into correspondence with  

③INSTANCE_NAME Will affect the name of the process  


SID： 

① Is an environment variable in the operating system , and ORACLE_HOME,ORACLE_BASE The usage is the same  

② In the operating system, to get the instance name , Must use ORACLE_SID. And ORACLE_SID Must be with INSTANCE_NAME The value is consistent.  


SERVICE_NAME： 

① The service name used to connect the database to the client  

② stay DataGuard in , If dynamic registration is used , It is recommended to use the same service_names 

③ stay DataGuard in , If you use static registration , It is suggested that listener Enter the same service name in (service_name) 

④ If static registration is used , that SERVICE_NAME Is equal to Listener.ora In the document GLOBAL_DATABASE_NAME Value  

screening 4 – View parameters

show parameter remote_login_passwordfile

ORA-01017 Common typical cases of errors and parts