Problem while executing my package from a different schema

Hi,
I developed a package.
Now when i try to execute my package( which is in Schema1) from a different schema(Sc2) in the same database(9.2.0.1)
i.e. execute <Sc1>.<package_name.Package_main_proc>;
I'm able to execute the package successfully.. but .. my package is deleting all records in all the tables used by the package !!
If I run the same package from my schema(Sc1).. everything is working fine.
i.e. its deleted only unwanted records after executing the whole package.
Can anyone pls help me.
Regards
Jack

Guido,
I'm sorry for asking a really vague question.
I included all the dbms_output.put_line() in my code. As i executed in my schema. I couldnt find any error.
So now, instead of calling my package from Sc1.
I compiled my package in Sc2( I dint get any errors) and then executed it.
Even now data is deleted from the tables.
So now i tried thru another schema(SC3)..
again compiled it and executed it.. now everything is working fine.
So to my understanding i just there is some dependency is Schema 2. But i'm not able to figure it out as i'm not getting any error.
Am i going is right direction. If not please correct me .
Thanks

Similar Messages

Getting Error while Execute SSIS Package from Console Application

Dear All,
SSIS package working fine directly.
I got following error while execute SSIS package from C# console application.
The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
OLE DB Destination failed validation and returned error code 0xC004800B.
One or more component failed validation.
There were errors during task validation.
Code :
public static string RunDTSPackage()
Package pkg;
Application app;
DTSExecResult pkgResults;
Variables vars;
app = new Application();
pkg = app.LoadPackage(@"D:\WORK\Package.dtsx", null);
Microsoft.SqlServer.Dts.Runtime.DTSExecResult results = pkg.Execute();
I have recreate the application with again new connection in SSIS.
Still not working, Please provide solution if any one have.
DB : SQL Server 2008 R2
Thanks and regards,
Hardik Ramwani

The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
Are you sure that you are running the same package via .NET which works fine from Visual Studio?
By reading error message, I can say that you have copied OLEDB task from another package OR you have deleted one OLEDB connection manager. Now when package is run this task tries to use the connection manager and not found thus throws error message.
Open all OLEDB destination tasks and you find connection manager missing. Connection Manager name should be provided there
Cheers,
Vaibhav Chaudhari
MCSA - SQL Server 2012

Facing a small problem while executing WDA application from portal

Hi Experts,
I developed web dynpro for ABAP application and placed table UI control, which contains 270 records. Executing from SE80, it is working fine and showing clearly all records.
This application integrated in portal, while executing this applicaiton from portal, it is working fine and showing all records.
Here I facing a small problem i.e Pager ( footer area ) of table.
When the table is displayed there are the small box in the below of the table showing ROWS 244 of 270.
244 will be available in a small box. this 244 is not showing clearly, while executing from portal ( last digit 4 displying half part only). but 244 showing clearly while executing from SE80.
Kindly suggest how to resolve this problem.
Thanks & Regards
Sridhar

Hi Gopi Krishna,
Thanks for your time. From SE80, it is working fine and showing clearly row number. There is no property for increase width of small box, which contains current row number).
Facing problem while executing from portal.
Thanks & Regards
Sridhar

Problem with execute SSIS package from stored procedure

Hi,
I would like to execute SSIS package from stored procedure. Therefore, I implemented sp which exec SSISDB.CATALOG.CREATE_EXECUTION method. When I try to test it from SSMS on remote server, I got error that
I was able to solve by adding “WITH EXECUTE AS …”. Then I got another error: The server principal "Domain\user" is not able to access the database "SSISDB" under the current security context. On Internet, I found a couple post that describe
how to access SSIS catalog (one of them by Ke Yang -
http://blogs.msdn.com/b/mattm/archive/2012/03/20/ssis-catalog-access-control-tips.aspx). It didn’t help. I’m still getting the error message.
How to debug this issue?
Any suggestion?
Thanks
SQL Server 2014 BI

SSMS does not propagate user credentials thus the error
Arthur
MyBlog
Twitter

Problem while executing the package

Hi Guys,
I am getting the problem while executin the package for 1 of the interface named PRE_SYNC_EX_ARMY_VEH_DEL.
The source tables are EX_ARMY_VEH_TMP and CONTROL_DEL & target table is CONTROL_DEL
All the three tables are in the same schema named RTO_STAGE.
I am looking in the operator as at the first session is in the process(running mode) with "DROP FLOW TABLE" as the message while all other sessions are in the waiting mode related to that interface PRE_SYNC_EX_ARMY_VEH_DEL.The previous interface before it ie PRE_SYNC_AXLE_DEL & PRE_SYNC_AXLE_DELNR is running okk(with all succesful session).
**In one statement I can summerize that execution of package is halting/stopped at one interface & not showing error in operator(showing running)**
what would be the problem?
Thanx
Edited by: user8849294 on Mar 1, 2010 10:17 PM
Edited by: user8849294 on Mar 2, 2010 9:36 PM
Edited by: user8849294 on Mar 2, 2010 9:43 PM

Hi,
You didn't mention the exact error.
Did you check if your interface succeeds outside the Package?
If yes, have you included any odiFileWait event which's why other tasks are kept in Wait mode?
In any case, if there's an error, the task with the red-colored icon shows the one with problem. Double-click it & go to the Execution tab to get the exact error

Problem while executing a report from Planning Web

Hi,
I've got this error message when I execute a report from Hyperion Planning (web) :
"5200: Error executing query. [1106] Error : Class component property name invalid[DataType]"
Can you help me please ?
Thanks.
Virgile.

I didn't see anyone post the resolution on this. I recently re-ordered the dimensions in my outline, and afterwards was getting that error. It's a simple fix of changing the database connection to something else, then changing it back. I was able to do this because I have multiple databases with the same outline structure. If you don't, possibly you may just have to re-create the connection, not sure.
Sabrina

ERROR WHILE MIGRATING SSIS PACKAGE FROM DEVELOPMENT TO PRODUCTION IN EXECUTION

HI,
I have a problem while executing the package after migrating from DEVELOPMENT to PRODUCTION.
We have two SQL database connections DEVMIDDLEWARE and PRODMIDDLEWARE for dev and prod respectively. When we have created package in development we have used DEVMIDDLEWARE and we have credentials in CONFIG file of that package and executed sucessfully. When
we migrated this same package to PRODUCTION when have given credentials of PRODMIDDLEWARE in CONFIG FILE of this package we are getting error as below
"Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic
error. Verify that the correct key is available. End Error Error: 2014-10-28 07:41:44.24     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC0202009     Source: Package Connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware"     Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.".
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC020801C     Source: Package Log provider "SSIS log provider for SQL Server"     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method
call failed. COM error object information is available. Source: "Package" error code: 0xC0202009 Description: "SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE
DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.". ". End Error Error: 2014-10-28 07:41:44.98
Code: 0xC0202009     Source: Package Connection manager "AGRDB01.abwr66"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record
is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'CC\epsdbuser'.". End Error Error: 2014-10-28 07:41:44.98     Code:
0xC020801C     Source: Data Flow Task OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "AGRDB01.abwr66"
failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC0047017
Source: Data Flow Task SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC004700C
Source: Data Flow Task SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-10-28 07:41:45.00     Code: 0xC0024107     Source: Data Flow Task
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 07:41:44 Finished: 07:41:45 Elapsed: 0.859 seconds. The package execution failed.
The step failed."
Can anyone help for this error.
Many thanx in Advance

Hi Babloo,
According to the error message, the package may have failed are as follows:
The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
The package may not run in the following scenarios:
The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Run an SSIS Package Under a Different Account
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error while running SSIS package from Integration service or via Job

Hi All,
I encounter the below error while running SSIS Package from Job or integration service. However on execution completes success fully while running from data tools. The issue occurs after migration to 2012 from 2oo5 dtsx. PFB the error.
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by
the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
A buffer failed while allocating 10485760 bytes.
The system reports 26 percent memory load. There are 206110765056 bytes of physical memory with 150503776256 bytes.
free. There are 2147352576 bytes of virtual memory with 185106432 bytes free. The paging file has 208256339968 bytes with 145642921984 bytes free.
The package also runs successfully from other servers. This happens only in one of our server.seems like issue with some sql configuration.

Hi ,
Are you running using SQL Agent Job and Data tools on same server or different?
If it is executing fine using Data tools and failing with Job it might be User credentials issue.Try
to run Job with your credentials by using proxy .
Regards,
Prathy
Prathy K

Error executing SSIS packages from Agent

Hi All,
     I designed SSIS package that loads data from Oracle table to SQl server table along with loading data into Diension and fact tables using SSIS packages only. First I created all SSIS packages that loads data into Staging tables from
Oracle table in next level loading data into Dimension table and final level is loading data into Fact table. At lasts I created One master package there I'm calling all packages (Execute package task) differently.
Configuration type: Parent package configuration for All child packages. XML config for parent package.
When I execute SSIS package from BIDS data is loading up to Fact table. When I execute SSIS packages through Sql server agent ( Using File System Deployment)When I execute SSIS package from Sql server agent it is throwing an error message like
Message
Executed as user: . Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 10:45:10 PM Error: 2013-10-17 22:45:12.60
Code: 0xC00220E6     Source: Master Data      Description: There is no project to reference. End Error Error: 2013-10-17 22:45:12.61     Code: 0xC0024107     Source:
Master Data      Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:45:10 PM Finished: 10:45:13 PM Elapsed:
2.59 seconds. The package execution failed. The step failed.
I'm uploaded config file also while at the time of scheduling job.
Regards,
Praveen
Regards, Praveen

Hi Praveen,
The issue may occur if the SQL Server Agent Service Account or Proxy account doesn’t have sufficient permissions. Please create a SQL Server Agent Proxy account that has the permissions to execute the package and perform update operations on the SQL Server
fact tables.
Reference:
http://technet.microsoft.com/en-us/library/ms175834.aspx
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Problem While Executing T.CODE DP90

Hi,
We have Upgrade our system from 4.6C to ECC6.
We are facing following problem while executing Resource Related Billing request
Through Transaction code DP90.
Process.
1.     We are creating Sales Order and system will create Service order automatically as per the configuration.
2.     In service order we have External as well internal operations ,
Internal operations will be confirmed through IW41, and External Operations we are creating Purchase Requisition then creating PO and MIRO,
After all Operations confirmed we will make Service order status as technically completed, then we are executing DP90 for Resource Related Billing, System will determine the material, combination of Cost element and Activity Type (Which is configured in T.Code ODP1) For External Operations System is Considering Activity Type for material determination in 4.6c but it is not considering Activity Type for Material Determination in ECC6 for External Operations.
   Please Help me,
Edited by: D B on Apr 29, 2008 6:13 PM

Hi Prashanth,
      Thanks for your reply, but all activity are valid in current period, in our Scenario in the old system for External Operations with combination of Activity type and Cost element system is determining material but where as in the new system for external operations it is not considering the Activity type and system is determining the material in the combination of   Cost element and Blank activity type so, we are getting different material in DP90.

Encoding problem while reading binary data from MQ-series

Dear all,
we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
It seems to us that
1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
2. Both CCSID parameters are not used anyway in JMS-adapter
How can we solve this problem without changing anything on MQ-site?
Here is the stack-trace:
Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
    at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
    at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
    at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
    at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
    at java.lang.Thread.run(Thread.java:770)
Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
    ... 36 more
Caused by: sun.io.MalformedInputException
    at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
    at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
    at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
    at java.io.InputStreamReader.read(InputStreamReader.java:208)
    at java.io.BufferedReader.fill(BufferedReader.java:153)
    at java.io.BufferedReader.readLine(BufferedReader.java:316)
    at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
    at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
    ... 40 more
Any ideas?
Kind regards, Stefan

Hi Stefan,
for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
The second MTB, which does the XML-Wrapping, is configured like this:
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = application/xml
xml.conversionType = SimplePlain2XML
xml.fieldNames = value
xml.fieldSeparator = §%zulu§%
xml.processFieldNames = fromConfiguration
xml.structureTitle = payload
Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á). E1 is (different from ISO) an "ß" in 850.
Any ideas?

Re: [iPlanet-JATO] Experiencing problem while executing model.

Hi Todd,
Thanks a lot for your input!
In the case , I found that "TO_CHAR(PLAN_DT, 'MM/DD/YYYY')" is alaised as a
column name in the resultset. So I am using this as a column in Jato
Descriptor for Plan_Dt. Now it is working fine.
Thanks and Regards,
Santa.
----- Original Message -----
From: Todd Fast <toddwork@c...>
Sent: Thursday, July 26, 2001 9:50 AM
Subject: Re: [iPlanet-JATO] Experiencing problem while executing model.
Santa--
I am experiencing a problem while executing a bounded model. I am usingQueryModelBase. Whenever the following query gets executed inonBeforeModel
execute of TiledView, it throws an exception describing "PLAN_DT not found
in ResultSet". If you execute this query on the SQL prompt then we getrows
of data. Please could you tell us how the mapping between model and
resultset works ? And what changes do we have to make to execute thisquery.
>>
SELECT PART_NM,NEWTXTDOLL
TO_CHAR(PLAN_DT, 'MM/DD/YYYY'),
FROM cpsselect
WHERE CHG_DT >= TO_DATE('2001-06-17', 'YYYY-MM-DD')The mapping of result set to model is done via JDBC, using the columnnames
you provide in your model's column descriptors. It sounds as if you are
providing the column name "PLAN_DT" in a descriptor, and when the model
tries to look up that column in the result set, there is no such columnand
the operation fails.
In order to debug this, you should try running your query with a JDBC
connection, not SQL*Plus or your command-line SQL tool. What you need to
find out is how the expresion "TO_CHAR(PLAN_DT, 'MM/DD/YYYY')" is aliasedas
a column name in the resut set. The easiest way to do this is to write a
simple class that does nothing but use your JDBC driver to connect the
database and execute this query. After execution, use theResultSetMetaData
information to find out the column names for the result set. Then, use
these column names in your JATO column descriptors.
Another Problem:We are not getting the values for NEWTXTDOLL column whenwe try to display it in a Tiled View.
I'm sorry, this isn't enough information for me to offer any suggestions.
Using the technique above, determine which columns are coming back in the
result set, and make sure your display fields in the TiledView are boundto
those column names. The problem could be something as simple as a typo in
the field's bound name, or something more complex like the column in the
result set being named something you don't expect.
Another approach might be to alias the columns yourself using the "AS
<alias>" expression, and assign them names that you choose instead ofusing
the names assigned by the database or JDBC driver.
Todd
[email protected]
The Information contained and transmitted by this E-MAIL is proprietary to
Wipro Limited and is intended for use only by the individual or entity to
which
it is addressed, and may contain information that is privileged, confidential
or
exempt from disclosure under applicable law. If this is a forwarded message,
the content of this E-MAIL may not have been sent with the authority of the
Company. If you are not the intended recipient, an agent of the intended
recipient or a person responsible for delivering the information to the named
recipient, you are notified that any use, distribution, transmission,
printing,
copying or dissemination of this information in any way or in any manner is
strictly prohibited. If you have received this communication in error, please
delete this mail & notify us immediately at mailadmin@w...
[Non-text portions of this message have been removed]

Hi Todd,
Thanks a lot for your input!
In the case , I found that "TO_CHAR(PLAN_DT, 'MM/DD/YYYY')" is alaised as a
column name in the resultset. So I am using this as a column in Jato
Descriptor for Plan_Dt. Now it is working fine.
Thanks and Regards,
Santa.
----- Original Message -----
From: Todd Fast <toddwork@c...>
Sent: Thursday, July 26, 2001 9:50 AM
Subject: Re: [iPlanet-JATO] Experiencing problem while executing model.
Santa--
I am experiencing a problem while executing a bounded model. I am usingQueryModelBase. Whenever the following query gets executed inonBeforeModel
execute of TiledView, it throws an exception describing "PLAN_DT not found
in ResultSet". If you execute this query on the SQL prompt then we getrows
of data. Please could you tell us how the mapping between model and
resultset works ? And what changes do we have to make to execute thisquery.
>>
SELECT PART_NM,NEWTXTDOLL
TO_CHAR(PLAN_DT, 'MM/DD/YYYY'),
FROM cpsselect
WHERE CHG_DT >= TO_DATE('2001-06-17', 'YYYY-MM-DD')The mapping of result set to model is done via JDBC, using the columnnames
you provide in your model's column descriptors. It sounds as if you are
providing the column name "PLAN_DT" in a descriptor, and when the model
tries to look up that column in the result set, there is no such columnand
the operation fails.
In order to debug this, you should try running your query with a JDBC
connection, not SQL*Plus or your command-line SQL tool. What you need to
find out is how the expresion "TO_CHAR(PLAN_DT, 'MM/DD/YYYY')" is aliasedas
a column name in the resut set. The easiest way to do this is to write a
simple class that does nothing but use your JDBC driver to connect the
database and execute this query. After execution, use theResultSetMetaData
information to find out the column names for the result set. Then, use
these column names in your JATO column descriptors.
Another Problem:We are not getting the values for NEWTXTDOLL column whenwe try to display it in a Tiled View.
I'm sorry, this isn't enough information for me to offer any suggestions.
Using the technique above, determine which columns are coming back in the
result set, and make sure your display fields in the TiledView are boundto
those column names. The problem could be something as simple as a typo in
the field's bound name, or something more complex like the column in the
result set being named something you don't expect.
Another approach might be to alias the columns yourself using the "AS
<alias>" expression, and assign them names that you choose instead ofusing
the names assigned by the database or JDBC driver.
Todd
[email protected]
The Information contained and transmitted by this E-MAIL is proprietary to
Wipro Limited and is intended for use only by the individual or entity to
which
it is addressed, and may contain information that is privileged, confidential
or
exempt from disclosure under applicable law. If this is a forwarded message,
the content of this E-MAIL may not have been sent with the authority of the
Company. If you are not the intended recipient, an agent of the intended
recipient or a person responsible for delivering the information to the named
recipient, you are notified that any use, distribution, transmission,
printing,
copying or dissemination of this information in any way or in any manner is
strictly prohibited. If you have received this communication in error, please
delete this mail & notify us immediately at mailadmin@w...
[Non-text portions of this message have been removed]

Short dump while executing info package in 3.5 data flow?

Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
Thanks

Hi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards.

Error when execute a package from SQL Server Agent

We have the next problem:
When we execute a package from a Job of SQL Server agent, it shows the success messege, but reviewing the results, the package didnt do all the tasks.
When we run it mannually by MSIS the package, it shows the success message and it works fine.
The workflow of the package is :
1) Shrink the databases (executing a sql file)
2) Backup the databases (Back up Database task of MSIS)
3) Rename the files to .BAK extension (by the Foreach loop container and fyle system task)
4) Execute command to compress the it (by a .bat)
5) Move the compress file to another location (by another Foreach loop)
Manually run correct, but when is a a SQL AGent Job that execute the package it does only the first 2 steps.
we are ussing Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (coffee) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
We are using a user with administrator privilegies
Cheers

Can you check if account running package has proper access. You may need to define a proxy account for that.
See
http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
http://gqbi.wordpress.com/2014/01/30/setting-up-a-proxy-account-to-run-sql-server-integration-services-ssis-2012-packages/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Execute SSIS Package from JOB which contains Execute Process Task calling a .bat file

Hi All,
I have a EXCEL Macro needs to be called from SSIS. We could not use Script task because of some internal reason.
So we have taken an approach to call a .BAT file using Execute Process Task. This .BAT file will call a .VBS file which will execute the EXCEL Macro.
The SSIS Package is running good if I execute the package from BIDS.
But the real problem is with the scheduling this SSIS Package using SQL JOB.
If i execute this SSIS package from SQL Server Job, its executing the whole package successfully except the Execute Process Task.
So the overall issue is SQL Server Job is not executing properly if I call any .BAT file from the SSIS Package.
Please give me suggestion to get rid of the issue. Thanks in advance.

Hi Sai.N,
If you run the SQL Server Agent job manually from SSMS, does the package execute properly? If the package executes properly when you run the job manually, the issue should occur due to permission issue. In this case, I suggest that you create a SQL Server
Agent proxy based on the current Windows account which you use to log onto the operating system, and run the job under the proxy account.
If it is not the issue, please enable logging in the package as Visakh mentioned and post the warning/error message for further analysis.
Regards,
Mike Yin
TechNet Community Support

Problem while executing my package from a different schema

Similar Messages

Maybe you are looking for