sorry that was my mistake in the information
this is one CDB-- this one displays correctly in the ADDM window
|2782172003|2782172003|AZTEST2C|--cdb
|1070155216|2782172003|TESTPDB|--pdb
this is another CDB that doesnt display correctly
2974455360 2974455360 AZTEST1
there should be a PDB listed here but it is not. I can go to oracle support but figured you would probably be able to provide a faster response
It's probably just not set up on the pluggable. There are some steps to do that here.
Scroll down to "Enabling ADDM in a Oracle 19c Pluggable Database" (about 1/4 of the way down)
I did do those steps before but it looks like i may have messed something up. I set it up on on 13 PDB's and only some are having the issue. what is the +40150
SRC_DBNAME SNAP_INTERVAL
——————– ——————–
AZTEST1 +40150 00:01:00.000000
If this is getting beyond the scope of this conversion i dont mind going to oracle.
I also noticed that the PDB with the ADDM issues do not show up in the DBA_HIST_DATABASE_INSTANCE view.
ok 100% my fault i forgot my / at the end of the EXEC dbms_workload_repository.modify_snapshot_settings(interval=>60)
in the script where the face smack emoji
thanks for your time
Glad you got it going. I added the face smack to your post. 
+40150 00:01:00.000000 is the snapshot interval. This is how often a snapshot of database statistics will be taken. So, that's every 40,150 days and 1 minute, so basically, never. It should have changed when you did modify_snapshot_settings (with the slash, of course).
BTW, you can modify the settings in Toad also, on the snapshot management tab. Just edit the snapshot interval or retention and then click the checkbox above to apply. I'm not sure if it would have worked before the ADDM window in Toad knew your DBID, that's why I didn't mention it earlier.