I have a Oracle Database 12C and, when i do the following query on SYS schema
select * from all_users;
i get listed USER_X.
However, when i try to alter USER_X's password, by doing the following
ALTER USER USER_X IDENTIFIED BY XPTO_123;
i get the error
SQL Error: ORA-01918: 01918. 00000 - "user '%s' does not exist"
Am i missing something?
Thanks
How was the 12C database installed? Does it uses the "Multitenant" architecture?
If so, alter the user's password may differ for CDB and PDB.
You can refer to this and this links for more infos.
Related
This question is for those who have experience with Adempiere ERP.
when logging in, I get the error table ad_system is not found. connecting to Postgresql I can see the database along with the table name. not sure why it says so. anyone else experienced the same issue?
my Postgres user does have superuser permissions
[error message on login]
Try to query the database to see if it has data or if it's empty, for example:
SELECT * FROM AD_System
or
SELECT * FROM C_BPartner
That error usually appears when you do a bad DB restoration and the DB Tables are empty.
I create user with
CREATE USER "C##XXXXX" IDENTIFIED BY "PasWordorSomthingLikeThat"
DEFAULT TABLESPACE "XXX_TABLE_SPACE"
TEMPORARY TABLESPACE "XXX_TABLE_SPACE_TEMP";
but from oracleSqlDeveloper I can't login into my user And find ORA-01017 Invalid Username/Password when connecting to 11g database from 9i client but he said to change security!
is that oracle set this option for the access database useless? what can i do to login my oracle database without change security parameters?
error:
ora-01017 invalid username/password
The parameter mentioned in your link is not valid for 19c. Try not using quotation marks in your create user command:
CREATE USER C##XXXXX IDENTIFIED BY PasWordorSomthingLikeThat
DEFAULT TABLESPACE XXX_TABLE_SPACE
TEMPORARY TABLESPACE XXX_TABLE_SPACE_TEMP;
And double-check your connect string to make sure you're connecting to the right CDB or PDB for the account.
I'm getting error "no permission for read/select access to DATABASE" when I try to connect to a Firebird database with a user different than SYSDBA, lets say user SOM.
If I create a new database with SYSDBA on the same server, then grant access to the objects there to SOM, it is connecting without problem, but for this particular database - not. I tried to give all rights, including to the system objects to SOM (I'm using the great IBExpert where this is possible), no success.
c:\Program Files\Firebird\Firebird_2_5\bin>isql -user SOM -password secret
Use CONNECT or CREATE DATABASE to specify a database
SQL> connect "c:\data\data.fdb";
Database: "c:\data\data.fdb", User: SOM
SQL> select * from exampletable ;
Statement failed, SQLSTATE = 28000
no permission for read/select access to DATABASE
Command error: select * from exampletable
I was unable to find way to grant anything to object DATABASE.
What could be the reason is that the problematic database was restored via gbak, version 2.5 from Firebird 3 database (downgrade on this way from Firebird 3 to 2.5).
A possible solution is to restore the database with user SOM, but I don't want that the user SOM is the owner of the database. If I do a backup and restore with SYSDBA, the same problem comes back again.
Solution provided in the firebird-support mailing list:
Attach as SYSDBA and run
UPDATE RDB$DATABASE SET RDB$SECURITY_CLASS = NULL
have you tried gbak from 2.5 to BACKUP FB 3 database?
FB 3 running
place gbak from 2.5 to fb 3 folder, as gbak25. Or, do as you wish, but gbak from 2.5 need to use fbclient.dll from 3.0
gbak25 -b -g -v db.fdb db.fbk -user ... -pass ...
then restore this backup on 2.5.
Below command used for connecting database through Firebird SQL.
CONNECT "C:\Users\vkaja\Desktop\testing_mysql\newdb.db"
In newdb.db file Schema, data are dumped from SQLite.
Here newdb.db has read-write permission. But error projected here is not a valid username and password.
Statement failed, SQLCODE = -902
Firebird doesn't care about the extension of the database file. fdb is 'standard', and gdb is historical, but it could be anything. However the database you are connecting to must be a Firebird database. You can't just open a database file from a different database system (eg SQLite).
Your problem is one of authentication: you are trying to authenticate without a username + password combination, and if you haven't set the appropriate environment variables, it means Firebird tries to authenticate with an empty user and password, which doesn't exist for your Firebird install. In general you also get this error if you use a username and password that is not known to Firebird.
But even if you fix the authentication problem, you would immediately get a different error: invalid database (or similar), because the file is not a Firebird database.
I am using Oracle 11g client 32bit on all my servers and i have proceeded with all the dump imports the very same way I am doing here.
Firstly I create the user with default tablespace
Secondly I alter the user quota unlimited on tablespace
Thirdly I grant connect resource dba to the user.
Then I exit from Oracle and this is my import command
C:\Users\romit.poladiya>imp fajbdummy/fa#dmate file='E:\dump\fajblatest.dmp' full=Y;
I have always been doing this and I do not know why I have not been able to import this time. Please assist. Let me know if you require any more information
Thanking the team in advance,
Romit
ORA-01017: invalid username/password; logon denied
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Cure: Use the correct username & password. Check the system to make sure that the username exists, and set the password if necessary.
The following issue can be closed as I was able to do the tnsping but unfortunately my oracle went into an Idle Instance while I was connecting. Earlier it was not an issue and I have no idea whatever happened and the the oracle just went into Shutdown