Release Notes
September 2017
These release notes provide information about the Spotlight® on Oracle release.
Topics:
Spotlight is a powerful diagnostic and resolution tool for Oracle databases. Its unique user interface provides you with an intuitive, visual representation of the activity on your database. Graphical flows illustrate the rate at which data is moving between database components. Icons display the value of key statistics and metrics.
Spotlight on Oracle is used to diagnose the performance of Oracle instances running on individual host machines. It also includes the following products:
Spotlight on Oracle RAC requires additional licensing. It enables the diagnosis of Oracle databases on multiple host machines under the Real Application Clusters (RAC) architecture and additionally may include monitoring of Exadata systems depending on the license purchased.
Spotlight on Oracle 10.5
Spotlight on Oracle 10.5 is a maintenance release with no new functionality.
Spotlight on Oracle 10.4
Spotlight on Oracle 10.4 is a maintenance release with no new functionality.
Spotlight on Oracle 10.3.3
Spotlight on Oracle 10.3.3 is a maintenance release with no new functionality.
Spotlight on Oracle 10.3.2
Spotlight on Oracle 10.3.2 is a maintenance release with no new functionality.
Spotlight on Oracle 10.3.1
Windows 10: Windows 10 is a supported platform for the installation of Spotlight on Oracle and the Spotlight Diagnostic Server, and for monitoring.
Spotlight on Oracle 10.3
In-Memory Diagnostics: Spotlight now provides diagnostic information for In-Memory databases in Oracle and Oracle RAC. What is the cost to the database of enabling In-Memory? Has the right amount of memory been allocated to the In-Memory column store? To what extent is I/O being consumed by In-Memory activities? Drilldown further by segments, SQL, statistics and sessions.
The following is a list of issues addressed and enhancements implemented in this release.
Area | Resolved Issue | Defect ID |
---|---|---|
Top Sessions drilldown | Enhancement - Use the Filter icon to show/hide background type sessions. | SOO-2593 |
Time to Failure alarm | Enhancement - Now able to calculate mountpoint space by running a series of scripts. For more information, see https://support.quest.com/spotlight-on-oracle/kb/215461. | SOO-2583 |
I/O | summary drilldown | Corrected erroneous negative values to 0 when the "Consumer Group" category is selected. | SOO-1681 |
Hungarian Locale | Corrected source of Exception error when creating an Oracle RAC connection in the Hungarian locale. | SOO-2298 |
Live Connections display | Corrected a problem where sometimes the selected Live Connection is no longer listed on the left pane connection display. | SOO-1634 |
The following is a list of issues addressed and enhancements implemented in 10.4.
Area | Resolved Issue | Defect ID |
---|---|---|
Installation | Dependency on .Net 3.5 is now removed. Spotlight on Oracle is now dependent on .Net 4.0 or above. | SOO-2421 |
Monitoring | Spotlight on Oracle supports monitoring of Oracle 12.2. | SOO-2605 |
Alarms | Corrected a problem where the Array Fetch Alarms were raised when the Spotlight User was the only connected user to the database. | SOO-2592 |
On adding an alarm action to send an email when the alarm is raised, the content of the email has been cleaned of special characters making it much easier to read. |
SOO-2618 | |
Creating a connection |
Corrected a problem where click "View information about objects installed and privileges required by Spotlight " when creating an Oracle RAC connection with a new user resulted in an unexpected error. |
SOO-2560 |
General | Corrected problem causing unexpected error with message: Assertion failure (E:\Jenkins\jobs\SoO Nightly Build - from GIT\workspace\Spotlight\Source\MDK\components\SpotlightGraphics.pas, line 348) | SOO-2610 |
The following is a list of issues addressed and enhancements implemented in 10.3.3.
Area | Resolved Issue | Defect ID |
---|---|---|
Browse History | Corrected the source of an unexpected error (Interface not supported) when using the History Browser. | 2557 |
Spotlight user creation script | References to the QUEST_LUCY_COLLECTOR package have been removed from the Spotlight user creation script for Oracle 11gR2 and above. | 2569 |
Removed code involving the SYS obects (SYS.EXECUTE_IMMEDIATE and SYS.BUILD_XVIEW) from the Spotlight user creation script for Oracle 11gR2 and above. |
2568 |
The following is a list of issues addressed and enhancements implemented in 10.3.2.
Area | Resolved Issue | Defect ID |
---|---|---|
Spotlight Essentials | Corrected a problem on sign in to Spotlight Essentials from the Spotlight on Oracle client through a proxy server. | 2272 |
Tablespace Utilization drilldown | Corrected the source of an unexpected error ("Range check error") on the Disk Storage | Tablespace utilization drilldown. | 2481 |
General | Corrected the source of unexpected errors ("Integer overflow" Source 02041D9D) when using Spotlight functionality using a periodic timer like the slideshow. | 2488 |
Monitoring Unix Connections |
Corrected a problem where the memory value display was incorrect on the Spotlight on Unix home page for some Unix connections. This issue was related to Linux bug https://bugzilla.redhat.com/show_bug.cgi?id=1246379 |
2516 |
Top Sessions |
Corrected Overflow error in Top session drilldown. |
2510 |
Predictive Diagnostics | Corrected a problem where Predictive Diagnostics charts displayed no data. | 2517 |
Spotlight charts | Corrected a problem with the zoom functionality in Spotlight charts. | 2524 |
The following is a list of issues addressed and enhancements implemented in 10.3.1.
Area | Resolved Issue | Defect ID |
---|---|---|
Monitoring UNIX connections | Fixed a problem where no data was displayed for Disk Reads and Disk Writes when monitoring a Unix connection, AIX 7.1 server. | 2433 |
Monitoring Oracle connections | Fixed a problem on the Tuning | Memory Management drilldown page where Total Oracle Memory failed to accept a 6 digit number. | 2434 |
Fixed a problem on the Configuration & Memory | Buffer Cache drilldown page where no data was displayed in the buffer cache details grid when a non-default pool was selected. | 2437 | |
General | Resolved "Integer Overview" issue. | 2430 |
The following is a list of issues addressed and enhancements implemented in 10.3.
Area | Resolved Issue | Defect ID |
---|---|---|
Slideshow | You can now configure the Slideshow to remain active through mouse or keyboard activity. | 2300 |
Licensing | Spotlight on Oracle can now accept licensing per monitored instance. | 2323 |
Spotlight Web Publisher | The Spotlight Web Publisher is now merged into the Spotlight Diagnostic Server. In previous releases of Spotlight on Oracle the Spotlight Diagnostic Server and Web Publisher were both required to use Spotlight Mobile. Now only the Spotlight Diagnostic Server is required. On upgrade to Spotlight on Oracle 10.3 the Spotlight Web Publisher will be removed automatically. | 2355 |
Unexpected Area | Fixed a problem where an Unexpected Error | Integer Overflow occurred on resizing a drilldown window. | 2296 |
Monitoring Oracle connections | On the Alert Log drilldown fixed error ORA 01426: numeric overflow. The Log viewer can open files up to 2Gb in size. | 2309 |
Top Sessions | Fixed the source of the following error on the Top Sessions drilldown: "Duplicates not allowed in table TopSessionsWithoutEvent". | 2354 |
Monitoring Oracle Data Guard | Fixed issues connecting to a Data Guard Standby database in environments with fast connections. | 2326 |
Monitoring Exadata | Fixed a problem where Spotlight is incorrectly derived the cell port number from the subnet mask. | 2290 |
Monitoring Unix | Fixed a problem where Spotlight could not connect to Red Hat 7. | 2291 |
The following is a list of issues known to exist at the time of this release.
Feature | Known Issue | Defect ID |
---|---|---|
General | Spotlight data not displayed when overhead settings are restored to default values: In some cases, restoring Overhead Management settings on a Spotlight component may prevent the display of Spotlight data in one or more drilldown pages. To view the data, disconnect the original Spotlight connection and then reconnect. | |
Queued Spotlight queries will complete despite changes to Overhead Management settings: When you use Spotlight's Overhead control to reduce or halt the collection of data from a connection, any existing queries that have been queued for execution will complete as if started under the previous overhead setting. | ||
Installation issues |
Brackets not permitted in installation path names: Prior to Oracle 11g, the Oracle client does not support an installation path for Spotlight that contains the brackets "(" and ")". For example: C:\Program Files (x86)\... Tip: For 64-bit operating systems we recommend not installing Spotlight on Oracle (Windows 32) in "c:\Program Files" since Windows re-directs this back to "C:\Program Files (x86)". |
|
Installing for multi-user access. If Spotlight is installed for use by multiple users of a system, the additional users must be local administrators. | ||
Upgrade issues |
When upgrading to Spotlight on Oracle 10.3.2 history data will be reset. If you would like to keep history between upgrades then you can change the folder spotlight stores history to, through Spotlight Options | storage->History Location. |
Feature | Known Issue | Defect ID |
---|---|---|
Connections | After connecting once with an Oracle 11g or Oracle 12c client, if you change the Oracle home to use a different client, the next time you connect you may see the error Entry Point Not Found… | 2226 |
From a Spotlight on Oracle connection where the Oracle database is installed on a Windows operating system, from drilldown Operating System | OS Processes right click on an Oracle process and select Top Sessions to open the Top Sessions drilldown - results in error: Unable to file Oracle session for this process. |
2197 | |
Limitations with automatic reconnection to Oracle systems:
|
||
Spotlight on Oracle connections: Spotlight on Oracle RAC automatically creates Spotlight on Oracle connections for each instance in the cluster. If, for example, you name your Oracle RAC connection "My cluster", and it has two instances with instance names of "CL1" and "CL2", then two Spotlight on Oracle connections named "My cluster CL1" and "My cluster CL2" will be created automatically when you first connect Spotlight to the cluster. If you already have Spotlight on Oracle connections with those names, the connection details will be overwritten by Spotlight on Oracle RAC. If you subsequently delete the Oracle RAC "My cluster" connection, you will need to delete the associated Spotlight on Oracle connections manually. | ||
Avoid simultaneous REXEC and SSH connections: Spotlight supports both REXEC and SSH connections to Oracle servers, but raises an error when you try to open simultaneous REXEC and SSH connections to the same Oracle server. | ||
Home Page / Drilldowns | Changing column order may disable sub-pages in SQL Analyze Trace drilldown page: Changing the order in which columns are displayed in the Trace File Details grid of the Trace Files page may disable the Summary, SQL Statements, and SQL Statement Details tabs, limiting your access to the other pages within SQL Analyze Trace. To counter this problem, right-click the Trace File Details grid and choose Restore Default Settings from the shortcut menu. | |
The Spotlight on Oracle Data Guard Standby icon is disabled for a connection to an instance that is part of an Oracle RAC cluster. This is by design. The metrics would not be accurate if the primary connection was not Oracle RAC. If the primary connection was to an Oracle database then the metrics would not be for the whole cluster. | ||
Negative value for Shared Pool Used component: The Shared Pool Used component on the Spotlight on Oracle home page may display a negative value when Oracle is first started or when the shared pool is flushed out. This occurs when the value for "shared pool free memory" in v$sgastat is larger than the original shared pool size (Oracle bug 3288917). | ||
Inaccurate value for Total RAM after network timeout error: After a network timeout error, Spotlight may display an inaccurate value for the Total RAM metric on the Spotlight on Oracle RAC home page. When this occurs, Spotlight's calculation of Total RAM has omitted data from one or more nodes in the cluster. | ||
Operating system Drilldown: (OS) statistics not reported by Spotlight on Oracle: Differences between versions of operating systems mean that Spotlight is unable to collect all OS statistics in all environments. The following list shows statistics in the Operating System drilldown pages that are not reported by Spotlight on Oracle for each operating system.
|
||
Installing and configuring DTrace scripts (Solaris 10 and later): DTrace, a dynamic analysis tool for Sun operating systems, was first introduced in Solaris version 10. You can enable and use Spotlight's DTrace drilldown to capture details about the interaction between Oracle and Solaris that would otherwise be unavailable.
Before doing this, you must configure the Solaris server under investigation. To do so:
For more information, see the DTrace User Guide. |
||
Predictive Diagnostics | Predictive Diagnostics is disabled for Read Only connections. Read Only databases cannot run (Predictive Diagnostics) jobs therefore no data will be gathered. | ST11604 |
Oracle configuration | OCI error displayed when the Oracle client setting is changed in a connection profile: In some circumstances, changing the Oracle client setting within a profile can cause problems with loading the correct OCI.DLL. To resolve this issue, set the Oracle client global option to the desired client. | |
Restarting Spotlight to change selected Oracle Home: Normally, you can change the Oracle Home setting for Spotlight on Oracle whenever the selected home is NOT being used for an active Spotlight connection. In certain circumstances, however, disconnecting from a database causes the termination of one or more executing queries. When this happens, you can select a new Oracle Home in a connection profile (or in the Spotlight on Oracle Options window) ONLY AFTER Spotlight itself has been restarted. |
||
Unable to create or open a Spotlight connection because of missing PATH entry for Oracle client:
|
||
Error when connecting to Oracle 10g database on LDAP server: Spotlight may encounter access violation errors when attempting to connect to an Oracle 10g database on an LDAP 9.2.0.1 server via an Oracle 11g client. To resolve this problem, we recommend using an Oracle 10g client to connect to the 10g database. | ||
Oracle error ORA-1031 when connecting to an Oracle database: To resolve the error ORA-1031: insufficient privileges in table Parameter when you try to connect to an Oracle database, add the following entry into the SQLNET.ORA file on the Spotlight client machine:
Note: This error is seen most often for the Parameter table, but can also occur for others. |
||
Read access required to analyze Oracle trace files: Before you can use Spotlight's SQL Analyze Trace facility to analyze trace files from a target Oracle database, the Spotlight OS User must have read access to the directory on the server specified by the Oracle parameter UserDumpDest. | ||
Open_cursors parameter: The open_cursors parameter for the database instance needs to be greater than 70 to allow Spotlight to diagnose the database instance correctly. | ||
Oracle error ORA-12154 when connecting to Predictive Diagnostics with Oracle Names Server: The known Oracle bug #2048583 may cause an ORA-12154 error to be raised when you navigate to the Predictive Diagnostics drilldown, preventing the display of the drilldown. A possible workaround is to upgrade your Oracle client. | ||
Oracle archiving | Close and re-open Spotlight connections to detect new archive destinations: When you add a new archive destination to a monitored Oracle database, it may not be detected by Spotlight. Disconnect from the database and then reconnect to view the details of the new archive destination. | |
Unreliable historical data for archive destinations: When viewed in History mode, the Spotlight connection may on occasion display incorrect data for archive log destinations. | ||
Information shown for a single node only in Alert Log and Archive Log diagnostics: In a clustered environment where the global_names parameter is set to TRUE, alert log and archive log diagnostics within Spotlight on Oracle RAC will display data for one node only. To work around this, add the entry
to the SPOTLIGHT.ORA file in the Plug-ins\SoO sub-folder of the Spotlight installation folder. This will change the global_names parameter for the relevant Spotlight session. |
||
Limited support for Archive Destinations on mapped network drives (Windows): Spotlight does not as yet calculate or display Time to Failure estimates for Oracle RAC systems on Windows platforms whose archive destinations are not local drives. | ||
Oracle 12c |
In an Oracle 12c Data Guard environment, in some circumstances the Transport Process Running alarm fails to fire when log shipping is stopped. Spotlight on Oracle expects the Oracle process to stop when log shipping is stopped, but in some circumstances the Oracle process continues to run (idle). |
SoO-1759 |
Plugged database sessions sometimes don't show in the Top sessions drilldown. To fix the issue, run alter system flush shared_pool |
SoO-1374 | |
When the Spotlight connection is to the container database, the Container drop down menu may not populate with all the plugged in databases. This applies to the Activity | Summary and Pluggable Databases | Resource Usage drilldowns. To fix the issue, run alter system flush shared_pool On Oracle RAC, run alter system flush shared_pool on every node of the RAC. |
SoO 1426 | |
When the Spotlight connection is to the container database:
When the Spotlight connection is to the plugged in database:
The problem is v$iostat_file is empty on the pluggable database. |
SoO-1376 SoO-1417 | |
When the Spotlight connection is to the container database:
When the Spotlight connection is to the plugged in database:
The problem is with Oracle counters not always incrementing correctly for plugged in databases. |
SoO-1377 SoO-1410 | |
Oracle Exadata |
After heavy use of the cellcli utility, CPU utilization on the cell host may hit 100% and stay there. The runaway processes appear to be java and cellsrv. To fix, identify the cell host on the Exadata | Cell Balance drilldown then enter the following Unix command on the appropriate cell host:
|
|
Windows Firewall has blocked some features of this program: You may see this Windows Security Alert while Spotlight is running.
|
PT32653067 | |
Oracle 11g | Spotlight support for Oracle 10g or 11g Instant Client: Spotlight on Oracle supports the use of the Oracle 10g or Oracle 11g Instant Client when it is the default Oracle client, but the Oracle Instant Client may not be available in the list of Oracle clients shown in the Spotlight connection profile or in the Oracle home item in the Spotlight on Oracle Options window. | |
Bad data in Latch Misses chart: The Latch Misses chart in the Activity Latches drilldown can show bad data for Oracle 11gR2 under category "Other". This is due to intermittent bad data being returned from Oracle for latch "JS slv state obj latch". Bug 9534870 has been raised with Oracle. Using the Filter button to remove the "Other" category from the chart is a possible workaround for this issue. | ||
Oracle 10g | Asynchronous I/O failure in Oracle 10g (Release 2) on Linux: In some Linux implementations, Oracle 10G (Release 2) is not able to report I/O activity or events to the operating system while using asynchronous I/O. This problem can cause database writer contention in Oracle and cause Spotlight to raise database writer alarms. To correct the problem, you need to stop the database and relink the base Oracle binary with the option async_on. [For more information, see Document 365416.1 on the Oracle Metalink Web site (https://metalink.oracle.com/).] | |
Missing Flashback data in Recovery Area page: When used to diagnose Oracle 10g (Release 1) databases, Spotlight on Oracle populates only some of the charts and tables in the Recovery Area page of the Disk Storage drilldown. The cause is the absence of the dynamic performance view v$flash_recovery_area_usage, which is defined only in Oracle 10g (Release 2) and later. Flashback components in the Disk Storage panel on the home page (the Flashback container, and the Size and Used fields) will also be disabled. | ||
Oracle 10g bug may affect display of SGA data: A bug introduced in Oracle 10g may result in several Spotlight components – in particular, the SGA Current Size component on the home page, and various components on the SGA Utilization page of the Configuration & Memory drilldown – to display the message "Unknown – Oracle Bug". The bug responsible for causing this error has been fixed in Oracle release 10.2.0.3. |
Feature | Known Issue | Defect ID |
---|---|---|
Spotlight Essentials user token |
Spotlight does not allow for multiple Windows users (on the same computer) to enable Spotlight for Mobile devices and web based analytics independently. Only the last Windows user's Spotlight Essentials user token is remembered. |
SoO-1520 |
Installation and Startup |
To install the Spotlight Diagnostic Server on a computer other than the Spotlight Client the remote computer must enable the "Remote Registry" service. The remote computer is the computer remote from the Spotlight Client. Note: By default the Remote Registry service is disabled on Windows 8. |
SoO-1810 |
If Spotlight on Oracle 10.3 is installed side by side with Spotlight on Oracle 10.2 or 10.1 then the Spotlight Client does not auto detect a pre existing Spotlight Diagnostic Server. Workaround: On the Spotlight on Oracle, View | Options | Configure Diagnostic Server page: 1) Enter the host of the Spotlight Diagnostic Server, 2) Spotlight detects that an upgrade is available. Click Upgrade/Install to upgrade the Spotlight Diagnostic Server. Alternative Workaround: On the Spotlight on Oracle, View | Options | Configure Diagnostic Server page: Reinstall the Spotlight Diagnostic Server. |
SOO-2166 | |
Spotlight Mobile |
When two Diagnostic Servers use the same User Token then the Heat Map will flip back and forth between the two at various intervals. |
|
Monitoring Connections |
For connections through the Spotlight Diagnostic Server (Spotlight Essentials and Spotlight Mobile)
|
DS-312 SoO-1894 |
Uninstall |
For Windows 8.x there may be issues using the Spotlight Client to uninstall the Spotlight Diagnostic Server. Workaround: For Windows 8.x use Windows Control Panel | Programs and Features. Uninstall "Spotlight Diagnostic Server for Oracle". |
SOO-1805 |
Feature | Known Issue | Defect ID |
---|---|---|
Connections | Connections to MySQL databases do not support the use of SSH public and private keys. | |
Activity drilldown | No data shown in Mutex page for MySQL versions 5.0.33 to 5.1.1: Because the data returned by the Show mutex status command depends on the compile options selected for the MySQL server, this version of Spotlight on MySQL does not display mutex information for MySQL versions 5.0.33 to 5.1.1. | |
Linux |
'iostat' required for full functionality on Linux systems: In UNIX-based systems, Spotlight on MySQL requires access to the iostat program in order to display its full functionality; it will display an error if iostat is not available. A number of Linux distributions do NOT install iostat by default. If you encounter an "iostat command not found" error while diagnosing a MySQL database, you can either:
|
|
Spotlight home page | Tablespace storage data not available without O/S user permissions to view InnoDB files: Without the O/S permission to view InnoDB files, the Tablespace components in the Storage panel of the Spotlight on MySQL home page display the value N/A. |
Feature | Known Issue | Defect ID |
---|---|---|
Connections |
REXEC and SSH protocols and Unix commands: Spotlight uses the REXEC or SSH protocols to submit various Unix commands (for example, netstat, vmstat, iostat, sar) to observe system activity. These commands must be accessible to an REXEC or SSH session for Spotlight to be able to observe Unix activity. If these commands are not located in the search path for REXEC or SSH sessions, Spotlight displays an error. |
|
'iostat' command may not be installed. Spotlight on Unix works with full functionality only when the iostat command is installed on the server under diagnosis. This may NOT be true for all Unix systems. If iostat is NOT installed, Spotlight may display an error message such as 'iostat: command not found'. If you encounter this error, you can: Install the iostat command on the server. (On Red Hat Linux, this command is included in the sysstat package.) |
||
Logging on as "root". When connecting to a Unix OS, you need to do so from a logon other than "root". Remote login as "root" has been disallowed for security reasons. |
||
Public-key cryptography available for SSH2 connections only: Spotlight can now use public-key cryptography (via DSA or RSA) to communicate securely with Unix systems, but this functionality is made available only under the SSH2 protocol. |
||
Password authentication for SSH connections that do NOT use public-key cryptography. To allow Spotlight to make SSH connections to any Unix or Linux hosts that permit SSH connections, you may need to alter the PasswordAuthentication configuration item in the sshd_config file. Set the value of PasswordAuthentication to yes. |
||
Password Authentication when using SSH to connect to Linux servers: To allow Spotlight to make SSH connections to Linux machines via username/password authentication, you may need to set the value of the PasswordAuthentication configuration item in /etc/ssh/sshd_config to yes. | ||
AIX Limitations |
Specific implementations of AIX may limit Spotlight's ability to collect data. These include:
|
|
HP-UX Limitations |
Specific implementations of HP-UX may limit Spotlight's ability to collect data. These include:
|
|
Linux Limitations |
Specific implementations of Linux may limit Spotlight's ability to collect data. These include:
|
|
Solaris Limitations |
Unix OS commands. Unix OS commands need version 5.6 of perl or later. If this is not available you should revert to using a shell script to obtain operating system data for this server. To do this, edit the file ScriptConfig.ini (in the ..\Plug-ins\DatasourceUNIX sub-folder of the Spotlight installation folder) according to the instructions supplied in the file. |
|
Problems with diagnosing Solaris 9 machines. A number of Spotlight home page components will not be populated when Spotlight diagnoses lightly-loaded Solaris 9 machines. This is caused by the output from the vmstat command regularly recording a "State Change" event, which in turn resets values for the vmstat command. In this case, the CPU spinner, User % gauge, System % gauge, Queue Length gauge, Free RAM label, Blocked Processes button, Swapped Processes button, Paging In and Paging Out flows, and Swapping In and Swapping Out flows will appear grayed out. |
||
Other Solaris Limitations:
|
Feature | Known Issue | Defect ID |
---|---|---|
Drilldowns |
Error Access denied on the Spotlight on Windows Home Page Open Sessions panel and the current user is in the Administrators group on both the local and the remote machine. To fix this issue: Enable the AllowRemoteRPC property in the registry of the monitored system. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server] " AllowRemoteRPC"=dword:00000001 or import the registry file AllowRemoteRPC.reg |
PT43095851 |
Processes drilldown. For some versions of Microsoft Windows, the Peak Mem Usage (MB) column in the Processes grid displays bytes or kilobytes rather than megabytes. | ||
Windows 7 error. When diagnosing a Windows 7 machine, the Network / TCPIP drilldown can show errors with the text "Error 80041010: Invalid class". This is due to problems within WMI (Windows Management Interface). | ||
Windows 7 hidden partition. Windows 7 is typically installed with a 200 MB hidden partition which contains the Windows Recovery Environment (WinRE). This partition is not shown on the Spotlight on Windows home page, but data for it will be displayed on the Logical Disk Activity drilldown. | ||
Missing event log message text. Redesigned resource information structures within Windows may prevent Spotlight from reading the content of event log messages on Vista and Windows Server 2008 systems. | ||
Missing Open Ports page. Spotlight cannot currently display the Open Ports page in the Network drilldown for Windows Vista and Windows Server 2008 systems. | ||
Excessive event log activity. If you are connecting to a machine that has an event log that is being updated excessively (more than two items being logged per minute), it is recommended that you turn off the event log feature for that system. This is because Spotlight on Windows maintains details of all event log items, which may cause the program to use an excessive level of memory. | ||
Incorrect or missing NBT information. When connecting to a local machine, sometimes Windows will not return the correct NBT information. This may cause the NBT flows on the main window to be dimmed. It may also cause the information in the NBT drilldown to be blank. | ||
Errors in performance counters and WMI: Spotlight on Oracle now reports fewer performance counter and WMI errors of the type "Error 80041010: Unknown IWbemLocator.ConnectServer error". It is impossible to eliminate these errors entirely if they are generated by the Windows server under diagnosis. | ||
Event log size. There is a 64 KB limitation to the size of event log records. | ||
Connections | Connection failure when Spotlight installed on Windows Vista. When you run Spotlight from a Windows Vista machine, you may receive an access denied error when you attempt to connect to a remote system as a user from a different domain than the current Spotlight user. To avoid this, make the current Spotlight user an administrator on the system being diagnosed, or run Spotlight under a local account on the Vista machine. | |
Service Manager is not accessible error on connecting to a Windows 8 or Windows 2008 server image. Resolution: Ensure the user on the Spotlight Client has administrator privileges on the windows server you want to monitor. |
SOO-34 ST14620 | |
Limit to simultaneous connections. It is recommended that no more than 10 simultaneous connections be executed from the same instance of Spotlight on Windows. Depending on the available system resources, the level of response will deteriorate if this number is exceeded. The number of connections possible may also be affected by option settings; for example, setting event log options to access thousands of event log items will degrade Spotlight performance and consume more memory. | ||
Remote Registry service. The Spotlight machine and the machine being diagnosed must have the Remote Registry service running. If you attempt to connect to a machine that has the Remote Registry service stopped, Spotlight will return the following error message: No Windows server called <machine name> could be found on the network. If the address is valid then the Remote Registry service may not be running on the remote server. Make sure the Remote Registry service is running on the Spotlight machine and the machine you are connecting to. |
||
Connecting to a machine running PC Anywhere. If a machine has PC Anywhere loaded and is using the PC Anywhere Performance Monitor extensions (from pcaperfctrs.dll), Spotlight may show "query failed" messages on that connection. To work around this issue, unload the PC Anywhere Performance Monitor extensions from the machine.. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center