立即与支持人员聊天
与支持团队交流

Identity Manager 8.2.1 - Installation Guide

About this guide One Identity Manager overview Installation prerequisites Installing One Identity Manager Installing and configuring the One Identity Manager Service Automatic updating of One Identity Manager Updating One Identity Manager Installing additional modules for a existing One Identity Manager installation Installing and updating an application server Installing the API Server Installing, configuring, and maintaining the Web Designer Web Portal Installing and updating the Manager web application Logging in to One Identity Manager tools Troubleshooting Advanced configuration of the Manager web application Machine roles and installation packages Configuration parameters for the email notification system How to configure the One Identity Manager database using SQL Server AlwaysOn availability groups

Database errors migrating a database to SQL Server AlwaysOn availability groups

Possible problems

  • The data does not start updating. The Configuration Wizard shows the message:

    The migration cannot be carried out because a replication is currently running.

  • The following error occurs during a One Identity Manager schema update:

    Database error 1468: The operation cannot be performed on database "<database name>" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group. ALTER DATABASE statement failed.

Cause

The database is part of an AlwaysOn availability group.

Solution

  1. Remove the database from the AlwaysOn availability group.

  2. Update the One Identity Manager schema.

  3. Put the database back into the AlwaysOn availability group.

DBQueue Processor does not process tasks

Possible issues

  • After restoring a One Identity Manager database from a database backup, no DBQueue Processor tasks are handled.

  • If the SQL Server in running on a virtual machine and the virtual machine is suspended, it is possible that no DBQueue Processor tasks are handled after restarting the virtual machine.

Probable reason

The SQL Server Service Broker cannot be reactivated during initialization of the DBQueue Processor. The Service Broker is implemented for DBQueue Processor communications.

Solution

Run the following steps using a suitable program for running SQL queries in the database:

IMPORTANT: Select a user that you use for migrating the database to run the SQL queries.

  1. Stop all DBQueue Processor components.

    exec QBM_PWatchDogPrepare 1

    go

    exec QBM_PDBQueuePrepare 1

    go

  2. Check whether other database sessions are active.

    select *

    from sys.sysprocesses p

    where dbid = DB_ID()

    and spid <> @@SPID

    If there are still sessions active, they must be closed first.

  3. Create a new ServiceBroker ID and enable message delivery.

    alter database <database name> set NEW_BROKER

    go

    alter database <database name> set enable_broker

    go

  4. Initializing the DBQueue Processor.

    exec QBM_PDBQueuePrepare 0,1

    go

    exec QBM_PWatchDogPrepare

    go

NOTE: If you restore a test or development database from a backup of another One Identity Manager database, these steps are run by the Database Compiler. In this case, it is not necessary to run the steps manually.

Message: Enter email address in configuration parameter

In a process for sending emails, the value of the SenderAddress or Address parameter is <Enter email address in configuration parameter "...">. Check process parameters in Job Queue Info.

The message is also sent to the One Identity Manager Service log file if extended error reporting in debug mode is configured for the One Identity Manager Service.

Probable issue

One Identity Manager sends email notifications about various actions taken within the system. One Identity Manager email notification system is not completely configured.

Solution

Check the configuration parameters for the email notification system. To do this, use the email configuration wizard.

To start the email configuration wizard in the Launchpad.

  1. In the Launchpad, in the Configuration section, select Configure email connection.

  2. Click Run.

To start the email configuration wizard in the Designer.

  1. In the Designer, in the Base data > General > Configuration parameters category, select the Common | MailNotification configuration parameter.

  2. In theConfiguration Parameter Editor, click ... next to the Value field.

Detailed information about this topic

Removing unnecessary modules from the One Identity Manager database

You can remove modules from the One Identity Manager database that you no longer require in your system.

IMPORTANT:

  • By removing a module, you lose all the data that goes with it. So it is important to make a backup of the One Identity Manager database before removing any modules.

  • In certain circumstances, dependencies to other modules may be deleted by removing a module. Therefore, update the One Identity Manager schema after removing a module.

  • Other tests may be necessary after removing a module. Remove the module in your test environment first and test the One Identity Manager functionality thoroughly. Make sure to also check any custom adaptations that may use functions in the modules that have been removed.

To remove a module

  1. Terminate all web applications using the Internet Information Services (IIS) Manager.

  2. Close all One Identity Manager tools except for Job Queue Info.

  3. Wait until all processes have stopped. You can do this using the Job Queue Info.

  4. Stop all One Identity Manager Services through the services manager.

  5. Stop all application servers using the IIS Manager.

  6. Wait until all DBQueue Processor tasks have completed. You can do this using the Job Queue Info.

  7. Close Job Queue Info.

  8. Start a suitable program for running SQL queries.

    IMPORTANT:

    • Select a user that you use for migrating the database to run the SQL queries.

    • Run the following steps separately using a suitable program for running SQL queries.

      Test the output of the query after each step. The output provides additional tips for removing a module.

    1. Activate single-user mode for the One Identity Manager database.

      exec dbo.QBM_PSingleUserRequest @@spid

    2. Stop the DBQueue Processor components.

      exec QBM_PWatchDogPrepare 1

      go

      exec QBM_PDBQueuePrepare 1

      go

    3. Delete all triggers in the database.

      exec QBM_PTriggerDrop '%', @force = 1

    4. Delete all constraints in the database.

      exec QBM_PConstraintFKDrop '%','%','%'

    5. Delete the module you no longer need.

      exec QBM_PModuleRemove '<3-character module abbreviation>'

      Example:

      declare @ModulesToRemove varchar(100) = 'SAP' + char(7)

      + 'SHR' + char(7)

      + 'SBW' + char(7)

      + 'SAC' + char(7)

      exec QBM_PModuleRemove @ModulesToRemove

      go

    6. If you delete the Business Roles Module (RMB), you must also delete the entries in the OrgRoot table.

      exec QBM_PDeleteDeep '<Key><T>OrgRoot</T><P>3031e9af-6a53-4876-bbfb-0f7fbf264131</P></Key>

  9. End single-user mode for the One Identity Manager database.

    exec dbo.QBM_PSingleUserRelease @@spid

  10. Update the One Identity Manager schema with the Configuration Wizard. Select all remaining modules for updating.

  11. If support sent you hotfixes for this version, then these hotfixes must also be reinstalled.

  12. Start the application server, the One Identity Manager Services and the web applications.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级