ORA-12317: logon to database (link name string) denied
Answer / guest
Cause: There are several possible causes for this error.
First, you can get this error if your username (and
password, if you are using database instead of operating
system authentication) in the secondary database are not
identical to your username (and password) in the primary
database. Second, you can get this error if your username in
the secondary database is invalid (has not been created).
Third, you can get this error if the username/password
combination specified in the connect string of the database
link definition is invalid (either not created or has an
invalid password).
Action: In the first case, ensure that the secondary
database contains a username (and password, if you are using
database authentication) identical to the one you are using
in the primary database. In general, you should always use
operating system authentication in Trusted ORACLE (see the
Trusted ORACLE RDBMS Guide to Security Features for more
information about the advantages of OS authentication). In
the second case, ensure that your username in the secondary
database has been created. In the third case, ensure that
the username specified in the connect string has been
created in the secondary database.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-07346: slnrm: normalized file name is too long
QSM-01029: materialized view, string, is stale in ENFORCED integrity mode
PCB-00625: An indicator variable is not required with this attribute
ORA-16702: generic resource manager warning
ORA-29806: specified binding does not exist
IMG-00516: default channel out of range
ORA-12017: cannot alter primary key mview 'string' to a rowid mview
DRG-10836: field section and attribute section can not be nested
SQL*Loader-00106: Invalid discard file name on command line
ORA-13502: Cannot rename SYSAUX tablespace
QSM-01078: materialized view, string, is marked invalid
ORA-02234: changes to this table are already logged