Oninit cdi / Archive
Talk to an expert →

temp tables in IDS

Posted in 2005

Topics: Storage & Space Management, Stored Procedures & SPL, Platform-Specific Issues, Versions, Editions & End-of-Life

Bob — — source: IIUG Forums & Mailing Lists

I have a vendor application that appears to be creating temp tables in the root dbspace. I'm baffled. I don't want their temp tables pounding IO in the same dbspace at the system catalogs. There are 2 temp spaces, and the application database is created in dbspace 'dbs1'. They may be created by the vendor's stored procedures. See below: User-created Temp tables : partnum tabname rowsize 1001b8 temp_invt 13 1001b7 hirarch 4 1001b6 parent 2 1001b5 tmp_ac 63 1001ae tmp_date 4 RH Linux 7.3, IDS 9.40.UC2XB

↪ replying to Bob
Murray Wood (IList) — — source: IIUG Forums & Mailing Lists

Assuming you have temp dbspaces in DBSPACETEMP, these tables will be logged temporary tables. Try creating a permanent dbspace in DBSPACETEMP and see whether they move into this dbspace. MW > -----Original Message----- > From: forum.subscriber@iiug.org > [mailto:forum.subscriber@iiug.org] On Behalf Of Bob > Sent: Thursday, 3 February 2005 11:44 a.m. > To: ids@iiug.org > Subject: temp tables in IDS [4142] > > I have a vendor application that appears to be creating > temp tables in the root dbspace. I'm baffled. I don't want > their temp tables pounding IO in the same dbspace at the > system catalogs. > There are 2 temp spaces, and the application database is > created in dbspace 'dbs1'. They may be created by the > vendor's stored procedures. See below: > > > User-created Temp tables : > partnum tabname rowsize > 1001b8 temp_invt 13 > 1001b7 hirarch 4 > 1001b6 parent 2 > 1001b5 tmp_ac 63 > 1001ae tmp_date 4 > > > RH Linux 7.3, IDS 9.40.UC2XB > > >

Glossary