Oracle PDB steps not executing in Discovery

[Ashupakasma]

Hello,

Getting issue while discovery is happening for 'Oracle Instance'.

There are some Oracle Instance type Container Data Base(CDB) The attribute is set to 'unknown. As this step is failed the step is not able to execute(Next step is -PDB discovery- Pluggable Database). Please suggest how to overcome this issue.

[AJ-TechTrek]

Hi @Ashupakasma ,

Seems some permission or access issues w.r.t reading that listener.ora or be it any thing in your database environment.

From this error I couldn't make out much, but check the discovery pattern log and you might observe some error in one of pattern step, this would give you pin pointed direction as to what command is failing.

On the applicative credentials, in pattern steps, there will be a configuration to run using applicative credentials, then only it would be used. So when you check the pattern log you can know until which step execution happened. There might be a case where any of the steps didn't use this credential.

I found some good doc reg 12c discovery in SNOW docs, sharing here, it mentions about some permissions in prerequisites, try following this, hope it resolves.

  or

We have the same problem. Only 1 PDB is discovered. The problem is step 10 in the "Get Oracle instance Size info" extension section.

It uses the command:

"export TNS_ADMIN=" + $ora_home_exe + "/network/admin;export ORACLE_HOME=" + $ora_home_exe + "; echo  \"select name from v\$pdbs;\" |" + "\"" + $ora_home_exe + "/bin/sqlplus\" -s " + "$$username$$/'$$password$$'@" + $computer_system.primaryHostname + ":" + $connect_sql[1].listener_port + "/" + $connect_sql[1].service_name

The connect_sql table is filled with multiple PDB's but the above command uses connect_sql[1] as this means only the first item in the connect_sql table is being queried and not the rest. This is why only 1 PDB has been discovered.

The rest of the pattern seems to be able handle multiple PDB's but the above command is wrong.

We have also a case running, but to me this is a bug in the pattern and not an enhancement request. This should have been working from the beginning. Otherwise we would still be discovering Oracle 11 and lower as there is a 1:1 relation between db and instance. This is what is changed in Oracle 12.2 so this pattern has no use when only discovering just one PDB as if there was still a 1:1 relation which is no longer true.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Ashupakasma]

Thanks @AJ-TechTrek ,

But still the issue not resolved. getting below error in 3rd step only

[Leviticus]

What do we change in the pattern to get it to iterate through all the pdb's?