NeoJax Honored Contributor.
Honored Contributor.
330 views

Unable to map secRole (m1, TEXT) to a5, varchar(50) in operator dbdict

Hi Experts,

We are trying to map field secRole (m1, TEXT) to (a5, varchar(50) in operator dbdict, but getting errors are below:

Operator_1.JPG

Getting the below error:
Operator_2.JPGSQL State: 42000-8180 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared. (record.update,start)
SQL State: 42S21-2705 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Column names in each table must be unique. Column name 'RECORD_NUMBER' in table '
SMSQL9B70B00A36530CD' is specified more than once. (record.update,start).

While saving the change to operator dbdict, I have changed SQL RC from false to true

Operator_3.JPG

Please suggest

Neo Jax 

0 Likes
3 Replies
Madddy Super Contributor.
Super Contributor.

Re: Unable to map secRole (m1, TEXT) to a5, varchar(50) in operator dbdict

can you provide more information as how are mapping the values

0 Likes
Highlighted
NeoJax Honored Contributor.
Honored Contributor.

Re: Unable to map secRole (m1, TEXT) to a5, varchar(50) in operator dbdict

Hi Maddy,

I forget to mention to version for HP Service Manager it is v9.41.

OOB secrole is mapped in operator dbdict as shown in below screenshot:

Operator_4.JPG

Now When I'm trying to map the secrole field as below :

Operator_1.JPGIt is throwing erros as mentioned in above post.

Pls suggest

Neo Jax

0 Likes
Respected Contributor.. Washim Respected Contributor..
Respected Contributor..

Re: Unable to map secRole (m1, TEXT) to a5, varchar(50) in operator dbdict

Hi Neo,

There is another utility apart from dbdict in HPSM, which is called - "System Definition Utility".  Go to left side Navigation pane, Click on "System Definition". Search for Operator table under "Tables". And look out for the field - "Secrole". Double click to expand the field properties. 

Update the alias table name from m1 to a1 and click on "Save". It will update the ddl at the backend. Now go and check the dbdict record. the field should be displaying under a1 as required.

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.