• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 96 subscribers
  • Views 4737 views
  • Users 0 members are here
Options
Related

Installation issue

oim_user
over 6 years ago

Hello

I have some trouble to install OIM (7.1.1) on Oracle database.

While installation  of the database scheam I have the following error message.

Processing step 'QBM ContentWaitForProcessing (wait for processing initial content)' failed.

2 - Wati command failed.

The operation has timed out

Database doesn't show any errors in logs.

Das anyone have an idea what might be the reason of it.

Thanks in advance.

Greg

Parents
  • 0 over 6 years ago

    I will add that it stops at operation "Wait for DBQueue processor"

    Regards

    Greg

  • 0 over 6 years ago in reply to oim_user

    To identify the reason for that timeout I suggest contacting support. One comon reason is, if this is a test system, that your Oracle system is very slow and the migration ran into the timeout on one of the several checkpoint during the process. But there are other possible explanations, that why you might want contact support.

    Or, use a more recent version of OneIM.

  • 0 over 6 years ago in reply to Markus Weiss-Ehlers

    We have solved the problem. You were right, that the Oracle performance was not enough. We have increased the parameter "job_queue_processes" on Oracle and this solved the problem.

    Thanks for your help.

  • 0 over 5 years ago in reply to Markus Weiss-Ehlers

    We've hit the same problem, in this case upgrading from v7.1.1 to v7.1.5 in an Oracle environment - they have already checked the job_queue_processes value and it is set to the maximum (1000) same as production.

    It seems the step is running a fairly I/O intensive query to update QBMFileRevision.FileContent - but I'm having trouble tracking down exactly where this query is defined (I got the query by looking in v$session joined to v$sql while the step was running).

    My assumption is that trying to upgrade v7.1.3 or v7.1.4 would hit the same problem as the upgrade to v7.1.5 (we have tried three times now) so, if we can't identify a mechanism for dealing with the slow performance, we would be thinking of a change to that update statement so it doesn't take as long.

Reply
  • 0 over 5 years ago in reply to Markus Weiss-Ehlers

    We've hit the same problem, in this case upgrading from v7.1.1 to v7.1.5 in an Oracle environment - they have already checked the job_queue_processes value and it is set to the maximum (1000) same as production.

    It seems the step is running a fairly I/O intensive query to update QBMFileRevision.FileContent - but I'm having trouble tracking down exactly where this query is defined (I got the query by looking in v$session joined to v$sql while the step was running).

    My assumption is that trying to upgrade v7.1.3 or v7.1.4 would hit the same problem as the upgrade to v7.1.5 (we have tried three times now) so, if we can't identify a mechanism for dealing with the slow performance, we would be thinking of a change to that update statement so it doesn't take as long.

Children