Repository Modeling Changes Repository Metadata: Other Upgrade Considerations

Planning to Upgrade from Oracle BI 10g to BI 11g 1-17 To enable the Administration Tool to open versioned MUD repository files and access MUD history, upgrade all repositories in the MUD directory. Upgrade all repository files in the MUD directory with the following naming patterns, where ddd is the version number: ■ modified subset of repository_name.ddd ■ repository_name.ddd To upgrade MUD repositories so that you can access MUD history: 1. Run bi-init.cmd or bi-init.sh on UNIX to launch a command prompt or shell window that is initialized to the Oracle instance. You can find this utility in: ORACLE_INSTANCEbifoundationOracleBIApplicationcoreapplicationsetup 2. Run obieerpdmigrateutil from the resulting shell window with the desired options, as follows: obieerpdmigrateutil -I input_repository_path -O output_repository_path -L ldif_output_path -U 10g_administrator_username where: input_repository_path is the name and location of the repository that you want to upgrade and encrypt. output_repository_path is the name and location of the upgraded and encrypted repository. This value can be the same as the input repository path. ldif_output_path is the path of the LDIF output file that is generated by the utility. It contains the users and groups from the old repository for importing into the LDAP Identity Store. 10g_administrator_username is the Administrator user name for the repository in the previous release. For example: obieerpdmigrateutil -I C:\mud_dir\my_repos.001 -O C:\upgr\my_repos.001 -L C:\upgr\ldif\my_ldif.ldif -U Administrator 3. When prompted, enter the 10g administrator password and a new repository encryption password. Do not forget the repository password, because you cannot open the repository without it. To avoid errors, use the same repository password for all repository files in the MUD environment. Note: You upgrade versioned MUD repository files using the obieerpdmigrateutil command-line tool. Do not use Upgrade Assistant to upgrade versioned MUD repository files. Similarly, do not use the obieerpdmigrateutil tool to upgrade production repository files. You must use Upgrade Assistant to upgrade the production repository. Tip: If you have a large number of MUD repositories, then you might want to create a script to automate the MUD repository migration tasks.