MAM 7.6.1.2:

I have an Oracle 19c view that is registered with Maximo via the Database Configuration application.
The view is a work in progress; occasionally, I need to make small changes to the way fields are calculated, etc.

Is it OK to update the view via the DB, without recreating the view in Maximo?

I understand that I probably shouldn't make changes to the view that Maximo would see (i.e. rename columns). But I'm wondering if there are changes that would be OK to make through the DB that wouldn't cause problems in Maximo.

Thanks.
#Maximo
#AssetandFacilitiesManagement

Obviously, we recommend keeping Maximo's metadata, which will include the view's query, as synchronized with reality as possible. And there are steps you can take to reduce the pain of recreating the imported object, like having a data-load of XML to put the descriptions and titles back.

That said, as long as the names, types and sizes of the columns don't change, you can probably safely get away with changing the from and where clauses of the view in the database without recreating the object in Maximo / updating Maximo's metadata for the view.

------------------------------
Blessings,
Jason Uppenborn
Sr. Technical Maximo Consultant
Ontracks Consulting
------------------------------

Original Message:
Sent: Wed February 17, 2021 10:31 AM
From: User1971
Subject: Is it OK to update a Maximo view through the DB?

MAM 7.6.1.2:

I have an Oracle 19c view that is registered with Maximo via the Database Configuration application.
The view is a work in progress; occasionally, I need to make small changes to the way fields are calculated, etc.

Is it OK to update the view via the DB, without recreating the view in Maximo?

I understand that I probably shouldn't make changes to the view that Maximo would see (i.e. rename columns). But I'm wondering if there are changes that would be OK to make through the DB that wouldn't cause problems in Maximo.

Thanks.
#AssetandFacilitiesManagement
#Maximo

If that maximo view created based on existing db view (when you crated first view in DB, than created new object in maximo DB configuration manager with same name and maximo will read query and all db columns), than from my point of view better to recreate maximo object (delete existing and create new). To store all existing relationships, MIF objects I suggest to create migration manager package, from other environment (for example from prod) and import it (because there is no possibility to import package from same env). 
But, anyway, you can always trick by editing manually CFG tables.
Tables for views are:
MAXVIEWCFG (MAXVIEW)
MAXVIEWCOLUMNCFG(MAXVIEW)
and default
MAXOBJECTCFG (MAXOBJECT)
MAXATTRIBUTECFG (MAXATTRIBUTE)
I suggest to edit CFG tables, don't forget to change ISCHANGED flags, and than apply db configuration from console to avoid db configuring hang

------------------------------
Andrey Ilinskiy
------------------------------

Original Message:
Sent: Wed February 17, 2021 10:31 AM
From: User1971
Subject: Is it OK to update a Maximo view through the DB?

MAM 7.6.1.2:

I have an Oracle 19c view that is registered with Maximo via the Database Configuration application.
The view is a work in progress; occasionally, I need to make small changes to the way fields are calculated, etc.

Is it OK to update the view via the DB, without recreating the view in Maximo?

I understand that I probably shouldn't make changes to the view that Maximo would see (i.e. rename columns). But I'm wondering if there are changes that would be OK to make through the DB that wouldn't cause problems in Maximo.

Thanks.
#AssetandFacilitiesManagement
#Maximo

Hi, one more thing to consider regarding updates to the view object from a sql tool, Maximo is sometimes sensitive to the datatype of calculated columns. Because this is a case where typically Maximo could not create the error (and normally would not trap the error), problems can be challenging to track down.

------------------------------
keith simmons
------------------------------

Original Message:
Sent: Wed February 17, 2021 10:31 AM
From: User1971
Subject: Is it OK to update a Maximo view through the DB?

MAM 7.6.1.2:

I have an Oracle 19c view that is registered with Maximo via the Database Configuration application.
The view is a work in progress; occasionally, I need to make small changes to the way fields are calculated, etc.

Is it OK to update the view via the DB, without recreating the view in Maximo?

I understand that I probably shouldn't make changes to the view that Maximo would see (i.e. rename columns). But I'm wondering if there are changes that would be OK to make through the DB that wouldn't cause problems in Maximo.

Thanks.
#AssetandFacilitiesManagement
#Maximo