01-11-2016 5:42 AM
Hi Gurus,
While posting J1IIN continuous for say N number of invoices, We get an error as such:
"SQL error 60 when accessing table "NRIV"."
What happened?
Error Text of the Database: "ORA-00060: deadlock detected while waiting for
resource"
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in procedure "READ_NRIV" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Error Text of the Database: "ORA-00060: deadlock detected while waiting for
resource"
This error is noted if J1IIN is (Excise invoice) is created continuously or Even if Triggered thru' BDC.
Requesting your suggestions in resolving the error
PS: Buffering in the Excise invoices number ranges is strictly not advised as it has Legal Implications
Thanks in advance
Regards,
Abhishek.U
01-11-2016 9:39 AM
The issue is not related to SAP but because of some oracle issue. You need to discuss with your Basis team on this and couple of OSS notes are there like 84348, 1023278 etc., and your Basis team can certainly have a look at these notes.
Meanwhile, if your issue is specifically related to bulk generation of excise invoices, why don't you try with J1I3 ?
G. Lakshmipathi
01-11-2016 9:25 AM
01-11-2016 9:39 AM
The issue is not related to SAP but because of some oracle issue. You need to discuss with your Basis team on this and couple of OSS notes are there like 84348, 1023278 etc., and your Basis team can certainly have a look at these notes.
Meanwhile, if your issue is specifically related to bulk generation of excise invoices, why don't you try with J1I3 ?
G. Lakshmipathi
01-20-2016 11:56 AM
Lakshmipathi sir,
In our business scenario, we have made changes such that we have written an exit to restrict the invoices to be posted only after updating the LR number;
At the time of posting the documents thru' program in the back, we were getting this deadlock error.
We have now found a workaround by posting the documents one by one in the background thru' program
Regards,
Abhishek U