24x7 provides drivers not for different Oracle servers, but for different types of Oracle client software. Different Oracle clients provide different API (called Oracle Call Interface) which are incompatible. However, Oracle still supports old programs by including additional files specifically to resolve the compatibility issues. When you install Oracle client please choose to install the necessary RSF files (Required Oracle Files) for version 8 or version 7. The 24x7 driver "7.3" and driver "8.0.4 and later" should work seamlessly with Oracle 9 client if proper RSF are installed. As far as I know there is a change in client version 9.1 and later that causes serious problems when the SQL being executed returns some result set(s) or internally uses PL/SQL variables. I don't know whether it is a bug in 24x7 or in the Oracle client. Here are two known workaround:
1. Instead of executing EXECUTE my_proc([paremeters]); use
BEGIN
my_proc([paremeters]);
END; 2. Set the job to run detached to prevent it from bringing the entire scheduler down As for Oracle own ODBC drivers they always were and still are very buggy. Avoid using them whenever possible. I recommend using Microsoft or Intersolv ODBC drivers for Oracle. : Just wondering if anyone else is having this type of problem. Below I
: describe my enviroment, the issues I had and my workaround to the issues.
: If anyone has any other ideas I'm open to suggestions. : Enviroment: 24x7 Automation Suite 3.3
: Windows 2000 SP2
: Oracle 9.2.0.1.0 (9i R2) : Issues: (1) No database profile specifically for 9i
: (2) When I use Oracle 8i profile 24x7 scheduler starts to run the job then
: exits while running and the scheduler needs to be restarted
: (3) Oracle 9i ODBC driver connects to database from 24x7 but generates errors
: running PL/SQL : Workaround: Install latest version of MDAC and use the Microsoft Oracle
: driver. Connects to DB and runs PL/SQL and SQL without problem.
|
