Oralce集羣管理-數據庫連接ASM報錯分析處理v1111

11.2.0.4 DBCA does not bring up pop-up window to enter password for SYS in ASM which results in ORA:01017 (INVALID USERNAME/PASSWORD; LOGON DENIED) (Doc ID 1597579.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.
SYMPTOMS

non-RAC -- 11204 -- HP-UX Itanium (11.31)     <---- It could apply to other platforms or a 'clustered' (RAC) configuration

DBCA does not bring up the ASM Credentail pop-up (below), where one enters the password for ASM's SYS, after selecting ASM for the storage location of the database (step 6/12 - Database File Locations)

Therefore the database creation fails (even when creating the database outside of DBCA -- ie, manually or via sqlplus and using the CREATE DATABASE command)


dbca logs shows:

/oracle/app/oracle/cfgtoollogs/dbca/trace.log_OraDb11g_home3_2013-10-29_11-15-02-AM
[AWT-EventQueue-0] [ 2013-10-29 11:31:07.368 EDT ] [SQLEngine.done:2189] Done called
[AWT-EventQueue-0] [ 2013-10-29 11:31:07.371 EDT ] [ASMUtils.validateASMConnection:265] can not connect ORA-01017: in valid username/password; logon denied
[AWT-EventQueue-0] [ 2013-10-29 11:31:07.372 EDT ] [SQLEngine.done:2189] Done called

Database alert Log shows:

Tue Oct 29 11:31:07 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /oracle/app/oracle
Errors in file /oracle/app/oracle/diag/rdbms/ctsgold/ctsgold/trace/ctsgold_asmb_9836.trc:
ORA-15055: unable to connect to ASM instance
ORA-01017: invalid username/password; logon denied
Database trace file
Trace file /oracle/app/oracle/diag/rdbms/ctsgold/ctsgold/trace/ctsgold_asmb_9836.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/app/oracle/product/11.2.0.4/dbhome_1
...
WARNING: failed to start ASMB (connection failed) state=0x1 sid='+ASM' home='/oracle/app/grid/product/11.2.0.4/grid'
ORA-15055: unable to connect to ASM instance
ORA-01017: invalid username/password; logon denied

CAUSE

Several things were tried like suggestions from Note:1269734.1, Note:1177483.1, Note:1468931.1, and even recreating the orapwd file from ASM, but none fix the issue.

Even tried to workaround the improper Job Role Separation (JRS) configuration, but that too did not worked. JRS is an optional feature that allows job separation between the roles of the ASM and the database administrators.

# id grid
uid=110(grid) gid=106(oinstall) groups=107(dba),108(oper),110(asmdba),111(asmoper) <----- 'asmadmin' OS role missing from 'grid'

# id oracle
uid=109(oracle) gid=106(oinstall) groups=107(dba),108(oper),110(asmdba),112(hvri)

# ls -ltra /oracle/app/grid/product/11.2.0.4/grid/bin/oracle
-rwsr-s--x 1 grid oinstall 502885304 Oct 15 15:07 /oracle/app/grid/product/11.2.0.4/grid/bin/oracle

$ ls -ltra /oracle/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle
-rwsr-s--x 1 oracle oinstall 573962880 Oct 15 17:36 /oracle/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle #<--- even with 'oinstall', as the OS group, it did not worked.

$ ls -ltra /dev/rdisk
crw-rw---- 1 oracle dba 13 0x000020 Oct 9 10:41 disk70 # <----- asm disks part of the 'dba' OS group
crw-rw---- 1 oracle dba 13 0x00001b Oct 9 10:42 disk65
crw-rw---- 1 oracle dba 13 0x000016 Oct 9 10:42 disk60
crw-rw---- 1 oracle dba 13 0x000022 Oct 9 10:42 disk72

The cause was improper Job Role Separation (JRS) even the same JRS misconfiguration worked for 11.2.0.2

SOLUTION

The OS role 'asmadmin' was not assigned to the user 'grid' in this case, but other JRS misconfigurations could also lead to this condition.


The fix is not as simple as to create the OS role 'asmadmin' and assign it to 'grid' and relink the gi_home. A full deinstall of the Oracle Homes (db_home first, and then gi_home) is required.


Deinstall the db_home and then the gi_home using the 'deinstall' tool:

===> http://docs.oracle.com/cd/E11882 ... le_sw.htm#HPDBI1332   #<----- this example is for HP-UX and Standalone (ie, non-RAC)
         Oracle® Database Installation Guide
         11g Release 2 (11.2) for HP-UX
         E49316-01
         7 Removing Oracle Database Software
   
Then reconfigure JRS appropriately:

===> http://docs.oracle.com/cd/E11882 ... nstall.htm#BABHHEJD   #<----- this example is for HP-UX and Standalone (ie, non-RAC)
         Oracle® Database Installation Guide
         11g Release 2 (11.2) for HP-UX
         E49316-01
         2.9 Creating Required Operating System Groups and Users

Finally, reinstall and reconfigure the gi_home and then the db_home (including launch DBCA to create the db which then DBCA will bring up the ASM Credentail pop-up).


REFERENCES

BUG:17662103 - DBCA THROWS ORA:01017: INVALID USERNAME/PASSWORD; LOGON DENIED

 

範例 2 

 

 

1)查alert日誌
2)The issue is caused by incorrect permissions of GI_HOME/bin/oracle and ORACLE_HOME/bin/oracle, which lead to connections failed from an RDBMS instance (RDBMS) to the ASM instance.
For this customer, the ASM instance works fine and the DG have been mounted, the permissions of GI_HOME/bin/oracle and ORACLE_HOME/bin/oracle are incorrect.
If the permissions are incorrect, this will lead to connections failed from an RDBMS instance (RDBMS) to the ASM instance.$ORACLE_HOME/bin/oracle is the main Oracle RDBMS kernel binary, and implements the functions of all background daemons: PMON, SMON, DBWR, LGWR, CKPT, etc.
Connection functionality implies attach to SGA shared memory, which needs to be initialized at instance startup; this happens with routines inside bin/oracle and (at a very high level) user privileges of who st arts up the instance need to match with user privileges of who wants to connect to the instance.
Database open implies opening files; this also happens in code inside bin/oracle. Again, privileges of who starts up the instance and attempts to open the database need to match the privileges of files where the data actually resides.ASM is implemented as an Oracle instance - starting out of the bin/oracle in GI_HOME; so you'll also have connections from an ORACLE_HOME instance (RDBMS) and a GI_HOME instance (ASM) for I/O path translations

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章