CA Business Service Insight [assign the version number for your book] Issues

Release Notes › Known Issues › CA Business Service Insight [assign the version number for your book] Issues

CA Business Service Insight [assign the version number for your book] Issues

This section discusses the issues that were detected in this version.

ACE Issues

38282

Migration of thousands of metrics from ACE1 to ACE2 sometimes results in errors.

Workaround: In large systems, migrate the metrics in chunks of 1000 until you complete migration of all the metrics.

38284

When a receiver task tries to launch its calculation, it is sometimes blocked because it’s sender task hasn’t progressed enough in its calculation. This is a valid case however, an error is written to the log with the following text:

Error: "#111 the calculation dates boundaries for task X are invalid Dates: [Z - Y]."

Note: The message is written many times until the receiver is able to start calculation. The error message can be ignored.

Initial Data Report Scheduling

As of version 8.2 initial data entities cannot be edited or otherwise modified directly and their corresponding edit icons are disabled.

As a result, Predefined Reports, Admin Reports, and Admin DB Reports cannot be scheduled directly.

To workaround this issue, follow these steps:

Select the report and right-click.
The available options display.
Select "Duplicate".
The Properties dialog displays.
Save the report / booklet with a different name.
Open the duplicated report.
Click Scheduling, Edit to schedule the duplicated report.

Tablespaces

37519

Customers sometimes disable database jobs because they refer to features that area irrelevant for that specific customer.

In some versions (not all) before version 8.2, the designated database login user and designated privileged user were oblidbadmin. In the current version, database jobs are created so that the designated database login user and designated privileged user are Oblicore.

When upgrading to version 8.2, all current jobs (10) created under schema Oblicore or oblidbadmin are automatically removed and are resubmitted under the user Oblicore. As a result, disabled jobs become active.

Therefore, redisable all jobs that were deliberately disabled in the past.

To disable the jobs, we recommend that you set the ‘broken’ attribute and not delete the job altogether. During future migrations, missing jobs can be recreated automatically.

Example:

-- Before upgrade. 
-- This searches for broken jobs. 
-- Record the results.
select what
  from dba_jobs
where schema_user = 'OBLICORE'
   and broken      = 'Y'

-- After upgrade. This selects the jobs 
select job
  from dba_jobs x
where schema_user = 'OBLICORE'
   and what        = 'oblicore.db_mng_forcast_pkg.cre_forcast_new_partition (''PSL'');'

-- This is a possible result.
JOB
---
48

-- This resubmits the job.
begin
   dbms_job.broken (48 , true);
   commit;
end;

-- or:
-- This resubmits the job (SQLplus).

exec dbms_job.broken (48 , true);
commit;