1 Oracle Data Integrator Console Issues and Workarounds

Transcription

1 Oracle Fusio Middleware Release Notes for Oracle Data Itegrator 12c (12.1.2) E September 2013 This documet describes kow issues associated with Oracle Data Itegrator ad icludes iformatio regardig post-istallatio patches. It icludes the followig sectios: Sectio 1, "Oracle Data Itegrator Cosole Issues ad Workarouds" Sectio 2, "Cofiguratio Issues ad Workarouds" Sectio 3, "Desig-Time Eviromet Issues ad Workarouds" Sectio 4, "Techologies ad Kowledge Module Issues ad Workarouds" Sectio 5, "Post-istall Patch Iformatio for Oracle Data Itegrator 12c" 1 Oracle Data Itegrator Cosole Issues ad Workarouds This sectio cotais iformatio o the followig: Sectio 1.1, "Oracle Data Itegrator Cosole Page Task Flow Resets whe Aother Tab is Closed" 1.1 Oracle Data Itegrator Cosole Page Task Flow Resets whe Aother Tab is Closed Whe a tab cotaiig a page is closed i Oracle Data Itegrator Cosole, all the tabs after this oe reset their task flows (the avigatio actios that were made). The pages i these tabs reset to the origial object that was opeed. [ ] 2 Cofiguratio Issues ad Workarouds This sectio cotais iformatio o the followig issues: Sectio 2.1, "Aget Startup Fails if Default Database is Not Assiged for Microsoft SQL Server" Sectio 2.2, "A Work Repository Caot Be Attached to a Master Repository i the GUID Format if the Overwrite Optio is Not Checked" Sectio 2.3, "Collocated ODI Aget is Not Displayed i Oracle Eterprise Maager FMW Cotrol" Sectio 2.4, "WebLogic Maaged Stadaloe Aget Target is Not Displayed" Sectio 2.5, "Keys Geerated Usig Java 7 Caot Be Used i WebLogic Server 10.3.x" Sectio 2.6, "Load Plas with May Parallel Steps Ru Out of Available Database Coectios" Sectio 2.7, "Test Coectio Fails While Creatig Stadaloe Aget with Third Party Databases" 1

2 2.1 Aget Startup Fails if Default Database is Not Assiged for Microsoft SQL Server A default database must be assiged to successfully complete the Stadaloe Aget startup with Microsoft SQL server. Execute the followig MSSQL statemet to make this assigmet: [ ] ALTER LOGIN <SQLLogi> WITH DEFAULT_DATABASE = <AvailDBName> 2.2 A Work Repository Caot Be Attached to a Master Repository i the GUID Format if the Overwrite Optio is Not Checked Whe attachig a Work Repository to the Master Repository i the GUID format, the followig error appears if the Overwrite optio is ot checked: ODI-3022:Attachig of Work Repository failed due to error: ODI-10228:Repository with id '2' or with ame 'xxxx' has bee already used i your master repository. As a workaroud, export the Work Repository to file, create a empty Work Repository, ad reimport the previously exported Work Repository to the ew Work Repository. [ ] 2.3 Collocated ODI Aget is Not Displayed i Oracle Eterprise Maager FMW Cotrol Status ad data are ot displayed i the Aget Home Page for WebLogic Maaged (Collocated) Stadaloe Agets i the ODI FMW Cotrol UI. To resolve this issue, cofigure the domai to iclude the Stadaloe Aget ad maually update the MASTER_REPO_TIMESTAMP attribute with the correct Master Repository ID (TimeStamp) i the followig file, ad the start Node Maager: [ ] <MW_HOME>/user_projects/domais/WLS_ODI/cofig/fmwcofig/compoets/ODI/<compoet_ ame>/istace.properties 2.4 WebLogic Maaged Stadaloe Aget Target is Not Displayed I Fusio Middleware Cotrol, whe the ODI Cosole Applicatio, ODI Stadaloe Aget, ad Master Repository cofiguratio pages are edited ad saved from the WebLogic Maaged Stadaloe Aget Home page, the WebLogic Maaged Stadaloe Aget target is o loger displayed i the UI. [ ] 2.5 Keys Geerated Usig Java 7 Caot Be Used i WebLogic Server 10.3.x For startig a stadaloe or collocated aget or a WebLogic Server 12c aget i SSL mode, the orgaizatio ad domai-specific keys must be added to the keystore. Ay cliet that eeds to trust this certificate must import the keytool ito its keystore or truststore. If the cliet is WebLogic Server 10.3.x ruig o Java 6 ad the keytool from Java 7 was used to geerate the origial keys, the WebLogic Server 10.3.x domai startup displays a error. [ ] As a workaroud, you ca: Use the keytool from Java 6 to geerate the keypair, export it ad import it ito the Java 7 keystore With the Java 7 keytool use the sytax, keytool -gekey -alias aget -keyalg RSA -keysize sigalg SHA1withRSA 2.6 Load Plas with May Parallel Steps Ru Out of Available Database Coectios Load plas with may parallel steps might ru out of available database coectios, as every parallel step cosumes a extra coectio. This ca be cotrolled by limitig the 'maximum umber of sessios' i the Aget cofiguratio. [ ] 2

3 2.7 Test Coectio Fails While Creatig Stadaloe Aget with Third Party Databases Whe usig ODI Stadaloe Istallatio, while creatig a ODI Stadaloe Aget usig a repository created with third-party databases (for example, SqlServer or DB2) usig the Cofiguratio Wizard, the "Test Coectio" fuctio fails. [ ] As a workaroud: 1. Whe the JDBC Test step fails, click Next. A Warig message is show. Click OK to dismiss the message. 2. Proceed through the remaiig steps to create the Stadaloe Aget usig the Cofiguratio Wizard. 3. Navigate to the directory <Stadaloe domai>/cofig/jdbc ad update the <url> etry i the file jdbc_ odimasterrepository-jdbc.xml as follows: Before: <url>jdbc:weblogic:sqlserver://<host>:<port></url> After: <url>jdbc:weblogic:sqlserver://<host>:<port>;databasename=<dbame></url> 3 Desig-Time Eviromet Issues ad Workarouds This sectio cotais iformatio o the followig issues: Sectio 3.1, "Uable to Modify a No-compliat Wallet Password" Sectio 3.2, "Mappig Editor Display is Not Arraged Properly whe May Coectors Exist" Sectio 3.3, "Sessio Variable is Not Displayed i the Sessio Variables Node" Sectio 3.4, "11g Backward-compatible SDK i 12c Issue" Sectio 3.5, "Sequece Expressio i Aggregate Compoet Causes Ivalid SQL" Sectio 3.6, "Operator Tree Shows Sessios Usig the Name of the Deploymet Specificatio" Sectio 3.7, "Uable to Save a Mappig After Materializig a Datastore Shortcut Refereced i the Mappig" Sectio 3.8, "Groovy Script Editor is Uable to Fid JDBC Drivers i the User Classpath" Sectio 3.9, "Uable to Ivoke HTTPS-based Web Services Through the ODI Studio Iteral Aget" Sectio 3.10, "11g Mappig Upgrade Issue" Sectio 3.11, "Task to Deploy ODI Data Services Fails whe Executed o a Stadaloe Aget" Sectio 3.12, "Null Password-related Coflict" Sectio 3.13, "Prit Mappigs/Reusable Mappigs Fails with Null Poiter Exceptio o Ivalid File Path" Sectio 3.14, "Markers Tab is Missig i Model Folder Editor" 3.1 Uable to Modify a No-compliat Wallet Password Whe creatig a ew ODI Studio UI logi, if a o-compliat Wallet Password is etered i the New Wallet Password dialog box, it caot be modified durig the ext attempt. Clickig Cacel i the New Wallet Password dialog box results i losig the other iformatio added durig the logi process. As a workaroud, set the LANG ad LC_ALL eviromet variables to e_us ad start ODI Studio. [ ] 3

4 3.2 Mappig Editor Display is Not Arraged Properly whe May Coectors Exist Whe a mappig cotais may datasets ad withi the datasets there are may jois, the coector lies ad joi boxes are ot always aliged i a orderly fashio i the Logical view of the Mappig Editor. As a workaroud, perform a maual Auto Arrage to clea the display. [ ] 3.3 Sessio Variable is Not Displayed i the Sessio Variables Node Tracked variables are ot displayed i the Variables ode i the Sessio List i the Operator Navigator. However, the variables ca be viewed i the Variable ad Sequece Values sectio of the Sessio Step or Sessio Task Editor. [ ] g Backward-compatible SDK i 12c Issue Whe usig the 11g backward-compatible SDK i 12c, a persistig mappig or model does ot implicitly persist paret folders ad projects as it did i 11g. As a workaroud, chage the cliet code to explicitly call SDK methods to persist projects ad paret folders. [ ] 3.5 Sequece Expressio i Aggregate Compoet Causes Ivalid SQL Whe usig a sequece as a mappig expressio i a aggregate compoet, the mappig fails to execute; for example, Oracle displays the followig error: ORA-02287: sequece umber ot allowed here As a workaroud, isert the sequece value i a separate compoet prior to the aggregate ad map it ito the aggregate. [ ] 3.6 Operator Tree Shows Sessios Usig the Name of the Deploymet Specificatio Whe differet mappigs that have deploymet specificatios with the same ame are ru, the Operator Tree caot distiguish betwee the mappigs ad they are all grouped uder the same deploymet specificatio. As a workaroud, reame deploymet specificatios to have uique ad recogizable ames. [ ] 3.7 Uable to Save a Mappig After Materializig a Datastore Shortcut Refereced i the Mappig After materializig a shortcut for a datastore, ope mappigs usig this datastore fail while savig ad the followig error is displayed: ODI-26182: Object was modified by aother user ad caot be saved. As a workaroud, close ad reope the mappig ad repeat chages. [ ] 3.8 Groovy Script Editor is Uable to Fid JDBC Drivers i the User Classpath A Groovy script, depedig o exteral JDBC drivers, may fail with a ClassNotFoudExceptio as the JDBC drivers i the user classpath are ot foud. As a workaroud, edit odi.cof ad add the JDBC driver jar usig AddJavaLibFile. For example, AddJavaLibFile./mysql-coector-java bi.jar. [ ] 4

5 3.9 Uable to Ivoke HTTPS-based Web Services Through the ODI Studio Iteral Aget The OdiIvokeWebService tool is uable to call HTTPS-based web services if ru through the ODI Studio iteral aget. As a workaroud, cofigure a exteral aget to perform the executio. [ ] g Mappig Upgrade Issue A mappig upgraded from 11g fails i the followig circumstaces: Whe the mappig uses a multi-coect LKM ad has jois or filters i the stagig area Whe the mappig is upgraded with 11g compatibility switched o ad is the coverted to a 12c mappig i ODI Studio As a workaroud, select a differet LKM after coversio. [ ] 3.11 Task to Deploy ODI Data Services Fails whe Executed o a Stadaloe Aget Whe geeratig ad deployig ODI data services usig a Groovy task i a procedure, the code executes properly i ODI Studio ad JEE Aget, but fails o the Stadaloe Aget. As a workaroud, use JEE Aget to deploy data services programmatically. [ ] 3.12 Null Password-related Coflict Null passwords are o loger accepted ad a error is displayed if a user is created with a ull password. However, the Password Policy dialog box i the Security Navigator allows the creatio of a policy that eables the use of ull passwords. [ ] 3.13 Prit Mappigs/Reusable Mappigs Fails with Null Poiter Exceptio o Ivalid File Path The Prit Mappigs/Reusable Mappigs commad i the Desiger Navigator i ODI Studio throws a Null Poiter Exceptio if the file path of the report PDF file is ot a absolute path to a valid locatio. As a workaroud, provide a valid file path. [ ] 3.14 Markers Tab is Missig i Model Folder Editor The Markers tab is missig i the Model Folder Editor. It is still possible to set markers through the cotext-meu of the model folder i the Desiger Navigator tree. [ ] 4 Techologies ad Kowledge Module Issues ad Workarouds This sectio cotais iformatio o the followig issues: Sectio 4.1, "IKM SQL Icremetal Update (Row by Row) Caot Target Japaese Tables" Sectio 4.2, "No-ASCII Data i a Exceptio Throw by a Jytho Script is Icorrectly Coverted" Sectio 4.3, "Usig IKM File to File (Java) with JAVA_HOME Specified i KM Optios Fails i Executio" Sectio 4.4, "LKM SQL to SQL (Built-i) Creates Idexes i the Wrog Phase" Sectio 4.5, "Icremetal Update Fails whe Mappig CLOB Colums to a Microsoft SQL Server Target with IKM MSSQL" Sectio 4.6, "Upgrade of ODI AA For SAP" 5

6 Sectio 4.7, "IKM SQL Icremetal Update (Row by Row) Fails with Sigle Backslashes i File Path" Sectio 4.8, "LKM File to SQL Fails if File-based Datastore is Nested i Reusable Mappig" Sectio 4.9, "Chage Data Capture for Oracle GoldeGate i Olie Mode Fails i Mappigs" 4.1 IKM SQL Icremetal Update (Row by Row) Caot Target Japaese Tables "IKM SQL Icremetal Update (Row by Row)" fails o task Flag rows for update if the target table ame cotais Japaese characters. I the geerated code, the itegratio table ame appears as I$_?????? where? characters replace Japaese characters. As a workaroud, replace this IKM with aother IKM suitable for the techology. For example, "IKM Oracle Icremetal Update" for Oracle. [ ] 4.2 No-ASCII Data i a Exceptio Throw by a Jytho Script is Icorrectly Coverted Whe a exceptio throw by a Jytho script cotais No-ASCII data, the No-ASCII data might be replaced with???. However, this does ot mea that busiess data is affected, ad more iformatio ca be obtaied i the exceptio stack. [ ] 4.3 Usig IKM File to File (Java) with JAVA_HOME Specified i KM Optios Fails i Executio Whe IKM File to File (Java) is used with JAVA_HOME specified i KM optios, it fails i executio. As a workaroud, set JAVA_HOME o the system level istead of i KM optios. [ ] 4.4 LKM SQL to SQL (Built-i) Creates Idexes i the Wrog Phase "LKM SQL to SQL (Built-i)" creates temporary idexes i the wrog phase resultig i poor performace. As a workaroud, use other LKMs such as "LKM SQL to SQL." [ ] 4.5 Icremetal Update Fails whe Mappig CLOB Colums to a Microsoft SQL Server Target with IKM MSSQL Whe mappig CLOB colums to a Microsoft SQL Server target with "IKM MSSQL", the Icremetal Update fails with the followig error message: ODI-1228: Task IKM MSSQL Icremetal Update (Flag useless rows) fails o the target MICROSOFT_ SQL_SERVER coectio SVR2_MSSQL. Caused By: java.sql.sqlexceptio: [FMWGEN][SQLServer JDBC Driver][SQLServer]The data types text ad text are icompatible i the equalto operator. [ ] As a workaroud, you ca: Add a ew data type VARCHAR(MAX) to Microsoft SQL Server: 1. Navigate to Topology > Physical Architecture > Techologies > Microsoft SQL Server, right-click Datatypes ad select New Datatype. 2. I the <NewObject> dialog box, eter varchar(max) i the Name field, VARCHAR(MAX) i the Code ad Reserved Code fields, create table sytax ad writable datatype sytax, ad eter V i the letter used i the ico field. 3. Click Save. Map Geeric SQL.CLOB to Microsoft SQL Server.varchar(max). 6

7 1. Navigate to Topology > Logical Architecture > Techologies > Geeric SQL, ope the CLOB datatype, switch to the Coverted To tab ad chage it to varchar(max) for Microsoft SQL Server. 2. Click Save. 4.6 Upgrade of ODI AA For SAP I older ODI SAP Adapter versios the extractio programs were executed as RFCs i dialog mode, however, the default executio mode of the latest ODI SAP Adapter has chaged to backgroud processig (the default value of LKM optio BACKGROUND_PROCESSING is true). I backgroud processig mode the extractio programs are executed as SAP reports ad allow a better resource utilizatio of the SAP systems. Backgroud processig is the recommeded executio mode. The dialog mode still works, but has bee deprecated. Ay existig scearios cotiue to use dialog mode executio util regeerated. After upgradig the SAP KMs, all ODI SAP mappigs execute i backgroud mode. To allow backgroud executio, please review the required SAP authorizatios i the followig sectios: For iformatio about the SAP privileges required for SAP ABAP BW, see "SAP ABAP BW Required Privileges" i Gettig Started with SAP ABAP BW Adapter for Oracle Data Itegrator. For iformatio about the SAP privileges required for SAP ABAP ERP, see "SAP ABAP ERP Required Privileges" i Gettig Started with SAP ABAP ERP Adapter for Oracle Data Itegrator. Please ote that the authorizatios for dialog ad backgroud executio mode are differet. If executio has to cotiue i dialog mode, the LKM optio BACKGROUND_PROCESSING should either be set to false i each mappig, or the default value should be chaged iside the KM. If the ODI objects istalled i the SAP systems have bee istalled by RKM SAP ERP v32 or later or RKM SAP BW v23 or later, reistall the SAP ABAP BW adapter as described i "Update ODI SAP Compoets," ad reistall the SAP ABAP ERP adapter as described i "Update ODI SAP Compoets," i the Applicatio Adapters Guide for Oracle Data Itegrator. Note that the adapters from the SAP system eed ot be uistalled first. If the ODI objects are istalled usig RKM SAP ERP or RKM SAP BW versios older tha v32, perform the followig steps: 1. Uistall SAP ABAP BW adapter as described i "Uistallig ODI SAP Compoets," ad uistall the SAP ABAP ERP adapter as described i "Uistallig ODI SAP Compoets," i the Applicatio Adapters Guide for Oracle Data Itegrator. 2. For SAP package ames ad fuctio group ames (KM optios SAP_FUNCTION_GOUP_ODI_ [DEV PROD] ad SAP_PACKAGE_NAME_ODI_[DEV PROD]), review "SAP Packages ad SAP Fuctio Groups" for SAP ABAP BW ad "SAP Packages ad SAP Fuctio Groups" for SAP ABAP ERP i the Applicatio Adapters Guide for Oracle Data Itegrator. 3. Reistall SAP ABAP BW adapter as described i "Update ODI SAP Compoets," ad reistall SAP ABAP ERP adapter as described i "Update ODI SAP Compoets," i the Applicatio Adapters Guide for Oracle Data Itegrator. The latest ODI SAP adapters support the cacellig of log ruig jobs i SAP. To eable the "Stop-immediate" fuctioality i ODI Operator, the OpeTool class must be chaged from oracle.odi.sap.km._odisapabapexecute to oracle.odi.sap.km._odisapabapexecutestoppable. See "Addig the Ope Tool" for SAP ABAP BW ad "Addig the Ope Tool" for SAP ABAP ERP i the Applicatio Adapters Guide for Oracle Data Itegrator. [ ] 4.7 IKM SQL Icremetal Update (Row by Row) Fails with Sigle Backslashes i File Path "IKM SQL Icremetal Update (Row by Row)" fails if the KM optio LOG_FILE_NAME is set to a Widows path cotaiig backslashes, for example LOG_FILE_NAME=C:\user\joe\odi_load.log. This worked i 11g releases. 7

8 As a workaroud, use a double backslash i the path, for example C:\\user\\joe\\odi_load.log. [ ] 4.8 LKM File to SQL Fails if File-based Datastore is Nested i Reusable Mappig A mappig usig "LKM File to SQL" with a file-based datastore ested i a reusable mappig fails with the followig exceptio: ODI-1227: Task LKM File to SQL (Load data) fails o the source FILE coectio XXXXX. Caused By: java.sql.sqlexceptio: ODI-40444: Colum ot foud: YYYYY As a workaroud, avoid usig a file datastore compoet withi a reusable mappig or move the output sigature compoet from the source executio uit to the stagig executio uit. [ ] 4.9 Chage Data Capture for Oracle GoldeGate i Olie Mode Fails i Mappigs Oracle GoldeGate Chage Data Capture (CDC) i olie mode will fail if the iitial load process is ot selected i the model. Eve though iitial load is ot applicable for Oracle GoldeGate i olie mode, you will ot be able to use the datastore from the model i a mappig. This will ot impact the Start Joural fuctio or ay CDC actio from withi the model. However, whe these datastores are used i a mappig with CDC, the mappig will fail. [ ] As a workaroud, you ca select iitial load processes i the model. Eve though iitial load processes are selected i the Model editor, iitial load will still be disabled as the optio to eable it exists i the JKM optio. Perform the followig steps to eable CDC: 1. Ope the Model for which the CDC is eabled. 2. Select the Jouralizig tab. 3. Click the Create butto for Iitial Load Capture Process ad specify placeholder values for Process ad Logical Process Name. There should ot be ay process by the same ame already defied i the Topology Navigator for the Oracle GoldeGate techology, but otherwise you ca use ay value. 4. Click OK to create the capture process istace. 5. Click the Create butto for Iitial Load Delivery Process ad specify placeholder values for Process Name ad Logical Process Name. The same restrictio for the iitial load capture process ame applies. 6. Select the same Target DB Logical schema used for the actual capture process istace. 7. Click OK to create the delivery process istace. 8. Cofirm that the JKM optio USE_OGG_FOR_INIT is set to false. You ca ow use the datastore from the model i mappigs with CDC. 5 Post-istall Patch Iformatio for Oracle Data Itegrator 12c It is strogly recommeded that the followig patches be applied after the istallatio of Oracle Data Itegrator. These patches are available through My Oracle Support ( ad are also distributed i the Oracle Data Itegrator dowload file as odi_1212_opatch.zip. Table 1 Patch Iformatio Patch Number Bugs Descriptio , , , TRACKING BUG FOR FMW UPGRADE CUMULATIVE BACKPORTS TO (Patch) 8

9 Table 1 (Cot.) Patch Iformatio Patch Number Bugs Descriptio ODI T2P FAILS IN FMW WITH -OPSSDATAEXPORT=TRUE NPE USING XDK WITH SUN SAAJ CLASSES; FDOMDOCUMENTBUILDER CONSTRUCTOR IS BROKEN While applyig this patch, see: Sectio 5.1, "Error Whe Applyig Patch Ca Be Igored." 5.1 Error Whe Applyig Patch Ca Be Igored While applyig the ODI recommeded patch umber (odi_1212_opatch.zip) to the ODI Eterprise Istallatio Oracle Home, you may see the followig error message: Error: There is a error with library regeeratio, please refer to the log file for details. OPatch will cotiue applyig the patch. You ca igore this error. The patch is correctly applied. 6 Documetatio Accessibility For iformatio about Oracle's commitmet to accessibility, visit the Oracle Accessibility Program website at Access to Oracle Support Oracle customers have access to electroic support through My Oracle Support. For iformatio, visit or visit if you are hearig impaired. Oracle Fusio Middleware Release Notes for Oracle Data Itegrator, 12c (12.1.2) E Copyright 2010, 2013, Oracle ad/or its affiliates. All rights reserved. This software ad related documetatio are provided uder a licese agreemet cotaiig restrictios o use ad disclosure ad are protected by itellectual property laws. Except as expressly permitted i your licese agreemet or allowed by law, you may ot use, copy, reproduce, traslate, broadcast, modify, licese, trasmit, distribute, exhibit, perform, publish, or display ay part, i ay form, or by ay meas. Reverse egieerig, disassembly, or decompilatio of this software, uless required by law for iteroperability, is prohibited. The iformatio cotaied herei is subject to chage without otice ad is ot warrated to be error-free. If you fid ay errors, please report them to us i writig. If this is software or related documetatio that is delivered to the U.S. Govermet or ayoe licesig it o behalf of the U.S. Govermet, the followig otice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, icludig ay operatig system, itegrated software, ay programs istalled o the hardware, ad/or documetatio, delivered to U.S. Govermet ed users are "commercial computer software" pursuat to the applicable Federal Acquisitio Regulatio ad agecy-specific supplemetal regulatios. As such, use, duplicatio, disclosure, modificatio, ad adaptatio of the programs, icludig ay operatig system, itegrated software, ay programs istalled o the hardware, ad/or documetatio, shall be subject to licese terms ad licese restrictios applicable to the programs. No other rights are grated to the U.S. Govermet. This software or hardware is developed for geeral use i a variety of iformatio maagemet applicatios. It is ot developed or iteded for use i ay iheretly dagerous applicatios, icludig applicatios that may create a risk of persoal ijury. If you use this software or hardware i dagerous applicatios, the you shall be resposible to take all appropriate failsafe, backup, redudacy, ad other measures to esure its safe use. Oracle Corporatio ad its affiliates disclaim ay liability for ay damages caused by use of this software or hardware i dagerous applicatios. Oracle ad Java are registered trademarks of Oracle ad/or its affiliates. Other ames may be trademarks of their respective owers. Itel ad Itel Xeo are trademarks or registered trademarks of Itel Corporatio. All SPARC trademarks are used uder licese ad are trademarks or registered trademarks of SPARC Iteratioal, Ic. AMD, Optero, the AMD logo, ad the AMD Optero logo are trademarks or registered trademarks of Advaced Micro Devices. UNIX is a registered trademark of The Ope Group. This software or hardware ad documetatio may provide access to or iformatio o cotet, products, ad services from third parties. Oracle Corporatio ad its affiliates are ot resposible for ad expressly disclaim all warraties of ay kid with respect to third-party cotet, products, ad services. Oracle Corporatio ad its affiliates will ot be resposible for ay loss, costs, or damages icurred due to your access to or use of third-party cotet, products, or services. 9

10 10