From what I heard, if your run your Oracle job from a JAL script using DatabaseConnectEx(...full profile...) instead of DatabaseConnect(...only profile name...) it will fix the problem. For some reasons second connection made to Oracle 8.0.4 (or a later varsion) using database type job or DatabaseConnect statement may crash the scheduler. DatabaseConnectEx works just fine. : I have the Oracle 8.1.6.0.0 Client installed on my server and I experience an
: intermittent problem where a scheduled job will work fine one night and
: then error out on another night. : I was wondering if there was some type of problem with the interface between
: 24x7 and Oracle 8i. I have switched to using the Oracle ODBC driver
: instead and this appears to work better.
|
