10g- to 11g dbua-upgrade failes with ora-16024
when I start the migration process with database upgrade assistant (dbua),
the parameter LOG_ARCHIVE_DEST_1 is set to 'LOCATION=""' in the init.ora file on the new Oracle 11g Home.
In the further processing the following error occures:
The database is running in the NOARCHIVELOG-Mode.
"Error-Message: ORA-16024: parameter LOG_ARCHIVE_DEST_1 cannot be parsed"
How can I influence the setting of LOG_ARCHIVE_DEST_1 ???
I hope you can help me!
OS: Win Server 2003 R2
Pablo (Paul) Berzukov
Author of Understanding Database Administration
available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
it is very closed to!!!
but log_archive_dest_1 ist set from 'LOCATION=F:\oracle\flash_recovery_area\\ARCHIVELOG' to the following: 'LOCATION=""' and is written in one line.
When LOG_ARCHIVE_DEST_1 is reset I got the same behaviour.
Is there any other parameter who is influencing this behaviour?
Thank you in advance!
has someone else an idea?
What steps do you prefer, to upgrade from Oracle 10.2.0.4 to 18.104.22.168 ?
The DB is more than one TB in size ...
So I dont want to use expdp/impdp.
the solution of the mistery is:
The spfile parameter LOG_ARCHIVE_DEST was set to LOG_ARCHIVE_DEST='' !
So "SHOW PARAMETER" is showing nothing but in the spfile you can see the difference!
ALTER SYSTEM RESET LOG_ARCHIVE_DEST SCOPE=BOTH SID='*';
Tags for this Thread
Click Here to Expand Forum to Full Width