Path: news.easynews.com!easynews!cyclone2.usenetserver.com!news.webusenet.com!telocity-west!TELOCITY!newsfeed-west.nntpserver.com!hub1.meganetnews.com!nntpserver.com!newsfeed.news2me.com!newsfeed.icl.net!newsfeed.fjserv.net!kibo.news.demon.net!demon!newshub1.nl.home.com!news.nl.home.com!amsnews01.chello.com!surfnet.nl!teleglobe.net!198.54.202.39.MISMATCH!ctb-nntp1.saix.net!not-for-mail From: "Billy Verreynne" Newsgroups: comp.databases.oracle.server Subject: Re: ORA-03212: Temporary Segment cannot be created in locally-managed tablespace Date: Thu, 8 Aug 2002 10:01:44 +0200 Organization: Verreynne Software Labs Lines: 47 Message-ID: References: NNTP-Posting-Host: 198.54.202.209 X-Trace: ctb-nnrp2.saix.net 1028793704 10589 198.54.202.209 (8 Aug 2002 08:01:44 GMT) X-Complaints-To: abuse@saix.net NNTP-Posting-Date: 8 Aug 2002 08:01:44 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: easynews comp.databases.oracle.server:157242 X-Received-Date: Thu, 08 Aug 2002 00:58:49 MST (news.easynews.com) "Epicentre team A" wrote > I've this error when connect. Here is the full text: 03212, 00000, "Temporary Segment cannot be created in locally-managed tablespace" // *Cause: Attempt to create a temporary segment for sort/hash/lobs in // in permanent tablespace of kind locally-managed // *Action: Alter temporary tablespace of user to a temporary tablespace // or a dictionary-managed permanent tablespace > why ? Temporary objects created by Oracle, can not reside in a permanent tablespace. When a database is created, it is the norm to create a tablespace called TEMP and specify it as a temporary tablespace. (refer to the CREATE TABLEAPACE command) When Oracle users are created, it is the norm to specify that this tablespace be used as their temporary tablespace. (refer to the CREATE USER command) What seems to be happening here, is that either the temp tablespace for the Oracle user that you are using has not been specified (resulting in an invalid default and permanent tablespace being assigned), or that the temp tablespace assigned for that user is no longer (or never was) a temporary tablespace. To fix: - determine the name of the temp tablespace on your database (refer to the view DBA_TABLESPACES or USER_TABLESPACES) - correct your Oracle user using the ALTER USER command (e.g. ALTER USER johndoe TEMPORARY TABLESPACE temp) It is unlikely that you will have the required permission to the 2nd step - in which case you need to use the an Oracle user with DBA privs (e.g. sys). -- Billy