I dont ever trust the space requirements check...
We make system tablespaces (system, sysaux,undo,temp) auto extend during
upgrade to avoid these issues and turn off auto extend and resize when
required afterwards.
Guess you will do too from now on :-)
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
On Wed, Sep 2, 2015 at 2:59 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
Glad it worked. You're welcome.
Sent from my iPad
On Sep 1, 2015, at 11:40 AM, Sandra Becker <sbecker6925@xxxxxxxxx> wrote:
Added the space, reran the upgrade, all is good. Thanks again for the
help.
Sandy
On Tue, Sep 1, 2015 at 7:04 AM, Sandra Becker <sbecker6925@xxxxxxxxx>
wrote:
Thank you, Andrew. That's exactly what I needed to know.
Sandy
On Mon, Aug 31, 2015 at 5:41 PM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
Startup upgrade, add temp space, and re-run catupgrd.
Sent from my iPad
On Aug 31, 2015, at 6:38 PM, Sandra Becker <sbecker6925@xxxxxxxxx>
wrote:
I have no problem adding space to TEMP, I'm just not sure how I would do
it at this point since some things were upgraded to 12c. Do I try to open
the database as 12c and re-run the perl upgrade script or just catupgrd?
Or do I try to open it as 11g? Or do I restore and start the process all
over?
Sandy
On Mon, Aug 31, 2015 at 3:53 PM, Ls Cheng <exriscer@xxxxxxxxx> wrote:
Hi
Do you have some huge sys/system owned segments?
catupgrd can be re-run
On Mon, Aug 31, 2015 at 11:17 PM, Sandra Becker <sbecker6925@xxxxxxxxx>
wrote:
I have a ticket open with Oracle support, but I'm still waiting to
hear back from them. I ran the dbupgdiag.sql script. No issues reported.
Ran the preupgrd.sql script which indicated temp space was adequate. It
did say SYSTEM was too small so I fixed that and the job_queue_processes
were too low so I adjusted it as well. Nothing else was reported. Two
hours later, the
upgrade fails with the information below. What do I need to do to
complete this upgrade? Do I need to restore back to 11g and redo
everything? Guidance is appreciated.
Oracle Server
ORA-01418: specified index does not exist
ORA-01418: specified index does not exist
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-12801: error signaled in parallel query server P000
ORA-12801: error signaled in parallel query server P000
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-01418: specified index does not exist
ORA-01418: specified index does not exist
ORA-12801: error signaled in parallel query server P000
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-06512: at line 8
ORA-01418: specified index does not exist
ORA-12801: error signaled in parallel query server P000
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-01418: specified index does not exist
ORA-01418: specified index does not exist
ORA-12801: error signaled in parallel query server P000
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
ORA-01418: specified index does not exist
ORA-01418: specified index does not exist
Oracle Server INVALID 12.1.0.2.0
01:37:10
JServer JAVA Virtual Machine VALID 12.1.0.2.0
00:07:49
Oracle Workspace Manager VALID 12.1.0.2.0
00:04:05
OLAP Analytic Workspace VALID 12.1.0.2.0
00:01:33
OLAP Catalog OPTION OFF 11.2.0.4.0
00:00:00
Oracle OLAP API VALID 12.1.0.2.0
00:01:41
Oracle XDK VALID 12.1.0.2.0
00:01:45
Oracle XML Database VALID 12.1.0.2.0
00:06:02
Oracle Database Java Packages VALID 12.1.0.2.0
00:00:52
Final Actions
00:03:26
Total Upgrade Time: 02:06:26
PL/SQL procedure successfully completed.
--
Sandy
GHX
--
Sandy
GHX
--
Sandy
GHX
--
Sandy
GHX
