Bingo Jim - we have the same issue it seems as ive just posted the same
Please open a support ticket and support can guide you through probably altering the table column length
I filed a support ticket. As a note, our dev environment at 8.3sp1 has the same issue. Both environments use SQL Server.
Same issue on 8.2 SP4 - SQL Server
New bulletin MS13-052 that was added by Shavlik today has a CVEID that is too long to fit into the column assigned in the bladelogic database. .
Defect QM001795382 with description - Catalog update fails with error :- ORA-12899: value too large for column "BLADELOGIC"."DEPOT_SOFTWARE_WIN_BULLETIN"."CVE_IDS" has been logged.
Both Oracle and SQL Server are affected.
Engineering are engaged and a solution will be provided ASAP.
If you experience this issue, please log a support ticket and ask to be linked to QM001795382 and the solution will be provided once it has been released.
Thanks & Regards,
For the SQLServer dbs, can we get the results of the following sent into your respective tickets please?
select data_type from information_schema.columns where table_name = 'depot_software_win_bulletin' and column_name = 'cve_ids';
That query only returns 'varchar' as a result, but looking at the table definition it is a varchar(50).
Is there any update onthis matter ? I have logged a call and had no response as of yet.
Also = is there a way of downloading the remaining of the catalog without this single patch ?
On our test environment we've expanded the varchar and dumped the table as a temp workaround and are in the middle of testing things.
The table looks to have rebuilt successfully after this.
It seems to have worked so far we are able to download the patches and patch analysis and remediation jobs are running ok.
Before we do the same on production can anyone advise if this would have any negative effects anywhere else on the system?
If this is SQL Server and data_type is varchar then you can run the below command :-
ALTER TABLE depot_software_win_bulletin ALTER COLUMN cve_ids VARCHAR(255);
This particular patch belongs to .Net Framework so if you exclude this filter from catalog , it will go successful , but there's no way to exclude just this patch so you have to exclude whole .Net Framework filter.
Sorry , I forgot to mention ,
The fix i suggested will likely break ETL so we will need to have a fix ready for that side as well , The ETA for the BDSSA side fix is currently Monday as they are more extensive than the BSA side change.
Same issue, also on version 8.1.03. The catalogue update failure also means we can't use the catalogue to analyse any servers in our production environments.
I've logged a ticket with support but I have to say I wouldn't be entirely comfortable altering the database on our production systems without testing, but we need to get things up and running ASAP!!
There is a fix availble, do you have a ticket opened with support? If not, please do so and request that it be assigned to me, I'll send the fix to you.
I'd like to have the ticket opened so that we can track how many customer's have been effected by this.