ALDSP 3.0/3.2/3.01 Release Notes - Oracle...ALDSP_3.0 / 3.2 / 3.01 Release Notes This page last...

ALDSP_3.0 / 3.2 / 3.01 Release Notes

This page last changed on Apr 29, 2008.

ALDSP 3.0/3.2/3.01 Release Notes

AquaLogic Data Services Platform provides read and write access to information in relational databases,web services, Java functions, XML files, delimited files, and other types of disparate data.

Once developed, application developers — using access technologies such as the ALDSP mediator API,JDBC, SQL, or Workshop controls — can invoke ALDSP operations as a means of providing theirapplications with access to integrated, updateable data from their enterprise.

Metadata, security, and cache management facilities are provided through the Data Services PlatformConsole (dspconsole).

Notes:

• This document covers:° ALDSP 3.0° ALDSP 3.2° ALDSP 3.01

References to ALDSP 3.0 in the notes should be seen as applying to all threereleases unless otherwise indicated.

• BEA AquaLogic® Data Services Platform was originally named Liquid Data for WebLogic®.Some artifacts of the original name remain in the product, path, and other artifacts.

Contents

• Contents• Revision Policy• What's New?• Product Installation and Upgrade• Configuration Information• Product Limitations and Workarounds• Supplemental Release Note Documentation

Revision Policy

AquaLogic Data Services Platform Release Notes is subject to revision between releases. The most recentversion can be found at:

Document generated by Confluence on Apr 29, 2008 16:38

http://edocs.bea.com/aldsp/docs30/relnotes/relnotes.html

For assistance in tracking unresolved issues please contact BEA Customer Support.

What's New?

http://edocs.bea.com/aldsp/docs32/dsp32wiki/what's%20new.html

Product Installation and Upgrade

http://edocs.bea.com/aldsp/docs30/install/index.html

Configuration Information

Supported Configurations

For support information on vendor operating systems, JDK, and hardware support, see either:

• ALDSP 3.0 and 3.01: Supported Configurations for BEA AquaLogic Data Services Platform 3.0 or• ALDSP 3.2: Supported Configurations for BEA AquaLogic Data Services Platform 3.2

Client Support

For this release, client applications are supported on the following JDKs:

• BEA JRockit 1.4.2 and Sun 1.4.2• BEA JRockit 5.0 and Sun 5.0

Supported Interoperability Products

This section describes the following interoperability products that are supported for use with ALDSP 3.0.

ALDSP 3.0 and 3.2 Product and Version Support

Product Version Supported ConfigurationRequired

WebLogic Portal 9.2 and 10.0 (WLP to ALDSPonly)

No

WebLogic Integration 9.2 (WLI to ALDSP only) In some cases


http://edocs.bea.com/aldsp/docs30/relnotes/relnotes.html

http://support.bea.com

http://edocs.bea.com/aldsp/docs32/dsp32wiki/what's%20new.html

http://edocs.bea.com/aldsp/docs30/install/index.html

http://edocs.bea.com/platform/suppconfigs/configs_al30/aldsp30/aldsp30.html

http://edocs.bea.com/platform/suppconfigs/configs_al30/aldsp32/aldsp32.html

AquaLogic Service Bus 2.6, 2.61, 3.0 No

AquaLogic EnterpriseSecurity

3.0 No

AquaLogic EnterpriseRepository

3.0.0.2 No

WebLogic Workshop ALDSP 3.2: 9.2 MP2 (for ALDSPControl only), 10.0 MP1, 10.1,10.2ALDSP 3.0: 9.2 MP2, 10.1, 10.2

In some cases

Special Configuration Instructions for WLI and WebLogic Workshop

•Configuration Instructions for WebLogic Integration 9.2 (WLI to ALDSP only)

ALDSP 3.0/3.01 only:WebLogic Integration 9.2 was shipped and tested with an older version of binxml.jar. To invokeALDSP 3.0 services such as ALDSP Control, Web Services API, or Mediator API from WLI underWebLogic 9.2, it is necessary to use the current version of this file. There are two ways to do this:

• You can change the WLI server classpath from:

${WL_HOME}/server/lib/binxml.jar

to the ALDSP 3.0 version:

${ALDSP_HOME}/lib/binxml.jar

• Alternatively, you can simply place the following first in your PRE_CLASSPATH:

${ALDSP_HOME}/lib/binxml.jar

Although there are no known issues associated with this change, making this switch may causeunexpected behavior in WLI.

•Configuration Instructions for WebLogic Workshop in conjunction with the ALDSP Control

ALDSP 3.2

If you have installed ALDSP 3.2 into a <BEA_HOME> containing an existing 10.0, 10.0MP1, 10.1,or 10.2 version of Workshop, no link copy is needed to ALDSP Control-enable Workshop.Similarly, if you install ALDSP independently and then install a supported version of Workshop andconfigure Workshop to use the same Eclipse installation as ALDSP, no link copy is required.


The following table clarifies this requirement:

ALDSP Version Requirement to copy a link ALDSPconfiguration file to Workshop?

3.0 Yes.

3.23.01

Yes, unless a supported version of Workshop(10.0, 10.0MP1, 10.1, or 10.2) is installed in thesame <BEA_HOME>.

ALDSP Control Configuration Instructions for 3.0 and Some 3.2 Installations

The following table describes the compatibility matrix between ALDSP and Workshop. The location ofconfiguration files and where they need to be installed in order for Workshop to operate as a client of anALDSP Control is specified.

ALDSP 3.0

WorkshopVersion

Source, Link File, Destination

9.2

Source: <aldsp_home>/eclipse-plugin/workshop9

File: com.bea.dsp.ide.control.feature.link

Destination: <workshop92_home>/workshop92/eclipse/links

10.1,10.2

Source: <aldsp_home>/eclipse-plugin/workshop10

File: com.bea.dsp.ide.control.feature.link

Destination: <bea_home>/tools/eclipse_pkgs/1.1/eclipse_3.2.2/eclipse/links

ALDSP 3.2 and 3.01

WorkshopVersion

Source, Link File, Destination

10.0,10.0MP1

Source: <aldsp_home>/eclipse-plugins/workshop1001

File: ALDSP 3.2:com.bea.aldsp32.eclipse.plugins.workshop1001.link

ALDSP 3.01:com.bea.aldsp301.eclipse.plugins.workshop1001.link

Destination: <bea_home>/tools/eclipse32/eclipse/link


9.2MP2




Destination: <workshop92_home>/workshop92/eclipse/links

10.2




Destination: <bea_home>/tools/eclipse_pkgs/1.1/eclipse_3.2.2/eclipse/links

JDBC Driver Support for Reporting Tools

The following section provides information on JDBC driver support for reporting applications used withthe AquaLogic Data Services Platform 3.0 JDBC driver:

Application and Version JDBC Native OpenLink ODBC/JDBCLite Bridge

Crystal Reports XI Supported

Business Objects XI, Release2

Supported

Hyperion BI 9+, InteractiveReporting

Supported

Microsoft Access 2000 Supported

Microsoft Excel 2000 Supported

Standards Support

The following Web services standards supported for this release:

Standards Version

SOAP 1.1, 1.2

WSDL 1.1

JAX-RPC 1.1

SDO 2.1

XML Schema 1.0

XQuery July 2004 Draft


Product Limitations and Workarounds

This section lists known limitations associated with the current BEA ALDSP release that users mayencounter. Information regarding these limitations includes:

• A CR (change request) number for each issue.• Applicable platform.• Detailed description of the problem and workarounds, where applicable.• Date, if the item is added or changed after the general availability release of the product.

Known Product Limitations and Possible Workarounds

Change RequestNumber

ReleaseFound

ReleaseAddressed

Field Descriptions

CR364732 3.2, 3.01 Using complex typeswith simple contentfrom an ALDSP 3.2(or ALDSP 3.0.1)client to an ALDSP3.0 server maygenerate anoptimistic lockingfailure errors.

All.

Using complex typeswith simple contentfrom an ALDSP 3.2 (orALDSP 3.0.1) client andserializing it to anALDSP 3.0 server maygenerate an optimisticlocking failure due toincorrect processing ofthe change summary onthe ALDSP 3.0 server.

Upgrade the ALDSP 3.0server to an ALDSP 3.2(or ALDSP 3.0.1) serverif using a complex typewith simple content.

CR364443 3.2 Manually adding anew server andmodifying a dataservice may generatean unexpectedexception inWorkSpace Studio1.1.

Platform All.


Description WorkSpace Studio 1.1may generate thefollowing unexpectedexception after youmanually add a newserver and then modifya data service:

org.apache.xmlbeans.XmlException:ThreadAWT-EventQueue-0:The 0th suppliedinput is not aschema document:its type is N=

atorg.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:211)

atsun.reflect.GeneratedMethodAccessor6.invoke(UnknownSource)

atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

atjava.lang.reflect.Method.invoke(Method.java:585)

atorg.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)

atorg.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553)

Specifically, WorkSpaceStudio 1.1 can generatethe exception when youdo the following:

1. Click the Serverstab and add a newserver.

2. Double-click a dataservice (a .ds file)to display the dataservice in theOverview tab.

3. Add an operationby right-clicking inthe Overview areaand choosing AddOperation.

Workaround Contact BEA CustomerSupport to requestpatch E36K for ASDSP3.2.

CR366025 3.2 Reinstalling ALDSP3.2 generates thefollowing error: "ABEA product orcomponent is alreadyinstalled in thisdirectory."


Platform All.

Description The error appears whenattempting to reinstallALDSP 3.2 in a<BEAHOME> directorywhere ALDSP 3.2 andany of the followinghave been installed anduninstalled:

• WebLogic Platform10.2

• WebLogic Portal10.2

• AquaLogic ServiceBus (ALSB) 3.0

• AquaLogicIntegrator (ALINT)3.0

Workaround When reinstalling ALDSP3.2, choose a new<BEAHOME> directory.

CR354149 3.2 3.2 Alias names inuser-defined SQLqueries may beignored whencreating SQLquery-based dataservices usingnon-core supporteddatabases.

Platform All.

Description JDBC version 4.0slightly modified thesemantics of thefollowing methods:

java.sql.ResultSetMetadata.getColumnName()java.sql.ResultSetMetadata.getColumnLabel()

In JDBC 3.0 and earlier,the getColumnName()

method returned aliasesas specified by the SQLAS clause. In JDBC 4.0,the call instead returnsthe original columnname, if available.Column aliases areavailable using thegetColumnLabel()

method.


Solution Do the following:

1. Create a customXML provider.

2. Set the followingattribute:

custom-rdb-provider/database-objects/column/@label-property-in-query-metadata

Set the attribute tocolumn-label tohave the driveruse thegetColumnLabel()

method to retrievethe alias (or actualname if there is noalias).Set the attribute tocolumn-name tohave the driveruse thegetColumnName()

method.

The attribute isoptional; if it isnot present thenthe value of theparent provideris used. NotethatAbstractSQLProvideruses thegetColumnName()

method.

CR359755 3.2 Stored proceduresmay return anincorrectly roundedvalue for the MONEYdatatype using theBEA SQL Server JDBCdriver.

Platform All (using BEA SQLServer JDBC driver).

Description When using the BEASQL Server JDBC driver,stored procedures mayincorrectly roundMONEY datatype values.For example, consider


the following storedprocedure:

ALTER PROCEDURE[wireless].[SP_SMALLMONEY_OUT]( @P_IDVARCHAR(10),@P_SMALLMONEYSMALLMONEY OUT)ASBEGINSELECT@P_SMALLMONEY =C_SMALLMONEYFROM ALL_DATATYPESWHERE C_ID = @P_IDEND

Using an original valueof 234.4000 in thedatabase, the BEA SQLServer driver returnsthe following incorrectvalue:

234

Workaround Contact BEA CustomerSupport to request theBEA SQL Server JDBCDriver Version3.4.0057. Alternatively,use the Microsoft SQLServer JDBC driver.

CR361824 3.2 A source upgrade of aWorkshop 8.1 JWS toWorkshop 10 maycause failures whencommunicating withold clients.

Platform All.

Description A source upgrade of aWorkshop 8.1 JWS toWorkshop 10 maygenerate differentWSDL definitions andcause failures whencommunicating with oldclients.

Workaround There are severalfunctionality changesbetween Workshop 8.1JWS and Workshop 10JWS implementations.


Refer to the followinglink to identify andresolve source upgradedjws files in Workshop10:http://edocs.bea.com/wlw/docs102/guide/upgrading/conUpgradingWebServices.html

CR362948 3.2 The fn-bea:delete()

andfn-bea:replace-value()

XQuery mutatorfunctions generate anerror when the pathcontains '//' in thefinal level.

Platform All.

Description When using thedelete() orreplace-value()

XQuery mutatorfunctions, the systemgenerates an error if thepath ends with//@attribute or//element_of_a_simple_type.Consider the followingprocedure:

declare proceduretns:test_delete_path_descendant-or-self_axis3(){

declare $custaselement(xs1:Customer):=ds1:getCustomerById(3);

declare $ce aschanged-element(xs1:Customer);

set $ce :=fn-bea:enable-changes($cust);

set $ce :=fn-bea:delete($ce,'.//@USE');ds1:updateCustomer($ce);}

The proceduregenerates the followingerror because .//@USE

is used to specify thepath when calling thefn-bea:delete()

function:

{bea-err}MUT007:Could notconstruct an XPaththat selects theparent node forXPath ".//@USE"


http://edocs.bea.com/wlw/docs102/guide/upgrading/conUpgradingWebServices.html

Note that the path cancontain '//' but notpreceding the final levelin the path. Forexample, the followingis valid:

x//y/z

But, the followinggenerates an error:

x//z

Note also that you canspecify//element_of_a_complex_type

at any level.

Workaround None.

CR362224 3.2 ALDSP 3.2 does notpush downoperations on BITdatatypes.

Platform All (using Microsoft SQLServer and Sybase).

Description Unlike ALDSP 3.0,ALDSP 3.2 does notpush down operationson BIT datatypes whenusing Microsoft SQLServer or Sybasedatabases.

Workaround None.

CR366180 3.2 Tabular view in theTest tab ofWorkSpace Studio 1.1may incorrectlyswitch the display of@attr and elementvalues.

Platform All.

Description When displaying resultsin the Test tab ofWorkSpace Studio 1.1,an element value mayappear in the @attrcolumn and the @attr


value may appear inplace of the firstelement.

Workaround Use the Tree view orText view to display theresults.

CR364732 3.2 Using complex typeswith simple contentfrom an ALDSP 3.2client to an ALDSP3.0 server maygenerate anoptimistic lockingfailure errors.

Platform All.

Description Using complex typeswith simple contentfrom an ALDSP 3.2client and serializing itto an ALDSP 3.0 servermay generate anoptimistic locking failuredue to incorrectprocessing of thechange summary on theALDSP 3.0 server.

Workaround Upgrade the ALDSP 3.0server to an ALDSP 3.2server if using complextype with simplecontent.

CR366431 3.2 Business Objects andCrystal Reports TableBrowser displays thesame column namemultiple times.

Platform All.

Description Publishing data servicefunctions to a SQL mapusing the same tablename in multipleschemas can causecertain reporting tools,such as BusinessObjects and CrystalReports, to display thesame column namemultiple times (as manytimes as the table ispublished) in the Table


Browser user interface.

Workaround Do not use the sametable name in multipleschemas whenpublishing data servicefunctions to a SQL map.

CR365752 3.2 Data Services Studiouser interfacebehavior is replacedwith WorkspaceStudio after installingALDSP 3.2 in anexisting ALDSP 3.0BEA_HOME directory.

Platform All.

Description When installing ALDSP3.2 in the sameBEA_HOME directory asa current installation ofWebLogic Server 9.2.2and ALDSP 3.0, theinstallation applicationrecognizes the presenceof Data Services Studio(Eclipse 3.2.2) andinstalls new plug-ins forboth WorkSpace Studio1.1 and Data ServicesStudio.After the installation iscomplete, the DataServices Studio userinterface behavior isreplaced withWorkspace Studio.

Workaround Install ALDSP 3.2 in anew BEA_HOMEdirectory.

CR365527 3.2 ALDSP classpathpatch does notappear in the serverlogs.

Platform All.

Description After using the BEASmart Update tool toinstall the ALDSPclasspath patch, arecord of the patch doesnot appear in the serverlogs.


Workaround To get the patchinformation, do thefollowing:

1. Set the domainpath by running:

setDomainEnv.cmd

or

setDomainEnv.sh

2. Run the java

weblogic.version

-verbose

command to printthe version. Theoutput appearssimilar to thefollowing:

WebLogic ServerTemporary Patchfor CR345472 ThuJan 17 16:13:48EST 2008ImplVersion:10.0.1.0WebLogicServer TemporaryPatch for CR322355Tue Oct 2310:53:45 PDT 2007ImplVersion:10.0.1.0AquaLogicDataServicesPlatform 3.2 10.0SP1 2008-03-2115:32:50 PDTPatch for CR365525ImplVersion:10.0.1.0

CR357742 3.0 3.2 Unable to start theAquaLogic DataServices Platform 3.0sample domain fromthe QuickStart page.

Platform All.

Description When attempting tolaunch the ALDSP 3.0sample domain byclicking the "StartAquaLogic DataServices Platform 3.0"link on the QuickStartpage, a pop-up window


appears displaying thefollowing message:

The link to thisapplication hasnot beenimplemented yet.Check this outlater!

Workaround Click Start -> BEAProducts -> BEAAquaLogic DataServices Platform ->Examples -> StartExamples Server tostart the sampledomain.

CR258884 3.0 Security filterdecisions are notaudited.

Platform All.

Description Security filter decisions(XQuery functions forsecurity) are notaudited.

Workaround None.

CR345482 3.0 Hyperion InteractiveReporting System isnot supported.

Platform All.

Description ALDSP 3.0 does notsupport the HyperionInteractive ReportingSystem.

Workaround None.

CR339279 3.0 Upgrading ALDSP 2.5projects that includemultibyte charactersmay generate errorsand produce garbledcharacters.

Platform All.

Description When upgrading anALDSP 2.5 project thatincludes multibytecharacters to ALDSP3.0, the following errormay appear in the log


view:

'Some characterscannot be mapped'

Similarly, when openingthe updated dataservice file, thefollowing error mayappear:

'ExceptionMessage: 'Somecharacters cannotbe mapped'MS932'

Garbled characters mayalso appear in the dataservice file.

Workaround The data service filewas properly upgraded.Reopen the data servicefile to have themultibyte charactersappear properly.

CR266307 3.0 Namespace URIs canbecome invalid whenusing file and foldernames containingembedded spaces.

Platform All.

Description ALDSP does not supportfile and folder namescontaining one or moreembedded spaces. Thiscan cause namespaceURIs to become invalidduring certainoperations such as aRefactor > Move andRefactor > Rename,among others.

Workaround Do not create file orfolder names containingembedded spaces.

CR350103 3.0 ALDSP licensechangesunexpectedly afterinstalling a newversion.

Platform All.


Description ALDSP uses the firstlicense found in theAquaLogic DataServices Platformlicense group (in thelicense.bea file). If youinstall multiple versionsof ALDSP, your licensemay changeunexpectedly becauseof the order of thelicenses, as shown inthe following segment:

<license-groupformat='1.0'product='AquaLogicData ServicesPlatform'release='3.0'>

<licensecomponent='DataServices Runtime'cpus='unvalued'expiration='2008-01-28'

ip='any'licensee='BEAEvaluationCustomer'signature='ZgOAWQ...'

type='EVAL'units='5'

/><license

component='DataServices Runtime'cpus='unvalued'expiration='2008-06-04'

ip='any'licensee='BEAEvaluationCustomer'serial='616351266349-2343532799844'signature='MC4CFQ...'

type='EVAL'units='unlimited'

/></license-group>

Note that in thisexample, the number of"units" in the licensechanges from anunlimited number tofive.

Workaround If you have multipleversions of ALDSPinstalled, do thefollowing:

1. Verify that themost flexiblelicense appearsfirst in the


AquaLogic DataServices Platformlicense group (inthe license.beafile).

2. Restart the server.

CR346860 3.0 ALDSP 2.5 SDOGenWeb service clientsneed additional stepsto run in backwardcompatibility mode.

Platform ALDSP 2.5

Description ALDSP 2.5 Web serviceclients that use staticSDOGen do not workout-of-the-box after theALDSP server and theDSP Control/JWS issource upgraded.

Workaround To use static SDOGenWeb service clients, dothe following:

1. In the sourceupgraded JWS file,modify theportName attributeof the@WLHttpTransportannotation andensure that itmatches the entrypresent in the 8.1generated WSDL.

2. Generate theWSDL file for theJWS and save thefile to a local disk.

3. Remove theparameterOrderattribute from theWSDL file.

4. Use the savedWSDL file in theclient instead ofthe WSDL filedynamicallyavailable from theJWS.For example,consider thefollowing WebLogic


8.1 call:

String wsdl ='http://acme/services/CustReadCtrlTest.jws?WSDL'weblogic.jws.proxies.CustReadCtrlTestSoapsoapCtrl = newweblogic.jws.proxies.CustReadCtrlTest_Impl(wsdl).getCustReadCtrlTestSoap();

Modify thestatement tomatch thefollowing:

String wsdl='file://local/services/CustReadCtrlTest.wsdl';weblogic.jws.proxies.CustReadCtrlTestSoapsoapCtrl = newweblogic.jws.proxies.CustReadCtrlTest_Impl(wsdl).getCustReadCtrlTestSoap()

CR351310, CR351492 3.0 Missing entries in thegeneration log.

Platform All.

Description The generation log maynot contain entries fortarget entities thatcannot be updated. Inthis case, the updatemap may beincomplete.

Workaround None.

CR337329 3.0 Running ALDSP 3.0 inthe same domain asWebLogic Integration(WLI) 9.2 can causeconflicts.

Platform ALDSP 3.0 andWebLogic Integration9.2

Description ALDSP 3.0 and WLI 9.2install incompatibleversions of thexquery.jar file. Thesoftware installed byALDSP 3.0 is a newerversion and is notcertified for use withWLI 9.2.

Workaround Do not create a domainthat is provisioned forALDSP 3.0 andWebLogic Integration


9.2.

CR354314 3.0 3.2 Changes made tomultiple dataspacesin a single session donot apply to alldataspaces atruntime.

Platform All.

Description After acquiring a lockfor a session, makingchanges to multipledataspaces, andcommitting the session,the changes arereflected only in a singledataspace. RestartingWebLogic Server causesthe changes to bereflected in all modifieddataspaces.

Workaround Make changes to only asingle dataspace duringa session. Aftercommitting the session,start a new session tomake changes toanother dataspace.

CR344413 3.0 Importing anAquaLogic ServiceBus (ALSB) SB proxyor accessing an ALSBSB proxy physicaldata service requiresthe ALSB sbresourceservlet to beavailable.

Platform All.

Description When importing webservices that are routedthrough an ALSB SBproxy, ALDSP requeststhe SB proxy WSDLthrough the ALSBsbresource servlet.Similarly, whenaccessing a physicaldata service that wascreated using the ALSBSB proxy, the ALDSPruntime retrieves the SB


proxy WSDL throughthe ALSB sbresourceservlet.Both operations requirethat the ALSB sbreourceservlet be available andrunning.

Workaround Ensure that the ALSBsbreource servlet isdeployed and running.

CR343216 3.0 Oracle timestampwith time zonereturns an incorrectvalue.

Platform Oracle 9i (using the BEAOracle JDBC driver).

Description The timestamp (withtime zone) returnedusing the BEA OracleJDBC driver may beincorrect.

Workaround Use the native OracleJDBC driver.

CR341851 3.0 An upgraded JWSthat returns anXMLBean type willnot compile.

Platform Workshop for WebLogicPlatform 9.2.2

Description All operations on anupgraded JWS thatreturns an XMLBeantype will have a compileerror similar to thefollowing after theupgrade:

The name'getCustomerByIdResult'specified injavax.jws.WebResultis different tothe XmlBean nameof 'CUSTOMER'

The message indicatesthat the return typedoes not match theelement name definedby the XMLBeanschema.


Workaround Remove the@WebResult annotationor change the name tomatch the schema type.

CR338622 3.0 3.2 Test View in ALDSPdoes not perform fullXML Schemavalidation of theresults of anoperation.

Platform All.

Description Schema validationbehavior has changedfrom ALDSP 2.x toALDSP 3.0. UsingALDSP 2.x, schemavalidation occurs on thequery return. In ALDSP3.0, the validation isperformed at the SDOstructural level anddoes not constitute afull schema validation.

Workaround During testing,temporarily wrap thefunction body using theXQuery validateconstruct to validate theresults of calling thefunction against theXML Schema, as shownin the followingexample:

validate {xquery

expression}

CR342747 3.0 Crystal Reports isunable to use readfunctions (acceptingno parameters)published as storedprocedures.

Platform Crystal Reports (usingthe JDBC driver).

Description Using a read function(accepting noparameters) publishedas a stored procedure


with Crystal Reportsgenerates an exceptionsimilar to the following:

java.sql.SQLException:Invalid storedprocedurereference:ReportingToolCertDataServices.Xtreme.'Read

atcom.bea.dsp.jdbc.exceptions.DSPExceptionFactory.create(DSPExceptionFactory.java:148)

atcom.bea.dsp.jdbc.driver.CallableDSPStatementImpl.updateWithNamedParameters(CallableDSPStatementImpl.java:2913)

Workaround Publish the readfunction withoutparameters as a tableinstead of a storedprocedure.

CR345630 3.0 The ALDSP 2.5 serverside streaming APIcannot be used inALDSP 3.0 withoutmodification.

Platform All.

Description In ALDSP 2.5, thestreaming API isavailable on the serverside only when used inthe same ALDSP 2.5application as a localMediator API client.ALDSP 3.0, however, nolonger uses the J2EEdeployment model fordataspace deployment.As a result, a clientusing the ALDSP 2.5streaming API cannotbe deployed inside anALDSP 3.0 dataspace.Doing so results in thefollowing exception:

javax.naming.LinkException.

Workaround ALDSP 3.0 supports thestreaming API for allJava Mediator APIclients (remote andlocal). Modify thestreaming API clientcode to use the ALDSP3.0 Java Mediator API


and use the streamingfacility in this API.

CR317803 3.0 Unable to displaydata lineage graphusing the MetadataBrowser withNetscape 8.1.

Platform Microsoft Windows,Netscape 8.1

Description When using Netscape8.1, clicking the DataLineage tab in theMetadata Browser maynot display the datalineage graph norprompt to download andinstall the SVG viewer.

Workaround To view data lineagegraphs using Netscape8.1, do the following:

1. Close the Netscapebrowser.

2. Download andinstall SVG viewerplug-in.

3. Copy theNPSVG3.dll file tothe<NetscapeHome>/pluginsfolder.

4. Restart theNetscape browser.Alternatively, youcan use thetabular view of theMetadata Browserto display the datalineage.

CR343348 3.0 The fn:doc() andfn-bea:collection()functions cannot beaccessed using theclient API.

Platform All.

Description ALDSP 3.0 does notoffer access to thefn:doc() andfn-bea:collection()functions through the


client API. Thesefunctions can causesecurity vulnerabilitiesand are thereforeblocked from clientaccess. The functionsare, however, availablefor use within dataservice XQuery bodies.

Workaround None.

CR318031 3.0 The Eclipse IDEdisplays the followingerror message: "Anout of memory errorhas occurred."

Platform All.

Description When working with theEclipse IDE, an "InternalError" dialog appearsdisplaying the followingerror message:"An out of memoryerror has occurred...Doyou want to exit theworkbench?"

Workaround Do the following:

1. Edit theconfiguration file.When using theData ServiceStudio to launchEclipse, edit the$<ALDSP_HOME>/bin/aldsp.inifile. When usingEclipseindependent ofData ServiceStudio, edit theeclipse.ini file.

2. Specify thefollowing memoryparameters for theEclipse IDE:

-vm<JDK_home>/jre/bin/java.exe-clean-vmargs-Xms256m-Xmx1024m-XX:PermSize=128m


CR347480 3.0 Upgrading anapplication to ALDSP3.0 may produce thefollowing errormessage: "Thisproject needs tomigrate WTPmetadata."

Platform All.

Description When upgrading anapplication from ALDSP2.5 to ALDSP 3.0, thefollowing error mayappear under theProblems tab:

This project needsto migrate WTPmetadata

Workaround This is an Eclipse errorand can occurindependent of ALDSP.Do the following:

1. Using Studio,rename theproject.

2. Select the projectin the ProjectExplorer andchoose Project >Build Automaticallyfrom the mainmenu to toggle thefeature off.

3. Select the projectin the ProjectExplorer andchoose Project >Clean from themain menu.

4. Close and relaunchStudio.

5. Optionally, renamethe project to theoriginal name.

6. Select the projectin the ProjectExplorer andchooseProject->BuildAutomatically fromthe main menu to


toggle the featureon.

CR347074 3.0 Changes to thedatabase definitionare not reflected inPreparedStatementcalls or in the dataservice after updatingthe metadata.

Platform All.

Description SQL queries use thePreparedStatementinterface which, bydefault, is cached by theWebLogic Server. Thedefault JDBCPreparedStatementcache size for is 10.This can result inincorrect preparedstatements being usedfrom the cache whendatabase table orcolumn definitions havechanged betweenprepared statementcalls.

Workaround Set thePreparedStatementcache size to 0 whenthe database tabledefinitions are changed.Using the WebLogicServer AdministrationConsole, do thefollowing:

1. Click to expand theServices, JDBC,and ConnectionPool nodes todisplay the list ofconnection pools inthe currentdomain.

2. Click theconnection poolthat you want toconfigure. A dialogdisplays in theright pane showingthe tabs associated


with this instance.3. Click the

Configuration tab,then click theConnections tab.

4. In StatementCache Size, enterzero (0) for thenumber ofstatements tocache perconnection perconnection poolinstance.

5. Click Apply to saveyour changes.

6. Reset the value ofthePreparedStatementcache size to theoriginal value.

CR297695 3.0 An "optimistic lockingfailure" exception canoccur if Oracle checksfor an empty stringwhen the actual valueis null.

Platform Oracle

Description Oracle stores bothempty strings and nullstrings as NULL, andboth are alwaysreturned as NULL whichmay cause an optimisticlocking error during anupdate operation.Consider the followingmapping:

<SomeElement>{data($db_row/VARCHAR_COLUMN)}</SomeElement>

whereVARCHAR_COLUMN is adatabase column ofVARCHAR type. In thiscase, the element isalways created evenwhen the column valueis NULL. An SDOmapping wouldtherefore map an empty


element to the emptystring value "".When the updatedelement is submitted tothe database, thefollowing exceptionoccurs:DataServiceException:Optimistic lockingfailureThe exception occursbecause theDSP-generated SQLstatements instructOracle to check for anempty string when theactual value is NULL.

Workaround Map the column to anoptional element, asshown in the following:

<SomeElement?>{data($db_row/VARCHAR_COLUMN)}</SomeElement>

This ensures that theelement is not created ifthe column value isNULL.

CR345834 3.0 Expensive functionsin LET clauses, suchas calls to webservices, may beinvoked multipletimes resulting indegradedperformance.

Platform All.

Description XQuery 3.0 inlines LETclauses that are usedonly once. This canaffect the number oftimes an expensivefunction, such as a webservice, is called.For example, considerthe following query:

declare functiontns:test($id1 asxs:string, $id2 asxs:string ){let $order1 :=tes:getOrder($id1)/OrderDetail


let $order2 :=for $x in

tes:getOrder($id2)/OrderDetailreturn

<ORDER><ORDER_ID>{fn:data($x/stns:orderID)}</ORDER_ID>

</ORDER>

for $o1 in$order1

return<ORDER>

<ORDER_ID>{fn:data($o1/stns:orderID)}</ORDER_ID><ORDER_DATE>{fn:data($o1/stns:orderDate)}</ORDER_DATE><TOTAL_ORDER_AMOUNT>

{fn:data($o1/stns:totalOrderAmount)}</TOTAL_ORDER_AMOUNT>

<STATUS>{

$order2[$o1/stns:orderDate=$o1/stns:estimatedShipDate]}</STATUS>

</ORDER>};

In this example, ALDSP3.0 inlines both $order1and $order2 since eachare used only once afterbeing defined. Thiscauses the system toperform repeatedevaluations of the webservice calls as part ofthe FOR clause (insteadof retrieving the savedvalues from thevariables) resulting indegraded performance.

Workaround Configure ALDSP toprevent the inlining ofexpensive LET clausesin loops by doing thefollowing:

1. Set the followingsystem property tofalse:

weblogic.xml.query.compiler.INLINE_SINGLE_EXPENSIVE_LETS_INTO_LOOPS=false

2. Restart theWebLogic Server.By default thisproperty is set totrue (which is alsothe defaultbehavior of ALDSP2.5).


CR314392 3.0 An exception occurswhen deploying anALDSP 3.0 applicationgenerated usingWorkshop forWebLogic 9.2 MP1 orearlier.

Platform ALDSP 3.0, Workshopfor WebLogic 9.2 MP1 orearlier.

Description An exception can occurwhen deploying anALDSP 3.0 application(using the AdminConsole) using a WSDLfile generated fromWorkshop for WebLogic9.2 MP1 or earlier.ALDSP does not supportWSDL files generatedusing Workshop forWebLogic 9.2 MP1 orearlier.

Workaround Generate the WSDLusing Workshop forWebLogic 9.2 MP2 andthen rebuild andredeploy theapplication.

CR321293 3.0 The server is unableto locate a referencedschema file specifiedusing the Eclipse XSDEditor.

Platform Eclipse XSD Editor onMicrosoft Windows

Description Microsoft Windows doesnot distinguish case infile and folder names.Therefore, the EclipseXSD Editor on MicrosoftWindows will not flag anerror when you specifya schema file nameusing incorrect case. Forexample, the editor willnot flag the followingentry when the actualschema file name isProfileView.xsd:


<xsd:importnamespace="urn:test"schemaLocation="profileView.xsd"/>

Workaround Verify the case whenreferencing schema filenames using the EclipseXSD Editor on MicrosoftWindows.

CR327132 3.0 A schema isgenerated with"minOccurs=0" for allcolumns, not justcolumns that are notnull.

Platform Informix (using BEA XAand BEA Non-XA JDBCdrivers).

Description When creating aschema using anInformix database witheither BEA XA or BEANon-XA drivers, aschema is generatedwith "minOccurs=0" forall columns, not justcolumns that are notnull.

Workaround None.

CR327305 3.0 The nativeSize ofdata types appears aszero (0) afterimporting tablesusing Sybase drivers.

Platform Sybase (using SybaseJDBC drivers)

Description When using Sybasedrivers, the nativeSizeof data types appear aszero (0) after importingtables, as shown in thefollowing sampleoutput:

xquery version"1.0" encoding"WINDOWS-1252";(::pragma xds<x:xdsxmlns:x="urn:annotations.ld.bea.com"targetType="t:sqlQuery"


xmlns:t="ld:SY/datasource/TC_SQLWhereWithConstant/sqlQuery"><creationDate>yyyy-mm-ddThh:mm:ss</creationDate><relationalDBname="datasource"providerId="Sybase-12.5.2"/><fieldxpath="FIRST_NAME"type="xs:string">

<extensionnativeXpath="FIRST_NAME"nativeType="varchar"nativeTypeCode="12"nativeSize="0"nativeFractionalDigits="0"/>\\

<propertiesnullable="false"/></field><fieldxpath="LAST_NAME"type="xs:string">

<extensionnativeXpath="LAST_NAME"nativeType="varchar"nativeTypeCode="12"nativeSize="0"nativeFractionalDigits="0"/>\\

<propertiesnullable="false"/></field>

Workaround Use the BEA SybaseJDBC drivers.

CR327820 3.0 Certain SQL queriesmay generate aschema with amissing elementname.

Platform Sybase

Description When using Sybase,SELECT statementssimilar to the followingmay generate schemaswith a missing elementname:

SELECTt1.PRODUCT_ID,sum(t2.QUANTITY)FROM PRODUCT t1JOINCUST_ORDER_LINE_ITEM_APPLt2 on(t1.PRODUCT_ID =t2.PRODUCT_ID)GROUP byt1.PRODUCT_ID

Workaround Specify aliases for thecolumns in the SQLstatements. Forexample, you couldrewrite the previousSELECT statement as


follows:

SELECTt1.PRODUCT_ID asPRODUCT_ID,sum(t2.QUANTITY)as QUANTITYFROM PRODUCT t1JOINCUST_ORDER_LINE_ITEM_APPLt2 on(t1.PRODUCT_ID =t2.PRODUCT_ID)GROUP byt1.PRODUCT_ID

CR328457 3.0 The Oracle JDBCdriver and the BEAOracle JDBC driverreturn differentlengths for CHARoutput parameters instored procedures.

Platform Oracle (using the OracleJDBC driver and BEAOracle JDBC driver).

Description The Oracle driver andthe BEA Oracle drivermay return differentlengths for CHAR outputparameters in storedprocedures. Forexample:

CREATE OR REPLACEPROCEDUREMYPROCEDURE1(P_CHAR_OUTOUT CHAR)...<procedure_body>...

In this example,P_CHAR_OUT is theoutput parameterreturned by the storedprocedure.

Workaround None.

CR328861 3.0 Ad-hoc queries inDSP controls thatreturn XML that doesnot conform to thedeclared XML typegenerate anexception.

Platform All.

Description When writing ad-hocqueries in a DSP


control, if the ad-hocquery returns XML thatdoes not conform to thedeclared XML type, thefollowing exception isgenerated whilemarshalling the SDOdata object.

java.lang.IllegalArgumentException:A type with thisname'ADDRESS_TYPE@urn:schemas-bea-com:ld-addr'already exists inthis type system.<ComponentHandler.handleRequest:115>java.lang.IllegalArgumentException:A type with thisname'ADDRESS_TYPE@urn:schemas-bea-com:ld-addr'already exists inthis type system.

Workaround Ensure that ad-hocqueries in DSP controlsconform to the XMLschema for the returntype.

CR331184 3.0 An exception occurswhile parsing a NEIMschema.

Platform All.

Description An XmlExceptionexception similar to thefollowing may occurwhile parsing a NEIMschema (whenattempting to create adata service andassociated schema, forexample):

org.apache.xmlbeans.XmlException:D:\EclipseWorkspaces\DSPDemo\NEIM\Schema\lexs\lexs.xsd:54:5:error: Problemparsing referencedXML resource -D:\EclipseWorkspaces\DSPDemo\NEIM\Schema\lexs\lexs-digest.xsd:689:1:error: Unexpectedelement: CDATAatorg.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225)

This may be caused byextra newline andwhitespace charactersat the end of the file.


Workaround Remove any newline orwhitespace charactersfrom the end of theNEIM schema file.

CR332755 3.0 An exception canoccur when using theALDSP 2.5 JDBCdriver with ALDSP 3.0applications.

Platform All.

Description When attempting to geta connection using theALDSP 2.5 JDBC driver(ldjdbc.jar) with anALDSP 3.0 application,anIncompatibleClassChangeErrorexception can occursimilar to the following:

Exception inthread "main"java.lang.IncompatibleClassChangeError:Implementing class

atjava.lang.ClassLoader.defineClass0(NativeMethod)

atjava.lang.ClassLoader.defineClass(ClassLoader.java:539)

atjava.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)

Workaround Contact BEA CustomerSupport to request thepatch for CR333047(patch file:CR333047_810sp6.jar)and add the file to yourclient classpath.

CR333489 3.0 XQueries may returnan incorrecttimestamp using theBEA XA driver.

Platform Oracle (using the BEAXA JDBC driver).

Description The BEA XA driver mayreturn an incorrecttimestamp when issueda query similar to thefollowing:

<result>{for $i in


f1:DATA_TIMESTAMP_ZONE()return

<row>{$i/C_ID}{if

(fn:data($i/C_TIMESTAMP_ZONE_3)instance ofxs:dateTime) then<C_TIMESTAMP_ZONE_3><type>TIMESTAMP_ZONE</type><xmltype>xs:dateTime</xmltype><data>{fn:data($i/C_TIMESTAMP_ZONE_3)}</data></C_TIMESTAMP_ZONE_3>

else<C_TIMESTAMP_ZONE_3></C_TIMESTAMP_ZONE_3>

}</row>

}</result>

In this example, theexpected return value isthe following:

<C_TIMESTAMP_ZONE_3><type>TIMESTAMP_ZONE</type><xmltype>xs:dateTime</xmltype><data>1999-04-15T08:00:00-07:00</data></C_TIMESTAMP_ZONE_3>

The BEA XA driverinstead returns thefollowing:

<C_TIMESTAMP_ZONE_3><type>TIMESTAMP_ZONE</type><xmltype>xs:dateTime</xmltype><data>1999-04-09T17:20:00+09:00</data></C_TIMESTAMP_ZONE_3>

Workaround Use the Oracle nativeXA JDBC driver.

CR333689 3.0 XQueries may returninconsistent resultsusing the BEA XAdriver.

Platform Oracle (using the BEAXA JDBC driver).

Description The BEA XA driver mayreturn inconsistentresults when issued aquery similar to thefollowing:

declare namespacens ="ld:test/RDBMS/OR-CR/DATA_NUMBER";declare namespacens1 ="ld:test/RDBMS/OR-CR/DATA_FLOAT";declare namespace


ns2 ="ld:test/RDBMS/OR-CR/DATA_NUMBER_N_S";declare namespacens3 ="ld:test/RDBMS/OR-CR/DATA_NUMBER_N";declare variable$ext as xs:decimalexternal;

<result>{

<column>{

let $x :=for $y inns:DATA_NUMBER()

where($y/C_ID mod 2)ne 0

return$y/C_NUMBER mod$y/C_ID

return(<all>

<test1>{$x}</test1><sql>{fn-bea:get-sql($x)}</sql>

</all>)

}</column>

}{

<const>{

let $x :=for $y inns1:DATA_FLOAT()

where$y/C_ID gt($y/C_FLOAT mod 2)

returnfn:concat(xs:string($y/C_ID),xs:string( 5 mod4))

return(<all>


</all>)

}</const>

}{

<func>{

let $x :=for $y inns2:DATA_NUMBER_N_S()

wherefn:string-length(xs:string($y/C_ID))eq fn:abs( -5 mod4)

returnfn:concat(xs:string($y/C_NUMBER_38_38), xs:string(4 mod5))

return(<all>


</all>)

}</func>


}{

<join>{

let $x:= for$y inns:DATA_NUMBER()

for $z inns2:DATA_NUMBER_N_S()

where$y/C_ID eq $z/C_ID

return$y/C_NUMBER mod$z/C_NUMBER_38_38

return(<all>


</all>)

}</join>

}{

<orderby>{

let $x:= for$y inns:DATA_NUMBER()

where true()order by

$y/C_ID mod$y/C_NUMBER

return$y/C_ID mod$y/C_NUMBER

return(<all>


</all>)

}</orderby>

}</result>

In this example, theexpected return value isthe following:

<result><column><all><test1>1.1E-1302.33</test1><sql>SELECTMOD(t1.'C_NUMBER',CAST(t1.'C_ID'AS NUMBER)) AS c1FROM'CRM'.'DATA_NUMBER't1WHERE(MOD(t1.'C_ID',2)!=0)</sql></all></column><const><all><test2>112131</test2><sql>SELECT(TO_CHAR(t1.'C_ID')|| '1') AS c1FROM'CRM'.'DATA_FLOAT't1WHERE(CAST(t1.'C_ID' AS


NUMBER) >MOD(t1.'C_FLOAT',2.0))</sql></all></const><func><all><test3>.123456789012345678901234567890123456784.1234.14</test3><sql>SELECT(TO_CHAR(t1.'C_NUMBER_38_38')|| '4') AS c1FROM'CRM'.'DATA_NUMBER_N_S't1WHERE(NVL(LENGTH(TO_CHAR(t1.'C_ID')),0)=1)</sql></all></func><join><all><test1>1.1E-130-1.1E-300.03</test1><sql>SELECTMOD(t1.'C_NUMBER',CAST(t2.'C_NUMBER_38_38'ASNUMBER)) AS c1FROM'CRM'.'DATA_NUMBER't1JOIN'CRM'.'DATA_NUMBER_N_S't2ON (t1.'C_ID' =t2.'C_ID')</sql></all></join><orderby><all><test1>-INF9.0E-310.67</test1><sql>SELECTMOD(CAST(t1.'C_ID'ASNUMBER),t1.'C_NUMBER')AS c1FROM'CRM'.'DATA_NUMBER't1ORDER BYMOD(CAST(t1.'C_ID'ASNUMBER),t1.'C_NUMBER')ASC</sql></all></orderby></result>

The BEA XA driverinstead returns thefollowing:

<result><column><all><test1>1.1E-1302.33</test1><sql>SELECTMOD(t1.'C_NUMBER',CAST(t1.'C_ID'AS NUMBER)) AS c1FROM'CRM'.'DATA_NUMBER't1WHERE(MOD(t1.'C_ID',2)!=0)</sql></all></column><const><all><test2>112131</test2><sql>SELECT(TO_CHAR(t1.'C_ID')|| '1') AS c1FROM'CRM'.'DATA_FLOAT't1WHERE(CAST(t1.'C_ID' ASNUMBER) >MOD(t1.'C_FLOAT',2.0))</sql></all></const><func><all><test3>.123456789012345678901234567890123456784.1234.14</test3><sql>SELECT(TO_CHAR(t1.'C_NUMBER_38_38')|| '4') AS c1FROM


'CRM'.'DATA_NUMBER_N_S't1WHERE(NVL(LENGTH(TO_CHAR(t1.'C_ID')),0)=1)</sql></all></func><join><all><test1>1.1E-130-1.1E-300.03</test1><sql>SELECTMOD(t1.'C_NUMBER',CAST(t2.'C_NUMBER_38_38'ASNUMBER)) AS c1FROM'CRM'.'DATA_NUMBER't1JOIN'CRM'.'DATA_NUMBER_N_S't2ON (t1.'C_ID' =t2.'C_ID')</sql></all></join><orderby><all><test1>0.09.0E-310.67</test1><sql>SELECTMOD(CAST(t1.'C_ID'ASNUMBER),t1.'C_NUMBER')AS c1FROM'CRM'.'DATA_NUMBER't1ORDER BYMOD(CAST(t1.'C_ID'ASNUMBER),t1.'C_NUMBER')ASC</sql></all></orderby></result>

Workaround Use the Oracle nativeXA driver.

CR334116 3.0 RequestConfig.OUTPUT_FILENAMEand invokeToFile()causes aDASException tooccur.

Platform All.

Description TheRequestConfig.OUTPUT_FILENAMEcapability has beenremoved from ALDSP3.0. Similarly, themediator functioninvokeToFile() is nolonger available inALDSP 3.0 Note that theRequestConfig.OUTPUT_FILENAMEflag is still available toensure backwardcompatibility withcertain methods,however, the feature isno longer supported inALDSP 3.0 and causesthe DASException tooccur if used.


Workaround None.

CR324401 3.0 Binary stringdatatype parametersto DB2 storedprocedures maycause an exception tooccur.

Platform DB2

Description Using binary stringdatatype parameters(for bit data) with DB2stored procedures maycause anXQueryTypeExceptionsimilar to the followingto occur:

Caused by:weblogic.xml.query.exceptions.XQueryTypeException:[ad-hoc], line 3,column 39:{err}XP0004:Invalid statictype:{http://www.w3.org/2001/XMLSchema}hexBinary

atweblogic.xml.query.compiler.TypeMatchExpression.typeCheckNoCache(TypeMatchExpression.java:124)

atweblogic.xml.query.compiler.Expression.typeCheck(Expression.java:308)

Workaround Do not use binary stringdatatype parameterswith DB2 storedprocedures.

CR329108 3.0 Projects are notlisted when addedduring new serverconfiguration.

Platform All.

Description Projects do not appearunder a configuredserver in the ServerView when youcomplete the followingsteps:

1. You create a newserver and thendelete the server(maintaining theconfiguredruntime).

2. You create a newdataspace runtime


(the targetruntime is definedbut not the targetdeploymentserver).

3. You add a newserver using thesame runtimecreated earlier.

4. You add theproject whilecreating theserver.

Workaround When adding theproject, click 'Finish' onthe 'Add and RemoveProjects' screen insteadof 'Click Next andFinish.'

CR339199 3.0 SQL substitutionstatements do notwork in applicationsmigrated from ALDSP2.5 to ALDSP 3.xdataspaces.

Platform All.

Description SQL substitutionstatements created forALDSP 2.5 may nolonger work after theapplication is migratedto an ALDSP 3.0dataspace. This isbecause the originalSQL statements mayhave changed betweenALDSP 2.5 and ALDSP3.0.

Workaround When migratingapplications from ALDSP2.5 to ALDSP 3.0dataspaces, recreateand test any SQLsubstitution statements.

CR351305 3.0 Microsoft VisualStudio displays anerror whenreferencing dataservice librariescontaining functions


that return item().

Platform Microsoft VisualStudio/ADO .NET

Description ADO .NET does notsupport WSDL files thatuse xs:anyType as thereturn value. SinceALDSP convertsfunctions that returnitem() to anyType*,Visual Studio displaysan error similar to thefollowing whenattempting to referencedata services containingthese types offunctions:

Custom tool error:Unable to importWebService/Schema.Unable to importbinding'librarySoapBinding'from namespace'ld:Logical/library_ws'.Unable to importoperation'XqueryNoInputOutput'.The element,XqueryNoInputOutputResponse,from namespace,ld:Logical/library_ws,was imported intwo differentcontexts:(StructMapping,MembersMapping).

Workaround Do not .NET-enabledata service functionsthat return item().

CR349648 3.0 ADO.NET cannothandle a WSDL filethat has multipleSchema type sectionsimporting types in anidentical targetnamespace.

Platform All.

Description ALDSP can generateWSDL files that havemultiple type sectionsreferring to an identicaltarget namespace.Although this is alegitimate WSDL file,


ADO.NET is unable toprocess this type ofWSDL file.The following provides acouple of situations inwhich you mayencounter this ADO.NETlimitation:

• A web servicesmap refers tofunctions in a dataservice with a key,thereby bringing inthe return typeschema and keyschema. Typicallythe return typeschema and keyschema are in thesame namespace.The resultingWSDL file wouldtherefore have atype section foreach schema whilethe namespace forboth type sectionswould be identical.

• A web servicesmap refers to a setof data servicefiles that havereturn types in thesame namespace.This would alsoresult in a WSDLfile that wouldhave a typesection for eachschema while thenamespace forboth type sectionswould be identical.Similarly, there areother scenariosthat can result inthis situation.

Workaround Do one of the following:

• Associate auser-created EDSkey that does nothave the same


namespace as thereturn typenamespace.

• Expose functionsand proceduresthat do not havekeys.

• Limit web servicemaps to a singledata service sothat the resultingWSDL file does notinclude multipletypes with anidentical targetnamespace.

CR349102 3.0 XQSE procedures andfunctions do notsupport element-levelsecurity.

Platform All.

Description Read-only libraryfunctions andnon-read-only libraryprocedures of a dataservice do not supportelement-level security.Element-level anddata-driven securityapply only to read andnavigate functions.

Workaround As an alternative toelement-level security,you can make relevantXQSE functions andprocedures protected orprivate, and write asingle-line XQuerywrapper function forfunctions andprocedures that youneed to make public.

CR348492 3.0 Eclipse-based toolsare installed onSolaris andHP/UX-basedsystems even thoughthey are not officiallysupported on theseplatforms.


Platform Solaris and HP/UX.

Description In silent/console mode,the AquaLogic DataServices Platforminstaller applicationinstalls Eclipse onSolaris andHP/UX-based systemsand creates links to theclient tools.

Workaround Do not use the tools onSolaris andHP/UX-based systems.The ALDSPEclipse-based IDE toolsare supported onMicrosoft Windows andLinux-based platforms.The tools are notsupported on Solarisand HP/UX-basedsystems.

CR347980 3.0 3.2 Missing vertical scrollbar in the DesignView when viewing aschema tree.

Platform All.

Description The vertical scroll bardoes not appear whenviewing a schema in theDesign View if nofunctions exist. This istrue even if the schematree expands beyondthe currently displayedview.

Workaround Adding a functiondisplays the scroll bar.

CR347865 3.0 The tree display inthe Test View maynot display fontscorrectly onLinux-based systems.

Platform Linux.

Description When using AquaLogicData Services Platformon Linux-basedsystems, the defaultLinux font size may


render text in the treedisplay of the Test Viewtoo large, resulting inlabels that are verticallyclipped.

Workaround Decrease the defaultLinux desktopapplication font size to 8point or smaller bychoosing Application >Preferences > Font >Application Font. If youdo not have theApplication menu onyour desktop, consultthe Linuxdocumentation on howto set application fonts.

CR346978 3.0 Unable to specify akey for certain typesof entity dataservices.

Platform All.

Description When attempting tomanually select thefields to specify the keyfor a web-service-baseddata service, theAquaLogic DataServices Platform(Eclipse ALDSPperspective) maydisplay an "Invalid KeySpecified" dialogindicating that thesystem cannot save theschema file.

Workaround To specify the key for adata service, thefollowing conditionsmust be met:

• The key schemaelement must bein the samenamespace as theEDS return typenamespace.

• The key schemaelement and thepath selectorelements must be


in the samenamespace as keyschema elementnamespace.

CR346456 3.0 The ALDSPperspective does notappear in Eclipsefollowing installationof ALDSP.

Platform Eclipse

Description A pre-installed versionof Eclipse configured touse JDK1.4 will not beable to detect an ALDSPinstallation.

Workaround When using apre-installed version ofEclipse, configureEclipse to use JDK150_10 or higher.

CR339726 3.0 Deploying adataspace with namelonger than 64characters is notsupported.

Platform All.

Description Dataspace names arelimited to 64 characters.Attempting to deploy adataspace with a namelonger than 64characters causes a'Name not valid'message to appear inthe ALDSP Console.

Workaround Use dataspace nameswith fewer than 64characters.

CR339900 3.0 An illegal URI errormessage is displayedwhen creating a newlogical data service.

Platform All.

Description When creating a newlogical data service,including preceding orembedded spaces in theschema file or folder


name causes an illegalURI error message toappear, similar to thefollowing:

ERROR:ld:JoinPattern/Logical/CustAddrCredit_1toM_1toM_Inner_Join.ds,line 9,column 125:{err}XQ0046:'ld:JoinPattern/Logical/schemas/CUSTOMER_ADDRESS_CREDIT_INNER_JOIN.xsd':illegal URIUpdatePattern/JoinPattern/LogicalCustAddrCredit_1toM_1toM_Inner_Join.dsline 911884332331353403

Workaround Do not includepreceding or embeddedspaces in schema fileand folder names.

CR352843 3.0 AquaLogic DataServices Platform 3.0requires twoWorkshop forWebLogic 9.2 MP2patches to be appliedfollowing installation.

Platform Workshop for WebLogic9.2 MP2

Description Two required Workshopfor WebLogic 9.2 MP2patches are notautomatically applied aspart of the AquaLogicData Services Platform3.0 installation process.

This issue doesnot apply toALDSP 3.2.

Workaround After installing ALDSP3.0, manually apply thefollowing Workshop forWebLogic 9.2 MP2patches using thesmartupdate tool:

• RQSU• PF7M

The patches are inthe 'downloaded'state after ALDSP


3.0 installation.You must haveWorkshop forWebLogic 9.2 MP2installed to applythe patches.

CR343891 3.0 Asynchronousoperations do notpropagate thetransaction context.

Platform All.

Description Asynchronous webservices and Javacontrols do notpropagate thetransaction context,regardless of thetransactionrequirements or settings(such asReadTransaction).Asynchronousoperations are likewiseunable to start newtransactions.

Workaround None.

CR352226 3.0 3.2 When performingcertain tasks afteradding an externalfunction, an errormessage may appear.

Platform All.

Description After adding an externalfunction, one of thefollowing errors mayappear:

• Clicking the Sourcetab may cause a"Resource is out ofsync with the filesystem" error toappear.

• Clicking the Sourcetab and modifyingthe code maycause the followingupdate conflicterror message toappear: "The file


has been changedon the file system.Do you want tooverwrite thechanges?"

• Right-clicking todelete an existingfunction from theOverview pagemay cause thefollowingrefactoringmessage toappear: 'The file"..." is out of syncwith theunderlying filesystem."

Workaround Click Refresh in theProject Explorer.Alternatively, you canclick "Yes" to overwritethe file.

CR338127 3.0 3.2 Unable to displaydata lineage graphusing Solaris-basedweb browsers.

Platform Firefox web browser onSolaris.

Description The Solaris version ofthe Firefox web browserdoes not include anative SVG viewer orplug-in. Therefore, youcannot display agraphical view of thedata lineage.

Workaround Display the data lineageusing the tabular view.

CR338237 3.0 3.2 Unable to displaydata lineage graphusing HP-UX-basedweb browsers.

Platform Firefox web browser onHP-UX.

Description The HP-UX version ofthe Firefox web browserdoes not include anative SVG viewer or


plug-in. Therefore, youcannot display agraphical view of thedata lineage.

Workaround Display the data lineageusing the tabular view.

CR352805 3.0 Unable to deploy Javaprojects upgradedusing ALDSP 3.0.

Platform All.

Description When upgrading Javaprojects (required by adata service) usingALDSP 3.0, the upgradeprocess adds Java 6.0facets that makes theJava projectsnon-deployable in aWebLogic Server 9.2MP2 environment.

Workaround Do the following:

1. In the\.settings\org.eclipse.wst.common.project.facet.core.xmlfile of theupgraded Javaproject, changethe line <installedfacet='jst.java'version='6.0'/> to<installedfacet='jst.java'version='5.0'/>.

2. In the\.settings\org.eclipse.jdt.core.prefsfile of theupgraded Javaproject, changethe value of thefollowingproperties from1.6 to 1.5:

• org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5• org.eclipse.jdt.core.compiler.compliance=1.5• org.eclipse.jdt.core.compiler.source=1.5

CR343934 3.0 3.2 Starting to serviceadministrationrequests on adeployed dataspacethat is in the activestate generates an


error.

Platform All.

Description When a deployeddataspace is already inthe active state, clickingto start servicingadministration requestscauses a deploymentexception to be loggedand displays thefollowing message:

EAR activation fordataspace '<name>'failed. Cause(s):-[Deployer:149156]Illegal state foroperation start:'STATE_ACTIVE'

Workaround Do not start servicingadministration requestson a deployeddataspace that is in theactive state. Instead, dothe following:

1. Stop thedataspace.

2. Click to startservicingadministrationrequests

CR352634 3.0 Certain data servicefunctions cannot bepublished as storedprocedures.

Platform All.

Description The following types ofdata service functionscannot be published asstored procedures:

• Functions withside-effects(procedures)

• Functions with asimple return type

Workaround None.

CR333331 3.0 SQL query generates


an "Extra charactersat the end of adatetime or interval"error.

Platform Informix, all UNIX(using the Informix XAJDBC driver).

Description When using the nativeInformix XA driver,certain SQL queries maygenerate an "Errorexecuting SQL query:Extra characters at theend of a datetime orinterval" error, asshown in the followingexample:

Caused by:com.bea.ld.wrappers.rdb.exceptions.RDBWrapperException:[ad-hoc],line 10, column 1:{bea-err}RDBW0004:[ifrtl20ds]:[SELECT DISTINCTt1.cc_type AS c1FROMrtlall_20:informix.credit_cardt1,rtlall_20:informix.addresst2WHERE((t1.customer_id =t2.customer_id)AND (t1.exp_date>= {ts '2007-01-0100:00:00'}) AND(t2.city = 'SanJose'))]:Error executingSQL query: Extracharacters at theend of a datetimeor interval.

atcom.bea.ld.wrappers.rdb.exceptions.RDBWrapperException.create(RDBWrapperException.java:81)

Workaround 3.0 Use the BEA InformixJDBC driver.

CR344349 A query produces aninvalid XML characterin the resultingdocument.

Platform DB2 (using the nativeDB2 JDBC driver).

Description When using the nativeDB2 driver, a querymay produce an invalidXML character


(Unicode: 0x0) in theresulting document.

Workaround Use the BEA DB2 JDBCdriver.

CR345306 3.0 SOAP 1.2 encodingnot supported forALDSP native webservices.

Platform All.

Description ALDSP supports SOAP1.1 and 1.2, and usesthe version todetermine the type ofSOAP binding to createduring WSDLgeneration. The defaultis 1.1. SOAP 1.2encoding is notsupported. Encoding isan optional featuredefined by the SOAP 1.2specification.

Workaround Create JAX-RPChandlers to handleencoded messages.

CR355266 3.0 ALDSP 2.5applications usingJPD calls fail to workwith ALDSP 3.0.

Platform All.

Description ALDSP 3.0 does notsupport applicationsmigrated from ALDSP2.5 to ALDSP 3.0 thatuse JPD call outs inupdate overwrites.

Workaround This feature is notavailable in ALDSP 3.0.Future versions ofALDSP will support thisfeature.

CR294861 3.0 An exception occursif a timestamp withtime zone is fetchedbefore LONG_RAW.

Platform All (using the OracleJDBC driver).

Description When using an Oracle


database, if atimestamp with a timezone is fetched before aLONG_RAW a "...Stream has alreadybeen closed" exceptionoccurs. This isconsistent with the wayOracle handlesLONG_RAW fetchedbefore blob and clob.

Workaround Reverse the fetch orderof timestamp with timezone and LONG_RAWwhen using Oracle.

CR286359 3.0 When importing orsynchronizingmetadata with anOracle database, thenative width of floatelements may beincorrectlycalculated.

Platform All (using the BEAOracle JDBC driver).

Description When importing orsynchronizing metadatawith an Oracle datasource, the width offloat elements may berendered incorrectly (15instead of 6 or 9). Thisproblem has beenobserved when usingthe WebLogic JDBCOracle driver (version3.0.5.0).

Workaround Metadatasynchronization usingOracle's native JDBCdriver(Oracle.jdbc.driver.OracleDriver)did not exhibit thisproblem. Therefore, ifthe width of native floatelements is an issue usethe Oracle JDBC driver.

CR292257 3.0 Duplicate names areallowed whenmapping storedprocedures to data


services duringmetadata import.

Platform All.

Description The SQL name mappinguser interface may allowmore than one storedprocedure with thesame name to beconfigured under thesame schema. However,if more than one storedprocedure with thesame name isconfigured, the user willsee unexpected resultsin the JDBC metadataAPI and on execution ofthe procedures viaJDBC.

Workaround In the Publish DataService Functions forSQL Use wizard,manually rename storedprocedures so thatthere are no duplicatenames.

CR291781 3.0 Excel Add-in willinitially attempt toreuse HTTP basicauthentication logincredentials for allWeb services hostedon the same port.

Platform All.

Description In cases where multipleWeb services areconfigured in a singleExcel worksheet, andthese Web services arehosted by the samehost machine and portnumber, the ExcelAdd-In will initiallyattempt to reuse thepreviously acceptedusername/password forthese services.If theusername/password isnot valid for a particularWeb service, a login


dialog will be displayed.Subsequent Web serviceinvocations during thesame Excel session willuse the correct logininformation for eachservice.

Workaround No action has to betaken, unless it is notdeemed acceptable thatan attempt is made toauthenticate a webservice call initially withincorrect credentials.In such cases Webservices requiringdifferent credentialsshould be grouped indifferent servers ORWeb services requiringdifferent credentialshosted on the samehost/port should beused on separate Excelworksheets.

CR290239 3.0 Several underlyingWSDL Elementdefinition attributesand Attributedefinition attributesare not currentlysupported in theAquaLogic DataServices PlatformExcel Add-in.

Platform All.

Description The following Elementdefinition attributes arecurrently unsupported:

• substitutionGroup• default• fixed• form• abstract• block• final

The followingAttribute definitionattributes arecurrentlyunsupported:


• default• fixed• form• abstract• block• final

Workaround Any WSDL containingthe definition attributeslisted above may notfunction as expected. Ifproblems areencountered, removethese definitionattributes from yourWSDL.

CR284834 3.0 You need tomaximizeperformance whenaccessing data in anInformix databasethrough ALDSP.

Platform All using Informixdatabase systems.

Description The WebLogic InformixJDBC driver is lessperformant than thenative Informix JDBCdriver when accessingdata through AquaLogicData Services Platform.

Workaround No workaroundnecessary, but for bestperformance withInformix data use thenative JDBC driver.

CR279492 3.0 When using a dataservice based on aWeb service atruntime, a validationerror may occur ifform and/orelementFormDefaultdo not match. Thishappens becauseredefinition of the'Form' attribute is notsupported.

Platform All.

Description At design time, if:


• TheelementFormDefaultattribute in theprimary schemadoes not matchtheelementFormDefaultattribute in animported orincluded schema,or

• if the formattribute of anelement does notmatch theelementFormDefaultattribute in theprimary schemathen at runtimevalidation errorswill occur whenaccessing Webservice-based dataservices.

Workaround TheelementFormDefault inthe primary schema andany imported orincluded schemasshould match prior tocompilation. Also, theform attribute of theelement should matchthe elementFormDefaultin the primary schema.

CR288384 3.0 The Data Lineagefeature in AquaLogicData ServicesPlatformadministrationconsole requires theX11 graphicalenvironment in Linuxand UNIXenvironments.

Platform UNIX and Linux

Description The following error:

java.lang.NoClassDefFoundError:sun/awt/X11GraphicsEnvironment


may occur whileaccessing the DataLineage feature ofAquaLogic DataServices PlatformAdministration Console.The circumstances arisewhen the AdministrationServer hostingAquaLogic DataServices PlatformAdministration Consoleis running on a Linux orUNIX host with one ofthe following conditions(not an exhaustive list):

• A headlessenvironment is inuse — forexample, withoutmonitor and/or Xserver.

• With a monitor,but the userrunning theadministrationserver is not thesame userlogged-in from themonitor, andtherefore, does nothave displaypermissions to thedefault display(:0.0).

Workaround To resolve this issue,set the followingheadless property totrue:

-Djava.awt.headless=true

The property can befound in the WeblogicServer startup script(startWeblogic.sh) inthe section of the scriptwhere the server isstarted.

CR283262 3.0 Unable to add criteria


to SQL when usingMS Excel withEasySoft or OpenLink.

Platform All.

Description In Microsoft Query,adding a query criteriausing the Add Criteriawindow, (Criteria ?AddCriteria) throws an errormessage whenaccessing AquaLogicData Services Platformdata sources.

Workaround To work around thisissue:

1. In the MicrosoftQuery window,select the Recordsmenu option. Ifthe AutomaticQuery option ischecked, thenclear this option.

2. Click View >Criteria. This willadd a Criteriawindow to thequery window intowhich you canenter appropriatecriteria.

3. To execute querywith the criteriaadded, clickRecords > QueryNow.

CR264597 3.0 String comparisonoperations involvingMS-SQL (and Sybase)may return incorrectresults when thecomparison operationis computed byMS-SQL.

Platform All.

Description See CR264597 Details

Workaround See CR264597 Details

CR204243 3.0 When casting


xs:decimal from anxs:integer or xs:long,resulting values maynot be preciselycorrect.

Platform All.

Description As above.

Workaround To avoid the possibilityof an incorrect resultuse a string literalinstead of an xs:integerliteral. For exampleinstead of:

xs:decimal(9223372036854775807)

use:

xs:decimal("9223372036854775807")

CR260587 3.0 An exception duringan SDO updateoperation can occur ifthe order of elementsin the client diffgramis changed and theValidate option isactive.

Platform All, using ADO.NETclients.

Description Sometimes the order ofelements in a diffgramchanges, potentiallyleading to datagraphvalidation failure.

Workaround If possible, turn offvalidation for theoperation.

CR265950 End-point namechanges do not takeeffect for operationsin document styleWeb services.

Platform All.


Description Document style Webservices use input (callparameter) types todetermine the Webservice operation beinginvoked. The operationname is not included inthe SOAP request. Forthis reason, overwritingthe operation name aspart of an end pointchange does not workfor document style Webservices.

Workaround None.

CR256214 3.0 Some DBMS systemsmay not properlyhandle "pusheddown" constants.

Platform Database platforms forwhich only genericsupport is provided.

Description SQL statements sent tobase (not specificallysupported) databaseplatforms use a "bestguess" as to the syntaxfor string literal. Suchformulations may notwork in all cases. Anexample of this isMySQL which requiresevery backslash

[aldsp2: \ ]

to be escaped withanother backslash.Such cases are nothandled by SQLgeneration code andmight result in invalidSQL being generated.

Workaround There are two possibleworkarounds for thisproblem:

• Convert constantsto parameters byusing an external


variable instead ofa constant. Forexample:

where$customer_id eqfn-bea:fence("CUSTOMER001")

• Properly escapethe XQuery stringliteral according tothe rules of theunderlyingdatabase.

CR248407 3.0 Metadata importwizard fails to detectin/out parameters.

Platform All.

Description In some situationsassociated with MSSQLand Sybase storedprocedures, a resultsetis returned which is notautomatically detected.

Workaround First, manually build aschema that is mappedto the output of theresultset. Then, whenimporting metadata usethe wizard, add aROWSET and link it tothe previously createdschema.

CR242938 3.0 Multi-dimension soaparrays are notsupported in RPCmode.

Platform All.

Description The Web serviceswrapper provided byAquaLogic DataServices Platform onlysupportssingle-dimension arraysin RPC style Webservices.

Workaround None.

CR224815 3.0 The initial invocation


of a Web service froman application servertypically takes moretime than subsequentcalls. If the timeoutvalue is less than thetime required for thefirst call, thealternate expression(typically a timeouterror) will beevaluated.

Platform All.

Description There is "startupoverhead" the first timethat a web service isinvoked. The overheadcan exceed the timeoutthreshold, leading to thespecified timeout error.

Workaround When setting timeouton expressions thathave a Web serviceinvocation, set thetimeout value to begreater than themeasured amount oftime required for thefirst invocation.

CR239369 3.0 XQueries maygenerate invalid SQLfor databases notsupporting UPPERand LOWER (SQL-92).Also, empty inputhandling for basedatabases (databasesnot specificallysupport) as well asOracle deviates fromthe XQueryspecification whenUPPER(null) orLOWER(null) ispushed down to thedatabase level.

Platform All platforms runningbase databases andOracle databases.

Description There are two aspectsto this problem:


• XQueriescontainingupper-case() orlower-case()functions arepushed down fordatabaseprocessing asUPPER andLOWER. Somedatabases may notsupport theseSQL-92 keywords,however. In suchcases thegenerated SQL willbe invalid andupon execution willfail.

• Similarly, inputhandling by basedatabases (as wellas Oracledatabases) maynot match theXQueryspecification. Thereason for this isthat the XQueryspecificationrequires thatfunctions return anempty string ifinput is an emptysequence.However, whenthese functions arepushed down, theyreturn an emptysequence instead.This happensbecauseLOWER(NULL) isNULL in SQL.

Workaround Use the fn-bea:Fence()function to preventpushdown ofupper-case() orlower-case() functionsto the database.Example:


lower-case(fn-bea:fence(...))

CR207637 3.0 An exception appearsfor XQuery functionsaccessing metadataderived fromMicrosoft SQL Serverstored procedurescontainingxs:decimal.

Platforms All.

Description When importing astored procedure fromMicrosoft SQL Server,the BEA JDBC driverincorrectly maps SQLdecimal type to schemainteger (xs:int) type.

Workaround During stored procedureimport, change the datatype from xs:int toxs:decimal.Alternatively, you canchange the importeddata service's metadatato specify the schematype for the affectedcolumn to bexs:decimal.

CR203394 3.0 ROWTYPE inputcursor is notsupported whencreating a dataservice from a storedprocedure.

Platform All.

Description Stored procedure INand INOUT cursorscontaining ROWIDs arenot currently supportedfor metadata import.

Workaround Avoid importingmetadata on storedprocedures whichrequired use of IN orINOUT ROWIDparameters.

CR214585 3.0 Erroneous results


may occur whenusing fn:matches()with a regularexpression containinga caret (^).

Platform All.

Description The matchbeginning-of-lineoperator (^) in regularexpressions produceserroneous results whenused with fn:matches().

Workaround Do not usefn:matches() with aregular expressioncontaining a caret (^).

CR215251 WLS 9.0 Identifiers within twocharacters of themaximum lengthallowed by the DBMSmay result in anerror.

Platform All platforms runningSybase (and possiblyother) databases.

Description Some DBMS systemsplace limits on thelength of identifiers (30in the case of Sybase).AquaLogic DataServices Platform placessingle quotes aroundqueries being pushed tothe database, effectivelyreducing the maximumidentifier length by twocharacters (28 in thecase of Sybase).

Workaround Possible options includerenaming the table orcreating a view with ashorter name.

CR226019 3.0 Access controlpolicies associatedwith a data servicefunction maydisappear if thefunction's number ofparameters ischanged.


Platform All.

Description A data service function'ssignature is its QNameand the number ofparameters (arity) ofthe function. If you setsecurity policies on afunction and thenchange the number ofparameters to thefunction, the function istreated as new and anypreviously set policieswill no longer be ineffect.

Workaround If a function's arity ischanged, reapplysecurity policies to thatfunction.

CR213916 3.0 BEA Informix JDBCdriver does notreturn nullabilityinformation.

Platform All platforms runningInformix.

Description The BEA Informix driverdoes not returninformation about tablecolumn nullability (thatis, it is marked asunknown). Duringmetadata import theminOccurs of theelements correspondingto the columns in thegenerated XML schemasis set to 0.

Workaround Modify the importedmetadata files bychanging the minoccursvalue for the nullablecolumns from 0 to 1.

CR214983,CR211701, CR201821

3.0 MSSQL VARIANTdatatype has onlylimited support.

Platform All.

Description There are twolimitations with thisMSSQL VARIANT data


type (sql_variant):

• For SQL_VARIANTdata type updatewill fail.

• You cannot read anull value for theSQL_VARIANTdata type.

Workaround None available.

CR221015, CR319972 3.0 During metadataimport the BEASybase JDBC drivermay not display alltables to which userhas authorizedaccess.

Platform All platforms accessingSybase through the BEASybase JDBC driver.

Description During metadata importthe BEA Sybase JDBCdriver may not show alltables which have beengranted access to theuser.

Workaround This is a BEA Sybasedriver limitation. For theimport purpose, you canchange to dbo user tosee the full complementof available tables.

CR202963 3.0 When using BEAOracle JDBC driverwith a TIMESTAMPvalues, storedprocedures aretruncated.

Platform All platforms runningOracle with the BEAOracle JDBC driver.

Description When using the BEA'sOracle JDBC driver, if astored procedurereturns a TIMESTAMPvalue then the valuegets truncated at themilliseconds level. Forexample, if the value


was:

1997-01-3109:26:50.124

then the storedprocedure will return a

1997-01-31 09:26:50.0

value.

Workaround Use the Oracle JDBCdriver stored proceduresthat returningTIMESTAMP values.

CR223429, CR228802 3.0 Sybase JDBC driverdoes not support agetBlob() call.

Platform All platforms runningSybase with the SybaseJDBC driver.

Description The AquaLogic DataServices Platform cacheconfiguration does notwork if using SybaseJDBC driver because theconfigurationimplementation uses agetBlob( ) call on theJDBC driver. TheSybase JDBC driverdoes not supportgetBlob( ).

Workaround Use the BEA JDBCdriver for Sybasedatabases when utilizingSybase as theAquaLogic DataServices Platform cachedata source.

CR214730 3.0 SQL Server JDBCdriver incorrectlyrenders the tinyintmaximum value.

Platform All platforms runningSQL Server with the


SQL Server JDBC driver.

Description The SQL Server tinyintmaximum value of 255gets interpreted as -1by the Microsoft SQLServer JDBC driver.

Workaround Use the BEA JDBCdriver for SQL Server.

CR223486,CR226239, CR226171

3.0 The Informix JDBCdriver does notsupport standardJDBC syntax forspecifyingTIMESTAMP values.

Platform All platforms runningInformix with theInformix JDBC driver.

Description The Informix nativedriver does not supportstandard JDBC syntaxfor specifyingTIMESTAMP values. Forexample:

1979-03-01 00:00:00.0

is not supported.

Workaround Use the BEA JDBCdriver for Informix.

CR199675 3.0 The BEA JDBC driverfor Oracle does notsupport UROWIDcolumn type for dataretrieval.

Platform All platforms runningOracle with the BEAJDBC driver.

Description When using BEA JDBCdriver for Oracle,retrieving UROWIDreturns an error,identified by thefollowing message:

[aldsp2:BEA][aldsp2:OracleJDBCDriver]Internalerror: Net8


protocol error

Workaround Use the Oracle JDBCdriver if your datacontains UROWIDcolumn type.

CR212515 3.0 The Oracle storedprocedure returningPL/SQL RECORD,BOOLEAN, or tablewith non-scalarelement types is notsupported.

Platform All platforms usingOracle.

Description Oracle stored procedurelimitations are detailedin the followingcurrently-availabledocument:http://www.stanford.edu/dept/itss/docs/oracle/9i/java.920/a96654/ref.htm#1007714

Workaround None available

CR202041 3.0 Metadata for SQLServer storedprocedures returningCURSOR outputcannot be created.

Platform All platforms using SQLServer.

Description When importingmetadata from SQLServer, storedprocedures that returnCURSOR output are notsupported.

Workaround Modify the importeddata service file toidentify the correct datatype for the cursor.

CR227440 3.0 Metadata for DB2stored proceduresreturning CLOB datacannot be created.

Platform All platforms using DB2.

Description When importingmetadata from DB2,stored procedures


http://www.stanford.edu/dept/itss/docs/oracle/9i/java.920/a96654/ref.htm#1007714

returning CLOB data arenot supported.

Workaround None available.

CR265965 3.0 Updating or deletingOracle'sCHAR/NCHAR withtrailing blanks failedwith an Optimisticlocking failuremessage using OracleJDBC driver.

Platform All using Oracle'snon-XA JDBC driver.

Description With Oracle's non-XAJDBC driver, CHAR andNCHAR columns canonly be updated if thenumber of characters is1024 or less.

Workaround Where possible useBEA's Oracle JDBCdriver (Type 4).

CR202962 3.0 Oracle storedprocedurescontaining CHAR orNCHAR as input maycause a Server error.

Platform All.

Description If you have Oraclestored procedures thatuse an INOUTparameter, you may getan error when you run astored procedure usingAquaLogic DataServices Platform. Theerror is similar to:

java.lang.RuntimeException:ORA-01460:unimplemented orunreasonableconversion requestedORA-06512: at"WIRELESS.SP_CHAR",line 17

Workaround Modify your storedprocedure call by


reducing the size of theINOUT parameter usingTRIM. Seealdsp2:Sample coderelated to CR202962, inaldsp2:Listing 1.

Supplemental Release Note Documentation

This section contains code and other additional information related to previously described release notes.

CR264597 Details

Summary

String comparison operations involving MSSQL (and Sybase) may return incorrect results when thecomparison operation is computed by MSSQL.

Description

Depending on the database and server configuration, MSSQL Server may use case-insensitive collationfor string comparison operations (this is the default configuration). This is in contrast to XQuery stringcomparison operations, which are case-sensitive.

When generating SQL, the AquaLogic Data Services Platform currently does not take database stringcollation into account. This can lead to different results being produced by expressions that are "pusheddown" to an MSSQL database, as compared to the results from their evaluation by the XQuery engine.

The following types of expressions are affected:

• string comparison operations• string functions: fn:contains( ), starts-with( ), ends-with()• order by clauses• group by clauses.

For example, consider the following two-row, two-column table based on:

CUSTOMER(ID, FIRST_NAME)

ID FIRST_NAME

1 John

2 john

The following XQuery might return different results depending whether it is evaluated by the database ornot.


for $c in CUSTOMER()where $c/FIRST_NAME eq "john"return $c/ID

According to XQuery semantics, this query should return:

<ID>2</ID>

as only the second record matches the selection criteria.

However, when the AquaLogic Data Services Platform pushes the query to the underlying MSSQLdatabase, the following SQL is generated:

SELECT t1."C_ID" AS c1FROM "CUSTOMER" t1WHERE t1."FIRST_NAME" = "john"

This might result in both records being returned by the MSSQL database (with case-insensitive stringcollation set):

<ID>1</ID><ID>2</ID>

Workaround

There are several workarounds to conforming with XQuery semantics for string comparisons whenpushing computations down to MSSQL.

Option 1

Consider changing the collation setting that the database uses for string comparisons. See "SQL ServerCollation Fundamentals" document located as of this writing at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar

Collation can change on a server, database or column level basis.

Option 2

Use the fn-bea:fence( ) function to block pushdown. In the above example, this would be rendered as:


http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da_1pwz.asp

for $c in CUSTOMER()where fn-bea:fence(data($c/FIRST_NAME)) eq "john"return $c/ID

Notice, however, that this approach may negatively impact performance since the AquaLogic DataServices Platform engine now must fetch and process the entire table.

To optimize performance, consider replicating the comparison operation in the query, thus allowing onecopy to be evaluated by the database while keeping the second copy on the AquaLogic Data ServicesPlatform engine. The following query illustrates such an approach:

for $c in CUSTOMER()where $c/FIRST_NAME eq "john"where fn-bea:fence(data($c/FIRST_NAME)) eq "john"return $c/ID

This approach limits the number of results that the XQuery engine must process but still applies thesecond selection in order to obtain the correct XQuery semantics.

CR202962 Listing 1

Here is the sample code for CR202962:

** CREATE OR REPLACE PROCEDURE WIRELESS.SP_CHAR(P_CHAR_IN IN CHAR,P_CHAR_OUT OUT CHAR,P_CHAR_INOUT IN OUT CHAR,P_ID_OUT OUT VARCHAR2 )ISTEMP VARCHAR2(10);BEGINSELECT C_ID INTO P_ID_OUTFROM WIRELESS.ALL_DATATYPESWHERE C_CHAR = P_CHAR_IN;

SELECT C_CHAR INTO P_CHAR_OUTFROM WIRELESS.ALL_DATATYPESWHERE C_ID = '2';

SELECT C_ID INTO TEMPFROM WIRELESS.ALL_DATATYPESWHERE C_CHAR = P_CHAR_INOUT;

SELECT 'WORK' INTO P_CHAR_INOUTFROM WIRELESS.ALL_DATATYPESWHERE C_ID = TEMP;END;/to adjust the size of PCHAR_INOUT using TRIM (see highlighted code)CREATE OR REPLACE PROCEDURE WIRELESS.SP_CHAR(P_CHAR_IN IN CHAR,P_CHAR_OUT OUT CHAR,P_CHAR_INOUT IN OUT CHAR,P_ID_OUT OUT VARCHAR2 )ISTEMP VARCHAR2(10);\*ACHAR CHAR(500);

BEGINACHAR := trim(P_CHAR_INOUT);\*SELECT C_ID INTO P_ID_OUT


FROM WIRELESS.ALL_DATATYPESWHERE C_CHAR = P_CHAR_IN;

SELECT C_CHAR INTO P_CHAR_OUTFROM WIRELESS.ALL_DATATYPESWHERE C_ID = '2';

SELECT C_ID INTO TEMPFROM WIRELESS.ALL_DATATYPES\*WHERE C_CHAR = ACHAR; // used to fail here\*SELECT 'WORK' INTO P_CHAR_INOUTFROM WIRELESS.ALL_DATATYPESWHERE C_ID = TEMP;

END;/

Version: 3.0 / 3.2 / 3.01

Document Date: January 2008

Revision: April 2008

© BEA Systems


http://edocs.bea.com/copyright.html

ALDSP 3.0/3.2/3.01 Release Notes - Oracle...ALDSP_3.0 / 3.2 / 3.01 Release Notes This page last...

Documents

Transcript of ALDSP 3.0/3.2/3.01 Release Notes - Oracle...ALDSP_3.0 / 3.2 / 3.01 Release Notes This page last...