I'm new to OTRS and have the Beta 4 with ITSM up and running. I'm working on loading CIs into the CMDB. I managed to get 48 items loaded via import ok. Somehow I managed to edit my import config item and removed the check to have 'name' be an identifier. When I ran the import again testing how to update an existing CI, it imported all of them again (duplicates).
I think I could go in and select them with 'bulk' and change them to 'expired' or some other state maybe but I would prefer to delete the records entirely.
Is there a way to remove these duplicates?
Thanks,
Gene
Import CI issues
Moderator: crythias
-
- Znuny newbie
- Posts: 6
- Joined: 12 Sep 2014, 23:09
- Znuny Version: OTRS 3.3
- Real Name: Gene Matthews
- Company: Hitachi CTA, Inc.
Import CI issues
OTRS::ITSM 4 Beta 5
Operating System: CentOS 6.4
Database: MySQL
Operating System: CentOS 6.4
Database: MySQL
Re: Import CI issues
Hello Gene,
I don't know if my answer will be helpful to you since I'm running OTRS 3.3.3 and you're running Beta 4, but there could be some similarities. Also, I'm running it on Linux, so if you're running it on Windows you'll have to translate any directory paths that I mention into their Windows equivalents.
There is a Perl script under the directory /opt/otrs/bin which I have used to delete CI's from the CMDB. The script is called 'otrs.ITSMConfigItemDelete.pl'. You can run this script with the following parameters:
--help (displays the help message)
--all (deletes all the CI's in the CMDB)
--class [name] (deletes all CI's of the class that you select)
--deploymentstate [name] (deletes all CI's of a particular deployment state; can only be used in conjunction with the --class parameter)
--ConfigItem [no.1] [no.2] [no.3] (deletes the individual CI's with the ConfigItem numbers that you provide as arguments to this parameter)
There is also a script in that same directory called 'otrs.ITSMConfigItemListDuplicates.pl' to find out which CI's are duplicated. Use --help to list all of its other parameters.
If you want to prevent duplicates from being created in the CMDB in the first place, you should be able to go to the Admin page, then click on SysConfig. There should be a drop-down menu to select the settings group. Select the ITSM Configuration Management settings group, then click on the Core::ITSMConfigItem subgroup. Look for a setting called 'UniqueCIName::EnableUniquenessCheck'. I found this to be set to "No" by default. When I set it to "Yes", it prevented duplicate CI names from being created in the CMDB.
Hope this helps.
I don't know if my answer will be helpful to you since I'm running OTRS 3.3.3 and you're running Beta 4, but there could be some similarities. Also, I'm running it on Linux, so if you're running it on Windows you'll have to translate any directory paths that I mention into their Windows equivalents.
There is a Perl script under the directory /opt/otrs/bin which I have used to delete CI's from the CMDB. The script is called 'otrs.ITSMConfigItemDelete.pl'. You can run this script with the following parameters:
--help (displays the help message)
--all (deletes all the CI's in the CMDB)
--class [name] (deletes all CI's of the class that you select)
--deploymentstate [name] (deletes all CI's of a particular deployment state; can only be used in conjunction with the --class parameter)
--ConfigItem [no.1] [no.2] [no.3] (deletes the individual CI's with the ConfigItem numbers that you provide as arguments to this parameter)
There is also a script in that same directory called 'otrs.ITSMConfigItemListDuplicates.pl' to find out which CI's are duplicated. Use --help to list all of its other parameters.
If you want to prevent duplicates from being created in the CMDB in the first place, you should be able to go to the Admin page, then click on SysConfig. There should be a drop-down menu to select the settings group. Select the ITSM Configuration Management settings group, then click on the Core::ITSMConfigItem subgroup. Look for a setting called 'UniqueCIName::EnableUniquenessCheck'. I found this to be set to "No" by default. When I set it to "Yes", it prevented duplicate CI names from being created in the CMDB.
Hope this helps.
-
- Znuny newbie
- Posts: 6
- Joined: 12 Sep 2014, 23:09
- Znuny Version: OTRS 3.3
- Real Name: Gene Matthews
- Company: Hitachi CTA, Inc.
Re: Import CI issues
Thanks! That was extremely helpful. We are also running on Linux. We are just learning our way around OTRS:ITSM (have been using a very old version of RT).
Gene
Gene
OTRS::ITSM 4 Beta 5
Operating System: CentOS 6.4
Database: MySQL
Operating System: CentOS 6.4
Database: MySQL