The hcheckemer.pl script (for emergency fix checking) is falling over on this package name. I am thinking it has something to do with the % sign in it.
Other packages with normal names do not fail at all.
Would you mind taking a look?
Release : 13.0.3
Component : CA Harvest Software Change Manager
I suspect the percent sign in the package name would cause an Oracle SQL statement to fail unless it’s escaped because Oracle thinks the percent sign is a wildcard character. The thing is, that looks like a package auto-numbering format. So if this is an active package, what I would expect to see there is a number and not the format. You are most likely getting the format and not an actual number because you’re adding to the package name at the time when you create the package. Here’s how it works:
When I create a package
If I don’t touch the package name and just click OK, I get a package name like this:
But, if I create a package and make any additions or changes to the package name while in the Create Package window:
The package name no longer conforms to the format, so the substitution of a sequence number in the package name doesn’t happen.
However, there’s a way around this. What you can do is configure your “Create Package” process to prevent any changes to the package name at the time of package creation:
After letting the package creation to complete, you can then go back and change the name of the package to include any additional wording you want:
Here’s where you can read more if you want: https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/harvest-scm/13-0/administrating/define-lifecycle-processes.html#concept.dita_9d1af57a6e7508bdfb52bd5bb809bb4a0a451617_DefineaCreatePackageProcess