Invalidating space timestamp
If the timestamp of a called remote procedure does not match the timestamp of the called procedure, then the calling (dependent) unit is invalidated and must be recompiled.
In this case, if there is no local PL/SQL compiler, then the calling application cannot proceed.
For the purposes of this FAQ there is no difference, as both need to commit after issuing any form of distributed query.
If the REMOTE_DEPENDENCIES_MODE parameter is not specified, either in the parameter file or using the ALTER SESSION or ALTER SYSTEM DDL statements, then timestamp is the default value.
If the program stays connected to Oracle but goes inactive for a significant period of time (such as a daemon, wait for alert, wait for mailbox entry, etc...) then when Oracle needs to wrap around and reuse the extent, Oracle has to extend the rollback segment because the remote transaction is still holding its extent.
This can result in the rollback segments extending to either their maximum extent limit or consuming all free space in the rbs tablespace even where there are no large transactions in the application.
* * * @param spaces The spaces to check * @param timestamp The timestamp against which to check.
ATG Data Anywhere Architecture™ provides a unified view of content and data across a business for organizations and their customers.
This entry is held until the SQL statement is committed even if the SQL statement is a query.
If the application code fails to issue a commit after the remote or distributed select statement then the rollback segment entry is not released.
If the value of the GLOBAL_NAMES initialization parameter is TRUE, then the database link must have the same name as the database to which it connects.
global_names open_links open_links_per_instance The global_name is made up of the db_name and the db_domain, and the first element (before the first .