1. Cannot connect to the database. "Invalid username or password"
Following are the probable causes for this error message:
a. The ADI Sign On (Security) has not been set up correctly (check this only
if this is a fresh install). Check the 3 cones on the bottom left of the
sign-on window and cross check :
GWYUID
FNDNAM
Connect String
Query on the database with help of DBA and check if the same are correctly
setup $FND_TOP/Secure/<hostname>_<instance name>.dbc (for Unix users)
b. The User name and Passwords have been modified in the main Applications
database (check this only for non-frequent users). Check with the DBA if the
username and password have been changed recently.
c. The file sqlnet.ora file does not have the NAMES. DIRECTORY_PATH set to
(TNSNAMES). Set NAMES.DIRECTORY_PATH to (TNSNAMES) in sqlnet.ora file in the
client PC
d. If you are on 11.5.3 or above, please apply "SERVER SIDE" pre-req patch
1779336. PLEASE NOTE THIS IS A SERVER SIDE PATCH AND IS PORT SPECIFIC.
e. After applying patch 1779336, if you still encounter the same error,
please upgrade to the latest version of ADI.
2. Cannot connect to the database. "Invalid username"
Verify that the username being entered is a valid username
and has not expired. If the username is determined to be correct
then you will need to deinstall and then reinstall SQL*Net.
To deinstall/reinstall SQL*Net:
a. Launch the Oracle Installer. Select your Oracle Home, location, etc.
b. On the right side of the Software Asset Manager you will see
the Oracle software that is currently installed. Select SQL*Net Client
and then click the [Remove] button.
c. On the left side of the Software Asset Manager screen, you will
see the choices available to you of products which can be installed.
Select SQL*Net Client then click the [Install] button. Note: If
you do not see SQL*Net Client on the left side, you will need
to select the [From] button and navigate to either the CD
or directory in which you can obtain this product.
This message could occur in a few different scenarios. The first
scenario is that the username is actually invalid. The second
cause of this problem is that SQL*Net is not making the correct
connection and will need to be reinstalled. The third (ADI 7 only)
is that you have not placed your TNSNAMES.ORA and SQLnet.ora in
both the %oracle_home%/network/admin and the %oracle_home%/net80/admin
directories on the local PC.
ORA ERRORS
----------
3. ORA-00942: table or view does not exist
Grant select access to APPLSYSPUB for FND_USER_VIEW and FND_USER :
Login to SQL*Plus as applsys/apps
SQL> grant select on fnd_user to applsyspub;
SQL> connect apps/apps
SQL> grant select on fnd_user_view to applsyspub;
Create synonyms in the APPLSYSPUB schema for APPS.FND_USER_VIEW and
APPLSYS.FND_USER :
Login to SQL*Plus as applsyspub/pub
SQL> create synonym fnd_user for applsys.fnd_user;
SQL> create synonym fnd_user_view for apps.fnd_user_view;
4. ORA-12545: TNS:Name lookup failure when signing on to ADI. You also
have oracle discoverer product installed.
If Discoverer has it's own copy of tnsnames.ora and sqlnet.ora in it's
directory structure, then find the files in the Discoverer structure --
look in the <discoverer_home>\Network\admin directory. After renaming the two
files, if they already exist in the following ADI directories, copy the ones
from Discoverer over into the ADI directories and test.
<adi_oracle_home>\network\admin & <adi_oracle_home>\net80\admin
AUTOMATION ERRORS
-----------------
5. You are trying to sign on to ADI and receive the following error:
Outline: MAINGLDI: DoSignOn
Source: oraGLDI32
Message: Object variable or width block variable not set
Error Number: 91
The Oracle Objects for OLE is conflicting or incorrect. To resolve this
problem, apply the following steps:
a. Bring up the Oracle Installer.
b. Select the Oracle Objects for OLE (ANY FOUND).
c. Hit the REMOVE button to deinstall these items.
d. Insert the ADI install CD.
e. From Oracle Installer, select the FROM button to find the CD-ROM.
f. Navigate to the appropriate folder for the platform and select the
.prd file for that platform (Window 95 or NT).
g. Select only the Oracle Objects for OLE (runtime) item.
h. Hit the INSTALL button.
i. When installed, exit Installer and reboot the machine.
6. You are trying to sign on to ADI and receive the following error:
Routine: MAINGLDI: DoSignOn
Source: GLDI32
Message Automation Error
Error Number - 2147417851
Check to see that the file NL80.DLL is in the <ADI_Home>\bin or system32 folder.
If it exists, test to ensure it is not corrupt ( See note:215800.1 How to
check for Incompatible Files)
7. After a number of consecutive responsibility changes within the same ADI
session, you receive the following error:
symptom: Routine: MAINGLDI: DoChangeResponsibility
Source: oraGLDI32
Message: Automation error
Error Number: -2147417851
The number of responsibility changes required before failure is generally three
or more. Bug 2537137 addresses this issue. This bug has been fixed in ADI 7.1.19.
Please upgrade to the latest ADI version.
8. You are trying to sign on to ADI and receive the following error:
An Upexpected error has occurred in ADI
Routine : MAINGLDI:DoSignOn
Source : oraGLDI32
Message: Automation error
Error Number: -2147417851
The NLS_LANG set on the desktop client does not match the one set on the database.
For example, if the NLS_LANG on the database is set to
AMERICAN_AMERICA.WE8ISO8859P1 on the database, it must also be set to
AMERICAN_AMERICA.WE8ISO8859P1 on the desktop client.
9. You are trying to sign on to ADI and receive the following error:
Procedure MainGLDI: DoSignOn
Source: oraGLDI32
Message: OLE Automation Error
ErrorNum: -2147417851
Make sure that no other Oracle applications are in use on the PC.
Start the Oracle Installer and check if there are two installed
components called 'Oracle Objects for OLE' and 'Oracle Objects for OLE
(runtime)'.
If they are installed, uninstall both of them and restart the PC.
Install ONLY 'Oracle Objects for OLE (runtime)' using the ADI CD or downloaded
ADI installation files. Restart the PC and try ADI again.
MISCELLANEOUS
-------------
10. ADI shows sysadmin responsibilities after applying patches 2782945,2778660
This issue has been fixed in patch 2921807. This patch is available for download
on metalink.
11. Trying to setup ADI in a RAC/TAF environment. Receiving error:
ORA 12197: TNS:keyword-value resolution error when trying to sign on to instance.
Is ADI supported in the RAC/TAF environment using load balance?
The setup for ADI is not supported. Following is the explanation:
ADI Development has done some preliminary investigation into the ADI tech stack
compliance to TAF. During discussions with the groups in Oracle that own
and maintain the client technology stack it was determined that one of the core
components is not TAF compliant. These facts and conclusion are presented for
the customer to consider.
1. Oracle Objects for OLE (OO4O) 8.0.6 which is used by ADI to connect to the
database does not support TAF connections.
2. OO4O introduced TAF support in 8.1.6.3.10 version.
3. ADI team has previously attempted to upgrade to a later version of OO4O
than 8.0.6 without success. It is thought that there are problems with the
Excel Macro environment in which case upgrading the tech stack is not be an
viable option.
Conclusion - The tech stack that ADI is currently certified against will only
allow non-TAF connections to be made.