My database team supports approximately 70 software developers. We have inherited many database maintenance utility scripts, that automate several routine database activities. In our dynamic software development environment we all developers to choose the version of the database schema to run their code against.
Our development environment is a unix variant, i.e. Oracle Solaris. When developers install new versions of the application they must associate the correct version of the database schema. So our team has devised a script to handle this chore for each developer. The problem is this script generates a log file and the naming of this log files sometimes gets missed name with a previous version.
Log file mechanics:
• Log file is named same as script being run
o Log file name is identical to script with a “g” plus number extension
o Example: script=DumpRecord logfile=DumpRecord.g1
• Print all current active variables
• Print all echo statements in script
This database utility script is run at a high rate of frequency almost concurrently by some users. The script allows J2EE software developers to update their individual schemas to run against their application in their isolated environment. Developers are separated by Oracle Solaris Zones, however supported by a single database.
Any ideas to avoid naming conflicts?