Problem with initialization Delta queue

Hi Gurus,
I have problem with initialization of delta queue when I try load transaction data from R3 (FM) to BI.
Error message: Deviation of (64 seconds) between qRFC counter (000012365466830000080000) and actual time (08.03.2009 21:10:19).
I have no idea where is the problem because this problem occurs only in PRD systems. In DEV and QUA system everything is OK.
System BI: BI 7.0
Source system: ECC 6.0
Thank you for all answers!
mp

Hi,
Replicate the DS in BW Prod and then Activate Transfer rules and then try.
First you delete the DElta quae in RSA7 for the particular datasource in the R/3
source system then you try to intialize, here you are trying to intialize datasource with
same selection conditons . thats why it is giving shortdump
Check
Business Content and Extractors
Thanks
Reddy

Similar Messages

Problem to initialize delta queue of datasource from CRM 7.0.

Hi all,
I've some problem to initialize delta queue of datasource from CRM 7.0. After initialize the Init in BW, the delta queue was created but after the user changed data, this changed didn't populated into delta queue.
I tried the steps below but without any success. Anybody know how can I correct this issue?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
these queues.
In Transaction SMQ1 if there are Queues existing with
names beginning with CRM_BWAn (n is number) then
activate these queues in the same transaction.
4.a)If required activate the datasource
Go to transaction BWA5 > select the required datasource and
activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
Go to transaction RSA1 > modeling > infosources > select the
infosource > right mouse click on the selected
infosource > choose option replicate datasource
Activate the infosource.
6. Go to the scheduler for the infosource > select delta in the
update >choose the option PSA only (in the Processing tab)

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

Kingston, Crucial, Twinmos memory has problem with K7N2-DELTA??

I need 2*256MB memory for my AMD 2500+XP.
Kingston, Crucial, Twinmos memory seem to have problem with K7N2-DELTA-ILSR
Is Samsung good?
Please do me a favor to choose one brand that fit my mobo in this link:
http://www.canadacomputers.com/memory.html
I tried KingMax(SuperRam Series, since they don't have the ram with the model listed in the test report) and Corsair(CMX256A-3200C2) ,both no good for 2*256MB DUAL channel
Thank you very much

I think OCZ and Samsung, is mostly work memory,r ight?
thx
I think I will try OCZ

Problem in initialization delta load

Hi All,
I am facing a problem while doing an initialization delta from one ODS obj to another.
Error says "data is not been updated in PSA table"
The ODS object I am trying to load is getting data from 3 ods below ODS obj, out of 3ODS's 2 were successfully loaded.
While doing this particular load it's coming with the same error. I tried full load also, but results are same.
Can anyone have some answers?
Regards,
Kironmoy

Hi,
In first init the data will move from the active data table to further data target then we will run delta at that tome the dat will go from change log table to further datatarget in our case u rrunning init but there is no daa in active data table so it is happening
here two options are there
1)either u can delete the change log table data and reload the data once again and do INIT with data transfer for further data target then it goes for next onwords delta data will come from change log table.
2)otherwise u go for INIT WITH OUT DATATRANSFER now no records will come to ur targeted datatarget just it gives delta flexibility only (by default 1 record willl come it is for delta initilization) now u go for the delta. now which are the records are avilable in change log those records will move from changelog to ur targeted datatarget.
Thanks
sathish

Problem with subsequent deltas after converting Full requests to Repair.

Hi All,
We are working on changing an existing system from loading from multiple extractors directly to a cube to loading each extractor to its own DSO and then combining the data in a 'consolidated' DSO and then on the the cube.
To avoid downtime in the production system when we do the cut-over we have decided to do full loads of historical data up to Sept 2007 and then do delta loading from then on.
So the steps so far have been:
1) Full load of data to low-level DSO's. to 09 2007.
2) Full load of data to 'consolidated' DSO.
3) Convert Full requests in consolidated DSO to Repair Full Requests (see SAP Note 689964).
4) Initialise Without Data Transfer to the 'consolidated' DSO.
5) Delta Initialise from 10 2007 from the source system to the low-level DSO's.
6) Delta from low-level DSO to consolidated DSO.
My problem is with step 6 - no records are loaded into the consolidated DSO after delta load of data to the low-level DSO - the load process runs correctly but tells me that there was no data available.
Can anybody see if there is a problem with my approach - I thought this was the correct way to convert from full loading to delta loading ?
A Merry Christmas and a Happy New Year to you all
Graham

Hi Siva,
Thanks for the reply.
I understand that there is only an active table with a write-optimised DSO - but delta processing should still be possible at the request level
(SAP Help on Write-Optimized DataStore Objects http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm)
Since write-optimized DataStore objects do not have a change log, the system does not create delta (in the sense of a before image and an after image). When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted.
In my case the 'new' request loaded into the DSO have not been loaded into the connected InfoProvider, so it should be processed.
Regards
Graham

Problem with masterdata delta update

Hi,
Iam facing problem with 0material (masterdata) delta problem i.e. I have already uploaded all the transaction and master data of a infocube. To day when Iam checking all the others working properly but only 0material master data (attrbutes and text) is not scheduling, when Iam trying to schedule it is giving the message like
<b>The last delta update was incorrect !
Therefore, no new delta update is possible.
You can cancel the request or:
Attempt to load the data of the last delta update again</b>
Could you pls tell me how to solve this.
Waiting for ur reply.
Thanks and Regards,
Girikumar.

Hi,
After your last failed Delta Request, where is the request ? is it in the Request Tab ? or is it in the Reconstruct Tab ?
Just make sure that the request was marked as "RED". If it is so, then the next Delta should be a REPEAT Delta.
Thats it will re load the request again.
You can delete the request from the REQUESTS tab and put it in the RECONTRUCT Tab. And then attempt a load.
Hope it helps,
Pradip Parmar.

Problem with K7N2 delta

Im having a problem with the K7N2 Delta. It was working just fine and i went into my Bios and saw that my FSB was only running at 133mgz. So i turnt it up to 200mgz. Now the darn think hangs and wont turn on. I tried to clear the Cmos and set the bus jumper to safe mode but then the computer just beeps. I dont understand what i did wrong. Any suggestions?
CPU- Xp2400+
Mobo- K7n2 Delta
Ram- 256 Atlas Percision 256 Kingston
Veido- Geforce FX 5700 Ultra
Hd- 4 gig western Digital / 20 gig western digital 7200rpm
power-300watt

well you o/c it about 50 percent and it will not have it
put j10 jumkper in safe mode
boot and put it back to 133
then shut down and put it in user mode

Problems with K7N2 Delta-L

Hi, I am new here, so hello :D
Well, I've just bought a MSI K7N2 Delta-L, beautifull board, with 2 x 256MB DDR400...
My actual PC, so:
MSI K7N2 Delta-L
Athlon XP 1700+ 1.5v DLT3C JIUHB
Thermaltake Volcano 7+
2 x 256MB PC3200 VM
Well, I updated bios to the last one (5.4) and all is running ok... but I have some problems.
1) I have problems when I try to overclock. One ot them, is that when I change a multiplier, o up the fsb... I must change jumpers, etc. etc. coz pc doesnt boot ... but later when I played with jumpers, it boot at speed that I wanted, like 10x200, etc. I dont know how to explain this problem! :(
2) Well, another problem is with "By H/W" option in vCore and Multiplier. When I select this option, the vCore sometimes go to 1.8v ... and when I select 1.8v, if it wants, its go to 1.6v in win... I dont know what to do, bios do what he wants.
3) Well, the last and I think most important problem, is when I try to change CAS Latency. I have 2.5-3-3-7 DDR400 memory. When I try to change CAS Latency to 2, in bios, its all right, it's boots, and figures CAS 2. But when I enter windows, ALL programs, says that CAS Latency is 2.5 !!! I tried lowering FSB to 133, and trying again CAS 2, but nothing, still CAS2.5 in win. I runned benchmarks, but no perfomance gaining with BIOS CAS2. What happens!!?? Another thing, was that if I put in BIOS, AUTO, when I chane FSB to 233, CAS Latency goes to 3, when I put FSB to 200, CAS Latency goes to 2.5, when I put FSB to 166, CAS Latency remains in 2.5, when I put FSB to 133, IT STILL BEEING in 2.5 .. !! It doesnt change... the same in FSB 100.
HELP!!! and thanks a lot :(
PD: Same problems with all bios.

Quote
Originally posted by Dancer
Quote
Originally posted by lmichani
Another problem, expanding problem "3)"
In bios, I go to multiplier option, I select 9.5.
In FSB, 200.
Then, in vCore, I select by H/W...
Save... ---> ... WOHOO !! 2200 MHz!
WHY !!?? (200 x 11 says in win) ... SSHHIITT!
- Another problem... when I select by H/W in vCore... it goes to 1.8v!!!!
IS GOING ON WITH MY BOARD? Is the crappy bios?!
Bump all you want, with this kind of language I don't think you're going to get an answer. :O Read the rules of the forum!
I didnt know that "SSHHIITT" and ":censored:" were "bad words"; btw I deleted them.
next time say me that by PM.

Odd USB Problem With K7N2 Delta-L

Hey all. I have a bit of a weird problem here I'm wondering if people can give some insight on. I have a K7N2 Delta-L mainboard that I've been using for two years now without the slightest problem. However, recently I've started experiencing some odd USB related problems which culminated in a big moment of panic for me yesterday. I'll start with what happened yesterday.
My system drive is 2x40GB PIDE drives running on an add-in Promise FastTrak133 controller. Yesterday, I was given 2x160GB drives from a client that I decided to upgrade my RAID with. I installed the drives and fired up my system, but had to reboot several times as the drives weren't jumpered right and not detecting on the Promise board. After I finally got the drives working, I noticed my USB had completely died. My USB keyboard and mouse didn't work and my TrueImage rescue disk (which I was going to use to restore my backup to the new RAID with) couldn't see the USB hard disk which contained the backup. I panicked about this for a while, but eventually managed to restore the keyboard and USB drive by unplugging the system, pulling the battery, waiting 15 minutes, putting the battery back and starting up. My mouse still didn't work, but once I got into Windows, it started to work after unplugging it and replugging it three times. All these devices work immediately when plugged into my laptop so I know they are OK.
Also, for the last few months leading up to yesterday, I've been having a problem with some USB devices not detecting properly when I startup. For example, the mouse will not respond until I either replug it (sometimes more than once) or on some occasions, just mash the buttons a few times at which point it kicks in. I also find that sometimes if I switch the keyset on my Zboard (which resets its USB connection), sometimes it won't get recognized as attached to the system unless I disconnect it or reboot. Both of these devices work perfectly in other systems I've tried them on and once I get them running in Windows, they don't kick out again unless the system is shut down (and they only fail to work on some boots, not all.) Every other aspect of the system works flawlessly.
I was wondering, has anyone else seen this before and is it something I can correct? Is this a sign that possibly the board is starting to die and I should look at upgrading? If I install an add-in USB card and disable the on-board USB, will I still be able to boot from USB devices? I cannot really afford a major upgrade right now, but I also can't afford to lose this system so I'll make the investment if this is a potential sign the board is failing. Thanks for reading and any help you can provide.
P.S. Here is a list of USB devices connected to my system, all of which I've tried disconnecting without fixing the problem:
Razer Copperhead Gaming Mouse (Latest Drivers & Firmware)
Ideazon Zboard (Latest Drivers)
Artec e48U+ Scanner (Latest Drivers, Powered By USB)
iMex USB 2.0 External HDD Enclosure
HP Photosmart 7600 Photo Printer (Runs Through Zboard USB Hub)

the PSU looks fine and should be capable of providing more than enough power - unless it is faulty for some reason. is it clogged up with dust? do you have another one you can test with?
does your case have its own USB port(s), if so disconnect from motherboard and see if that makes any difference
also, try going to Device Manager, uninstalling all the Host Controllers listed under Universal Serial Bus controllers, and then rebooting to reinstall the drivers
i presume you have already referred to this sticky topic: If you are having problems with USB ports, read this topic.

Serius problem with k7n2 delta 2

I have problems with my k7n2 delta2 does not recognize a AtlonXP 3000+ was working in this plate, doing tests of overclock,when to restart do not work the processor in this plate but,the motherboard (k7n2 delta 2) works with other processors, and processor 3000+ works with other motherboards, but Athlon 3000+ with k7n2 delta 2 does not work together, I tested of everything recover the bios, to update the bios and nothing, dont change to default, I hope that can help me beforehand thankful.
tengo problemas con mi k7n2 delta2 no reconoce un AtlonXP 3000+ que ya estaba trabajando en esta placa madre, haciendo pruebas de overclock, y despues de reiniciarla ya no quiso reconocer el procesador athlon xp 3000+, la placa madre (k7n2 delta 2) trabaja con otros procesadores, y el procesador 3000+ trabaja con otras placas madres, pero el Athlon 3000+ con k7n2 delta 2 no trabajan juntos, ya he probado de todo restaurar el bios, actualizar el bios y nada, parece que no efectua los cambios a default, no se que hacer, espero que me puedan ayudar agradecido de antemano.
cuando tiene otro cpu enciende correctamente pero cuando le pongo el xp 3000+ no enciende el monitor ni marca ningun error solo no inicias, pero si enciende.

Why do you say Bios doesn't go to default options if with other CPUs Mobo turns on ? You must have in mind that each time you replace the CPU you must Clear CMOS to return to default options, and also you should clean HSF base and CPU die from old thermal grease. At least you know both CPU and Mobo works.
Por qué dices que la Bios no vuelve a las opciones por defecto si la tarjeta madre funciona con otros procesadores ? Debes tener en cuenta que cada vez que cambias de CPU deberías borrar las opciones que entraste en la Bios como también limpiar la base del disipador de temperatura de la CPU y la CPU misma y usar nueva pasta térmica. Al menos sabes que tanto la CPU como la tarjeta madre trabajan.

Problems with K7N2 Delta @ FSB200Mhz

Hi,
SORRY FOR MY POOR ENGLISCH
I've got a problem with my K7N2 Delta -L Board.
I use a Athlon XP Palo 1700+. Standart for this proz is FSB 133 and multi 11.
Now i tried to use FSB 200 an multi 7,5. =>1500Mhz.
I works fine an never crashs.
BUT if i turn off the pc for more than 15mins it doesn't reboot anymore. Only a safereboot@100mhz is possible.
The setting have to be in the BIOS advanced chipset AUTO an FSB 200 than it boots and restarts without problems until i turn it off.
The setting MANUAL and FSB 200 doesn't work even if i don't change any other setting. It never boots
RAM : CPU is 1:1. RAM is 400Mhz
What's wrong?

Yes, the Proz is unlocked. It works fine. The "strange" thing is, that after a shutdown and power-off of more then 15min it hangs while rebooting.
You have to choose auto performance and FSB 200 otherwise it does't works with FSB higher than 150
Why raise the v-core? It works fiin without probs and stable only boot-probs after power-off . Reboots works fine.
The same proble occurs while using FSB 166.
What has MSI done?
Auto FSB200 works
Manual FSB 200 not
and the aren't able to reply to e-mails...
Sorry next time spend some more € for an working a*us MB

R/3 Patch Upgrde Problem due BW Delta Queue.

Hi Expert,
I have extracted all the logistic & delta data in BW to make delta queue emplty. My query is that ,should it delete these queue in RSA7 or it should disappear after extraction.
In LBWQ there are only two entry MCEX17 & MCEX17_1 , these queue are still there after extraction.what to do these queue ?
These queues are giving error while upgrading patch.
2LIS_13_VDITM
2LIS_13_VDHDR
2LIS_11_VDITM
2LIS_11_VDHDR
2LIS_17_IONOTIF
Regards,
Anand Mehrotra.

Hello Anand ,
There is no need to delete the queues for the upgrade, you only need to make sure that there is no data in these queues in rsa7 that need to be extracted, if you run the relevant infopackage twice on the BW side then it should clear the data from RSA7 , before doing this please make sure that all data has been updated from lbwq to rsa7 (if using queued delta) and that there is no data in sm13 for the queues. In RSA7 you can double click on the Individual queues and if you check under delta and delta repeat option for these logistics queues you should find 0 records.
Best Regards,
Des

Problems with K7N2 DELTA 2 LSR and reader LG 52X max

My computer has one mainboard MSI K7N2 DELTA2 LSR. updates the bios to version 11.4 but asi when even inserted a CD the coputador sticks my D-ROM is a LG 52X MAX. that can help me.
I am Chilean for that reason my English is not very good.

what it happens to me is that it is congealed, but when extracting the CD defrosts by ningun reason sticks. when it updates the bios to the B4. I work in the beginning well but despues I reiterate the problem that could now be I put my computer in my signature
the reason to update the bios ones was the problem with the cd player
lo que me sucede es que se congela, pero al extraer el cd se descongela por ningun motivo se pega.
cuando actualice la bios a la B4. al principio funciono bien pero despues se reitero el problema. que podrá ser. ahora puse mi computador en mi firma.
la razon para actualizar la bios era el problema con el lector de cd

Graphic problems with k7n2 delta

I am having some problems with this motherboard. First, the booting, that doesn't work all the time. But the main problems happens with the graphics: the wallpapers doesn't show properly and some problems with the games also happen. Is it because of my graphic card (radeon) in conflict with the nvidia chipset?

wrong section, you need the 'AMD nVidia/AMD/SiS SocketA based board' section.
Hopefull a kind moderator will move your post

Problem with K7N2 Delta-ILSR, please help

First off, these are the specs for the computer to which I shall be referring in this post:
K7N2 Delta-ILSR
AMD 2700+
1x512MB PC3200 Memory Corsair CM64SD512
Seagate Barracuda 80GB 7200RPM SATA ST380013AS
ATI 9600 Pro
400 Watt power supply
Cendyne 52x cd burner
Here's what happened. I installed everything with only minor difficulties, mostly due to getting the hard drive to work. They were worked through with little problem due, in large part, to this forum. I installed Windows XP, and we ran a number of things with no problem after the OS installation. The drivers for the video card loaded well. 3DMark2003 ran beautifully. After I got that working, I went to put my friend's old hard drive in as a slave, so he could get the files off of it. This seemed to work well enough. Then we went to load the drivers for the motherboard. When it got to the audio driver, we got the old "blue screen". Then the computer reset and tried booting 98 from the old hard drive. We shut down and disconnected the old hard drive. Then we restarted to find that after the second screen XP would not begin to boot. After some playing around we decided it best to reinstall, because with no combination could we get the OS to boot up. So we reinstalled, with a full format. This time, the first thing I went for was the motherboard drivers. It stopped at the audio driver, again, and gave us the old "blue screen", again. This time, instead of stopping the boot after the second screen, it came up with this message
Windows could not start because the following file is missing or corrupt:
\system32\hal.dll.
Please re-install a copy of the above file.
Any suggestions would be greatly appreciated before we decide what to do next. Please let me know if any more information is required. None of the bios settings have been altered, save to boot from the CD.
Thank you,
M.Cordier

i would test ram
http://www.memtest86.com
and go to drive makers site and get their testing utility
other possibility is a crap psu like them qtecs

Problem with initialization Delta queue

Similar Messages

Maybe you are looking for