Problems with the lock file

解决Oracle数据库中patch打失败导致的锁问题
最新推荐文章于 2022-03-21 07:48:02 发布
原创 最新推荐文章于 2022-03-21 07:48:02 发布 · 670 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了在使用Oracle数据库时遇到patch打失败并导致锁住问题的情况，通过查看日志和文件存储目录，发现是某个patch未成功安装导致当前patch无法继续安装。解决方案在于删除该锁文件，从而解锁并允许后续patch正常安装。

打patch的时候出现这个错误。

Problems with the lock file
Lock file exists, details are:
 Interim Patch   7120509 is holding the lock from this patch 6864082,
 probably due to previous unsuccessful operation

这种明显说明是7120509这个patch没有打成功而导致无法打6864082这个patch。应该是有lock。

 

查询ls -la $ORACLE_HOME/.patch_storage

total 320
drwxr-x---  11 otzj9i   dba         8192 Dec 10 19:05 .
drwxr-xr-x  58 otzj9i   dba         8192 May 17  2009 ..
drwxr-x---   3 otzj9i   dba         8192 May 17  2009 4695511
drwxr-x---   3 otzj9i   dba         8192 May 17  2009 5695378
drwxr-x---   3 otzj9i   dba         8192 May 17  2009 5868257
drwxr-x---   3 otzj9i   dba         8192 May 17  2009 6122097
drwxr-xr-x   2 otzj9i   dba           96 Dec 10 19:05 6864082
drwxr-x---   2 otzj9i   dba         8192 Dec 10 16:07 7120509
drwxr-x---  13 otzj9i   dba         8192 May 17  2009 8290549
drwxr-x---   3 otzj9i   dba         8192 May 17  2009 8339234
-rw-r-----   1 otzj9i   dba          935 May 17  2009 LsInventory__05-17-2009_10-44-50.log
-rw-r-----   1 otzj9i   dba          846 May 17  2009 LsInventory__05-17-2009_10-45-26.log
-rw-r-----   1 otzj9i   dba          935 May 17  2009 LsInventory__05-17-2009_10-49-41.log
-rw-r-----   1 otzj9i   dba         2315 May 17  2009 LsInventory__05-17-2009_11-46-37.log
-rw-r-----   1 otzj9i   dba         2356 May 17  2009 LsInventory__05-17-2009_11-50-25.log
-rw-r-----   1 otzj9i   dba         2356 May 17  2009 LsInventory__05-17-2009_12-37-19.log
-rw-r-----   1 otzj9i   dba         2315 Jun  2  2009 LsInventory__06-02-2009_11-42-42.log
-rw-r-----   1 otzj9i   dba         2315 Jun  2  2009 LsInventory__06-02-2009_11-43-22.log
-rw-r-----   1 otzj9i   dba          902 Nov 13 19:49 LsInventory__11-13-2012_19-49-41.log
-rw-r-----   1 otzj9i   dba          250 Dec 10 15:38 patch_locked
drwxr-x---   2 otzj9i   dba         8192 May 17  2009 tmp

猜测是这个锁将patch锁住了，无法打下一个patch

z4as8031:testsale > vi patch_locked
"patch_locked" 9 lines, 250 characters
Locked for patch  :  7120509
Locked by class   :  Apply
Locked by process :  8886
Locked at time    :  Mon Dec 10 15:38:35 2012
Effective User ID :  16209
Real User ID      :  16209
Host details      :  z4as8031
RAC node details  :  Not Applicable

果然是这样，删除这个就可以了。

 

详解进程文件锁FileLock
shijinupc的专栏
08-17 2万+
import java.io.FileNotFoundException; import java.io.IOException; import java.io.RandomAccessFile; import java.nio.ByteBuffer; import java.nio.channels.FileChannel; import java.nio.channels.FileL
锁——FileLock 文件锁
wjw的博客
07-25 2492
文件锁（FileLock），使用文件锁锁住文件后，其他进程不能操作读或写文件，除非当前进程release或unlock文件锁。 前两天看码云上的oim项目源码，该项目即使用了文件锁来防止同一账户重复登录（当然，该方法是不太合理的，因为用户换一台电脑或修改锁文件路径即可同一账户重复登录，但也是一个文件锁使用的不错的例子） 文件锁分为共享锁、独占锁，加锁方式有阻塞（lock()）和非阻塞(tryL...
webstorm svn Problems while loading file history 问题
ISaiSai的专栏
09-16 4681
解决办法：    “Version Control” -> “Subversion” -> “Presentation” 下 取消下面選項目 “Show merge source in history and annotations” checkbox to fix the case 参考文档 http://fanli7.net/a/kaifagua
Error:A problem was found with the configuration of task ':app:packageRelease'. > File 'F:\AndroidSt
q9104422999的博客
11-04 5232
异常信息: 配置的属性文件不存在Error:A problem was found with the configuration of task ':app:packageRelease'. > File 'F:\AndroidStudioProjects\sun\SunshineCarLife\app\build\intermediates\res\resources-release-strip
the host '192.168.2.100'is unreachable,The host may be down,or there may be a problem with......解决办法
huicooling的博客
06-07 1万+
我这里遇到这样的问题，是因为网关和网络IP没有配置对造成的，解决办法如下：第一步：打开VM，点中要操作的虚拟机，鼠标点击左上角  编辑/虚拟网络编辑器，如下图所示：            第二步：若是选择自定义网关，即选择如上图的VMnet8模式，选中VMnet8，查看子网IP是否与本地Windows网关是否一致，我这里是192.168.72.0                第三步：NAT设置，...
The Google File System & 译文
天高任鸟飞，海阔凭鱼跃
09-27 3856
The Google File System Sanjay Ghemawat, Howard Gobioff, and Shun-Tak Leung Google∗ 【西周翻译】   ABSTRACT 概述     We have designed and implemented the Google File System, a scalable distributed file sys...
hdu1195 Open the Lock （bfs）
苏苏爱自由
04-16 1608
Open the Lock Time Limit: 2000/1000 MS (Java/Others)    Memory Limit: 65536/32768 K (Java/Others) Total Submission(s): 6618    Accepted Submission(s): 2979 Problem Description Now an emerg
The OSError: Can't read data (can't open directory) encountered when using h5py indicates an issue with accessing the HDF5 file or the underlying data within it. While the error message specifically mentions "can't open directory," in the context of h5py and HDF5 files, this often points to problems with the HDF5 file itself or the permissions to access it, rather than a literal directory issue on the file system. Potential causes and solutions for this error include: Corrupted HDF5 file: The HDF5 file being accessed might be corrupted or improperly closed, leading to unreadable data. Solution: Attempt to open the file with an HDF5 viewer or validate its integrity using HDF5 tools if available. If corrupted, a backup or recreation of the file may be necessary. Insufficient file permissions: The user running the Python script may lack the necessary read permissions for the HDF5 file. Solution: Verify and adjust file system permissions to ensure read access for the user or process attempting to open the HDF5 file. File in use or locked: Another process might be actively using or holding a lock on the HDF5 file, preventing h5py from accessing it. Solution: Ensure that no other applications or processes are concurrently accessing the HDF5 file. Close any other programs that might be using the file. Incorrect path or non-existent file: Although less likely given the specific error message, a typo in the file path or the file not existing at the specified location could lead to read failures. Solution: Double-check the path to the HDF5 file to confirm its accuracy and existence. Issues with underlying HDF5 library: In rare cases, problems with the HDF5 library installation itself (which h5py relies on) could manifest as read errors.
09-08
with h5py.File(file_path, 'r') as f: # 读取数据的操作 data = f['your_dataset'][:] except OSError as e: print(f"Error: {e}") else: print(f"File {file_path} does not exist.") ``` #### 检查文件完整...
[!] Unable to read the license file `LICENSE` for the spec `FirebaseAppCheckInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuth (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuthInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCore (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreExtension (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreInternal (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseInstallations (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `Fyber_Marketplace_SDK (8.3.8)` [!] Unable to read the license file `LICENSE` for the spec `GoogleUtilities (8.1.0)` [!] Unable to read the license file `LICENSE` for the spec `RecaptchaInterop (100.0.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAppCheckInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuth (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuthInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCore (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreExtension (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreInternal (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseInstallations (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `Fyber_Marketplace_SDK (8.3.8)` [!] Unable to read the license file `LICENSE` for the spec `GoogleUtilities (8.1.0)` [!] Unable to read the license file `LICENSE` for the spec `RecaptchaInterop (100.0.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAppCheckInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuth (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuthInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCore (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreExtension (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreInternal (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseInstallations (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `Fyber_Marketplace_SDK (8.3.8)` [!] Unable to read the license file `LICENSE` for the spec `GoogleUtilities (8.1.0)` [!] Unable to read the license file `LICENSE` for the spec `RecaptchaInterop (100.0.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAppCheckInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuth (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseAuthInterop (11.15.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCore (11.8.1)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreExtension (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseCoreInternal (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `FirebaseInstallations (11.8.0)` [!] Unable to read the license file `LICENSE` for the spec `Fyber_Marketplace_SDK (8.3.8)` [!] Unable to read the license file `LICENSE` for the spec `GoogleUtilities (8.1.0)` [!] Unable to read the license file `LICENSE` for the spec `RecaptchaInterop (100.0.0)` [!] The `Unity-iPhone [Release]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Unity-iPhone/Pods-Unity-iPhone.release.xcconfig'. This can lead to problems with the CocoaPods installation
08-07
] The `MyApp [Debug]` build configuration overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-MyApp/Pods-MyApp.debug.xcconfig`. ``` 这种警告通常出现在项目中手动修改...
Locking is not possible in the directory C:\eclipse\configuration\org.eclipse.osgi. A common reason is that the file system or Runtime Environment does not support file locking for that location. Please choose a different location, or disable file locking passing "-Dosgi.locking=none" as a VM argument.Unabled to create lock manager.
07-15
Eclipse may fail to start if there is a file locking issue in the `org.eclipse.osgi` directory, typically due to leftover lock files or processes that did not shut down properly. This can occur when ...
nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sun Sep 28 06:39:34 2025 installer version: 560.28.03 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin nvidia-installer command line: ./nvidia-installer --ui=none --no-questions --accept-license --disable-nouveau --no-cc-version-check --install-libglvnd Using built-in stream user interface -> Detected 16 CPUs online; setting concurrency level to 16. -> Scanning the initramfs with lsinitramfs... -> Executing: /usr/bin/lsinitramfs -l /boot/initrd.img-6.8.0-84-generic -> Multiple kernel module types are available for this system. Which would you like to use? (Answer: MIT/GPL) -> The file '/tmp/.X0-lock' exists and appears to contain the process ID '1790' of a running X server. -> You appear to be running an X server. Installing the NVIDIA driver while X is running is not recommended, as doing so may prevent the installer from detecting some potential installation problems, and it may not be possible to start new graphics applications after a new driver is installed. If you choose to continue installation, it is highly recommended that you reboot your computer after installation to use the newly installed driver. (Answer: Abort installation) ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
最新发布
09-29
我们面临的问题是：在安装NVIDIA驱动时，由于X服务器正在运行以及NVIDIA内核模块已加载，导致安装失败。 根据引用[1]提到的内核版本和gcc版本问题，以及引用[2][3][4]中提到的卸载和清理方法，结合我们之前回答中的...
.git/index.lock
12-27
The `.git/index.lock` file serves as a mechanism to prevent concurrent access conflicts when multiple processes attempt to modify the Git index simultaneously. When performing operations that alter ...
Java 进程间文件锁FileLock详解
热门推荐
我的专栏
09-18 4万+
最近需要在两个进程中对同一个文件进行操作，正好Java 提供了文件锁FileLock类，利用这个类可以控制不同程序（JVM）对同一文件的并发访问，实现进程间文件同步操作。 FileLock是java 1.4 版本后出现的一个类，它可以通过对一个可写文件(w)加锁，保证同时只有一个进程可以拿到文件的锁，这个进程从而可以对文件做访问；而其它拿不到锁的进程要么选择被挂起等待，要么选择去做一些其它的
【死磕NIO】— 跨进程文件锁：FileLock
chenssy 的技术博客
03-21 2542
大家好，我是大明哥，一个专注于【死磕 Java】系列创作的程序员。 【死磕 Java 】系列为作者「chenssy」 倾情打造的 Java 系列文章，深入分析 Java 相关技术核心原理及源码 死磕 Java ：https://www.cmsblogs.com/group/1420041599311810560 上篇文章（【死磕 NIO】— 深入分析Channel和FileChannel）已经详细介绍了 FileChannel的核心原理及相关API，了解了FileChannel是用来读写和映射一个系.
ORA-01940: cannot drop a user that is currently connected
xionglang7的专栏
07-31 3万+
用删除某个用户，但是删除时有用户连接 SQL> conn /as sysdba Connected. SQL> drop user test cascade; drop user test cascade * ERROR at line 1: ORA-01940: cannot drop a user that is currently connected   通过查看用户的进行
oracle rename数据文件的两种方法
xionglang7的专栏
12-11 2万+
第一种  alter tablespace users rename datafile '==' to ‘***'; 这种方式需要数据库处于open状态，表空间在offline的状态下才能更改。   SQL> alter tablespace users rename datafile '/opt/ora10g/oradata/orcl/user0100.dbf','/opt/ora10
oracle 获得两个时间相差的秒数
xionglang7的专栏
06-20 1万+
我们常常只需要得到两个时间相差的秒数，常见的方法是使用EXTRACT来抽取获得的INTERVAL类型的日、时、分和秒来分别计算。 1，创建表 create table t_timestamp (id number, t1 timestamp, t2 timestamp); --插入数据 insert into t_timestamp  values (1, to_timestamp('2
expdp的远程导出到本机
xionglang7的专栏
12-13 1万+
以前总是很困惑expdp要在服务器上去进行导出，然后通过网络传递到本机，今天终于解决了这个难题哈哈 1）在本地计算机中建立directory 2）在本地计算机的tnsnames.ora中配置远程连接的代替字符串 3）在本地计算机中创建db_link  在cmd下输入expdp 用户名/密码 directory=bakdir network=jm234 dumpfil
ORA-12712: new character set must be a superset of old character set
xionglang7的专栏
08-02 1万+
搭建了一台oracle服务端，在建库的时候字符集设置成了AL32UTF8字符集，导致与所有客户端的字符集不一致。 于是我想将字符集修改为ZHS16GBK。 首先查看服务端字符集 select * from v$nls_parameters where parameter = 'NLS_CHARACTERSET' NLS_CHARACTERSET ZHS16GBK 然后用sys用户进行修改
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值