The following warning messages are observed when activating a config file containing wildcard entries
Warning 2015-11-10 02:08:58.349170 8053 1 Activation: Cannot expand wildcard specification, invalid schema. Skipping ("OWNER_NAME"."%") (activating sid SIDname[module ocf]
Since the other objects activate successfully and only invalid objects are ignored in activation process, you can do one of the following:
A. Do nothing as no future warnings will appear unless the config file is activated again and moreover such entries will in no way interfere with activation process and only have a nuisance value by way of generating those annoying messages.
B. If the warning messages are too much of a distraction, you can correct the problem by the following steps:
1. Identify all the problem schema that generates the warning.
2. Whenever doing another activation in future, if those problem schema are in the config file in the form of wildcard, make a copy of the active config file, edit the copy prior to activation and comment out entry for each problem schema with a '#' sign as the first character (or remove the entry altogether). Here is an example of commenting it out where the schema SCOTT is problematic:
# expand scott.% scott.% target_server@o.targetSID
3. Activate the copy. This will suppress those messages about invalid schema in all future activation as the invalid schema are removed or commented out from the config file.
