Here are examples of errors raised due to the CNO lack of permissions, when attempting to create the listener.Some important information these errors tell us: 1 The domain controller where those permissions are being checked.Right-click the Computers container and choose Properties. Click the Add button and enter the cluster named object (CNO). Click the Object Types button, check 'Computers' and click Ok and then Ok again. Back in the Properties dialog, click the Advanced button and the "Advanced Security Settings for SQL" dialog should appear. Right click the OU/Container you want the VCO to reside in and click “New” - “Computer.” In the example below, we are creating the listener object in the Computers container. Provide a name for the object (this will be your listener name) and click “OK." 6. Right click the VCO you just created and select “Properties”. If you created your Windows Cluster and named it AGCluster - it would appear in Failover Cluster Manager.This is your CNO: In order to confirm that a lack of CNO permissions is responsible for listener creation failure, launch Powershell with elevated privileges and generate the cluster log on the node hosting the availability group primary replica, where you failed to create the listener: Open the cluster log using Notepad.
Check the state of the WSFC cluster and validate the network name and IP address with the network administrator.Note that Oracle Fail Safe provides a centralized message facility.When you perform an action that results in an error, the system locates the message associated with the error and displays it.cluster action validates the installation and network configuration of the cluster.You can perform a cluster verification at any time.