Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12c to OAS 2025 migration Error Import Bar file

Received Response
206
Views
17
Comments

After importing the .bar file through Snapshot in DV, I get the error: The error code is: BAR_600001

I ran a test importing the components separately, and this was the result.

Restore Snapshot:

1. Deployed Model (RPD) - success

2. Jobs - success

3. Configuration and Settings - success

4. Application Toles - success

5. Credentials - success

6. Classic Content - It was a failure

a. Catalog Content - It was a failure

i. Shared Folders

b. User Folders and Personalizatiosn - It was a failure

i. Workbooks

That is, the error occurs with the Catalog Content. Can someone tell me what might be happening and how to solve it?

I would really appreciate your help.

regards,

Joan

Tagged:
«1

Answers

  • GayathriAnand-Oracle
    edited Jun 25, 2025 2:51PM

    Hi

    Please check \importbar_<date>\webcat_content_plugin.0.0.log to see details of why the webcatplugin failed. Do you have HashUserHomeDirectories setting in instanceconfig.xml file?

    If yes please follow workaround steps in this KM doc for import to succeed: Content From User Folders in Hashed Catalog Is Not Migrated From OBIEE 12c to OAS (Doc ID 3021637.1)

    Thanks

    Gayathri

  • Gianni Ceresa
    edited Jun 25, 2025 3:08PM

    What Gayathri said: the logs in <domain>/bilogs/metadata/importbar... are extremely (almost too much) detailed and do contain all the details pointing at what went wrong in the process (it can really be a long log, read it carefully to avoid false-errors that aren't the real root cause but a consequence of it).

    Based on the root cause, then you can take the required actions to prevent/avoid the error.

  • Joan Alvarado
    Joan Alvarado Rank 3 - Community Apprentice
    edited Jun 25, 2025 3:35PM

    HI @Gianni Ceresa @GayathriAnand-Oracle thank you very much for the feedback. Do I need to enable something to see that log in the metadata folder? Because I don’t see any log there.

    I'm going to do a new installation of OAS 2025 to have everything in order, and then import the .bar file again.

    And I would like to know, what is the best way to import the .bar file: via Snapshot through DV, or using the importarchive.sh command?

    Is it necessary to configure LDAPS first before importing the .bar file so that the catalog can recognize the user folders, or if LDAPS is not configured, should it not affect the .bar file import?

    regards,

    Joan

  • You should see the logs in metadata folder without enabling additional logging.

    And yes the users should be created in the target environment before you do a snapshot import.

    thanks

    gayathri

  • Joan,

    You don't really need to redo an install of OAS 2025…

    Every time you import the BAR you can override almost everything, therefore it's a bit like having a new install all the time.

    And I don't see why users should exist to be able to import the catalog: when a user leave the company, the personal folder is still in the catalog, the user is still the owner, even if they don't exist anymore in the LDAP. The catalog objects don't really have a hard dependency on users/groups/app roles.

    Importing the security is different: trying to create application roles and their members if those members do not exist, the import could fail (also because in OAS 2025 even in WebLogic EM there is now a check on the existence on groups before you can add them as members of an approle, therefore it's possible the BAR import also adopted this new default of validating the existence of the member before to add it).

    What I find more interesting is that in OAS 2025 you couldn't find the log files…

    I didn't try with OAS 2025 to import a old BAR (from OBIEE), I did it last time with OAS 2024 and the logs were there. Another user reported that apparently he couldn't find any log when running the export of a BAR. Could it be that in OAS 2025 there is a setting that changed to "off" for that logs? Possible … no clue to be fair (there have been some regressions in OAS 2025 with bad settings by default compared to previous versions).

  • Joan Alvarado
    Joan Alvarado Rank 3 - Community Apprentice

    Hi @Gianni Ceresa

    When I restore the .bar file in the Snapshot, the import only fails when I have 'Classic Content' checked.

    image.png

    If I uncheck 'Classic Content', the import completes successfully.

    While the snapshot is being restored, it creates the directory importbar_20250625_201449_2091284203, but it's empty, and when the restoration finishes, it’s no longer there — it disappears.

    oramid@server:~/app/oracle/product/domains/oas_domain/bilogs/metadata/importbar_20250625_201449_2091284203> ll
    total 0
    oramid@server:~/app/oracle/product/domains/oas_domain/bilogs/metadata> ll
    total 0

    Regarding the roles, I am importing the roles I have in OBIEE 12 into OAS 2025.

    • OBIEE 12c roles
      BIAuthor
      BIConsumer
      BIAdministrator
      _GRP2ROLE_PZQ12
      _GRP2ROLE_VWOS
      _GRP2ROLE_KennzahlenSystem
      _GRP2ROLE_PZP42
      _GRP2ROLE_PZX2
      _GRP2ROLE_PZP32
      _GRP2ROLE_PZP41
      _GRP2ROLE_PZM4
      _GRP2ROLE_BEMI

    • OAS 2025 roles
      BIDataModelAuthor
      BIDataLoadAuthor
      DVConsumer
      BIContentAuthor
      BIServiceAdministrat
      DVContentAuthor
      BIConsumer

    I realized that the roles were overwritten — the roles from the OAS 2025 installation were deleted, and the ones from OBIEE were imported. After that, I was no longer able to log in with the WebLogic user.

    Is this normal? What should be done in this situation?

    regards,

    Joan

  • User_R6QL9
    User_R6QL9 Rank 1 - Community Starter

    Hello,

    I am experiencing the same issue. Getting insufficient privileges after importing the snapshot from OAS 7 to OAS 25.

    Any official Oracle SR about this?

    Thanks,

    Andres

  • Your OBIEE 12c BAR contains mostly only catalog content: your RPD is meant to be somewhat clean (that's good practices) and therefore usually isn't a problem when importing. Your security should also be somewhat clean, even if seeing the _GRP2ROLE_ prefixes those are catalog groups that have been migrated automatically in 12c, without cleaning them up into real approle without that default prefix.

    That's why the catalog import log file is quite important, because it will contains the reasons of the error, and I have no clue why you don't have log on disk once the import happen.

    The security being fully replaced is a, sadly, working as designed. In my opinion it's wrong, very wrong, mostly when importing a previous version of a BAR file. And because of that I always migrate security myself by merging the default security model to preserve the default roles and policies with the custom one.

    There are scripts that can be used to restore the security, I believe there is a document in MOS covering that, but I don't have a link to it…

  • No SR because that would be between the customer raising it and Oracle. But there should be at least one MOS note covering this. Did you try searching in https://support.oracle.com ?

  • I realized that the roles were overwritten — the roles from the OAS 2025 installation were deleted, and the ones from OBIEE were imported. After that, I was no longer able to log in with the WebLogic user.

    Is this normal? What should be done in this situation?

    When you upgrade your system to Oracle Analytics Server, Oracle Analytics Server grants some new permissions to the existing application roles so that your users automatically get access to the new features in Oracle Analytics Server.

    For out-of-place migrations, permissions sets for existing application roles are not overwritten.

    Unlike Oracle Analytics Cloud (OAC), OAS does not enforce a standard security policy for a set of predefined application roles. In OAS, you are free to design your security policy (application roles and permission or permission set grants) however you choose. Consequently, if you import a Snapshot that contains different application roles and/or permission (set) grants than the OAS 'clean slate' installation, the security policy from your Snapshot will be restored. If your security policy does not include grants on certain permissions then you will need to manually add those grants. 

    To review the permission sets available for Oracle Analytics Server or to change any of the default assignments, see Grant or Revoke Permissions Assignments in 

    Managing Security for Oracle Analytics Server

    .