During the install, the error "Failed to create service for Net8 Client" is displayed?
The source of the problem is unclear, but a workaround is to restart and Install again. We are still investigating and looking for a better solution.

What about "Some Oracle products are currently in use. Please stop all Windows NT services and quit applications that are using Oracle's products before proceeding with this install." window?
This issue is also under current investigation. It is most prevalent on Windows XP, although it has occurred on Windows 2000 PCs also.

Workaround 1: Rename C:\orant\BIN\CORE40.DLL to something else, ie. CORE40_old.DLL, reboot, run Installer again.

Workaround 2: Reboot in the Safe mode and run the installer.

Cause: What is known about the cause at this time: CORE40.DLL is used by Windows Network Services (svchost). The link is memory resident, therefore a reboot clears the link. The alternative of restarting in the Safe Mode does not start Network Services, so does not link to CORE40.DLL, so does not appear to be in use.

What about "A write error occurred while trying to copy ...SQLLIB80.DLL. Would you retry the operation, ignore the error, or allow the error to be processed by the installer?" window?
This is related to the above "services" issue. Follow Workaround 1 or 2 above.

"You need to install Administration Installation Guide 4.1.33f or later before installing this patch." window?
When installing the Discoverer 4.1.47 patch, double click “Oracle Discoverer 4.1.47.09.00” to reveal the subcomponents.
While depressing the Ctrl key, click each of the three subcomponents.
Note: Installing the parent process (Oracle Discoverer 4.1.47.09.00) results in this error.

BACK TO TOP

It doesn't work. "Failed to connect to database - ORA-12154: TNS: could not resolve service name."?
Verify C:\orant\NET80\ADMIN\SQLNET.ORA has been deleted.

"Failed to connect to mst3k:UVA ODS Specialist@ODS Failed to connect to database- ORA-12203: TNS: unable to connect to destination."?
VPN issue. VPN may not be running or Windows XP Internet Connection Firewall (ICF) could be on.

A ORA-12203 also results when the "Connect" field is left blank. Its normally "iODS".

"ORA-12222: TNS: no such protocol adapter."
Apparently the protocol adapter has been corrupted. One solution could be to reinstall Discoverer again. A shorter solution is to manually install the protocol adapter as follows:

Insert the Discoverer 4.1.37 CD, autostart or run e:\setup. The next screen should indicate:
Name: DEFAULT_HOME
Location: C:\orant
Click OK, Custom Install (bottom button), in left pane, double click Oracle Protocol Adapters, click (highlight) Oracle TCP/IP Protocol Adapters 8.0.6.0.0.
click Install button. Close. Reboot. Re-try Discoverer.

"ORA-12571: TNS: packet writer failure"?

There does not seem to be a single solution to this error. It’s a networking error that can be caused by many things. This list reviews some of the possible solutions.

1. Spyware – the most popular cause has been spyware, adware or other malware. Spyware is software that tracks your web surfing activities. Most popular cause results from visiting music download sites. Possible solution may be to install & run spyware cleaner products.

2. Firewall – there have been reports of the installation of ZoneAlarm (left Unconfigured) blocked network traffic to cause ORA-12571 error. This could be true of any misconfigured personal firewall. ZoneAlarm monitors individual program activity such that one program may have internet access and another denied. Ensure Discoverer is granted access.

3. Network – some blockages were the result of incorrect network configuration. At UVa, this is the least probable cause.

4. MacAfee and Panda Antivirus have been reported to block access and cause the ORA-12571 error.

Discoverer "Cannot create virtual memory swapfile".
The short/ quick fix is: have the Discoverer user go to Tools>Options > Cache tab and click on the Clear Cache Now button.

Here is what research reveals:
Discoverer can't create a cache file. So why not? It's assumed it used to work, so the temp directory and permissions are probably OK.
1. Is there disk space available where ever the cache is? (ie C drive)
2. Then, delete the cache and/or bump the size: Discoverer , Tools > Options > Cache tab and click on the Clear Cache Now button. The Cache Status field should then show, 0kb used in memory, 0kb used on disk.

~~~~~~~~~~~~~~~~~~~~~~~~~
Cause
There are four potential causes for this issue.
1. The temp directory specified in menu Tools > Options > Cache tab, does not exist.
2. The temp directory exists, but does not have enough space needed to run the queries.
3. The temp directory exists, has enough space, but the user does not have write access to this directory.
4. The cache needs to be cleared.

Fix
The following are solutions to each of the four causes.
1. In Discoverer Desktop go to menu option, Tools > Options > Cache tab and change the Disk Cache Directory to a valid directory on the server.
2. Add more space to the directory specified for the Disk Cache Directory.
3. Grant write access to the Disk Cache Directory for this Discoverer Desktop user.
4. In Discoverer Desktop go to menu option, Tools > Options > Cache tab and click on the Clear Cache Now button. The Cache Status field should show, 0kb used in memory, 0kb used on disk.

~~~~~~~~~~~~~~~~~~~~~~~~~
The default Discoverer settings (in the tools/options/cache tab)

Cache Memory = 20,000 (20MB)
Disk Cache = 4,000,000 (4MB)
Disk Cache Directory = a valid temp folder on their local drive, default location: C:\orant\DISCVR4\temp.

It still doesn't work.
Ensure C:\orant\NET80\ADMIN\TNSNAMES.ORA has been newly downloaded and is of file type "ORA", not TXT. Some browsers download the TNSNAMES.ORA file as a type TXT. The file type may not be visible if "Hide Extensions for Known File Types" is on.

BACK TO TOP

Error "Failed to connect to database -Unable to connect to Oracle Applications database: invalid username/ password."?
Incorrect password. To verify or set the password, log into the Oracle Applications from http://www.virginia.edu/integratedsystem/. Remember that the password in ODS is from the Oracle Applications on the previous day.

When you choose your Integrated System password, please do not include the characters $ or @. While these are acceptable characters for the Integrated System application, they will cause an error when you try to log in through Discoverer. It interprets the '@' as the beginning of the instance name. A decimal "." will cause failure when using Brio Query.

Error "Your password has expired"?
If you get the “Your password has expired” notice when logging on to the I.S. applications, you will be unable to log on to Discoverer until the day after you change your password in the I.S. applications. Discoverer will not lock you out unless your system password has expired. It will shutdown, however, after three failed attempts to log on. You will have to reopen Discoverer and try again.

Avoid using $, @, / or \ in your password. It is safest to avoid using any special characters.

This can be the result of an incorrect version. The version should be 4.1.47.
Discoverer is dietributed on two CDs: 4.1.37 and a patch to 4.1.47.
This version has been valid since spring of 2004 and will be valid until at least Spring 2007. (3/21/06)

But I just changed my password!
If a user changes their password today in Oracle applications, that new password won't be in affect in the ODS (using Discoverer) until tomorrow. The old password in the ODS is unchanged until tomorrow.

Why? Each night, a copy of the production database is copied to ODS (Operational Data Store). The passwords go with it. The password in ODS is yesterday's production password. That also applies to password expiration. Discoverer 4.1 will not allow access with an expired password. Discoverer 3.1 did not check the expiration.

Discoverer will not lock you out unless your system password has expired. It will shutdown, however, after three failed attempts to log on. You will have to reopen Discoverer and try again.

BACK TO TOP

Error "Unable to connect to mst3k:@ODS You do not have access to any End User Layer tables."?
Incorrect/ invalid Oracle responsibility. Users logging into the ODS should use an ODS responsibility, ie UVA ODS Specialist.

Double click on a local copy of a .DIS file opens old Discoverer 3.1.
If a user double-clicks on a local copy of a Discoverer report (DIS file type) via Windows Explorer to launch Discoverer and it opens the old 3.1 version, its a Windows file association problem.

To associate file type DIS with version 4.1:
Windows 2000: open Windows Explorer, Tools, Folder Options, File Types tab, click on DIS, click Change, Other, Browse to c:\orant\discvr4\dis4usr.exe, Open, OK, Close.
Windows XP: open Windows Explorer, Tools, Folder Options, File Types tab, click on DIS, click Advanced button, highlight "open" action, Edit, Browse to c:\orant\discvr4\dis4usr.exe, Open, OK, Close. (updated 3/26/04)

How to Uninstall Discoverer 3.1.
Most Oracle client tools and components are managed with the Oracle Installer. They are not usually available in the Windows Add/ Remove panel.

To remove Discoverer 3.1, click on Start, Programs, Oracle for Windows NT (includes Windows 2000 and XP), Oracle Installer. The right pane displays the installed components. Click to highlight the line"-Oracle Discoverer 3.1.36" (or 3.1.44) then click the Remove button. Upon completion, exit Oracle Installer. Some additional cleanup up may be required, such as removing desktop and taskbar icons.

Discoverer 3.1 does not need to be removed. It is independent of Discoverer 4.1.

Firewalls and the Win XP Internet Connection Firewall (ICF)
Firewalls are designed to restrict internet traffic. Some personal firewalls like ZoneAlarm and BlackIce can be configured to allow connectivity to Oracle systems. If misconfigured, they may block access.

Windows XP has a personal firewall called Internet Connection Firewall (ICF). It can restrict access to Oracle Applications.

Firewalls may be part of your departments IT security plan, but should you need to disable ICF: open My Network Places, click View Network Connections (left panel), right-click on Local Area Connection (or other connection as applicable), Properties, Advanced tab, and UNcheck "Protect my computer...", OK. Close all windows and restart the system.

How do I include Information Warehouse settings?
Information Warehouse settings have already been included in the TNSNAMES.ORA file.

Which Operating Systems are certified?
Microsoft Windows XP Professional, Windows 2000 SP4+, Windows NT 4.0 SP5 - SP6a, Windows 98. (Windows 95 has been De-supported)

MS Windows NT/ 2000/ XP "Power Users Group" or "Administrator" privileges are required for software installation.

Discoverer report run time notice: Discoverer gives you the option of warning you if a query will run longer than a certain number of minutes that you determine. Under the Tools menu, select Options, then select Query Governor, and see "Warn me if predicted query time exceeds," followed by a box. In version 11i of the Integrated System, the system will try to predict the run time of the query, and if it is longer than the number of minutes in the box, it will ask you if you still want to run the query. If you do not want to be asked this each time you run a query, set the number in the box higher.