Skip to main content
Solved

Oracle 'Bad Depth Indicator' error in IFS10

M
Do Gooder (Customer)
Forum|alt.badge.img+4

Hi,

We have started getting an Oracle ‘Bad depth indicator’ error when calling ‘Error_Sys.Record_General’ function from a custom event.

 

We have reported this to IFS support who in turn have raised this with Oracle support. Please see the long response from them below. In short they have concluded that it is intermittent and that they don’t know how to re create it. They have given us a workaround which is to re compile the affected packages.

 

Has anyone else seen this error?

“

This was the full error stack we extracted when you were getting the error within purchase order lines. 

ORA-64610: bad depth indicator
ORA-06512: at line 16
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2186
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2304
ORA-06512: at "IFSAPP.ERROR_SYS", line 128
ORA-06512: at "SYS.UTL_CALL_STACK", line 99
ORA-06512: at "IFSAPP.ERROR_SYS", line 113
ORA-06512: at "IFSAPP.ERROR_SYS", line 119
ORA-06512: at "IFSAPP.ERROR_SYS", line 337
ORA-06512: at line 3
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2300
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2309
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2159
ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2192
ORA-06512: at "IFSAPP.EVENT_SYS", line 199
ORA-06512: at "IFSAPP.EVENT_SYS", line 199
ORA-06512: at "IFSAPP.PURCH_ORDER_LINE_NEW_EVI", line 10
ORA-04088: error during execution of trigger 'IFSAPP.PURCH_ORDER_LINE_NEW_EVI'
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 1415678042
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 21289
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 21493
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 17332
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 17351
ORA-06512: at "IFSAPP.PURCHASE_ORDER_LINE_PART_API", line 17362
ORA-06512: at line 10

Error_sys package (which is IFS code) uses 3 methods in Utl_Call_Stack dictionary package (which is Oracle code) namely UTL_Call_Stack.Unit_Line, UTL_Call_Stack.Subprogram & Utl_Call_Stack.Dynamic_Depth to format error texts in IFS application. ORA-64610 error is thrown when one of the above Utl_Call_Stack procedures try to access a non-existent stack position. 

As highlighted in red, the error stack shows a 10 digit number as the line number. PURCHASE_ORDER_LINE_PART_API has nearly 30000 lines of code so line number 1415678042 in the above stack shown by Oracle is incorrect. This incorrect value on line number changes when executed from a different Oracle session but it is still either a 9 or 10 digit number according to what we have seen so far. It seems that sometimes metadata related to these errors are getting saved into unreachable memory locations(Stack) in Oracle database. That seems to be the root cause for this error.

Showing this 9 or 10 digit number in error stack seems to be having some dynamic behavior. The issue seems to disappeared when the package is recreated. It seems that recreating affected IFS package is solved the issue as it recreates packages in different memory locations. Adding debug info seems to be doing this without dropping and recreating the package and that was why we suggested you to try it.

If you can see the same error for any other package or in other databases, could you please try the same step and let us know the results? And please feel free to raise if you have any questions. 
“

 

Best answer by Sandun Madola

Hi Erik  (@magnum80 ),

I have worked in a similar case which was reported to IFS. I think commenting my detail findings will be helpful. Some of the wording little bit similar to the answer you have already received. 

The “ORA-64610: bad depth indicator” error was recreated using a custom menu and “Execute online SQL” event action in one of the IFS internal environment. After around 3 hours the oracle error was unabled to recreate. It’s hard to say how the issue was resolved. The same steps were followed to recreate the issue in the different IFS internal environments. But I was unable to recreate the issue as on demand. 

First part of this reply I write summary of my investigation. Latter part of this reply I write little bit more detail.

------------------ Summary of My investigation ------------------ 

After discussing with the IFS experts who have seen this issue and with my own investigations, I can summarize the investigations to the below point. 

  • Our aim was to find a workaround without applying the oracle patch for this issue since the oracle patch introduces side effects.
  • Some scenarios the developers could be able to avoid the bad depth error by creating two custom events. The first custom event to implement the required functionality and the second custom event to post a background job to execute the first custom event. But if you wish to make a pop-up message like error message or warning then this method is not suitable. (Ex: This is not suitable for below PLSQL block)
  • Some scenarios the developers could be able to avoid the error by recompiling the affected IFS package in the database.
  • Some scenarios the developers could be able to avoid the error by dropping and re-deploying the affected IFS package in the database.  But this may revoke the granted permissions to the package and may introduce additional work.
  • Some scenarios the developers mentioned that the issue is solved without doing any additional work. (Error has disappeared without any known reason)
  • Most of the cases the developers could be able to avoid the error by adding the debug information to the affected IFS package in the database. This is the suggested solution, since there is not a permanent fix at the moment. 
  • The nature of the error is intermittent. Hence, it’s impossible to report to Oracle support, as there is not a proper test plan to recreate the issue. 
  • There is a 9-digit, or 10-digit number is shown in the error stack by Oracle which is incorrect (Ex: ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 2005732968). This incorrect value line number changes when executed from a different Oracle session, but it is still either a 9-digit or 10-digit number according to what we have seen so far. It seems that sometimes metadata related to these errors are getting saved into unreachable memory locations (Stack) in Oracle database. That seems to be the root cause for this error.


 

The “ORA-64610: bad depth indicator” error was recreated using a custom menu and “Execute online SQL” event action in one of the IFS internal environment. 

------------------ Below SQL block used to recreate the issue ------------------

DECLARE BEGIN Error_SYS.Appl_General('CustomerOrderLine', 'WARNING: This is a warning message.'); END;


 
Then Application throw below oracle exception. 

------------------ Error ------------------
ORA-64610: bad depth indicator ORA-06512: at line 16 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2184 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2304 ORA-06512: at "IFSAPP.ERROR_SYS", line 136 ORA-06512: at "SYS.UTL_CALL_STACK", line 99 ORA-06512: at "IFSAPP.ERROR_SYS", line 121 ORA-06512: at "IFSAPP.ERROR_SYS", line 127 ORA-06512: at "IFSAPP.ERROR_SYS", line 331 ORA-06512: at line 3 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2300 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2309 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2159 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2192 ORA-06512: at "IFSAPP.EVENT_SYS", line 199 ORA-06512: at "IFSAPP.EVENT_SYS", line 199 ORA-06512: at "IFSAPP.SANMLK_CUST_ORDER_LINE_EVU", line 10 ORA-04088: error during execution of trigger 'IFSAPP.SANMLK_CUST_ORDER_LINE_EVU' ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 2005732968 ORA-06512: at "IFSAPP.CUSTOMER_ ORDER_LINE_API", line 29405 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 30369 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22358 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22405 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22420 ORA-06512: at line 10


------------------ Explanation of the error ------------------
Error_sys package (which is IFS code) uses 3 methods in Utl_Call_Stack dictionary package (which is Oracle code) namely UTL_Call_Stack.Unit_Line, UTL_Call_Stack.Subprogram & Utl_Call_Stack.Dynamic_Depth to format error texts in IFS application. ORA-64610 error is thrown when one of the above Utl_Call_Stack procedures try to access a non-existent stack position. 

As mentioned in the above error, the error stack shows a 10-digit number as the line number. CUSTOMER_ORDER_LINE_API has nearly 43400 lines (by 11th-June-2020) of code so line number 2005732968 in the above stack shown by Oracle is incorrect. This incorrect value line number changes when executed from a different Oracle session but it is still either a 9-digit or 10-digit number according to what we have seen so far. It seems that sometimes metadata related to these errors are getting saved into unreachable memory locations (Stack) in Oracle database. That seems to be the root cause for this error.

------------------ What was the side effect introduced by the Oracle patch ------------------

"The oracle error "ORA-64610: bad depth indicator" can be solved by applying the " windows bundled patch 12.2.0.1.190716WINDBBP" which was suggested by the solution 264924.

But after applying the above fix as a side effect "Database processes has stopped".

Example scenario: The issue reported by the same customer. 

  • Bad depth error reported by the case : G2061955. 
  • Database processes has stopped, reported by the case : G2128097


------------------ Suggested Solutions ------------------

Showing this 9-digit or 10-digit number in error stack seems to be having some dynamic behavior.

  • The issue seems to disappear when the package is recreated by dropping and re-deploying the affected IFS package in the database. It seems that recreating affected IFS package is solved the issue as it recreates packages in different memory locations.
  • Adding debug information seems to be doing this without dropping and recreating the package and that is the solution we suggest trying.

If the same error can be seen for any other package or in other databases, please try adding debug info to those packages.
 

------------------ Why IFS unable to request a fix from Oracle ------------------
Both the Customers and IFS also experienced, the error is intermittent. It appears in a database, continues for some time and suddenly disappears without a known reason.  

When requesting a patch from Oracle Support, they always request a test plan to reproduce the issue in their own environments. It seems to be a mandatory thing when they report it to their development team to implement a patch. And the test plan should be valid (should reproduce the issue) for the whole time period when the SR is continuing. So, in this case we are getting stuck when preparing such a test plan since we currently do not know how to reproduce 10 digits number in the error stack. Further we do not have any internal database where this error can be seen on request.

As our R&D team has informed us, some time ago, they have found an internal database where this error can be seen. They have reported it to Oracle support. Without having a test plan to reproduce the issue, Oracle support has agreed to investigate the error within the R&D’s database via a Webinar. During the first session of the Webinar, issue has reproduced but not during the second session. (Error has disappeared without any known reason) The SR has not been continued further.

So, we are getting stuck when requesting a patch/permanent solution from Oracle Support and hope the situation can be understood. Currently we do not have an option other than recompiling the package or recreating package or adding debug information to the package to solve the error. Some scenarios adding two custom events solves the issue, but this is not suitable for throwing popup messages like errors or warnings. 
 

If anyone can add more inputs to reproduce the issue (10 digits number in error stack) it would be highly appreciated to continue this.

Thanks.
Kind regards,
Sandun Madola.

View original
    Did this topic help you find an answer to your question?

    17 replies

    Savinda Suvimal
    Hero (Employee)
    Forum|alt.badge.img+11

    Hi

    I have seen this in several occasions and the same solution worked for me. I was unable to report this to Oracle because problem is not re-creatable on demand.

     

    BR

    Savinda

    M
    Sandun Madola
    B
    3 people like this
    • M
      Minura De Silva
    • Sandun Madola
      Sandun Madola
    • B
      Ben Monroe
    M
    Do Gooder (Customer)
    Forum|alt.badge.img+4
    • magnum80
    • Author
    • Do Gooder (Customer)
    • 11 replies
    • April 21, 2020

    Hi Savinda,

    Thanks for your reply. What version of Oracle are you using?

     

    Regards,


    Erik

    M
    1 person likes this
    • M
      Minura De Silva
    Savinda Suvimal
    Hero (Employee)
    Forum|alt.badge.img+11

    Hi,

    It's 12.2.0.1.0 with WINDOWS DB BUNDLE PATCH 12.2.0.1.200114(64bit):30446296

     

    /Savinda

    M
    1 person likes this
    • M
      Minura De Silva
    JULIAN
    Hero
    Forum|alt.badge.img+9
    • JULIAN
    • Hero
    • 75 replies
    • April 21, 2020

    Hi, 

     

    we have experienced same and we were likewise informed by support to recreate the package which solved the problem. 
     

    have not encountered it since. 

    M
    1 person likes this
    • M
      Minura De Silva
    M
    Do Gooder (Customer)
    Forum|alt.badge.img+4
    • magnum80
    • Author
    • Do Gooder (Customer)
    • 11 replies
    • April 21, 2020

    Hi Julian,

     

    Thanks for your response. We have only just tried the re compilation so to early to say if it has offered a permanent fix. Up until now it has been intermittently been appearing over a period of 6 months across 3 different databases…

    We are soon planning to upgrade to Oracle 19, maybe that will help.

    M
    1 person likes this
    • M
      Minura De Silva
    JULIAN
    Hero
    Forum|alt.badge.img+9
    • JULIAN
    • Hero
    • 75 replies
    • April 21, 2020

    We basically did the Oracle 19c upgrade immediatly after. 

    M
    Yasas Kasthuriarachchi
    2 people like this
    • M
      Minura De Silva
    • Yasas Kasthuriarachchi
      Yasas Kasthuriarachchi
    J
    Sidekick (Customer)
    Forum|alt.badge.img+9
    • jhooperyan
    • Sidekick (Customer)
    • 65 replies
    • April 22, 2020

    We reported the bug to IFS and got this response in minutes.  We had the patch in 2 days.  We are running IFS Apps10 UPD6 (this problem only started after our UPD6 upgrade) running “Product: Oracle database - (enterprise edition) Product Version : (12.2.0.1.0) Product language: (English) Operation system/version: Microsoft Windows Server 2016 (64 bit) version 1607 (OS Build 14393.3504)” at the time

     

    Thank you for contacting IFS Global Support and requesting our assistance.
    This is caused by a bug in Oracle database. You need to apply a Windows DB Bundle Patch to correct it. Could you please send me the following details? see the example below. 


    Product: Oracle database -( enterprise edition/Standard Edition)
    Product Version : (12.1.0.1)
    Product language: (English)
    Operation system/version : (Microsoft Windows x64 (64 bit) 2008 R2)

    M
    J
    2 people like this
    • M
      Minura De Silva
    • J
      jamie.malangyaon
    Sandun Madola
    Hero (Employee)
    Forum|alt.badge.img+13
    • Sandun Madola
    • Hero (Employee)
    • 144 replies
    • Answer
    • July 17, 2020

    Hi Erik  (@magnum80 ),

    I have worked in a similar case which was reported to IFS. I think commenting my detail findings will be helpful. Some of the wording little bit similar to the answer you have already received. 

    The “ORA-64610: bad depth indicator” error was recreated using a custom menu and “Execute online SQL” event action in one of the IFS internal environment. After around 3 hours the oracle error was unabled to recreate. It’s hard to say how the issue was resolved. The same steps were followed to recreate the issue in the different IFS internal environments. But I was unable to recreate the issue as on demand. 

    First part of this reply I write summary of my investigation. Latter part of this reply I write little bit more detail.

    ------------------ Summary of My investigation ------------------ 

    After discussing with the IFS experts who have seen this issue and with my own investigations, I can summarize the investigations to the below point. 

    • Our aim was to find a workaround without applying the oracle patch for this issue since the oracle patch introduces side effects.
    • Some scenarios the developers could be able to avoid the bad depth error by creating two custom events. The first custom event to implement the required functionality and the second custom event to post a background job to execute the first custom event. But if you wish to make a pop-up message like error message or warning then this method is not suitable. (Ex: This is not suitable for below PLSQL block)
    • Some scenarios the developers could be able to avoid the error by recompiling the affected IFS package in the database.
    • Some scenarios the developers could be able to avoid the error by dropping and re-deploying the affected IFS package in the database.  But this may revoke the granted permissions to the package and may introduce additional work.
    • Some scenarios the developers mentioned that the issue is solved without doing any additional work. (Error has disappeared without any known reason)
    • Most of the cases the developers could be able to avoid the error by adding the debug information to the affected IFS package in the database. This is the suggested solution, since there is not a permanent fix at the moment. 
    • The nature of the error is intermittent. Hence, it’s impossible to report to Oracle support, as there is not a proper test plan to recreate the issue. 
    • There is a 9-digit, or 10-digit number is shown in the error stack by Oracle which is incorrect (Ex: ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 2005732968). This incorrect value line number changes when executed from a different Oracle session, but it is still either a 9-digit or 10-digit number according to what we have seen so far. It seems that sometimes metadata related to these errors are getting saved into unreachable memory locations (Stack) in Oracle database. That seems to be the root cause for this error.


     

    The “ORA-64610: bad depth indicator” error was recreated using a custom menu and “Execute online SQL” event action in one of the IFS internal environment. 

    ------------------ Below SQL block used to recreate the issue ------------------

    DECLARE BEGIN Error_SYS.Appl_General('CustomerOrderLine', 'WARNING: This is a warning message.'); END;


     
    Then Application throw below oracle exception. 

    ------------------ Error ------------------
    ORA-64610: bad depth indicator ORA-06512: at line 16 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2184 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2304 ORA-06512: at "IFSAPP.ERROR_SYS", line 136 ORA-06512: at "SYS.UTL_CALL_STACK", line 99 ORA-06512: at "IFSAPP.ERROR_SYS", line 121 ORA-06512: at "IFSAPP.ERROR_SYS", line 127 ORA-06512: at "IFSAPP.ERROR_SYS", line 331 ORA-06512: at line 3 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2300 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2309 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2159 ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API", line 2192 ORA-06512: at "IFSAPP.EVENT_SYS", line 199 ORA-06512: at "IFSAPP.EVENT_SYS", line 199 ORA-06512: at "IFSAPP.SANMLK_CUST_ORDER_LINE_EVU", line 10 ORA-04088: error during execution of trigger 'IFSAPP.SANMLK_CUST_ORDER_LINE_EVU' ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 2005732968 ORA-06512: at "IFSAPP.CUSTOMER_ ORDER_LINE_API", line 29405 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 30369 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22358 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22405 ORA-06512: at "IFSAPP.CUSTOMER_ORDER_LINE_API", line 22420 ORA-06512: at line 10


    ------------------ Explanation of the error ------------------
    Error_sys package (which is IFS code) uses 3 methods in Utl_Call_Stack dictionary package (which is Oracle code) namely UTL_Call_Stack.Unit_Line, UTL_Call_Stack.Subprogram & Utl_Call_Stack.Dynamic_Depth to format error texts in IFS application. ORA-64610 error is thrown when one of the above Utl_Call_Stack procedures try to access a non-existent stack position. 

    As mentioned in the above error, the error stack shows a 10-digit number as the line number. CUSTOMER_ORDER_LINE_API has nearly 43400 lines (by 11th-June-2020) of code so line number 2005732968 in the above stack shown by Oracle is incorrect. This incorrect value line number changes when executed from a different Oracle session but it is still either a 9-digit or 10-digit number according to what we have seen so far. It seems that sometimes metadata related to these errors are getting saved into unreachable memory locations (Stack) in Oracle database. That seems to be the root cause for this error.

    ------------------ What was the side effect introduced by the Oracle patch ------------------

    "The oracle error "ORA-64610: bad depth indicator" can be solved by applying the " windows bundled patch 12.2.0.1.190716WINDBBP" which was suggested by the solution 264924.

    But after applying the above fix as a side effect "Database processes has stopped".

    Example scenario: The issue reported by the same customer. 

    • Bad depth error reported by the case : G2061955. 
    • Database processes has stopped, reported by the case : G2128097


    ------------------ Suggested Solutions ------------------

    Showing this 9-digit or 10-digit number in error stack seems to be having some dynamic behavior.

    • The issue seems to disappear when the package is recreated by dropping and re-deploying the affected IFS package in the database. It seems that recreating affected IFS package is solved the issue as it recreates packages in different memory locations.
    • Adding debug information seems to be doing this without dropping and recreating the package and that is the solution we suggest trying.

    If the same error can be seen for any other package or in other databases, please try adding debug info to those packages.
     

    ------------------ Why IFS unable to request a fix from Oracle ------------------
    Both the Customers and IFS also experienced, the error is intermittent. It appears in a database, continues for some time and suddenly disappears without a known reason.  

    When requesting a patch from Oracle Support, they always request a test plan to reproduce the issue in their own environments. It seems to be a mandatory thing when they report it to their development team to implement a patch. And the test plan should be valid (should reproduce the issue) for the whole time period when the SR is continuing. So, in this case we are getting stuck when preparing such a test plan since we currently do not know how to reproduce 10 digits number in the error stack. Further we do not have any internal database where this error can be seen on request.

    As our R&D team has informed us, some time ago, they have found an internal database where this error can be seen. They have reported it to Oracle support. Without having a test plan to reproduce the issue, Oracle support has agreed to investigate the error within the R&D’s database via a Webinar. During the first session of the Webinar, issue has reproduced but not during the second session. (Error has disappeared without any known reason) The SR has not been continued further.

    So, we are getting stuck when requesting a patch/permanent solution from Oracle Support and hope the situation can be understood. Currently we do not have an option other than recompiling the package or recreating package or adding debug information to the package to solve the error. Some scenarios adding two custom events solves the issue, but this is not suitable for throwing popup messages like errors or warnings. 
     

    If anyone can add more inputs to reproduce the issue (10 digits number in error stack) it would be highly appreciated to continue this.

    Thanks.
    Kind regards,
    Sandun Madola.

    X
    Yasas Kasthuriarachchi
    T
    6 people like this
    • X
      Xavier Fernando
    • Yasas Kasthuriarachchi
      Yasas Kasthuriarachchi
    • T
      Tharaka Ranasinghe
    • durette
      durette
    • Sanuri Karunarathana
      Sanuri Karunarathana
    • S
      Sahan Wellala
    P
    Do Gooder (Partner)
    Forum|alt.badge.img+3
    • Piotr Cz
    • Do Gooder (Partner)
    • 1 reply
    • August 26, 2020

    I’ve got similar case at customer’s test installation. Unfortunately adding debug info to packages did not help ☹. I’ve also registered case (G2179884) but first answer was “contact you partner” so to solve problem I have to contact myself 😊.

     

    Are there any other possible solutions?

     

    If necessary it’s possible to use test installation as reference for demonstrating problem to Oracle support.

     

    Regards,

    /PC

     

    M
    Do Gooder (Customer)
    Forum|alt.badge.img+4
    • magnum80
    • Author
    • Do Gooder (Customer)
    • 11 replies
    • August 26, 2020

    The only thing that helped us in the end was to upgrade to Oracle 19.

    durette
    Superhero (Customer)
    Forum|alt.badge.img+19
    • durette
    • Superhero (Customer)
    • 525 replies
    • August 27, 2020

    The “depth” is the the depth of the call stack. IFS uses this depth so security checks aren’t unnecessarily made at every level. Recompiling the packages rebuilds this ordering.

    As a side note somewhat related to this issue, for custom packages, I recommend you do not set PLSQL_OPTIMIZE_LEVEL any higher than the default value of 2, since at level 3, the inlining of packages flattens the call stack and makes debugging far more difficult.

    If you find this forum useful, please consider paying back to the community in your own areas of expertise. If you ask for help in a private message, please know that I will likely repost it as a forum question (with your personal details redacted) and answer it here. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
    Sandun Madola
    T
    2 people like this
    • Sandun Madola
      Sandun Madola
    • T
      Tharaka Ranasinghe
    A
    Superhero (Employee)
    • anmise
    • Superhero (Employee)
    • 1426 replies
    • November 16, 2020

    D

    Navinth Bakmeedeniya
    Hero (Employee)
    Forum|alt.badge.img+12

    You can refer to below link for the original service request I reported to Oracle where you can get more info on this. (in which they included in the patch 27529661 in their BP 12.2.0.1.190716WINDBBP)

     

    https://support.oracle.com/epmos/faces/SrDetail?srNumber=3-19511884961

     

    Test case was in Oracle 12.2.0.1 on Microsoft Windows x64 (2016 Server)
     

    Sandun Madola
    T
    durette
    3 people like this
    • Sandun Madola
      Sandun Madola
    • T
      Tharaka Ranasinghe
    • durette
      durette
    Chathuranga Samarakoon
    Hero (Partner)
    Forum|alt.badge.img+12



    The “ORA-64610: bad depth indicator” issue was resolved after applying the below oracle patches and compiled the objects.


    Oracle® Database Patch (30446296) version 12.2.0.1.200114Skip Headers
    Oracle® Database Oracle JavaVM Component 12.2.0.1.200114 on Windows 64bit (30525838)

    Chathuranga Samarakoon
    X
    Ragaventhan Sathananda
    Dharshankumaar Mahendran
    6 people like this
    • X
      Xavier Fernando
    • Ragaventhan Sathananda
      Ragaventhan Sathananda
    • Dharshankumaar Mahendran
      Dharshankumaar Mahendran
    • T
      Tharaka Ranasinghe
    • Dilhan Perera
      Dilhan Perera
    • Ragul Ravindira
      Ragul Ravindira
    Ragaventhan Sathananda
    Superhero (Partner)
    Forum|alt.badge.img+15

    Patches 30446296, 30525838 have been outdated with the APR2021 release. It is recommendable to apply the latest one (APR2021):

    Patch 32392089:
    https://updates.oracle.com/download/32392089.html

    Patch 32427674:
    https://updates.oracle.com/download/32427674.html

    Ragaventhan S - https://www.linkedin.com/in/ragaventhan-sathananda/
    Kasun Balasooriya
    M
    X
    8 people like this
    • Kasun Balasooriya
      Kasun Balasooriya
    • M
      Minura De Silva
    • X
      Xavier Fernando
    • Yasas Kasthuriarachchi
      Yasas Kasthuriarachchi
    • Shanuka Lashan
      Shanuka Lashan
    • Dharshankumaar Mahendran
      Dharshankumaar Mahendran
    • T
      Tharaka Ranasinghe
    • Ragul Ravindira
      Ragul Ravindira
    durette
    Superhero (Customer)
    Forum|alt.badge.img+19
    • durette
    • Superhero (Customer)
    • 525 replies
    • May 20, 2021

    I ran into this issue while attempting to upgrade from 12.1.0.2.171017 to 12.1.0.2.190416 on Windows 64-bit, going from bundle patch 26720785 to bundle patch 29413116.

    Running datapatch in the database itself after upgrading the software makes the error go away.

    :: Assumptions:
:: Oracle is installed to D:\ORACLE\PRODUCT\12.1.0\DBHOME_1
:: The instance and service are called IFS9DEV4
:: The patch is unzipped to C:\DOWNLOADS\ORACLE_DATABASE\


set ORACLE_BASE=d:\oracle
set ORACLE_HOME=%ORACLE_BASE%\product\12.1.0\dbhome_1
set PATH=%ORACLE_HOME%\perl\bin;%PATH%
set PATH=%ORACLE_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%

net stop msdtc
net stop OracleServiceIFS9DEV4
net stop OracleVssWriterIFS9DEV4
net stop OracleOraDB12Home1TNSListener

cd /d "c:\Downloads\oracle_database\p29413116_121020_MSWIN-x86-64\29413116"

call opatch apply

net start OracleOraDB12Home1TNSListener
net start OracleVssWriterIFS9DEV4
net start OracleServiceIFS9DEV4
net start msdtc

cd /d "D:\oracle\product\12.1.0\dbhome_1\OPatch"
set ORACLE_SID=ifs9dev4
datapatch

     

    If you find this forum useful, please consider paying back to the community in your own areas of expertise. If you ask for help in a private message, please know that I will likely repost it as a forum question (with your personal details redacted) and answer it here. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
    Ragaventhan Sathananda
    1 person likes this
    • Ragaventhan Sathananda
      Ragaventhan Sathananda
    SAKUIN
    Do Gooder (Customer)
    Forum|alt.badge.img+1
    • SAKUIN
    • Do Gooder (Customer)
    • 4 replies
    • August 23, 2021

    We came across same Error after upgrading from Apps8 to Apps10 UPD9.

     

    This was from a custom Event. Disabling it was getting rid of error message so it was surely repeatable.

     

    Did not get much help from IFS Support on it as it was Custom Event.

    Modified the custom event to use Error_Sys.Record_General to Command_SYS.Mail 

     

    Solution is weird. We got this as a workaround by getting an email in place of an Error Alert. But ok for the timebeing until we find the root cause.

    SAKUIN
    M
    1 person likes this
    • M
      Minura De Silva

    Reply


    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings