oracle — tests an oracle database server
[ localhost ORACLE_CONNECT=... ORACLE_HOME=... ORACLE_BASE=... ORA_USER=... ORA_PASS=... ORACLE_TNSADMIN=... ORACLE_NLS_LANG=... ORACLE_ORA_NLS33=...
]oracle
Create Special Oracle User and special View to connect reduce security problems and enable Big Sister to fetch state. Of course you can also use a dba user but we don't prefer username and password from highly privileged users in config files.
Edit PLSQL Script (see sample/oracle/bs-user-view.sql in your distribution) with password for sys and change username and password according your needs:
Default:
[username]/[password] sys/change_on_install check_db/check_db
ORACLE_CONNECT: Connect String constisting looking like [HOSTNAME]:[ORACLE_SID]:[BIG_SISTER_COLON_NAME] Eg. Your database runs on "Asterix" and the Oracle SID you want to surveille is called TVD806. You want to have the collon beeing called "ORACLE DEMO". So your ORACLE_CONNECT string looks like: "Asterix:TVD806:ORACLE DEMO".
ORACLE_HOME: Home directory of the oracle product (where you have installed oracle version) ORACLE_BASE: Home of the oracle user. ORA_USER:User to connect to oracle db. ( with our prepared PLSQL default is check_db) ORA_PASS: Password for oracle user ORA_USER ( with ourprepared PLSQL default is check_db) ORACLE_TNSADMIN: Path where oracle will find the tnsnames.ora optional fields: ORACLE_NLS_LANG, ORACLE_ORA_NLS33
eg:
localhost ORACLE_CONNECT=[ds1skeys:DKMS2:oAPP2]\ ORACLE_HOME=[/u00/app/oracle/product/8.1.6]\ ORACLE_BASE=[/u00/app/oracle]\ ORACLE_NLS_LANG=[american_america.WE8ISO8859P1]\ ORACLE_ORA_NLS33=[/u00/app/oracle/product/8.1.6/ocommon/nls/admin/data]\ ORA_USER=[TSMW] ORA_PASS=[TSMW] ORACLE_TNSADMIN=[/u00/app/oracle/network]\ oracle