Release Notes
Release 53.0
E75742-03
February 2017
This document describes the enhancements that are introduced and the Access Service Ordering Guidelines (ASOG) issues that have been implemented in Oracle Communications MetaSolv Solution Access Service Request (ASR) 53.
This document consists of the following sections:
See ASR Installation Guide for instructions about installing ASR 53.
The ASR53BD.sql file is included in this release. The installer provides all upgrades to MetaSolv Solution executable files and stored procedure files (Procs directory).
MetaSolv Solution 6.3.0.x supports ASR 53 on the following software versions:
Oracle Enterprise Linux Server 6.6 (or later) and 7.0 (or later)
Red Hat Enterprise Linux Server 6.6 (or later) and 7.0 (or later)
AIX 7.1 Update 1
HP Itanium 11.31 Update 7
Oracle Solaris 11
Windows Server 2012 R2
Oracle WebLogic Server 12.2.1.2
Oracle Database 12c R1
JacORB 3.8
MetaSolv Solution 6.2.1.x supports ASR 53 on the following software versions:
Oracle Linux Server release 5.5 (Carthage)
Red Hat Enterprise Linux Server 5
Oracle Solaris 10 update 5/08 or higher (on a SPARC machine)
AIX 6.1 or higher (on a POWER6 machine)
HP-UX 11.23 or higher (on an Itanium machine. 32-bit and 64-bit JAVA supported)
Windows Server 2008 R2
Oracle WebLogic Server 10.3.1
Oracle Database 11g R2
JacORB 2.3.1
This section describes new enhancements in ASR 53.
ASR now supports updated operating systems and underlying software systems. See "Software Support" for more information.
Additional Circuit Information (ACI) Form
Power Type and Voltage (PTV)
Related Circuit ID (RCID)
End User Special Access (EUSA) Form
Related Circuit ID (RCID)
Switched Ethernet Services (SES) Form
Power Type and Voltage (PTV)
Related Circuit ID (RCID)
Access Service Request Number (ASR NO) Field
The existing definition of the Access Service Request Number (ASR NO) field has been modified in the following forms:
Additional Circuit Information (ACI)
Administrative (ADMIN)
Clarification/Notification Request (C/NR)
Confirmation Notice (CN)
Dedicated Internet Service (DIS)
End Office Detail (EOD)
End User Special Access (EUSA)
Enhanced Customer Interface (ECI)
Ethernet Virtual Connection (EVC)
Feature Group A (FGA)
Multipoint Service Legs (MSL)
Network Assignment Information (NAI)
Open Billing (OB)
Permanent Virtual Connection (PVC)
Ports Configuration (PC)
Private Internet Protocol (PIP)
Ring/Additional Ring Information (ARI)
Service Address Location Information (SALI)
Switched Ethernet Services (SES)
Translation Questionnaire (TQ)
Transport
Trunking
Virtual Concatenation (VCAT)
Virtual Connection (VC)
WATS Access Line (WAL)
Table 1 describes the Access Service Ordering Guidelines (ASOG) issues that have been implemented in this release.
| Issue Number | Description |
|---|---|
|
3525 |
The UI and API usage validation changes have been implemented for the Response Type Requested (RTR) field in the ADMIN form. The valid entry changes for the Number of Virtual Connections (NVC) field have been implemented in the following forms:
The valid entry notes changes for the following fields have been implemented in the ADMIN form:
The valid entry notes changes for the following fields have been implemented in the EVC form:
|
|
3544 |
Added new Power Type and Voltage (PTV) field in the following forms:
|
|
3547 |
The valid entry changes and valid entry notes changes for the General Exchange Tariff Options Code (GETO) field have been implemented in the SES form. The valid entry changes valid entry notes changes for the following fields have been implemented in the EUSA form:
|
|
3548 |
Added new Related Circuit ID (RCID) field in the following forms:
The format changes for the following fields have been implemented in the EUSA form:
|
|
3492 |
The UI and API usage validation changes and definition changes have been implemented for the ASR NO field in various forms. See "Access Service Request Number (ASR NO) Field" for the list of forms in which these changes have been implemented. |
Table 2 lists the customer-reported bugs that have been fixed in this release.
| BugDB Number | Description |
|---|---|
|
22737500 |
Issue When you try to supplement an ASR order without changing the version, the application returns the following error: ORA-01403: no data found This issue occurs only when the Capture ASR Audit and Supplement History preference is enabled. Resolution The code has been corrected and now the application does not return any error when you try to supplement an ASR order without changing the version. |
|
22917647 |
Issue When running the asr_master.sql script in a UNIX environment, you receive the following errors: SP2-0310: unable to open file "VALPC.SQL" SP2-0310: unable to open file "VALASR.sql" SP2-0310: unable to open file "valpip.SQL" SP2-0310: unable to open file "valdis.SQL" SP2-0310: unable to open file "VALPVC.SQL" Resolution The code has been corrected and now you no longer receive these errors when running the asr_master.sql during ASR installation. |
|
23017353 |
Issue When you create an ASR order using the importTRANSPORT CORBA API, the values in the LD1, LD2, LD3, and SATH fields are changed in the Service Address Location Information (SALI) form when you open the order using the GUI. Resolution The code has been corrected and now the values in the LD1, LD2, LD3, and SATH fields remain unchanged when you create an ASR order using the importTRANSPORT ASR CORBA API. |
|
23057749 |
Issue Duplicate rules exist in the ASR_GUIDELINE_RULE table. Resolution The code has been corrected and now duplicate rules do not exist in the ASR_GUIDELINE_RULE table. |
|
23577181 |
Issue This issue occurs in situations where you create an end user location in the End User Location Maintenance window with both MSAG and OBF addresses. When you specify the OBF address on an ASR order using the SASN field and also specify a different name in the EUNAME field, the application creates a new end user location instead of reusing the existing end user location's information (other than the location name). Resolution The code has been modified and now when creating an end user location in the End User Location Maintenance window with both MSAG and OBF addresses, if you specify the OBF address on an ASR order using the SASN field and also specify a different name in the EUNAME field, the application does not create a new end user location; instead, it reuses the existing end user location's address (other than the location name). |
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.
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.
Oracle Communications MetaSolv Solution ASR Release Notes, Release 53.0
E75742-03
Copyright © 2017, 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.