I am new to Oracle. I did a fresh installation of Windows 7 x64 on my laptop to install Oracle 12c Enterprise Edition (for learning purpose).
While on admin windows account, I first made a standard windows user with a password to use during the installation. The installation went fine as well as the creation of default ORCL database. The only warning I got was "The selected Oracle home is outside of Oracle base" which I fixed by going back to directories option and setting the directory from "Admin Name" to "Oracle" and it adjusted all directories according to "Oracle" name (I found this solution on internet).
Now after system restart, I am trying to connect to ORCL database using username and password I defined in setup and it just keeps telling me that my logon is incorrect "ora-01017 invalid username/password logon denied" whether I use SQL Developer or SQL Plus command line ?
I have tried searching on internet and didn't find anything much useful or say it's too technical that I don't understand, can anyone explain in simple way that what should I do to make this thing work ?
Thank you and sorry if I sound frustrated, I did this installation twice on Windows 8 which led to errors in my OS then switched Windows 7 and now this third installation is also leading to this error.
Open SQL Plus and type this "Sys as SYSDBA" for username and don't type any password and it will automatically connected.
Enter user-name: Sys as SYSDBA
Enter password: (don't need)
Screenshot
http://i.stack.imgur.com/E4seR.png
remember password is case-sensitive by default, maybe this could be your problem.
in oracle 11g and 12c this parameter is case-sensitive., so check your password and write it as you created.
try to login with a user that have CONNECT grant. sys or system should work.
I can relate since I went through the same thing recently. Under Windows 10 (2020).
In my case, I use Spanish language computers, and by default, Oracle 12c for Windows expects an ENGLISH language character set or whatever.
SOLUTION: Go to Windows Regional Settings and select English as the default "regional format". In my case I went with "Spanish (United States)". Then restarted SQL Developer and BOOM: No more cryptic "ora-01017" errors!
GOOD PRACTICE: I only added "SYS" as SYSDBA to connect for the first time (since I have no other users YET). From the much-expected SQL Developer's Worksheet (SYS as SYSDBA) I created a "normal" user. Then, I created a "default (normal)" connection profile for that new user and started doing DDLs from that connection.
It works flawlessly from there. Hope it helps in your case!
Related
I'm following the below tutorial to install Oracle business intelligence 12c on Linux 7.7
,my Oracle database is already installed and working fine.
http://bisoftdiary.com/obiee12c_linux_installation/
when I run the script ./config.sh
after reach to this step it says ensure the database is compatible,I really don't understand what is wrong with my database ?
I have passed the issue by making the password more complex, but unfortunately the error message doesn't tell me the issue with my password ,it should mention clearly the issue with my password so I can correct it.
I'm in the process of setting up a new laptop for application development work and today I installed SQL Server 2017 Developer Edition on this computer. I used the Basic install option rather than the Customize install option. Some pertinent facts:
operating system is Windows 10
device name is MARIGOLD
administrator on this computer is an e-mail address and the characters that appear before the # symbol for the e-mail are knot22
When the confirmation screen was displayed after installing SQL Server, it showed the SQL Administrator as MARIGOLD\knot2 (see red line that points this out in screenshot). Notice that there is a 2 missing - was was expected was MARIGOLD\knot22. Why did it chop off the user name? Is there a way to fix this?
Your username on the computer is "knot2".
This may not match the display name.
The following procedure will lose all stored credentials. You may lose program data, bookmarks contact lists... as well as some file permissions
The easiest way to solve this is to:
Create a temporary admin account, Grant the account all privileges in SQL Server.
Login as that user.
Backup the entire C:\users\knot2 directory(including hidden and system files). You may have to reboot to do this.
Delete the "knot2" user.
Create "knot22" user.
Grant the "knot22" account all privileges in SQL Server.
Copy the backup of C:\users\knot2 into C:\users\knot22
Remove or disable the temporary user.
It is up to you to figure out if it is worth it or not.
I installed HANA Express in a VMware Workstation environment, and also Eclipse 4.6 with the HANA administrator plugin. Both VMWare and Eclipse run on Windows 10. I can start HANA with no issues, however when I try to connect from the Eclipse plugin the connection fails.
The tutorial to configure the HANA administrator plugin in Eclipse instructs to enter SYSTEM as user and then a password. The problem is that in the HANA Express tutorial the only user that seems to be set up is the "database master" (see text below). Therefore, I don't have the SYSTEM password and I don't know the "database master" user (even though I know the password). How to make this work?
Step 3: Startup: Configuration Script
A configuration script will run if this is the first login. When prompted
for HANA database master password, enter a strong password.
Tip: Make a note of this password, since you’ll need it later. You can enter
the same password you used earlier, or a new password. If you are entering a
new password, see the password rules earlier in this tutorial.
XSA_ADMIN
XSA_DEV
XSA_SHINE
TEL_ADMIN
When prompted to Confirm “HANA database master password”, enter the strong
password again.
This is the error I get in Eclipse log:
The SYSTEM password is the same as the master database password for HXE. If that does not work, try HXEHana1
Also, I see you are trying to connect to instance number 00. If the HXE VM is 2.0 sps00 or higher, the default instance number is 90.
You can rule out connectivity problems by running the following from the Virtual Machine's console:
hdbsql -n localhost -i 90 -d SYSTEMDB -u SYSTEM
This will connect to your instance and prompt for the password for user SYSTEM so you can confirm which one is right before configuring HANA Studio.
I had the same issue.
I used user : XSA_ADMIN and the HANA password chosen as part of the tutorial.
Its now connected.
Regards
I have Oracle SQL Developer version 4.1.19 (64 bit) with JDK8 included.
This is working for Oracle connections which require a {username, password} combination - no problem there.
My issue is that I cannot connect with an OS Authentication configuration.
Please note that I can connect from the command line with OS authentication by using sqlplus /#MY_TNS_NAME and this works fine.
I have the SQL Developer application configured to use the OCI/Thick driver and also to use the x64 12.1.0.2.0 basic instant client. This seems to be configured ok in that if I check Help->About-Properties then sqldeveloper.oci.available has the value "true".
However, each time that I test the connection I receive the failure message
"ORA-01017: invalid username/password; logon denied"
My OS is Windows 7 Enterprise x64 SP1
I have obviously checked the option "OS Authentication" :).
Is there any other configuration that I need to change/check in order to get SQL Developer to allow me to connect via OS Authentication? (Changing the authentication type is not an option for me).
Thanks in advance.
Had the same issue. The cause is that SQL Developer's lightweight JDBC does not support extended authentication. SQL*Plus, to the contrary, is compiled against native driver, that's why it has no problem.
Solution: in SQL Developer, go
Tools -> Preferences -> Database -> Advanced Parameters
If you have Use Oracle Client already checked, just check Use OCI/Thick driver. That's all. If not, check Use Oracle Client first, and specify driver path. Idea was taken from here
Speaking about clients, Oracle allows to have a zoo of versions. If you have problems selecting working client, the cleanest option would be to use path where your SQL*Plus resides. Just strip \bin from its end, and make sure its CPU architecture matches SQL Developer.
Oracle Sql developer and sqlplus work with OS authentication in absolutely different ways.
Sql developer always tries to authorize by substituting to the user name "\".
SLQPLUS substitutes only the user name. When adding a domain to the user name.
OSAUTH_PREFIX_DOMAIN = TRUE (windows registry). Sqlplus appends the domain name to the name.
Sql developer always tries to authorize by substituting to the user name "\" without domain name.
Example 1.
CREATE USER "OPS$ORACLE.ADMIN" IDENTIFIED EXTERNALLY
PROFILE DEFAULT
DEFAULT TABLESPACE tablespace_oracle_admin
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON tablespace_oracle_admin
ACCOUNT UNLOCK ;
C:\ORA\DB\product\11.2.0\dbhome_1\bin\sqlplus /
SQL> Select user from dual;
USER
___________________
OPS$ORACLE.ADMIN
To connect from sql developer with the database, it is necessary to put the "/" symbol instead of the
user name without specifying a password.
Select user from dual;
USER
___________________
OPS$ORACLE.ADMIN
Example 2.
CREATE USER "OPS$\ORACLE.ADMIN" IDENTIFIED EXTERNALLY
PROFILE DEFAULT
DEFAULT TABLESPACE tablespace_oracle_admin
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON tablespace_oracle_admin
ACCOUNT UNLOCK ;
When connecting to using Sql developer, OS authentication work!!!!
Select user from dual;
USER
___________________
OPS$\ORACLE.ADMIN
Where are your Sqlnet.ora and tnsNames.ora files located?
I had to create an environment variable TNS_ADMIN with a custom location that contained my sqlnet.ora and tnsnames.ora files.
Make sure your sqlnet.ora file contains the line:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
You also need to ensure that the instant client location e.g. c:/instantclient12 is the first entry in your PATH variable.
What happens when you press the test button when setting the Oracle client location in sql developer?
Please find all the files I'm refering to at this link:
http://whyisthisinmyfood.com/sql/
I have installed a new copy of "SQL Server 2008 R2 Management Studio Express (x86)" on two Windows 7 computers. The SAME install file for both computers. Installed the same way. (as far as I know, I chose the same options)
One at home and one at work.
The one at home seems to work perfectly I "Execute" this file (ITD132-Inventory Initial with data.sql) and it works fine. When I "Execute" it at work I get:
Msg 262, Level 14, State 1, Line 1
CREATE DATABASE permission denied in database 'master'.
..and a bunch of stuff after that which is caused because the database was not created in the first place.
I have compared the permissions on both computers.
see these files:
home computer : non-networked.jpg
work computer: work-networked.jpg
I read in one post that to create new Logins one must be logged in as the Administrator. I log into the Server Managment studio with my windows credentials and I am the Local Admin for my work computer and I have not been able to find any other place to log in as an administrator for this SQL Server Management Studio (so clearly I'm not sure whats meant by that)
At this point I think my problem is that I need to create a user who is not just the "BUILTIN\User" (because this login does not have permissions) with permissions.
But I have no idea how to login as an administrator to create this user role.
Please forgive me if these are obvious answers as I am just starting with this MS Management studio and am not very familiar with T-SQL.
Thanks,
Diana
If you install SQL Server, you get asked during installation process which user or user group should have the Admin-Privileges. If your computer is part of a domain and you login locally, things might get complicated.
The easiest (but not safest way) to login as a "superuser" if to enable the "sa" user.
this is one user that logs on with a password (not integrated logon) and has all the juice to run every script possible :-) By default it's disabled - googling I found a easy how-to enable it:
http://sudeeptaganguly.wordpress.com/2010/04/20/how-to-enable-sa-account-in-sql-server/
I think you are correct that you need to create another user with enough permission. Generally logging in with "integrated security" using your Windows credentials should have enough permissions (assuming the same user is the user that installed SQL Server). If not, you have better luck logging in as the SQL Server user "sa" (system administrator) which should have full permission. Do you know the "sa" password?
Note: the security mode for SQL Server can be set to "Only integrated security with Windows users", "SQL Server security" or "both". The "sa" account will only work if the SQL Server security is enabled. You may be able to access these settings using your BuiltIn\User account.