OFSAA 7.3 Upgrade Fails on Obsolete Atomic Schema with ORA-01017: Invalid Username/Password (Doc ID 1481026.1)

Last updated on MAY 22, 2016

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

When upgrading Oracle Financial Services Analytical Applications (OFSAA) 7.2.10 to OFSAA 7.3, the upgrade fails when you run the Upgrade.sh script.  When you review the OFSAAIUpgrade.log, you see that your main "atomic" schema is upgraded successfully but you see an error associated with one of your atomic schema users that is no longer used and no longer exists.  The error on the obsolete schema causes a rollback of all upgrade changes.

Below are some of the errors in the OFSAAIUpgrade.log:

[UPGRADELOG] [2012-08-02 18:30:05,605] Attempting to connect atomic1a on jdbc:oracle:thin:@server1.oracle.com:1521:OFSAADEV
[UPGRADELOG] [2012-08-02 18:30:05,943] Exception
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
.
.
.
[UPGRADELOG] [2012-08-02 18:30:05,947] Not able to connect atomic schema atomic1a
[UPGRADELOG] [2012-08-02 18:30:05,968] ============================================================================
[UPGRADELOG] [2012-08-02 18:30:05,968] Database rollback started
[UPGRADELOG] [2012-08-02 18:30:05,968] ============================================================================
[UPGRADELOG] [2012-08-02 18:30:05,969] Attempting to connect config on jdbc:oracle:thin:@server1.oracle.com:1521:OFSAADEV
[UPGRADELOG] [2012-08-02 18:30:06,201] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:06,201] Rollback Table Encryption.
[UPGRADELOG] [2012-08-02 18:30:06,201] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:08,556] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:08,556] Config Schema Restore started
[UPGRADELOG] [2012-08-02 18:30:08,556] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:08,557] ########### Executing scripts from restore_config.sql ###########
[UPGRADELOG] [2012-08-02 18:30:28,823] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:28,824] Config Schema Restore Completed
[UPGRADELOG] [2012-08-02 18:30:28,832] ----------------------------------------------------------------------------
.
.
.
[UPGRADELOG] [2012-08-02 18:30:59,270] ============================================================================
[UPGRADELOG] [2012-08-02 18:30:59,270] Database rollback completed
[UPGRADELOG] [2012-08-02 18:30:59,270] ============================================================================
[UPGRADELOG] [2012-08-02 18:30:59,270] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:59,270] ************************ Error in FTPSHARE Upgrade *************************
[UPGRADELOG] [2012-08-02 18:30:59,270] ************************ OFSAAI Rollback started *************************
[UPGRADELOG] [2012-08-02 18:30:59,270] ----------------------------------------------------------------------------
[UPGRADELOG] [2012-08-02 18:30:59,272] ============================================================================
[UPGRADELOG] [2012-08-02 18:30:59,272] OFSAAI rollback completed
[UPGRADELOG] [2012-08-02 18:30:59,272] ============================================================================


Reviewing all of the errors in the log, an "Atomic Schema Restore" is performed for multiple atomic schema users.

In the OFSAA environment being upgraded, you have multiple atomic schema users for multiple Infodoms.  However, you only want to upgrade one of the atomic schemas.  The error above occurs for an atomic schema that is no longer used.  However, the error causes the upgrade on the "good" atomic schema and the config schema to be rolled back and causes the upgrade process to fail before the new files are copied.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms