Incident Management Context and Intelligence

I used a Netcool/OMNIbus tool "nco_osreport" with -dbinit option, and got the SQL statements ( insert statements) to build New OMNIbus DB .

Then , I noticed that the auto-generated insert statements has two patterns. See below.

  (1) insert into TableName (col1,col2,...,colN) values (val1,val2,...,valN)

  (2) insert into TableName values (val1,val2,...,valN)

The difference between the two insert statements above is whether or not the column names are explicitly specified.

I have two questions .

(Q1) What caused this difference?

(Q2) Can I control the differences in these output specifications using environment variables, registry values, etc.?

Please teach me .

Hi Ken, thanks for your question!  Unfortunately I don't think you are going to get an answer in this forum, this Alerting forum is scoped to the IBM Instana product.  We do have a forum for our AIOps product which includes Netcool/OMNIbus tools in it over here.   I've reposted your question over there!

I used a Netcool/OMNIbus tool "nco_osreport" with -dbinit option, and got the SQL statements ( insert statements) to build New OMNIbus DB .

Then , I noticed that the auto-generated insert statements has two patterns. See below.

  (1) insert into TableName (col1,col2,...,colN) values (val1,val2,...,valN)

  (2) insert into TableName values (val1,val2,...,valN)

The difference between the two insert statements above is whether or not the column names are explicitly specified.

I have two questions .

(Q1) What caused this difference?

(Q2) Can I control the differences in these output specifications using environment variables, registry values, etc.?

Please teach me .