Help appreciated!!!
I am in the process of upgrading to datastage 6 (and sybase 12.5) on Solaris 8. And am getting the following warning with all jobs using sybase stage, even with a simple 'select' sybase stage:
========================================================
test..SYBASEOC_0: Sybase Server warning 2762 (severity 16) from stored procedure 'sp_tables', line 212: The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database.
========================================================
I had debugging turned on in Sybase and saw nothing strange.
Any ideas?
Thanks,
Zinna
Sybase connection
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The message is very clear, you're trying to get Sybase to do something (use CREATE TABLE in the tempdb database from within a multi-statement transaction) which Sybase's own rules do not permit.
Either use a different database, or use a single statement transaction to create the table (which might, in turn, involve using a separate stored procedure if that's how you want to control things).
Edited by - ray.wurlod on 12/10/2002 16:56:00
Either use a different database, or use a single statement transaction to create the table (which might, in turn, involve using a separate stored procedure if that's how you want to control things).
Edited by - ray.wurlod on 12/10/2002 16:56:00
But the problem is, no where in my job do I create a table. It is a simple select sybase stage which just selects data from one table and output to sequential file. Why would a "Create Table.." be issued in tempdb? Transaction logging is off, auditing is off. Does datastage use temporary tables when I use Sybase stage?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hmm, tricky.
Looks like sp_tables is itself attempting to create a temporary table, and Sybase is objecting because tempdb database is being used (and, presumably, sp_tables is a multi-statement stored procedure). I suspect this is happening when the Sybase Open Client software is attempting to access a list of available tables in the database. (But, to be honest, Sybase is not my forte - consult your Sybase support/DBA.)
Might be worth checking whether you can set/change your default database, to try to avoid tempdb.
I note also that you are upgrading both DS and Sybase. Do you have any opportunity to try upgrading just one, to see whether it's the new version of DS or the new version of Sybase that's causing you this grief?
Edited by - ray.wurlod on 12/13/2002 13:16:48
Looks like sp_tables is itself attempting to create a temporary table, and Sybase is objecting because tempdb database is being used (and, presumably, sp_tables is a multi-statement stored procedure). I suspect this is happening when the Sybase Open Client software is attempting to access a list of available tables in the database. (But, to be honest, Sybase is not my forte - consult your Sybase support/DBA.)
Might be worth checking whether you can set/change your default database, to try to avoid tempdb.
I note also that you are upgrading both DS and Sybase. Do you have any opportunity to try upgrading just one, to see whether it's the new version of DS or the new version of Sybase that's causing you this grief?
Edited by - ray.wurlod on 12/13/2002 13:16:48