ERP form error message on a SQL database

Tags:
ERP
SQL
SQL Database
SQL Server errors
We have a problem with the ERP system on our SQL database. Whenever an ERP form at our client’s end remains idle for 15 minutes, an error message pops up when the form is made active again. This message is: “FRM-40733: PL/SQL built-in DBMS_ERROR_CODE failed.” Our DBA team is blaming it on a network issue, but we insist that that it is a problem with either the form design or with compatibility. Do you know what the issue might actually be?

Answer Wiki

Thanks. We'll let you know when a new response is added.

It could be useful to know some more details about your database and forms versions.
It sounds to me like a network issue, but I think it could also be that the database connection is timing out due to some database/sqlnet setting.

Is there some network device between the database and the application (or app server) ? If yes, I would review any timeout setting on that device.

I found this on metalink, but with no solution:

<pre>Problem
——-
While trying to open up an AERS case, error message FRM-40733 appears.
Session appears to hang and user must restart their application session.

FRM-40733 PL/SQL built in DBMS_error_code failed

Analysis
========
This can be a generic error for any application that exploits FORMS.

1. If at a particular point in time,the instance encountered an error
( eg : ORA-3113 – end of file on communication channel …or
ORA-3114 – database connection lost … or some Internal ORA -600 error
that lead to stoppage of any of the Background Processes…
( SMON, PMON ……) then the form would have abruptly thrown the exception
as its database connection thread to the kernel can no
longer communicate to the DB kernel. At that point in time the form is capable
of throwing any error message. </pre>

If the forms can be modified, you could try to set some timer in the form, to issue any simple select statement against the database every 5 minutes, and see what happens.

Hope this helps.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Nido77
    thanx for reply. here are some more information about our setup. cisco asa5520 firewall between database server and clients. any port is opened on firewall for database server. database server operating system is Linux database version 10g. Forms 6i hope this information will be suffice. anxiously waiting for your precious comments.
    10 pointsBadges:
    report
  • Farookh
    Dear All, Same issue we are facing in prod.

    We are using OAS 10g and DB 10g both hosted on linux 5.4.

    Kindly advise

    Regards
    Farookh
    10 pointsBadges:
    report
  • aneeshp555

    I'm not sure the below solutions can help you, i fell it is a network issue if it is working please update me on aneeshp@royalgroup.ae

    1. By default, Windows 7 suspends an inactive network connection to a shared folder residing on a server after 15 minutes however; you can modify this setting through Group Policy settings. When a session is suspended and the client computer resumes its activity the network connection is automatically re-established. Still, some users find it annoying to see red marks on mapped network drives in Windows Explorer.

    The Group Policy security setting allows you to determine the amount of continuous idle time that must pass in a Server Message Block (SMB) session before the session is suspended due to inactivity. The default setting is not defined, which means that the system suspends a session after 15 minutes of idle time for connections to servers’ shares and the setting remains undefined for workstations.

    To configure this setting on a single Windows 7 computer, open the Local Group Policy Editor snap-in by typing gpedit.msc in the Start search text box and pressing enter.

    • Go to Local Computer Policy\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options node.
    • Double click Microsoft network server: Amount of idle time required before suspending a session
    • In the text field provided under Disconnect when idle time exceeds:, enter the number of minutes
    • Then click Apply and OK.

    Note, that a value of 0 means to disconnect an idle session as quickly as is reasonably possible. The maximum value is 99999, which is 208 days; in effect, this value disables the policy.


    2, This autodisconnect feature in Windows 7 provides us some problems - a connection to a software´s database gets lost while idle and we don´t want this to happen. Behavior is, that after user gets back to his machine, the network drive mapped to that database is marked with X, and requires a click on it, to re-establish the connection.

    I found out, that by default, autodisconnect feature does this: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q297684
    I believe the command net config server /autodisconnect:-1 will gives us the result we want, but this is something what needs to be spread to entire organization. Any ideas how to accomplish this?

    0 pointsBadges:
    report
  • ToddN2000
    Sounds like a time out issue. When things like this happen it's always good to start with your connection string and check out the parameters. Some my end the connection by default and you may need to change settings like pooling and timeout.
    59,500 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: