This action might not be possible to undo. Are you sure you want to continue?
1] Modified 21-AUG-2009 Type TROUBLESHOOTING Status PUBLISHED
Introduction: ~~~~~~~~~~~~~ This bulletin lists the documented causes of getting ---> prompted for a password when trying to CONNECT as SYSDBA ---> errors such as ORA-01031, ORA-01034, ORA-06401, ORA-03113,ORA-09925, ORA-09817, ORA-12705, ORA-12547 The dbacheck script in note 67984.1 may help troubleshoot issues of this nature. a) SQLNET.ORA Checks: --------------------1. The "sqlnet.ora" can be found in the following locations (listed by search or der): $TNS_ADMIN/sqlnet.ora $HOME/sqlnet.ora $ORACLE_HOME/network/admin/sqlnet.ora Depending upon your operating system, it may also be located in: /var/opt/oracle/sqlnet.ora /etc/sqlnet.ora A corrupted "sqlnet.ora" file, or one with security options set, will cause a 'connect internal' request to prompt for a password. To determine if this is the problem, locate the "sqlnet.ora" that is being us ed. The one being used will be the first one found according to the search order listed above. Next, move the file so that it will not be found by this search: % mv sqlnet.ora sqlnet.ora_save Try to connect internal again. If it still fails, search for other "sqlnet.ora" files according to the searc h order listed above and repeat using the move command until you are sure there are no other "sqlnet.ora" files being used. If this does not resolve the issue, use the move command to put all the "sqlnet.ora" files back where they were before you made the change: % mv sqlnet.ora_save sqlnet.ora If moving the "sqlnet.ora" resolves the issue, then verify the contents of th e file: a) SQLNET.AUTHENTICATION_SERVICES If you are not using database links, comment this line out or try setting it to: SQLNET.AUTHENTICATION_SERVICES = (BEQ,NONE)
b) SQLNET.ora".ora listener.ora tnsnames.ora".sh " runs during installation. Set the permissions correctly in the "TNS_ADMIN" files.or a". If it is. run "root.3.ora 586 Jun 1 12:07 sqlnet.ora" file on UNIX.ora listener. you will need to reset the value of this environment variable: sh or ksh: ---------$ ORACLE_HOME=<path_to_ORACLE_HOME> $ export ORACLE_HOME Example: $ ORACLE_HOME=/u01/app/oracle/product/7.ora" files reside.ora b) Software and Operating System Issues: ---------------------------------------1. (This setting is added to the "sqlnet.ora tnsnames.CRYPTO_SEED This should not be set in a "sqlnet. The environment variable TNS_ADMIN defines the directory where the "sqlnet. These files must contain the correct permissions. this is the default behavior.ora 82274 Jul 12 15:23 tnsnames.ora -rw-r--r--rw-r--r--rw-r--r-1 oracle dba 1 oracle dba 1 oracle dba 1628 Jul 12 15:25 listener.ora".sh" or edit the permissions on the "sqlnet.ora" if it is built by one of Oracle's network cofiguration products shipped wi th client products) c) AUTOMATIC_IPC If this is set to "ON" it can force a "TWO_TASK" connection. Try setting this to "OFF": AUTOMATIC_IPC = OFF 2.Remark: on certain platforms. which are set when "root.3 $ export ORACLE_HOME csh: ---- .ora $ ls -l sqlnet. "tnsnames . comment the line out. and "listener. "tnsnames. As root.ora" files by hand as follows: $ cd $TNS_ADMIN $ chmod 644 sqlnet. and "listener. Be sure $ORACLE_HOME is set to the correct directory and does not have any typing mistakes: % cd $ORACLE_HOME % pwd If this returns a location other than your "ORACLE_HOME" or is invalid.
% setenv ORACLE_HOME <path_to_ORACLE_HOME> Example: % setenv ORACLE_HOME /u01/app/oracle/product/7. ksh or on HP/UX only csh: ----------------------------env grep -i two .or TWO_TASK=PROD You will need to unset the environment variable "TWO_TASK": sh or ksh: . Otherwise you may be able to connect internal but you will receive an ORA-01034 "Oracle not available" error. Ensure $TWO_TASK is not set.3. Check that $ORACLE_SID is set to the correct SID. In most cases using a link as part of your "ORACLE_HOME" is fine as long as you are consistent.3 /u01/app/oracle/7.3 % svrmgrl SVRMGR> connect internal If this prompts for a password then most likely the combination of your "ORACLE_HOME" and "ORACLE_SID" hash to the same shared memory address of another running instance. and does not have any typos: % echo $ORACLE_SID Refer to Note:1048876. 2. An example of this might be: You have "ORACLE_HOME" set to "/u01/app/oracle/product/7. the instance may try to start using the memory location that another instance is using.3 If your "ORACLE_HOME" contains a link or the instance was started with the "ORACLE_HOME" set to another value.6 for more information. (including capitalization).3 % setenv ORACLE_HOME /u01/app/oracle/7.or echo $TWO_TASK csh: ---setenv grep -i two If any lines are returned such as: TWO_TASK= . To check if "TWO_TASK" is set.3" and start the instance.3. but their use is supported. Then you do something like: % ln -s /u01/app/oracle/product/7.3.3. 3.3. do the following: sh. Oracle recommends that links not be used as part of the "ORACLE_HOME".
do the following as the "oracle" software owner: % chmod 6751 oracle If you receive an ORA-03113 "end-of-file on communication" error followed by a prompt for a password. it will issue the ORA-03113 error. All rights reserved.1. "osdba" group checks: .---------unset TWO_TASK csh: ---unsetenv TWO_TASK Example : $ TWO_TASK=V817 $ export TWO_TASK $ sqlplus /nolog SQL*Plus: Release 8.0 . When Oracle cannot do this (either because of permissions or because of the "alert. Check the permissions on the Oracle executable: % cd $ORACLE_HOME/bin % ls -l oracle ('ls -n oracle' should work as well) The permissions should be rwsr-s--x. you should also unset two_task.0.log" being greater than 2 Gigabytes in size). or 6751.log" file in "udump". group dba.4.7. 5.log must not be greater than 2 Gigabytes in size. (or the appropriates name s for your installation). Permissions should be: 755 (drwxr-xr-x) Also. If you are running Oracle release 8.0. When you start up "nomount" an Oracle pseudo process will try to write the "alert. then you may also need to check the ownership and permissions on the dump directories.Production on Fri Dec 31 10:12:25 2004 (c) Copyright 2000 Oracle Corporation. the alert. 4. The login connect string may be getting its value from the TWO_TASK environment variable if this is set for the user. If the permissions are incorrect. and upon starting "svrmgrl" you receive an ORA-06401 "NETCMN: invalid driver designator" error. SQL> conn / as sysdba ERROR: ORA-01031: insufficient privileges $ unset TWO_TASK $ sqlplus /nolog SQL> conn / as sysdba Connected. These directories must belong to Oracle. This error may occur while creating a database.
1 section 3 for more details. Another possible cause for ORA-01031 is very long lines in /etc/group. The "root" user is a special case and cannot connect to Oracle as the "internal" user unless the effective group is changed to the "osdba" group .s" or "$ORACLE_HOME/rdbms/lib/config. so you cannot issue "newgrp" from within a shell script. b.oracleas Potential causes for problems are multiple entries for the same group or o racle user in the /etc/passwd file. Keep this in mind if you plan on executing scripts as the "root" user. c.a. a proper entry lo oks like: dba::108:oracle. verify that t he "osdba" group is only listed once in the "/etc/group" file and that the us ers belonging to the dba group are properly comma separated. Refer to entry Note:50507. . Check for any errors in the /etc/group and /etc/passwd file.o .1 section 3 for more details. do the followin g: % id uid=1030(oracle) gid=1030(dba) The "gid" here is "dba" so the "config. d. To verify the operating system groups the user belongs to.c". or modify the "config" file and relink the "oracle" binary. To do this. This problem may also occur on other Uni x systems. Typically this is set to "dba". typically a Unix/ Linux kernel will only take the first one into consideration.o also causes this to fail. and "LOGNAME" are not set to "root".ascii "dba\0" If these do not match. Sun support suggests the /etc/group line should be at most 512 characters including the new line character. Make sure the operating system user issuing the CONNECT INTERNAL belongs to the "osdba" group as defined in the "$ORACLE_HOME/rdbms/lib/config.c" may contain an entry such as: /* 0x0008 15 */ . A corrupted config. which is typically "dba". you either need to add the operating system user to the group as it is seen in the "config" file. "USERNAME". Be sure you are not logged in as the "root" user and that the environment variables "USER". either modify the "/etc/password" file (not recommended) or use the "newgrp" command: # newgrp dba "newgrp" always opens a new shell. Refer to entry Note:50507. Regenerate the config.s" or "config.
oracle In this case the "ID" of "1601" is owned by "oracle" and if there are no other instances running in most cases this can safely be removed: % ipcrm -m 1601 If your SGA is split into multiple segments you will have to remove all segments associated with the instance.e. 6. If there are other instances running. and this may * * cause database corruption. and you are not sure which memory segments belong to the failed . * * * * Please call Oracle Support Services for assistance * * if you have any doubts about removing shared memory * * segments.root 0x0eedcdb8 --rw-r----. as seen in this example. * * * ****************************************************************** If an instance crashed or was killed off using "kill" there may be shared memory segments hanging around that belong to the down instance. you will need to unmount the filesystem and mount it without the "nosuid" option. Check that the oracle user uid and gid are matching with /etc/passwd and /etc/group : $ id uid=500(oracle) gid=235(dba) $ grep oracle /etc/passwd oracle:x:500:235:oracle:/home/oracle:/bin/bash ^^^ $ grep dba /etc/group dba:x:253:oracle ^^^ This type of mismatch will also causes an ORA-1031 error. Consult your operating system documentation or your operating system vendor for instruction on modifying mount options. If there are no other instances running on the machine you can issue: % ipcs -b T ID Shared Memory: m 0 m 1601 KEY MODE OWNER GROUP root dba SEGSZ 68 4530176 0x50000ffe --rw-r--r-. Please read the following warning before you attempt to use the information in this step: ****************************************************************** * * * WARNING: If you remove segments that belong to a running * * instance you will crash the instance. 7. Verify that the file system is not mounted no set uid: % mount /u07 on /dev/md/dsk/d7 nosuid/read/write If the filesytem is mounted "nosuid".
do the following: Check your "pfile". Reboot the machine. then create one. size = 4308992 Note the "Shmid" for Oracle8 and "Seg Id" for Oracle7 for each running inst . You are looking for the parameter "audit_file_dest". otherwise if this directory exist but is not writable. By process of elimination find the segments that do not belong to an instance and remove them.instance.Shared Seg Id Address 2016 80000000 Total: # of segments ance. the second default value for the directory is: $ORACLE_HOME/rdbms/audit (this is the only default directory for pre 10. from version 10. Shut down all the instances on the machine and remove whatever shared memory still exists that is owned by the software owner.ora" file has the "ifile" parameter set. If the "init<your_sid>. It is typically in the "$ORACLE_HOME/dbs" directory and will be named "init<your_sid>. where "<your_sid>" is the value of "ORACLE_SID" in your environment. change to that directory. otherwise change to the default directory . b. you can do the following: a. 8.3.2 RDBMS versions).ora.2 onwards the first default value for parameter AUDIT_FILE_DEST is: $ORACLE_BASE/admin/$ORACLE_SID/adump. containing Subareas 0-0 Total size 000000000000b8c0. Alternatively retreive the parameter by typing: show parameter audit_file_de st . you will also have to check the included file as well.3 or newer. If you are prompted for a password and then receive error ORA-09925 "Unable to create audit trail file" or error ORA-09817 "write to audit file failed". c. that it is also writab le. If your Oracle software is release 7. you can connect into each instance that is up and identify the shared memory owned by that instance: % svrmgrl SVRMGR> connect internal SVRMGR> oradebug ipc In Oracle8: ----------Area #0 `Fixed Size'. If "audit_file_dest" is set. If not any of the default directories exist. Ensure that yo u have memory -------------Size 4308992 = 1. an error ORA-09925 "Unable to create audit trail file" is raised. along with "SVR4 Error: 28: No space left on device". Minimum Subarea size 00000000 Subarea Shmid Size Stable Addr 0 7205 000000000000c000 80000000 In Oracle7: -----------------------. Make sure that if the first default directory exists.
so. For C-shell. you need to verify the settings for "ORA_NLS". You need to ensure that "ORACLE_HOME" and "LD_LIBRARY_PATH" are set correctl y.2 is installed. and you are attempting to have it coexist. You will need to consult your Installation and Configuration Guide for the proper settings for these environment variables.enough space to create the audit file. type: $ $ $ $ LD_LIBRARY_PATH=$ORACLE_HOME/lib export LD_LIBRARY_PATH ORACLE_HOME=/u01/app/oracle/product/8. Verify environment variable settings. and receive a TNS-12571 "packet writer failure" error. verify you can write to the directory: % touch afile If it could not create the called "afile". Ensure that the disk the instance resides on has not reached 100% capacity. this may be the cause of 'connect internal' prompting for a password. "ORA_NLS32". you are running the "startup. "ORA_NLS33" or "NLS_LANG". 1" being used at runtime.1: oracle_home/bin/svrmgrl fatal relocation error symbol not found kgffiop RDBMS v7.4 For Bourne or Korn shell. If you have installed Oracle software and are trying to connect with Server Manager to create or start the database.0. The audit file is generally 600 bytes in size. RDBMS v8. If it does exist. If connect internal prompts you for a password and then you receive an ORA-12705 "invalid or unknown NLS parameter value specified" error.4 export ORACLE_HOME 12.3. 10.6 11.4 is a separate "oracle_home". If in SVRMGRL (Server Manager line mode).0.sql" script and receive the following error: ld:so. % df -k If it has reached 100% capacity. Additional disk space will need to be made available before 'connect interna l' . type: % setenv LD_LIBRARY_PATH $ORACLE_HOME/lib % setenv ORACLE_HOME /u01/app/oracle/product/8. This is due to the wrong version of the client shared library "libclntsh. you need to change the permission s on your audit directory: % chmod 751 9. please refer to Note:1064635.0.
this can happen if the host . Check permissions on /etc/passwd file (Unix only). Check the /etc/hosts file (Unix only). 14. otherwise it defaults to the use of the file orapw that consequently causes access proble ms for any other database that has the parameter set to shared. First check the permissions to make s ure the file can be read at all.1. Set the parameter REMOTE_LOGIN_PASSWORDFILE to shared for all instances that share the common password file and create an exclusive orapw<sid> password files f or any instances that have this set to exclusive.2.Production on Sat Sep 21 16:21:18 2002 Copyright (c) 1982.0.1 13.2 and 7. 8192) lwp_mutex_wakeup(0xFF3E0778) lwp_mutex_lock(0xFF3E0778) time() open("/etc/passwd". ERROR: ORA-01031: insufficient privileges Trussing sqlplus will show also the problem: 25338: 25338: 25338: 25338: 25338: 25338: munmap(0xFF210000. Oracle Trace is enabled by default on 7. 2002.1 for more details. O_RDONLY) getrlimit(RLIMIT_NOFILE.0 . be sure that if an instance has REMOTE_LOGIN_PASSWORDFILE set t o exclusive that the file $ORACLE_HOME/dbs/orapw<sid> does exist. 15. All rights reserved.dat files in $ORACLE_HOME/otrace/admin director y.3. Oracle Corporation. connect internal fails with ORA-1031.3.will work.3 (depends on platform) This can caused high disk space usage by these files and cause a number of apparently mysterious side effects. If Oracle cannot open the password file. When you get ora-1031 "Insufficient privileges" on connect internal after yo u supply a valid password and you have multiple instances running from the sam e ORACLE_HOME. Example: -------# chmod 711 /etc/passwd # ls -ltr passwd -rwx--x--x 1 root sys 901 Sep 21 14:26 passwd $ sqlplus '/ as sysdba' SQL*Plus: Release 9. It is possible 'connect / as sysdba' succeeds b ut a subsequent startup command fails with ORA-01031. since Oracle is not able to verify if the user trying to connect is indeed in the dba group. For additional information refer to Note:97849.dat and regid. Delete process. See Note:45482. 0xFFBE8B28) = 0 = 0 = 0 = 1032582594 Err#13 EACCES = 0 16.
Oracle cannot read the file. 2.name_service_door" has incorrect permissions.name_service_door" (permission denied). This file is a flavor of IPC specific to Solaris which Oracle software is usi ng This can also cause connect internal problems. See entry Note:1066589.name is not properly configured in /etc/hosts. then you do not have the correct OS privileges to issue a connect internal. You may also receive errors such as: ORA-12705: ORA-01012: LCC-00161: ORA-01031: invalid or unknown NLS parameter value specified not logged on Oracle error (possible syntax error) insufficient privileges Refer to entry Note:1027964. successive connect internal attempts might prompt for a password. by updating the /etc/hosts file wi th a host name that includes a fully qualified domain name this issue can be reso lved. This problem occurs when using Parallel Server and the True Cluster software together. then ORA_DBA needs to be removed and granted again to be updated. On Solaris. if the file "/etc/.6 6. svrmgrl works as expected. running SVRMGRL (Server Manager line mode). You will receive a message that "The Oracle user cannot access "/etc/. You are on Digital Unix. 5. and you receive an ORA-12547 "TNS:lost contact" error and a password prompt.6 for more details.6 for more details. On OpenVMS. If Parallel Server is not linked in. Please refer to Note:1010852. If you are using Multi-Threaded Server (MTS). A dedicated server connection is required to start up or shutdown the databas e.6 for suggestions on how to resolve this problem 4. or ORA_DBA. .ORA" file includes a parameter to make a dedicated server connection. check if DBA_AUTHORIZATION is set to BYPASS in the registry. See Note:1058680. c) Operating System Specific checks: -----------------------------------1. check that the privileges have been granted at the Operating Syst em level: $ SET DEFAULT SYS$SYSTEM: $ RUN AUTHORIZE If the list returned by AUTHORIZE does not contain ORA_<SID>_DBA. Unless the database alias in the "TNSNAMES. If ORA_<SID>_DBA was added AFTER ORA_DBA. make sure you are using a dedic ated server connection. if you are able to connect internally but then startup fails for some reason. On Windows NT. 3. On Windows NT. it will make a shared connection to a dispatch er.
2. you should refer to entr y Note:1040607.6 8. then you need to: 1.a grep adjust If this returns nothing. that is connecting via anything except the bequeath adapter. Obtain the patch for TCR 1.a. They are as follows: 1) Use mkpasswd command to remove the index. there is a note that sta tes: If REMOTE_OS_AUTHENT is set to true.5 requires an Operating System patch which previous versions of Oracle did not require. On AIX 4. There is two workarounds and one solution.3.X '/ as sysdba' does not work as well.0.2 of the Silicon Graphics UNIX (IRIX) operating system and you have recently installed RDBMS release 8. Relink Oracle Another possibility is that you need to raise the value of kernel parameter per-proc-stack-size when increased from its default value of 2097152 to 83886080 resolved this pr oblem. This patch is for the MC SCN and adds the symbol "adjustSequenceNumber" to the library /usr/ccs/lib/libssn. You are on version 6. 3. In the "Oracle7 Administrator's Reference for UNIX".0.Oracle V8. you will be prompted for a password regardless . This is a known AIX bug and it occurs on all RS6000 ports including SP2. if you are connecting remotely. However. users who are members of the dba group on the remote machine are able to connect as INTERNAL without a password. Apply the patch. If you are logged on as "oracle/dba" and an attempt to log in to Server Manag er using "connect/internal" prompts you for a password. d) Additional Information: -------------------------1. This is valid until a new user is added to "/etc/passwd" or modified: # mkpasswd -v -d 2) Touch the "/etc/passwd" file.3 after applying ML5 or higher you can not longer connect as inter nal or if on 9.5 from Digital. If the "/etc/passwd" file is newer than the index it will not use the password file index: # touch /etc/passwd 3) Obtain APAR IY22458 from IBM. 7. You can determine if the patch is applied by running: % nm /usr/ccs/lib/libssn. Any questions about this APAR should be directed to IBM.3. The above patch allows svrmgrl to communicate with the TCR software.
6 ORA-00106 or ORA-01031 ERROR when trying to STARTUP or SHUTDOWN DATABASE Note:1066589.of the value of "REMOTE_OS_AUTHENT".1 UNIX: Connect INTERNAL / AS SYSBDA Privilege on Oracle 7/8 Note:242490.Enterprise Edition Keywords BEQ. ORA-3113.1 How to properly configure the "/etc/hosts" file on Linux Bug:644988 REMOTE_OS_AUTHENT=TRUE: NOT ALLOWING USERS TO CONNECT INTERNAL W ITHOUT PASSWORD Search Words: ~~~~~~~~~~~~~ svrmgrm sqldba sqlplus sqlnet remote_login_passwordfile Show Related Information Related Products * Oracle Database Products > Oracle Database > Oracle Database > Oracle Serv er . ORA-6401.0. ORA-9925 Back to topBack to top Rate this document Article Rating Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy .6 LCC-00161 AND ORA-01031 ON STARTUP Note:1058680.6 SGI: ORA-01012 ORA-01031: WHEN USING SRVMGR AFTER 8. Refer to bug 644988 References: ~~~~~~~~~~~ Note:1048876.1 SYSDBA and SYSOPER Privileges in Oracle8 and Oracle7 Note:18089. OBJECT PRIVILEGES.3 INSTALL Note:97849. ORA-1034.6 UNIX: Connect Internal asks for password when TWO_TASK is set Note:1040607.6 UNIX: Connect internal prompts for password after install Note:1064635.6 ORA-12571: PACKET WRITER FAILURE WHEN STARTING SVRMGR Note:1010852. ORA-1031.6 OPENVMS: ORA-01031: WHEN ISSUING "CONNECT INTERNAL" IN SQL*DBA O R SERVER MANAGER Note:1027964. ORA-9817. PASSWORD Errors LCC-161. ORA-12705.1 Connect internal Requires Password Note:50507. ORA-1012.
Please use 'Contact Us' for other feedback.Comments Provide feedback for this article. Cancel . Important Note: this feedback is anonymously visible to other customers until pr ocessed by Oracle Support.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.