CMS ID Request Template - Oracle



CMS ID Request Template

Process

• Complete this CMS ID Request Template, and send to certsup_ww@

• All requests must include, in addition to this CMS ID Request Template, an appropriate, fully completed eBOM template. The requirements for eBOM completion are as follows:

o OS Certification: Each OS Certification is comprised of 2 OCE Certification Projects - a Database Single Instance OS Certification project, and a RAC OS Certification project. Therefore, 4 templates should be completed, as follows:

▪ CMS ID Request Template (this template), stating DB (Single Instance) OS Certification as the type of testing

▪ DB (Single Instance) eBOM Template

▪ CMS ID Request Template (this template), stating RAC OS Certification as the type of testing

▪ RAC eBOM Template

o DB (Single Instance) Virtualization Technology Validation

▪ CMS ID Request Template (this template)

▪ DB (Single Instance) eBOM Template

o RAC Clusterware/CFS/Virtualization/Interconnect Validation

▪ CMS ID Request Template (this template)

▪ RAC eBOM Template

• All requests must go through an approval process; if approved, CMS ID's will be provided via email, along with information on how to obtain the latest version of the relevant OCE software.

Note: All OCE templates are available for download from the OCE Online Resources page.

Important: All fields with grey background are mandatory; failure to provide information for all mandatory fields will result in the rejection of the request

|Project Information |

|Vendor Name |  |

|Vendor contact information |  |

|Type of Certification/Validation Project |  |

|(Note: choose just one; separate requests must be submitted if multiple types are required) | |

|DB (Single Instance) - OS Certification | |

|DB (Single Instance) - Virtualization Technology Validation | |

|RAC - OS Certification | |

|RAC - Clusterware Validation | |

|RAC - Cluster File System Validation | |

|RAC - Virtualization Technology Validation | |

|RAC - Interconnect Protocol Validation | |

|What specific technology will be tested, including version: |  |

|(e.g. CFS, Clusterware, etc) | |

|Full version of Oracle Software to be certified: |  |

|(Note: FULL version; e.g. 11.2.0.2.0. Entering a version such as “11gR2” will not suffice) | |

|Platform (one per request template) |  |

|Linux x86 | |

|Linux x86_64 | |

|Linux Itanium | |

|Linux on POWER | |

|z/Linux | |

|AIX Based System | |

|Solaris SPARC (64-bit) | |

|Solaris X64 | |

|HP PA RISC | |

|HP Itanium | |

|MAC OS X | |

| | |

|Full OS version (one per request template) |  |

|Expected outcome, for example: |  |

|Certified combination published on Metalink | |

|Validation results published on vendor website | |

|White paper / best practices doc created | |

|Location of hardware (e.g. vendor site, Oracle lab, etc) |  |

|If hardware is located at vendor site, please describe how access may be provided to Oracle |  |

|staff to debug issues | |

|If project pre-approved by Oracle please specify pre-approver(s) |  |

|Expected start date (DD/MM/YYYY) |  |

|Expected completion date (DD/MM/YYYY) |  |

|Additional information |  |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download