6/23/2009 · Enter user-name: / as sysdba Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – Production With the Partitioning, OLAP, Data Mining and Real Application.
user1865419 wrote: Database is running OK. I can logon as system but not sys. When using sqlplus / as sysdba or sqlplus sys/ {syspassword} as sysdba get ORA-01031: insufficient privileges. l select * from v_$pwfile _users view and its empty , no rows. I have the password file orapwinfdev in the DBS directory.
17 rows · 8.138 V$PWFILE_USERS. 8.138. V$PWFILE_USERS. V$PWFILE_USERS lists all users in.
Answer: The v$pwfile_users view contains a list of all users who have been granted the SYSDBA or SYSOPER privilege. In 11g there is a new column in v$pwfile_users for the SYSASM privilege: SYS AS SYSDBA @ orcl11 SQL> select * from v$pwfile_users, Use V$PWFILE_USERS to find the users allowed to login the database using the password file.
You can find if a user has been granted an administrative privilege on a local (PDB) level, for a CDB root, or for an application root by querying the SCOPE column of the V$PWFILE_USERS dynamic view. You can grant the SYSDBA or SYSOPER administrative privilege to.
8/22/2013 · SQL> SELECT * FROM v$pwfile_users WHERE username=KING_PDB USERNAME SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM CON_ID -KING_PDB FALSE FALSE FALSE TRUE FALSE FALSE 3 [/cc] When login as local user KING_PDB without SYSBACKUP the login time is updated.
3/21/2007 · SQL> select * from v$pwfile_users USERNAME SYSDB SYSOP —– —– —– SYS TRUE TRUE JEREMY TRUE FALSE No problem – NFS seems to work fine. (And without any special mount options like datafiles and clusterware files require!), select USERNAME,SYSDBA,SYSOPER,SYSASM from v$pwfile_users. and if its 12 or 19 run: select USERNAME, SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, CON_ID from v$pwfile_users. And also there should be no error when it is run on any version of the DB. (just no rows selected) Please suggest.Thanks. sql oracle.
6/4/2014 · A 12c multitenant database introduces the new concept of local users and common users. This article shows simple use cases why DBAs may want to create common users in contrast to the common users that are created automatically, like SYS, SYSTEM, MDSYS etc. A typical requirement is to have a superuser other than SYS, but with the same power.