Data Source ID must be of type IDataSource

I'm trying to do a report with a chart in it (I don't know if the fact that it has a chart makes any difference), and I'm getting the following error where the chart should appear:
The DataSourceID of the ReportDataSource 'DataSetD' of the ReportViewer 'ReportViewer1' must be the ID of a control of type IDataSource. A control with ID 'MyReportDataSetD' could not be found.
I have the following .aspx code for my report/chart:
<rsweb:ReportViewer ID="ReportViewer1" runat="server">
<LocalReport ReportEmbeddedResource="MyProject.Report2.rdlc" ReportPath="Report2.rdlc">
<DataSources>
<rsweb:ReportDataSource DataSourceId="MyReportDataSetD" Name="DataSetD" />
</DataSources>
</LocalReport>
</rsweb:ReportViewer>
When I created my chart, I specified the Data source as MyReportDataSet and the Dataset as DataSetD. They are both showing up under Data Sources and Datasets, respectively, in my Report Data window.
I did not add any code behind, and I do not know if I need to and if so, what I need to add. After a long search on the internet, I have not been able to find enough complete information on charts to easily be able to do charts in Visual Studio 2013
with SQL Server 2012, so I have been trying to piece this together little by little from information from various articles on the internet and taking help from MSDN forums.
Any help would be great.
Thanks.
When I created my chart, I specified MyReportDataSetD as my DataSource (which now appears under DataSources in my Report Data window), and I specified DataSetD as my Dataset (which now appears
under Datasets in my Report Data window)
DataSetD was selected from the database datasource MyReportDataSetD, so Data
When I created my chart, I specified MyReportDataSetD as my DataSource (which now appears under DataSources in my Report Data window), and I specified DataSetD as my Dataset (which now appears
under Datasets in my Report Data window)
DataSetD was selected from the database datasource MyReportDataSetD, so Data
When I created my chart, I specified MyReportDataSetD as my DataSource (which now appears under DataSources in my Report Data window), and I specified DataSetD as my Dataset (which now appears
under Datasets in my Report Data window)
DataSetD was selected from the database datasource MyReportDataSetD, so Data
When I created my chart, I specified MyReportDataSetD as my DataSource (which now appears under DataSources in my Report Data window), and I specified DataSetD as my Dataset (which now appears
under Datasets in my Report Data window)
DataSetD was selected from the database datasource MyReportDataSetD, so Data

Hello,
Based on the error message, the issue is related to the report data source.
In your post, the Data source name is MyReportDataSet
and the Dataset is DataSetD. However the .aspx code is as following:
<rsweb:ReportDataSource DataSourceId="MyReportDataSetD" Name="DataSetD" />
Please verify the data source name and also note it is case sensitive.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Similar Messages

DSP Web Service Data Source runtime error "Invalid xsi:type qname"

I have created a DSP data service that uses a web service as a data source.
The web service wraps an Oracle PL/SQL package and works when tested independantly of the DSP data service.
When I test the DSP data service using the weblogic workshop test view I get the error below:
weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
(The full stack trace and the WSDL imported into DSP are at the bottom of this posting)
I am new to DSP but I have created data services from the DSP tutorials succesfully before.
This is the first data service I have tried to create which is not from a DSP tutorial.
I dont really understand the error message.
It appears to me that type EmpRecUser is being prefixed by the wrong name space. In the WSDL the namespace is 'tns:' in the error message the namespace is: 'ns0'.
<element name="getEmpResponseElement">
<complexType>
<sequence>
<element name="result" type="tns:EmpRecUser" nillable="true"/>
</sequence>
</complexType>
</element>
I created the web service in Oracle J Developer from the tutorial URL below.
http://www.oracle.com/technology/obe/obe1013jdev/10131/wsfromplsqlpackage/devwsfrom%20plsql.htm#p
weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:169)
     at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
     at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
     at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
     at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
Caused by: weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ValidationException: null
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ExceptionCollection.add(XMLValidatorForXMLBeans.java:340)
     at org.apache.xmlbeans.impl.validator.Validator.emitError(Validator.java:175)
     at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:207)
     at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:193)
     at org.apache.xmlbeans.impl.validator.Validator.beginEvent(Validator.java:458)
     at org.apache.xmlbeans.impl.validator.Validator.nextEvent(Validator.java:246)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processBeginElementToken(XMLValidatorForXMLBeans.java:1205)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processToken(XMLValidatorForXMLBeans.java:1322)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processTokensOnHold(XMLValidatorForXMLBeans.java:1349)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.gotBeginElementToken(XMLValidatorForXMLBeans.java:772)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:100)
     at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
     at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
     at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
     at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
     at com.bea.ld.server.QueryInvocation.getResult(QueryInvocation.java:461)
<definitions
name="EmpWebService"
targetNamespace="http://hr/EmpWebService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://hr/EmpWebService.wsdl"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://hr/EmpWebService.wsdl/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hr/EmpWebService.wsdl/types/"
elementFormDefault="qualified" xmlns:tns="http://hr/EmpWebService.wsdl/types/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<element name="getEmpElement">
<complexType>
<sequence>
<element name="empNo" type="decimal" nillable="true"/>
</sequence>
</complexType>
</element>
<element name="getEmpResponseElement">
<complexType>
<sequence>
<element name="result" type="tns:EmpRecUser" nillable="true"/>
</sequence>
</complexType>
</element>
<complexType name="EmpRecUser">
<complexContent>
<extension base="tns:EmpRecBase">
<sequence>
<element name="departmentId" type="decimal" nillable="true"/>
<element name="managerId" type="decimal" nillable="true"/>
<element name="hireDate" type="dateTime" nillable="true"/>
<element name="jobId" type="string" nillable="true"/>
<element name="employeeId" type="decimal" nillable="true"/>
<element name="commissionPct" type="decimal" nillable="true"/>
<element name="salary" type="decimal" nillable="true"/>
<element name="lastName" type="string" nillable="true"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="EmpRecBase">
<sequence/>
</complexType>
</schema>
</types>
<message name="EmpWebService_getEmp">
<part name="parameters" element="tns0:getEmpElement"/>
</message>
<message name="EmpWebService_getEmpResponse">
<part name="parameters" element="tns0:getEmpResponseElement"/>
</message>
<portType name="EmpWebService">
<operation name="getEmp">
<input message="tns:EmpWebService_getEmp"/>
<output message="tns:EmpWebService_getEmpResponse"/>
</operation>
</portType>
<binding name="EmpWebServiceSoapHttp" type="tns:EmpWebService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getEmp">
<soap:operation soapAction="http://hr/EmpWebService.wsdl/getEmp"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="EmpWebService">
<port name="EmpWebServiceSoapHttpPort" binding="tns:EmpWebServiceSoapHttp">
<soap:address location="http://localhost:8888/PL_SQL_WS-GetEmployee-context-root/EmpWebServiceSoapHttpPort"/>
</port>
</service>
</definitions>

DSP validates the results from webservices. Whatever you tested the webservice with outside of DSP, probably does not.
Can you capture the output of the webservice and attach it as well? You can capture the webservice response by running the wls server with the command-line property -Dweblogic.webservice.verbose=true
Can you also open a case with customer support for this? I will not likely have much time to look at it.
- Mike
btw - the namespace prefixes are just place-holders that are defined with xmlns:prefix="some-uri". It is the namespace uri's that must be equivalent. If, in one case you have the definition xmlns:tns="myUri" and in another case xmlns:ns0="myUri" - then tns:EmpRecUser is equivalent to ns0:EmpRecUser.
Perhaps in the webservice result there is no definition, or an incorrect definition for the namespace prefix ns0 - that would explain the complaint about the QName ns0:EmpRecUser. According to the wsdl, there should be a definition for ns0 as :
xmlns:ns0="http://hr/EmpWebService.wsdl"
in the webservice response.

Using sql bulk copy throwing exception -The given value of type String from the data source cannot be converted to type int of the specified target column

Hi All,
I am reading notepads files and inserting data in sql tables from the notepad-
while performing sql bulk copy on this line it throws exception - "bulkcopy.WriteToServer(dt); -"data type related(mentioned in subject )".
Please go through my logic and tell me what to change to avoid this error -
public void Main()
Dts.TaskResult = (int)ScriptResults.Success;
string[] filePaths = Directory.GetFiles(@"C:\Users\jainruc\Desktop\Sudhanshu\master_db\Archive\test\content_insert\");
for (int k = 0; k < filePaths.Length; k++)
string[] lines = System.IO.File.ReadAllLines(filePaths[k]);
//table name needs to extract after = sign
string[] pathArr = filePaths[0].Split('\\');
string tablename = pathArr[9].Split('.')[0];
DataTable dt = new DataTable(tablename);
|
string[] arrColumns = lines[1].Split(new char[] { '|' });
foreach (string col in arrColumns)
dt.Columns.Add(col);
for (int i = 2; i < lines.Length; i++)
string[] columnsvals = lines[i].Split(new char[] { '|' });
DataRow dr = dt.NewRow();
for (int j = 0; j < columnsvals.Length; j++)
//Console.Write(columnsvals[j]);
if (string.IsNullOrEmpty(columnsvals[j]))
dr[j] = DBNull.Value;
else
dr[j] = columnsvals[j];
dt.Rows.Add(dr);
SqlConnection conn = new SqlConnection();
conn.ConnectionString = "Data Source=UI3DATS009X;" + "Initial Catalog=BHI_CSP_DB;" + "User Id=sa;" + "Password=3pp$erv1ce$4";
conn.Open();
SqlBulkCopy bulkcopy = new SqlBulkCopy(conn);
bulkcopy.DestinationTableName = dt.TableName;
bulkcopy.WriteToServer(dt);
conn.Close();
Issue 1:-
I am reading notepad: getting all column and values in my data table now while inserting for date and time or integer field i need to do explicit conversion how to write for specific column before bulkcopy.WriteToServer(dt);
Issue 2:- Notepad does not contains all columns nor in specific sequence in that case i can add few column ehich i am doing now but the issue is now data table will add my columns + notepad columns and while inserting how to assign in perticular colums?
sudhanshu sharma Do good and cast it into river :)

Hi,
I think you'll have to do an explicit column mapping if they are not in exact sequence in both source and destination.
Have a look at this link:
https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlbulkcopycolumnmapping(v=vs.110).aspx
Good Luck!
Kaur.
Please mark as answer if this resolves your issue.

Data Source for Ms Sql2005

Hi all,
We are unable to create a data source with JDBC version 2 type for ms sql2005 server.
We had used the following things to create a data source.
XADS Classname: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
In additional we gave the connection string and user name and password.
Created a driver with sqljdbc.jar.
Is there anything other than that we need to do?
The same connection string is working fine for JDBC version 1 type data source.
Regards,
Prakasu.M

Hello Prakasu
I have moved this thread to the Netweaver Administrator forum (this is not a PI technical issue). You have a better chance of getting a quality answer to your query if it is opened in the correct forum. I think the Netweaver Administrator is the best forum for this issue.
Can anyone assist with this JDBC DataSource issue?
Regards
Mark Smyth
XI/PI Moderator

Query for records on a block with Query Data Source Type : Procedure

Hi All,
The veriosn of form I'm using is:
Forms [32 Bit] Version 6.0.8.23.2
I have a block based on a procedure.
But when I enetr-query and search for records specific to ceratin criteria even then the result of the Query is all records.
Is Query not allowed on a block with Query Data Source Type : Procedure.
Hope my question is clear.
Thanks in advance.
Regards
Arif

When you use a table based block, forms can construct any select with any where clause based on the given inputs. Using a procedure based block, forms cannot "know" which in or out parameter of the procedure corresponds to which item. Even if Forms could pass the value of an item to an argument automagically, the procedure would have to "do something" with the argument, and you´d have to code it.
So, any item that should be used in the where-clause must be mapped to an argument.
Perhaps it would be easier to use a table based block querying a view? For DDL, you could use an instead-of-trigger on the view.
Regards,
Gerd

Power View in SharePoint Server - The data extension type for a data source is not valid

Hi All,
All of a sudden I am getting following error when trying to create Power View report using shared report data source (no error testing the connection):
"The current action cannot be completed. The data extension type for a data source
'http://dev/Shared Ducuments/Sales.rsds' is not valid for this operation"
I already have a data source (I had created it after creating my site collection a week ago) and when I use this source to create Power View report then there is no error but I am getting above error when I create another similar data source and use it to create
a Power View report.
Please help me to resolve the error.
Thanks

I am going nuts! I had selected 'Analysis Services' instead of 'Microsoft BI Semantic Model for Power View'

Missing Connection Types in Report Data Source Properties

I am running three installations of SharePoint 2013 with SQL 2012 for Business Intelligence, with Kerberos working.
I have been having intermittent issues with SQL Reporting Services in a multi-server configuration, but finally had it working in all three environments. We discovered many of our issues were caused by master page customizations which we have now disabled
temporarily while we work on function issues.
However, we started having a new problem with Reporting Services on just ONE of the environments, and we are not sure what happened. Most everything appears to still be working, except Reporting Services. I have verified that features are enabled
in both the farm and the site collection, as well as insured managed content types are being allowed on the target document libraries. I also verified the Reporting Service properties and database connections. However, I have found two clear symptoms
which I can find no other information regarding (in logs or in online searches):
1) If we try to create a new "Report Data Source" using the SharePoint UI, it will open a new Data Source Properties window, but in the "Data Source Type" field, there are no values available for me to select my connection type (e.g.,
Microsoft SQL Server).
2) In Central Administration, while administering the Reporting Services Service Application, I can manage a majority of the settings, including System Settings, Manage Jobs, Key Management, etc. However, if I click on the link for "E-mail Settings,"
I get the dreaded "Sorry Something went wrong screen," with an error saying that "Object reference is not set to an instance of an object."
So I am hoping someone has an idea of where I can look for additional information on this issue, or even better, knows what I am missing to get Reporting Services functional again in this environment!
Thanks in advance for any help provided.
Elohir

However, we started having a new problem with Reporting Services on just ONE of the environments, and we are not sure what happened.
Hi Elohir,
I assume you are installing Reporting Services SharePoint mode for SharePoint 2013, you need to:
1. Install "Reporting Services – SharePoint" and "Reporting Services add-in for SharePoint Products" on the SharePoint server that the SSRS service will run on. All other SP servers only need the "Reporting Services
add-in for SharePoint Products."
2. Run the Insall-SPRSService and Install-SPRSServiceProxy on Central Admin and SSRS server.
3. Start SSRS Service only on desired SSRS servers.
http://msdn.microsoft.com/en-us/library/jj219068.aspx
Since the issue occurs only to one of the environments, please provide more information about your multi-server configuration, and point out the server where the issue occurs.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Power view couldn't load the model or data source because the data source type is not supported

Hi,
I have SQL 2012 standard edition in my local. I have developed SSAS & deployed in local. I have been asked to develop power view report in excel 2013 using this SSAS. But when I tried to do in Excel 2013 professional Plus, I am getting below error:
Power view couldn't load the model or data source because the data source type is not supported.
Does power view is supported in standard edition of SQL or it requires Business/Enterprise edition of SQL server?
Thanks in advance

What type of SSAS install are you using?
PowerView in Excel 2013 currently only supports Tabular data sources.
Only PowerView in Sharepoint 2013 supports both Tabular and Multi-Dim data sources. (provided you have the required Sharepoint and SQL updates installed)
http://darren.gosbell.com - please mark correct answers

Re: Invalid Type CURR while activating the data source from R/3 to BI 7

Dear Expert,
I have created a data source using function module and has it successfully replicated in BI 7.
But when I try to activate it, I run into the problem associated with "Invalid Type CURR" with two of the CURR fields.
Could you help me to resolve this problem or provide me with some suggestions?
Thanks and appreciated.
Arthur

In SAP BW 7.0 Currency types are managed via transaction RSCUR.. Perhaps you should check if everything is ok (i mean to check if the Currency Types are transported) before to active your DataSource.
It's only a suggestion .. good luck !

Problem to create data source with OCI type of driver

Hi Experts
We are creating an XA datasource with OCI type of driver using an enterprise application with data-sources.xml, the xml is like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
<data-sources>
     <data-source>
          <data-source-name>OCI_DS_XA</data-source-name>
          <driver-name>ORACLE_DRIVER</driver-name>
          <init-connections>1</init-connections>
          <max-connections>25</max-connections>
          <max-time-to-wait-connection>120</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>60</connection-lifetime>
               <run-cleanup-thread>300</run-cleanup-thread>
          </expiration-control>
          <sql-engine>Vendor_SQL</sql-engine>
          <jdbc-2.0>
               <xads-class-name>
                    oracle.jdbc.xa.client.OracleXADataSource
               </xads-class-name>
               <object-factory>
                    oracle.jdbc.pool.OracleDataSourceFactory
               </object-factory>
               <properties>
                    <property>
                         <property-name>serverName</property-name>
                         <property-value><SERVER_NAME></property-value>
                    </property>
                    <property>
                         <property-name>serverPort</property-name>
                         <property-value>1521</property-value>
                    </property>
                    <property>
                         <property-name>databaseName</property-name>
                         <property-value>ORCL</property-value>
                    </property>
                    <property>
                         <property-name>driverType</property-name>
                         <property-value>oci</property-value>
                    </property>
                    <property>
                         <property-name>user</property-name>
                         <property-value>username</property-value>
                    </property>
                    <property>
                         <property-name>password</property-name>
                         <property-value>password</property-value>
                    </property>
               </properties>
          </jdbc-2.0>
          </data-source>
</data-sources>
We have installed oracle client in server M/C and configured all the environment variables. While we are deploying the application from CE developer studio IDE to the CE 7.1 AS, we are getting the following error:
Description:
          1. Exception has been returned while the 'sap.com/DS_TEST_EAR' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7653550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "OCI_DS_XA".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1467)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:468)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.frame.core.database.DatabaseException: Exception of type java.sql.SQLException occurred: Closed Connection.
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:49)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1400)
     ... 33 more
Caused by: java.sql.SQLException: Closed Connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
     at oracle.jdbc.driver.GetCharSetError.processError(T2CConnection.java:3082)
     at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2811)
     at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:300)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344)
     at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:136)
     at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:194)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:121)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:333)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:84)
     at com.sap.sql.connect.factory.XADSPooledConnectionFactory.getPooledConnection(XADSPooledConnectionFactory.java:27)
     at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.initConnections(DBDataSourcePoolImpl.java:1099)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.<init>(DBDataSourcePoolImpl.java:49)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:507)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:136)
     at com.sap.sql.manager.OpenSQLManager.createDataSource(OpenSQLManager.java:141)
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:42)
     ... 34 more
But when we are creating the datasource with thin type of driver, it is working fine. We have already created a driver with name ORACLE_DRIVER in server using the ojdbc14.jar using Netweaver administrator consol.
Same this is happening when we are creating the OCI type of datasource by using Netweaver administrator consol by specifying all the parameter as above and also the initial connection pool size is more than zero.
Same thing is happening for normal (JDBC 1x) datasource creation with OCI type driver.

Hello,
I ran a search on SDN, related to your error code, i found the following:
UnsupportedClassVersionError in NWDS CE
DeploymentWarning-WebService-Collection
Maybe its useful to you
Regards,
Siddhesh

Data Type field read only in Data source for transaction data (PC_FILE)

Hi folks,
I need to change Data Type for some of the fields in "Field" tab in data source for transactional data. It became read only after I activate the data source. Need help in making it editable. All fields now have Data type=CHAR.
Thanks

Nevermind folks. I got it.

WCF Service as Data source in SSRS report with Complex Types

Hi All,
I have a requirement where we are suppose to use WCF service as datasource in SSRS. I was able to do that when the WCF response type was simple.
Now the requirement have changed where the response type is complex . I couldn't figure out a way of accessing WCF with complex types.
Any pointer will be of great help as I couldn't find any related articles for this kind of scenario.
Raj

Hi Raj,
WCF uses a serialization engine called the Data Contract Serializer by default to serialize and deserialize data (convert it to and from XML). All .NET Framework primitive types, such as integers and strings, as well as certain types
treated as primitives, such as DateTime and XmlElement,
can be serialized with no other preparation and are considered as having default data contracts. Many .NET Framework types also have existing data contracts. For a full list of serializable types, see Types
Supported by the Data Contract Serializer.
New complex types that you create must have a data contract defined
for them to be serializable. You can explicitly create a data contract by using DataContractAttribute and DataMemberAttribute attributes.
This is normally done by applying the DataContractAttribute attribute
to the type.
You can refer to :
http://msdn.microsoft.com/en-us/library/ms733811(v=vs.110).aspxhttp://www.codeproject.com/Articles/738844/Using-WCF-Data-Contract-Known-Types-by-Example
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Abnormal termination of runform when PROCEDURE is used as Query Data Source Type

I created a package with a procedure that returns a table of records. This
procedure tested OK in SQLPLUS. I then created a form and in this form a block
that used this procedure as the Query Data Source Name, and of course the Query
Data Source Type has been set to PROCEDURE. This form runs beautifully when the
number of records returned is small (a few hundreds). But when the number of
records is large (I have one case where the total number of records returned
was 11099) then it will crash. I also found that whenever this happens, there
will be a file in my C:\TEMP with funny namessuch as s90, s81, etc. They are
always the same size (5008 kBytes).
Anyone any ideas?
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chandra movva([email protected]):
Create a view and base your block on view.That could solve the problem unless you have other requirements specifically.<HR></BLOCKQUOTE>
Chandra,
Thank you for your suggestion. Unfortunatel, we have requirements that translate to logics too complicated to be handled by views, and that is why we use PROCEDURES. This actually works very well and very fast, except when we have lots of records returned, then it fails. I am just wondering whether this is a configuration problem ???
Regards,
A. Leung
null

Block Property (Query Data Source Type)

Hello Friends
I am using Forms 6i.oracle 9i.
in the Block Property Pallete under Query Data Source Type there
are 4 Type is mentioned.i have used Table,From Clause Query but yet to use Transactional Trigger and Procedure.How to use this two and it will be very kind enough if u give any example about these twos.
Regards

There's a whole bunch of explanation about this subject in the online help of Forms. Just select the Query Data Source Type property and press F1. The initial explanation is very limited but there are a number of useful links under "Related topics"

Query data source type = procedure or from clause

1)I have a form where a block is based on a from clause. In the source name I entered a simple sql statement.
Isn't the items suppose to show without any other action or
WHAT ELSE DO I NEED TO DO IN ORDER TO SEE THE BLOCK ITEMS EQUIVALENT TO THE COLUMNS IN THE QUERY?
2) I have a form where a block is based on a procedure.
First I created a package in a program unit with the procedures query_procedure, insert_procedure, update_procedure, delete_procedure and lock_procedure.
Then I set the query data source name to the package query_procedure. The columns and arguments were automatically filled by Forms - they are fine as well.
Forms automatically created the block triggers insert-procedure,delete-procedure, update-procedure and lock-procedure.
Everything seems to be fine but when I run the form and execute the query I get frm 40505 - unable to perform query.
What am i doing wrong?
This is the package:
PACKAGE pkgdeptemp IS
type dept_emp is record (
empno number(4),
ename varchar2(10),
job varchar2(9),
hiredate date,
sal number(7,2),
deptno number(2),
dname varchar2(14));
success constant number :=0;
type dept_emp_ref is ref cursor return dept_emp;
type dept_emp_tab is table of dept_emp index by binary_integer;
procedure query_procedure (resultset in out dept_emp_ref, p_empno in number);
procedure lock_procedure (dmlset in out dept_emp_tab);
procedure insert_procedure (dmlset in out dept_emp_tab);
procedure update_procedure (dmlset in out dept_emp_tab);
procedure delete_procedure (dmlset in out dept_emp_tab);
END;
PACKAGE BODY pkgdeptemp IS
function get_success return number is
     begin
          return(success);
     end;
procedure query_procedure (resultset in out dept_emp_ref, p_empno in number) is
begin
     open resultset for
          select e.empno, e.ename, e.job, e.hiredate, e.sal, e.deptno, d.dname
          from emp e, dept d
          where e.deptno = d.deptno
          and e.empno = nvl(p_empno, e.empno);
end query_procedure;
procedure lock_procedure(dmlset in out dept_emp_tab) is
     tempout number(4);
begin
     for i in 1..dmlset.count loop
          select empno
          into tempout
          from emp
          where empno = dmlset(i).empno
          for update;
     end loop;
end lock_procedure;
procedure insert_procedure (dmlset in out dept_emp_tab) is
     cursor c_dept (i binary_integer) is
     select deptno
     from dept
     where deptno = dmlset(i).deptno;
     tempout number(4);
begin
     for i in 1..dmlset.count loop
          open c_dept(i);
          fetch c_dept into tempout;
          if c_dept%notfound then
               insert into dept(deptno,dname)
               values(dmlset(i).deptno, dmlset(i).dname);
          end if;
          close c_dept;
          insert into emp (empno,ename,job,hiredate,sal,deptno)
          values (dmlset(i).empno, dmlset(i).ename, dmlset(i).job, dmlset(i).hiredate, dmlset(i).sal, dmlset(i).deptno);
     end loop;
end insert_procedure;
procedure update_procedure (dmlset in out dept_emp_tab) is
     cursor c_dept (i binary_integer) is
     select deptno
     from dept
     where deptno = dmlset(i).deptno;
     tempout number(4);
begin
     for i in 1..dmlset.count loop
          open c_dept(i);
          fetch c_dept into tempout;
          if c_dept%notfound then
               insert into dept(deptno,dname)
               values(dmlset(i).deptno, dmlset(i).dname);
          else
          update dept
          set deptno=dmlset(i).deptno,
          dname=dmlset(i).dname;
          end if;
          close c_dept;
     update emp
          set empno=dmlset(i).empno,
          ename=dmlset(i).ename,
          job=dmlset(i).job,
          hiredate=dmlset(i).hiredate,
          sal=dmlset(i).sal,
          deptno=dmlset(i).deptno;
     end loop;
end update_procedure;
procedure delete_procedure (dmlset in out dept_emp_tab) is
begin
     for i in 1..dmlset.count loop
          delete from emp where empno = dmlset(i).empno;
     end loop;
end delete_procedure;
END;

for ur q1:
create the text items manually in the layout editor or in the obj navigator then specify there properties manually in the the pallette.
database item = yes
column name = field name in ur select statement
for q2:
try running the form again and press F8 then if an error occur press F1 or shift F1 to show the error in ur code.
i suspect u forgot to specify a value for the in parameter the reason why u get an error that is specify the actual parameter for ur in argument then press F8.
enjoy!

Data Source ID must be of type IDataSource

Similar Messages

Maybe you are looking for