Question:
Hi All,
Our version is 3.0(B). Our process chain contained 7 parallel loading jobs. One job failed and in the step-by-step analysis, under system response we find "Caller 70" is missing error. Also, this is just for your info that all the other jobs are of less than 1million records and the job that failed is of 1.3 millon records and that too only the first package of this job containing 498765 failed. Rest of the packages are of nearly 215000 records.
What does this mean?
Thanks in advance..
- Gary
Also, I am not sure whether I can upload the failed packet from PSA, as the packet already arrived in PSA as per the PSA node status in the monitor details section. The deatils section nodes say that the transfer rules failed. Is there a way I can know which record(s) of the package caused failure in transfer rules? Also, as per my knowledge we dot have any transfer rules defined.
Our Data flow structure is
-------------------------------
Generic DataSource ->InfoSource->ODS->InfoCube
Here are the important nodes from the monitor details section:
********
under extraction node there is red on one packet. 498765 records sent (498765 records recieved)
under Transfer (Idocs and TRFC) node there is red on one packet.
Data Package 1: arrived in BW; Processing: Data Packet not yet processed
under Processing(data packet) node, there is read on one package.
Data Package 1(498765): Errors occured
- After expanding this node, the status of several nodes is as below:
*(Green)Update PSA( 498765 records posted )
- 498765 records written in PSA_ZBWAP
*(RED)Transper rules( 498765 records ): Errors occured
- (Green) Transaction Data Received. Processing being started.
- (Yelloe with a Circle) Message missing. Transfer rules finished
-(Yelloe with a Circle) Update rules(0 records). Missing Messages
-(Yelloe with a Circle) Update rules(0 new/ 0 changed). Missing Messages
-(Yelloe with a Circle) Processing End: Missing Messages
********
Thanks in advance.
- Gary
Answer:
Hello,
did you find a solution to this problem? I have same problem for all cubes created.
Is it possible that this is a installation problem ?
Regards, Inma
Answer:
Hi Inna,
No solution yet. Still looking for a solution.
- Gary
Answer:
There are plenty of posts about good old caller 70. There has been no definite response though.
We had multiple processes in the chains and some customised extractors. We are on 3.0b and have not had problem for some time. To get around problem we removed some of the parellel processing and lengthened the chain.
Also removed some of the customised extractors to run on there own. This seems to have resolved the issue for us. Hope it helps.
Answer:
Hello,
we have this problem fixed yet, I know that adding to table TSORA the following entries:
PSAPDSX PSAPDSX
PSAPDSX620 PSAPDSX620
PSAPDSXDIM PSAPDSXDIM
PSAPDSXFACT PSAPDSXFACT
PSAPDSXODS PSAPDSXODS
PSAPDSXUSR PSAPDSXUSR
the problem is fixed, we have reported this problem to SAP, and this is the solution they gave us. I don't event know if any user can do this. It seems that it is a problem with database and tablespaces.
Hope this helps, Inma
Answer:
Had the same problem this weekend (*grrrr*). But the entries were there already in TSORA...
And it seems that I cannot update / rewrite the faulty records via the monitor.
Used PSA only (everything okay) updating the cube with this I got the "caller 70" (with short dump DBIF_RSQL_SQL_ERROR, Exception CX_SY_OPEN_SQL_DB) and want to update the cube manually but this doesn't work. As only 40,000 of above 1,500,000 are faulty I don't want to request the whole data again...
_________________
Juergen Limbach
Answer:
Hi Folks
We have the same error called CALLER 70 but the fixes discussed in the forum I guess all are Oracle related, we are on DB2 390 and with the patch 12. Any one has expeienced the same CALLER 70 erro on DB2 environment and is there any fix???
Any help is highly appreciated.
Thanks
guest
Answer:
when u had dump did u check on the Source system side. If the source system has Sql db error then u might try loading the info cube with dropping the index that way the load goes well.
Try it out.
thanks
Bw1
Answer:
Hi,
Please refer to SAP NOTE 631668.
regards