Hi all,
I am preparing for objects migration between two BI 4.1 systems with LCM_CLI command line. Both of the systems are on SP2 release (kinda out of date release) and there is no way to update them before migration. From my past experience I know that LCM_CLI had a problem with migrating of some objects on SP2 (confirmed by SAP) - particularly with DFOs which already existed on the destination system (which basically exist always) resulting in failed migration job. Anyway, I have done a bit of analysis here and found out that every object which is created from a corresponing DFO xml file during installation, has a property of SI_DEFAULT_OBJECT set to true. Objects which are apparently not populated from DFO do not have this property - which basically means that this property is NULL.
However, just yesterday I have found that indeed there are some objects on a brand new system which do not have SI_DEFAULT_OBJECT at all, but still existing on a out of the box BI 4.1 installation.
Example below is an example query for folder hierarchy objects via AdminTools:
SELECT TOP 1000 static, relationships, SI_PARENT_FOLDER_CUID,
SI_OWNER, SI_PATH FROM CI_INFOOBJECTS,CI_APPOBJECTS,CI_SYSTEMOBJECTS WHERE
DESCENDENTS("SI_NAME='Folder Hierarchy'", "SI_ID in (23)") AND SI_DEFAULT_OBJECT IS NULL
LONG USED BO SYSTEM-> Number of InfoObject(s) returned: 744
OUT OF THE BOX BO SYSTEM-> Number of InfoObject(s) returned: 44
Those 44 objects on a brand new BO system are folder structure objects of Samples. My question here is that why these objects are not created with SI_DEFAULT_OBJECT property as well? They were not created by any user intervention. I assume that these objects are not essential for BO system to be operational but are there anyway from scratch installation? Any insight here is appreciated.
Thanks:)
Erik.