Question: How do I
fix the REP-501 error in Oracle reports?
REP-501:
Unable to connect to the specified database.
ORA-01017: invalid
username/password; logon denied
Answer:
REP-501 typically means that Oracle*Reports is unable to
locate any available Oracle Databases. By default, Oracle
Reports will only look for available databases in
tnsnames.ora.
REP-501: Unable to
connect to the specified database.
Cause:
Reports Builder tried to but could not
connect to ORACLE. The possible causes of this error include
a case where Oracle is temporarily unavailable or your
connect information was not valid.
Action: Retry the connection and
check the network connectivity. Note that after three
attempts you will be disconnected from the SQL*Reports
server.
See MOSC document titled "REP-501 Error When Connecting to
Oracle Reports Using Externally Authorized User" ( Doc ID
162457.1 ).
Oracle SQL*Reports notes
that a common cause of this REP-501 error includes:
- TNS:
Check for a missing
entry in the tnsnames.ora file. The tnsnames.ora file in
located in the $OI/config location.
- Case
sensitivity parameter settings:
If the
SEC_CASE_SENSITIVE_LOGON=TRUE in the pile or spfile, Oracle will make the Reports log on credentials case
sensitive, and the report server will not be able to connect to
the database by default; and throw the REP-501 error.
You should set
SEC_CASE_SENSITIVE_LOGON=FALSE and
FORMS_USERNAME_CASESENSITIVE = 1 in
$ORACLE_HOME/forms/server/default.env .
-
Bad User ID or connect string: Run
the form in debug mode and find the username, password and
connect string. If you pass a command line with USERID=/
to the Reports Server, then a REP-501 error is generated because
it will try to use the username of the Reports Server
process rather than the username of the client.
- TNS_ADMIN:
Also check TNS_ADMIN. TNS_ADMIN may be pointing to a
directory where tnsnames.ora is missing or the values does
not match the connecting database service name, causing the
REP-501 error.
- ons.conf:
Also,
the Reports Server gives error REP-501 changing the "nodes"
value in the ons.conf file on the midtier server.
- Memory leak: Bounce the
servers to clean-up system.
- Bug: See
Bug 10100777: REPORTS ENGINE CRASH WITH REP-501
Follow these steps to check your connectivity in SQL*Plus:
-
Check with "ping" using the IP
address ("ping 198.11.34.43")
-
Check with "ping" using DNS name
(e.g. "tnsping uranus")
-
Try telnet to the IP on port 1521
(telnet 1.2.3.4 1521)
-
Check with "tnsping" using TNS
service name
-
Invoke SQL*Plus from the OS command
line "sqlplus fred@flintstone". If this fails,
check to ensure that your listener has the
flintstone service defined.
-
Sign-on to SQL*Plus and connect
with the TNS name ("connect fred/flintstome@service_name")
-
Within SQL*Plus, try a select from
table@remote_db_link
|
|
|
|
|
Oracle Training from Don Burleson
The best on site
"Oracle
training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!
|
|
|
|
| |
|
Burleson is the American Team
Note:
This Oracle
documentation was created as a support and Oracle training reference for use by our
DBA performance tuning consulting professionals.
Feel free to ask questions on our
Oracle forum.
Verify
experience!
Anyone
considering using the services of an Oracle support expert should
independently investigate their credentials and experience, and not rely on
advertisements and self-proclaimed expertise. All legitimate Oracle experts
publish
their Oracle
qualifications.
Errata?
Oracle technology is changing and we
strive to update our BC Oracle support information. If you find an error
or have a suggestion for improving our content, we would appreciate your
feedback. Just
e-mail:
 and include the URL for the page.
Copyright © 1996 - 2020
All rights reserved by
Burleson
Oracle ®
is the registered trademark of Oracle Corporation.
|
|
