Urgent!!! Database migration from 805 to 817

Did you disable the system triggers before migrating? The best way to perform the migration is to migrate to the base version and then make sure that you were able to open the database and so, then proceed with the application of patch set to the migrated database.

I'm surpries that oracle had suggested the migration to the patched database instance directly. If you don't mind can you pass me the metalink doc id. Just curious to see.

My rule of thumb is first migrate to the base version and then make sure that the application can function, then proceed applying the patchset to the migrated database.

Sam

Hi Sam,

I fully agree with you but note 148902.1 suggest not to migrate at the time of installation. This note is interoperability note for Oracle apps 11.0.3 with Enterprise edition 8.1.7.

Secondly, I have other foll. questions.

1. Why it still shows 8.1.7.1.1 in v$version query inspite of migrated to 8.1.7.1.3.

2. I just read somewhere that we should also run catexp.sql and utlconst.sql just after running u080005.sql. Pl. tell me if I also need to run these scripts.

3. I have changed COMPATIBLE parameter from 8.0.5 to 8.1.7 in init.ora file and bounced the database. Database started perfectly OK but now when I gave command shutdown normal, it looks like it has got hung.

In alert.log, it shows waiting for logins to complete. Infact, there are no other logins to the database at present.

What should I do in this case.

Thanks,

Quote:

---

Originally posted by samdba

3. I have changed COMPATIBLE parameter from 8.0.5 to 8.1.7 in init.ora file and bounced the database. Database started perfectly OK but now when I gave command shutdown normal, it looks like it has got hung.

In alert.log, it shows waiting for logins to complete. Infact, there are no other logins to the database at present.

What should I do in this case.

---

Shutdown immediate.