admin on July 16th, 2010

This post is for all that continue to have problem with “dot” and “comma” on query.

I mean for all that have result from query with “.” and “,” excanged please try this way:

add an option to jvm:

  • -Duser.language=en_US

or apply this other one option:

  • -Duser.language=en -Duser.country=US

I say that because seems that there is a bug on java jvm on windows and ignore “locale” set inside Orabbix.

Inside Orabbix locale is set so:

Locale.setDefault( new Locale( “en”, “US” ) );

but some people continue to have some problem.

With this way you are going to solve all trouble about dot and comma excange.

You can modify the run.bat like this one :

java  -Duser.language=en -Duser.country=US -Dlog4j.configuration=./conf/log4j.properties -jar orabbix-0.9.1.jar start ./conf/config.props

Tags: , , ,

admin on July 13th, 2010

Here you see the new screenshots for graphs with Orabbix 0.9.1 and Zabbix Server 1.8.2

  1. DB Version
  2. SGA Memory Usage
  3. DB Version
  4. SGA Memory Usage
  5. Shared Pool
  6. Hit Ratio
  7. Pin/Hit Ratio
  8. Logical I/O
  9. Physical I/O
  10. Sessions/Processes
  11. Sessions
  12. PGA
  13. Events Waits
  14. ArchiveLog

[aslideshow effect=”random” play=true playframe=false controls_play=true]
Orabbix Logo
DB Version
SGA Memory Usage
Shared Pool
Hit Ratio
Pin/Hit Ratio
Logical I/O
Physical I/O
Sessions/Processes
Sessions
PGA
Events Waits
ArchiveLog
[/aslideshow]

Tags: , ,

admin on July 12th, 2010
Orabbix 0.9.1 is out!
Orabbix Logo
In this release there is just a little but really nice improvement:
Now Orabbix retrieve the connection, once has get the connection to database execute a query like “select sysdate from dual” this just to pubblish a green dot on zabbix if database is alive, if DB is Alive i send “1” to Zabbix Server, and if ALIVE Orabbix goes ahead with all database checks.
This pros is just to exclude an useless execution of queryes on database that
are unavailable.
On zabbix template I’ve added “alive” that register if a database is alive or not.
This is really useful e.g. to calculate a SLA so you can put database availability on your SLAS.
Other than i’ve added a trigger if Alive is 0 a trigger send a mail that database is not available.
Alive is also useful because there is another trigger connected with.
This new trigger is “no data received from orabbix” that is incredibly useful because simply “sum” the value retrieved from zabbix and if the sum is less than 1 on 10 minutes zabbix send an email. I consider 10 minute the maximum acceptable time between a run of Orabbis to anotheone (you can change an spcify a different schedule con config.props)
{Template_Oracle:alive.sum(600)}<1
(Thank’s to Thiago for this  hint)
so if Orabbix is not working you are going to have a new mail.
Orabbix is freely available and downloadable from here or on sourceforge as usual.

Tags: , ,

admin on July 2nd, 2010
Dear Followers,
on this release i’ve correct some bugs:
  • Fixed a minor bug about quantity of thread generated.
  • Fixed problem concerning wrong Locale setting on server
  • Added support for more than one Zabbix Server.
  • Completely rewrote the “sender” Object
  • Improved performances
  • Tested and completely compatible with Zabbix 1.8.2
Now orabbix support more than one Zabbix server so you can easily migrate from one version to zabbix to  anotherone and keep both live, or you can have a Zabbix server that act as “backup” etc…

You can download directly from my website simply registering and downloading the Orabbix 0.9 or on sourceforge as usual.

Sources are already committed on sourceforge.

Stay Tuned! News are coming!

Pleas if you like this project please consider to donate, so you are going to support this project.

Tags: , , ,

I was working on an integration between Orabbix and Rman catalog, in the next release you will see this integration and how it’s work.
Anyway all my backup with rman was used to have this problem:
RMAN-08137: WARNING: archive log not deleted as it is still needed
This is not really a “problem” it’s just a warning, but i don’t like have all my rc_rman_status table of the rman catalog full of this warning.
To solve this i’ve changed my rman script in this way:

run {
# Andrea Dalle Vacche
# TAPE BACKUP ver. 1.3 27/05/2010
#
allocate channel t1 type ‘SBT_TAPE’;
backup format ‘ARC_%n_T%T_t%t_s%s_p%p’ archivelog all;
#
# TO SOLVE RMAN-08137: WARNING: archive log not deleted as it is still needed
#
DELETE ARCHIVELOG UNTIL TIME ‘sysdate – 30/(24*60)’ BACKED UP 1 TIMES TO DEVICE TYPE SBT_TAPE;
release channel t1;
}
exit;

With this script Rman delete the archivelog that are older than 30 minutes and backed up at least one time on tape.

This requirement was born from this query:

SELECT ‘ DB NAME->’
|| db_name
|| ‘- ROW TYPE->’
|| row_type
|| ‘- START TIME->’
|| to_char(start_time, ‘Dy DD-Mon-YYYY HH24:MI:SS’)
|| ‘- END TIME->’
|| to_char(end_time, ‘Dy DD-Mon-YYYY HH24:MI:SS’)
|| ‘- MBYTES PROCESSED->’
|| mbytes_processed
|| ‘- OBJECT TYPE->’
|| object_type
|| ‘- STATUS->’
|| status
|| ‘- OUTPUT DEVICE->’
|| output_device_type
|| ‘- INPUT MB->’
|| input_bytes / 1048576
|| ‘- OUT MB’
|| output_bytes / 1048576
FROM rc_rman_status
WHERE start_time > SYSDATE – 1
AND (status LIKE ‘%FAILED%’ OR status LIKE ‘%ERROR%’)
ORDER BY end_time;

This is the query that i run on catalog to retrieve all the error on rman but i don’t like to have just ‘%FAILED%’ or ‘%ERROR%’ because it’s important keep monitored also ‘%WARNING%’ that sometime help a lot in our work.

Obviously you need use this statement:

DELETE ARCHIVELOG UNTIL TIME ‘sysdate – 30/(24*60)’ BACKED UP 1 TIMES TO DEVICE TYPE SBT_TAPE;

in all backup that you do also on full backup.

e.g. like this one:

run {
# Andrea Dalle Vacche
# TAPE BACKUP ver. 1.3 27/05/2010
#
allocate channel t1 type ‘SBT_TAPE’;
backup full format ‘ONL_FULL_%n_T%T_t%t_s%s_p%p’ database plus archivelog;
#
# TO SOLVE RMAN-08137: WARNING: archive log not deleted as it is still needed
#
DELETE ARCHIVELOG UNTIL TIME ‘sysdate – 30/(24*60)’ BACKED UP 1 TIMES TO DEVICE TYPE SBT_TAPE;
delete noprompt force obsolete;
release channel t1;
}
exit;

Tags: , , , ,

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this. To know all the policy detais click here.

Close