Use the area above the neck to solve the problem (1): Sqlplus Landing Report No permissions error

For a variety of reasons, for a long time did not come here to publish their articles. Some time ago encountered an interesting question, embarrassed me a whole afternoon, here write to share with you.

When you use the Sqlplus tool to log in to an Oracle database as a SYSDBA, you suddenly encounter an issue with no permissions. It felt very strange at that time, this machine landing command: Sqlplus/as sysdba I understand is the most insurance of a landing method. How does it report no permissions? A little sweating on the head. After half an afternoon of fiddling still without fruit, now think of it was a mess! There is no way to infer the problem from the principle, just a random test, no result is reasonable. Calm down after thinking, finally cleared up the idea, this way of landing is to walk the operating system certification, you can eliminate the impact of monitoring failure. Verify that the Sqlplus sys/xxx as SYSDBA command is logged in normally, eliminating the possibility of a password file exception. Then the requirements of the operating system certification is the UID and GID and user name Group name correctness, I will use the ID command to look at, sure enough, the Oracle User ID and user name corresponding to normal, can GID and group name does not correspond, only show the GID does not display the group name. What is this for? Curious Strange! Think of the UNIX system GID and group name corresponding relationship from where, the answer in front of the/etc/group file, right! That's him! Check his permissions found that, in addition to the root user and the root group has read permissions, other users are not, how can this? Prove that Oracle users cannot read the contents of the file at all! No wonder the Oracle user under the Execute ID command cannot see the group name of the GID. Modify the file permissions correctly, chmod a+r/etc/group. Again into the Oracle user view, the ID command appears normal. Through the Sqlplus/as SYSDBA can log in normally, and no longer prompt no permission.

That's it! Anything that is not inferred from the principle will not be solved, but may make things worse!

This article is from the "cultural Rogue dba Life" blog, reprint please contact the author!

Use the area above the neck to solve the problem (1): Sqlplus Landing Report No permissions error