AnsweredAssumed Answered

Schema Migration Fails after upgrade 7.0.2

Question asked by Ashish Ahluwalia on Oct 10, 2017
Latest reply on Oct 12, 2017 by Rakhee Tarar

Like • Show 0 Likes0
Comment • 10

At the very end of the upgrade process from Aveksa RSA via L and G 7.0 to 7.0.2

Lakhwinder Singh, Boris Polikarpov the DB Schema migration fails:

1) Tried re-running the migrate.sh (/home/oracle/deploy/migrate.sh)

java.sql.SQLException: ORA-24344: success with compilation error
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69

If I look at the database, through SQLPLUS Client, I can see that under CHANGED_USER_TYPE, it created a duplicate for SUPERVISOR_NAME, which I can remove manually abd when I re-run script it recreates and fails..

Other Option I tried :

2) The Upgrade and Migrate Guide says, that

If you chose not to migrate the database, when you start RSA Identity Governance and

Lifecycle for the first time after upgrading, the Initialization Status indicates that the database

schema is out-of-date. At the prompt, enter the following password: AuthorizeMigration. The

startup process performs a migration of the database, which updates the schema.

So I Open up the Admin UI, and its says that Schema Must be Migrated and I give the password as AuthorizeMigration, which it accepts and invokes nothing but migrate.sh, (/home/oracle/deploy/migrate.sh) , which again fails as explained above...

Basically the upgrade is impacted due to migrate DB is not working as expected.

Does Anyone know how to fix it please?

regards,

Ashish Ahluwalia

No one else has this question

Outcomes

10 Replies

Boris Lekumovich Oct 10, 2017 2:12 AM
Mark Correct
Correct Answer
Are you trying to upgrade to 7.0.2 GA or 7.0.2 P02?
Like • Show 0 Likes0
Actions
Ashish Ahluwalia Oct 10, 2017 4:57 PM
Mark Correct
Correct Answer
We are upgrading to 7.0.2 GA.

See the output of migrate.sh, and it fails at when it is near 96%, while executing createPublicSchema.sql
....see below

[oracle@tdc2dapp95 database]$ sudo /home/oracle/deploy/migrate.sh
Executing sys statements . . .
[0:00:00   1%] executing initHashesOnMigration.sql
[0:00:01   2%] executing Create Scripts/Update_PerfStats_Profile.sql
----------------------------------------
Starting Migration process: 2017/10/10 16:58:23
Migrating system: tdc2dapp95.transurban.com.au
Migrating From:
    Product Version: 7.0.0
    Build Number : 93958
    Patch Version : P01
Migrating To:
    Product Version: 7.0.2
    Build Number : 126845
----------------------------------------
Executing avuser statements . . .
[0:00:01   5%] executing Upgrade/Utils/Migration_Utils_Pkg.pks
[0:00:01   5%] executing Upgrade/Utils/Migration_Utils_Pkg.pkb
[0:00:01   5%] executing Upgrade/packages/Migration_Pkg.pks
[0:00:01   6%] executing Upgrade/packages/Migration_Pkg.pkb
[0:00:02 16%] executing migration/beforeMigration.sql
[0:00:02 17%] executing migration/statisticsBeforeMigration.sql
[0:00:09 20%] executing migration/updateWorkflow.sql
[0:00:09 20%] .executing com.aveksa.migration.jdbctool.JavaStepUpdateWorkflow
[0:00:10 41%] executing migration/createReportViews.sql
[0:00:16 86%] executing Upgrade/packages/Pre_Migration_Pkg.pkb
[0:00:16 86%] executing Upgrade/Extend_GTT_User_Tables.sql
[0:00:17 87%] executing migration/migrateWorkflowRule.sql
[0:00:17 87%] .executing migration/../Upgrade/packages/WorkflowRule_Migration_Pkg.pks
[0:00:17 87%] .executing migration/../Upgrade/packages/WorkflowRule_Migration_Pkg.pkb
[0:00:18 93%] executing migration/populateReports.sql
[0:00:18 93%] .executing com.aveksa.migration.jdbctool.JavaStepPopulateReports
[0:00:18 95%] executing migration/afterMigration.sql
[0:00:18 96%] executing migration/createPublicSchema.sql
[0:00:18 96%] .executing com.aveksa.migration.jdbctool.JavaStepPublicSchemaViews
/home/oracle/database/migration/createPublicSchema.sql(3):
DECLARE
v_user CONSTANT VARCHAR(30) := 'ACMDB';
BEGIN
PUBLIC_SCHEMA.init(v_user);
commit;
end;
java.sql.SQLException: ORA-24344: success with compilation error
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69
ORA-06512: at line 4

=============================================
ORA-24344: success with compilation error
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69
ORA-06512: at line 4
============================================
Like • Show 0 Likes0
Actions
Rakhee Tarar Oct 10, 2017 5:49 PM
Mark Correct
Correct Answer
ORA-06512: at "AVUSER.SIEM_INTEGRATION", line 134
ORA-06512: at "AVUSER.PUBLIC_SCHEMA", line 69
ORA-06512: at line 4

The error is an exact match with line numbers.

Probably the same cause :
"The custom user attribute SUPERVISOR_NAME conflicted with an
existing, identical attribute during a schema migration."

Fix Version :7.0.2 P02.
Let us have a look at V7.0.2 Patch 2 Release Notes

Also, i would have support case open to double check.
Like • Show 0 Likes0
Actions
- Ashish Ahluwalia @ Rakhee Tarar on Oct 10, 2017 6:06 PM
  Mark Correct
  Correct Answer
  Hi Rakhee,
  
  Thank you for the response.
  
  I searched the release notes -Release 7.0.2 Patch 2 and it does have the mention as below:
  =========================================================
  Migration
  Issue Description
  SF-950767
  ACM-74441
  The custom user attribute SUPERVISOR_NAME conflicted with an existing, identical attribute during a schema migration.
  =========================================================
  
  Does it mean we should upgrade to 7.0.2 patch 02 not the GA build?
  Can we modify the migrate script specifically the one which modifies public schema, i.e createPublicSchema.sql?
  
  Kind regards,
  Ashish Ahluwalia.
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Ashish Ahluwalia on Oct 10, 2017 6:35 PM
    Mark Correct
    Correct Answer
    From the internal notes of the fix (P02), most likely it will resolve the problem you are encountering.
    Is there any specific reason why not to upgrade to the latest patch on top of v7.0.2?
    Like • Show 0 Likes0
    Actions
    - Ashish Ahluwalia @ Boris Lekumovich on Oct 10, 2017 11:35 PM
      Mark Correct
      Correct Answer
      I upgraded from current state(upgraded to 7.0.2 except DB migration)
      to 7.02 HF02. using patch.sh in Aveksa_7.0.2_GAHF02.
      
      After that when I login to Admin UI, it asks to migrate DB and when I authorizeMigration, it goes in same error as above.
      
      Is there a separate migrate.sh is shipped with Aveksa_7.0.2_GAHF02?
      I have just used Aveksa_7.0.2_GAHF02.tar.gz as the installed and ran it .
      
      I cant find any document other than release notes which I followed.
      
      Regards,
      Ashish Ahluwalia,
      Like • Show 0 Likes0
      Actions
Ashish Ahluwalia Oct 11, 2017 7:08 PM
Mark Correct
Correct Answer
Hi Boris and All,

Because we have custom attribute (SUPERVISOR_NAME) in out database, the migration from 7.0 to 7.02 fails.

As per RSA, the upgrade is supported from 7.0 to 7.0.2 and then patch 02 can be applied on it.
I do not think there is a direct upgrade possible from 7.0 to 7.02 patch 02, atleast as per RSA documentation.

Can you please share a process to follow in our case, since the custom attributes were created by RSA professional services. Would really help us move to next version.

Kind regards,
Ashish Ahluwalia.
Like • Show 0 Likes0
Actions
- Boris Lekumovich @ Ashish Ahluwalia on Oct 11, 2017 7:35 PM
  Mark Correct
  Correct Answer
  Hi Ashish,
  Is it stated in the documentation that direct upgrade is not possible from 7.0 to 7.0.2 P2?
  
  I suggest you reach out to support for resolving the migration error.
  
  P.S
  The latest patch on v7.0.2 is P03
  Like • Show 0 Likes0
  Actions
Ashish Ahluwalia Oct 11, 2017 7:39 PM
Mark Correct
Correct Answer
Hi Boris,

Thanks a lot for your reply. I had raised a support case with RSA and was informed by RSA Support engineer that upgrade should be done first to GA build and then patch should be applied.

I also found out the Migration Utility, https://community.rsa.com/docs/DOC-75393
Not sure if this would help fix the issue, at this stage.

regards,
Ashish Ahluwalia.
Like • Show 0 Likes0
Actions
Rakhee Tarar Oct 12, 2017 9:34 AM
Mark Correct
Correct Answer
Hi Ashish,

There is no direct route to go to 7.0.2 P02 directly .
The error is an exact match of ACM-74441 .At this point probably Dev fix is the answer.
Better to have support case open (as you already) to get a workaround/dev fix to go past the error.

Thanks,
Rakhee
Like • Show 0 Likes0
Actions

Schema Migration Fails after upgrade 7.0.2

Outcomes

Related Content

Recommended Content