4 Replies Latest reply on Jun 13, 2014 6:07 PM by 1885afa3-739e-415e-9518-34ca73e7c7a8

    Temporary space usage via linked databases


      Im attempting to address an issue with a client, who's attempting to insert data (roughly 200k rows) into a table after a clone. They're receiving the error ORA-01652 unable to extend temp segment by 128 in tablespace TEMP. However, the table is accessed via a public link through the APPS schema on this cloned database. The APPS schema, however, uses ORATMP, not TEMP (TEMP isn't even on this linked database, however, temp IS on the database in which the user is logged into). I am of the understanding that when you access via a link, All the operations take place on that database, not on the local one. The linked database has roughly 50 gigs of temp available. Is there a chance this user is somehow using the local temp, and not the temp via the link?