This article describes known issues and solutions at the time of this release. If you need to call Customer Service with any questions or problems regarding an issue, refer to its associated ID number in parentheses, if available.
- Page 22 of the Symantec Fraud Detection Service v3.2, Installation and Deployment Guide, states the following in step 4.
Unzip the FDS<package_name>.tar using an available Linux command.
tar -xvzf FDS_3_0_ALPHA.tar
Since the file was not run through gzip, the example should read as follows.
tar -xvf FDS_3_0_ALPHA.tar
- If you do not include all of the mandatory parameters and then run the schema creation script, the creation process should stop, but instead it may run the whole script with many errors. To work around this issue, check that you have included all mandatory parameters. See the table below for the mandatory attributes based on oracle.conf settings:
|Database object create
- After deleting all end-user clusters (manually or as a result of sliding windows), the anomaly distribution at case creation time does not appear in the Investigation Console View Event Details tab. There is no workaround at this time. (artf50840)
- The system creates an event type with duplicate variable names if a column and converter have the same alias. To work around this issue, verify that you are using unique aliases. (artf51029)
- The cleanall.sh utility does not delete the Fraud Detection System configuration when you run it with the “config” parameter. To work around this issue, use the configuration_import utility with the “clean” flag. This ensures that the old configuration is deleted before you import the new one. (artf51317)
- When refining an Investigation Console search, the system deletes the first refine filter value when you add a second one. To work around this issue, add some conditions, and then update the refine filter values. (artf51740)