How to solve "Waiting for repository update" with 360Plus

How to solve "Waiting for repository update" with 360Plus

Resolving REPO0032 Error: “ Waiting for repository update ” in 360Plus


Symptom

During a 360Plus backup task, the job fails with the following error:


Error message:
REPO0032: Error updating backup folder: repo003
Status: Waiting for repository update

This error appears in the 360Plus backup task logs.


Environment

  • Product: 360Plus

  • SAP BI Platform: BusinessObjects 4.2 or 4.3

  • Operating System: Windows

  • Database: All supported databases


Cause

The error is triggered when 360Plus cannot verify that the Disaster Recovery repository is configured correctly. This validation is performed through specific registry keys and a database flag.


Resolution

Follow the steps below to correct the configuration.

1. Update the Windows Registry

  1. Open Registry Editor (regedit).

  2. Navigate to the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Prefs\com\g\360\preferences\generic\<bobj_version>

Where <bobj_version> stands for your SAP BI version:

  • 424 for BI 4.2

  • 430 for BI 4.3

  1. In this folder, ensure the following String values exist:

  • RepoConfiguredForDR

  • univ.repo.configured

  1. If they do not exist, create them:

    • Right-click in the right pane → New > String Value

    • Name the key accordingly

    • Double-click the key and set Value data to:

      true

2. Update the 360Suite Database

Open a SQL client connected to the 360Suite database and run the appropriate command.

  • Oracle:

UPDATE plusversconfigentity SET lockrepo = 0;
  • Other databases (SQL Server, PostgreSQL, etc.):

UPDATE plusversconfigentity SET lockrepo = FALSE;

3. Rerun the Backup Job

  • Restart the backup task in 360Plus.

  • The repository status will be recognized correctly, and the backup will proceed.


Note

Ensure that no other 360Suite / 360Plus instance is using the same repository schema when performing these changes.

    • Related Articles

    • Fixing encoding issues in MySQL

      Symptom Encountering character encoding issues when using MySQL database as a repository for 360Eyes. Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence ...
    • DB006 : Could not acquire change log lock

      Symptoms When saving the database configuration in the 360Suite Administration Console, the following error message appears: DB006 : Could not acquire change log lock Cause When the application is upgraded, the database structure is updated (new ...
    • How to create a Webi Destination List

      Environment Product : 360Suite Other relevant information: Client wants to use a Dynamically updating Excel file as Destination List for Cast tasks Resolution Add the Excel Destination file to CMC Then create a WEBI document based on the Excel ...
    • "Invalid tag: FORMAT_DICT" error

      Symptoms After upgrading a BusinessObjects (BOBJ) environment, you may encounter the error with 360Suite feature like 360Cast or 360Bind: Unexpected exception: Failed to parse document. Invalid tag: FORMAT_DICT These features typically work with ...
    • How to expand Dataprovider SQL Query column in 360Eyes database

      Symptom When running 360Eyes Impact Analysis Reports (such as Report 52), users observe that the SQL query stored in the 360eyes_REPORTS.unx / Eye Document / Dataprovider / Dataprovider Sql Queryfield is incomplete, partial or truncated. This often ...