I am currently using the 2.4.1 version of the 24x7 scheduler.

I have created a JAL script to move data from a production Oracle 8 database to a test Oracle 8 database.

DatabaseConnectEx( "ODBC", "ORATEST", "ORATEST", "USER1", "PASS1", FALSE )
*
* Various JAL database commands
*
DatabaseDisconnect( )

DatabaseConnectEx( "ODBC", "ORATEST", "ORATEST", "USER2", "PASS2", FALSE )
*
* Various JAL database commands
*
DatabaseDisconnect( )

The problem is that the second connect does not work properly. Watching the connection occur on the database session monitor shows that the script is connecting as USER1/PASS1 not USER2/PASS2.

I have split the script into two jobs and this works fine but I think I should be able to connect and reconnect multiple times in a single JAL script.

John

Try the following:
1: Place Wait(60) in between to check whether it gets disconnected after the first connection
2. Check your ODBC driver documentation to find out whether it has "connection pooling"

Just out of my curiosity, why don't you use native driver for Oracle connection instead of ODBC?

: I am currently using the 2.4.1 version of the 24x7 scheduler.

: I have created a JAL script to move data from a production Oracle 8 database
: to a test Oracle 8 database.

: DatabaseConnectEx( "ODBC", "ORATEST",
: "ORATEST", "USER1", "PASS1", FALSE )
: *
: * Various JAL database commands
: *
: DatabaseDisconnect( )

: DatabaseConnectEx( "ODBC", "ORATEST",
: "ORATEST", "USER2", "PASS2", FALSE )
: *
: * Various JAL database commands
: *
: DatabaseDisconnect( )

: The problem is that the second connect does not work properly. Watching the
: connection occur on the database session monitor shows that the script is
: connecting as USER1/PASS1 not USER2/PASS2.

: I have split the script into two jobs and this works fine but I think I
: should be able to connect and reconnect multiple times in a single JAL
: script.

: John

I would like to use the native connection but I am using ODBC because it appears to be more stable. When I use a Native Oracle 8.0.4 - 8i database profile the second time the job runs the scheduler disappears and has to be restarted. On the plus side when I do use the Native connection the first time it does work properly.

Actually before I posted this I ran the job in debug mode and watched it disconnect from the database before stepping to the next line.

Connection pooling is on for 60 seconds. I turned off connection pooling and got the the same result.

Addition Information: Useing Oracle Client Software Version 8.1.6 (8i Rel 2 )

It sounds like a bug, I forwarded this issue to support

: I would like to use the native connection but I am using ODBC because it
: appears to be more stable. When I use a Native Oracle 8.0.4 - 8i database
: profile the second time the job runs the scheduler disappears and has to
: be restarted. On the plus side when I do use the Native connection the
: first time it does work properly.

: Actually before I posted this I ran the job in debug mode and watched it
: disconnect from the database before stepping to the next line.

: Connection pooling is on for 60 seconds. I turned off connection pooling and
: got the the same result.

: Addition Information: Useing Oracle Client Software Version 8.1.6 (8i Rel 2 )

In my tests this happens for ODBC connection only. When using native Oracle driver it works fine.

By the way, the stability problem with subsequent Oracle connections has been fixed in recent versions, please upgrade your 24x7 Scheduler

: I would like to use the native connection but I am using ODBC because it
: appears to be more stable. When I use a Native Oracle 8.0.4 - 8i database
: profile the second time the job runs the scheduler disappears and has to
: be restarted. On the plus side when I do use the Native connection the
: first time it does work properly.

: Actually before I posted this I ran the job in debug mode and watched it
: disconnect from the database before stepping to the next line.

: Connection pooling is on for 60 seconds. I turned off connection pooling and
: got the the same result.

: Addition Information: Useing Oracle Client Software Version 8.1.6 (8i Rel 2 )