in 11g, alter user works fine: oracle@hostxyz25:/opt/app/oracle/ [crs111] +asm1 oracle@hostxyz25:/opt/app/oracle/ [+ASM1] sq SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 4 14:07:16 2009 Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options SQL> alter user sys identified by foo; User altered. SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options oracle@hostxyz25:/opt/app/oracle/ [+ASM1] sqlplus sys/foo@asm_hostxyz25 as sysdba SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 4 14:07:31 2009 Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options SQL> alter user sys identified by foobar; User altered. SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options oracle@hostxyz25:/opt/app/oracle/ [+ASM1] sqlplus sys/foobar@asm_hostxyz25as sysdba SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 4 14:07:43 2009 Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP, Data Mining and Real Application Testing options What you need to be careful though, if you're using sysasm, that information gets lost when you would choose to recreate the password file. So you have to issue another grant SYSASM to sys after doing that. Both ways work just the same (in 11.1). Cheers Stefan ========================= Stefan P Knecht CEO & Founder s@xxxxxxxx 10046 Consulting GmbH Schwarzackerstrasse 29 CH-8304 Wallisellen Switzerland Phone +41-(0)8400-10046 Cell +41 (0) 79 571 36 27 info@xxxxxxxx http://www.10046.ch ========================= On Wed, Mar 4, 2009 at 10:01 AM, bao jiejie <baojiejie@xxxxxxxxx> wrote: > Dear gurus, > > Anyone experience such kind of work to change the sys password of an ASM > instance? > > will that affect other ASM instances in the RAC nodes also? > > first come out to me is logging in as sysdba and "alter user" , of course , > can not work, > > So how about change it only via ORAPWD ? anyone experienced that before ?? > > then comes to another question, how to change that in 11g cause it using > "connect / as sysasm " > > Thanks a lot. > > -- > > ("'-''-/").___..--''"'-._ > '7_ 7 ) '_. ( ).'-.__.') > (_Y_.) ._ ) '._ '. ''-..-' > _.'--'_..-_/ /--'_.' ,' > (il),-'' (li),' ((!.-' > > Best regards, > Yours sincerely House > baojiejie@xxxxxxxxx > > >