AA3 and Delta 1010

I am a newbie to this forum but I have used AA since it was Cool Edit. I "upgraded" to AA1.0 when it was first introduced. I have used it exclusively for stereo recordings and never had any trouble.
I recently built a mobile multitrack studio using M-Audio's Delta 1010 as the sound card with appropriate mic pre amps, etc. I built a PC (Windows XP Pro) specifically for this rack solely for recording. It uses an AMD Dual Core processor running at 2.21 GHz with 2GB of RAM. The HD has 240 GB total space with 90GB free. All went well with numerous 5-channel surround sound recordings (Minnetonka's DTS SurCode).
Last week, I recorded a friend's big band, his church choir and another big band all with promises of demo CDs. I recorded them using all 8 Delta 1010 channels instead of just 5. All recordings suffered staggered track time drift and are unusable. The recording sessions were 600 miles away.
I have at least two questions:
Is there any way to salvage the time-drifted tracks?
I have already upgraded to AA 3.0 (today) Is there a way to make sure this does not happen again?
Thanks!

[email protected] wrote:
> Great!
> I will spend some extra time setting up the system to make sure I use
> the most current drivers.
> BTW, I added a second SATA hard drive for my recorded files -- no
> program files on this disk.
The classic default advice is to have temp folder on one drive and audio
file folder on another. With two temp folder being suggested it becomes a
suggestion of having three (sets of) spindles. I have empty 16 gb partitions
outermost on two drives in my stationary daw, formatted with fat32, those
are for audio temp files only.
Another classic advice is to defrag prior to recording so as to have
contiguous empty space and NOT defrag after recording so as to maintain the
files in the interleaved state they are written to disk in. There may be all
kinds of good reasons to not apply this .... but do understand the reasoning
in it.
Also: while paritioning implicitly is suggested please do be aware that it
can also end up being a nuisance and a constraint. Plan carefully and
wisely.
> Thanks to all.
Kind regards
Peter Larsen

Similar Messages

Logic Pro 8 and Delta 1010 random audio stuttering

Since installing Logic Pro 8, I have two problems which I suspect may be related:
1. Launching Logic will sometimes freeze my Mac and bring up that familiar screen that says I must immediately restart. This seems random, happening maybe one time out of 7 or 8.
 2. The other problem is that launching Logic 8 sometimes results in apparent misbehavior by my PCI audio card, a Delta 1010. In such cases, I will immediately hear something that sounds like very loud white noise coming out of the audio interface and into my mixer, but with a rapid stutter (confirmed by the VU meters on the Delta control panel, which vibrate like they're having a seizure). Nothing seems to stop the noise, except quitting Logic and restarting the Mac. This misbehavior seems quite random and there's nothing I've been able to do to track it down or make it repeatable -- all I can do is quit Logic, restart, and hope that this time it works. Fortunately, if I can finally get Logic 8 launched without the noise factor, it runs fine and virtually never crashes.
Anyone have any similar problem or ideas about the cause? I'm thinking about replacing the Delta 1010 with a new Firewire audio interface, in anticipation of buying a new Mac later this year. But I don't want to do it now if it's not the 1010's fault.
(Details: I am using the latest driver for the Delta 1010, downloaded from M-Audio's web site; the latest version of Logic 8 (8.0.1); and Mac OSX 10.4.11. I've got this all running on an older Mac, a G4 Dual 1.25 with 2 GIGS Ram. I've got the Delta 1010 selected as the default input and output in Audio MIDI setup, using the Mac built-in output only for the System Output. None of these issues were happening with Logic 7, and I haven't changed anything since then, except for installing Logic 8 and gradual Tiger upgrades. I also seem to have no problems using the Delta 1010 with Final Cut Pro. I suppose the possibilities are: incompatibility with Logic 8 and some other software, the Delta 1010 card is going bad, an issue with other connected peripherals (USB hub, Firewire Hub, Edirol UM-550), bad ram... or something else?)

Hi,
There are two things to bear in mind here.
1) In my experience, it takes a little longer for the driver to kick in after boot up, so wait a minute before launching Logic.
2) I recently reinstalled the 10.4.10 driver on my friend's Mac (same config as yours) and it now works as it should.
Best Wishes

MAudio Delta 1010 PCI Digital Recording Rack Mount and Mac Pro

A great digital audio rack-mount converter is MAudio's Delta 1010. It uses a PCI card for which I heard one could get a replacement PCI-X interface card, but such is not available for PCI-Express slots which are all the Mac Pro workstations have.
Does anybody know of a solution? Perhaps an interface that converts PCI or PCI-X to FireWire, USB, or PCI-Express? In other words, any way at all to make use of equipment for which the manufacturer doesn't supply a Mac Pro'able interface?
(And my apologies if this is just a silly question; I'm not super hip to all the hardware stuff.)
Thanks,
Rich Apple

$2000 US Dollars for the Magma PE6R4 converter (less in Canadian Dollars, of course) would be a pretty high price to pay to save my $800 Delta 1010 audio solution...

Using multiple delta 1010s in logic

can't use multiple delta 1010s works fine using one when i select multiple on logic comes through very distorted and then slowly dies. any ideas?

I would say something like:
"In normal operation, Logic listens to all incoming MIDI ports, and sums the data together, forwards it to the arrange page, and then distributes it to the selected instrument track - hence all controllers which be channelised to control the current instrument (or multiple instruments).
If you enable "Multiplayer Record" mode, then what happens is that Logic distributes incoming MIDI events to the selected tracks via the MIDI channel.
So, you can set track 1 to listen to channel 2, track 2 with a different plugin to channel 14 etc - up to 16 channels.
So in this way, you can play up to 16 independent instruments from up to 16 independent controllers.
Logic currently has a bottleneck at the summing point, which means you lose the incoming MIDI port info, which is why your controllers need to be sending on different MIDI channels, but in short, set controller 1 to transmit on one channel, set controller two to transmit on a different MIDI channel, have multiplayer record enabled "Auto demix by channel if
multitrack recording"), and you can then choose which track should respond to which controller by adjusting the track object's MIDI channel.
The manual explains the procedure in "Recording on Multiple MIDI Tracks" on page 382."
Now sue me...

ALSA is not detecting my M-Audio Delta 1010 sound card (x86-64)

Hi
I've been searching Arch forums and googling for my problem but I can't find a suitable answer.
I installed my M-Audio Delta 1010 sound card on this PC but ALSA doesn't get it to work.
Chipset envy24 / ice1712
On dmesg I find:
$ dmesg | grep -i ice1712
[ 8.135832] snd_ice1712: probe of 0000:05:06.0 failed with error -5
However, it is listed on lsmod:
$ lsmod | grep '^snd' | column -t
snd_hda_codec_hdmi 24529 4
snd_ice1712 59590 0
snd_cs8427 6970 1 snd_ice1712
snd_i2c 4107 2 snd_ice1712,snd_cs8427
snd_ice17xx_ak4xxx 2437 1 snd_ice1712
snd_ak4xxx_adda 8070 2 snd_ice1712,snd_ice17xx_ak4xxx
snd_hda_codec_realtek 61420 1
snd_ac97_codec 113344 1 snd_ice1712
snd_mpu401_uart 5980 1 snd_ice1712
snd_hda_intel 26181 5
snd_hda_codec 98034 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6429 1 snd_hda_codec
snd_rawmidi 18800 1 snd_mpu401_uart
snd_seq_device 5269 1 snd_rawmidi
snd_pcm 75735 5 snd_ice1712,snd_ac97_codec,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7218 2 snd_pcm,snd_hda_intel
snd_timer 18935 1 snd_pcm
snd 60189 25 snd_ice1712,snd_hda_codec_realtek,snd_ac97_codec,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_i2c,snd_pcm,snd_rawmidi,snd_hda_codec,snd_ak4xxx_adda,snd_hda_intel,snd_mpu401_uart,snd_seq_device,snd_cs8427
I followed some instruction and created a alsa-base.conf file with:
$ cat /etc/modprobe.d/alsa-base.conf
options snd slots=snd_ice1712,snd_hda_intel
options snd_ice1712 index=0
options snd_hda_intel index=1
aplay -l returns:
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: SB [HDA ATI SB], device 0: ALC889 Analog [ALC889 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: SB [HDA ATI SB], device 1: ALC889 Digital [ALC889 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
Seems card 0 is reserved for the m-audio card but is not being detected by ALSA
envy24control also exits with:
$ envy24control
No ICE1712 cards found
Finally, my /dev/snd
$ ls -l /dev/snd
total 0
drwxr-xr-x 2 root root 80 Dec 7 20:25 by-path
crw-rw----+ 1 root audio 116, 7 Dec 7 20:25 controlC1
crw-rw----+ 1 root audio 116, 16 Dec 7 20:25 controlC2
crw-rw----+ 1 root audio 116, 6 Dec 7 20:25 hwC1D0
crw-rw----+ 1 root audio 116, 15 Dec 7 20:25 hwC2D0
crw-rw----+ 1 root audio 116, 14 Dec 7 20:25 hwC2D1
crw-rw----+ 1 root audio 116, 13 Dec 7 20:25 hwC2D2
crw-rw----+ 1 root audio 116, 12 Dec 7 20:25 hwC2D3
crw-rw----+ 1 root audio 116, 5 Dec 7 20:26 pcmC1D0c
crw-rw----+ 1 root audio 116, 4 Dec 7 20:26 pcmC1D0p
crw-rw----+ 1 root audio 116, 3 Dec 7 20:26 pcmC1D1p
crw-rw----+ 1 root audio 116, 2 Dec 7 20:25 pcmC1D2c
crw-rw----+ 1 root audio 116, 11 Dec 7 20:27 pcmC2D3p
crw-rw----+ 1 root audio 116, 10 Dec 7 20:26 pcmC2D7p
crw-rw----+ 1 root audio 116, 9 Dec 7 20:26 pcmC2D8p
crw-rw----+ 1 root audio 116, 8 Dec 7 20:26 pcmC2D9p
crw-rw---- 1 root audio 116, 1 Dec 7 20:25 seq
crw-rw----+ 1 root audio 116, 33 Dec 7 20:25 timer
$ ls -l /dev/snd
total 0
drwxr-xr-x 2 root root 80 Dec 7 20:25 by-path
crw-rw----+ 1 root audio 116, 7 Dec 7 20:25 controlC1
crw-rw----+ 1 root audio 116, 16 Dec 7 20:25 controlC2
crw-rw----+ 1 root audio 116, 6 Dec 7 20:25 hwC1D0
crw-rw----+ 1 root audio 116, 15 Dec 7 20:25 hwC2D0
crw-rw----+ 1 root audio 116, 14 Dec 7 20:25 hwC2D1
crw-rw----+ 1 root audio 116, 13 Dec 7 20:25 hwC2D2
crw-rw----+ 1 root audio 116, 12 Dec 7 20:25 hwC2D3
crw-rw----+ 1 root audio 116, 5 Dec 7 20:26 pcmC1D0c
crw-rw----+ 1 root audio 116, 4 Dec 7 20:26 pcmC1D0p
crw-rw----+ 1 root audio 116, 3 Dec 7 20:26 pcmC1D1p
crw-rw----+ 1 root audio 116, 2 Dec 7 20:25 pcmC1D2c
crw-rw----+ 1 root audio 116, 11 Dec 7 20:27 pcmC2D3p
crw-rw----+ 1 root audio 116, 10 Dec 7 20:26 pcmC2D7p
crw-rw----+ 1 root audio 116, 9 Dec 7 20:26 pcmC2D8p
crw-rw----+ 1 root audio 116, 8 Dec 7 20:26 pcmC2D9p
crw-rw---- 1 root audio 116, 1 Dec 7 20:25 seq
crw-rw----+ 1 root audio 116, 33 Dec 7 20:25 timer
controlC0 and pcmC0 is not present!
So, what might be causing the probe error -5?
I really need to get this card working! :S
I have Arch up to date!
Hardware specs:
CPU: AMD FX6100
Board: Gigabyte (can't recall the model) with NVidia chipset
Thank you,

I have an m-audio delta 1010lt as well, it's a great card but it sits in my closet now because I "upgraded" to a motherboard that doesn't have legacy PCI slots. However, I'm pretty sure I remember the card working for me and being "plug and play" under arch with kernel 3.3 or newer. So some things I would consider:
Try checking IRQs, make sure nothing is overlapping.
Try using the LTS kernel, to see if it is kernel related, since ice1712 module should ship with almost any kernel => 2.6.26.
How many watts is the power supply? Sometimes insufficient wattage can result in drivers failing to load.
What other sound cards do you have installed? Have you tried blacklisting all of the other cards in your system using alsa-base.conf? This is a bit extreme, but might be a useful troubleshooting measure, as some people have had issues in the past with alsa indexing mutiple cards to the same slot number

Black Lion Audio Delta 1010 mod.

well, i went away on holiday and sent my trusty old delta 1010 in to black lion audio for a pick me up. i thought i would share my preliminary impressions here with the good folk here.
first thing is; it was almost more trouble than it was worth trying to get the thing back into the country. customs incorrectly charged me VAT at the UK border, and then calculated it based on the US dollar value rather than on the converted value. so i ended up having to pay over double what i wasn't supposed to have paid at all. plus parcel force holding fees. now that's irritating.
i have not had the unit running much longer than hour so these are just very preliminary views. i have also posted a cople of cues to A/B.
well, what they said was i should notice a bit more beef in the bottom end, a little more crispness, and a wider image. and i did. to be honest, i was never really unhappy with the unit anyway, having had opportunities to compare how it went against HD rigs, MOTU, and nyquist converters and so forth. and i never really felt i was missing much. at the end of the day i am more interested in the music than i am in the technology. but i had recommended black lion as a possiblity to so many MOTU users who were dissatisfied i thought i ought to put my money where my mouth was.
so i was inclined to be skeptical, but i think for those for whom sound is really important, this has got to be a route well worth looking at. the cue i have posted is a rough draft that i quite like, and it is quite rough - but it does have elements that demonstrate the difference between before and after quite well. i am not sure how exactly i have managed to match the settings from the first version to the second, but you can hear a much more in phase bass, and a little extra sparkle in the high end.
certainly just playing back stuff recorded on the un-modified unit sounded a touch better, but i think i am going to enjoy not having to work quite so hard to clean up lower-midrange murk when it comes to mixing on the modified unit. i mix out the box so i should find a benefit going both ways.
so do i feel it was worthwhile personally? maybe. i am not overwhelmed but then i was not really that unhappy. i did feel from time to time that icould hear how the 1010's sound could be imporved, which was why i thought it might be worth a shot. and i plan to stick with the current setup for some time before making a really big change, so in the meantime i think i have given my setup a little leg-up in quality.
the cues to A/B can be found at:
www.stevenson.homechoice.co.uk/documents/
they are 'ye shanghai 2', old and new.

hi, Rohan,
by now, after a few days of testing, how are the BL mods?
as you are aware, this is just part of the story on the quest for a better sound.
you should hear more detail at a given SPL.
the "quicker" electronics should allow much more critical mid range detail to be heard. for instance, two different clarinet patches playing closely together should now have more detail and separate characteristics.
the troublesome 150-500cps area should be less troublesome and require less eq'ing. the fatiguing 1k - 5k area should be smoother and respond to adjustments more accurately with less eq applied.
also, any faults in your sample libs should be more apparent.
these mods would come into their own more if you do a lot of live recordings with real players.
- sample libs mixed up will be more noticable as the original ambiences will be more apparent. what you thought blended well might not be blending as well now.
anyway, maybe it's time to start earballing some new monitors. these are the most important element, except, maybe the room itself.
all the best, and look forward to less ear fatigue. david r.

Get rid babylon and delta search, uninstall wont work because it doesn't show up, please help

I want to keep my firefox but have caught this babylon and delta search and no matter what i do it will not go

Remove Babylon Features:
Remove Toolbar (from Extensions)
1. Open Mozilla Firefox. Go to FF menu button.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Remove/Disable the Babylon Toolbar 1.5.0.
4. Restart your browser.
Remove Toolbar (from Add/Remove Programs)
1. Click the Start button on your computer.
2. Select Add-ons & than select Extensions. (delete excess text)
3. Select Programs and Features.
4. Select Babylon Toolbar from the Programs list.
5. Right click to uninstall.
6. Press YES on the popup message.
Remove Search Provider
1. Open Mozilla Firefox. Click on the Search bar, located on the right side of your address bar
2. Press the F4 key and select Manage Search Engines from the drop down list that appears.
3. Select Search the Web (Babylon) and click on the Remove button.
4. Click OK to save your changes.
Remove/Change Home Page:
5. Open Mozilla Firefox. Click on the FF menu button.
6. Select Options.
7. Now select the General tab.
8. In the section of the popup labeled "Home Page," insert the URL of your desired Home Page.
9. Click OK to save the changes.
Remove Babylon Search from New Tab
If when you open a new tab in Firefox, Babylon Search still appears:
1. Type in the address bar line about:config and press enter.
2. Confirm the popup message.
3. In the search field, type "browser.search.selectedEngine". (remove excess text here)
5. Restart your Browser.

No initial load of Customers, Material and delta load of Sales Orders.

Hi Experts,
I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
- Customer_main load, it was succesful, but no BP's of R/3 are available.
- Material, it failed in SMW01, SMQ2, the errors are:
Mat. for Initial Download: Function table not supported
EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
Plant xx is not assigned to a business partner
- Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
Thanks,
-Pat

Hi Ashvin,
The error messages in SMW01 for MAterial initial load is :
     Mat. for Initial Download: Function table not supported
     EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
     EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
     Plant 21 is not assigned to a business partner
I have done the DNL_PLANT load successfully. Why then the plant error?
Some of the messages for BP:
Messages for business partner 1331:
No classification is assigned to business partner 1331
For another,
     Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
     City Atlanta does not exist in country US
     Time zone EST_NA does not exist
     You are not allowed to enter a tax jurisdiction code for country US
     Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
Till these 2 are not solved, I cannot go into the Sales order loads.
Any ideas will be greatly appreciated.
Thanks,
-Pat

Full and delta Data loads in SAP BI 7.0

Hi,
Kindly explain me the difference between full and delta data loads in cube and DSO.
When do we select change log or active table(with or without archive) with full/delta in DTP for DSO.
Please explain the differences in data load for above different combinations.
With thanks and regards,
Mukul

Please search the forums. This topic has already been discussed a lot of times.

Middleware: BDoc to IDoc conversion - init and delta

Hi,
First of all let me just say, that I know nothing about CRM (I'm an XI guy), but need to investigate on a matter, so please take that into accound when reading this post and responding to it.
Scenario:
Business Partners, Business Transaction Messages (orders and activities) need to be replicated to an external system. This is achieved by converting BDocs for the respective messages into IDocs via CRM Middleware and then sending IDoc to XI which in turn posts data to external database. This process should function both INIT and DELTA.
So far so good.
The problem is when having created for instance a new direct order and saved it. The BDoc is generated and converted to IDoc (CRMXIF_ORDER_SAVE02). In the fields OBJECT_TASK in the IDoc I get the expected 'I' for INSERT. This is what I expect.
Now, if I make a change to the order and saves it again the generated IDoc still contains just an 'I' for INSERT in the before mentioned fields. This is not to be expected - should be an 'U' for UPDATE, but this does not happen.
Anybody have any ideas why this happens and what is wrong?
Best Regards,
Daniel

Hi,
Thanks for your answer. I'm on CRM 5.0. The note you mentioned seems not to be related to my problem. My question is regarding "download" of data from CRM to XI through CRM middleware. When trying to do this the "change pointers" (fields OBJECT_TASK and/or TASK) are not set correctly in the IDoc's generated by middleware (everything is writtens INSERTs), which means I cannot from XI determine by the data received if I'm to perform an update/insert/delete into the database.
Best regards,
Daniel

Basic Question on Copy and Delta link which one to use when?

Hi
Its basic question
My understanding about copy and Delta link is
Copy doesnot ahve direct relationship with source object (but it acts as a sibling) any changes done to spurce object does not affect target object.
Where as Delta link will have a parent child relation ship between source object bacially its a copy of source and inherits id properties. in case if i change source object does this affect target object, we can delete, add content to delta link target object.
let's say if i want to use standard quickpoll iView do i need to use copy or delta link similarly for other iviews, worksets, roles which one will be better.
Regards,
Murali

Murali,
Yes, your understanding is right.
Case 1 : Copy
A- Object
B- Copy of A
Both of them are independent.Any changes in A are not dependent on B and vice versa.
Case 2 : Delta Link
A - Object
B - Copy of A (via Delta link)
Any changes to A are reflected in B, as A is a parent and B a child.
But B would be an independent entity.Any changes to B would not effect A.
When you use either of them, depends on your need. When you are working with standard iviews or roles or workset, you can do a copy of the original, because in most cases we would not make changes to the standard roles or worksets or iviews. There by eliminating the process of making a delta copy.
But, if you are dealing with the roles that you have created and want to make a copy of it, you can use a delta link, because, even if you want to add more iviews and worksets to that role, they would get reflected when you make a delta copy.
Hope that helps.
Consider rewarding points for handy posts!
Cheers,
Sandeep Tudumu
Edited by: Sandeep Tudumu on May 6, 2008 2:10 AM

Error in Full and Delta CPACache refresh.

Hi Experts,
In our production environent we have a SOAP -> XI - > PROXY scenario [Synchronous].
The Consumer of the WebService has reported an error:
500_Internal_Server_Error = SOAP:Server_Server_Error_XIAdapter_ADAPTER.JAVA_EXC
When I checked there are no messages in SXMB_MONI , but when I checked the Cache Refresh History I found that
there was error in both Full and Delta Cache Refresh. But the restart of the XI(Production) server resolved the issue.
The error is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.pxi.su0956</EngineName>
<RefreshMode>F</RefreshMode>
- <GlobalError>
<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>
org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:157) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code)) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:56) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:871) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:640) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.process(CacheRefresh.java:104) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Can anyone tell me what is the cause of this error and how restart of the XI server resolved the issue?
Thannks,

Guys,
I have deployed the below components and after this repository could not be started which gives the below error.
1000.7.11.10.18.20130529165100
SAP AG
sap.com
SAP_XIAF
1000.7.11.10.11.20130529165100
SAP AG
sap.com
SAP_XIESR
1000.7.11.10.15.20130529165100
SAP AG
sap.com
SAP_XITOOL
We have the same issue. Still the Restart did not solve ths issue.
Can anybody help? We are not able to start the XI Repository.
Our PI components are as below
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR
CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:
        com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm
l|CacheRefreshMDB^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M
1000.7.11.10.6.20121015232500
SAP AG
sap.com
MESSAGING
Regards
Omkar

Setup table and delta mechanisim

Hi,
Can anyone explain in detail setup table concept in LO extraction and
Delta mechanisim?
Sridhar

Hi
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
1. Data Flow
Relevant T-Codes
a) Initializtion
LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application -> Delete/Fill Setup(reconstructing) Table content
RSA3: Check content of setup table
b) Delta upload
SM13: Display update table/Extraction Queue content
RSA7: Display Delta Queue content
Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

Delta get once and delta request wise?

hi friends,
what scenerio we use delta get once and delta by request at DTP in BI 7.0? i studied many threads, i didnt understand , get delta once some snapshot like? what is the meaning?
can u give me any example , its great?
regards
ss

Indicator: Only Get Delta Once
Source requests of a DTP for which this indicator is set are only transferred once, even if the DTP request is deleted in the target.
Use
If this indicator is set for a delta DTP, a snapshot scenario is built.
A scenario of this type may be required if you always want an InfoProvider to contain the most up-to-date dataset for a query but the DataSource on which it is based cannot deliver a delta (new, changed or deleted data records) for technical reasons. For this type of DataSource, the current dataset for the required selection can only be transferred using a 'full update'.
In this case, a DataStore object cannot usually be used to determine the missing delta information (overwrite and creation of delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this indicator and perform a snapshot scenario. Only the most up-to-date request for the DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again during the DTP delta process. When the system determines the delta when a new DTP is generated, these earlier (source) requests are seen as 'already fetched'.
Setting this indicator ensures that the content of the InfoProvider is an exact representation of the source data.
Dependencies
Requests that need to be fetched appear with this indicator in the where-used list of the PSA request, even is they have been deleted. Instead of a traffic light you have a delete indicator.
Get Data by Request
This indicator belongs to a DTP that gets data from a DataSource or InfoPackage in delta mode.
Use
If you set this indicator, a DTP request only gets data from an individual request in the source.
This is necessary, for example, if the dataset in the source is too large to be transferred to the target in a single request.
Dependencies
If you set this indicator, note that there is a risk of a backlog: If the source receives new requests faster than the DTP can fetch them, the amount of source requests to be transferred will increase steadily.
Source : https://forums.sdn.sap.com/click.jspa?searchID=5462958&messageID=3895665
Re: Diff between Only Get Delts Once and Get Data by Request
Check this blog as well : /people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148

How to do delta detection and delta creation

Hi
i am new to OWB , please help me in
how to do delta detection and delta creation using OWB
Thanks

Hi Bassem,
for delta detection in your data source there are three possibilities:
1. the source data has some identifier when it has been modified and deleted data is marked an not physically deleted
In this case you just filter the data that has been changed in your owb mappings.
2. you use some change data capture technologies
You have to install this manually when using owb 11.1 or older versions (google for oracle and cdc). owb 11R2 brings built in support for change data capture.
3. you get all the data and identify the delta manually
In the owb mapping you left outer join the data from your source with the existing data in your target and filter for the data that is new or has been modified. In a second step you identify the deleted data by selecting the data in your target minus the data from your source.
Which approach is the best depends on your specific system architecture.
Regards,
Carsten.

AA3 and Delta 1010

Similar Messages

Maybe you are looking for