CORA error AHD05519 / How to update CORA version?

[EricoDellaVallePrezzi76043714]

We have developed a process to sync CMDB from 12.7 to 14.1 using CABI/grloader. Every time I run the process there are cora issues and I get the following error:

 

AHD05519:Erro ao registrar MDB: (MDB and ca_owned_resource are not consistent; asset_source_uuid(62C754B878D21E4C981D41CE0AC90B02) not found in ca_owned_resource table

 

We have installed CORACLEANUP hoping that the CORA version would be updated and that error would be fixed.

 

Does anyone know a way to update CORA version?

If you type coraver on cmd you see the current version of CORA in use.

 

We have 12.7 and 14.1 versions installed.

 

12.7 coraver:

coraapi     12.5.0.59
corajava    12.5.0.59
coramss     12.5.0.59
coraorcl    12.5.0.59
corasql     12.5.0.59
corasys     12.5.0.59
corauuid    12.5.0.59

 

14.1 coraver:

coraapi     12.5.0.1
corajava    12.5.0.1
coramss     12.5.0.1
coraorcl    12.5.0.1
corasql     12.5.0.1
corasys     12.5.0.1
corauuid    12.5.0.1

 

Thanks

[Anon Anon]

Hi Erico,

 

Cora 12.5.0.1 is the latest version. The error you were referring could occur if there is a CMDB tables inconsistency. You can perform the below steps:

 

pdm_reg_assets -f

pdm_reg_assets -U

 

Run the coracleanup and then run below command:

 

pdm_reg_assets

 

Thanks,

Naveen

[EricoDellaVallePrezzi76043714]

Now I get the following error when running CORACLEANUP

 

a minute or less remainingException in doUpdate: 'IO Error: Software caused conn

ection abort: recv failed', statement: 'Alter table ca_discovered_software ENABL

E CONSTRAINT ca_di_r000002c700000000'

Exception in doUpdate: 'Closed Connection', statement: 'Alter table ca_discovere

d_hardware ENABLE CONSTRAINT ca_di_r000002ac00000000'

 

We are about to make a system restore and rerun the whole process to see if the error persists.

[Aleksandar Stancic]

try this

CORACLEANUP /DATABASE mdb /SERVER localhost /SCOPE all /METHOD reinit /TYPE

2 /USERNAME ServiceDesk /PASSWORD CAdemo123

 

it should reregister CI's in your MDB and fix the problem (just change the parameters to match your environment)

[Anon Anon]

If you still see the same error when running the above command, then replace SCOPE all with SCOPE USD.

 

 

Thanks,

Naveen

[EricoDellaVallePrezzi76043714]

No luck, same error.

Since this is our test environment, we will restore the Database from another environment.