Hmm... could be a bug since it's supposed to tell you that the table devices does not exist.
And there are no different levels of axl access.. if your user has axl access (and thus can send sql queries for instance) the update commands must work (unless you try to do something that would violate the db constraints.. in that case you'll get an error from the database layer telling you what you're trying to do is not permitted).
Hmmmâ¦. The plot thickens. I received an eval phone that I was trying to set up. I was trying to update the tkModel field to the appropriate value so that the phone registration would not be rejected. Apparently update permissions are set on a field by field basis - unless I am missing some referential integrity issue here.
SO, this query works:
admin:run sql update Device set Description="Wes 7 9 2 5" where name = "SEP002290EA9F61"
But this one does not work:
admin:run sql update Device set tkModel=484 where name = "SEP002290EA9F61"
No UPDATE permission.
Ironically, when I look at the type model table, there is an entry, but it's obviously "turned off". Guess I'll have to try and track down a patch or see what I need to turn it on!
admin:run sql select * from TypeProduct where enum=371
enum name moniker tkmodel maxports showindropdown devicenameformat isinstalleddefault devicenamestring
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.