HP 3PAR System Reporter 3.1 MU1 Software Release Notes (QL226-97308, December 2013)

Defects fixed in HP 3PAR System Reporter 3.1 MU1
ResolutionDescription
This problem is addressed in the Region Mover log messageThe Region Mover log should not report the 'Region
Movement discarded information' as an error message.
This is fixed by initializing the JavaScript array in the right way.If large volumes (more than 64k records) of data are
selected for the report, JavaScript error is displayed.
This is fixed by providing additional configuration variables in
the config.tcl, under the 3PAR-rpt directory. If the apache server
The Schedule report e-mail link must contain HTTP port
number on which the web server listens. This is observed
is configured for a port other than 80, the entry “setif the apache server is configured to a port other than
80. Sysdb::httpdport <port>” in config.tcl, under the 3par-rpt
directory, must have an appropriate port number as part of the
configuration.
Best effort restart is made to address this issue, if the first restart
attempt fails.
It was observed once in System Reporter that the sampling
operation had stopped because the restart attempt of the
sysrptsched process had failed.
This is due to the change in Inform CLI API behavior. This is
addressed in the System Reporter.
System Reporter always uses the Secure SSL mode for
CLI connection, regardless of whether the Use SSL option
(in the Add InServ screen) is selected or not.
Known issues
DescriptionItem
Internet Explorer has a limit of 2048 characters. Firefox (browser) has 65,536
character limit. Apache produces a "413 Entity Too Large" error after 4000 characters.
The message "Unrecognized data
report" can be generated by Internet
Explorer when a URL is very long.
Workaround:
Break the query into a smaller size (especially for PD/LD reports).
Excel 2003 has the row limit set at 65,536. Excel 2007 has a maximum limit of
1,048,576 rows. If the data being retrieved from the database exceeds these limits,
an overflow error occurs.
An overflow message can be
generated by the Build Report Menu
for some reports with a large
Workaround:
No workaround has been found to this problem except filtering the data to run smaller
queries.
number of objects (such as LD
space).
System Reporter requires that the database user in Oracle and MySQL have a
password.
System Reporter does not work
correctly if a database user account
is created without a password.
Workaround:
Ensure that the database user has a password.
The speed of extraction depends on the speed of the database. Also, the current
version of the extraction utility is a single threaded application where the IO speed
depends on the speed of the destination disks.
The extraction utility can take a long
time to perform the extraction
process when working with large
databases.
Workaround:
Extract smaller chunks of data at a time.
The extract utility is designed to execute from the server that has System Reporter
installed. It uses the System Reporter parameter file to execute.
The extraction utility can only be run
from a Server that has System
Reporter installed.
Workaround:
None.
The extracted files are stored in ASCII files with line feed, tab and spaces so the size
of the extraction file can be much larger than the data stored in the database.
The files resulting from the
processing of the extraction utility
can be large.
Workaround:
None.
Defects fixed in HP 3PAR System Reporter 3.1 MU1 7