PUP-1729: Remove Debian Sid from build targets Acceptance testing on Debian Sid (unstable) was failing regularly due to factors outside of our control, like broken packages in the distribution’s own repositories.
abc RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00558: error encountered while parsing input commands RMAN-01009: syntax error: found "identifier": expecting one of: "integer" RMAN-01008: the bad identifier was: mybackup RMAN-01007: at line 2 column 25 file: /tmp/whole_.
For many tasks that use an auxiliary database, RMAN creates an automatic auxiliary instance for use during the task, connects to it, performs the task, and then destroys it when the task is completed.
This allows us to enable agp(4) again for G5 machines which makes X11 usable on the Dual G5 with radeondrm(4).
In the scheduler, make the cost of moving a process to the primary CPU a bit higher.
PUP-1529: Usability regression caused by PUP-1322 Fixes a regression caused by the fix for PUP-1322: syntax errors reached while loading an include would be squelched, which would eventually result in a misleading “class not found” error.
PUP-751: Performance regression due to excessive file watching This performance regression was also linked to PUP-1322: excessive file watching was causing a significant slowdown during catalog compilation.
These duplicate events were particularly problematic for Puppet DB, since they could cause the whole transaction to be rolled back. PUP-1485: test agent/fallback_to_cached_assumes no master is running by default The acceptance test for falling back to a cached catalog would still run with a puppet master, even though the functionality assumed that the puppet master was unavailable.
The test now guarantees that the master will be unreachable by specifying a bogus server.
You do not give any explicit command to connect to automatic auxiliary instances.
RMAN connections to a database are specified and authenticated in the same way as SQL*Plus connections to a database.