Thanks for the question, fdsafa.
Asked: March 07, 2016 - 10:20 am UTC
Last updated: March 07, 2016 - 5:29 pm UTC
Version: 12.1.0.2
Viewed 1000+ times
You Asked
Hi
We had been using automatic parallelism for our test database (12.1.0.2). We had sofar good results for our conversion and batch jobs.
Also we were interested about in-memory parallelism achieved through this.
We also are using global temporary tables with clob fields as methods to create messages to be passed to other systems or use interfaces.
For some time consuming statements we are now hitting oracle error from parallel server p000:
ORA-14453: ORA-14453: attempt to use a LOB of a temporary table, whose data has already been purged
Can we somehow prevent automatic parallelism not to kick in when global temporary tables are used ?
Help and any ideas are much appreciated.
and Chris said...
You could try stopping parallelism by:
- Using the /*+ no_parallel */ hint, or
- disabling auto parallelism in your session:
alter session set parallel_degree_policy = manual;