| Oracle Financial Analyzer Installation and Upgrade Guide Release 11i Part Number A96137-01 |
|
This appendix provides information about the most common types of errors and the corresponding error messages that you may encounter as you start Financial Analyzer for the first time or use Financial Analyzer after upgrading.
This appendix includes the following topics:
If there is an error in connecting to Express, you may receive the following message: "Cannot connect to Express."
The message "Cannot connect to Express" indicates that you are not able to make a connection to an Express Server session for one of the following reasons:
Username
Password
Domain, if required
Server, if required
UUID or EndPoint, if required
xpdb.db file is located in the oracle_home/OLAP/OES630/SERVICE/OEC630 directory. If the directory and file do not exist, they have not been installed. Install them. If the file exists, check the File I/O option in the Express Service Configuration Manager to verify that the ServerDBPath setting contains the oracle_home/OLAP/OES630/SERVICE/OEC630 directory. If it does not, edit the setting.
Log on locally right. Check with your network administrator to verify that this right has been set for the network ID.
If there is an error in attaching to the personal database specified in the Express Server Login, you may receive the following message: "Cannot attach to personal database because it cannot be found or it is already attached by another user."
The message "Cannot attach to personal database because it cannot be found or it is already attached by another user" indicates that you cannot attach to the personal database specified in the Express Server Login for one of the following reasons:
If there is an error in starting up a workstation, you may receive the one of the following messages: "Cannot attach the OFAS database" or "You are not a valid Oracle Financial Analyzer user."
The messages "Cannot attach the OFAS database" and "You are not a valid Oracle Financial Analyzer user" indicate that an error has occurred for one of the following reasons:
|
|
![]() Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|