This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Using SQL database, Maximo v6.2.1.
Our INVENTORY table has the Audit flag on and we have a functioning a_inventory table which contains data changes made to INVENTORY. At this time, there are only a few attributes that are being audited and they were set before my time. I'd like to turn on a few more attributes and thought this would be an opportunity to configure the audit settings without having to do a 'hard' dbconfig. I've used this SQL method in the past to set a default value (temp) on the FAILURECODE attribute of the ASSET table.
Process I've used before:
Go to DBConfig, open the OBJECT table, update the ATTRIBUTE and SAVE
Bring down Maximo app and run the following SQLs
1. update maxattribute set defaultvalue='TEMP'
where objectname='asset' and attributename='failurecode'
2. update maxattributecfg set defaultvalue='TEMP'
where objectname='asset' and attributename='failurecode'
and Viola... done.. no DBConfig required.
Has anyone out there used this technique... do you have any useful SQL that I can borrow or comments on this procedure?
I think in this case what you have done - works, but I would
not make this a standard practice. In some instances, you may
end up causing your instance of maximo to not start at all, and
then you will be in real trouble - just because you did not want to
dbconfig. As a rule of thumb you can update the maxattributecfg and then do a dbconfig. Maxattribute is what happens after the new settings are read from maxattributecfg - in some cases database
objects have to be actually created. In later versions, you can
run dbconfig through the front end. Good luck.
--- In MAXIMO@yahoogroups.com, "hcmjo" <joanne_waddell@...> wrote:
>
> Using SQL database, Maximo v6.2.1.
> Our INVENTORY table has the Audit flag on and we have a functioning a_inventory table which contains data changes made to INVENTORY. At this time, there are only a few attributes that are being audited and they were set before my time. I'd like to turn on a few more attributes and thought this would be an opportunity to configure the audit settings without having to do a 'hard' dbconfig. I've used this SQL method in the past to set a default value (temp) on the FAILURECODE attribute of the ASSET table.
>
> Process I've used before:
> Go to DBConfig, open the OBJECT table, update the ATTRIBUTE and SAVE
> Bring down Maximo app and run the following SQLs
> 1. update maxattribute set defaultvalue='TEMP'
> where objectname='asset' and attributename='failurecode'
> 2. update maxattributecfg set defaultvalue='TEMP'
> where objectname='asset' and attributename='failurecode'
>
> and Viola... done.. no DBConfig required.
>
> Has anyone out there used this technique... do you have any useful SQL that I can borrow or comments on this procedure?
>
I agree . I really would recommend this as a good practice. DB Config does
a bunch of things behind the scenes. If you're taking down the Maximo app,
then why not go ahead with the DB Config instead?
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
geoffkresse
Sent: March-13-13 6:12 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Auditing INVENTORY attributes and DBConfig
techniques
I think in this case what you have done - works, but I would
not make this a standard practice. In some instances, you may
end up causing your instance of maximo to not start at all, and
then you will be in real trouble - just because you did not want to
dbconfig. As a rule of thumb you can update the maxattributecfg and then do
a dbconfig. Maxattribute is what happens after the new settings are read
from maxattributecfg - in some cases database
objects have to be actually created. In later versions, you can
run dbconfig through the front end. Good luck.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "hcmjo"
<joanne_waddell@...> wrote:
>
> Using SQL database, Maximo v6.2.1.
> Our INVENTORY table has the Audit flag on and we have a functioning
a_inventory table which contains data changes made to INVENTORY. At this
time, there are only a few attributes that are being audited and they were
set before my time. I'd like to turn on a few more attributes and thought
this would be an opportunity to configure the audit settings without having
to do a 'hard' dbconfig. I've used this SQL method in the past to set a
default value (temp) on the FAILURECODE attribute of the ASSET table.
>
> Process I've used before:
> Go to DBConfig, open the OBJECT table, update the ATTRIBUTE and SAVE
> Bring down Maximo app and run the following SQLs
> 1. update maxattribute set defaultvalue='TEMP'
> where objectname='asset' and attributename='failurecode'
> 2. update maxattributecfg set defaultvalue='TEMP'
> where objectname='asset' and attributename='failurecode'
>
> and Viola... done.. no DBConfig required.
>
> Has anyone out there used this technique... do you have any useful SQL
that I can borrow or comments on this procedure?
>