Source in , source out not match

hi ,
i have a little bug really boring problem with color ,
in fact with few plans of my edit color don't use the good in and out point , there are good on the timeline the plan is good sized , i colorise it and when i want to make a render
i see that color try to render about 20 minutes of my rush instead of the 5 or 10 seconds of the plan
i dont understand why
all my rushes are seamly digitalized with no time code break
so when color try to render all my rush it take 30 minutes insteads of 10 seconds
thanks for ur help

No speed changes or time remaps, it's very well documented. Take your time remapped section in FCP, export it out as a self-contained movie, import into FCP, replace the new clip with the speed changed clip and then send to Color.
Please read the Release Notes in the Help section of the Color Menu bar. Little hidden "Gotcha!"s like this are thoroughly documented.

Similar Messages

Posting date in AFRU and 2lis_04_p_arbpl data source is not matching

Hi Experts,
We are facing an issue with 2LIS_04_P_ARBPL data source, posting date in AFRU table and in data source is not matching.
For example: we booked an activity confirmation of value 100 on 01.01.2015 posting date, Counter 1, Operation 10
For the same operation another counter is confirmed on 01.02.2015 posting date.
So, in AFRU table:
Prod Order     Operation     Confirmation Number     Counter     PostingDate     Activity
1001               10               8001                             1              01.01.2015       100
1001               10               8001                             2              01.02.2015       0
In 2lis_04_p_arbpl data source, counter field is missing due to which only 1 record is coming which is:
Prod Order     Operation     Confirmation Number     Counter     PostingDate     Activity
1001               10               8001                             1              01.02.2015       100
In data source, activity of value 100 is coming on 01.02.2015 date instead in AFRU table it is booked on 01.01.2015 posting date by which we are unable to match the value in query which is based on posting date.
Please help on this.
Thanks,
Sameer

Hi Sameer,
Please check on which date the production order has status as "completed".
It could be on 01.02.2015.
Thanks,
Vimal

Selction of US or US Extended Keyboard Input Source does not match my US keyboard

Before upgrade from Maverick to Yosemite my US key board matched the diagram shown in Input Sources in Key Board Viewer. Now it has symbols in different locations that do not match my keyboard.

Check System Preferences/Keyboard/Input Sources to make sure that is set correctly. If so, would you post a screen shot so people can see what you are seeing? Make sure you cover any personal information using Preview. Post the screen shot in a Reply using the camera icon or you can drag the screen shot into a reply. Copy and paste doesn't work.
Screen shots

Print priview and print out not matching

I have a developed a script for Goods receipt.
In the Print Priveiw in MB90 all the boxes inserted by me are appearing
but in the print out some of this boxes are not appearing .
Please help its a bit urgent.

Hi
wat you are seeing in the print preview is just the place where the boxes are displayed but unless you specify the intensity or the thicknessof the lines for the box they will not appear in the print.
try giving some intesity as 10.
Regards
Zarina

"The installed product does not match the installation source" error

Each time I attempt to use the SL disk to update the Apple drivers in Windows XP SP3 on my MacBook Pro 13" I get the error message posted in the title. I used this same disk successfully to update my MacPro. Anyone know what this means?
"The installed product does not match the installation source. Until a matching osurce is provided or the installed product and source are synchronized, this action can not be performed."

I get the same error, and I have an idea of what's going on.
When I try to install Boot Camp 3, Windows asks me to locate "BootCamp.msi". If I try to uninstall Boot Camp via "Add/Remove Programs", the same prompt comes up.
What I think is happening is that the original installer for Boot Camp 2.0 is being requested. But I have applied the Boot Camp 2.1 update, which has no BootCamp.msi file associated with it.
So I'm at a road block of sorts, unable to install Boot Camp 3.0. I cannot download the original Boot Camp 2.0 installer from Apple, only the 2.1 update. (I recently moved across the country and didn't bring my 10.5 media.)
Any ideas out there on what can be done to get Boot Camp 3.0 installed?
Message was edited by: Human Being

Bitlocker enabled drive, recovery key needed during boot, PCS did not match, event id 24635, source bitlocker-driver

Hi
After rebooting one of our test machines, bitlocker wanted the recovery key.
There were no hardware modifications on that machine.
Error message in event log:
Bootmgr failed to obtain the bitlocker volume master key from the TPM because the PCRs did not match
Event id 24635, source bitlocker-driver
Each time the machine starts, the recovery key is needed.
Any idea how to solve that issue and why it happens?
update:
Second partition was created manually on that machine. So that's clear that bitlocker reacts...
But now: how can I confirm those changes so that the recovery key is not needed each time we boot?

Hi,
I would like to confirm if BitLocker accepts the recovery key?
Please update the BIOS to improve the stability for TPM first.
I also would like to suggest you disable and enable BitLocker again to reset the settings.
For more information, please refer to the following link:
http://technet.microsoft.com/en-us/library/dd835565(WS.10).aspx
Regards,
Arthur Li
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]
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.

Source port type for BPELProcess does not match target port type for EJB

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Unique Identifier of the source style does not match the target st

I'm running into a bunch of problems with an export/import, but I'll limit myself to the more opaque ones for the moment. We've got a page group in place and are trying to overwrite it, or at least parts of it, with a revised version. The export appears to succeed, but the pre-check (and consequently, it appears, the entire import) fails. One of the few specific errors has to do with a style:
[ERROR] id = NULL context = style_pre_check user = PORTAL The Unique Identifier of the source style MY_STYLE does not match the target style MY_STYLE.
The style in question exists in both our development environment (from which we're exporting) and our target environment (into which we're importing, of course). It hasn't even been changed in the development environment, so it's identical to what it's replacing. Does anybody know what's going on here and how it might be fixed?

This indicates the style in the production did not come from the same development system as the one you're attempting the new import from. Also, this could happen, if for some reason you had deleted the style in the development after it was deployed to production and (re-) created a new style with the same name.
In order for pre-check to succeed, you would need to either rename the style on the production or rename it on development and re-export and import the transport set again.

JLDAP source from OpenLdap does not match current package

The wiki page for the JLDAP downloads ('LDAP Classes for Java -
Developer Community' (http://developer.novell.com/wiki/index.php/Jldap))
indicates "Source code matching this release is available through the
OpenLDAP Open Source initiative." Unfortunately, the current packages
(which have needed bug fixes) were modified in 2009, but the most
current source on the OpenLDAP site is from 2008. Consequently, we don't
have source that we can use to debug during development, which is
hindering our ability to effectively develop new functionality against
eDirectory. Is there a plan to get the most up-to-date source available?
mkilpatr
mkilpatr's Profile: http://forums.novell.com/member.php?userid=10119
View this thread: http://forums.novell.com/showthread.php?t=413181

mkilpatr;1987221 Wrote:
> The wiki page for the JLDAP downloads ('LDAP Classes for Java -
> Developer Community' (http://developer.novell.com/wiki/index.php/Jldap))
> indicates "Source code matching this release is available through the
> OpenLDAP Open Source initiative." Unfortunately, the current packages
> (which have needed bug fixes) were modified in 2009, but the most
> current source on the OpenLDAP site is from 2008. Consequently, we don't
> have source that we can use to debug during development, which is
> hindering our ability to effectively develop new functionality against
> eDirectory. Is there a plan to get the most up-to-date source available?
Hi,
The source can not be different, because there is only on source
repository and that is OpenLDAP. Even the Novell's libraries are built
from the OpenLDAP Source only. The source changes and bug fixes from all
the JLDAP maintainers (both from and outside Novell) wil be checked in
to OpenLDAP's JLDAP repository only.
-WITH REGARDS,-
*-Palaniappan N-*
palaniappan1's Profile: http://forums.novell.com/member.php?userid=12325
View this thread: http://forums.novell.com/showthread.php?t=413181

The key columns of the country measure group attribute do not match in either number or data types to the key columns of the source attribute

I have a country dimension which is used in 5 cubes. Now I want to change 'key column' property of the country attribute. Whenever I do this, I get an error as "The key columns of the country measure group attribute do not match in either number or
data types to the key columns of the source attribute". I dont understand what this error is about.
Can someone please help? Thanks in advance.
-Regards,
Raj Patil

sounds like you need to verify your dimensional usage tab to verify the relationships between dim and fact on the measure group.
Hi Talktorajpatil,
As Jon said, you can verify the relationships between dim and fact on the measure group on the dimensional usage tab. Use this section to define how you "join" your measure groups to your dimensions. There may be a Dimension-Measure Group relationship
that is defined using the wrong attributes and you'll need to select the correct attributes to link the Dimensions to the measure groups. Here are some similar thread for your reference.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/74203b66-8a71-4681-8e47-8f99cce87b3d/error-on-the-measure-group-which-do-not-match-the-data-type-of-the-key-column?forum=sqlanalysisservices
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2421058d-fd4a-44b8-8c7c-b0b349bbef2d/measure-group-attribute-key-column-does-not-match-source-attribute?forum=sqlanalysisservices
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

IMPORT Target Portal does not match the Source Portal version

Hi,
Executing the import via the command line gives me the following error: Error: Target Portal does not match the Source Portal version
Cannot proceed with Import
Checking the output of the script tells me that the portal source has version 9.0.2.6 and the target 9.0.4.0.
Does this mean that there is no backwards compatibilty?
How should I continue from here?
Best Regards

Portal Export/Import utilities are designed only to work between Portals which are at the same version level.
For more information, please see this section in the Portal Export/Import FAQ for 9.0.2.6:
http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/DEPLOY_PERFORM/9023_EXPORT_IMPORT_FAQ_0308.HTM#question_5
OracleAS Portal allows you to upgrade your existing content to the latest release of Portal.
What you need to do in your particular case is to upgrade your existing portal installation from 9.0.2.6 to 9.0.4 before using Portal Export/Import between your two portal instances.
Best Regards,
Harry

"Source File does not match XML Schema"

Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.
This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?
Thanks, Don
IMPORT LOG ENTRY:
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
<MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@[email protected]"
>
     <Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
          <Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
          <Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
          <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
          <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
          <Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
     </Open>
</MDM_Log>
SOURCE FILE:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<MDMCUSTOMER>2463</MDMCUSTOMER>
<CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE>
- <RETURN>
<TYPE />
<MESSAGE />
</RETURN>
- <PT_CONTPART_RETURN>
- <item>
<MDM_CONTACT>0000000001</MDM_CONTACT>
<CONTACT>0001111119</CONTACT>
</item>
- <item>
<MDM_CONTACT>0000000004</MDM_CONTACT>
<CONTACT>0002222229</CONTACT>
</item>
</PT_CONTPART_RETURN>
- <PARTNERS>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>RE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001333329</PARTNER_NUMBER>
<DEFAULT_PARTNER>X</DEFAULT_PARTNER>
</item>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>WE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001555559</PARTNER_NUMBER>
<DEFAULT_PARTNER />
</item>
</PARTNERS>
</item>
</CUSTOMER>
</ns1:CustomerCreateResp>
SCHEMA:
   <?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
<xsd:element name="CustomerCreateResp" type="CustomerCreateResp" />
- <xsd:complexType name="CustomerCreateResp">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="CUSTOMER">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PARTNERS" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

You have to define the namespace in the URI field of XML Schmea in Console.
In MDM Console,
Admin -> XML Schemas -> Create XML Schema
You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.
Please update this post if fixed your problem.

SSIS OLE DB Data Source: literal does not match format string

Dear All,
this is my first post on this forum, so sorry if I choose wrong category for this question, but I stuck...
I'm using SSIS from SQL Server 2k8 R2 in Windows Server 2k8 R2. I have installed Oracle Client 10.2.0.2 32 bits and Oracle Client 10.2.0.4 64bits. I want to connect to Oracle 8i and Oracle 9i by these clients.
Unfortunately when I want to see a preview, only error occurs to me:
ORA-01861: literal does not match format string (OraOLEDB)
I have read a lot about this issue but nothing helps me (to_date, cast, convert etc.).
This is query which I use:
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '99991231'I have investigated that the problem is with TRANSACTIONDATE column (which is VARCHAR2 data type in database).
I want also inform You that the same query in SSIS 2005 on Windows 2005 64 bits worked fine.
Could You help me to find a solution?
Thanks in advance,
Łukasz - chalunster
PS. Sorry for my english
Edited by: BluShadow on 16-May-2011 15:15
put {noformat}{noformat} tags into the message and encoded the < symbol so that it formats correctly.

user10450810 wrote:
Dear All,
this is my first post on this forum, so sorry if I choose wrong category for this question, but I stuck...
I'm using SSIS from SQL Server 2k8 R2 in Windows Server 2k8 R2. I have installed Oracle Client 10.2.0.2 32 bits and Oracle Client 10.2.0.4 64bits. I want to connect to Oracle 8i and Oracle 9i by these clients.
Unfortunately when I want to see a preview, only error occurs to me:
ORA-01861: literal does not match format string (OraOLEDB)
I have read a lot about this issue but nothing helps me (to_date, cast, convert etc.).
This is query which I use:
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '99991231'
I have investigated that the problem is with TRANSACTIONDATE column (which is VARCHAR2 data type in database).
I want also inform You that the same query in SSIS 2005 on Windows 2005 64 bits worked fine.
Could You help me to find a solution?
Thanks in advance,
Łukasz - chalunster
PS. Sorry for my englishHi
Welcome to OTN Forums!
Are you sure you are using following code
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < 'If yes, then youistake is there,
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < 'your script is not ended you can use this
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '20110101'or
WHERE to_date(TRANSACTIONDATE,'YYYYMMDD') >= to_date('20050101','YYYYMMDD')
AND to_date(TRANSACTIONDATE,'YYYYMMDD') < to_date('20110101','YYYYMMDD')Edited by: Mahir M. Quluzade on May 16, 2011 6:59 PM

SQL Server Reporting Services: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Hey everyone, So I am trying to get a report onto the server, and in BIDS I kept getting a login screen repeating over and over when I tried to deploy my report, so I tried to upload the file at http://<servername>/Reports This worked, but then trying
to run this report from http://<servername>/Reports did not work either because "An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'FTYDataSource'. (rsErrorOpeningConnection) For more information
about this error navigate to the report server on the local server machine, or enable remote errors" Anyways I tried to add a New Data Source (which I would use in the report) at http://<servername>/Reports, type ODBC, with the connection string Dsn=blah_blahblah.
I try to test the connection here and get the error ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified This is really getting old fast, everything I try, a new error comes up. Granted I am new at this,
but this still should not be this troublesome. Does anyone have any ideas on what could FINALLY allow me to just put a report out onto the server?!? THANK YOU in advance for ANY help.

Hi,
Please try setting the credentials of the datasource.
1. Double click and open the datasource in your project.
2. Click on the credentials tab, and click on option button 'Use this username and password'
3. Enter the username and password to connect to the datasource
4. Deploy or upload the datasource to the report server and try accessing the reports.
Hope this helps.
Please click "Mark as Answer" if this resolves your problem or "Vote as Helpful" if you find it helpful.
BH

XML Data Source: does not seem to validate against XSD

I setup XML data source using the example "b-c.xml" and "b-c.xsd"; I changed the
root element of "b-c.xml" from "<db>" to "<Customers>"; but Liquid Data does not
seem to care or validate the instance document against the XSD.
Is this a known bug? It's something very basic and obvious!

LD does indeed catch and report the mis-match at run-time as shown in the exception
below.
It does not valid the XML file against the schema at configuration time, only
at run-time. Hence Step 8 here - http://edocs/liquiddata/docs81/admin/xml.html#1035818
But beware - in some (most) cases LD does not do validation against the schema
for performance reasons. If the schema does not match you will simply get empty
results.
- Mike
java.rmi.RemoteException: Query Execution Error (Run Time) 1-2-3-24: Cannot process
XML file source XM-BB-C. (com.enosysmarkets.xqdm.translators.XqdmTranslatorException:
Invalid root element name: 'CUSTOMERS'. Expected: 'db')
"David Song" <[email protected]> wrote:
>
I setup XML data source using the example "b-c.xml" and "b-c.xsd"; I
changed the
root element of "b-c.xml" from "<db>" to "<Customers>"; but Liquid Data
does not
seem to care or validate the instance document against the XSD.
Is this a known bug? It's something very basic and obvious!

Source in , source out not match

Similar Messages

Maybe you are looking for