| Agile Product Lifecycle Management Averify Release Notes Release 9.3.5 E61167-01 |
|
 Previous |
Averify Release Notes
Release 9.3.5
E61167-01
January 2016
Averify is a scripting tool that performs an integrity check against the PLM database and reports on specific errors. Averify includes a check for missing indexes and inconsistent data stored in the various database tables. Averify only reports errors, and does not attempt to fix them or modify your database.
Running Averify and using the results to eliminate known errors is a prerequisite for diagnosing problems. Averify is not comprehensive, however, and finding no errors does not certify a database as perfect.
Averify can be downloaded from My Oracle Support (https://support.oracle.com). The software should be downloaded to your destination database server.
Extract the averify.zip file to a local drive. After Averify is extracted, all of the files are located in the following directories on the local drive:
\bin
\config
\lib
\logs
\META-INF
\scripts
The averify.properties file, located in the \config directory, contains a set of properties where you can specify database details. By default, the file does not contain user-supplied information. You must modify the averify.properties file to complete the destination database details, averify options, and email options. The destination database parameters contain information about the user and host details of the database you are checking. The Averify options contain information on which portions of the database you want to verify. The email options enable you to send the averify.zip file, containing the averify.log and oracle_averify_report.log, to a specific email address upon completion.
If you do not wish to change the averify.properties file each time you run Averify with different options, you can set the environment variable, PROPERTYFILE, with the full path to another .properties file. You can create multiple .properties files modified with the parameters you need for specific runs of Averify.
| Parameter | Value Definition |
|---|---|
| averify.dest.jdbc.url | The JDBC connection string to the destination database. The format is jdbc:oracle:thin:@<DESTINATION_DB_HOST_NAME>:<PORT>:<SID> where DESTINATION_DB_HOST_NAME is the hostname of the destination database, PORT is the listener port of the destination database (1521 is the default), and SID is the database instance. |
| averify.dest.jdbc.driver | The database driver of the destination database. The default is oracle.jdbc.driver.OracleDriver. |
| averify.dest.tns.name | The TNS entry name in the Oracle Home of the destination database. |
| averify.dest.oracle.home | The Oracle Home of the destination database. This value can be a mapped drive on the system where Averify is run on the host machine.
Note: Use either double back slashes or a forward slash for directory separation, for example, d:/oracle/ora92. |
| Parameter | Value Definition |
|---|---|
| averify.nls.lang | Specifies the NLS parameter value used by the database. The default value is AMERICAN_AMERICA.AL32UTF8. |
| Parameter | Value Definition |
|---|---|
| averify.runOption | Specifies how you want Averify to check the database. The values are all, modules, resetflags, tables, and testcases.
Note: Only one option can be specified for this parameter. |
| averify.modules | Specific modules chosen for averify to check. This parameter is only used if you entered modules as the value of the runOption parameter.
Note: You can check tables that are not specific to the Agile database with the checkNonAgileTables module. |
| averify.testcases | Specific testcases chosen for Averify to check. This parameter is only used if you entered testcases as the value of the runOption parameter. |
| averify.tables | Specific database tables chosen for Averify to check. This parameter is only used if you entered tables as the value of the runOption parameter. |
An example of how the averify details work is as follows:
averify.runOptions=modules averify.modules=ppm, pcpqm, XXXX averify.testcases=AGIL-0000XXXXXX Because the specified runOptions parameter is modules, the testcases parameter is ignored when averify is run. |
|
| Parameter | Value Definition |
| averify.email | Decides if the averify.zip file, containing the averify.log and oracle_averify_report.log, is sent as an email attachment upon completion. Value options are true or false. If set to false, the log files can still be viewed in the \logs directory. |
| averify.customer | Name of Agile customer. |
| averify.mailhost | Name of email server. |
| averify.mailport | Port number of your email server. The standard default is 25. |
| averify.toAddress | averify@oracle.com |
| averify.fromAddress | Email address of the sender. |
| averify.ccAddress | Email address of an additional recipient. |
This section should be configured each time Averify is run. The logs are used by Oracle Agile PLM Development only and are not a replacement for logging a request.
Running Averify and using the results to eliminate known errors is a prerequisite for diagnosing problems. Averify is not comprehensive, however, and finding zero errors does not certify a database as perfect.
To run Averify:
Make sure you have downloaded the latest version of Averify from My Oracle Support (https://support.oracle.com).
Make sure you have backed up your database.
Clone your Production database to a Test environment. This can be done using export/import utilities, Recovery Manager, or copying backup database files from one file system to another and recreating the control file.
Shut down the application server if it is connected to the Test environment to prevent users from connecting to the database.
Go to the Averify_Home\bin directory and run the averify.bat script on Windows or averify.sh script on UNIX.
|
Note: If you are running Averify as a Cron job, add the following line to the averify.sh file after the # Set up the environment comment line:cd /export/home/oracle/averify/bin |
You are prompted to enter the database user name and database password.
|
Note: If errors are generated in the oracle_averify_report.log file, contact Oracle Support. |
You can monitor the status through the log file that is generated while Averify is run. The \logs directory contains the averify.log file.
If you chose to have the log files sent as an email attachment, the averify.zip file, containing the averify.log and oracle_averify_report.log, is sent upon completion.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Averify Release Notes, Release 9.3.5
E61167-01
Copyright © 2010, 2016. Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
