cancel
Showing results for 
Search instead for 
Did you mean: 

Restoring from offline backup.

Former Member
0 Kudos

Hi,

We are performing oracle upgradation from 10.2.0.4 to 11.2.0.3. when we started the dbua after completion of 11% dbua got aborted because it could not parsed parameter log_archive_dest1. Then i rectified that and started upgrade manually since i wasnt able to login and do any thing after manual upgrade in the logs i saw many ora-01722 and different ora- errors.

Also after completion of manual upgrade i took backup offline.

Before upgradataion i took offline backup database was in no archive log mode.

while running pre-upgrade script i have created database restore point. i have enabled archivelog, flashback got enable from the pre upgrade script. successfully created restore point.

After manual upgradation when i restored my database using flashback database and tried to open database with resetlogs

i am getting errors as below

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Process ID: 944

Session ID: 267 Serial number: 131

Now i tried to restore database using brtools taken very firstly before upgradation when archivelog were diabled

it was saying

BR0454W Values of oracle_home are different: current 'D:\oracle\EDD\11203', back

up belafpls.afd 'D:\oracle\EDD\102'

BR0455W Value 'D:\oracle\EDD\11203' of oracle_home will be used for restore

   Kindly suggest guys how should i proceed i want to restore database again with 10.2.0.4 without loosing data in it.

Accepted Solutions (1)

Accepted Solutions (1)

former_member188883
Active Contributor
0 Kudos

Hi Balactia,

After manual upgradation when i restored my database using flashback database and tried to open database with resetlogs

i am getting errors as below

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Process ID: 944

Session ID: 267 Serial number: 131

Wondering, as you have completed the upgrade successfully why you need to perform restoration again ? Are there any issues with the upgrade ??

As per the error logs database needs to be opened with startup upgrade option.

Could you try and post the results.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi,

Thanks all for your reply

I am not sure whether my upgrade is successful or not earlier dbua got terminated with error log_archive_dest1 could not be parsed then i rectified it and then continued with manual upgrade due to size limit logs would not be uploaded

below is the link to download logs of manual upgrade

http://www.4shared.com/rar/kT8nRpdc/upgrade.html

I have restored my database to the backup with the backup taken before upgrade it is showing

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

I opened my db with uprade option and ran catupgrd script with

then i got below error

DOC>#######################################################################

DOC>#

DOC>######################################################################

DOC>######################################################################

DOC>    The following statement will cause an "ORA-01722: invalid number"

DOC>    error if the user running this script is not SYS.  Disconnect

DOC>    and reconnect with AS SYSDBA.

DOC>######################################################################

DOC>######################################################################

DOC>#

no rows selected

DOC>######################################################################

DOC>######################################################################

DOC>    The following statement will cause an "ORA-01722: invalid number"

DOC>    error if the database server version is not correct for this script.

DOC>    Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT", and use

DOC>    a different script or a different server.

DOC>######################################################################

DOC>######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC>   The following statement will cause an "ORA-01722: invalid number"

DOC>   error if the database has not been opened for UPGRADE.

DOC>

DOC>   Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT",  and

DOC>   restart using UPGRADE.

DOC>#######################################################################

DOC>#######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC>     The following statement will cause an "ORA-01722: invalid number"

DOC>     error if the Oracle Database Vault option is TRUE.  Upgrades cannot

DOC>     be run with the Oracle Database Vault option set to TRUE since

DOC>     AS SYSDBA connections are restricted.

DOC>

DOC>     Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT", relink

DOC>     the server without the Database Vault option, and restart the server

DOC>     using UPGRADE mode.

DOC>

DOC>

DOC>#######################################################################

DOC>#######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC>   The following statement will cause an "ORA-01722: invalid number"

DOC>   error if Database Vault is installed in the database but the Oracle

DOC>   Label Security option is FALSE.  To successfully upgrade Oracle

DOC>   Database Vault, the Oracle Label Security option must be TRUE.

DOC>

DOC>   Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT",

DOC>   relink the server with the OLS option (but without the Oracle Database

DOC>   Vault option) and restart the server using UPGRADE.

DOC>#######################################################################

DOC>#######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC>   The following statement will cause an "ORA-01722: invalid number"

DOC>   error if bootstrap migration is in progress and logminer clients

DOC>   require utlmmig.sql to be run next to support this redo stream.

DOC>

DOC>   Run utlmmig.sql

DOC>   then (if needed)

DOC>   restart the database using UPGRADE and

DOC>   rerun the upgrade script.

DOC>#######################################################################

DOC>#######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC>   The following error is generated if the pre-upgrade tool has not been

DOC>   run in the old ORACLE_HOME home prior to upgrading a pre-11.2 database:

DOC>

DOC>   SELECT TO_NUMBER('MUST_HAVE_RUN_PRE-UPGRADE_TOOL_FOR_TIMEZONE')

DOC>                       *

DOC>      ERROR at line 1:

DOC>      ORA-01722: invalid number

DOC>

DOC>     o Action:

DOC>       Shutdown database ("alter system checkpoint" and then "shutdown abort").

DOC>       Revert to the original oracle home and start the database.

DOC>       Run pre-upgrade tool against the database.

DOC>       Review and take appropriate actions based on the pre-upgrade

DOC>       output before opening the datatabase in the new software version.

DOC>

DOC>#######################################################################

DOC>#######################################################################

DOC>#

Now I have restored my db with backup taken after manual upgrade its open but not sure whether this upgrade is successfully done or not i have attached logs in the link given above

kindly advice whether the upgrade was done properly or not after reviewing those logs

Regards

Reagan
Advisor
Advisor
0 Kudos

Hello

Now I have restored my db with backup taken after manual upgrade its open but not sure whether this upgrade is successfully done or not i have attached logs in the link given above

If you have the database upgraded then I suggest you to run the post upgrade scripts from SAP t confirm the upgrade status.

Regards

RB

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

I have completed my db upgrade

DOC>#######################################################################

DOC>#

DOC>######################################################################

DOC>######################################################################

DOC>    The following statement will cause an "ORA-01722: invalid number"

DOC>    error if the user running this script is not SYS.  Disconnect

DOC>    and reconnect with AS SYSDBA.

DOC>######################################################################

DOC>######################################################################

DOC>#

i was assuming above comment as an error and i was restoring db to earlier version

i have successfully completed my upgrade and postupgrade and application is up and running

Thank you all for for your replies

Regards,

former_member188883
Active Contributor
0 Kudos

Hi Balactia,

Looks like upgrade is completed and there are no issues with database and application.

Regards,

Deepak Kori

Reagan
Advisor
Advisor
0 Kudos

Hello

BR0454W Values of oracle_home are different: current 'D:\oracle\EDD\11203', backup belafpls.afd 'D:\oracle\EDD\102'

BR0455W Value 'D:\oracle\EDD\11203' of oracle_home will be used for restore

These are not errors instead they are just warnings.

If there are no other error messages in the restore log then the database will get restored.

If the restore fails then provide the complete restore log.

Regards

RB