If you need to find out if a SQL Server instance has ForceEncryption turned on at a server level, the only reasonable way to do this is read it through the registry. You must look for:
Yes, crazy that this can happen. But sometimes you just have to live by other people’s (i.e the sysadmin’s) rules.
Here’s some VBScript on making sure a service account stays unlocked. You can schedule it to run periodically. The account it’s run as needs permission to unlock the service account, obviously.
In 10g, if you are trying to make DDL changes on a busy object, you’re met with:
ORA-00054: resource busy and acquire with NOWAIT specified
If you google how to fix this, you're told to re-run the transaction, or find out what’s locking the object. If you're trying to make schema changes on a live system in a scripted/automated way, you don't want to interfere with production processes and you need to deal with re-running the transaction in an automated way. This is the solution: