Oracle object's becomes INVALID in a heteregenous environment
Hello All
We have a 19.21 database running on Exadata in an heteregenous environment
The remote database is IBM1 DB2
We have certian packages and procedures in our Oracle database that have dependencies that live on the IBMi database
We have noticed that IF someone is trying to access a particlar package / procedure and during that time if the connection to the remote database is lost OR that remote database is
down for maintenance, that procedure / package body becomes INVALID
We have a couple of questions about this
#1. Is that a normal behavior documented somewhere in the manuals? i,e, if an oracle object has a dependency on the remote database and that remote database is down or a session