Home » RDBMS Server » Server Administration » ORA errors reflected in Apps not registering in the database alert log (Solaris 10, Oracle 10g R2, Tomcat)
ORA errors reflected in Apps not registering in the database alert log [message #642905] Tue, 22 September 2015 20:43 Go to next message
reym21
Messages: 217
Registered: February 2010
Location: Philippines
Senior Member

Gurus,

Can you enlighten me why ORA errors reflected in our Apps server logs
where not registered in our database alert log?

Thanks.
Re: ORA errors reflected in Apps not registering in the database alert log [message #642906 is a reply to message #642905] Tue, 22 September 2015 20:48 Go to previous messageGo to next message
BlackSwan
Messages: 26274
Registered: January 2009
Location: SoCal
Senior Member
reym21 wrote on Tue, 22 September 2015 18:43
Gurus,

Can you enlighten me why ORA errors reflected in our Apps server logs
where not registered in our database alert log?

Thanks.

Oracle differentiates between application errors, which the database itself does not really care about,
and database errors which can impact database behavior.

database errors get logged into alert_SID.log
Application errors get logged only if & when the application code is implemented to log any detail.
Re: ORA errors reflected in Apps not registering in the database alert log [message #642909 is a reply to message #642906] Tue, 22 September 2015 21:06 Go to previous messageGo to next message
reym21
Messages: 217
Registered: February 2010
Location: Philippines
Senior Member

BlackSwan: Thanks for this, but who will initiate then the resolution of errors-- obviously its the Oracle DBA, right (and usually the blame)? But what would be the part of the Apps group in resolving the issue-- these people would say that the issue lies in the database level not in the Apps level. Thanks again.
Re: ORA errors reflected in Apps not registering in the database alert log [message #642912 is a reply to message #642909] Tue, 22 September 2015 21:30 Go to previous messageGo to next message
BlackSwan
Messages: 26274
Registered: January 2009
Location: SoCal
Senior Member
reym21 wrote on Tue, 22 September 2015 19:06
BlackSwan: Thanks for this, but who will initiate then the resolution of errors-- obviously its the Oracle DBA, right (and usually the blame)? But what would be the part of the Apps group in resolving the issue-- these people would say that the issue lies in the database level not in the Apps level. Thanks again.


DBA is responsible for errors that go into alert_SID.log file.
All other errors are application errors; whether the error get written to some application log file or ignored.
Error is Oracle way of reporting a problem.
Application bugs must be resolved by Application Developers.
Re: ORA errors reflected in Apps not registering in the database alert log [message #642913 is a reply to message #642912] Tue, 22 September 2015 21:55 Go to previous messageGo to next message
reym21
Messages: 217
Registered: February 2010
Location: Philippines
Senior Member

BlackSwan: This is a straightforward and revealing infos. But, are you referring that this is the standard? Since most IT Managers in our company had traditional mindset that associate "ORA errors" and "Oracle" solely to the database. Anyway, thank you very much for this.

Best regards,
Re: ORA errors reflected in Apps not registering in the database alert log [message #642914 is a reply to message #642913] Tue, 22 September 2015 22:36 Go to previous messageGo to next message
BlackSwan
Messages: 26274
Registered: January 2009
Location: SoCal
Senior Member
reym21 wrote on Tue, 22 September 2015 19:55
BlackSwan: This is a straightforward and revealing infos. But, are you referring that this is the standard? Since most IT Managers in our company had traditional mindset that associate "ORA errors" and "Oracle" solely to the database. Anyway, thank you very much for this.

Best regards,


SQL> select 1/0 from dual;
select 1/0 from dual
        *
ERROR at line 1:
ORA-01476: divisor is equal to zero



Why would any rational person believe that above is a problem that DBA should fix when DBA did not write the code that produced it?
Re: ORA errors reflected in Apps not registering in the database alert log [message #642918 is a reply to message #642913] Wed, 23 September 2015 01:10 Go to previous messageGo to next message
Michel Cadot
Messages: 65955
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

In addition, do not you mix up Oracle Applications error and Oracle RDBMS errors.
Only the latter belong to DBA, the former belong to your Oracle application admin.

Re: ORA errors reflected in Apps not registering in the database alert log [message #642938 is a reply to message #642918] Wed, 23 September 2015 03:34 Go to previous messageGo to next message
reym21
Messages: 217
Registered: February 2010
Location: Philippines
Senior Member

Sir Michel: Thanks for this additional infos.

Best regards,
Re: ORA errors reflected in Apps not registering in the database alert log [message #642944 is a reply to message #642913] Wed, 23 September 2015 06:31 Go to previous messageGo to next message
EdStevens
Messages: 1005
Registered: September 2013
Senior Member
reym21 wrote on Tue, 22 September 2015 21:55
. . . most IT Managers in our company had traditional mindset that associate "ORA errors" and "Oracle" solely to the database.


Then most IT managers in your company need to be re-educated.
Re: ORA errors reflected in Apps not registering in the database alert log [message #642964 is a reply to message #642905] Wed, 23 September 2015 09:13 Go to previous messageGo to next message
bpeasland
Messages: 51
Registered: February 2015
Location: United States
Member

As others have said, there is a difference between application errors and database errors. Application errors, even if they start with "ORA-" need to be addressed by application developers. The application will receive the error and it is up to the application to decide what to do with it. Some apps simply echo the same error message back to the end user. I find this approach to be confusing for the end user that simply could care less about ORA-xxxx. Where I work, we trap the ORA error in our app code. We give the user a more user-friendly error message but we log the actual ORA- error into a log table in the database. This way, we can go back and research application errors after the fact.


Cheers,
Brian
Re: ORA errors reflected in Apps not registering in the database alert log [message #642993 is a reply to message #642964] Thu, 24 September 2015 06:56 Go to previous messageGo to next message
EdStevens
Messages: 1005
Registered: September 2013
Senior Member
bpeasland wrote on Wed, 23 September 2015 09:13
Where I work, we trap the ORA error in our app code. We give the user a more user-friendly error message but we log the actual ORA- error into a log table in the database. This way, we can go back and research application errors after the fact.


Cheers,
Brian


Brian,
I know you and I have discussed this before and are in agreement, but for the sake of the OP, allow me to point out that a key to your system is that you actually trap and record the original ORA- message. The bane of DBAs is the application the simply replaces the original error message (and its code) with a "user friendly" (read: "meaningless") message. The actual, meaningful error is lost forever, and yet the DBA is somehow expected to know that "Error. Please contact your IT department" actually means (in this one particular instance only) "ORA-01476".
Re: ORA errors reflected in Apps not registering in the database alert log [message #643321 is a reply to message #642993] Mon, 05 October 2015 01:51 Go to previous message
reym21
Messages: 217
Registered: February 2010
Location: Philippines
Senior Member

To EdStevens & Brian (bpeasland),

I appreciate your input.

Thank you & best regards,
Previous Topic: query of 'dba_free_space' is too slow??!!
Next Topic: I've been getting the error In the alert log since the database was built using an rman clone.
Goto Forum:
  


Current Time: Wed Nov 14 07:37:26 CST 2018