Re: Database snapshot cloning and lockfiles

  • From: Seth Miller <sethmiller.sm@xxxxxxxxx>
  • To: Don Seiler <don@xxxxxxxxx>
  • Date: Tue, 7 Apr 2015 15:27:17 -0500

It's definitely db_unique_name.

On Tue, Apr 7, 2015 at 3:19 PM, Don Seiler <don@xxxxxxxxx> wrote:

"Usually" is probably the key word. I can tell you with all certainty that
I have lock files that us the db_unique_name and NOT the SID. However it
isn't using either one in this case I'm trying to sort out. I'd be happy
with ORACLE_SID!

Don.

On Tue, Apr 7, 2015 at 3:14 PM, Mladen Gogala <dmarc-noreply@xxxxxxxxxxxxx
wrote:

On 04/07/2015 02:14 PM, Seth Miller wrote:

I think it uses the SID for the lock file but since you are using a
different SID and db_name, my guess is that you are seeing a symptomatic
error message being caused by something else.

It uses the SID, you are correct:

[oracle@oradb ~]$ ls -l $ORACLE_HOME/dbs
total 10248
-rw-rw---- 1 oracle oinstall 1544 Apr 7 16:11 hc_orcl.dat
-rw-rw---- 1 oracle oinstall 1544 Nov 13 2013 hc_rac11.dat
-rw-rw---- 1 oracle oinstall 1544 Dec 20 2013 hc_rst.dat
-rw-r--r-- 1 oracle oinstall 2851 May 15 2009 init.ora
-rw-r----- 1 oracle oinstall 1044 Oct 20 2013 initorcl.ora
-rw-r----- 1 oracle oinstall 954 Nov 12 2013 initrac11.ora
-rw-r--r-- 1 oracle oinstall 1733 Oct 20 2013 initrst.ora
-rw-r----- 1 oracle oinstall 24 Oct 20 2013 lkORCL
----------------------------------------------------------------------
-rw-r----- 1 oracle oinstall 24 Nov 13 2013 lkRAC11
-rw-r----- 1 oracle oinstall 24 Oct 27 2013 lkRST
-rw-r----- 1 oracle oinstall 1536 Jun 13 2014 orapworcl
-rw-r----- 1 oracle oinstall 1536 Nov 12 2013 orapwrac11
-rw-r----- 1 oracle oinstall 10436608 Apr 6 19:28 snapcf_orcl.f
-rw-r----- 1 oracle oinstall 4608 Apr 7 16:11 spfileorcl.ora

Lock files are usually of the form $ORACLE_HOME/dbs/lk$ORACLE_SID

--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com

--
//www.freelists.org/webpage/oracle-l





--
Don Seiler
http://www.seiler.us

Other related posts: