Autoupgrade Error: UPG-1401, ORA-38760 due to guaranteed restore point



In the middle of 11.2.0.4 upgrade to 19c with auto upgrade i deleted flash back log files due to space constraints. Forgot to include parameter(apx.restoration=no) to instruct autoupgrade utility not to do a guaranteed restore point.


Autoupgrade had following error
upg> 
-------------------------------------------------
Errors in database [APX]
Stage     [DBUPGRADE]
Operation [STOPPED]
Status    [ERROR]
Info    [
Error: UPG-1401
Opening Database APX in upgrade mode failed
Cause: Opening database for upgrade in the target home failed.
For further details, see the log file located at /home/oracle/APX/APX/101/autoupgrade_20200614_user.log]
-------------------------------------------------
Logs: [/home/oracle/APX/APX/101/autoupgrade_20200614_user.log]


autoupgrade_20200614_user.log had this detailed error


2020-06-14 21:02:52.419 ERROR 
DATABASE NAME: APX
         CAUSE: ERROR at Line 8 in [Buffer]
        REASON: ORA-38760: This database instance failed to turn on flashback database
        ACTION: [MANUAL]
        DETAILS: 38760, 00000, "This database instance failed to turn on flashback database"
// *Cause: Database flashback is on but this instance failed to
//         start generating flashback data. Look in alert log for more
//         specific errors.
// *Action: Correct the error or turn off database flashback.

2020-06-14 21:02:52.443 ERROR Database Open Failed for APX ORACLE instance started.
Total System Global Area 1207958960 bytes
Fixed Size                  8895920 bytes
Variable Size             721420288 bytes
Database Buffers          469762048 bytes
Redo Buffers                7880704 bytes
Database mounted.
ORA-38760: This database instance failed to turn on flashback database



2020-06-14 21:02:52.445 ERROR Opening Database APX in upgrade mode failed 
2020-06-14 21:02:52.446 ERROR Exception Error in Database Upgrade [APX] 
2020-06-14 21:02:52.469 ERROR APX Return status is ERROR 
2020-06-14 21:02:52.488 INFO Starting error management routine 
2020-06-14 21:02:52.495 INFO Ended error management routine 
2020-06-14 21:02:52.504 ERROR Error occurred while running the dispatcher for job 101
Cause: Opening database for upgrade in the target home failed. 

 First solution came to mind was Turing off flashback database.

started the database to mount mode and ran


Alter database flashback off;

resumed autoupgrade but again it failed with same error. Even i tried with archive log disabling but autoupgrade was always failing with same error.


Finally i had to delete the restore point autoupgrade automatically creates when it starts the upgrade process.
SQL> select name from v$restore_point ;
NAME
--------------------------------------------------------------------------------
AUTOUPGRADE_221145114461854_APX

started the database to mount mode and ran
drop restore point AUTOUPGRADE_221145114461854_APX;

 after dropping restore point i resumed autoupgrade and then it was able to continue

upg> resume -job 101
Resuming job: [101][APX]
upg> lsj
+----+-------+---------+---------+-------+--------------+--------+--------+-------+
|Job#|DB_NAME|    STAGE|OPERATION| STATUS|    START_TIME|END_TIME| UPDATED|MESSAGE|
+----+-------+---------+---------+-------+--------------+--------+--------+-------+
| 101|  APX|DBUPGRADE|EXECUTING|RUNNING|20/06/14 15:39|     N/A|04:56:08|Running|
+----+-------+---------+---------+-------+--------------+--------+--------+-------+
Total jobs 1



status -job 101
Progress
-----------------------------------
Start time:      20/06/14 15:39
Elapsed (min):   798
End time:        N/A
Last update:     2020-06-15T04:56:42.531
Stage:           DBUPGRADE
Operation:       EXECUTING
Status:          RUNNING


Comments

Post a Comment

Popular posts from this blog

Error processing request - Contact your application administrator apex 20.1

Image
After upgrading 11.2.0.4 to 19c with apex 20.1 accessing apex_admin/apex pages was throwing “Error processing request” Contact your application administrator. There were three invalid objects for APEX_200100 WWV_FLOW_SESSION_RAS WWV_FLOW_WIZARD_API WWV_FLOW_DATA_LOADER Tried compiling these objects but compile was completing with PL/SQL: ORA-00942: table or view does not exist To resolve the issue following rant needs to be given then compile (ran both grant and compile as sysdba) grant select on SYS.DBA_XS_DYNAMIC_ROLES to APEX_200100; grant select on SYS.DBA_TAB_IDENTITY_COLS to APEX_200100; alter package APEX_200100.WWV_FLOW_SESSION_RAS compile body; alter package APEX_200100.WWV_FLOW_WIZARD_API compile body; alter package APEX_200100.WWV_FLOW_DATA_LOADER compile body; Returned 0 invalid object for APEX_200100  select * from dba_objects where status = 'INVALID' and owner = 'APEX_200100' ; Now both admin and apex pages ar
Read more

APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter (R12 12.1.3)

Image
APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter After upgrading oracle application 11i(11.5.10.2) to R12(12.1.3) running concurrent program request caused this issue When concurrent program is run for a concurrent request after upgrading to R12 12.1.3 the lov, which is attached to a parameter, gives APP-FND-01436: “List of Values cannot find any values for you to choose”. When the same request is run from oracle applications 11i 11.5.10.2 the same value set is working fine. The value set is based on a table. If you go and test the value set query from the value set definition screen it returns complete successful message yet if you go to the parameter of the concurrent request program form where the particular value set is used it gives you the above error. After searching google and oracle support I found metalink note 1400963.1, EBS R12.1: Parameter for Concurrent Request Using Table Based LOV G
Read more

WEB ADI - issues encountered during initial access

Image
On accessing create document link under Desktop Integrator responsibility browser was showing following error Set BNE UIX Physical Directory profile value to proper directory at site level Location = $COMMON_TOP/html/cabo/  (11i) Location = $COMMON_TOP/webapps/oacore/html/cabo/  (R12) As this was a cloned instance the value of this profile setting was pointing to a wrong location. set as BNE UIX Physical Directory /u03/oracle/prodcomn/html/cabo/ Access to functions are controlled by function security so to access and work with web adi the user should have proper access. You should have access to particular integrator to access and work with it Find out responsibility which is created to work with web adi check the main menu for this responsibility. Modify the responsibility or Menu if default is not fitting to your needs. For instance Desktop Integration Menu has create document, Define Lay out, Define Mapping, Manage Documents, Setup options Note : you must add
Read more