Missing out-of-the-box fields (sys_created, sys_created_on...) on table

peter_repan
Tera Guru

Hi all,

we are facing curious issue: for some reason we are missing out of the box fields like sys_created, sys_created_by, sys_updated, sys_updated_by (+ other "sys_"... fields) on table alm_hardware.

Don't know where they gone. On wiki is "Base system fields cannot be deleted. Additionally, any missing base system fields are recreated when the instance is upgraded."

My question is - does anyone idea what could happened or how to fix it (without waiting for a upgrade)?

Thank you

1 ACCEPTED SOLUTION

I guess the issue was with Read ACLs alm_asset.* of the parent table. They forbid the admin to read the parent table, so that the record on child table could be read only partially.


View solution in original post

18 REPLIES 18

Please refer the below report by ServiceNow when I create a incident on HI for similar issue:



Most Probable Cause:


The following two properties were set to wrong values hence we were getting the exception 'java.lang.IllegalArgumentException: Illegal pattern character 'Y' ':


'glide.system.locale' had a value 'USD'


and


glide.sys.date_format had a value 'MM/DD/YYYY'



You mentioned that earlier you've changed 'glide.sys.date_format' property.



Solution Proposed:


In order to provide relief we've updated the above two properties to the following values and restarted both nodes.


glide.system.locale = en.US


glide.sys.date_format = MM-dd-yyyy



Also a Problem created for the similar issue: Refer the HI Problem Record PRB624318



Hope this helps.


nehruvj
Giga Contributor

Please refer this also where the system date fields are missing in the table level:



mysql> desc sys_properties;


+--------------+--------------+------+-----+---------+-------+


| Field               | Type                 | Null | Key | Default | Extra |


+--------------+--------------+------+-----+---------+-------+


| name                 | varchar(100) | YES   | UNI | NULL       |             |


| type                 | varchar(40)   | YES   |         | NULL       |             |


| description   | mediumtext     | YES   |         | NULL       |             |


| choices           | mediumtext     | YES   |         | NULL       |             |


| is_private     | tinyint(1)     | YES   |         | NULL       |             |


| ignore_cache | tinyint(1)     | YES   |         | NULL       |             |


| value               | mediumtext     | YES   |         | NULL       |             |


| sys_id             | char(32)         | NO     | PRI |                 |             |


| read_roles     | varchar(255) | YES   |         | NULL       |             |


| write_roles   | varchar(255) | YES   |         | NULL       |             |


| suffix             | varchar(100) | YES   |         | NULL       |             |


+--------------+--------------+------+-----+---------+-------+


11 rows in set (0.00 sec)mysql> desc sys_script_include;


+-----------------+--------------+------+-----+---------+-------+


| Field                     | Type                 | Null | Key | Default | Extra |


+-----------------+--------------+------+-----+---------+-------+


| name                       | varchar(40)   | YES   |         | NULL       |             |


| description         | mediumtext     | YES   |         | NULL       |             |


| script                   | mediumtext     | YES   |         | NULL       |             |


| active                   | tinyint(1)     | YES   |         | NULL       |             |


| client_callable | tinyint(1)     | YES   |         | NULL       |             |


| sys_id                   | char(32)         | NO     | PRI |                 |             |


| api_name               | varchar(100) | YES   |         | NULL       |             |


| access                   | varchar(40)   | YES   |         | NULL       |             |


+-----------------+--------------+------+-----+---------+-------+


8 rows in set (0.00 sec)


Hi Jawaharlal,



I'm sorry but I don't understand the connection with my issue. Could you please explain?


I guess the issue was with Read ACLs alm_asset.* of the parent table. They forbid the admin to read the parent table, so that the record on child table could be read only partially.


Thanks for the update. This will help us to think on ACLs also...