Migrating from HPUX11 to HPUX11i

[Hugo Matos]

Hi,

I'm currently migrating some applications from HPUX 11 (Oracle 8.0.5) to HPUX 11I (Oracle 8.1.7).

No problems occurred in build process, but in runtime I get some errors such as FETCH OUT OF SEQUENCE, error in PREPARE STATEMENTS, error while OPEN CURSORS, etc.

These errors do not happen in HPUX 11 with Oracle version 8.0.5.

I'd like to know if the errors occur due to the different HPUX version or due to the difference in Oracle versions.

Is there any procedure I should follow to safely migrate applications from HPUX 11 to HPUX 11i (commands to avoid, deprecated commands, ...)?


Thanks in advance.

Hugo Matos

[Ross Zubritski]

Hugo,

FETCH OUT OF SEQUENCE, error in PREPARE STATEMENTS, error while OPEN CURSORS, etc. are Oracle specific errors. You may want to check out Oracle Metalink for these symptoms.

Regards.

REZ

[Don Spare]

Oracle version 8.1.7 is stricter in its execution of various rules. Things that would slip by in earlier versions are reported as errors in 8.1.7. The only real solution to those problems is to research the error and modify the code so it doesn't do what the error is complaining about.

I had a similar experience after upgrading from 8.1.6 to 8.1.7. A stored procedure using a SELECT... FOR UPDATE cursor failed because there was a commit issued before all records had been processed. This had worked for over 2 years in 8.1.6 but failed in 8.1.7. I modified the code to process with a ROWID instead and the error went away. As a side effect the procedure ran in half the time.

[Ravi_8]

Hi,

As for as my experience is concerned, migrating oracle doesn't cause any problem, but migrating OS causes. remedy is backup the oracle, cold install the 11i and put back the oracle.

[Steven E. Protter]

These are oracle issues, triggered however by OS issues on the upgrade.

1) I'm proud of you for even getting a migration to work. When I went to HP class the failure rate in the lab was around 40%.

2) You need to make sure 11i is up to date on patches.

Start with the December 2002 Gold Pack.

Then make sure your java version is current and all java patches are in.
http://www.hp.com/go/java

There is a patch list there. Don't go to java 1.4, its not supported.

Think you're done. No. Oracle maintains a list of patches over and above December 2002 that they insist must be on the OS prior to running the database.

Here is the oracle doc, metalink access required. Post back here if you don't have metalink and need the list.

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=43507.1

Think you're done? Nope. Now that you have all the patches in, you'll need to relink the database.

Shut down the database relink it, and then re-run your tests.

Since you did a migrate, it's no likely that you have issues with 32 bit to 64 bit conversion. If however your platform supported both bit levels and you jumped to 64 bit, you have another migration headche to think about.

I'm linking in an old thread.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x0060ef70e827d711abdc0090277a778c,00.html

Enjoy your reading. Hope some of this stuff helps.

SEP