 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
Duck
Joined: 26 May 2010 Posts: 6 Country: Germany |
|
I can not send a message with DB Alert,the config. is failed |
|
Hallo,
I can not send a message with DB Alert Expert, becouse the configuration of Alert is failed. I get following error message:
But I have recorded the line utl_file_dir=G:\APPS\EPON\DATABASE\EPON\TRACE\BDUMP in the init.ora of the server, whrere recline the Oracle database EPON and into init.ora of the client wherewith I work.
My destination is to send the info/error/warning message to my client.
What can I do?
Thanks and regards.
|
|
Wed May 26, 2010 8:55 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Have you restart the Oracle server after changes in utl_file_dir parameter?
Can you see the new value when you run SELECT * FROM V$PARAMETER query?
|
|
Wed May 26, 2010 9:00 am |
|
 |
Duck
Joined: 26 May 2010 Posts: 6 Country: Germany |
|
|
|
 |
 |
Have you restart the Oracle server after changes in utl_file_dir parameter?
Can you see the new value when you run SELECT * FROM V$PARAMETER query? |
Hi, yes I have restart Oracle Server and I can see the query, not with "SELECT * FROM V$PARAMETER ", but I can see the query.
I'm not sure, that I chart true parameter in the Alert Log Monitor(see please the pic).
Wich File I mus to chart in the "File Name" mask? What mus I to chart into "Text to search in log files"?
regards.
|
|
Thu May 27, 2010 8:13 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
The name seems to be correct. This should be the name of the log file you want the log monitoring package to monitor. Could be any log file you want, including Oracle alert log file.
The alert log monitoring package needs to be able to open the file. That's why for the Oracle alert log you need to add the value of BACKGROUND_DUMP_DEST parameter to UTL_FILE_DIR parameter. This is to enable access to that path from within the database. Without that the access will be blocked for security reasons.
Please also verify that ORA_MONITOR user needs explicit SELECT permissions to retrieve data from SYS.V_$PARAMETER view. For more details you may want to take a look at the code of ORA_MONITOR.LOG_MONITOR package. This may help you to understand how the monitoring for alert logs is working and which parameters and settings are required for that.
Also please use DB Tools DB Job utility to verify that ORA_MONITOR's jobs are installed in the database and they are enabled. If they are disabled or not yet installed, it won't be able to scan your alert log file for the specific error messages.
Please let us know if you still have difficulties making it to run.
Last edited by SysOp on Mon Jun 14, 2010 8:04 am; edited 1 time in total |
|
Thu May 27, 2010 9:05 am |
|
 |
Duck
Joined: 26 May 2010 Posts: 6 Country: Germany |
|
Thank you for the advice. |
|
Hello,
thank you for the advice, but I haven't got the configuration of DB Alert.
Regards.
|
|
Mon Jun 14, 2010 3:42 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
|
|
Which error or errors are you getting now?
|
|
Mon Jun 14, 2010 8:06 am |
|
 |
Duck
Joined: 26 May 2010 Posts: 6 Country: Germany |
|
I get the same error |
|
I get the same error sadly. I dont understand that, I have added the line: utl_file_dir=G:\APPS\EPON\DATABASE\EPON\TRACE\BDUMP into init.ora from Epon Database.
Perhaps is the konfiguration false of DB Alert( see the pics).
The Database Epon has only alert file: epon_alert.log .
Thanks and regards.
|
|
Thu Jun 17, 2010 9:33 am |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|