The lock file will only be re-created if the main file exists.

This behavior is relied on is several places.

This reverts commit 46679981.

This is a revert of a revert.  I am putting back my modification
to start archive IDs at 1 because of the following error message
from cta-taped:

Dec  1 18:01:02 itdssbuild01 cta-taped: <155>2016-12-01T18:01:02.172441+01:00 cta-taped[19232]: LVL="Error" TID="19307" MSG="Failed to open tape file for writing" thread="TapeWrite" TPVID="V41001" fileId="0" fileSize="1167" fSeq="1" diskURL="root://itdssbuild01.cern.ch//eos/itdssbuild01/userfiles/testdir/group1?eos.lfn=fxid:0000086c" exceptionMessage="Unexpected fileId in WriteFile::WriteFile (expected != 0, got: 0) or fSeq (expected >=1, got: 1)"
Dec  1 18:01:02 itdssbuild01 cta-taped: <155>2016-12-01T18:01:02.173739+01:00 cta-taped[19232]: LVL="Error" TID="19307" MSG="An error occurred for this file. End of migrations." thread="TapeWrite" TPVID="V41001" fileId="0" fileSize="1167" fSeq="1" diskURL="root://itdssbuild01.cern.ch//eos/itdssbuild01/userfiles/testdir/group1?eos.lfn=fxid:0000086c" exceptionCode="666" exceptionMessage="Unexpected fileId in WriteFile::WriteFile (expected != 0, got: 0) or fSeq (expected >=1, got: 1)”

The drop_oracle_catalogue_schema.sql is raw SQL and contains no
PL/SQL.  The logic to protect a LOCKED catalogue schema is
therefore gone.

Operators/admins should now use the cta-catalogue* command-line
tools instead.  These tools are safe.

This reverts commit 8ea69101.