Re: Upgrade session interrupted - nohup catupgrd.sql?
- From: troach@xxxxxxxxx
- To: kadmon@xxxxxxxxx,oracle-l@xxxxxxxxxxxxx
- Date: Thu, 21 Oct 2010 13:31:57 +0000
You got a lot of comments which are good. When running these things remote I
always use screen so that if my session is disconnected I am able to reconnect
without it getting killed due to a network interrupt or something happening on
the client side like Windows trying to automatically restart due to a windows
update or a system crash. Just my 2 cents :)
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: cam <kadmon@xxxxxxxxx>
Sender: oracle-l-bounce@xxxxxxxxxxxxx
Date: Thu, 21 Oct 2010 13:28:42
To: <oracle-l@xxxxxxxxxxxxx>
Reply-To: kadmon@xxxxxxxxx
Subject: Upgrade session interrupted - nohup catupgrd.sql?
Hello all,
This seems like an obvious and common one but I haven't managed to
find any relevant Q&As here or on the OTN discussion boards.
While remotely running catupgrd.sql to take an instance from 9.2.0.8
to 11.1.0.7 my session was killed... When I got back on, I decided the
situation was closest to the situation described under Resource
exhaustion in the 11g Upgrade guide and went for:
- shutdown abort
- startup upgrade
- @catupgrd.sql
This seems to have just completed successfully but I'd be interested
in any responses to the following:
- does this seem like the correct way to resume the upgrade - it isn't
explicitly documented anywhere.
- since its not interactive, I assume its OK to nohup catupgrd - but
people don't often seem to do it. Can anyone confirm that it works and
doesn't get confused for some reason?
cam
--
//www.freelists.org/webpage/oracle-l
Other related posts:
